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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Name Display not working with Lucent 5ESS and Call Manager 3.2

Our PSTN Connection goes to Sprint’s 5ESS Switch using the 6608 Module in the 6509 (NI2 ISDN Variant). Now, Calling Name is giving us some troubles in both directions. Calling Number does work.

CallManager sends the Calling Name to the PSTN using an optional IE the “display IE” (0x28). The Sprint 5ESS Sends the Calling Number, Called Number and Name Display using a Optional IE called the “Facility IE” (0x1C) with the information encoded in “ASN.1”.

Strange thing is that we can decode Caller ID in both directions (Number only) but no Name. Is there anyway to make call Manger send the name display using the Facility IE? Or is there a better ISDN Variant to use when connecting to the Lucent 5ESS? I have included the “SETUP” messages below for your reference captured with Sniffer T1 Module:

5ESS To the CallManager:

DLC: ----- DLC Header -----

DLC:

DLC:

DLC: Frame 15 arrived at 14:07:48.6166; frame size is 67 (43 hex) bytes.

DLC: Destination = DTE.D

DLC: Source = DCE.D

DLC:

LAPD: ----- Link Access Procedure D (LAPD) -----

LAPD:

LAPD: Address byte #1 = 02

LAPD: 0000 00.. = SAPI = 0

LAPD: .... ..1. = Command/Response bit

LAPD: .... ...0 = EA

LAPD: Address byte #2 = 01

LAPD: 0000 000. = TEI = 0

LAPD: .... ...1 = EA

LAPD: Control byte #1 = 3E

LAPD: 0011 111. = N(S) = 31

LAPD: .... ...0 = I (Information transfer)

LAPD: Control byte #2 = 3A

LAPD: 0011 101. = N(R) = 29

LAPD: .... ...0 = Poll bit

LAPD:

ISDN: ----- ISDN Call Control (Generic Q.931 Primary Rate) -----

ISDN:

ISDN: Protocol discriminator = 08 (Q.931 user-network call control messages)

ISDN: Length of call reference = 2 bytes

ISDN: Call reference field = 00E7

ISDN: 0... .... .... .... = Message from call reference originator

ISDN: .000 0000 1110 0111 = Call reference value = 00E7

ISDN: Message type = 05 (Setup)

ISDN:

ISDN: Info element id = 04 (Bearer capability)

ISDN: Length of information element = 3 byte(s)

ISDN: Octet 3 value = 80

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Coding standard (CCITT)

ISDN: ...0 0000 = Information transfer capability (Speech)

ISDN: Octet 4 value = 90

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Transfer mode (Circuit mode)

ISDN: ...1 0000 = Information transfer rate (64 kbit/s)

ISDN: Octet 5 value = A2

ISDN: 1... .... = Extension bit

ISDN: .01. .... = Layer 1 identification

ISDN: ...0 0010 = Layer 1 protocol (G.711 u-law)

ISDN:

ISDN: Info element id = 18 (Channel identification)

ISDN: Length of information element = 3 byte(s)

ISDN: Octet 3 value = A9

ISDN: 1... .... = Extension bit

ISDN: .0.. .... = Interface implicitly identified

ISDN: ..1. .... = Primary interface

ISDN: .... 1... = Only the indicated channel is acceptable

ISDN: .... .0.. = Not the D-channel

ISDN: .... ..01 = Information channel selection (As indicated in following octets)

ISDN: Octet 3.2 value = 83

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Coding standard (CCITT)

ISDN: ...0 .... = Channel indicated by number

ISDN: .... 0011 = Channel/map element type (B-channel units)

ISDN: Channel number = 23

ISDN:

ISDN: Info element id = 1C (Facility)

ISDN: Length of information element = 21 byte(s)

ISDN: Octet 3 value = 9F

ISDN: 1... .... = Extension bit

ISDN: ...1 1111 = Protocol profile (?)

ISDN:

ASN.1: ----- Abstract Syntax Notation One -----

ASN.1:

ASN.1: 1.1 Context-Specific Primitive [11], Length=1, Data = "<00>"

ASN.1: 1.2 Context-Specific Constructed [1], Length=15

ASN.1: 2.1 INTEGER, Length=1, Value = "1"

ASN.1: 2.2 OBJECT IDENTIFIER, Length=7, Value = "{1.2.840.10005.0.4}"

ASN.1: 2.3 ENUMERATED, Length=1, Value = "0"

ASN.1: 1.3 Universal Type 30, Length=2, Value = "<8283> (8283)"

ASN.1: 1.4 Application Constructed [12], Length=12

ASN.1: 2.1 Constructed BOOLEAN, Length=3420470

ASN.1: 3.1 Constructed GeneralizedTime, Length=48

ASN.1: 4.1 Constructed NumericString, Length=56

ASN.1: 5.1 SEQUENCE [of], Length=53

ASN.1: 6.1 Constructed VideotexString, Length=112

ASN.1: 7.1 NULL, Length=2147483647, Value = ""

