sr-users May 2014

sr-users@lists.kamailio.org

96 participants
155 discussions

app_python not able to import from Router

by Örn Arnarson

Hello, I've tried installing kamailio both from deb and from source (4.0.4 in both cases) on Ubuntu server 14.04. In both cases, I'm having problems with importing from the Router module in python, which I presume is made available when invoked from kamailio with the python module loaded. Here's what I see when trying to start kamailio with a python script with "from Router import LM_ERR": May 28 16:34:13 vcr01 kamailio: NOTICE: <core> [sr_module.c:627]: load_module(): /usr/lib/x86_64-linux-gnu/kamailio/modules/app_python.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead May 28 16:34:13 vcr01 /usr/sbin/kamailio[19652]: INFO: rr [../outbound/api.h:49]: ob_load_api(): Failed to import bind_ob May 28 16:34:13 vcr01 /usr/sbin/kamailio[19652]: INFO: rr [rr_mod.c:159]: mod_init(): outbound module not available May 28 16:34:13 vcr01 /usr/sbin/kamailio[19652]: ERROR: app_python [python_support.c:132]: python_handle_exception(): mod_init: Unhandled exception in the Python code:#012Traceback (most recent call last):#012 File "/etc/kamailio/callrouting.py", line 2, in <module>#012 from Router import LM_ERR#012ImportError: cannot import name LM_ERR May 28 16:34:13 vcr01 /usr/sbin/kamailio[19652]: ERROR: <core> [sr_module.c:939]: init_mod(): init_mod(): Error while initializing module app_python (/usr/lib/x86_64-linux-gnu/kamailio/modules/app_python.so) I load the module so: loadmodule "app_python.so" and set the following parameters: modparam("app_python", "script_name", "/etc/kamailio/handler.py") modparam("app_python", "mod_init_function", "mod_init") What am I doing wrong? Am I missing some additional modules from kamailio? handler.py is just the sample python script provided with the package. Any pointers appreciated. Regards, Örn

9 years, 10 months

JSSIP with Kamalio with SIP end points

by Steve Ng

Hi, My users are from a web application using JSSIP. They each have a sip trunk account, which could be from any provider. JSSIP would connect to Kamailio's websocket server passing the SIP trunk credential information and Kamailio will relay it to that specific sip trunk provider? Is there anyway that I could use Kamailio as the middleman? Is it a combination of dispatcher module and websocket module? Thanks! Regards, Steve

9 years, 10 months

drouting failure loop

by Pete Ashdown

I'm trying to get my head around how to do a failure loop in droute through all possible destinations, and if all destinations are exhausted, go to failureroute. Does anyone have an example of this? Without the ability to do a while on (!t_relay()) to determine whether to go to use_next_gw(), I'm not sure how I can. Thanks in advance.

9 years, 10 months

new ngcp-rtpengine release?

by Juha Heinanen

i noticed that there is new entry in ngcp-rtpengine changelog: ngcp-rtpengine (3.3.0.0+0~mr3.4.0.0) unstable; urgency=low does that mean that there is new stable release 3.3? what does ~mr3.4.0.0 mean? -- juha

9 years, 10 months

Reason header body to acc_sip_reason_column

by Juha Heinanen

if response has reason header, i would like to gets its body to acc_sip_reason_column field rather than the reason on the response status line which does not bring any added value. any comments on how to achieve that? -- juha Session Initiation Protocol Status-Line: SIP/2.0 404 Not Found ... Reason: Q.850;cause=88;text="INCOMPATIBLE_DESTINATION"

9 years, 10 months

Use of received=X.X.X.X param in Contact header of REGISTER message

by Luis F Urrea

Hi all, I have an existing Kamailio installation that is handling registrations and NAT traversal for clients. There is one particular build of softphone that sends us a received=X.X.X.X param in its REGISTER message and it seems that the current Kamailio's config in place always uses that address to store the AOR. It happens to be that the client appears to be misbehaving and sending an outdated IP address on that field. My question is where in the NAT traversal functions do I have control over using this param or not. TIA

