sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

Kamailio multihoming
by roman＠dmytriv.com 11 Apr '11

11 Apr '11

Hello everybody!!! J Did any of you know or have configured Kamailio servers in redundant and load distribution mode on geographically dispersed servers. Can you share some ideas how can this be done. I'm thinking about 2 -3 servers that can be used to distribute load and for redundancy as well. Is Kamailio capable of this or this needs to be done on OS level. Thank you Roman

2 3

Re: [SR-Users] Kamailio XCAP for Kamailio IMS
by Daniel-Constantin Mierla 08 Apr '11

08 Apr '11

Hello, can you run kamailio with global parameter 'debug=3' and send the syslog messages for such case? That will give the hints about what is going wrong there. I see some characters are hexa encoded, but better see first the logs. Cheers, Daniel On 4/8/11 11:14 AM, Pavel Segeč wrote: > > Hi, > > I'm using Kamailio SIMPLE AS server as the presence and XCAP solution > as the extension for my Kamailio based IMS platfom. As the base > Presence configuration i'm using the default config as is described > inside of the tutorial from ASIPTO site, it works well for pure ietf > SIP SIMPLE environment. But when using it with the IMS, I sniff during > putting the new record 500 Error. May somebody show me a direction > what should be wrong? > > thanks > > palo > > PUT > /xcap-root/resource-lists/users/palo/index/~~/resource-lists/list%5B@name=%22doubango%22%5D/entry%5B@uri=%22sip:segi@ims1.sip.uniza.sk%22%5D > HTTP/1.1 > > Host: 158.193.139.36:5060 > > Content-Length: 151 > > Connection: Keep-Alive > > User-Agent: XDM-client/OMA1.1 > > X-3GPP-Intended-Identity: palo > > Content-Type: application/xcap-el+xml > > <entry uri="sip:segi@ims1.sip.uniza.sk" > xmlns="urn:ietf:params:xml:ns:resource-lists"> > > <display-name>segi(a)ims1.sip.uniza.sk</display-name> > > </entry>HTTP/1.1 500 Server error > > Via: SIP/2.0/TCP 158.193.152.64:20735 > > Server: kamailio (3.1.2 (i386/linux)) > > Content-Length: 0 > > > > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6025 > (20110408) __________ > > Tuto spravu preveril ESET NOD32 Antivirus. > > http://www.eset.sk > > > _______________________________________________ > 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 -- Daniel-Constantin Mierla http://www.asipto.com

2 2

ring_insert_callid() fixup error
by Juha Heinanen 08 Apr '11

08 Apr '11

i have modparam("siputils", "ring_timeout", 30) but i get Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: siputils [ring.c:378]: ring_insert_callid functionality deactivated, you need to set a positive ring_timeout Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/sip-proxy/sip-proxy.cfg:658 Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/sip-proxy/sip-proxy.cfg:691 when i start sip router (master version). i looked the code briefly and it tests module param value in fixup function, which i have not seen before. is this a bug or am i missing something? -- juha

2 3

Kamailio and several Asterisk - Realtime DB Integration
by Alejandro Rios P. 08 Apr '11

08 Apr '11

Hi all, I am testing the scenario described here: http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb It works great with one instance of Asterisk, but now that I'm testing with two Asterisk instances to load balance, and I see a problem regarding the registration forwarding to the second Asterisk. I tried adding a second "uac_req_send()" bellow the first one, but Kamailio only sends the first request and the REGISTER never gets to the second Asterisk: # Forward REGISTER to Asterisk route[REGFWD] { if(!is_method("REGISTER")) { return; } $var(rip) = $sel(cfg_get.asterisk.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); $uac_req(furi)="sip:" + $au + "@" + $var(rip); $uac_req(turi)="sip:" + $au + "@" + $var(rip); $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); $uac_req(all) = null; $var(rip2) = $sel(cfg_get.asterisk2.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip2) + ":" + $sel(cfg_get.asterisk2.bindport); $uac_req(furi)="sip:" + $au + "@" + $var(rip2); $uac_req(turi)="sip:" + $au + "@" + $var(rip2); $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); } I also tried appending another branch and sending the second uac_req_send() from there, but it is not being sent. How can I use uac_req_send() several times for the same request or in parallel? Thank you, Alejandro Rios Peña DISCLAIMER: The opinions expressed are my own, and not necessarily those of my employer. <http://www.avatar.com.co>

