To capture active SIP registrations, the best way I have found is to run the following on a Linux, BSD system. If you have your endpoints register to your proxy/gateway you can capture the traffic very nicely using the tshark utility. Which is the console (text-based) version of Wireshark. I am capturing the following fields (From Address, Expiry Time, Display Info, Frame Time, IP Destination, and IP Source) in my SIP messaging...
"STUN (Simple Traversal of UDP (User Datagram Protocol) through NATs (Network Address Translators)) is a network protocol allowing a client behind a NAT (or multiple NATs) to find out its public address, the type of NAT it is behind..."
need to add our protocol specific implementation via ProtocolFilter. Grizzly ships with a ReadFilter than can be used to read bytes, independently of the transport used (UDP or TCP). Mainly, the ReadFilter reads the available bytes, and pass the control o
** Posted using Viigo: Mobile RSS, Sports, Current Events and more ** We all know about SIP, and it's hard to deny its impact on IP communications, especially VoIP. Well, fellow blogger<sep/>
The Open IMS Core is an implementation of IMS Call Session Control Functions (CSCFs) and a lightweight Home Subscriber Server (HSS), which together form the core elements of all IMS/NGN architectures as specified today within 3GPP, 3GPP2, ETSI TISPAN and
Session Initiation Protocol (SIP) is a signalling protocol, widely used for setting up and tearing down multimedia communication sessions such as voice and video calls over the Internet
Simple Traversal of UDP through NATs (STUN), is a network protocol allowing a client behind a NAT (Network Address Translator) to find out its public address, the type of NAT it is behind and the internet-side port associated by the NAT with a particular