[OpenSIPS-Users] Opensips 1.11 on Centos 6.6, running but not listening?

[bluerain]

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.
HT501)  but when I do some wireshark at my firewall, I don't see these weird
characters though, so where they from?  (e.g. the opensips said it parsed
"°#001°°V•'Ï&#034ðé", I don't see those weird stuff in data captures at my
firewall.)  Or maybe I am not looking at the right places?

Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3676]:
ERROR:core:receive_msg: Unable to parse msg received from [xxx]
Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3675]:
ERROR:nathelper:fix_nated_sdp_f: Unable to get bodies from message
Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3678]:
ERROR:core:parse_first_line: bad request first line
Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3678]:
ERROR:core:parse_first_line: at line 0 char 14: 
Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3678]:
ERROR:core:parse_first_line: parsed so far: °#001°°V•'Ï&#034ðé 
Mar 26 17:22:42 OSIPIBD-4 /usr/local/sbin/opensips[3678]:
ERROR:core:parse_msg: message=<>



--
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-tp7596152p7596167.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.