2 1

SIP-XMPP problem, please help
by Martin Pohančeník 08 Apr '11

08 Apr '11

Hello everyone. I am a student at University of Žilina (Faculty of Management Science and Informatics), which has been recently awarded Kamailio 2010 Awards for various articles about SIP and KAMAILIO on portal nil.uniza.sk. I am doing a bachelor thesis on topic SIP/SIMPLE - XMPP traversal, but I am experiencing some problems. I have a working Kamailio server serving domain sip.uniza.sk and a working Jabberd2 server serving domain xmpp.uniza.sk. I am running Kamailio 3.1 with XMPP module with following configuration: fork=yes children=4 log_stderror=yes alias="sip.uniza.sk" ... loadmodule "XMPP.so" ... modparam("xmpp", "backend", "component") modparam("xmpp", "domain_separator", "*") modparam("xmpp", "gateway_domain", "sip.uniza.sk") modparam("xmpp", "xmpp_domain", "xmpp-sip.uniza.sk") modparam("xmpp", "xmpp_host", "server.xmpp.uniza.sk") modparam("xmpp", "xmpp_password", "secret") ... #main routing logic route { ... if( uri=~"sip:.+[*].+@sip.uniza.sk") { # absorb retransmissions ### if (!t_newtran()) { sl_reply_error(); return; } if (method == "MESSAGE") { log("*** xmpp-handled MESSAGE message.\n"); if (xmpp_send_message()) { t_reply("200", "Accepted"); } else { t_reply("404", "Not found"); } return; } else { t_reply("403","not supported"); exit; } } ... } To my knowledge there is no configuration required on the Jabberd2 server (except the password, that the XMPP component authenticates with). I am trying to enable SIP clients to chat with the XMPP clients and vice versa. SIP clients can send messages to XMPP clients. XMPP modules translates SIP to XMPP and forwards the massage to Jabberd2 server. URIs look like: XMPP client from SIP view: xmpp_client*xmpp.uniza.sk(a)sip.uniza.sk SIP client from XMPP view: sip_client*sip.uniza.sk(a)xmpp-sip.uniza.sk The message arrives to XMPP client, but he can not reply. I have sniffed the traffic on the Kamailio server. The XMPP message arrives to kamailio XMPP module (correct port and everything), but the module somehow ignores it, doesn't translate XMPP to SIP and doesn't send it to the SIP recipient. The sniffed message looks like: <message xmlns='jabber:client' type='chat' to='SIP_client*sip.uniza.sk@ xmpp-sip.uniza.sk' id='mir_47' from='XMPP_client(a)xmpp.uniza.sk/Miranda '><body>hello</body></message> Any suggestions on where can the problem be ?? Do I have to add some lines to routing logic for XMPP module to process the XMPP message (from Jabberd2) for SIP_client ?? Thanks Martin

3 5

TLS certificate on sip-router.org expired
by Timo Reimann 08 Apr '11

08 Apr '11

Heya, just noticed that the TLS certificate on sip-router.org has expired since 9.8.2010. Try an HTTPS connection to the web-page, i.e., https://sip-router.org to see. It seems to be self-signed though. Anyways, I just wanted to let you know. Cheers, --Timo

1 0

Kamailio XCAP for Kamailio IMS
by Pavel Segeč 08 Apr '11

08 Apr '11

Hi, I'm using Kamailio SIMPLE AS server as the presence and XCAP solution as the extension for my Kamailio based IMS platfom. As the base Presence configuration i'm using the default config as is described inside of the tutorial from ASIPTO site, it works well for pure ietf SIP SIMPLE environment. But when using it with the IMS, I sniff during putting the new record 500 Error. May somebody show me a direction what should be wrong? thanks palo PUT /xcap-root/resource-lists/users/palo/index/~~/resource-lists/list%5B@name=%2 2doubango%22%5D/entry%5B@uri=%22sip:segi@ims1.sip.uniza.sk%22%5D HTTP/1.1 Host: 158.193.139.36:5060 Content-Length: 151 Connection: Keep-Alive User-Agent: XDM-client/OMA1.1 X-3GPP-Intended-Identity: palo Content-Type: application/xcap-el+xml <entry uri="sip:segi@ims1.sip.uniza.sk" xmlns="urn:ietf:params:xml:ns:resource-lists"> <display-name>segi(a)ims1.sip.uniza.sk</display-name> </entry>HTTP/1.1 500 Server error Via: SIP/2.0/TCP 158.193.152.64:20735 Server: kamailio (3.1.2 (i386/linux)) Content-Length: 0

