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

No Called Party ID on CME connected to ISDN2e

Greetings, i have a UC520 connected to an ISDN2e connection and dont appear to be getting caller id presented for inbound calls.

I have enabled the following debug and cant see the calling number being presented by the carrier.

"debug voice dialpeer inout"

Snippet:

002670: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=509, Voice-Interface=0x865BD57C,

Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

002671: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=10

002672: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=509, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_FAX

002673: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

002674: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Calling Number=, Called Number=509, Peer Info Type=DIALPEER_INFO_SPEECH

002675: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=509

002676: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

002677: Aug 28 08:58:38.988: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=20027

002678: Aug 28 08:58:38.992: //-1/CFD8C44B8039/DPM/dpMatchPeersCore:

Calling Number=, Called Number=509, Peer Info Type=DIALPEER_INFO_SPEECH

002679: Aug 28 08:58:38.992: //-1/CFD8C44B8039/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=509

002680: Aug 28 08:58:38.992: //-1/CFD8C44B8039/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

002681: Aug 28 08:58:38.992: //-1/CFD8C44B8039/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

Can i ask if this is normal behavior for ISDN2e circuits?

Regards

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: No Called Party ID on CME connected to ISDN2e

It can be confirmed, no calling number is present, and you should complain to telco.

If their asnwer is "all Ok", show them the trace above.

5 REPLIES
Hall of Fame Super Gold

Re: No Called Party ID on CME connected to ISDN2e

Please take "debug isdn q931". Do not enable any othet debug.

Community Member

Re: No Called Party ID on CME connected to ISDN2e

This is a call from my mobile to extension 509. The call was disconnected before being answered.

I do have an incomming dial peer configured to strip the "642" from the beginning of the called number to match the internal extension number.

002847: Aug 28 10:00:00.728: ISDN BR0/2/0 Q931: RX <- SETUP pd = 8 callref = 0x01

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x8A

Exclusive, B2

Called Party Number i = 0x81, '642509'

Plan:ISDN, Type:Unknown

002848: Aug 28 10:00:00.740: ISDN BR0/2/0 Q931: TX -> CALL_PROC pd = 8 callref = 0x81

Channel ID i = 0x8A

Exclusive, B2

002849: Aug 28 10:00:00.764: ISDN BR0/2/0 Q931: TX -> ALERTING pd = 8 callref = 0x81

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

002851: Aug 28 10:00:05.152: ISDN BR0/2/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x4B

Cause i = 0x8090 - Normal call clearing

002852: Aug 28 10:00:05.308: ISDN BR0/2/0 Q931: RX <- RELEASE pd = 8 callref = 0xCB

002853: Aug 28 10:00:05.308: ISDN BR0/2/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x4B

002854: Aug 28 10:00:07.092: ISDN BR0/2/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x01

Cause i = 0x8090 - Normal call clearing

002855: Aug 28 10:00:07.096: ISDN BR0/2/0 Q931: TX -> RELEASE pd = 8 callref = 0x81

Cause i = 0x8090 - Normal call clearing

002856: Aug 28 10:00:07.148: ISDN BR0/2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x01

This is a call from my mobile to extension 509. The call was answered then i ended the call after 3 seconds.

002857: Aug 28 10:02:47.580: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x01

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Exclusive, B1

Called Party Number i = 0x81, '642509'

Plan:ISDN, Type:Unknown

002858: Aug 28 10:02:47.596: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref = 0x81

Channel ID i = 0x89

Exclusive, B1

002859: Aug 28 10:02:47.620: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8 callref = 0x81

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

fh-nwk-uc520#

002860: Aug 28 10:02:49.920: ISDN BR0/1/0 Q931: TX -> CONNECT pd = 8 callref = 0x81

Channel ID i = 0x89

Exclusive, B1

002861: Aug 28 10:02:49.980: ISDN BR0/1/0 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x01

fh-nwk-uc520#

002862: Aug 28 10:02:49.980: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to N/A N/A

fh-nwk-uc520#

002863: Aug 28 10:02:53.532: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x01

Cause i = 0x8090 - Normal call clearing

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

002864: Aug 28 10:02:53.532: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to N/A N/A

002865: Aug 28 10:02:53.532: %ISDN-6-CONNECT: Interface BRI0/1/1:1 is now connected to N/A N/A

002866: Aug 28 10:02:53.532: %ISDN-6-CONNECT: Interface BRI0/2/0:1 is now connected to N/A N/A

002867: Aug 28 10:02:53.532: %ISDN-6-CONNECT: Interface BRI0/2/1:1 is now connected to N/A N/A

002868: Aug 28 10:02:53.532: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1 disconnected from unknown , call lasted 3 seconds

fh-nwk-uc520#

002869: Aug 28 10:02:53.560: ISDN BR0/1/0 Q931: TX -> RELEASE pd = 8 callref = 0x81

002870: Aug 28 10:02:53.604: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x01

Regards

Hall of Fame Super Gold

Re: No Called Party ID on CME connected to ISDN2e

It can be confirmed, no calling number is present, and you should complain to telco.

If their asnwer is "all Ok", show them the trace above.

Community Member

Re: No Called Party ID on CME connected to ISDN2e

Thank you for your time, glad im not going mad!

Regards

Hall of Fame Super Gold

Re: No Called Party ID on CME connected to ISDN2e

You're welcome, please remember to rate useful posts with the scrollbox below.

219
Views
0
Helpful
5
Replies
CreatePlease to create content