It shows the value of the expires parameter that will be sent in the
next REGISTER.
If the registrar is imposing a specific expiration time, we could obey :)
Please try the attached patch and let me know if it's working ok.
diff --git a/modules/uac_registrant/registrant.c
b/modules/uac_registrant/registrant.c
index 2e73f61..2595a01 100644
--- a/modules/uac_registrant/registrant.c
+++ b/modules/uac_registrant/registrant.c
@@ -355,6 +355,7 @@ int run_reg_tm_cback(void *e_data, void *data, void *r_data)
rec->state = REGISTERED_STATE;
if (exp) {
rec->registration_timeout = now + exp - timer_interval;
+ rec->expires = exp;
} else {
rec->registration_timeout = now + rec->expires
- timer_interval;
}
On Fri, Nov 8, 2013 at 8:52 PM, Jeff Pyle <[email protected]> wrote:
> Hello,
>
> I noticed a display error on the reg_list fifo command from uac_registrant
> on 1.10.
>
> # opensipsctl fifo reg_list
> AOR:: sip:[email protected] expires=3600
> state:: REGISTERED_STATE
> last_register_sent:: Fri Nov 8 20:47:22 2013
> registration_t_out:: Fri Nov 8 21:02:02 2013
> registrar:: sip:domain.com
> binding:: sip:[email protected]:5060
> dst_IP:: IPv4 ip=switch.remote.ip.address
>
> I specified the expire time in the registrant table row as 3600. In this
> case the switch replied with 900 in the 200 OK. The "registration_t_out"
> value is correct, but the expires= time shows my 3600 request time instead
> of the switch's returned 900.
>
> Unless this is by design?
>
>
> - Jeff
>
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
--
VoIP Embedded, Inc.
http://www.voipembedded.com
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
