sr-users September 2015

sr-users@lists.kamailio.org

82 participants
126 discussions

ERROR: mediaproxy [mediaproxy.c:1978] #347
by Ngoc 02 Oct '15

02 Oct '15

Hello supporter, I took a look kamailio and get the error: Sep 29 11:28:37 lvps46-163-74-198 /usr/local/sbin/kamailio[1738]: ERROR: mediaproxy [mediaproxy.c:1978]: EngageMediaProxy(): engage_media_proxy requires the dialog module to be loaded and configured. How to resolved this problem, please help me. Regards, --------------------------- Dinh Hong Ngoc Technical Lead Edge-works Software Co.,ltd Hall 5, Quang Trung Software City, Tan Chanh Hiep Ward, Dist. 12, Ho Chi Minh City, Vietnam. Email: ngoc.dinh(a)edge-works.net Phone: +84 8 54371075 | Mobile: +84 909 911 406 Site: http://www.edge-works.net

2 1

blf problem
by huseyin kalyoncu 01 Oct '15

01 Oct '15

Hi I am trying to implement BLF functionality as described in http://kb.asipto.com/kamailio:presence:k43-blf. I am using the same conf with the one in the tutorial except that i am using postgres database instead of mysql. The problem is BLF is not working with this config (presence server and proxy server are in the same kamailio with same IP). But when I separate presence server from proxy server (2 different kamilio boxes with different IPs) BLF working perfect. i can see PUBLISH & NOTIFY messages in the tcpdump output with the working configuration. But i can not see any PUBLISH messages in the tcpdump output with the original config (one with presence and proxy servers are same). My question in the normal working environment (when BLF working perfectly); should i see PUBLISH and NOTIFY messages in the tcpdump output when the presence and proxy servers are the same? thanks Huseyin

2 9

SIP and conntrackd experience?
by Grant Bagdasarian 01 Oct '15

01 Oct '15

Hello, Does anyone have experience with SIP and conntrackd? Our media and signaling is separated. Does this work for VPN connections where SIP is sent over the VPN but the media over public internet? Thanks, Grant

2 5

modifying $fu / $fU (R-URI From)
by Sven Neuhaus 01 Oct '15

01 Oct '15

Hello, I'm having some troubles with modifying $fU in my kamailio.cfg. The following line appears to have no effect: $fU = $(fU{s.substr,2,0}); I would expect it to remove the first two leading characters from $fU. Has anyone else seen this? I have the same issue with modifying $fu. We're not using the uac module. And we're using the latest stable version of Kamailio. Thanks, -Sven

4 4

out of memory Error
by Yasin CANER 01 Oct '15

01 Oct '15

3 15

Crash kamailio 4.3.1
by Thibault Gueslin 30 Sep '15

30 Sep '15

After upgrading to kamailio 4.3.1 and modifying the config, I get this crash very often: ... CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 21 ALERT: <core> [main.c:728]: handle_sigs(): child process 9341 exited by a signal 11 ALERT: <core> [main.c:731]: handle_sigs(): core was not generated INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLD INFO: <core> [main.c:794]: sig_usr(): signal 15 received INFO: <core> [main.c:794]: sig_usr(): signal 15 received INFO: <core> [main.c:794]: sig_usr(): signal 15 received ... Is it known ? or may be related to my config ? Thank you Thibault

3 23

db_text and caching/reloading
by Asgaroth 30 Sep '15

30 Sep '15

Hi, I am busy testing the db_text module for some modules who's configuration does not change that often. If I set the db_mode for db_text to 0 (caching), it appears that if I modify the file directly (in this case the address dbtext file) and then issue a "kamctl address reload" the updated contents are *not* reloaded. However, if I set db_mode to 1, then the contents of the db_text file automatically reload when I change it on the file system. Is it possible to run db_text in caching mode but to also force a reload if I manually update the underlying database file? Additionally, in kamctlrc, I had to add the following variable: DBTEXT_PATH="/etc/kamailio/db_text" Whereas the original example for db_text path in kamctlrc is as follows: # database path used by dbtext, db_berkeley or sqlite #DB_PATH="/etc/kamailio/db_text" Is this just a typo in the kamctlrc distribution or is the variable meant to be DB_PATH or DBTEXT_PATH? Thanks

