>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 <[email protected]> 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, Mar 26, 2015 at 7:37 PM, Bogdan-Andrei Iancu <[email protected]> > wrote: > >> 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 Founder and Developer >> http://www.opensips-solutions.com >> >> On 25.03.2015 17:41, bluerain wrote: >> >>> 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 opensips install with no issue, but there >>> are >>> some module it didn't install which I need (e.g. db_unixodbc and db_mysql >>> and httpd) >>> >>> 2. So I went ahead download the source and all the dependency files >>> needed >>> and re-complie the oepnsips to get those .so files >>> >>> 3. After some tweaking of the database table structure and some other >>> stuff, >>> I was able to get opensips 1.11 running without error (on the message.log >>> file) using my 1.9 config file. >>> >>> So I did opensipsctl restart (just to make sure opensips starts) >>> I see: >>> >>> INFO: Restarting OpenSIPS : >>> INFO: stopped >>> >>> INFO: Starting OpenSIPS : >>> INFO: Removing stale PID file /var/run/opensips.pid. >>> INFO: started (pid: 2079) >>> >>> but when I try to use a VoIP device to register to it, it doesn't >>> response. >>> thus I did: >>> "sudo netstat -plnt" >>> >>> The only think I see that opensips is listening on is port 8888 by PID >>> 2080 >>> (I don't see 2079 at all) >>> >>> So what is happening? why no error and it seems opensips running but >>> yet is >>> not listsening on port 5060? >>> >>> I have 2 nic card and eth0 is the one with public IP and the default >>> route >>> where as the eth1 is the one with private IP and no default route. Thus >>> I >>> am sure everything is route out of the eth0 (public IP). >>> >>> When I do simply the command "opensips", it would simply return: >>> >>> Listening on >>> udp: xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]:5060 >>> Aliases: >>> *: (my FQDN):* >>> >>> So it looks like it think is listening on port 5060 but is not? >>> >>> Any help would be appreciated greatly! >>> >>> Thank you! >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-11-on-Centos-6-6-running-but-not-listening-tp7596152.html >>> Sent from the OpenSIPS - Users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Aron Podrigal - //Be happy :-)
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
