[OpenSER-Users] openser listen:0.0.0.0

[toly]

Greetings,

Below are the parts of routing script,


listen=0.0.0.0        # This is where OpenSER installed
port=5070
children=8
reply_to_via = no
sip_warning = yes
check_via = no
dns=no
rev_dns=no
disable_dns_blacklist=true


route {
        if (!pike_check_req()) {
                xlog("L_NOTICE", "TRACKING [0] ALARM - TOO MANY HITS on
IP=$si !!");
                exit;
        };

        # -----------------------------------------------------------------
        # Sanity Check Section
        # -----------------------------------------------------------------
        if (!mf_process_maxfwd_header("10")) {
                sl_send_reply("483", "Too Many Hops");
                exit;
        };

        if (msg:len > max_len) {
                sl_send_reply("513", "Message Overflow");
                exit;
        };

      
        force_rport();


        # -----------------------------------------------------------------
        # Record Route Section and Acc section
        # -----------------------------------------------------------------

        if (method=="INVITE" && nat_uac_test("19")) {
                record_route_preset("_DNS_NAME_HIDDEN_:5070;nat=yes");                              
        } else if (method!="REGISTER") {
                  record_route();
        };
        ......
}

I have no problems with the script with normal ip or dns name, that's why I
have not posted the whole.
It does not work with listen=0.0.0.0 
If A invites B, then B send OK, proxy can't route ACK from A to B - it's
looping
the same happened with BYE , proxy can't route - it's looping

On proxy's startup I get this in the log:
06/24 19:37:42  warning  <socket_info.c: 590> WARNING: fix_socket_list:
could not rev. resolve 0.0.0.0
06/24 19:37:42  debug  <socket_info.h: 316> DEBUG:socket2str:
<udp:0.0.0.0:5070>
06/24 19:37:42  warning  <socket_info.c: 590> WARNING: fix_socket_list:
could not rev. resolve 0.0.0.0
06/24 19:37:42  debug  <socket_info.h: 316> DEBUG:socket2str:
<tcp:0.0.0.0:5070>

As I understand 0.0.0.0 will be included in the record-route and as a result
proxy will not be able to route the message.

Can anybody answer with with more formal explanation of it?

Thanks a lot,
Toly

-- 
View this message in context: http://www.nabble.com/openser-listen%3A0.0.0.0-tp18103385p18103385.html
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.