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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Callback - incompatible destination ?

Hi !

I try to configure an ISDN callback - The call is initiated and disconnected - Callback is started, to the number I am dialing from.

But gets disconnected because of the error message "incompatible destination" !

I am using a XIRCOM ISDN ISDN CARD dialing to a 3660 Access Router which is connected to a PBX.

I am calling from another port connected to the same PBX .

8227 is calling to 3333 ! (now - just for testing)

DEBUG:

*Mar 1 02:25:48: ISDN Se1/0:15: RX <- SETUP pd = 8 callref = 0x007E

*Mar 1 02:25:48: Sending Complete

*Mar 1 02:25:48: Bearer Capability i = 0x8890

*Mar 1 02:25:48: Channel ID i = 0xA98384

*Mar 1 02:25:48: Facility i = 0x91A10A020282A002011E0A0101

*Mar 1 02:25:48: - ETSI Supplementary Service, Invoke, Unsupported operation

*Mar 1 02:25:48: Calling Party Number i = 0x00, 0x83, '8227', Plan:Unknown, Type:Unknown

*Mar 1 02:25:48: %LINK-3-UPDOWN: Interface Serial1/0:3, changed state to up

*Mar 1 02:25:48: ISDN Se1/0:15: TX -> CALL_PROC pd = 8 callref = 0x807E

*Mar 1 02:25:48: Channel ID i = 0xA98384

*Mar 1 02:25:48: ISDN Se1/0:15: TX -> CONNECT pd = 8 callref = 0x807E

*Mar 1 02:25:48: Channel ID i = 0xA98384

*Mar 1 02:25:48: ISDN Se1/0:15: RX <- CONNECT_ACK pd = 8 callref = 0x007E

*Mar 1 02:25:48: ISDN Se1/0:15: CALL_PROGRESS: CALL_CONNECTED call id 0xC, bchan 3, dsl 0

*Mar 1 02:25:48: ISDN Se1/0:15: RX <- SETUP pd = 8 callref = 0x007F

*Mar 1 02:25:48: Sending Complete

*Mar 1 02:25:48: Bearer Capability i = 0x8890

*Mar 1 02:25:48: Channel ID i = 0xA98385

*Mar 1 02:25:48: Facility i = 0x91A10A0202830002011E0A0101

*Mar 1 02:25:48: - ETSI Supplementary Service, Invoke, Unsupported operation

*Mar 1 02:25:48: Calling Party Number i = 0x00, 0x83, '8227', Plan:Unknown, Type:Unknown

*Mar 1 02:25:48: %LINK-3-UPDOWN: Interface Serial1/0:4, changed state to up

*Mar 1 02:25:48: %ISDN-6-CONNECT: Interface Serial1/0:3 is now connected to 8227

*Mar 1 02:25:48: ISDN Se1/0:15: TX -> CALL_PROC pd = 8 callref = 0x807F

*Mar 1 02:25:48: Channel ID i = 0xA98385

*Mar 1 02:25:48: ISDN Se1/0:15: TX -> CONNECT pd = 8 callref = 0x807F

*Mar 1 02:25:48: Channel ID i = 0xA98385

*Mar 1 02:25:48: ISDN Se1/0:15: RX <- CONNECT_ACK pd = 8 callref = 0x007F

*Mar 1 02:25:48: ISDN Se1/0:15: CALL_PROGRESS: CALL_CONNECTED call id 0xD, bchan 4, dsl 0

*Mar 1 02:25:48: AAA: parse name=Serial1/0:3 idb type=13 tty=-1

*Mar 1 02:25:48: AAA: name=Serial1/0:3 flags=0x55 type=1 shelf=0 slot=1 adapter=0 port=0 channel=3

*Mar 1 02:25:48: AAA: parse name=<no string> idb type=-1 tty=-1

*Mar 1 02:25:48: AAA/MEMORY: create_user (0x61BAE36C) user='test' ruser='NULL' ds0=16777219 port='Serial1/0:3' rem_addr='8227' authen_type=CHAP service=PPP priv=1 initial_task_id='0'

*Mar 1 02:25:48: AAA/AUTHEN/START (453232446): port='Serial1/0:3' list='' action=LOGIN service=PPP

*Mar 1 02:25:48: AAA/AUTHEN/START (453232446): using "default" list

