[cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)
Mike O
mikeeo at msn.com
Fri Mar 2 16:13:34 EST 2012
Calling and called transformation patterns are your friend here. You can set isdn types at the egress gateway
Date: Fri, 2 Mar 2012 14:25:13 -0500
From: lelio at uoguelph.ca
To: mikeeo at msn.com
CC: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)
OK. Well, this is odd. The call from the PBX is definitely populating the calling party information, which is why calls are showing up on Rogers phones. This is where calls from the IP sets are not doing this. But conversely, calls from the IP sets having the called party information populated, but the PBX calls do not. Strange! OK, not that strange, it's probably how the PBX is marking calls.
Well, at least it provides a reasoning behind the difference.
Thanks all....
Mar 2 13:32:51: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0003 Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xE9808397 Exclusive, Interface 0, Channel 23 Display i = 0xB1, 'Lelio Fulgenzi' Calling Party Number i = 0x0081, '519<snip>' Plan:Unknown, Type:Unknown Called Party Number i = 0xA1, '1226<snip>' Plan:ISDN, Type:National Locking Shift to Codeset 5 Codeset 5 IE 0x41 i = 0x84890100000000Mar 2 14:13:03: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0860 Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xE9808396 Exclusive, Interface 0, Channel 22 Calling Party Number i = 0x2183, '519<snip>' Plan:ISDN, Type:National Called Party Number i = 0x80, '1226<snip>' Plan:Unknown, Type:Unknown Locking Shift to Codeset 5 Codeset 5 IE 0x41 i = 0x84890100000000
---
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: "Lelio Fulgenzi" <lelio at uoguelph.ca>
To: "Mike Olivere" <mikeeo at msn.com>
Cc: "cisco-voip" <cisco-voip at puck.nether.net>
Sent: Friday, March 2, 2012 12:24:27 PM
Subject: Re: [cisco-voip] Calling Party Number not showing up on some carriers sets (most of the time)
I'd like to try out this debug q931 stuff...
I can push calls out to a particular 3845 gateway.
Is debugging q931 stuff process intensive?
Is "debug isdn q931" all I need?
---
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: "Mike Olivere" <mikeeo at msn.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "cisco-voip" <cisco-voip at puck.nether.net>
Sent: Thursday, March 1, 2012 3:29:33 PM
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> 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
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
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/20120302/33c34bd0/attachment.html>
More information about the cisco-voip
mailing list