Company Forums » Companies beginning with C » Callcentric > Inbound caller id showing 12 numbers

Inbound caller id showing 12 numbers

Hmm. I've never seen this happen using CC with a variety of devices including PAP2T.

Let me ask:

On your PAP2T under Admin/Advanced settings (»192.168.0.xxx/admin/advanced), on the "Regional" page, is the Caller ID method set for "Bellcore--North America/China", and is the Caller ID FSK set to "Bell 202" ??

This may not relate to the problem at all, but it won't hurt to check.

Yes, those are the settings. This is driving me crazy, and probably CC Tech Support also:) They have been superb but insist they are only sending the standard 11 digit string.

Today, I took a brand new PAP2, performed a factory reset just to be sure, configured line 1 on CC and line 2 on voip.ms. tests show the CC side is receiving the additional 1 while the voip.ms is not. I was with VoicePulse for years using these PAP2's and never had this problem.

Thanks for your response and I'm open to any other suggestions available.

As a diagnostic test:

1) Download the very basic CallCentric softphone.
»www.callcentric.com/support/devi···lcentric

2) Unplug your PAP2T device temporarily.

3) Set up the CallCentric softphone, which is just punching in the 1777 number and your password. Let it register.

4) Using another phone line, call your CallCentric DID. The call will ring on the softphone. What does the caller ID on the softphone say?

-------------------------------------------------

Another test:

Call FROM your Voip.MS line TO your CallCentric account, two different ways:

1) By calling the CallCentric DID.

2) By making a Voip.MS speed dial entry using 1777xxxxxxx@in.callcentric.com (Again, that is syntax of in.callcentric.com)

What are the results of these two methods as far as the CID??

The call from a pots line showed 1 area code and number.

The call from the VOIP.MS line showed anonymous although a call from that number anywhere else shows the caller id.

Another test, I forwarded the CC line to the voip.ms line. Same problem, an extra 1. However if I call the voip.ms line direct the extra 1 is not present.

reply to jamesdean123
Another test, if I forward to the voip.ms via the sip uri the extra 1 is there. If I forward to the voip.ms via the direct did the extra 1 is not there.

I've no idea, I'm sorry. Nothing seems to fit.

It must be something very unusual and very subtle. I hope that it works out for you....

Thanks again for all of your help. I see that you are using both services and at least for my purpose which is only US calling voip seems to be somewhat cheaper plus 6 second billing.

Would you care to share your thoughts on each service as far as dependability, call quality and tech support? At this point I am ready to just move over to voip the only negative is I just paid $50.00 to port 2 numbers to CC.

Having moved from VoicePulse after many years without this problem, do you still think it could be a CLEC issue?

If I added another DID from CC and the problem exists would that eliminate a CLEC issue?

Thanks again for all of the time you spent on this.

I think I'm making progress. I received a call from CC today and was asked to ask voip to analyze the call records from the above referenced test. Voip responded and confirmed the SIP URI call did in fact have an extra 1 in it.

Keeping fingers crossed.

I'm sorry. I must correct the above statement. According to the information available to me as a person who supervises this issue (from CC side) - Voip.ms has NOT confirmed that "the SIP URI call did in fact have an extra 1 in it". They confirmed (and that was clearly seen from their call detail records) that the SIP URI in fact "have 1 in it". - please note - there is very big difference between saying "have 1" and "have extra 1". As the [Voip.ms] CDR shows (in the picture attached to your support message) - the VOIP.ms received the call with CLID matching 100% the one that Callcentric sent to. The CLID presented by Callcentric for calls originated from/to North American lines always has 11 digits in a format 1-NPA-NXX-YYYY.

My understanding is that Voip.ms shows the CLID precisely the way they receive it - therefore if/when it's received in NPA-NXX-YYYY format - it's shown without "1" in the CDR while when it's received in 1-NPA-NXX-YYYY format - it's also shown as such.

It appears as both, your Caller ID device and your PIKA telephony card were manufactured before the VoIP era begun therefore they always add "1" in front of whatever they receive - I have also still such device in my possession - even when it received international CLID, something like 34-234-567-8900-22, it still adds "1" in front of the number...

Thank you for your response. However, the following are the facts which also have been submitted in your aforementioned trouble ticket:

1) This hardware has been used for over 6 years with VoicePulse, obviously a VOIP service without the incoming calls having a 12 digit caller id.

2) This hardware configured with VOIP.MS does not have the caller id with 12 digits.

3) This hardware configured with a POTS line does not have the caller id with 12 digits.

4) 2 of the 5 devices showing the 12 digit caller id have been purchase in the last 12 months so they are obviously within the time frame of VOIP technology.