9 years, 10 months

Problems migrating from rtpproxy/rtoproxy.so to rtpproxy-ng/rtpengine

by LAA

On 05/28/14 13:31, LAA wrote: >>* Hi all, *>> >>* I'm currently running a pilot with kamailio 4.1.3 stable, and I would *>>* like to test WebRTC Capabilities. Websockets Support is runnig OK, and *>>* now I'm trying to deal with calls between WebTRC and legacy softphones. *>>* I have installed rtpengine (as it a replacement for old mediaproxy-ng), *>>* and it is running: *>> >>* rtpengine --table=0 --ip=192.168.0.197 --listen-udp=127.0.0.1:12222 <http://127.0.0.1:12222> * >You need to use the --listen-ng=... option instead of listen-udp for >this to work. >cheers Thanks Richard, of course it works. Regards. Luis. > > > > > >

9 years, 10 months

Kamailio on P2020RDB-PCA

by ashwin

Hi, I tried to compile Kamailio on Freescale P2020RDB-PCA.And I'm getting the following error bison -d -b cfg cfg.y make: *** [cfg.tab.h] Broken Pipe Please give recommendations to solve the error. Thanks -- View this message in context: http://sip-router.1086192.n5.nabble.com/Kamailio-on-P2020RDB-PCA-tp128073.h… Sent from the Users mailing list archive at Nabble.com.

9 years, 10 months

Problems migrating from rtpproxy/rtoproxy.so to rtpproxy-ng/rtpengine

by LAA

Hi all, I'm currently running a pilot with kamailio 4.1.3 stable, and I would like to test WebRTC Capabilities. Websockets Support is runnig OK, and now I'm trying to deal with calls between WebTRC and legacy softphones. I have installed rtpengine (as it a replacement for old mediaproxy-ng), and it is running: rtpengine --table=0 --ip=192.168.0.197 --listen-udp=127.0.0.1:12222 As a first step, I'm trying to migrate the standard NAT handling configuration to the new module. (...) #loadmodule "rtpproxy.so" loadmodule "rtpproxy-ng.so" (...) #modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7624") modparam("rtpproxy-ng", "rtpproxy_sock", "udp:127.0.0.1:12222") NAT hanling is not working, and I catched this message from /var/log/syslog May 28 18:55:35 kamailio rtpengine[2474]: Failed to properly parse UDP command line '4547_3 d7:command4:pinge' from 127.0.0.1:60874, using fallback RE May 28 18:55:35 kamailio rtpengine[2474]: Failed to properly parse UDP command line '4545_4 d7:command4:pinge' from 127.0.0.1:57236, using fallback RE And from Kamailio's log: May 28 19:23:47 kamailio /usr/local/sbin/kamailio[4868]: ERROR: rtpproxy-ng [rtpproxy.c:1425]: rtpp_test(): proxy responded with invalid response May 28 19:23:47 kamailio /usr/local/sbin/kamailio[4869]: ERROR: rtpproxy-ng [rtpproxy.c:1425]: rtpp_test(): proxy responded with invalid response Is rtpproxy-ng module compatible with rtpengine? Best regards Luis.

9 years, 10 months

Interpreting messages in log

by Gilbert T. Gutierrez, Jr.

Can someone help me interpret what I a seeing in my log? Gilbert May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=521 a=5 n=route May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=665 a=16 n=if May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=625 a=24 n=has_totag May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=525 a=24 n=t_check_trans May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=528 a=5 n=route May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=797 a=16 n=if May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=784 a=25 n=is_method May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=792 a=16 n=if May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=787 a=27 n=auth_check May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=788 a=26 n=auth_challenge May 28 09:53:09 faxsvr /usr/sbin/kamailio[1811]: ERROR: *** cfgtrace: c=[//etc/kamailio/kamailio.cfg] l=789 a=2 n=exit

9 years, 10 months

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

Jump to page:

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 May 2014