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

[Matthew Loraditch]

We have seen the same thing with at&t wireless here in the states. It in some cases helps to force your Calling Party ISDN type and plan to whatever settings they should be for the numbers you send, rather than let CCM decide which can end up with them coming out as unknown/unknown.


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 [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike Olivere
Sent: Thursday, March 01, 2012 3:30 PM
To: Lelio Fulgenzi
Cc: cisco-voip
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)


Did you debug q931 and compare legacy pbx to cisco cm outputs?


Sent from my iPhone

On Mar 1, 2012, at 3: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120301/0142b33b/attachment.html>