sr-users March 2015

sr-users@lists.kamailio.org

88 participants
151 discussions

evapi_relay some problems
by dolphin 28 Mar '15

28 Mar '15

Hello, I test the evapi modules function , but not full operation ,only receive not send to client I capture the important setup parameters are as follows: debug=3 loadmodule "evapi.so" #----- evapi params ----- # modparam("evapi", "bind_addr", "0.0.0.0:8448") modparam("evapi", "netstring_format", 0) modparam("evapi", "workers", 4) event_route[evapi:connection-new] { evapi_relay("{ \"event\": \"test\",\n \"data\": { \"fU\": \"fU\" }\n}"); xlog("L_WARN", "new connection from $evapi(srcaddr):$evapi(srcport)\n"); } scene : One client connected kamailio server x.x.x.x:8448 use nc tools , I get garbled , kamailioserver not sent to me client , Because this is the right format to display josn ? sh-4.2# nc -n x.x.x.x 8448 ; øX±š^C any suggestions or missing something ? my syslog : Mar 28 14:31:37 SIP /home/pkg/kamailio-4.2.3/sbin/kamailio[297164]: DEBUG: evapi [evapi_dispatch.c:385]: evapi_accept_client(): new connection - pos[0] from: [x.x.x.x:56215] Mar 28 14:31:37 SIP /home/pkg/kamailio-4.2.3/sbin/kamailio[297164]: DEBUG: evapi [evapi_dispatch.c:531]: evapi_relay(): relaying event data [{ "event": "test",#012 "data": { "fU": "fU" }#012}] Mar 28 14:31:37 SIP /home/pkg/kamailio-4.2.3/sbin/kamailio[297164]: DEBUG: evapi [evapi_dispatch.c:561]: evapi_relay(): sent [0x7f939ab158f8] [{ "event": "test",#012 "data": { "fU": "fU" }#012}] (44) Mar 28 14:31:37 SIP /home/pkg/kamailio-4.2.3/sbin/kamailio[297164]: WARNING: <script>: new connection from x.x.x.x:56215 kamailio server : root@SIP:/etc/init.d# dpkg -l | grep libev-dev ii libev-dev 1:4.11-1 amd64 static library, header files, and docs for libev root@SIP:/etc/init.d# uname -a Linux SIP 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux root@SIP:/home/pkg/kamailio-4.2.3/sbin# ./kamailio -V version: kamailio 4.2.3 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 15:13:09 Mar 27 2015 with gcc 4.7.2 download : http://www.kamailio.org/pub/kamailio/latest/src/kamailio-4.2.3_src.tar.gz

1 0

Routing PSTN calls from Asterisk through Kamailio to UAC & loose_route
by Anthony Messina 27 Mar '15

27 Mar '15

I've been working on integration of Asterisk and Kamailio, currently on the same host with different ports, and have come across a problem with calls that originate from the Asterisk side (PSTN/DAHDI) and route through Kamailio to a SIP UAC. In short, when the SIP UAC (10.1.1.9) sends the BYE, loose_route() is returning -1 and the BYE is routed back to Kamailio (10.1.1.1:5060) instead of Asterisk (10.1.1.1:5080). I am using the stock WITHINDLG route configuration. RR module settings are as follows: modparam("rr", "enable_full_lr", 1) modparam("rr", "append_fromtag", 1) The BYE from the SIP UAC contains the following Route header which only contains the contents of Kamailio's Record-Route header. I have attached the full sip trace for review as well. Route: <sip:10.1.1.1;lr=on;ftag=2400d939-de0b-4456-9e01-f9a3302f3e25;nat=yes>. What would be the best method to resolve this issue in either Asterisk or Kamailio? Should I manually add a Record-Route header for the Asterisk host:port to Kamailio config? Is there something to be done in Asterisk? Thanks. -A -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

2 2

Kamailio - Used By Directory
by Daniel-Constantin Mierla 27 Mar '15

27 Mar '15

