Failing to geta a PRI working in Doha. Outbound calls failing with invalid number format. inbound calls also failing. Sure this is down to the ISDN plan / type. Inbound calls also fail - the setup message on q931 has plan type : ISDN Type:National on the inbound call setup - if this offers any clue ?
Here's a debug q931 from a failing outbound call :-
Progress Ind i = 0x8183 - Origination address is non-ISDN
This is the information that Telco must provide. Telco must tell what things they expect. Otherwise, it's all about permutation and combinations.. It can be hard to guess and find the correct combination of parameters. It can be tried though!!
So i made a call from the CLI using csim start and it connected. I noticed that in the outbound Q931 message there was no 'calling number' sent to the telco. I then made a test call from a handset which *did* send the calling number in the Q931 setup message and it failed.
I then translated the calling number (outbound) to remove it completely and calls are setting up correctly now. So the issue appears to be the telco rejected the message if the sending number was in the wrong format (incorrect number of digits maybe?). I have yet to confirm what format they need it in so for the time being and to get this to work I have removed the callign number from the Q931 setup message and we have outbound calls.
The issue does not appear to have been the ISDN plan type settings.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...