From what I have seen in the past, I believe that your client has some
garbage in the beginning of the message, so opensips would say that it
could't parse the first line. Whereas wireshark is a bit smarter to skip
over it.
On Sun, Jul 12, 2015 at 2:30 PM, John Nash john.nash...@gmail.com wrote:
Hello Frank,
I saw your message
http://lists.opensips.org/pipermail/users/2015-March/031296.html Did you
get any head or tail of this issue?..I also face the same situation where
in wireshark I see perfect messages but opensips log shows unable to parse
and shows junk characters
John
On Thu,
thx for the reply, I think I fixed the issue, but do you know why am I seeing
so many of these error messages? Is it just means some of the SIP message
opensips gets can not be parsed or have some weird stuff in it? I checked
these IP, they are from VoIP devices manufactured by Grandstream (e.g.
Hi,
First check if opensips actually started : run ps auxw | grep opensips
If it didn't , check the logs (messages or syslog) for errors.
If you see the process, check with netstat -lnp | grep opensips to see
the listening interfaces of OpenSIPS.
Regards,
Bogdan-Andrei Iancu
OpenSIPS
I am currently running Opensips 1.9 on Debian Whizzy, but as stated on my
other thread, I am getting some weird error which opensips would suddenly
stop working.
So, I am starting a new installation of Opensips 1.11 on Centos 6.6 using
the yum install method:
1. I was able to install yum