Hello, in order to facilitate easier interaction and updates, references (http://www.kamailio.org/w/references/) and some of the business use cases already listed on kamailio.org are in the process of being moved to a new page: - http://www.kamailio.org/w/used-by/ This offers now the possibility to submit new entries without the interaction with Kamailio admins that could lead to delays. The form is available at: - http://www.kamailio.org/w/used-by-form/ The goals is to show where Kamailio is used as well as increase the visibility of the products, solutions and services offered by the Kamailio community. Anyone is welcome to add own references. Besides a spambot protection of the form, we rely for now on the good manners of human nature, if you notice anything inadequate there, please report to be corrected. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 0

tsilo module
by Alex Balashov 27 Mar '15

27 Mar '15

Hello, I don't understand the tsilo module. What is the practical use case for it? Thanks, -- 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 3

Kamailio BLF Issue TCP vs UDP
by Fred Posner 27 Mar '15

27 Mar '15

Greetings all: Having a weird issue with BLF relay from Kamailio <-> FreeSWITCH on the EC2 network. Set-up: Natted Client <-> Natted Kamailio <-> Natted FreeSWITCH Kamailio has a public advertised IP (Amazon Cloud) and sends to FreeSWITCH's public IP (Amazon Cloud). Clients register to Kamailio and the registration sent to FreeSWITCH (via uac). What works: When a client registers to kamailio via UDP, all works beautifully. What doesn't work: When a client registers to kamailio via TCP, a NOTIFY is sent with almost no information. Example of UDP traffic: U 2015/03/26 22:12:30.483767 FREESWITCH_IPADDR:5060 -> KAMAILIO_NAT_IPADDR:5060 NOTIFY sip:3000@CLIENT_PUBLIC_IPADDR:42477;line=51w5wsns SIP/2.0. Via: SIP/2.0/UDP FREESWITCH_IPADDR;rport;branch=z9hG4bKv7X88FmKg04UF. Route: <sip:KAMAILIO_PUBLIC_IPADDR>;lr=on;ftag=xew5nmpr9q;nat=yes. Record-Route: <sip:KAMAILIO_PUBLIC_IPADDR>;lr=on;ftag=xew5nmpr9q;nat=yes. Max-Forwards: 70. From: <sip:3000@CLIENT_DOMAIN;user=phone>;tag=YF4HMSQNlOOt. To: <sip:3000@CLIENT_DOMAIN>;tag=xew5nmpr9q. Call-ID: 3134323734303730333531303039-ji1sw7gyd7uj. CSeq: 366877453 NOTIFY. Contact: <sip:3000@FREESWITCH_IPADDR:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.18+git~20150312T185523Z~4eed221b69~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Event: dialog. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Subscription-State: active;expires=2686. Content-Type: application/dialog-info+xml. Content-Length: 546. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="14" state="full" entity="sip:3000@CLIENT_DOMAIN"> <dialog id="312b3bee-d405-11e4-a8b6-41b65d0bd045" direction="initiator"> <state>confirmed</state> <local> <identity display="3000">sip:3000@CLIENT_DOMAIN</identity> <target uri="sip:3000@CLIENT_DOMAIN"> <param pname="+sip.rendering" pvalue="yes"/> </target> </local> <remote> <identity display="*98">sip:*98@CLIENT_DOMAIN</identity> <target uri="sip:**3000@CLIENT_DOMAIN"/> </remote> </dialog> </dialog-info> U 2015/03/26 22:12:30.483877 KAMAILIO_NAT_IPADDR:5060 -> CLIENT_PUBLIC_IPADDR:42477 NOTIFY sip:3000@CLIENT_PUBLIC_IPADDR:42477;line=51w5wsns SIP/2.0. Via: SIP/2.0/UDP KAMAILIO_PUBLIC_IPADDR:5060;branch=z9hG4bKfabf.4908255bf1623d250ddf7d51a3b49fb8.0. Via: SIP/2.0/UDP FREESWITCH_IPADDR;received=FREESWITCH_IPADDR;rport=5060;branch=z9hG4bKv7X88FmKg04UF. Record-Route: <sip:KAMAILIO_PUBLIC_IPADDR>;lr=on;ftag=xew5nmpr9q;nat=yes. Max-Forwards: 69. From: <sip:3000@CLIENT_DOMAIN;user=phone>;tag=YF4HMSQNlOOt. To: <sip:3000@CLIENT_DOMAIN>;tag=xew5nmpr9q. Call-ID: 3134323734303730333531303039-ji1sw7gyd7uj. CSeq: 366877453 NOTIFY. Contact: <sip:3000@FREESWITCH_IPADDR:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.18+git~20150312T185523Z~4eed221b69~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Event: dialog. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Subscription-State: active;expires=2686. Content-Type: application/dialog-info+xml. Content-Length: 546. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="14" state="full" entity="sip:3000@CLIENT_DOMAIN"> <dialog id="312b3bee-d405-11e4-a8b6-41b65d0bd045" direction="initiator"> <state>confirmed</state> <local> <identity display="3000">sip:3000@CLIENT_DOMAIN</identity> <target uri="sip:3000@CLIENT_DOMAIN"> <param pname="+sip.rendering" pvalue="yes"/> </target> </local> <remote> <identity display="*98">sip:*98@CLIENT_DOMAIN</identity> <target uri="sip:**3000@CLIENT_DOMAIN"/> </remote> </dialog> </dialog-info> Example of TCP failure: U 2015/03/26 22:19:45.963196 FREESWITCH_IPADDR:5060 -> KAMAILIO_NAT_IPADDR:5160 NOTIFY sip:3001@CLIENT_PUBLIC_IPADDR:5065;transport=tcp SIP/2.0. Via: SIP/2.0/UDP FREESWITCH_IPADDR;rport;branch=z9hG4bKjH5Nt8QKUU9Sp. Route: <sip:KAMAILIO_PUBLIC_IPADDR:5160;r2=on;lr=on;ftag=9jSFr02tgvHym;nat=yes>. Route: <sip:KAMAILIO_PUBLIC_IPADDR:5160;transport=tcp;r2=on;lr=on;ftag=9jSFr02tgvHym;nat=yes>. Max-Forwards: 70. From: "3000" <sip:3000@CLIENT_DOMAIN>;tag=9jSFr02tgvHym. To: <sip:3001@CLIENT_DOMAIN>;tag=1dba0f3ceb32436bi0. Call-ID: 0882b1bc-4ea9-1233-f3a2-12e513dfd8f0. CSeq: 73368127 NOTIFY. Contact: <sip:mod_sofia@FREESWITCH_IPADDR:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.18+git~20150312T185523Z~4eed221b69~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Event: refer;id=101. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Subscription-State: terminated;reason=noresource. Content-Type: message/sipfrag;version=2.0. Content-Length: 16. . SIP/2.0 200 OK. T 2015/03/26 22:19:45.963407 KAMAILIO_NAT_IPADDR:5160 -> CLIENT_PUBLIC_IPADDR:5065 [AP] NOTIFY sip:3001@CLIENT_PUBLIC_IPADDR:5065;transport=tcp SIP/2.0. Via: SIP/2.0/TCP KAMAILIO_PUBLIC_IPADDR:5160;branch=z9hG4bKe961.8d1f19f1acc0295e5e397afa76910115.0. Via: SIP/2.0/UDP FREESWITCH_IPADDR;received=FREESWITCH_IPADDR;rport=5060;branch=z9hG4bKjH5Nt8QKUU9Sp. Max-Forwards: 69. From: "3000" <sip:3000@CLIENT_DOMAIN>;tag=9jSFr02tgvHym. To: <sip:3001@CLIENT_DOMAIN>;tag=1dba0f3ceb32436bi0. Call-ID: 0882b1bc-4ea9-1233-f3a2-12e513dfd8f0. CSeq: 73368127 NOTIFY. Contact: <sip:mod_sofia@FREESWITCH_IPADDR:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.18+git~20150312T185523Z~4eed221b69~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Event: refer;id=101. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Subscription-State: terminated;reason=noresource. Content-Type: message/sipfrag;version=2.0. Content-Length: 16. . SIP/2.0 200 OK. My thoughts is that this is on FreeSWITCH, just not sending a NOTIFY with anything of value. That being said, I'd love to know if (a) anyone else has had this issue or (b) if someone has a different theory. Thanks! -- Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct)

4 11

rtpengine DTLS
by Marc Soda 25 Mar '15

25 Mar '15

I'm running a new kamailio/rtpengine instance and, using webrtc, I can't get audio to flow between the browser and rtpengine. Kamailio seems to be handing it off properly. Based on the rtpengine logs and a packet capture it doesn't look like DTLS is being negotiated properly: https://gist.github.com/marcantonio/ea0077a5884e4e4b6b45 I see "SRTCP output wanted, but no crypto suite was negotiated" and I've never seen that one before (the SRTCP part). I have this exact config working elsewhere, but this new setup is not working? Any advice? Thanks, Marc

1 1

Siremis error Call to a member function getQuoted()
by canuck15 25 Mar '15

25 Mar '15

When you add/update/view Administrator usernames To reproduce Administration > User Management > Click on any existing username. The browser goes blank. Error in apache logs is: PHP Fatal error: Call to a member function getQuoted() on a non-object in /var/www/html/openbiz/bin/data/BizDataSql.php on line 237 This is on the latest Siremis v4.2.0 downloaded today I am using CentOS v6.6, php v5.3.3

3 11

active_watchers - dbt_table_check_row(): null value not allowed - field 17
by Alexandru Raileanu 25 Mar '15

25 Mar '15

Hi, I have kamailio 4.2 with presence, auth, textdb activated. The scenario is that Kamailio receives a SUBSCRIBE, sends 200ok then a NOTIFY. (like it should do) The problem is what when I kill kamailio and run it again, it gives me this error: 0(30580) ERROR: db_text [dbt_tb.c:474]: dbt_table_check_row(): null value not allowed - field 17 0(30580) DEBUG: db_text [dbt_file.c:480]: dbt_load_file(): error at row=1 col=26 c=1 0(30580) ERROR: db_text [dbt_lib.c:307]: dbt_db_get_table(): could not load database from file [active_watchers] 0(30580) ERROR: db_text [dbt_base.c:460]: dbt_delete(): failed to load table <active_watchers>! The field with null values is record_route, so if I put some value I manage to run kamailio. my conf, maybe I missed some field? #!define DBURL "text:///etc/kamailio/dbtext" #!ifdef WITH_PRESENCE modparam("presence", "db_url", DBURL) modparam("presence", "max_expires", 3600) modparam("presence", "server_address", "sip:10.0.37.1:5060" ) modparam("pua_reginfo", "default_domain", "10.0.37.1") modparam("pua_reginfo", "server_address", "sip:10.0.37.1") modparam("pua_reginfo", "outbound_proxy", "sip:10.0.37.1") modparam("pua_reginfo", "publish_reginfo", 1) modparam("pua", "db_mode", 2) modparam("pua", "hash_size", 11) modparam("pua", "db_url", DBURL) modparam("pua", "db_table", "pua") modparam("pua", "min_expires", 0) modparam("pua", "default_expires", 3600) modparam("pua", "update_period", 1000) modparam("pua", "dlginfo_increase_version", 1) modparam("pua", "reginfo_increase_version", 1) modparam("pua", "check_remote_contact", 0) modparam("pua", "fetch_rows", 1000) modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) #!endif Or as a workaround, can I reset the active_watchers table every time I start kamailio? because *kamdbctl create/drop/init* wipes all the other tables... thanks a lot! Alex

2 2

File transferring issue
by Wingsravi R 25 Mar '15

25 Mar '15

Dear Kamailio'ns, I am working on kamailio Server (V 4.0) installed on Ubuntu 12.04 system. Currently i am trying file transfer feature using IMSDroid SIP clients. file transferring is fine between two IMSDroid clients but at the receiving end (file recipient) i cont see the sender identity/ sender name. it is just displaying as 'null' (Screen shot is attached). But the full file is transferring to destination address without any problem. I have configured MSRP module related script in my kamailio configuration file (find the attachment). but i guess it is not invoking anyway when file transferring and the file transferring is negotiating client-to-client basis. And also find Sip capture of file transfer (ngrep based) for better understanding. What could be the problem? Why at the file recipient side it is not displaying sender's identity (instead it is 'null')? how can i resolve this issue? Anyone please help me in resolving this issue. Any help will greatly appreciate. Regards, Ravi.

5 6

[4.2.x] "socket" feature missing in dispatcher module
by Sven Neuhaus 25 Mar '15

25 Mar '15

Hello, in 4.2.2, the "socket" module was added to the documentation of the dispatcher module (see http://kamailio.org/docs/modules/4.2.x/modules/dispatcher.html#dispatcher.e… ), however the code is missing, the feature isn't implemented in 4.2.x. This was in commit 9bb59f922. Please include the patch that adds this feature from the trunk in the 4.2.x branch, as documented. A brief search turned up the commits aae775859f54f84734ba2cfc2945c02c52b95e1f and 2a605383d5c524d9875256c7f95f64216b970331 with this feature, perhaps there are more. Thanks, -Sven Neuhaus

2 1

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

Jump to page:

2026

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