by using this configuration, for the skinny message , i only receive skinnykeealive , and not the skinny message that inform for start and stoP call are not received [ that is imPortant for the aPPlication used for recording each call).
You can try using the keyword 'both', but from my experience this causes duplicate packets.
You may be on the wrong switch for the traffic you're looking for if you're not seeing the right SCCP messages. The VLAN traffic you're looking for may not go through that particular switch. Find out where the phone is at, where the destination is at, and check out your spanning tree topology.
I try to config span that it still same a problem.
And Engineer's record team told that
"To elaborate further for the voice packet sniffed from IP phone connected to CallManager 8.0.2, we analyzed the packet by using Wireshark (a network protocol analyzer) and found that aside SKINNY mes sage “KeepAliveMessage” & “KeepAliveAckMessage”, there is no other SKINNY message such as “CallStateMessage=1 (off hook)”, “CallStateMessage=2 (on hook)”, “CallStateMessage=5 (connected)”, etc" but in CallManager 4.2 have all SKINNY message."
How I do this case?
I attach file that how a different between capture packet CCM4.2 and CCM 8.0.
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...