Hello,
not the sca developer, nor a user of the module, but if after reboot the
UA reuses the previous dialog (same call-id, tags, etc.) then
record-route should not be changed, RFC3261 section 12.2:
Requests within a dialog MAY contain Record-Route and Contact header
fields. However, these requests do not cause the dialog's route set
to be modified, although they may modify the remote target URI.
I am not aware of other recent RFCs that could amend this specification,
but I haven't followed closely the RFC published lately.
So from RFC3261 specs perspective, the module is ok. On the other hand,
I understand the need to be flexible to cope with various SIP systems,
therefore one can add a modparam to control behaviour and have a mode
when the record route is updated in such case.
If it is a new dialog after reboot, then a new record should be created
by SCA module, not updating the old record.
Cheers,
Daniel
On 07.02.23 12:04, Vinayak Makwana wrote:
> Hello all,
> I am using the sca module in kamailio script.so when i
> subscribe with my ip phone for SCA Presence i get all the information
> in a sca_subscriptions table for the first time. When I reboot the
> device I get a new record-route header in trace but It does not update
> *record-route *Filed in sca_subscriptions table.
>
> Can anyone help me out with this issue ?
>
> _Here's modparam configuration
> _
> modparam("sca", "db_update_interval", 10 )
> modparam("sca", "db_url", DBURL_LOCAL)
> modparam( "sca", "line_seize_max_expires", 30)
> modparam( "sca", "purge_expired_interval", 1800)
> --
>
>
> *<https://www.ecosmob.com/itexpo/>
> *
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our
> website, any views or opinions presented in this email are solely
> those of the originator and do not necessarily represent those of the
> Company or its sister concerns. Any liability (in negligence, contract
> or otherwise) arising from any third party taking any action, or
> refraining from taking any action on the basis of any of the
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for
> the use of the addressee(s) and contains information that is
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination,
> distribution, or copying of this communication is prohibited. Please
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of
> viruses, trojans, similar or new contaminants/malware, interceptions
> or interference, and may not be compatible with your systems. You
> shall carry out virus/malware scanning on your own before opening any
> attachment to this e-mail. The sender of this e-mail and Company
> including its sister concerns shall not be liable for any damage that
> may incur to you as a result of viruses, incompleteness of this
> message, a delay in receipt of this message or any other computer
> problems.
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
> Edit mailing list options or unsubscribe:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
