Add #!define WITH_IPAUTH to your script and the server's IP address to the
address table and restart Kamailio.
Packets from your local address to your local address are routed through
your loopback interface. lo0 looks like some BSD, so you can verify that in
the routing table with netstat -rn
On Sat, Sep 17, 2016, 18:09 Torsten Hantzsche <thantzs...@petitenet.de>
> while playing with the script from
> and "kamailio 4.4.3 (x86_64/freebsd) 5a2195" I could not see any NOTIFY
> going out to the subscribed watcher.
> "tcpdump -i lo0" shows self injected PUBLISH packets challenged with
> "407 Proxy Authentication Required" and there they got stuck.
> The PUBLISH packets are sent on lo0 from my network address to the same
> address (here 10.0.0.106 to 10.0.0.106). The proxy challenge is also sent
> 10.0.0.106 to 10.0.0.106.
> An xlog entry with the variable "$Ri" in route REQUEST shows 10.0.0.106
> Since these packets are only seen on lo0, should "$Ri" not show 127.0.0.1?
> After disabling the WITH_AUTH variable, the watcher is getting its
> Now I wonder under which circumstances this script is supposed to function
> correctly without changes in the AUTH route?
> By the way, I had the same problem with the provided script of the
> msilo module (
> which too only works if there is no "auth_challenge" in the way.
> Could somebody with more insight in Kamailio internals give some hints
> on this, please? How can it get solved in an elegant way?
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list