Sending Complete Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA9839F Exclusive, Channel 31 Calling Party Number i = 0x0081, '2222' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '01064861110' Plan:Unknown, Type:Unknown *Jan 24 09:01:32.624: ISDN Se0/2/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8003 Cause i = 0x8286 - Channel unacceptable
Can you check with Telco as to why they think the channel is unacceptable to them? Ask them to check whether the channels on their side are active and not busied out. By default, the User side of the PRI starts allocating channels from 31 and goes to 1 as simultaneous calls come in.
I asked you to change the channel selection order now you see this issue even on channel 1.
Jan 24 09:01:32.624: ISDN Se0/2/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8003 Cause i = 0x8286 - Channel unacceptable
The call is constantly being released by your telco.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...