Module: sip-router
Branch: master
Commit: 83add48b7c1cdf0d9f64c24bcc134195699daac1
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=83add48…
Author: Robert Boisvert <rdboisvert(a)gmail.com>
Committer: Timo Teräs <timo.teras(a)iki.fi>
Date: Thu Oct 10 08:25:05 2013 -0400
mohqueue: fixes
* cleaned up all error paths (fixed crashes)
* added support for INVITEs that get stuck
* adjusted code to avoid compiler warnings
* PRACK only invoked if Require: 100rel set
* fixed bug that allowed a new call to be created more than once
Documentation
* updated NOTES
---
modules/mohqueue/NOTES | 17 +--
modules/mohqueue/mohq_funcs.c | 301 ++++++++++++++++++++++-------------------
2 files changed, 171 insertions(+), 147 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=83a…
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#351 - registrar: process expired contacts first
User who did this - Víctor Seva (linuxmaniac)
----------
We are selecting the contact by instance but when we are trying to update the record we are using:
3(3091) DEBUG: usrloc [ucontact.c:682]: db_update_ucontact_addr(): aor:testuser1003
3(3091) DEBUG: usrloc [ucontact.c:689]: db_update_ucontact_addr(): contact:sip:testuser1003@127.0.0.1:50602;ob
3(3091) DEBUG: usrloc [ucontact.c:696]: db_update_ucontact_addr(): callid:1-3141@127.0.0.1
not the instance or the right old contact: sip:testuser1003@127.0.0.1:6666;ob
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=351#comment1115
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#351 - registrar: process expired contacts first
User who did this - Víctor Seva (linuxmaniac)
----------
More tests. Using sqlite for ddbb.
Using the second register with Contact: "TestBria" <sip:[field0 file="callee.csv" line=0]@[local_ip]:[local_port];ob>;reg-id=1;+sip.instance="<urn:uuid:C3DD6013-20E8-40E3-8EA2-5849B02ED0C4>" results in the right contact in memory but no changes on the ddbb
----------
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=351#comment1114
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi,
I've an observation regarding PUBLISH message handling. on
receiving of PUBLISH message, SER is sending NOTIFY with presence
information of all the buddies available in the buddy list while it should
be sending that only for the buddy updating his/her presence information.
Because of this the size of every NOTIFY message traversing on the network
is quite high.
Please help if there is any change I'll have to do to achieve the desired.
Thanks and Regards,
--Piyush Bansal
The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
Hi,
I've an observation regarding PUBLISH message handling. on
receiving of PUBLISH message, SER is sending NOTIFY with presence
information of all the buddies available in the buddy list while it should
be sending that only for the buddy updating his/her presence information.
Because of this the size of every NOTIFY message traversing on the network
is quite high.
Please help if there is any change I'll have to do to achieve the desired.
Thanks and Regards,
--Piyush Bansal
The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
please help
----- Forwarded by Piyush Bansal/RCOM/RelianceADA on 10/10/2013 10:51 AM
-----
From:
Piyush Bansal/RCOM/RelianceADA
To:
serusers(a)iptel.org, serdev(a)iptel.org
Date:
10/09/2013 12:15 PM
Subject:
query regarding SER
HI there,
I have few queries regarding data deletion from database tables-
1. Once the timer of REGISTER expires, the entry for that user is not
getting deleted from "location" table.
2. Same thing is happening with SUBSCRIBER timer expiry. The entries from
presence tables are not getting deleted.
Please suggest how to debug this issue??
Thanks and Regards,
--Piyush Bansal
The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.