sr-users January 2014

sr-users@lists.kamailio.org

93 participants
141 discussions

by Stuart Feeser

My exact problem is described here,<http://lists.kamailio.org/pipermail/sr-users/2013-January/076554.html> but the thread never explains how to solve the problem, *"here" = * http://lists.kamailio.org/pipermail/sr-users/2013-January/076554.html *Description of the issue: * 1. Installing Kamailio 4.1 (latest download) on a *64 bit* Linux Mint version 16 Petra 2. The system compiles cleanly. I have included MAKE and Make Install info below 3. *ims_registrar_pcscf.so will not load* 4. * ims_qos.so will not load* 5. As an FYI, cdp.so successfully loads. I mention this because cdp.so uses semaphore but does not have the sem_post problem. I compared cdp.so with ims_registrar.pcscf.soMakefiles to see if there was something obvious, but no luck. 6. As an FYI, I get the exact same error from a debian apt-get install, so using the canned Debian solution won't work for me either. 7. The config file I used is the one included with the system which I completed with some info just for testing. I have attached it purely as FYI but I don't think that is the issue. *Parts of the syslog messages relevant for issue* Jan 26 22:03:21 PC03 kamailio: ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </lib64/kamailio/modules/ims_qos.so>: /lib64/kamailio/modules/*ims_qos.so:* *undefined symbol: sem_post* Jan 26 22:03:21 PC03 kamailio: ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </lib64/kamailio/modules/ims_registrar_pcscf.so>: /lib64/kamailio/modules/ *ims_registrar_pcscf.so*: *undefined symbol: sem_post* *Relevent section of MAKE* CC (gcc) [M ims_qos.so] cdpeventprocessor.o CC (gcc) [M ims_qos.so] mod.o CC (gcc) [M ims_qos.so] rx_aar.o CC (gcc) [M ims_qos.so] rx_asr.o CC (gcc) [M ims_qos.so] rx_authdata.o CC (gcc) [M ims_qos.so] rx_avp.o CC (gcc) [M ims_qos.so] rx_str.o CC (gcc) [M ims_qos.so] stats.o make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_qos.so] ims_qos.so CC (gcc) [M ims_registrar_pcscf.so] async_reginfo.o CC (gcc) [M ims_registrar_pcscf.so] reg_mod.o CC (gcc) [M ims_registrar_pcscf.so] save.o CC (gcc) [M ims_registrar_pcscf.so] service_routes.o CC (gcc) [M ims_registrar_pcscf.so] ul_callback.o make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_registrar_pcscf.so] ims_registrar_pcscf.so CC (gcc) [M ims_registrar_scscf.so] api.o CC (gcc) [M ims_registrar_scscf.so] common.o CC (gcc) [M ims_registrar_scscf.so] config.o CC (gcc) [M ims_registrar_scscf.so] cxdx_avp.o CC (gcc) [M ims_registrar_scscf.so] cxdx_callbacks.o CC (gcc) [M ims_registrar_scscf.so] cxdx_sar.o CC (gcc) [M ims_registrar_scscf.so] lookup.o CC (gcc) [M ims_registrar_scscf.so] path.o CC (gcc) [M ims_registrar_scscf.so] registrar_notify.o CC (gcc) [M ims_registrar_scscf.so] reg_mod.o CC (gcc) [M ims_registrar_scscf.so] regpv.o CC (gcc) [M ims_registrar_scscf.so] regtime.o CC (gcc) [M ims_registrar_scscf.so] reply.o CC (gcc) [M ims_registrar_scscf.so] rerrno.o CC (gcc) [M ims_registrar_scscf.so] save.o CC (gcc) [M ims_registrar_scscf.so] server_assignment.o CC (gcc) [M ims_registrar_scscf.so] sip_msg.o CC (gcc) [M ims_registrar_scscf.so] stats.o CC (gcc) [M ims_registrar_scscf.so] userdata_parser.o CC (gcc) [M ims_registrar_scscf.so] usrloc_cb.o ---------------------------------------------------------------------------------------------------- *Make Install* LD (gcc) [M ims_icscf.so] ims_icscf.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_icscf.so install -m 755 ims_icscf.so //lib64/kamailio/modules make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_qos.so] ims_qos.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_qos.so install -m 755 ims_qos.so //lib64/kamailio/modules make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_registrar_pcscf.so] ims_registrar_pcscf.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_registrar_pcscf.so install -m 755 ims_registrar_pcscf.so //lib64/kamailio/modules

10 years, 3 months

undefined symbol: sem_post

by Stuart Feeser

