sr-dev July 2014

sr-dev@lists.kamailio.org

25 participants
140 discussions

[tracker] Comment added: sca_call_info_update() function for 180 responses

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#446 - sca_call_info_update() function for 180 responses User who did this - Jorj Bauer (jorj) ---------- Confirmed working, tested with Polycom OS 3.3.4 and 4.0.6 - no adverse affects found against 3.3.4. I would trim the patch - remove lines 1075-1077 of sca_call_info.c: - state = SCA_APPEARANCE_STATE_ALERTING; - break; - and let it fall through to 183. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=446#comment1546 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, 4 months

rtpengine SDP duplication

by Alex Balashov

Hello, I'm running the latest Kamailio 4.1 branch and rtpengine:master:15640991d7fc9d398749f77460b821296cccdcb6, and am running into a curious issue where the SDP body is duplicated (included twice) on a second branch. The scenario is that call goes out on branch #1 and an rtpproxy_offer("ow-") is made. That branch fails with a 503 and another branch goes out with the same offer to a different destination. The original SDP offer on branch #1: v=0 o=Sansay-VSXi 188 1 IN IP4 rtpengine s=Session Controller c=IN IP4 rtpengine t=0 0 m=audio 32816 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv a=rtcp:32817 The SDP offer on branch #2 ends up being: v=0 o=Sansay-VSXi 188 1 IN IP4 rtpengine s=Session Controller c=IN IP4 rtpengine t=0 0 m=audio 32816 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv a=rtcp:32817 v=0 o=Sansay-VSXi 188 1 IN IP4 rtpengine s=Session Controller c=IN IP4 rtpengine t=0 0 m=audio 32816 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv a=rtcp:32817 Interestingly enough, this seems to be premeditated, because on the first one, the Content-Length is 237, and on the second, 434. So, something clearly thinks that this is an appropriate thing to do. If it makes a difference, I'm using two rtpengines RR'd in a set. I am unable to reproduce this in my development environment and am unsure as to whether it's something that happens in all circumstances where there is such failover, or only intermittently. Still, is there any reason why it could be? Thanks! -- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ Please be kind to the English language: http://www.entrepreneur.com/article/232906

10 years, 4 months

[tracker] Comment added: CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#450 - CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route User who did this - Guillaume Bour (gbour) ---------- Thank you Carlos, No, I do not have git write access ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=450#comment1545 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, 4 months

[tracker] Comment added: CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#450 - CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route User who did this - Carlos Ruiz Diaz (caruizdiaz) ---------- Hi, the patch looks good. Do you have write access to the repo? I will try it myself later today or possibly tomorrow, and push it to master in case you can't do it. Thanks for you contribution :). ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=450#comment1544 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, 4 months

[tracker] Task opened: CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route (Attachment added)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Guillaume Bour (gbour) Attached to Project - sip-router Summary - CNXCC: use of pseudo-variables in *cnxcc:call-shutdown* event route Task Type - Improvement Category - Module Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - By adding real from and to headers in built fake SIP message when executing *cnxcc:call-shutdown* event route, it allows the use of pseudo-variables such as $fU or $tU, as well as dialog variables. i.e: <code> event_route[cnxcc:call-shutdown] { xlog("L_INFO", "cnxcc [$ci]: $fU is out of credit ($dlg_var(cnxcc_start))\n"); } </code> One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=450 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, 4 months

[tracker] Comment added: CRASH: Program terminated with signal 6, Aborted. (Attachment added)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#449 - CRASH: Program terminated with signal 6, Aborted. User who did this - Nuno Miguel Reis (nmreis) ---------- Hi Daniel. Yes, there were some hints in the log file. Please take a look at the attached log file. The PID is between square brackets after the timestamp. Look for timestamp: '20140708 10:49:57.074009'. That should be the cause. Thanks. ---------- One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=449#comment1543 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, 4 months

