|
Home > Archive > Voice over IP Cisco > September 2006 > Caller-id and name debugging
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Caller-id and name debugging
|
|
| Bob A. Bowie 2006-09-25, 1:12 am |
| Hello, I have a CCM 4.1.3 with an mgcp gw running a PRI on 2811 isr.
I am trying to pass caller-id name and number, i am getting the calling
number but not the name.
Which debug do I need to run on the voice gw to see if the info is passing?
Which CCM trace would display if the call manager is sending and receiving
the info?
Thanks.
| |
| Aman Chugh 2006-09-25, 1:12 am |
| debug isdn q931.
http://www.cisco.com/en/US/products...080237271.shtml
Aman
On 9/25/06, Bob A. Bowie <bababooey@cox.net> wrote:
>
> Hello, I have a CCM 4.1.3 with an mgcp gw running a PRI on 2811 isr.
> I am trying to pass caller-id name and number, i am getting the calling
> number but not the name.
>
> Which debug do I need to run on the voice gw to see if the info is
> passing?
> Which CCM trace would display if the call manager is sending and receiving
> the info?
>
> Thanks.
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| J. Oquendo 2006-09-25, 1:12 am |
| On Mon, 25 Sep 2006, Bob A. Bowie wrote:
> Hello, I have a CCM 4.1.3 with an mgcp gw running a PRI on 2811 isr.
> I am trying to pass caller-id name and number, i am getting the calling
> number but not the name.
>
> Which debug do I need to run on the voice gw to see if the info is passing?
> Which CCM trace would display if the call manager is sending and receiving
> the info?
>
> Thanks.
debug isdn q931
--
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
=+=+=+=+=+
J. Oquendo
http://pgp.mit.edu:11371/pks/lookup...arch=0x1383A743
sil infiltrated . net http://www.infiltrated.net
"How a man plays the game shows something of his
character - how he loses shows all" - Mr. Luckey
| |
|
| >From the Voice-GW, debug q931. This is a call from CCm to PBX.
Where is the calling name supposed to be?
2811#
*Sep 25 16:32:16.651: ISDN Se1/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 = 0xA98397
Exclusive, Channel 23
Net Specific Fac i = 0x00E6
Calling Party Number i = 0x0081, '5670800'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '2757001'
Plan:Unknown, Type:Unknown
*Sep 25 16:32:16.671: ISDN Se1/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8003
Channel ID i = 0xA98397
Exclusive, Channel 23
*Sep 25 16:32:16.675: ISDN Se1/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8003
Progress Ind i = 0x8081 - Call not end-to-end ISDN, may have in-band info
*Sep 25 16:32:36.235: ISDN Se1/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0003
Cause i = 0x8090 - Normal call clearing
*Sep 25 16:32:36.247: ISDN Se1/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8003
*Sep 25 16:32:36.267: ISDN Se1/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0003
2811#
---- Aman Chugh <aman.chugh@gmail.com> wrote:[vbcol=seagreen]
> debug isdn q931.
>
> http://www.cisco.com/en/US/products...080237271.shtml
>
> Aman
>
>
> On 9/25/06, Bob A. Bowie <bababooey@cox.net> wrote:
| |
| Ryan Ratliff 2006-09-25, 1:11 pm |
| It can be in a few places actually.
In the CCMAdmin page for this endpoint do you have "Display IE Outbound"
checked? This is required for CM to present the Display IE in the Q931
Setup message.
It will require a reset of the gateway to take affect (will drop calls). If
you have 'ccm-manager config' enabled simply reset it via CCMAdmin. If you
are not using that feature you will need to do a 'no mgcp/mgcp' on the
router.
-Ryan
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of bababooey@cox.net
Sent: Monday, September 25, 2006 12:29 PM
To: Aman Chugh
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Caller-id and name debugging
>From the Voice-GW, debug q931. This is a call from CCm to PBX.
Where is the calling name supposed to be?
2811#
*Sep 25 16:32:16.651: ISDN Se1/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 = 0xA98397
Exclusive, Channel 23
Net Specific Fac i = 0x00E6
Calling Party Number i = 0x0081, '5670800'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '2757001'
Plan:Unknown, Type:Unknown *Sep 25 16:32:16.671: ISDN
Se1/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8003
Channel ID i = 0xA98397
Exclusive, Channel 23
*Sep 25 16:32:16.675: ISDN Se1/0/0:23 Q931: RX <- ALERTING pd = 8 callref =
0x8003
Progress Ind i = 0x8081 - Call not end-to-end ISDN, may have in-band
info *Sep 25 16:32:36.235: ISDN Se1/0/0:23 Q931: TX -> DISCONNECT pd = 8
callref = 0x0003
Cause i = 0x8090 - Normal call clearing *Sep 25 16:32:36.247: ISDN
Se1/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8003 *Sep 25
16:32:36.267: ISDN Se1/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref =
0x0003 2811#
---- Aman Chugh <aman.chugh@gmail.com> wrote:
> debug isdn q931.
>
>
http://www.cisco.com/en/US/products..._tech_note09186
a0080237271.shtml[vbcol=seagreen]
>
> Aman
>
>
> On 9/25/06, Bob A. Bowie <bababooey@cox.net> wrote:
receiving[vbcol=seagreen]
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Robert Kulagowski 2006-09-25, 7:12 pm |
| bababooey@cox.net wrote:
> 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 = 0x9F8B0100A10F02017606072A8648CE1500040A
0100
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 =
0x9F8B0100A117020177020100800F5444532020
20202020202020202020
Protocol Profile = Networking Extensions
0xA117020177020100800F544453202020202020
202020202020
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.
| |
| Ryan Ratliff 2006-09-25, 7:12 pm |
| 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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Robert Kulagowski
Sent: Monday, September 25, 2006 2:39 PM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Caller-id and name debugging
bababooey@cox.net wrote:
> 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 = 0x9F8B0100A10F02017606072A8648CE1500040A
0100
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 =
0x9F8B0100A117020177020100800F5444532020
20202020202020202020
Protocol Profile = Networking Extensions
0xA117020177020100800F544453202020202020
202020202020
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|