[cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)

Thu Mar 1 19:55:22 EST 2012

It becomes more complicated as your dial plan gets larger. I do the calling number at the PRI level as my clients (so far) always just want their 10 digit isdn, national numbers outpulsed, for the called number that's trickier. In my scenarios I have to do that at the route pattern level. You can also manipulate the calling number here. I believe there are other places in the call path you can manipulate this, but don't recall off the top of my head

Matthew G. Loraditch - CCVP, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>
________________________________
From: cisco-voip-bounces at puck.nether.net [cisco-voip-bounces at puck.nether.net] on behalf of Lelio Fulgenzi [lelio at uoguelph.ca]
Sent: Thursday, March 01, 2012 7:39 PM
To: Nate VanMaren
Cc: cisco-voip
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)

Thanks Nate.

Does 10 digit local dialing come into play here at all?

When I send local 10 digit calls out as National, I get a +1 on my cell phone. When I send it out as Subscriber, the +1 is gone. Luckily, most cell phones can interpret this correctly, but I'm sure we'll get plenty of calls complaining.

And while marking it as Subscriber will work for calls from one campus, because I use the same route patterns for remote campuses, the calls will come out as subscriber without the +1 but from a long distance number.

I lose either way. :(

Sent from my iPhone...

"There's no place like 127.0.0.1"

On Mar 1, 2012, at 7:24 PM, Nate VanMaren <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>> wrote:

It depends on what your sending out.

So If you’re sending 10 digits in NANP, then it’s national.

International is used when you’re only sending an international number, not with an access code,

If your sending 7 digits, then that’s subscriber number.

If you send out 011 InterNational number you need to set unknown/unknown. If you don’t send the 011, then you send international.

-nate

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, March 01, 2012 2:54 PM
To: Erick
Cc: cisco-voip
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)

I'm wondering if when the PBX passes the call to CallManager it marks it properly and then CallManager just passes that value along. I'm having a bit of a hard time finding the information in the CallManager traces to compare the two calls.

The telco did come back showing that a call from our location did have unknown. I did a quick test and was able to modify the results using a combination of types and plans. I'm hoping to speak to them to get an idea of best practices as to how to mark these.

For example, is it OK to mark all calls as national, or should I mark some as subscriber if appropriate? Do I have to mark my international calls as International? With our TEHO implementation, should I mark the call as national when coming from a different location?

I can just see this being the first change in a domino affect, ugh. Why was this working until only a short time ago?!?!?!

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Erick" <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: "cisco-voip" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Thursday, March 1, 2012 3:57:03 PM
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)
I had the same behavior with a Siemens PBX and CUCM to multiple cellular carriers.  It didn't make sense but it worked.

On Mar 1, 2012, at 2:48 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
Something to review, but I can force a call out the same gateway that calls from the PBX are sent out of and still have Unknown appearing.

Very weird.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Erick" <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: "cisco-voip" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Thursday, March 1, 2012 3:40:55 PM
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)
Been there.

Verify you have the proper information in the dropdowns in the 'call routing information - outbound calls' section of the PRI/gateway configuration.

On Mar 1, 2012, at 2:24 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

OK, here's a weird one.

We have had complaints about calls from our campus showing up as Unknown to a certain (Rogers) carrier.

I've done some testing and can replicate the problem using different phones, different gateways, different telco providers (Telus, Bell), etc. All show the same results. Unknown to Rogers customers, but the correct number to other carrier customers (Bell).

The one anomaly is when an outbound call is placed from one of our legacy PBX phones which are connected to our Cisco system via T1/PRI. Calls from these phones have the correct calling party number displayed on Rogers clients phones.

I've tried to replicate (albeit one at a time) any difference between the call routing from the HiCom vs the IP phone and no difference in the outcome.

Anybody have any clue what might be causing this?

My first thought is that it is a Rogers issue, but the fact that we are sending the number out for a particular group of users and it works fine has me thinking. Could the calls be marked slightly differently and this difference is not recognized by Rogers?

The problem only started happening a few months ago.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120302/b21c77fc/attachment.html>