we've run into a strange problem regarding the communication between the mobile clients and the CUMA server.
On the ASA which is acting as a TLS proxy we got this message:
TLSP c9a5bf30: ==> Proxy Tx 58 bytes TLSP c9a5bf30: Started SSL handshake with Server TLSP c9a5bf30: Data channel ready for the Client TLSP c9a5bf30: <-- Proxy Rx 689 bytes TLSP c9a5bf30: ==> Proxy Tx 198 bytes TLSP c9a5bf30: --> Proxy Rx 437 bytes TLSP c9a5bf30: --> Rx #1 bp c5864ee0 bytes 406 TLSP c9a5bf30: --> Rx #1 sd ca4662d0, start_limit c5865280, end c5865416, bytes 406
MMP:: received 406 bytes from outside:220.127.116.11/1383 to inside:10.10.10.10./5443 MMP:: unsupported header MMP:: error=-1 from outside:18.104.22.168/1383 to inside:10.10.10.10/5443 TLSP c9a5bf30: Inspect action returned code 3 TLSP c9a5bf30: Tear down proxy for Client outside:22.214.171.124/1383. TLSP c9a5bf30: Tear down proxy for Server inside:10.10.10.10/5443. TLSP c9a5bf30: Lic released
When a client tries to connect to the server, the certificate is checked and then the session just hangs (terminated).
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...