Our CallManager connect to PSTN trough a DT24+. The PRI comes from a 5ESS (release 13). The Calling Number pass fine but did anyone achieve to get the Calling Name in&out of a similar topology? Thanks.
According to standards, the Network-side of the ISDN trunk provides the Display IE. If the 5ESS is the Network-side, then you will need to configure display names for all the phone numbers assigned to IP phones that are across the PRI trunk, and to send the caller name to the IP phones, the delivery of the Display IE needs to be enabled. Also, I'm not positive this is required, but if you are using CallManager previous to version 3.0(5a) then you need to set the CallManager Service Parameter "DisplayIEDeliveryFlag" to T. If you are running 3.0(5a) or later, you need to check the box on the DT-24+ gateway configuration screen that says Display IE Delivery.
Then, once you have a trace file that includes a call where no name display occurred and you think it should have, use the Q931 Translator tool to open the file and look at the Q.931 messages to find out what is happening. The tool is located on your CallManager 3.0(x) server in the directory C:\Program Files\Cisco\bin
We did set IE flags but still the trace shows and "Unexpected recognized Ie found in Isdn message". It seems there is a protocol mismatch with the 5ESS, but we tried all possible combinations. I was wondering if anyone in the forum experienced the same thing. I wonder about other CallManagers connected directly to PSTN/5E.
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 ...