ASN.1:

ADDR HEX ASCII

CALL MANAGER TO 5ESS:

DLC: ----- DLC Header -----

DLC:

DLC:

DLC: Frame 108 arrived at 14:05:19.2893; frame size is 62 (3E hex) bytes.

DLC: Destination = DCE.D

DLC: Source = DTE.D

DLC:

LAPD: ----- Link Access Procedure D (LAPD) -----

LAPD:

LAPD: Address byte #1 = 00

LAPD: 0000 00.. = SAPI = 0

LAPD: .... ..0. = Command/Response bit

LAPD: .... ...0 = EA

LAPD: Address byte #2 = 01

LAPD: 0000 000. = TEI = 0

LAPD: .... ...1 = EA

LAPD: Control byte #1 = 00

LAPD: 0000 000. = N(S) = 0

LAPD: .... ...0 = I (Information transfer)

LAPD: Control byte #2 = 02

LAPD: 0000 001. = N(R) = 1

LAPD: .... ...0 = Poll bit

LAPD:

ISDN: ----- ISDN Call Control (Generic Q.931 Primary Rate) -----

ISDN:

ISDN: Protocol discriminator = 08 (Q.931 user-network call control messages)

ISDN: Length of call reference = 2 bytes

ISDN: Call reference field = 001D

ISDN: 0... .... .... .... = Message from call reference originator

ISDN: .000 0000 0001 1101 = Call reference value = 001D

ISDN: Message type = 05 (Setup)

ISDN:

ISDN: Info element id = 04 (Bearer capability)

ISDN: Length of information element = 3 byte(s)

ISDN: Octet 3 value = 80

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Coding standard (CCITT)

ISDN: ...0 0000 = Information transfer capability (Speech)

ISDN: Octet 4 value = 90

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Transfer mode (Circuit mode)

ISDN: ...1 0000 = Information transfer rate (64 kbit/s)

ISDN: Octet 5 value = A2

ISDN: 1... .... = Extension bit

ISDN: .01. .... = Layer 1 identification

ISDN: ...0 0010 = Layer 1 protocol (G.711 u-law)

ISDN:

ISDN: Info element id = 18 (Channel identification)

ISDN: Length of information element = 3 byte(s)

ISDN: Octet 3 value = A9

ISDN: 1... .... = Extension bit

ISDN: .0.. .... = Interface implicitly identified

ISDN: ..1. .... = Primary interface

ISDN: .... 1... = Only the indicated channel is acceptable

ISDN: .... .0.. = Not the D-channel

ISDN: .... ..01 = Information channel selection (As indicated in following octets)

ISDN: Octet 3.2 value = 83

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Coding standard (CCITT)

ISDN: ...0 .... = Channel indicated by number

ISDN: .... 0011 = Channel/map element type (B-channel units)

ISDN: Channel number = 23

ISDN:

ISDN: Info element id = 28 (Display)

ISDN: Length of information element = 14 byte(s)

ISDN: Information = "Person X"

ISDN:

ISDN: Info element id = 6C (Calling party number)

ISDN: Length of information element = 12 byte(s)

ISDN: Octet 3 value = 00

ISDN: 0... .... = Extension bit

ISDN: .000 .... = Type of number (Unknown)

ISDN: .... 0000 = Numbering plan (Unknown)

ISDN: Octet 3a value = 80

ISDN: 1... .... = Extension bit

ISDN: .00. .... = Presentation indicator (Presentation allowed)

ISDN: .... ..00 = Screening indicator (User-provided, not screened)

ISDN: Number digits = "XXXYYY7409"

ISDN:

ISDN: Info element id = 70 (Called party number)

ISDN: Length of information element = 11 byte(s)

ISDN: Octet 3 value = 80

ISDN: 1... .... = Extension bit

ISDN: .000 .... = Type of number (Unknown)

ISDN: .... 0000 = Numbering plan (Unknown)

ISDN: Number digits = "XXXYYY8055"

ISDN:

I have modified the names and calling numbers to protect the customer's identity. Any help in trying to get this work would be appreciated.

Thanks.....Darryl

2 REPLIES
Cisco Employee

Re: Name Display not working with Lucent 5ESS and Call Manager 3

calling party name is only supported on Call manager using the standard Q.931 display IE 0x28, name as facility message is not supported. If the carrier cannot supply name in standard display IE then this functionality will not be available to you.

New Member

Re: Name Display not working with Lucent 5ESS and Call Manager 3

Hello,

This is what I thought. Is it safe to say that Sprint is not following the Q.931 / NI2 Speciifcations or is how they have implemented it their interpretation and is OK? Does anyone know if the 5ESS cab be configured to use the display IE versus the Facility IE? I need to get this working for my customer. Is there another ISDN Variant that could be used (and certified by Cisco) with the Lucent 5ESS?

Thanks in advance...Darryl

450
Views
0
Helpful
2
Replies
CreatePlease login to create content