1 0

Problems with event_route[htable:mod-init]
by Camila Troncoso 07 Apr '11

07 Apr '11

Hello, I´m using Kamalio 3.1.0 and want to alter some databases (mysql) tables at kamailio starts. I read that the route event_route[htable:mod-init] allows me to do that, but i´m having some problems. I load htable.so module and insert the event_route[] in mi kamailio.conf script but when I start kamailio it returns an error: Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): usrloc Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): registrar Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): uri_db Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): domain Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): permissions Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): group Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): mi_fifo Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): avpops Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): dialog Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): lcr Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): sqlops Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): rtimer Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [sr_module.c:828]: DEBUG: init_mod_child (-127): htable Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: htable [htable.c:185]: rank is (-127) Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: htable [htable.c:191]: executing event_route[htable:mod-init] (1) Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:630]: SIP Request: Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:632]: method: <OPTIONS> Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:634]: uri: <sip:you@kamailio.org> Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:636]: version: <SIP/2.0> Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: <core> [mem/q_malloc.c:366]: qm_malloc(0x82bbfa0, 32) called from <core>: parser/msg_parser.c: parse_headers(341) Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: <core> [mem/q_malloc.c:406]: qm_malloc(0x82bbfa0, 32) returns address 0x834f780 frag. 0x834f768 (size=32) on 1 -th hit Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: <core> [mem/q_malloc.c:366]: qm_malloc(0x82bbfa0, 116) called from <core>: parser/msg_parser.c: get_hdr_field(130) Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: <core> [mem/q_malloc.c:406]: qm_malloc(0x82bbfa0, 116) returns address 0x834f7d0 frag. 0x834f7b8 (size=116) on 1 -th hit Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/parse_via.c:2300]: end of header reached, state=2 Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:515]: parse_headers: Via found, flags=2 Apr 7 15:30:22 server4967 /usr/local/sbin/kamailio[31610]: DEBUG: <core> [parser/msg_parser.c:517]: parse_headers: this is the first via Apr 7 15:30:22 server4967 kamailio: ERROR: <core> [daemonize.c:307]: Main process exited before writing to pipe * * * * My event_rout[] is as fallows: event_route[htable:mod-init]{ sql_query("cd", "select prefix from lcr_rule", "rc"); xlog("L_INFO", "dbr = $dbr(rc=>rows)"); if($dbr(rc=>rows)>0){ $var(i) = 0; while($var(i)<$dbr(rc=>rows)){ $var(prefijo)=$dbr(rc=>[$var(i),0]); xlog("L_INFO", "$dbr(rc=>[$var(i),0])"); sql_query("cd", "ALTER TABLE rebalse ADD COLUMN Prefijo_$var(prefijo) INT","rr"); $var(i) = $var(i) + 1; } } sql_result_free("rc"); } I tested the commands inside the event_route[] and they work fine… Can someone help me? Regards, *Camila Troncoso **|* Ingeniero de Desarrollo RedVoiss *|*ctroncoso(a)redvoiss.net Santiago - Chile *|* +56 2 2408535 www.redvoiss.net

2 1

It's ClueCon Time!
by marketing＠cluecon.com 07 Apr '11

07 Apr '11

1 0

"kamctl fifo debug" does not work
by Klaus Darilion 07 Apr '11

07 Apr '11

root@pbx-kam-1:/home/klaus3000# kamctl fifo debug DEBUG:: 2 root@pbx-kam-1:/home/klaus3000# kamctl fifo debug 0 DEBUG:: 0 Mar 9 11:04:23 pbx-kam-1 /usr/sbin/kamailio[4548]: INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): core.debug has been changed to 0 but: root@pbx-kam-1:/home/klaus3000# kamctl fifo debug DEBUG:: 2 Is this a bug? regards Klaus

2 2

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