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

PBX Caller-ID issues

I have a T1-PRI tie line between the PBX(Avaya G3) and my Call Manager 5.1 w/2811 voice gateway. The issue is getting the caller-id to work on calls coming from the Avaya. The company that handles the Avaya says they are sending the Caller-Id but all I get is the extension the user is calling from. Running a debug here it the output I get.

*Jun 15 14:24:17.765: ISDN Se0/2/0:23 Q931: TX -> RELEASE pd = 8 callref = 0xE395

*Jun 15 14:24:17.789: ISDN Se0/2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x6395

*Jun 15 14:24:20.917: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x642C

Bearer Capability i = 0x9090A2

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98386

Exclusive, Channel 6

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0xA1, '8353'

Plan:ISDN, Type:National

Called Party Number i = 0x81, '8460'

Plan:ISDN, Type:Unknown

Locking Shift to Codeset 6

Codeset 6 IE 0x55 i = 0x010002050500, '85', 0x00000310, 'H', 0xA600000200000000000000000000000000

Codeset 6 IE 0x55 i = 0x0A0202050500, '85', 0x00000310, 'H', 0xA600000F00, 'Server Room Dow'

*Jun 15 14:24:20.933: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0xE42C

Channel ID i = 0xA98386

Exclusive, Channel 6

*Jun 15 14:24:20.933: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8 callref = 0xE42C

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

*Jun 15 14:24:23.597: ISDN Se0/2/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x642C

Cause i = 0x8190 - Normal call clearing

*Jun 15 14:24:23.609: ISDN Se0/2/0:23 Q931: TX -> RELEASE pd = 8 callref = 0xE42C

*Jun 15 14:24:23.641: ISDN Se0/2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x642C

If any one has any ideas they would be helpful.

7 REPLIES
Gold

Re: PBX Caller-ID issues

I believe this is the issue with the Codeset being used to send Caller ID. Can you try to have them send it using Codeset 0. CallManager does not support Codeset 6.

I believe to for the display name to work on Avaya the following will have to be done. Go to the trunk-group configuration and change the parameter "Codeset to send display" from 6 to 0.

Hope this works.

New Member

Re: PBX Caller-ID issues

Hi,

I have a similar problem with Avaya /Cisco call. Did the change of "codeset to Send Display: 0" resolved the problem?.

Did you have to change other parameters in the Avaya o in CISCO gateway?

Thanks in advance

Re: PBX Caller-ID issues

Are you using QSIG/MGCP/T1 ? I have several customers working in this format. Without QSIG you won't get supplementary features like Calling Party Name. There is a PBX integration guide;

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/410364av.pdf

New Member

Re: PBX Caller-ID issues

I am using QSIG/EI/H.323 with a 2851 gateway (version 12,3(14T6) and a call manager express 3.2 in a router 3745. Calls from Cisco to Avaya are o.k but calls from Avaya to Cisco can't see caller name.

Next debug isdn q931

*Oct 20 10:44:49: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref = 0x1B85

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18386

Preferred, Channel 6

Facility i = 0x9FAA068001008201008B0100A1100202967306072B0C0287780104040100

Facility i = 0x9FAA068001008201008B0100A11802029674020100800F4962617272612C2047696C62657274

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0xA1, '7022'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '7266'

Plan:ISDN, Type:National

*Oct 20 10:44:49: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9B85

Channel ID i = 0xA98386

Exclusive, Channel 6

*Oct 20 10:44:50: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8 callref = 0x9B85

*Oct 20 10:44:55: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8 callref = 0x9B85

*Oct 20 10:44:55: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x1B85

*Oct 20 10:45:05: ISDN Se0/0/1:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x9B85

Cause i = 0x8090 - Normal call clearing

*Oct 20 10:45:05: ISDN Se0/0/1:15 Q931: RX <- RELEASE pd = 8 callref = 0x1B85

*Oct 20 10:45:05: ISDN Se0/0/1:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x9B85

Thanks

Carlos

Re: PBX Caller-ID issues

Hi Carlos,

You may want to try this command:

Serial0/0:23

isdn supp-service name calling

New Member

Re: PBX Caller-ID issues

You need QSIG setup on your PBX trunk between your callmanager.

New Member

Re: PBX Caller-ID issues

You should use the MGCP between Callmanager5.1 and W/2811. Because H.323 can't deliver the call-id/calling name. Also QSIG should be configured between the 2811 and AVAYA PBX on the T1-PRI line.

Last week I encounted the same issue as yours. But my PBX is SIEMENS, and i resolved it using the MGCP/QSIG.

737
Views
0
Helpful
7
Replies
CreatePlease to create content