[tracker] Comment added: usrloc driver error on query: Duplicate entry 'XXXXXXXXXXXX' for key 'ruid_idx'

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#448 - usrloc driver error on query: Duplicate entry 'XXXXXXXXXXXX' for key 'ruid_idx' User who did this - Savolainen Dmitri (sdi) ---------- i have tested of course. before reboot user 1111(a)sip.erinaco.ru exists <code> mysql>select * from location where username='1111' and domain='sip.erinaco.ru' \G *************************** 1. row *************************** id: 112154 ruid: ulcx-53b65903-dec-1 username: 1111 domain: sip.erinaco.ru contact: sip:1111@192.168.10.100 received: NULL path: NULL expires: 1970-01-01 03:00:00 q: 1.00 callid: dfjrewr12386fd6-343(a)kamailio.mi cseq: 1 last_modified: 1970-01-01 03:00:00 flags: 0 cflags: 0 user_agent: SIP Router MI Server socket: NULL methods: NULL instance: NULL reg_id: 0 1 row in set (0.00 sec) </code> [snen@sw4]# ./kamctl restart [snen@sw4]# ./kamctl ul add '1111(a)sip.erinaco.ru' 'sip:1111@192.168.10.100' let's have a look at kamailio log: Jul 11 11:55:58 sw4 ./kamailio[28446]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Duplicate entry 'ulcx-53b65903-dec-1' for key 'ruid_idx' Jul 11 11:57:58 sw4 ./kamailio[28446]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Duplicate entry 'ulcx-53b65903-dec-1' for key 'ruid_idx' Jul 11 11:59:58 sw4 ./kamailio[28446]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Duplicate entry 'ulcx-53b65903-dec-1' for key 'ruid_idx' let's have a look at mysql query log: <code> 1453 Query update location set expires='1970-01-01 03:00:00',q=1.00 ,cseq=1,flags=0,cflags=0,user_agent='SIP Router MI Server',received=NULL,path=NULL,socket=NULL,methods=NULL,last_modified='1970-01-01 03:00:00',callid='dfjrewr12386fd6-343(a)kamailio.mi',instance=NULL,reg_id=0,contact='sip:1111@192.168.10.100' where ruid='ulcx-53b65903-dec-1' 1453 Query insert into location (username,contact,expires,q,callid,cseq,flags,cflags,user_agent,received,path,socket,methods,last_modified,ruid,instance,reg_id,domain ) values ('1111','sip:1111@192.168.10.100','1970-01-01 03:00:00',1.00 ,'dfjrewr12386fd6-343(a)kamailio.mi',1,0,0,'SIP Router MI Server',NULL,NULL,NULL,NULL,'1970-01-01 03:00:00','ulcx-53b65903-dec-1',NULL,0,'sip.erinaco.ru') </code> now, let's update again (second update after reboot): [snen@sw4]# ./kamctl ul add '1111(a)sip.erinaco.ru' 'sip:1111@192.168.10.100' and look at query log <code> 140711 12:13:58 1453 Query update location set expires='1970-01-01 03:00:00',q=1.00 ,cseq=2,flags=0,cflags=0,user_agent='SIP Router MI Server',received=NULL,path=NULL,socket=NULL,methods=NULL,last_modified='1970-01-01 03:00:00',callid='dfjrewr12386fd6-343(a)kamailio.mi',instance=NULL,reg_id=0,contact='sip:1111@192.168.10.100' where ruid='ulcx-53b65903-dec-1' </code> so cseq incremented after second update only, and the callid is the same ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=448#comment1542 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, 4 months

[tracker] Comment added: CRASH: Program terminated with signal 6, Aborted.

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#449 - CRASH: Program terminated with signal 6, Aborted. User who did this - Daniel-Constantin Mierla (miconda) ---------- Were there any error messages in the syslog? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=449#comment1541 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, 4 months

[tracker] Task closed: modules/tmx: t_is_failure_route() code or documentation is wrong

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#445 - modules/tmx: t_is_failure_route() code or documentation is wrong User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Not a bug Additional comments about closing: If still considered an issue, re-open with further details. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=445 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, 4 months

[tracker] Comment added: usrloc driver error on query: Duplicate entry 'XXXXXXXXXXXX' for key 'ruid_idx'

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#448 - usrloc driver error on query: Duplicate entry 'XXXXXXXXXXXX' for key 'ruid_idx' User who did this - Daniel-Constantin Mierla (miconda) ---------- After reboot there is a different call-id (because is randomly generated now), so it should be ok. Have you tested and get the error after reboot? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=448#comment1540 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, 4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev July 2014