Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

NOT Receiving name Display of IP extension when PBX phone calls

I need to verify the setup of the gateway or the RDB. When callers on PBX phones call 7960 IP phones they do not receive the name of the caller until the call is answered or goes to voice mail. Would like it to show up when the call is placed. Using a VG200 as a gateway with DM100 as primary switch type. D-channel is set with RCAP as ND2.

5 REPLIES
New Member

Re: NOT Receiving name Display of IP extension when PBX phone ca

It may be the configuration of the 7960 phones. Take a look at the following URL to see if that helps.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/admin_gd/3_0_5/p6phones.htm#1097557

New Member

Re: NOT Receiving name Display of IP extension when PBX phone ca

The only section of this that would apply would be the H.323 Cient-specific devices which would be the VG200 gateway and I have alll the IE entries that apply checked. I can see the name come across on the VG200 q.931 trace.

New Member

Re: NOT Receiving name Display of IP extension when PBX phone ca

Do you see the name in the Display IE?

If you do, run a debug MGCP packet and make sure the information is being backhauled correctly to CallManager.

Regards,

Justin

New Member

Re: NOT Receiving name Display of IP extension when PBX phone ca

I do see the name in the Q.931 trace. It is aftewr the Notify. I have attached the q.931 trace and the MGCP packet debug. How do I decifer the MGCP packet data?

Ybor-1VG200gtway2#

.Feb 6 14:42:33.120: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8 callref = 0x07

Bearer Capability i = 0x8090A2

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xE9808307

Exclusive, Interface 0, Channel 7

Display i = 0xB1, 'CALL PILOT WORKSTA.'

Calling Party Number i = 0x0980, '25070'

Plan:Private, Type:Unknown

Called Party Number i = 0x89, '25633'

Plan:Private, Type:Unknown

.Feb 6 14:42:33.180: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x87

Channel ID i = 0xE9808307

Exclusive, Interface 0, Channel 7

Ybor-1VG200gtway2#

.Feb 6 14:42:33.180: ISDN Se1/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x87

Progress Ind i = 0x8088 - In-band info or appropriate now available

Ybor-1VG200gtway2#

.Feb 6 14:42:45.268: ISDN Se1/0:23 Q931: TX -> NOTIFY pd = 8 callref = 0x87

Notification Ind i = 0xF1

Display i = 0xB2, ' Bob Brumm'

.Feb 6 14:42:45.272: ISDN Se1/0:23 Q931: TX -> PROGRESS pd = 8 callref = 0x87

Progress Ind i = 0x8188 - In-band info or appropriate now available

.Feb 6 14:42:45.820: ISDN Se1/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x87

.Feb 6 14:42:45.844: ISDN Se1/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x

07

Ybor-1VG200gtway2#

.Feb 6 14:42:46.584: ISDN Se1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x0

7

Cause i = 0x8190 - Normal call clearing

.Feb 6 14:42:46.608: ISDN Se1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x87

.Feb 6 14:42:46.632: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0

x07

Ybor-1VG200gtway2#

MGCP PACKET Debug:

Ybor-1VG200gtway2#debug mgcp packets

Media Gateway Control Protocol packets debugging is on

Ybor-1VG200gtway2#

.Feb 11 15:58:01.157: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:01.157: NTFY 194663 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:58:01.161: MGCP Packet received from 10.71.40.24-

200 194663

Ybor-1VG200gtway2#

.Feb 11 15:58:16.157: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:16.157: NTFY 194664 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:58:16.161: MGCP Packet received from 10.71.40.24-

200 194664

Ybor-1VG200gtway2#

.Feb 11 15:58:20.045: MGCP Packet received from 10.71.40.24-

CRCX 30961 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

C: D000000002002433000000008000000d

L: p:20, a:PCMU, s:off

M: recvonly

.Feb 11 15:58:20.073: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:20.073: 200 30961 OK

I: 95F

v=0

c=IN IP4 10.71.40.7

m=audio 17568 RTP/AVP 0

<---

.Feb 11 15:58:20.085: MGCP Packet received from 10.71.40.24-

RQNT 30962 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: d

R: D/[0-9ABCD*#]

S: G/rt

Q: process,loop

.Feb 11 15:58:20.097: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:20.097: 200 30962 OK

<---

Ybor-1VG200gtway2#

.Feb 11 15:58:31.157: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:31.157: NTFY 194665 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:58:31.161: MGCP Packet received from 10.71.40.24-

200 194665

.Feb 11 15:58:32.157: MGCP Packet received from 10.71.40.24-

MDCX 30965 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

C: D000000002002433000000008000000d

I: 95F

X: d

L: p:20, a:PCMU, s:off

M: sendrecv

R: D/[0-9ABCD*#]

S:

Q: process,loop

v=0

o=- 2399 0 IN EPN S1/DS1-0/13@Ybor-1VG200gtway2.tec.net

s=Cisco SDP 0

t=0 0

c=IN IP4 10.71.40.5

m=audio 19400 RTP/AVP 0

.Feb 11 15:58:32.173: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:32.173: 200 30965 OK

<---

.Feb 11 15:58:32.701: MGCP Packet received from 10.71.40.24-

RQNT 30966 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: d

R: D/[0-9ABCD*#]

S:

Q: process,loop

Ybor-1VG200gtway2#

.Feb 11 15:58:32.709: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:32.709: 200 30966 OK

<---

Ybor-1VG200gtway2#

.Feb 11 15:58:33.753: MGCP Packet received from 10.71.40.24-

MDCX 30967 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

C: D000000002002433000000008000000d

I: 95F

X: d

M: recvonly

R: D/[0-9ABCD*#]

Q: process,loop

.Feb 11 15:58:33.765: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:33.765: 200 30967 OK

<---

.Feb 11 15:58:33.805: MGCP Packet received from 10.71.40.24-

DLCX 30969 S1/DS1-0/13@Ybor-1VG200gtway2.tec.net MGCP 0.1

C: D000000002002433000000008000000d

I: 95F

X: d

S:

.Feb 11 15:58:33.833: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:33.833: 250 30969 OK

P: PS=80, OS=12800, PR=79, OR=12640, PL=0, JI=520, LA=0

<---

Ybor-1VG200gtway2#

.Feb 11 15:58:45.698: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:58:45.698: NTFY 194666 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:58:45.702: MGCP Packet received from 10.71.40.24-

200 194666

Ybor-1VG200gtway2#

.Feb 11 15:59:00.698: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:59:00.698: NTFY 194667 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:59:00.702: MGCP Packet received from 10.71.40.24-

200 194667

Ybor-1VG200gtway2#

.Feb 11 15:59:15.697: send_mgcp_msg, MGCP Packet sent to 10.71.40.24 --->

.Feb 11 15:59:15.697: NTFY 194668 *@Ybor-1VG200gtway2.tec.net MGCP 0.1

X: 0

O:

<---

.Feb 11 15:59:15.701: MGCP Packet received from 10.71.40.24-

200 194668

Ybor-1VG200gtway2#

New Member

Re: NOT Receiving name Display of IP extension when PBX phone ca

You are expecting "Ringing Line Presentation" instead of the "Connected on Line Presentation" behaviour. It is being reviewed as a possible future capability of Q.Sig on Call Manager 3.3.X.

You may want to review page 16 of 16.

http://www.cisco.com/application/pdf/en/us/guest/products/ps702/c1237/ccmigration_09186a00800e04ac.pdf

I had a better document with a table that described your issue, and murphy's law, I can't seem to find it. When I do I will send it you.

109
Views
0
Helpful
5
Replies
CreatePlease to create content