11 Oct
2013
11 Oct
'13
10:32 p.m.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - rene montilva (renex)
Attached to Project - sip-router
Summary - UAC Module Fail to refresh REGISTER
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - i'm testing uac module with a did provider, apparently it works the first
register, when it's going to refresh the session the register packed don't send
the proxy-authorization header.
My kamailio is 4.0, the debian wheezy repository
this is my parameter config:
#!ifdef WITH_UAC
#---------- uac params ----------#
modparam("uac", "reg_db_url",DBURL)
modparam("uac", "reg_timer_interval",60)
modparam("uac", "reg_retry_interval",120)
modparam("uac", "reg_db_table", "uacreg")
modparam("uac","credential","username:domain:password")
modparam("uac","auth_realm_avp","$avp(i:10)")
modparam("uac","auth_username_avp","$avp(i:11)")
modparam("uac","auth_password_avp","$avp(i:12)")
modparam("uac","restore_mode","auto")
modparam("uac", "reg_contact_addr", "xx.xx.xx:5060")
#!endif
this is the route block:
if(uac_reg_request_to("$fU", 1))
{
xlog("L_NOTICE", "Found remote user [$rU] on [$rd] via
[$du]");
t_on_failure("REMOTE_AUTH");
t_relay();
}
inside route[LOCATION] at the end:
#!ifdef WITH_UAC
if(uac_reg_lookup("$rU", "$ru")) {
xlog("request from a remote SIP provider [$ou => $ru]\n");
}
lookup("location");
#!endif
failure_route[REMOTE_AUTH] {
if ($T_reply_code == 401 or $T_reply_code == 407) {
xlog("L_NOTICE", "Remote asked for authentication");
uac_auth();
}
}
this is the error log by syslog
ct 11 13:52:47 rene /usr/sbin/kamailio[7413]: INFO: <script>: Routing locally
generated REGISTER to<sip:ippbx.xxxxx.com>
Oct 11 13:52:47 rene /usr/sbin/kamailio[7400]: ERROR: uac [uac_reg.c:537]:
uac_reg_tm_callback(): authentication failed for <2127207679>
this is sip trace with first register:
Frame 209: 671 bytes on wire (5368 bits), 671 bytes captured (5368 bits) on interface 0
Ethernet II, Src: Hewlett-_6b:6e:49 (10:1f:74:6b:6e:49), Dst: Cisco_7f:1e:69
(00:13:1a:7f:1e:69)
Internet Protocol Version 4, Src: 10.20.8.45 (10.20.8.45), Dst: xx.xx.xx.xx (xx.xx.xx.xx)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:ippbx.xxxxx.com SIP/2.0
Message Header
Via: SIP/2.0/UDP 10.20.8.45;branch=z9hG4bKb278.906502e4.0
To: sip:5201341115@ippbx.xxxxx.com
From: sip:5201341115@ippbx.xxxxx.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-4cad
CSeq: 11 REGISTER
Call-ID: 2e81fffd-7628(a)127.0.0.1
Max-Forwards: 70
Content-Length: 0
User-Agent: kamailio (4.0.3 (i386/linux))
Contact: <sip:01133212720@xxx.xxx.xxx:5060>
Expires: 60
Proxy-Authorization: Digest username="1341115", realm="xxxxx",
nonce="5DB4B614FCD76AD44FFFC3BEAECBDA9B", uri="sip:ippbx.xxxxx.com",
response="d7d38055e339a2554cf2bb7e79e9b6f4", algorithm=MD5
this is sip trace with the second register:
Frame 681: 468 bytes on wire (3744 bits), 468 bytes captured (3744 bits) on interface 0
Ethernet II, Src: Hewlett-_6b:6e:49 (10:1f:74:6b:6e:49), Dst: Cisco_7f:1e:69
(00:13:1a:7f:1e:69)
Internet Protocol Version 4, Src: 10.20.8.45 (10.20.8.45), Dst: xx.xx.xx.xx
(66.33.146.52)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:ippbx.xxxxx.com SIP/2.0
Message Header
Via: SIP/2.0/UDP 10.20.8.45;branch=z9hG4bKb278.a06502e4.0
To: sip:5201341115@ippbx.xxxxx.com
From: sip:5201341115@ippbx.xxxxx.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-4d45
CSeq: 10 REGISTER
Call-ID: 2e81fffe-7628(a)127.0.0.1
Max-Forwards: 70
Content-Length: 0
User-Agent: kamailio (4.0.3 (i386/linux))
Contact: <sip:01133212720@xxx.xxx.xxx:5060>
Expires: 60
there isn't proxy-authorization Header
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=352
You are receiving this message because you have requested it from the Flyspray bugtracking
system. If you did not expect this message or don't want to receive mails in future,
you can change your notification settings at the URL shown above.