This can happen when connected to certain Integrated Services Digital Networks (ISDN). When Cisco CallManager is the user side of the Primary Rate Interface (PRI), it can send a Progress Indicator (PI) information element (IE) in the alerting message, which is invalid in some PRI protocols. In the case where Cisco CallManager immediately connects the call after this, such as when forwarding to voicemail or answering with an auto attendant, the ISDN network complaint about the Progress Indicator can come after the connect message is already sent, which causes a protocol violation, and Cisco CallManager disconnects the call. This only happens with a Media Gateway Control Protocol (MGCP) controlled PRI gateway.
In order to fix the issue, change the DisableAlertingPI service parameter to True in all servers in the cluster, because when Cisco CallManager is configured as user side with the DMS-100 protocol, it must not send a PI in the alerting message.
See this call scenario:
1.NETWORK USER NETWORK 1.Setup---------> 2. (CFA) Setup-----> 3. CallProceeding<-------- 4.CallProceed<--- 5. Alerting<-------------- (with PI) 6.Alerting<------ (must without PI)
Please help.I have a Cisco CP-8841-3PCC-K9 Phone Help which I have factory reset, but this still seems to be provisioning to a service.I am trying to get to the Admin portal but there appears to be a password set through the provisioning service. I d...
Hi Everyone. Our Manager wants a way that people with IT issues call the help desk and the following needs to happen. It will be in the queue for up to two minutes for Level 1 to pickup the call. Then it will be in the queue for another two...
I am trying to AES 256 open_ssl encrypt a string variable. UCCX 12.5 supports the "PBKDF2WithHmacSHA256", which is what I am testing with. It was debugging fine (albeit not successfully performing the encryption) until I added the "return java.util.Base64...