We have a H323 Gateway with a Call Manager, with one E1 connected to a PBX through QSIG, and to the PSTN throufh a net4 PRI. When we make a call from an analog phone to the PSTN it fails with the message: "Cause i = 0x829F - Normal, unspecified"
If we made the call from the analog phone to an ip phone it is OK:
It looks like if there is a problem with the two switch types
I have attached the isdn q931 debug, the voice dialpeer debug and, not sure, the voice ccapi inout.
There are more calls in the log, as the system is up and running.
You will see the call finally establishes, because in order to solve it we have configured and alternative way for this call. Instead of the call going through the gateway (dialpeer 5) (from the PBX(E1)-gateway- PSTN(E1)) we have done it through the Call Manager (PBX(E1)-CCM-Gateway-PSTN(E1))
I beleive the problem here is with the E1 provider. Your gateway doesn't report an error, but does receive the diconnect message with the '31' cause code from the provider's switch. Looking at the q931 debug from both the PBX-PSTN and the CCM-PSTN calls, the difference seems to be the Called Party Number Plan is 'Private' from the PBX and 'Unknown' from the CCM.
You can force the Called Party Number Plan and Type from the seriel interface for the E1. Try this command on the PSTN E1 interface:
isdn map address .* plan unknown type unknown
Thinking about this some more, I think it makes sense. There is probably an option within the PBX to set the outgoing ISDN switch type. It is probably set to something like Tie line or possibly internal, which is why it is specifying a private number plan. The PSTN switch rejects it because it isn't configured to deal with private number plans.
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: email@example.com 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 ...