Hi,
I’m wondering if there is a flag somewhere in the UAC module config that prevents remote registration from happening.
It looks like I’ve loaded the uacreg table but I can’t see any REGISTER methods being sent from Kamailio to the remote peer.
The remote registrants are loaded using this config:
listen=udp:172.16.176.150:5060
loadmodule "db_postgres.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "counters.so" loadmodule "uac.so"
modparam("uac", "reg_db_url", DBURL) modparam("uac", "reg_contact_addr", “172.16.176.150:5060") modparam("uac", "reg_db_table", "uacreg") modparam("uac", "reg_timer_interval", 10) modparam("uac", "reg_retry_interval", 10)
request_route { route(RELAY); }
route[RELAY] {
t_on_reply("MANAGE_REPLY");
if (!t_relay()) { sl_reply_error(); } exit; }
And it looks like this has been consumed by Kamailio:
$ kamcmd uac.reg_dump { l_uuid: 2cc6776d-61ed-4ea1-a3ae-055f89bd4d3f l_username: 126231943099723776 l_domain: 172.16.176.150 r_username: 1000 r_domain: 172.16.176.129 realm: 172.16.176.129 auth_username: 1000 auth_password: password auth_proxy: sip:172.16.176.129:5080 expires: 0 flags: 0 diff_expires: -1531235076 timer_expires: 0 reg_init: 1531234841 reg_delay: 0 }
Doing a refresh successfully reloads the uacreg data
$ kamcmd uac.reg_refresh 2cc6776d-61ed-4ea1-a3ae-055f89bd4d3f
I can get Kamailio to forward an OPTIONS message to the remote peer () to verify network connectivity, e.g. :
$ru = "sip:1000@172.16.176.129:5080"; $fs = "udp:172.16.176.150:5060";
But Kamailio does not appear to generate REGISTER messages either after first boot or as a result of the manual refresh.
This is using an instance of Kamailio 5.0.1. Should I try with a newer version?
Is there a way to get extra debugging of the uac module?
If I increase the debug verbosity, I get quite granular detail for the DB traffic, but the uac module doesn’t appear to emit much diagnostics.
Many thanks,
Ben
Hello,
is the 'expires' value in the db records greater than 0? It is shown 0 in the rpc dump.
Cheers, Daniel
On 11.07.18 13:36, Ben Hood wrote:
Hi,
I’m wondering if there is a flag somewhere in the UAC module config that prevents remote registration from happening.
It looks like I’ve loaded the uacreg table but I can’t see any REGISTER methods being sent from Kamailio to the remote peer.
The remote registrants are loaded using this config:
listen=udp:172.16.176.150:5060
loadmodule "db_postgres.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "counters.so" loadmodule "uac.so"
modparam("uac", "reg_db_url", DBURL) modparam("uac", "reg_contact_addr", “172.16.176.150:5060") modparam("uac", "reg_db_table", "uacreg") modparam("uac", "reg_timer_interval", 10) modparam("uac", "reg_retry_interval", 10)
request_route { route(RELAY); }
route[RELAY] {
t_on_reply("MANAGE_REPLY");
if (!t_relay()) { sl_reply_error(); } exit; }
And it looks like this has been consumed by Kamailio:
$ kamcmd uac.reg_dump { l_uuid: 2cc6776d-61ed-4ea1-a3ae-055f89bd4d3f l_username: 126231943099723776 l_domain: 172.16.176.150 r_username: 1000 r_domain: 172.16.176.129 realm: 172.16.176.129 auth_username: 1000 auth_password: password auth_proxy: sip:172.16.176.129:5080 expires: 0 flags: 0 diff_expires: -1531235076 timer_expires: 0 reg_init: 1531234841 reg_delay: 0 }
Doing a refresh successfully reloads the uacreg data
$ kamcmd uac.reg_refresh 2cc6776d-61ed-4ea1-a3ae-055f89bd4d3f
I can get Kamailio to forward an OPTIONS message to the remote peer () to verify network connectivity, e.g. :
$ru = "sip:1000@172.16.176.129:5080"; $fs = "udp:172.16.176.150:5060";
But Kamailio does not appear to generate REGISTER messages either after first boot or as a result of the manual refresh.
This is using an instance of Kamailio 5.0.1. Should I try with a newer version?
Is there a way to get extra debugging of the uac module?
If I increase the debug verbosity, I get quite granular detail for the DB traffic, but the uac module doesn’t appear to emit much diagnostics.
Many thanks,
Ben
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
On 11 Jul 2018, at 17:11, Daniel-Constantin Mierla miconda@gmail.com wrote: is the 'expires' value in the db records greater than 0? It is shown 0 in the rpc dump.
Yes, that was it.
After setting the expires field to 360 and the reg_delay to 3, kamailio sent the REGISTER messages to the auth proxy:
7(9339) DEBUG: tm [uac.c:427]: t_uac_prepare(): next_hop=sip:172.16.176.129:5080
So now the uac module has successfully registered with the remote proxy.
Many thanks for you help, very much appreciated :-)
Ben
It should also work without setting reg_delay, however, reg_delay purpose it to spread the registrations not to be done all at the same time, so if you set it, try to use several values if you have many users.
Cheers, Daniel
On 12.07.18 00:11, Ben Hood wrote:
On 11 Jul 2018, at 17:11, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
is the 'expires' value in the db records greater than 0? It is shown 0 in the rpc dump.
Yes, that was it.
After setting the expires field to 360 and the reg_delay to 3, kamailio sent the REGISTER messages to the auth proxy:
7(9339) DEBUG: tm [uac.c:427]: t_uac_prepare(): next_hop=sip:172.16.176.129:5080
So now the uac module has successfully registered with the remote proxy.
Many thanks for you help, very much appreciated :-)
Ben