I am receiving the following error message from an isdn q931 debug on an AS5300 while attempting to make an outbound call on an ISDN PRI that is configured for NFAS: Cause i = 0x82A2 - No circuit/channel available. However, I am able to make inbound calls with no problems on this circuit.
I have contacted the phone company, and they told me that the problem may be the number of digits (7 vs. 10) that I am sending them. This happens with local and long distance calls, and when dialing 7 digits or 10.
I have been working with the TAC and Verizon on this issue and have not been able to come up with a resolution. Any help would be greatly appreciated.
First you need to make sure that the T1/NFAS PRI's are plugged in and configured the right order..Means nfas_int 0 to 3 should be configured and plugged in as its configured on switch.
Number of digits shouldn't matter here. Both local and long distnace call should go through (i assume that the line is provisioned for outbound calls as well in telco switch) You can see that how many digits router is sending by "debug isdn q931".
Now try removing "isdn negotiate-bchan resend-setup" and see if that helps.
That may cause channel mismatch. Pl. visit following url for more on that
Is the unsuccessful outbound call analog or ISDN? Although I don't see a group-async interface configured but since you have 192 MICA modems installed in this access server so I am curious to know what (analog or ISDN) you are complaining about. Pls post "debug isdn q931" for an unsuccessful outbound call for further troubleshooting.
I appreciate everyone's input on this issue. I have been working with the phone company and have somewhat consolidated the issue. I know that the issue only occurs when making outbound analog calls via the PRI. When I call a data-only call on the ISDN, it goes through with no problems. However, analog calls are causing me problems. Finally, I have a question for everyone. When I telnet directly to the modems that are connected to the PRI (e.g. port 2001) and make an analog call, it goes through just fine.
Now the errors you are getting is different..The router receiving the call is disconnecting the call with cause "Bearer capability not implemented". That means the receiving router is not provisioned to terminate 64kbps isdn data calls (Bearer Capability i = 0x8890) originated by this router.
Visit following link for those bearer cap decoding
So i think at this point telco have fixed the line and isdn call had forwarded all the way to the receiving router but the router receiving the call has no way to terminate that pure isdn data call. So talk to other side router admin for that.
Here is the link for troubleshooting call failures on isdn lines
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...