[cisco-voip] Caller-id and name debugging
Ryan Ratliff
rratliff at cisco.com
Mon Sep 25 14:52:21 EDT 2006
His was outbound so it would have been included in a Display IE if CM were
configured to send it.
-Ryan
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert Kulagowski
Sent: Monday, September 25, 2006 2:39 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Caller-id and name debugging
bababooey at cox.net wrote:
>>From the Voice-GW, debug q931. This is a call from CCm to PBX.
> Where is the calling name supposed to be?
RX <- SETUP pd = 8 callref = 0x1E2C
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98382
Exclusive, Channel 2
Facility i = 0x9F8B0100A10F02017606072A8648CE1500040A0100
Protocol Profile = Networking Extensions
0xA10F02017606072A8648CE1500040A0100
Component = Invoke component
Invoke Id = 118
Operation = InformationFollowing (calling_name)
Name information in subsequent FACILITY
message
Calling Party Number i = 0x2181, '<snip>'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '<snip>'
Plan:Unknown, Type:Unknown Sep 25 13:35:48.820: ISDN
Se0/2/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x1E2C
Facility i =
0x9F8B0100A117020177020100800F544453202020202020202020202020
Protocol Profile = Networking Extensions
0xA117020177020100800F544453202020202020202020202020
Component = Invoke component
Invoke Id = 119
Operation = CallingName
Name presentation allowed
Name = TDS Sep 25 13:35:48.856: ISDN
Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x9E2C
Channel ID i = 0xA98382
Exclusive, Channel 2
Sep 25 13:35:48.856: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8 callref =
0x9E2C
Progress Ind i = 0x8088 - In-band info or appropriate now available
=======
From your example it doesn't look like calling name is being delivered, and
in mine the calling name was "TDS". But watch your debug for a little while
and make sure that the one example you sent wasn't a fluke.
If you're consistently not getting it, tell your provider.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list