OpenSIPS/OpenSER-a versatile SIP Server / Bugs / #636 uac_registrant expires decrementing

#636 uac_registrant expires decrementing

Milestone: 1.10.x

Status: closed-fixed

Owner: Ovidiu Sas

Labels: modules (454)

Priority: 5

Updated: 2015-02-28

Created: 2013-03-25

Creator: Paul

Private: No

Two outgoing registrations with identical parameters. When viewed with Opensips CP , over time , the second entry "expires=" keeps decreasing from the value in the database (240). It eventually reaches 1 and then contact errors appear in the log. the other registrant expires also starts to decrease at this point.

Discussion

Ovidiu Sas - 2013-03-25

Hello,

Can you provide more details about what are you trying to achieve?
Also, if there are errors in the log, please paste them here.

Regards,
Ovidiu Sas

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2013-03-26

uac_registrant_errors.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2013-03-26

Uploaded file with more information.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ovidiu Sas - 2013-03-26

Please put your comments in the 'Comments' section so other can search and find if looking for similar issues.

You were saying:
I'm registering to a service provider's two proxies. The registrations are successful and I am receiving incoming calls. However, opensisps has been operating normally for about a week until various messages started to appear in the log. Doing some checking, I noticed that the "expires=xxx" from the "reg_list" MI command was displaying expires=1. I restarted opensips and it was now returning expires=240 as the correct value. Over time it started to decrement again as seen from the MI reg_list output. The real domain names have been masked.

Opensips CP "reg_list" command: begins at "expires=240" and decrementing until it eventually gets to 1.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ovidiu Sas - 2013-03-26

I pushed a fix in trunk for avoiding altering the initial expires.
Please test it and let me know how it works.

Also, if you can provide me some traces related to the REGISTER/200ok, it would help.
You can send the trace privately to me or post them here after you obfuscate all the sensitive data.

Regards,
Ovidiu Sas

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2013-03-30

"expires=" is no longer decrementing but the message below appears in the log every few days.

Mar 30 00:58:13 sip /usr/sbin/opensips[17527]: CRITICAL:core:timer_ticker: timer handler <uac_reg_check> lasted (2140000 us) for more than timer tick (1000000 us) -> potential timer shifting

The messages relating to the REGISTER/200ok have not re-appeared.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Bogdan-Andrei Iancu - 2013-04-01

assigned_to: nobody --> osas

status: open --> open-accepted
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ovidiu Sas - 2013-04-01

It seems that you are having some DNS issues.
Try to use IPs instead of FQDNs in registrar's URI and see if the issue is still present.

Regards,
Ovidiu Sas

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2013-04-19

Ovidiu, message has not re-appeared using the IP's directly instead of the domain names for registration.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ovidiu Sas - 2013-04-20

Thank you for the update.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ovidiu Sas - 2013-04-20

status: open-accepted --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.