unavailable channel disconnect

Unanswered Question
Apr 2nd, 2008

Hi;

Changed out callmgrs from 4.x to 6.1 over weekend.

Remote site in London has a H323 gateway w/ partial E1 to PSTN. Nothing was changed in config but now out calls can not be made from one phone. Q931 debug shows call being setup but router disconnects it with a "unavailable channel" cause code.

Stanger thing is it is only happening from this one phone. the other phones work fine.

below is debug from attempted call from x307 and then good call from x305, both to same number over same E1 channel.

Any suggestions would be welcome:

005349: Apr 1 15:19:59.963 gmt: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8 callref = 0x03FC

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9838A

Exclusive, Channel 10

Calling Party Number i = 0x0081, '2075622307'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '08701662801'

Plan:Unknown, Type:Unknown

005350: Apr 1 15:20:00.183 gmt: ISDN Se0/1/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x83FC

Channel ID i = 0xA9838A

Exclusive, Channel 10

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

005351: Apr 1 15:20:00.643 gmt: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x03FC

Cause i = 0x80AC - Requested circuit/channel not available

005352: Apr 1 15:20:00.783 gmt: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x83FC

005353: Apr 1 15:20:00.787 gmt: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x03FC

JCF-LN-2821-1#

JCF-LN-2821-1#

JCF-LN-2821-1#

005354: Apr 1 15:21:12.840 gmt: ISDN Se0/1/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 2075622305

005355: Apr 1 15:21:12.840 gmt: ISDN Se0/1/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 08701662801

005356: Apr 1 15:21:12.840 gmt: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8 callref = 0x03FD

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9838A

Exclusive, Channel 10

Calling Party Number i = 0x0081, '2075622305'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '08701662801'

Plan:Unknown, Type:Unknown

005357: Apr 1 15:21:13.052 gmt: ISDN Se0/1/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x83FD

Channel ID i = 0xA9838A

Exclusive, Channel 10

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

005358: Apr 1 15:21:16.544 gmt: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x83FD

005359: Apr 1 15:21:17.504 gmt: ISDN Se0/1/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x83FD

005360: Apr 1 15:21:19.312 gmt: ISDN Se0/1/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x83FD

005361: Apr 1 15:21:19.316 gmt: %ISDN-6-CONNECT: Interface Serial0/1/0:9 is now connected to 08701662801 N/A

005362: Apr 1 15:21:19.316 gmt: ISDN Se0/1/0:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x03FD

Thanks

Rob

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Paolo Bevilacqua Wed, 04/02/2008 - 16:15

Hi, reading better, should not be an IOS issue but CM one. That could be proved by debug cch323 showing something going on after setup ack.

Unfortunately I'm not good at CM to suggest anything to check in there. Hope others can help.

kthorngr Wed, 04/02/2008 - 16:40

Is the problem phone a newer generation phone and the working and older generation phone?

If so you may be running into the problem described in CSCsi61965. If this is the issue then modify the Enterprise Parameter 'Advertise G.722 Codec' by setting it to disable. Reset the problem phone and see if the call works. ou will then need to follow the steps in the defect and reset all of the newer phones.

Kevin

rvincent Thu, 04/03/2008 - 06:39

Kevin:

you may have something there....the non-working phone is a 7961, the others are 7960's.

I'll give it a try

thanks

Rob

rvincent Thu, 04/03/2008 - 15:29

Kevin:

It worked!

changed the g722 setting from default to disable on the non-working device

funny that the bug description does not talk about a straight call but it did the trick

thanks

Rob

Actions

This Discussion