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

Call id in use

Hi all,

This is a wierd error message that I am getting when connecting the call. Not all the calls but many of the calls are disconnecting with this error message. I could not understand the reason behind this nor could I understand the error.

Here is the output of debug isdn q931.

Dec 2 13:30:14: ISDN Se0:15: TX -> SETUP pd = 8 callref = 0x14C4

Dec 2 13:30:14: Sending Complete

Dec 2 13:30:14: Bearer Capability i = 0x8090A3

Dec 2 13:30:14: Channel ID i = 0xA9839F

Dec 2 13:30:14: Progress Ind i = 0x8183 - Origination address is non-IS

DN

Dec 2 13:30:14: Display i = 'cisco'

Dec 2 13:30:14: Calling Party Number i = 0x00, 0x80, '1111', Plan:Unkno

wn, Type:Unknown

Dec 2 13:30:14: Called Party Number i = 0x81, '0091407759160', Plan:ISD

N, Type:Unknown

Dec 2 13:30:14: ISDN Se0:15: RX <- CALL_PROC pd = 8 callref = 0x94C4

Dec 2 13:30:14: Channel ID i = 0xA9839F

Dec 2 13:30:15: ISDN Se0:15: RX <- ALERTING pd = 8 callref = 0x94C4

Dec 2 13:30:15: Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may

have in-band info

Dec 2 13:30:24: ISDN Se0:15: RX <- CONNECT pd = 8 callref = 0x94C4

Dec 2 13:30:24: Channel ID i = 0xA9839F

Dec 2 13:30:24.572: %ISDN-6-CONNECT: Interface Serial0:30 is now connected to 0

091407759160

Dec 2 13:30:24: ISDN Se0:15: TX -> CONNECT_ACK pd = 8 callref = 0x14C4

Dec 2 13:30:30.573: %ISDN-6-CONNECT: Interface Serial0:30 is now connected to 0

091407759160

Dec 2 13:31:30.594: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId D

8F8EC35 EBEB1810 8BC40010 DC2FB16E, SetupTime 13:30:14.934 GMT Mon Dec 2 2002, P

eerAddress 0091407759160, PeerSubAddress , DisconnectCause 54 , DisconnectText

call id in use, ConnectTime 13:30:24.584 GMT Mon Dec 2 2002, DisconnectTime 13:3

1:30.594 GMT Mon Dec 2 2002, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitP

ackets 924, TransmitBytes 21703, ReceivePackets 1091, ReceiveBytes 25218

Dec 2 13:31:30.594: %ISDN-6-DISCONNECT: Interface Serial0:30 disconnected from

0091407759160 , call lasted 66 seconds

Dec 2 13:31:30: ISDN Se0:15: TX -> DISCONNECT pd = 8 callref = 0x14C4

Dec 2 13:31:30: Cause i = 0x80D4 - Call ID in use

Dec 2 13:31:30.750: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId D

8F8EC35 EBEB1810 8BC40010 DC2FB16E, SetupTime 13:30:14.890 GMT Mon Dec 2 2002, P

eerAddress , PeerSubAddress , DisconnectCause 54 , DisconnectText call id in us

e, ConnectTime 13:30:24.580 GMT Mon Dec 2 2002, DisconnectTime 13:31:30.740 GMT

Mon Dec 2 2002, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 1091,

TransmitBytes 25218, ReceivePackets 924, ReceiveBytes 21703

Dec 2 13:31:30: ISDN Se0:15: RX <- RELEASE pd = 8 callref = 0x94C4

Dec 2 13:31:30: ISDN Se0:15: TX -> RELEASE_COMP pd = 8 callref = 0x14C4

Please help me

Kiran

2 REPLIES
Silver

Re: Call id in use

The disconnect is most likely coming from the IP network. Can you run traces on the originating gateway and see what happens.

New Member

Re: Call id in use

The scenario is like this...

The calls from external clients are coming to a softswitch, and softswitch sends the calls to the cisco AS5300 from where they get terminated via a dedicated channel. Where do you want me to run traces on now.

Please reply.

Thank you.

99
Views
0
Helpful
2
Replies