My exact problem is described here,<http://lists.kamailio.org/pipermail/sr-users/2013-January/076554.html>but the thread never explains how to solve the problem, *"here" = * http://lists.kamailio.org/pipermail/sr-users/2013-January/076554.html *Description of the issue: * 1. Installing Kamailio 4.1 (latest download) on a *64 bit* Linux Mint version 16 Petra 2. The system compiles cleanly. I have included MAKE and Make Install info below 3. *ims_registrar_pcscf.so will not load* 4. * ims_qos.so will not load* 5. As an FYI, cdp.so successfully loads. I mention this because cdp.so uses semaphore but does not have the sem_post problem. I compared cdp.so with ims_registrar.pcscf.so Makefiles to see if there was something obvious, but no luck. 6. As an FYI, I get the exact same error from a debian apt-get install, so using the canned Debian solution won't work for me either. 7. The config file I used is the one included with the system which I completed with some info just for testing. I have attached it purely as FYI but I don't think that is the issue. *Parts of the syslog messages relevant for issue* Jan 26 22:03:21 PC03 kamailio: ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </lib64/kamailio/modules/ims_qos.so>: /lib64/kamailio/modules/*ims_qos.so:* *undefined symbol: sem_post* Jan 26 22:03:21 PC03 kamailio: ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </lib64/kamailio/modules/ims_registrar_pcscf.so>: /lib64/kamailio/modules/ *ims_registrar_pcscf.so*: *undefined symbol: sem_post* *Relevent section of MAKE* CC (gcc) [M ims_qos.so] cdpeventprocessor.o CC (gcc) [M ims_qos.so] mod.o CC (gcc) [M ims_qos.so] rx_aar.o CC (gcc) [M ims_qos.so] rx_asr.o CC (gcc) [M ims_qos.so] rx_authdata.o CC (gcc) [M ims_qos.so] rx_avp.o CC (gcc) [M ims_qos.so] rx_str.o CC (gcc) [M ims_qos.so] stats.o make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_qos.so] ims_qos.so CC (gcc) [M ims_registrar_pcscf.so] async_reginfo.o CC (gcc) [M ims_registrar_pcscf.so] reg_mod.o CC (gcc) [M ims_registrar_pcscf.so] save.o CC (gcc) [M ims_registrar_pcscf.so] service_routes.o CC (gcc) [M ims_registrar_pcscf.so] ul_callback.o make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_registrar_pcscf.so] ims_registrar_pcscf.so CC (gcc) [M ims_registrar_scscf.so] api.o CC (gcc) [M ims_registrar_scscf.so] common.o CC (gcc) [M ims_registrar_scscf.so] config.o CC (gcc) [M ims_registrar_scscf.so] cxdx_avp.o CC (gcc) [M ims_registrar_scscf.so] cxdx_callbacks.o CC (gcc) [M ims_registrar_scscf.so] cxdx_sar.o CC (gcc) [M ims_registrar_scscf.so] lookup.o CC (gcc) [M ims_registrar_scscf.so] path.o CC (gcc) [M ims_registrar_scscf.so] registrar_notify.o CC (gcc) [M ims_registrar_scscf.so] reg_mod.o CC (gcc) [M ims_registrar_scscf.so] regpv.o CC (gcc) [M ims_registrar_scscf.so] regtime.o CC (gcc) [M ims_registrar_scscf.so] reply.o CC (gcc) [M ims_registrar_scscf.so] rerrno.o CC (gcc) [M ims_registrar_scscf.so] save.o CC (gcc) [M ims_registrar_scscf.so] server_assignment.o CC (gcc) [M ims_registrar_scscf.so] sip_msg.o CC (gcc) [M ims_registrar_scscf.so] stats.o CC (gcc) [M ims_registrar_scscf.so] userdata_parser.o CC (gcc) [M ims_registrar_scscf.so] usrloc_cb.o ---------------------------------------------------------------------------------------------------- *Make Install* LD (gcc) [M ims_icscf.so] ims_icscf.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_icscf.so install -m 755 ims_icscf.so //lib64/kamailio/modules make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_qos.so] ims_qos.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_qos.so install -m 755 ims_qos.so //lib64/kamailio/modules make[2]: `libkcore.so.1.0' is up to date. make[2]: `libkamailio_ims.so.0.1' is up to date. LD (gcc) [M ims_registrar_pcscf.so] ims_registrar_pcscf.so make[2]: Nothing to be done for `install-if-newer'. make[2]: Nothing to be done for `install-if-newer'. touch //lib64/kamailio/modules/ims_registrar_pcscf.so install -m 755 ims_registrar_pcscf.so //lib64/kamailio/modules

10 years, 3 months

alias_db DID regex?

by Pete Ashdown

Is there a way to use regex or Asterisk style numerical patterns in alias_db or any other db routing modules? Compressing a block of a hundred DID numbers to one entry would be really nice.

10 years, 3 months

direct2rupayan@gmail.com has indicated you're a friend. Accept?

by direct2rupayan＠gmail.com

10 years, 3 months

Static forward, reverse proxy

by Diego Woitasen

Hi, I need to configure Kamailio to act as reverse/frontend proxy, with static routing using rtpproxy. It will receive the SIP messages using UDP and must forward the traffic to the backends using TCP. The only IP address that the endpoints must see is the IP address of Kamailio. I've been looking at different examples on the web but I can't found something similar and I can't figure out how to start reading the official docs. If anyone has an example, doc or a hint it will be welcome. Regards, Diego -- Diego Woitasen Linux and Open Source solutions architect at www.vhgroup.net

10 years, 3 months

Re: [SR-Users] Kamailio behind NAT