5) Calls forwarded from CC to VOIP.MS via SIP URI contains 12 digits, calls forwarded direct to the VOIP.MS DID number do not. Why the difference?

The only factor in this configuration that causes the problem is CC.

As discussed in my aforementioned postings CC has been great in customer support. Unfortunately, I have a problem not present with any other provider that neither of us can diagnose and therefore we are not a fit.

I'm apologizing again, the point #5 is not correct. I personally saw the information you sent to Callcentric (as I wrote - I personally supervised this issue since the day one you asked us about - simply because it's out of ordinary, very peculiar case).

Calls forwarded via SIP URI NEVER showed 12 digits - it's confirmed by the CDRs you attached from Voip.ms - they were all 11 digits beginning with "1".

It was your DEVICE which _showed_ 12 digits when call was forwarded from Callcentric to VOIP.ms via SIP - those totally are TWO different things - the fact _what_ your device shows and the fact _what_ was sent (and what you may see within CDRs even on Voip.ms side).

Again - please try to understand me (as well as the person who worked with your from our support department) - it's absolutely irrelevant that your device worked with Voice Pulse or that you have 5 more other devices or phones (I have those too... in my garage). I've already explained that - your device WILL show correct 11 digit CLID when it's received as 10 digits (without "1" in front at all, so called NPA-NXX-YYYY format) - then that device will ADD "1" in front of CLID thus MAKING it look correct. It was appropriate logic 5, 10 and 20 years ago. BEFORE the VoIP era started. Because Callcentric operates Internationally - it ALWAYS sends CLID in International format. Which is Country code first. In case of North America - country code is "1". Thus CC sends North American number as "1" followed by 10 digit NPA-NXX-YYYY..

Yes, I perfectly understand that in your case it worked (also perfectly ) with other providers. But that doesn't work with Callcentric - then it's either the time to change provider (pity for us) or change your hardware (or change setting of it, if possible) or keep forwarding calls to another provider (thus unfortunately paying double toll) who shows the CLID in 10 digit format.

Callcentric support advised and many times asked you to install any soft-phone like X-Lite or Zoiper - those would right away show you that the CLID received from Callcentric is 11 digit, 1-NPA-NXX-YYYY format.
For whatever reason you have not conducted the above simplest (5 minutes to get results) test. Also our support has sent to you SIP traces clearly showing the CLID in proper 11 digit format.

Here are 4 other simplest ways to find out about the CLID received from Callcentric:

1. PSTN method: Setup DID forward to: 18004444444 (Verizon/MCI CLID reader) which will read back your ANI - this would be to the PSTN.
2. International iNUM CLID reader: Setup DID forward to: 011883510000000093 which will read back your CLI - this would be to iNum's CLI test.
3. iNUM to SIP URI: 011883510074745000 which will read back your CLI - this would be via iNum to SIPPhone (now Gizmo/Google).
4. "Genuine" SIP URI: 17474745000@proxy01.sipphone.com - Direct via SIP URI to SIPPhone (now Gizmo/Google) - it will also read aloud the CLID received from the call.

In all those examples you'll actually hear the caller ID read back to you - it'll match the normal 11 digit format beginning from "1".

I do hope that this "exhausting", leading nowhere, case can be closed now.

Can we agree to disagree? In business we sometimes have issues that just cannot be resolved and this is the case for the both of us.

I have initiated a partial port until I decide what I will be doing with the 2ND number. I trust that CC will respond in the same courteous and professional manner that I have experienced thus far, at least through your online support system.

Sure, I absolutely agree with you on that there are issues that cannot be resolved and _this_ is one of them.

I even absolutely agree that your device (or multiple devices) show extra "1" and 12 digits CLID when a call comes from Callcentric - right, but that is specific to a particular device or a group of which may add its own "1" in front of a number.

But being a professional network engineer who has facts on hands and all possible ways to verify them while those verification methods are public and available to anyone who wants to use them including yourself - I cannot agree with a declaration that "Callcentric sends extra "1" or that it sends 12 digit Caller ID" - this statement is incorrect because Callcentric sends 11 digit CLID which begins with "1" followed by NPA-NXX-YYYY for North American numbers.

Yes, you may trust CC and its support (I don't usually participate in the support myself, but I may supervise some issues/cases) team. I'm apologizing if my replies in this thread could be interpreted in any way other than strictly professional engineering input (English was my 5th language which I've started to learn when I was 30, still learning).

reply to jamesdean123
Wow, what is your 1st language? It's not relevant to the discussion at hand but since you brought it up it has peaked my curiosity.