Hi Aqs;
Checking with full debug on I can see that the publish appears to be created.
udp_rcv gets the publish (source IP is servers public IP 5.6.7.8:5060). From
what I can see the AUTH route is sending a proxy auth challenge.
5(5525) received on udp socket: (106/100/1017) [[PUBLISH
sip:[email protected] SIP/2.0 0D 0A Via: SIP/2.0/UDP
5.6.7.8;branch=z9hG4bK0ae2.85bf70]]
5(5525) received on udp socket: (106/100/526) [[SIP/2.0 407 Proxy
Authentication Required 0D 0A Via: SIP/2.0/UDP
5.6.7.8;branch=z9hG4bK0ae2.85bf70510]]
I think it’s getting caught here;
route[AUTH] {
if (is_method("REGISTER") || from_uri==myself)
{
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
auth_challenge("$fd", "0");
exit;
}
So that looks like the first issue. If I patch AUTH route to allow through
anything with the servers source IP (A bit dangerous as someone could faking IP
source on UDP. is there a better way?) the proxy_challenge no longer gets sent
and I see what I think is it trying to send a notify to the watchers phone;
send_notify_request(): NOTIFY sip:[email protected] via sip:1.2.3.4:5065 on
behalf of sip:[email protected] for event dialog : [email protected]
However it doesn’t come out of the ethernet port (sngrep) and I can’t see any
obvious failure. Although that may be me as I’m still trying to follow debug
logs!
Given the line above is there a way to trace it?
Thanks!
Best regards
Mark_______________________________________________
Kamailio (SER) - Users Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
