Dear, What is the best solution for sip packet analyzing, on the busy server, to find the reason of one-way calling? best
Depends on your setup of course but the best way we have found is to span (copy) the Ethernet port of the OpenSER server to a different and dedicated machine that captures the packets. The load of the OpenSER box should not be impacted in this case.
To do specifically a span you would need a Cisco switch, but I would suspect most managed switches do something similar.
http://www.cisco.com/warp/public/473/41.html
-James
-----Original Message----- From: users-bounces@lists.openser.org [mailto:users-bounces@lists.openser.org] On Behalf Of Pezhman Lali Sent: Tuesday, June 17, 2008 11:01 AM To: users@lists.openser.org Subject: [OpenSER-Users] packet analyzing
Dear, What is the best solution for sip packet analyzing, on the busy server, to find the reason of one-way calling? best
_______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
What is one-way calling? similar to One-way audio?
I do all my debugging using "ngrep" for SIP debugging and tcpdump/wireshark if I need to debug RTP too (I use tcpdump to write a pcap file under Linux and then I use wireshark to analyze it)
If you have NAT problems take a look at the IP addresses and port numbers in Contact: headers, RURI, Via: headers and SDP.
regards klaus
Pezhman Lali schrieb:
Dear, What is the best solution for sip packet analyzing, on the busy server, to find the reason of one-way calling? best
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
James Van Vleet -
Klaus Darilion -
Pezhman Lali