by John Smith

Hello Klaus, I had already two sockets bound each to two independent physical interfaces. I have added the force_send_socket at each rtpproxy It is necessary to use the cwie / cwei flags in the rtpproxy_manage call? Currently audio does not flow back to the softphones, it gets lost at Kamailio. Thank you for your help > ----- Original Message ----- > From: Klaus Darilion > Sent: 01/23/14 12:26 AM > To: Kamailio (SER) - Users Mailing List > Subject: Re: [SR-Users] Kamailio behind NAT > > Am 21.01.2014 17:33, schrieb John Smith: > > The next test has been to comment out the rtpproxy_manage at NATMANAGE function and to put it both at route[RELAY] and onreply(route) following your post in this list from January 2013:http://lists.sip-router.org/pipermail/sr-users/2013-January/076254.html. > > > > Now the media flows from Phone1 to Kamailio, from Kamailio to Asterisk and back, but it gets stuck at Kamailio. I cannot see it flow towards the public IP of the Phone2. > > > > The force_send_socket you used could be of any use here? > That's what I recommend: > > - use 2 sockets, one for communication with internal nodes, one for > external clients > - in your Kamailio config check the direction of every message: i->e or > e->i (for requests and responses). Depending on the direction set the > proper IP when calling manage_rtpproxy and force the send socket: > > regards > Klaus > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

10 years, 3 months

pv_printf buffer overflow

by Aman Agarwal

I am running Kamailio-4.1.0 and I am getting this error If I try to parse JSON string longer than 1024 characters. ERROR: <core> [pvapi.c:1338]: pv_printf(): no more space for spec value ERROR: <core> [pvapi.c:1347]: pv_printf(): buffer overflow -- increase the buffer size... ERROR: <core> [sr_module.c:1696]: get_str_fparam(): Could not convert the PV-formated string to str ERROR: json [json_funcs.c:42]: json_get_field(): cannot get json string value I searched online for a fix and it was suggested to increase the PV_PRINT_BUF_SIZE in pvar.c. The source code for Kamailio 4.1.0 does not contain this file. I did not find this constant in other files too . Can some please suggest how to increase the buffer size? Thanks

10 years, 3 months

Replicate registration

by Volkan Oransoy

Hi all, I am trying to setup an active-active pair of sip proxies. I have connected two kamailio boxes to the same PostgreSQL database and my usrloc db_mode is 3. I can see the registration data in the database but "ul show" outputs of two device is not same. I think writing registration data to the same db is not enough. I have found a method to replicate the registraiton process. With t_replicate, I synchronize REGISTER requests to both boxes. But I had to disable shared database because of uniqe id validations. route[REGISTRAR] { > if (is_method("REGISTER")) > { > if(isflagset(FLT_NATS)) > { > setbflag(FLB_NATB); > } > if (!save("location")) > sl_reply_error(); > t_replicate("sip:10.1.1.2:5060;transport=udp"); > exit; > } > } My media servers randomly sends calls to SIP proxies. If Media server send the call to the original registrar then the replicated, call initiates normally. But when UA registered in first proxy, and Media server sends the call to the send one, even if second one has UA in location table, call does not initiate. Does anyone have an idea about this kind of an active active setup? Thanks in advance. Best regards, /Volkan

10 years, 3 months

P_usrloc - expired locations

by Helena Garcia-Nieto

Hi All, I am testing the p_usrloc module in order to write the location information of my kamailo server (Kamailio is on version 4.0.2) in two db As first test both DB are on the same machine, as well as the master db. On final version master and one db would probably be on the same machine and the second db on a different one. I have read on the p_usrloc module the following note: The p_usrloc module still has some missing feature, like automatic expiry of contacts and dumping of all users via the fifo cmd. And I can sadly see that the locations are not being deleted automatically after expiring. My users are mobile apps, that are programmed to be always logged in, and reconnecting to sip and IM servers if the devices detects a drop on the connection (bad wi-fi connection), or the user just move between different 3G cells. So the locations are most likely not going to be properly "unregistered" (expire 0) Have anyone found a solution or can give me some advice on how can I force the expired locations to be erased from the db, just as the usrloc module does? Thanks in advanced! Helena

10 years, 3 months

Kamailio with extern Presence and XCAP server

by mohammed alyaseen

Hi all, Since 2 weeks I am trying to get Kamailio presence and xcap servers working. I am testing with RCS clients (native android clients). Somehow the presence server of kamailio doesn't like some subscribe events of RCS for example "Event: xcap-diff;path="resource-lists/users/sip:22222@kamailio.test/index", when RCS sends subscribe with this event, kamailio returns "Bad Event"... Another problem is some AUIDs used by RCS in the HTTP GETs for example ext-resource-lists. Kamailio doesn't support such as AUIDs and replies with not supported auid error.... Now I want to use extern presence and xdms servers, which run on the same virtual machine, where Kamailio is running. What should I do to achieve this? Any advice would be appreciated... Thanks Medo

10 years, 3 months

← Newer
1
2
3
4
5
6
7
8
9
...
15
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 January 2014