No Caller ID with Cisco CME

olivier.bedard · ‎01-31-2008

Hi,

We do not receive the CallerID on our system. We do receive the calling number, but not the calling name.

We opened a support ticket with the telco and they confirmed that they were sending the information down the pipe.

Here's the configuration of our interface:

interface Serial0/0/0:23

no ip address

encapsulation hdlc

isdn switch-type primary-5ess

isdn incoming-voice voice

isdn supp-service name calling

isdn bchan-number-order ascending

isdn outgoing ie facility

no cdp enable

We are running:

12.4(11)XJ4 / CME 4.1(0)

Here's an example debug log of an incoming call:

ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00D8

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 = 0x9F8B0100A1080201010201008400

Calling Party Number i = 0x2180, '5145551234'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '2505'

Plan:Unknown, Type:Unknown

ISDN Se0/0/0:23 SERROR: isdn_get_name_from_gtd: false ret

ISDN Se0/0/0:23 SERROR: process_pri_simple: NO name in GTD

ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x80D8

Channel ID i = 0xA98381

Exclusive, Channel 1

ISDN Se0/0/0:23 SERROR: isdn_get_name_from_gtd: false ret

ISDN Se0/0/0:23 SERROR: process_pri_simple: NO name in GTD

ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x80D8

ISDN Se0/0/0:23 SERROR: isdn_get_name_from_gtd: false ret

ISDN Se0/0/0:23 SERROR: process_pri_simple: NO name in GTD

ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x80D8

ISDN Se0/0/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x00D8

ISDN Se0/0/0:23 **ERROR**: call_progress: DEV_CONNECTED VOICE ERROR: Bearer capability not available(0x3A): b channel 0 call id 0x85

Thank you!

paolo bevilacqua · ‎01-31-2008

Hi,

in short the switch is telling you that the name is not available. Why, you should ask telco. Here's the relevant part of your trace decoded, in the unlikely event you meet some telco technician willing to discuss it.

Facility i = 0x9F8B0100A1080201010201008400

0x9f Service Discriminator: Network Extension

0x8b Component Type: Interpretation

0x01 Component Length

0x00 Discard Unrecognized Invoke Components

0xa1 Component Type: Invoke

0x08 Component Length

0x02 Invoke ID Tag: Universal Integer

0x01 Invoke ID Length

0x00 Invoke ID Value

0x02 Operation Tag: Universal Integer

0x01 Operation Length

0x00 Operation Value: Calling Name

0x84 Argument Tag: Context-Specific NameNotAvailable

0x00 Argument Length

The router comes to the same conclusion as you can read in clear text:

ISDN Se0/0/0:23 SERROR: process_pri_simple: NO name in GTD

I've shameless copied the decode from a source readily available on the web. Nonetheless, please rate this post if it helps you!

olivier.bedard · ‎02-01-2008

Thank you for the reply.

However, what if my telco is 100% certain they send the information ?

I've been told by the technician that the info was sent "through the standard facility, not through a q931 message".

Does that make senses to you ?

benwsegura · ‎01-31-2008

Here is an example of the output we recieved when we performed a debug isdn 931q command. The % signs represent the callers number and name displayed. I changed them for privacy.

To me, it looks like you are not getting the info from the carrier. You may want to check with them. CLID on a PRI is in the D channel, channel 24. Channels 1-23 are your B channels.

Oct 25 11:23:50.495: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x0037

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 = 0x9F8B0100A10F02010106072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA10F02010106072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 1

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Calling Party Number i = 0x2183, '3%%%%%%%%0'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '4500'

Plan:Unknown, Type:Unknown

Oct 25 11:23:50.519: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8037

Channel ID i = 0xA98381

Exclusive, Channel 1

Oct 25 11:23:50.527: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x8037

Oct 25 11:23:50.691: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x0037

Facility i = 0x9F8B0100A117020101020100800F47454E4E55534F204348524953544F

Protocol Profile = Networking Extensions

0xA117020101020100800F47454E4E55534F204348524953544F

Component = Invoke component

Invoke Id = 1

Operation = CallingName

Name presentation allowed

Name = G%%%%% CH%%%%

Oct 25 11:24:02.607: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x8037

Oct 25 11:24:02.631: ISDN Se0/0/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0037

Oct 25 11:24:02.635: ISDN Se0/0/0:23 **ERROR**: call_progress: DEV_CONNECTED VOICE ERROR: Bearer capability not available(0x3A): b channel 0 call id 0x4F

Oct 25 11:24:02.635: %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 3%%%%%%%%0 N/A

Oct 25 11:24:06.367: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x0037

Cause i = 0x8090 - Normal call clearing

Oct 25 11:24:06.371: %ISDN-6-DISCONNECT: Interface Serial0/0/0:0 disconnected from 3%%%%%%%%0 , call lasted 3 seconds

Oct 25 11:24:06.371: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x8037

Oct 25 11:24:06.391: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0037u all

paolo bevilacqua · ‎01-31-2008

Woops! Privacy violation above , any bytehead can still read the name in hex :)

benwsegura · ‎01-31-2008

Sorry about that. Which lines do I need to edit?

paolo bevilacqua · ‎02-01-2008

Too late for edit. Mine was only a jokeful remark !