sr-dev June 2014

sr-dev@lists.kamailio.org

21 participants
153 discussions

[tracker] Comment added: route name in action struct (Attachment added)
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#441 - route name in action struct User who did this - Víctor Seva (linuxmaniac) ---------- Something like this, doesn't it? ---------- 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=441#comment1522 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.

1 0

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Nuno Miguel Reis (nmreis) ---------- Hi Daniel! The last attachment from Monday, 09 June 2014, 12:05 GMT+1 named kamailio.log.tar.bz2 was named that way by me, by mistake, but it really has the full dump output you have requested inside. Moreover I agree with you that the crash could be related with the way I'm using presence. I've sent an email some days ago to the mailing list asking about some errors regarding persistence of presence status in database. I didn't have any reply's. I'm pretty sure i still have some mistakes on the way I'm dealing with presence right now but, kamailio shouldn't crash even if it is looping in a PUBLISH on 127.0.0.1 by some mistake right? Looking forward to hear from you. Best Regards, Nuno. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1521 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.

1 0

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Daniel-Constantin Mierla (miconda) ---------- The last bz2 file you attached here is a syslog file, not the full dump with the extra info. The transaction from the second file attached here shows a PUBLISH request, not an INVITE. The PUBLISH is looping locally a lot, as there seems to be a lot of VIA headers with 127.0.0.1. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1520 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.

1 0

Fwd: Create multiple profiles using dialog module
by Rahul MathuR 09 Jun '14

09 Jun '14

*Hello,* *Please accept my apologies for asking a simple question - Is there any example which shows how can I create the dialog profile **value based on the SIP domain or SIP Server IP (IP like- 112.23.134.5). I** need to control many SIP Server IPs with limited channels to each with my** Kamailio Proxy.* *I am a newbie to kamailio world.* *-- Warm Regds.MathuRahul*

4 21

[tracker] Comment added: route name in action struct
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#441 - route name in action struct User who did this - Daniel-Constantin Mierla (miconda) ---------- First patch is ok, but the second has hardcoded only route for everything but failure route. You can add a function like: <code> char* get_current_route_name() { switch(route_type) { case REQUEST_ROUTE: return "route"; case FAILURE_ROUTE: return "failure_route"; case BRANCH_ROUTE: ... default: return "unknown"; } } </code> You can see all the relevant route types in route.h file from core. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=441#comment1519 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.

1 0

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Nuno Miguel Reis (nmreis) ---------- One more thing: You probably already noticed but I've replaced all the visible IP addresses besides 127.0.0.1 with '<__HIDDEN__IP__ADDR__>'. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1518 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.

1 0

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available (Attachment added)
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Nuno Miguel Reis (nmreis) ---------- Hi Daniel. Yes the 2 are from the same dump. Even so i'm reattaching a new full dump with the extra info corresponding to the second file all in one. Hope that helps. BR, Nuno. ---------- 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=440#comment1517 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.

1 0

[tracker] Comment added: CRASH: segmentation fault after INVITE
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#439 - CRASH: segmentation fault after INVITE User who did this - Nuno Miguel Reis (nmreis) ---------- Hi will try that later on. I'll let you know the outcome as soon as possible. Thanks. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=439#comment1516 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.

1 0

[tracker] Comment added: route name in action struct (Attachment added)
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#441 - route name in action struct User who did this - Víctor Seva (linuxmaniac) ---------- Removed \0 in first patch. using route=[X] or failure_route=[Y] in the output. ---------- 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=441#comment1515 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.

1 0

[tracker] Comment added: CRASH: segmentation fault after INVITE
by sip-router 09 Jun '14

09 Jun '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#439 - CRASH: segmentation fault after INVITE User who did this - Daniel-Constantin Mierla (miconda) ---------- Can you grab the log messages via syslog? Because it includes the pid in the message and it is possible to see what the process did before crashing. Now it is impossible to figure out what the process that crashed did. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=439#comment1514 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.

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2014