cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

AMA-CUCM Troubleshooting: Best Practices for Reading Trace Files

1203
Views
0
Helpful
1
Replies
Cisco Employee

CUCM 8.6 QSIG to Nortel Option 81 No Caller ID

Working on an H.323 QSIG trunk to Nortel Option 81. Everything is working except caller ID on local calls. Cisco phones making local (7digit) calls only display the lead trunk (BTN) number for caller ID. Long distance calls display the correct caller ID. The Nortel has a separate local and LD trunks. Nortel phones have correct caller id displayed for both local and LD calls.

Topology/Call Flow

Cisco Phone -> CUCM -> 2911GW -> Nortel ->PSTN

Gateway is a 2911 running 15.0(1)M5

It looks like we are sedning the same information to the Nortel on both callS AND the Q931 information on both calls looks to be correct.

Local Call (Not Working)

*Sep 19 20:24:26.865: ISDN Se0/0/0:23 Q931: Sending SETUP  callref = 0x5429 callID = 0xD3B2 switch = primary-qsig interface = Network

*Sep 19 20:24:26.865: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x5429

        Sending Complete

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98384

                Exclusive, Channel 4

        Calling Party Number i = 0x0081, '4065565382'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '95998310'

                Plan:Unknown, Type:Unknown

*Sep 19 20:24:26.941: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xD429

        Channel ID i = 0xA98384

                Exclusive, Channel 4

*Sep 19 20:24:28.077: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8  callref = 0xD429

Long Distance Call (Working)

*Sep 19 20:26:31.213: ISDN Se0/0/0:23 Q931: Sending SETUP  callref = 0x542A callID = 0xD3B3 switch = primary-qsig interface = Network

*Sep 19 20:26:31.213: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x542A

        Sending Complete

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98383

                Exclusive, Channel 3

        Calling Party Number i = 0x0081, '4065565382'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '912088306374'

                Plan:Unknown, Type:Unknown

*Sep 19 20:26:31.293: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xD42A

        Channel ID i = 0xA98383

                Exclusive, Channel 3

*Sep 19 20:26:31.449: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8  callref = 0xD42A

        Cause i = 0x81E4 - Invalid information element contents

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

*Sep 19 20:26:35.313: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8  callref = 0xD42A

So it apprears to be something on the Nortel side??? What can I check on the Nortel to see how these two calls are recieved and routed to the locan and LD trunks.


1 REPLY 1
Highlighted

CUCM 8.6 QSIG to Nortel Option 81 No Caller ID

Have you had any luck solving this issue?  

I am having the exact same problem.  What I have found is that the local provider is saying that the number is not coming across in E.164 format which then appears to them as an unknown number so they just append either the main phone number to the caller ID or sometimes the phone number associated with billing contact.  The nortel works just fine in both senarios, but there seems to be something lost in translation between the Cisco and Nortel.   So far I haven't been able to find a setting to fix this.

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards