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 - Daniel-Constantin Mierla (miconda)
----------
It seems syslog.txt is from another crash, where the process was doing some db related operations. Am I wrong?
In case you do lookup(location) in a failure route, can you try with latest version of git branch 4.0? Few days ago I fixed an issues that could result in a crash.
If not, can you enable one core dump per process and get all the details (log, ngrep, backtrace) for the same crash to be able to compare them?
In case the core dump per process is not enabled, the core dump can be overwritten by another process than the one that actually crashed first.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=348#comment1099
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.
A new Flyspray task has been opened. Details are below.
User who did this - Daniel Tryba (dtryba)
Attached to Project - sip-router
Summary - Invalide tel INVITE crashes 4.0.3
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Somehow a couple of Avaya IPOffices manage to generate a strange INVITE when dialling 00 resulting in a crash of kamailio 4.0.3 (http://deb.kamailio.org/kamailio wheezy):
# kamailio -V
version: kamailio 4.0.3 (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 17:01:35 Aug 19 2013 with gcc 4.7.2
This is reproducable.
Short syslog output:
kamailio[14257]: ERROR: <script>: SIPOUT: tel:+sip.pocos.nl
kamailio[14257]: ERROR: <core> [resolve.c:1728]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: ""
kamailio[14257]: ERROR: tm [ut.h:337]: uri2dst2(): failed to resolve ""
kamailio[14257]: ERROR: tm [t_fwd.c:1534]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches
kamailio[14257]: ERROR: sl [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)
kamailio[14257]: ERROR: <script>: ===== noanswer of dialog [3094:6591]
kamailio[14257]: WARNING: tm [t_lookup.c:1564]: t_unref(): WARNING: script writer didn't release transaction
4926763.717035] kamailio[14257]: segfault at 1b ip 00007f7388ccf107 sp 00007fff43cdd5e0 error 6 in tm.so[7f7388c8e000+86000]
kamailio[14280]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 16
kamailio[14253]: ALERT: <core> [main.c:788]: handle_sigs(): child process 14257 exited by a signal 11
kamailio[14253]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generated
kamailio[14253]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD
kamailio[14279]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14278]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14277]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14276]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14273]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14270]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14269]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14265]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14264]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
kamailio[14262]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
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=348
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#347 - avpops: avp_check() use xavp semantic on first parameter
User who did this - Daniel-Constantin Mierla (miconda)
----------
Ah, I misunderstood, you referred to key as in $xavp(key1=>key2)? Maybe you should add this to docs to make it clear.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=347#comment1098
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#347 - avpops: avp_check() use xavp semantic on first parameter
User who did this - Daniel-Constantin Mierla (miconda)
----------
Can be applied. But I would change in docs that * cannot be used in first key with * cannot be used in the first parameter.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=347#comment1097
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.
Hello,
Does anyone have any ideas about this?
If not it's something I want to try and do before the freeze (any
suggestions as to how would be appreciated) as it will be a nice finishing
touch to the WebSocket/outbound/stun/auth_ephemeral stuff I've worked on
over the last couple of releases.
Thanks,
Peter
On 19 September 2013 21:36, Peter Dunkley <peter.dunkley(a)crocodilertc.net>wrote:
> Hello,
>
> I was wondering if there was an easy way to decode HTTP URLs in
> event_route[xhttp:request]?
>
> For example, it would be good to be able to breakdown a URL like:
> /sip?apiKey=abcdefg&username=1234567890:alice@example.com
> into "path/on/server" ("/sip" in this case) and a set of parameters. For
> the parameters something like the {param.value,name} transformation for SIP
> header parameters would be ideal (which works perfectly for picking values
> out of HTTP Cookie: headers).
>
> I noticed that there is already an {s.urldecode.param} transformation in
> the PV module but I couldn't find any documentation for it in the wiki and
> looking at the code it doesn't appear to do this anyway.
>
> Regards,
>
> Peter
>
>
> --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#347 - avpops: avp_check() use xavp semantic on first parameter
User who did this - Víctor Seva (linuxmaniac)
----------
Update documentation
----------
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=347#comment1096
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.
A new Flyspray task has been opened. Details are below.
User who did this - Víctor Seva (linuxmaniac)
Attached to Project - sip-router
Summary - avpops: avp_check() use xavp semantic on first parameter
Task Type - Bug Report
Category - Module
Status - New
Assigned To - Víctor Seva
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - With this patch now you can use:
avp_check("$xavp(test[1]=>op[*])","re/$xavp(test[1]=>re[*])/g")
No [*] on first key for now.
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=347
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.