Calling Party Name missing on VG224 FXS port

roitsupport · ‎03-08-2009

Hello,

I am troubleshooting an issue with the calling party name missing from analog phones caller-id causing the phone to display unknown name or out of area for the calling party information.

The setup is as follows: PSTN PRI---3825---(MGCP)---CUCM---(SCCP)---VG224---FXS port. CUCM version 6.1.3

Telco is providing the calling party number in the SETUP message which is being forwarded to the VG224 analog port fine. However, the issue is the telco is not providing the calling party name until the FACILITY message. Once FACILITY arrives, CUCM already routed the call to the analog phone with missing calling party name information which causes the unknown name information to be displayed by the VG224 connected phone. TAC is suggesting converting the MGCP gateway to H.323 gateway but this will add additional management and monitoring issues.

Telco says that they cannot add the calling party name to the SETUP message.

Has anyone else ran into this problem and if so, is there any way to fix this issue without doing a conversion on the gateway?

sh run of the PRI and debug output below:

interface Serial0/0/0:23

no ip address

encapsulation hdlc

isdn switch-type primary-ni

isdn incoming-voice voice

isdn bind-l3 ccm-manager

no cdp enable

end

003970: *Mar 5 22:59:20.904: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8186

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

003971: *Mar 5 22:59:21.052: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8186

003972: *Mar 5 22:59:21.060: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0186

003973: *Mar 5 22:59:30.312: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x1879

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Facility i = 0x9F8B0100A10F02013E06072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA10F02013E06072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 62

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Calling Party Number i = 0x2180, '408XXXXXXX'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '623XXXXXXX'

Plan:ISDN, Type:National

003974: *Mar 5 22:59:30.332: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x9879

Channel ID i = 0xA98381

Exclusive, Channel 1

003975: *Mar 5 22:59:30.332: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x9879

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

003976: *Mar 5 22:59:30.856: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x1879

Facility i = 0x9F8B0100A11702013F020100800F434953434F2053595354454D532020

Protocol Profile = Networking Extensions

0xA11702013F020100800F434953434F2053595354454D532020

Component = Invoke component

Invoke Id = 63

Operation = CallingName

Name Presentation Allowed Extended

Name = CISCO SYSTEMS

003977: *Mar 5 22:59:33.168: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0184

Cause i = 0x8090 - Normal call clearing

003978: *Mar 5 22:59:33.204: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8184

003979: *Mar 5 22:59:33.216: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0184

Called party numbers do come across OK, I manually added the XXXXXXX to the numbers.

gogasca · ‎03-08-2009

Unfortunatly No, we discuss this with De time ago and problem is Call Info message once is recieved by the VG224 cannot be updated with new Call info message after ISDN Q931 Facility arrives.

Nicholas Matthews · ‎03-08-2009

The feature you're needing to use is documented here:

http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn2800xw.html#wp363697

I do not believe that MGCP has this capability. This is probably why TAC is suggesting a change to H323.

hth,

nick

roitsupport · ‎03-09-2009

It definitely does...next questions.

1) Is it possible for the Telco to send the calling party name in the SETUP message or is that something that the protocol doesn't support?

2) Do you think that having an MGCP gateway send the calling party name from the FACILITY message would be something that could be supported in a future release?

Nicholas Matthews · ‎03-09-2009

It is normally sent in the SETUP message. To do otherwise is abnormal, and which is why we have a new feature to support it in the facility message afterwards.

I don't currently know of any plans to implement that in MGCP. If you would like to have this changed, you can talk to your account team to have a feature request filed.

hth,

nick