*Mar 1 02:25:48: AAA/AUTHEN/START (453232446): Method=LOCAL

*Mar 1 02:25:48: AAA/AUTHEN (453232446): status = PASS

*Mar 1 02:25:49: AAA/MEMORY: dup_user (0x61BAE50C) user='test' ruser='NULL' port='Serial1/0:3' rem_addr='8227' authen_type=CHAP service=PPP priv=1 source='create callback'

*Mar 1 02:25:49: ISDN Se1/0:15: RX <- DISCONNECT pd = 8 callref = 0x007E

*Mar 1 02:25:49: Cause i = 0x8090 - Normal call clearing

*Mar 1 02:25:49: %ISDN-6-CONNECT: Interface Serial1/0:4 is now connected to 8227

*Mar 1 02:25:49: %ISDN-6-DISCONNECT: Interface Serial1/0:3 disconnected from 8227 test, call lasted 1 seconds

*Mar 1 02:25:49: %LINK-3-UPDOWN: Interface Serial1/0:3, changed state to down

*Mar 1 02:25:49: AAA/MEMORY: free_user (0x61BAE36C) user='test' ruser='NULL' port='Serial1/0:3' rem_addr='8227' authen_type=CHAP service=PPP priv=1

*Mar 1 02:25:49: ISDN Se1/0:15: TX -> RELEASE pd = 8 callref = 0x807E

*Mar 1 02:25:49: ISDN Se1/0:15: RX <- RELEASE_COMP pd = 8 callref = 0x007E

*Mar 1 02:25:49: Cause i = 0x8090 - Normal call clearing

*Mar 1 02:26:04: ISDN Se1/0:15: TX -> SETUP pd = 8 callref = 0x000B

*Mar 1 02:26:04: Bearer Capability i = 0x8890

*Mar 1 02:26:04: Channel ID i = 0xA9839F

*Mar 1 02:26:04: Called Party Number i = 0x81, '8227', Plan:ISDN, Type:Unknown

*Mar 1 02:26:04: ISDN Se1/0:15: RX <- SETUP_ACK pd = 8 callref = 0x800B

*Mar 1 02:26:04: Channel ID i = 0xA9839F

*Mar 1 02:26:04: ISDN Se1/0:15: RX <- DISCONNECT pd = 8 callref = 0x800B

*Mar 1 02:26:04: Cause i = 0x80D8 - Incompatible destination

*Mar 1 02:26:04: ISDN Se1/0:15: TX -> RELEASE pd = 8 callref = 0x000B

*Mar 1 02:26:04: ISDN Se1/0:15: RX <- RELEASE_COMP pd = 8 callref = 0x800B

*Mar 1 02:26:04: Cause i = 0x8090 - Normal call clearing

*Mar 1 02:26:04: AAA/MEMORY: free_user (0x61BAE50C) user='test' ruser='NULL' port='Serial1/0:3' rem_addr='8227' authen_type=CHAP service=PPP priv=1

*Mar 1 02:26:10: %ISDN-6-DISCONNECT: Interface Serial1/0:4 disconnected from 8227 , call lasted 22 seconds

*Mar 1 02:26:10: ISDN Se1/0:15: TX -> DISCONNECT pd = 8 callref = 0x807F

*Mar 1 02:26:10: Cause i = 0x8090 - Normal call clearing

*Mar 1 02:26:11: ISDN Se1/0:15: RX <- RELEASE pd = 8 callref = 0x007F

*Mar 1 02:26:11: Cause i = 0x8090 - Normal call clearing

Does anyone have an idea ?

thx

Hans

1 REPLY
Bronze

Re: Callback - incompatible destination ?

Incompatible destination usually means that an attempt was made to connect to non-ISDN equipment. For example, to an analog line. However, your incoming call has a bearer cap of 8890, as does out outbound call; this should be OK then. You might confirm if you see the same message when you try to initiate a call (no callback) from the cisco to the XIRCOM. It may also be useful to verify if the message is coming from the XIRCOM or the PBX, but I would think that you'll need to verify either of their configs first. Worst case, you might try the "isdn map" command under the cisco interface to see if this serves as a workaround, although I don't think that it will make a difference.

210
Views
0
Helpful
1
Replies