23 May
2008
23 May
'08
12:55 a.m.
Hi Iñaki,
I had the same issue with a Nortel CS1k switch, the easiest way to check this
problem is to use the Wireshark feature "Display raw text for SIP message"
which can be enabled under preferences / protocols / SIP
regards,
Andreas
Ovidiu Sas schrieb:
Hello Inaki,
Perform a raw capture using tcpdump and open the file with wireshark.
Check the lower window in wireshark where you have the message
displayed in hex format.
There you will be able to spot '\n' and '\r'. To find the hex codes,
perform a 'man ascii' on your linux box.
Regards,
Ovidiu Sas
On Tue, May 20, 2008 at 10:53 AM, Iñaki Baz Castillo <ibc(a)in.ilimit.es> wrote:
El Tuesday 20 May 2008 16:37:03 Bogdan-Andrei
Iancu escribió:
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Iñaki,
have you tried the "-W byline" ? - it will format you the lines.
Hi Bogdan. Yes, in fact I use this option "-W byline", but this
option just
splits the trace into lines (macthing "\n"). This is not enough for me since
\r is not showed.
I need it since I send and receive traffic from a carrier using a painful
Nortel CS2K softswitch that separes SDP lines with \r instead of the
mandatory \r\n adn they are applying dirty and not working patches during
production state so I need a way to monitorize it.
Thanks a lot.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users