I just found that this error only occurs on mobile network connections, not on Wi-Fi. So something in the mobile network IP
On 27 July 2015 at 18:42, Nabeel <[email protected]> wrote: > I am using rtpproxy with OpenSIPS, I can register to the server but I get > the following error when making a call: > > ERROR:core:parse_via: bad port > ERROR:core:parse_via: <SIP/2.0/TCP > 10.31.188.230:38703:-1;rport;branch=z9hG4bK66793#015#012Max-Forwards: > 70#015#012To: > <sip:[email protected];transport=tcp>#015#012From: > <sip:[email protected]>;tag=z9hG4bK07391365#015#012Call-ID: > [email protected]#015#012CSeq > <http://[email protected]#015%23012CSeq>: 1 > CANCEL#015#012Contact: > <sip:[email protected]:38703;transport=tcp>#015#012Expires: > 3600#015#012User-Agent: Name/1.3.4/MP-S168#015#012Content-Length: > 0#015#012#015#012> > ERROR:core:parse_via: parsed so far:<SIP/2.0/TCP 10.31.188.230:38703> > ERROR:core:get_hdr_field: bad via > DBG:core:set_err_info: ec: 1, el: 3, ei: 'error parsing Via' > DBG:core:get_hdr_field: error exit > > The config I'm using: > > modparam("registrar","received_avp", "$avp(42)") > modparam("usrloc","nat_bflag",6) > modparam("nathelper", "ping_nated_only", 1) > modparam("nathelper", "natping_tcp", 1) > modparam("nathelper", "sipping_bflag", 7) > modparam("nathelper", "natping_interval", 5) > modparam("nathelper", "sipping_from", "sip:pinger at PUBLIC-IP:5060") > modparam("nathelper", "received_avp", "$avp(i:801)") > modparam("nathelper", "nortpproxy_str", "") > modparam("rtpproxy", "rtpproxy_sock", "udp:PUBLIC-IP:7890") > modparam("nat_traversal", "keepalive_state_file", "/etc/keepalive_state") > modparam("nat_traversal", "keepalive_interval", 5) > > > How do I fix this? > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
