sr-users January 2015

sr-users@lists.kamailio.org

94 participants
134 discussions

Double attempt to record-route, RR param not added
by ron.kamailio＠mcleodnet.com 03 Jan '15

03 Jan '15

I have been away from Kamailio for a while and starting working on a project where it would be a good fit. I am having a problem when I try to add a Record-Route header with a tag. I see a message in the log indicating that a Double attempt to record-route was made, and the tag that I specified (;rtpproxy=yes), does not get included. I have checked-over the scripts defined in the kamailio.cfg, and I am very sure that record_route() does not get called more than once. Also, the log only shows record_route being execute a single time. Can anyone suggest how I can troubleshoot this problem further? 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=206 a=57 n=set_adv_addr 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=207 a=58 n=set_adv_port 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=208 a=25 n=record_route_preset 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=209 a=62 n=force_send_socket 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=210 a=2 n=exit 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=235 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=231 a=41 n=isflagset 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=232 a=25 n=add_rr_param 5(32087) DEBUG: rr [record.c:899]: add_rr_param(): rr_param_buf=<;rtpproxy=yes> 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=235 a=25 n=xlog 5(32087) ERROR: <script>: new ru: sip:19999009595@192.168.100.52:5080 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=236 a=24 n=record_route 5(32087) ERROR: rr [rr_mod.c:262]: w_record_route(): Double attempt to record-route 5(32087) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[//etc/kamailio/kamailio.cfg] l=237 a=5 n=route 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=247 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=244 a=25 n=is_method 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=246 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=245 a=25 n=t_is_set 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=245 a=25 n=t_on_branch 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=250 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=247 a=25 n=is_method 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=249 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=248 a=25 n=t_is_set 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=248 a=25 n=t_on_reply 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=254 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=250 a=25 n=is_method 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=252 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=251 a=25 n=t_is_set 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=251 a=25 n=t_on_failure 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=257 a=16 n=if 5(32087) ERROR: *** cfgtrace:request_route=[RELAY] c=[//etc/kamailio/kamailio.cfg] l=254 a=24 n=t_relay The complete log file, script files, and SIP trace can be found here: http://www.siplabs.net/tracebin/record-route/kamailio-log.txt http://www.siplabs.net/tracebin/record-route/kamailio.cfg http://www.siplabs.net/tracebin/record-route/bgcf-local.cfg http://www.siplabs.net/tracebin/record-route/sip-trace.txt Thanks and Happy New Year, Ron

2 3

presence - Error deleting subscription
by Jan Gaida 03 Jan '15

03 Jan '15

Hello, We are upgrading our servers to Kamailio 4.2 and we see a lot of error messages "Failed to delete subscription from memory". Scenario: This happens every time there is a Notify Timeout (408) and Kamailio tries to delete the subscription. Consequences: I don't know whether the delete fails because the entry did never exist, was already deleted or because the comparison (to_tag, callid or from_tag) is incorrect. It would be nice to at least have some details in the log message. I have not noticed any consequences to general functionality. I suspect the commit (74d73953327ad7702922b27ba37c71e3283659c3) to be responsible for this error because it introduced some extra checks on deletion. Does this happen to anybody else? What may be configured incorrectly on our system? Kind regards *Jan **Gaida* Ingeniero Desarrollo Software C/ Marconi 3 (PTM) 28760 Tres Cantos Spain jan.gaida(a)grupoamper.com | www.grupoamper.com -- This message and any attachments are intended only for the use of the individual to whom they are addressed and it may contain information that is privileged or confidential. If you have received this communication by mistake, please notify us immediately by e-mail or telephone.The storage, recording, use or disclosure of this e-mail and its attachments by anyone other than the intended recipient is strictly prohibited. This message has been verified using antivirus software; however, the sender is not responsible for any damage to hardware or software resulting from the presence of any virus. Este mensaje y cualquier anexo son exclusivamente para la persona a quien van dirigidos y pueden contener información privilegiada o confidencial. Si usted ha recibido esta comunicación por error, le agradecemos notificarlo de inmediato por esta misma vía o por teléfono. Está prohibida su retención, grabación, utilización o divulgación con cualquier propósito. Este mensaje ha sido verificado con software antivirus; sin embargo, el remitente no se hace responsable en caso de que en éste o en los archivos adjuntos haya presencia de algún virus que pueda generar daños en los equipos o programas del destinatario.

2 4

t_suspend()/t_continue() problem
by Dmytro Bogovych 02 Jan '15

02 Jan '15

Greetings. I'm trying to adopt kamailio to handle incoming calls / generate push notifications for softphone running on Windows Phone 8. Starting point was this publication http://www.kamailio.org/events/2014-KamailioWorld/day2/26-Daniel-Constantin… I adopted the script from publication a bit - now notification URI is extracted from REGISTER messages + INVITE transactions are not resuming when unregistering happens. However it does not work for me yet. I see the suspicious output in kamailio log when softphone registers after incoming push notification. Please ignore ERROR: level name - it is just dirty logging call, not real problem. Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: ERROR: <script>: resuming trasaction [40951:63820139] dbogovych (40951:63820139) Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: tm [t_lookup.c:1635]: t_lookup_ident(): DEBUG: t_lookup_ident: transaction found Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:181]: lookup(): contact for [dbogovych] found by address Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 90211984 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 91061218 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 91229062 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 90750343 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 87612750 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: registrar [lookup.c:327]: lookup(): instance is 91841578 Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction Can this "script writer didn't release transaction" be the problem? Thank you :)

1 2

Happy New Year!
by Daniel-Constantin Mierla 01 Jan '15

01 Jan '15

A very dynamic 2014 for Kamailio has reached its end! Thank you everyone for contributing to it! Looking forward to 2015, a lot of new features in Kamailio and new contributors! I wish a healthy and prosperous year to all Kamailio friends, hoping to meet many of you at Kamailio World Conference and other events around the globe! Happy New Year! Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

4 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2015