Hello,
as said earlier, it might be a bug. You probably need to investigate the module code to
get more information. If you are not able to do that, you could create an issue on our
tracker about it.
Cheers,
Henning
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com<https://gilawa.com/>
From: Vinayak Makwana <vinayak.makwana(a)ecosmob.com>
Sent: Tuesday, February 14, 2023 12:40 PM
To: miconda(a)gmail.com
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] Re: SCA Presence : Record-Route Filed Not Update in sca_subscriptions
Table
Hello,
We are getting a New updated call-id and record-route header after rebooting the SCA
device in SUBSCRIBE Packet. So we have observed in sca_subscriptions table it's
updating a new call-id field but it's not updating the record-route field.
Could you guide us for the above case ?
On Tue, Feb 14, 2023 at 12:06 AM Daniel-Constantin Mierla
<miconda@gmail.com<mailto:miconda@gmail.com>> wrote:
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)
--
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
sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org>
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<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Kamailio World Conference - June 5-7, 2023 -
www.kamailioworld.com<http://www.kamailioworld.com>
--
Regards,
Vinayak Makwana
[Das Bild wurde vom Absender entfernt. Ecosmob Technologies Pvt.
Ltd.]<https://www.ecosmob.com/>
Ecosmob Technologies Pvt. Ltd.
https://www.ecosmob.com
VoIP | Web | Mobile | IoT | Big Data
[Das Bild wurde vom Absender
entfernt.]<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.