1 3

ACK and BYE are forwarded statelessly (failed to parse Route HF)
by Miroslav Dunaev 30 Sep '15

30 Sep '15

Hello everyone, I have a setup where kamailio acts as UAC to a SIP provider. Kamailio is also configured to pass all incoming calls to an Asterisk. Here is a diagram: Phone<-->Asterisk(10.10.11.232)<--->(PRIV:10.10.11.238)Kamailio(PUB:44.44.44.148)<--->(194.213.29.92)SIP-provider. When a call comes in from the SIP-provider, it gets all the way to the phone. But when the SIP-provider sends BYE or ACK (during hungup event or 200OK/SDP asterisk response.). I get this errors in my kamailio log: siputils [checks.c:100]: has_totag(): totag found <core> [parser/parse_rr.c:49]: do_parse_rr_body(): parse_rr_body(): No body for record-route rr [loose.c:106]: find_first_route(): failed to parse Route HF rr [loose.c:929]: loose_route(): There is no Route HF tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffffffffffff tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=10101, isACK=1 tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed ..... .... .... siputils [checks.c:100]: has_totag(): totag found tm [t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=0xffffffffffffffff tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=10101, isACK=1 tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found tm [t_funcs.c:279]: t_relay_to(): SER: forwarding ACK statelessly here is the link to: kamailio.cfg, ngrep -i any capture, debug_level6 log: http://labmir.com/kamailio/ Looking at the SIP ACK that comes from SIP provider I can see that they use strict routing. (i.e. TO field is set to kamailio's public IP that is next hop to them). Maybe I am wrong to judge that its not loose routing just because of the TO field. Anyways, because of (failed to parse Route HF) error, ACKs and BYEs are forwarded by kamailio statelessly, as a result kamailio uses wrong interface to forward them (SIP_dailog.txt line:233) and therefore asterisk never sees ACKs or BYEs. How can I make kamailio recognize ACKs and BYEs belonging to a dialog and pass them statefully through the right interface? It is worth to mention that I use exactly the same config with a different SIP-provider (which is peered to our PUB IP not registered through UAC like in this case) and it works flawlessly. Thank you, Mir

2 1

Anybody in Beijing interested in Kamailio related project cooperation ?
by Thierry Luo 29 Sep '15

29 Sep '15

很报歉通过这个邮件列表打扰大家。我们是一个创业团队，刚刚拿到投资，正在组建核心团队，现需要一位在OpenIMSCore （或Kamailio/OpenSIPS）方面有经验的C/C++开发工程师加盟，待遇优厚，期权可谈，职位在北京。请有意者速与 luoyongheng(a)nane.cn <mailto:luoyongheng@nane.cn> 联系。谢谢！打扰见谅！罗

1 0

Best practices for troubleshooting deadlocks?
by Alex Balashov 29 Sep '15

29 Sep '15

Hello, Very occasionally, we encounter what appear to be deadlocks in all UDP receiver threads. All Kamailio processes are running, but no SIP messages are being processed. On one of our high-volume installation, this happens extremely infrequently -- maybe once every month or two. On these occasions, the operator restarts the proxy before we get a chance to go in and figure out what's going on. So, I'm trying to provide the operator with a procedure to execute prior to restarting the proxy on these occasions, so that we can see a snapshot of where the receiver threads are stuck. As far as I can tell, unless Kamailio itself segfaults, there's no specific PID that one can attach GDB to in order to get an overhead snapshot of all the child processes. Here's what I came up with: --------------------------------------------- #!/bin/bash kamcmd -s /tmp/kamailio_ctl ps > thread_log.txt echo >> thread_log.txt while read PID; do gdb --pid=$PID<<EOF>>thread_log.txt set print elements 0 thread apply all bt full generate-core-file detach EOF done < <(kamcmd -s /tmp/kamailio_ctl ps | grep 'udp receiver' | awk '{print $1}') --------------------------------------------- As far as I can tell, this should give me the most ample visibility into the state of the threads, with further core dumps to inspect if follow-up is needed. Hopefully this will result in some fixes back to the project. However, if there are any other suggestions for information to grab in such a scenario, I'm all ears. Thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

← Newer
1
2
3
4
5
6
7
...
13
Older →

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 September 2015