sr-dev October 2013

sr-dev@lists.kamailio.org

33 participants
254 discussions

[tracker] Comment added: Invalide tel INVITE crashes 4.0.3

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#348 - Invalide tel INVITE crashes 4.0.3 User who did this - Petrov (Vasyly) ---------- Hello. I have the same problem. First time it is happend Sep 11 14:56:07 again Oct 7 19:34:54 if I reboot system all going ok and all work. Kamailio 4.0. I'll try to get debug but it's so hard write 1 monts but I'll try. If you find what fix this problem please tell me. Thank you. <code>Sep 11 14:56:07 kamailio[1053]: ALERT: <core> [main.c:788]: handle_sigs(): child process 1055 exited by a signal 11 Sep 11 14:56:07 kamailio[1053]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generated Sep 11 14:56:07 kamailio[1053]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD Sep 11 14:56:07 kamailio[1081]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1088]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1084]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1077]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1075]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1062]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1073]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1070]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1069]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1066]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1058]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1064]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1061]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1056]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1086]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1078]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1057]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Sep 11 14:56:07 kamailio[1053]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)</code> <code>Oct 7 19:34:54 kamailio[1036]: ALERT: <core> [main.c:788]: handle_sigs(): child process 1040 exited by a signal 11 Oct 7 19:34:54 kamailio[1036]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generated Oct 7 19:34:54 kamailio[1036]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD Oct 7 19:34:54 kamailio[1049]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1062]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1050]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1057]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1053]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1047]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1059]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1042]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1039]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1044]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1041]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1038]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1052]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received Oct 7 19:34:54 kamailio[1036]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)</code> ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=348#comment1113 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.

10 years, 8 months

git:richard.good/diameter_rx_media: modules/ims-qos: fix typo in cdpeventprocessor

by Richard Good

Module: sip-router Branch: richard.good/diameter_rx_media Commit: 13473c328ce9489558b523f46e346c2d14f93139 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=13473c3… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Wed Oct 9 18:05:43 2013 +0200 modules/ims-qos: fix typo in cdpeventprocessor --- modules/ims_qos/cdpeventprocessor.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/modules/ims_qos/cdpeventprocessor.c b/modules/ims_qos/cdpeventprocessor.c index 1017c5c..8cb8751 100644 --- a/modules/ims_qos/cdpeventprocessor.c +++ b/modules/ims_qos/cdpeventprocessor.c @@ -210,7 +210,6 @@ void cdp_cb_event_process() { if (p_session_data->subscribed_to_signaling_path_status) { LM_DBG("This is a subscription to signalling bearer session"); - ; //nothing to do here - just wait for AUTH_EV_SERVICE_TERMINATED event } else { LM_DBG("This is a media bearer session session");

10 years, 8 months

git:richard.good/diameter_rx_media: Merge branch 'master' into richard.good /diameter_rx_media

by Richard Good

Module: sip-router Branch: richard.good/diameter_rx_media Commit: e92edd6201d25069bcfc7afb4d62602ce7b79729 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e92edd6… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Wed Oct 9 17:58:36 2013 +0200 Merge branch 'master' into richard.good/diameter_rx_media ---

10 years, 8 months

git:tmp/tm_async_reply_support: Merge branch 'master' into tmp/ tm_async_reply_support

by Richard Good

Module: sip-router Branch: tmp/tm_async_reply_support Commit: ea9ae8a511783843dfe8b4e15892e540c26ab586 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ea9ae8a… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Wed Oct 9 17:57:32 2013 +0200 Merge branch 'master' into tmp/tm_async_reply_support ---

10 years, 8 months

git:master: module/tm: changed log level from WARN to DBG for informational message

by Jason Penton

Module: sip-router Branch: master Commit: a3bddf300ff82b9d811acb5dd6ec2e25f0eab07c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a3bddf3… Author: Jason Penton <jason.penton(a)smilecoms.com> Committer: Jason Penton <jason.penton(a)smilecoms.com> Date: Wed Oct 9 17:55:20 2013 +0200 module/tm: changed log level from WARN to DBG for informational message --- modules/tm/t_reply.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/tm/t_reply.c b/modules/tm/t_reply.c index 351eac3..6b64abc 100644 --- a/modules/tm/t_reply.c +++ b/modules/tm/t_reply.c @@ -910,7 +910,7 @@ void faked_env(struct cell *t, struct sip_msg *msg, int is_async_env) { } else { /*we don't need to restore anything as there was no "environment" prior to continuing (we are in a different process)*/ - LM_WARN("nothing to restore in async continue, useless call\n"); + LOG(L_DBG, "nothing to restore in async continue, useless call\n"); } } }

10 years, 8 months

[tracker] Comment added: registrar: process expired contacts first

by sip-router

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) ---------- Sorry, In this test case I'm using sip:testuser1003@127.0.0.1:6666 as Initial Contact. So this is what you will get on the ddbb as final result and nothing in memory. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=351#comment1112 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.

10 years, 8 months

[tracker] Comment added: registrar: process expired contacts first (Attachment added)

by sip-router

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) ---------- This is a test of this case with master without ddbb but if you enable mysql you will get as result the danieltest@10.15.20.162:52132 contact there. ---------- 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#comment1111 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.

10 years, 8 months

query regarding SER

by Piyush.Bansal＠relianceada.com

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.

10 years, 8 months

git:refs/tags/3.3.5: ChangeLog: updated for v3.3.5

by Victor Seva

Module: sip-router Branch: refs/tags/3.3.5 Commit: 50e14c8d4904d26a04574694aaf5616bf870325f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=50e14c8… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Aug 12 16:58:22 2013 +0200 ChangeLog: updated for v3.3.5 --- ChangeLog | 306 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 306 insertions(+), 0 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=50e…

10 years, 8 months

query related to NOTIFY message size

by Piyush.Bansal＠relianceada.com

Hi there, I have certain queries regarding batch SUBSCRIBE and NOTIFY. I have a user who has 100 buddies in his buddy list. If any of his buddy changes his/her presence status, that user gets a NOTIFY message with presence status of all the 100 buddies. In that case, the message size is exceeding 500 KB. Thats quite a higher value for a UDP packet. Can anybody suggest- 1. If there is any way to restrict the size of the packet. 2. How to ensure that the packet is received correctly by the client. 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.

10 years, 8 months

← Newer
1
...
13
14
15
16
17
18
19
...
26
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2013