- sr-users - kamailio.org

Re: [SR-Users] Destination number restriction
by Keith 03 Oct '13

03 Oct '13

Also I would like to try and store these numbers in a the DB somehow to minimise code. Keith On Thu, Oct 3, 2013 at 1:40 PM, <sr-users-request(a)lists.sip-router.org>wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.sip-router.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.sip-router.org > > You can reach the person managing the list at > sr-users-owner(a)lists.sip-router.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Destination number restriction (Keith) > 2. Re: append_hf to reply generated by kamailio (Grant Bagdasarian) > 3. Re: append_hf to reply generated by kamailio (Grant Bagdasarian) > 4. Re: append_hf to reply generated by kamailio (Klaus Darilion) > 5. Re: Destination number restriction (Morten Isaksen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 3 Oct 2013 11:14:10 +0100 > From: Keith <keith(a)hubner.co.uk> > To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List" <sr-users(a)lists.sip-router.org> > Subject: [SR-Users] Destination number restriction > Message-ID: > <CAK7Ybu8= > JNk+P4ASeB66XP6_3jUqxO1jhQBiPvAbDoEg5gjeDQ(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I am looking to restrict calls based on destination numbers, e.g. so people > can't call premium rate etc. Which module is best to achieve this? > > Thanks, > Keith >

2 1

Re: [SR-Users] Destination number restriction
by Keith 03 Oct '13

03 Oct '13

Thanks Morten, So basically it's saying, if it matches that number and the user does not have the permission to call it then block. I am a bit unclear of the AVP stuff to be honest, is this trying to match the username to the attribute in the table? And what value does it look for in the table? Thanks, Keith On Thu, Oct 3, 2013 at 1:40 PM, <sr-users-request(a)lists.sip-router.org>wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.sip-router.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.sip-router.org > > You can reach the person managing the list at > sr-users-owner(a)lists.sip-router.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Destination number restriction (Keith) > 2. Re: append_hf to reply generated by kamailio (Grant Bagdasarian) > 3. Re: append_hf to reply generated by kamailio (Grant Bagdasarian) > 4. Re: append_hf to reply generated by kamailio (Klaus Darilion) > 5. Re: Destination number restriction (Morten Isaksen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 3 Oct 2013 11:14:10 +0100 > From: Keith <keith(a)hubner.co.uk> > To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List" <sr-users(a)lists.sip-router.org> > Subject: [SR-Users] Destination number restriction > Message-ID: > <CAK7Ybu8= > JNk+P4ASeB66XP6_3jUqxO1jhQBiPvAbDoEg5gjeDQ(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I am looking to restrict calls based on destination numbers, e.g. so people > can't call premium rate etc. Which module is best to achieve this? > > Thanks, > Keith >

1 0

Destination number restriction
by Keith 03 Oct '13

03 Oct '13

Hi, I am looking to restrict calls based on destination numbers, e.g. so people can't call premium rate etc. Which module is best to achieve this? Thanks, Keith

2 1

append_hf to reply generated by kamailio
by Grant Bagdasarian 03 Oct '13

03 Oct '13

Hello, Is it possible to append a new header to a reply generated by Kamailio and also have it present when duplicating the message to a capture server? At the moment the 603 Reply is duplicated to my capture server, but I don't know how to append a new header, because the kamailio script stops executing after exit is called. >From what I understood: onreply_route is only executed when receiving replies. Is there a reply_route which is executed for all replies, including the ones generated by kamailio itself? For instance inside this code block: request_route { ..... if($var(routing_query_result) =~ "DESTINATION_NOT_ALLOWED") { xlog("L_INFO", "[R-CORE-INCOMING-INVITE:$ci] !>" "Rejecting the call, because the destination is not allowed\r\n"); sl_send_reply("603", "Decline"); exit; } ..... }

2 3

Replace header value in failure_route
by Grant Bagdasarian 03 Oct '13

03 Oct '13

Hello, I'm trying to replace the value of a custom header in the failure_route, using the subst function. subst('/^X-Dispatcher:(.+)$/"X-Dispatcher: \$(avp(dsattrs){param.value,dispatcher})"/i'); I also tried it with the subst_hf, but that didn't work either. I'm getting the following message: 5(19536) DEBUG: <core> [re.c:454]: subst_run(): subst_run: running. r=1 5(19536) DEBUG: textops [textops.c:681]: subst_f(): lst was (nil) Does anyone have an idea what I'm doing wrong here? I'm not a regex expert, so I'm guessing there is an error in the pattern. Regards, Grant

3 5

Re: [SR-Users] Scripting
by Keith 03 Oct '13

03 Oct '13

Hi, I am looking to add some scripting to Kamailio so I can set my own variables and configure from my own web page. Anyone point me in the right direction? Thanks, Keith

1 0

Jitsi Load contact from Kamailio
by Kethzer Docteur 02 Oct '13

02 Oct '13

Im trying to enable xcap service on kamailio. I would like to know if it possible work as show in the video. Thanks for any leads how to get it works as same as the youtube video below. https://www.youtube.com/watch?v=3laTBL6NnbE -- Kethzer Docteur

1 0

pkg.stats problem
by Vitaliy Aleksandrov 02 Oct '13

02 Oct '13

Hello, I have one installation with a strange pkg.stats output: root@host:~# kamcmd pkg.stats index 36 { entry: 36 pid: 2599 rank: -4 used: 16234288 free: 15788240 real_used: 16900864 } After some time I've checked it again and found that used and real_used fields grew up while free wasn't changed: root@host:~# kamcmd pkg.stats index 36 { entry: 36 pid: 2599 rank: -4 used: 19393184 free: 15788240 real_used: 20125968 } Additional info: - kamailio-4.0.2 started with -m 128 -M 16 - Process:: ID=36 PID=2599 Type=tcp main process - this server works as a websocket(ws,wss) to udp/tcp gateway. How is it possible that real_used is bigger that -M allows and free value is not changing while used/real_used are growing up.

4 13

xcap server config snippets
by Daniel-Constantin Mierla 02 Oct '13

02 Oct '13

Hello, there were several emails related to usage of embedded xcap server module, so I am pasting here relevant snippets from config file that should get people started. Cheers, Daniel #!define WITH_XHTTP #!define WITH_XCAPSRV tcp_accept_no_cl=yes tcp_rd_buf_size=65536 pv_buffer_size=65536 sql_buffer_size=65536 #!define XHTTP_PORT 8080 #!define XHTTPS_PORT 8443 #!ifdef WITH_XHTTP loadmodule "xhttp.so" #!endif #!ifdef WITH_XCAPSRV loadmodule "xcap_server.so" #!endif #!ifdef WITH_XCAPSRV # ----- xcap_server params ----- modparam("xcap_server", "db_url", DBURL) modparam("xcap_server", "buf_size", 65536) #!endif ... #!ifdef WITH_XHTTP event_route[xhttp:request] { xdbg("===== xhttp: request [$rv] $rm => $hu\n"); set_reply_no_connect(); if ($Rp != XHTTP_PORT #!ifdef WITH_TLS && $Rp != XHTTPS_PORT #!endif ) { set_reply_close(); xlog("L_WARN", "HTTP request received on $Rp\n"); xhttp_reply("403", "Forbidden", "", ""); exit; } if (!www_authorize("mydomain.com", "subscriber")) { www_challenge("mydomain.com", "0"); exit; } set_reply_close(); route(XCAPSRV); # other http access xhttp_reply("200", "ok", "text/html", "<html><body>OK: $si:$sp</body></html>"); exit; } #!endif route[XCAPSRV] { #!ifdef WITH_XCAPSRV if(! ($hu=~"^/xcap-root/")) { return; } # xcap ops - break down http uri to get xcap user id route(XCAPURI); $xcapuri(u=>data) = $var(hu); if($xcapuri(u=>uri)==$null) { xlog("==== xhttp failed uri => [$hu] ~ [$var(hu)]\n"); xhttp_reply("404", "Not Found", "text/html", "unsupported xcap uri"); exit; } if($xcapuri(u=>xuid)=~"^sip:.+@.+") $var(uri) = $xcapuri(u=>xuid); else $var(uri) = "sip:"+ $xcapuri(u=>xuid) + "@" + $Ri; # handle XCAP capability request if($xcapuri(u=>auid)=="xcap-caps") { if ($rm == "GET") { $var(xbody) = "<?xml version='1.0' encoding='UTF-8'?> <xcap-caps xmlns='urn:ietf:params:xml:ns:xcap-caps'> <auids> " + #!ifdef WITH_RLS " <auid>rls-services</auid> " + #!endif " <auid>pidf-manipulation</auid> <auid>xcap-caps</auid> <auid>resource-lists</auid> <auid>pres-rules</auid> <auid>org.openmobilealliance.pres-rules</auid> <auid>org.openmobilealliance.user-profile</auid> <auid>org.openmobilealliance.pres-content</auid> <auid>org.openmobilealliance.search</auid> <auid>org.openmobilealliance.xcap-directory</auid> </auids> <extensions> </extensions> <namespaces> " + #!ifdef WITH_RLS " <namespace>urn:ietf:params:xml:ns:rls-services</namespace> " + #!endif " <namespace>urn:ietf:params:xml:ns:pidf</namespace> <namespace>urn:ietf:params:xml:ns:xcap-caps</namespace> <namespace>urn:ietf:params:xml:ns:resource-lists</namespace> <namespace>urn:ietf:params:xml:ns:pres-rules</namespace> <namespace>urn:oma:xml:xdm:user-profile</namespace> <namespace>urn:oma:xml:prs:pres-content</namespace> <namespace>urn:oma:xml:xdm:search</namespace> <namespace>urn:oma:xml:xdm:xcap-directory</namespace> </namespaces> </xcap-caps>"; xhttp_reply("200", "ok", "application/xcap-caps+xml", "$var(xbody)"); } else { append_to_reply("Allow: GET\r\n"); xhttp_reply("405", "Method Not Allowed", "", ""); } exit; } # be sure auth user access only its documents if ($rm!="GET" && $au!=$(var(uri){uri.user})) { xlog("==== xhttp forbidden => [$au] != [$(var(uri){uri.user})]\n"); xhttp_reply("403", "Forbidden", "text/html", "operation not allowed"); exit; } xdbg("SCRIPT: xcap service $xcapuri(u=>auid) for $xcapuri(u=>xuid)\n"); switch($rm) { case "PUT": xcaps_put("$var(uri)", "$var(hu)", "$rb"); if($xcapuri(u=>auid)=~"pres-rules") { pres_update_watchers("$var(uri)", "presence"); pres_refresh_watchers("$var(uri)", "presence", 1); #!ifdef WITH_RLS } else if($xcapuri(u=>auid)=~"rls-services" || $xcapuri(u=>auid)=~"resource-lists") { rls_update_subs("$var(uri)", "presence"); #!endif } else if($xcapuri(u=>auid)=~"pidf-manipulation") { pres_refresh_watchers("$var(uri)", "presence", 2, "$xcapuri(u=>uri_adoc)", "$xcapuri(u=>file)"); } exit; break; case "GET": $var(furi) = "sip:" + $au + "@" + $ar; if ($au!=$(var(uri){uri.user})) { # be sure only auth user gets its non-profile documents if (!($xcapuri(u=>auid)=~"user-profile" || $xcapuri(u=>auid)=~"pres-content")) { xhttp_reply("403", "Forbidden", "", ""); exit; } else { # be sure only permitted user gets others profile documents pres_auth_status("$var(furi)", "$var(uri)"); $var(rc) = $rc; if ($var(rc) != 1) { xhttp_reply("403", "Forbidden", "", ""); exit; } } } xcaps_get("$var(uri)", "$var(hu)"); exit; break; case "DELETE": xcaps_del("$var(uri)", "$var(hu)"); if($xcapuri(u=>auid)=~"pres-rules") { pres_update_watchers("$var(uri)", "presence"); pres_refresh_watchers("$var(uri)", "presence", 1); #!ifdef WITH_RLS } else if($xcapuri(u=>auid)=~"rls-services" || $xcapuri(u=>auid)=~"resource-lists") { rls_update_subs("$var(uri)", "presence"); #!endif } else if($xcapuri(u=>auid)=~"pidf-manipulation") { pres_refresh_watchers("$var(uri)", "presence", 2, "$xcapuri(u=>uri_adoc)", "$xcapuri(u=>file)"); } exit; break; case "POST": if($xcapuri(u=>auid)=~"search") { xhttp_reply("501", "Not Implemented", "", ""); } else { if($xcapuri(u=>auid)=~"xcap-directory") { append_to_reply("Allow: GET\r\n"); } else { append_to_reply("Allow: DELETE, GET, PUT\r\n"); } xhttp_reply("405", "Method Not Allowed", "", ""); } exit; break; } #!endif return; } # Return fixed XCAP URI in $var(hu) route[XCAPURI] { #!ifdef WITH_XCAPSRV # Jitsi... if ($hu=~"^/xcap-root/resource-lists/users/.*/index$") { $var(hu) = $(hu{re.subst,!(^/xcap-root/resource-lists/users/.*/).*$!\1generallist.xml!}); } else if ($hu=~"^/xcap-root/pres-rules/users/.*/presrules$") { $var(hu) = $(hu{re.subst,!(^/xcap-root/)pres-rules(/users/.*/)presrules!\1org.openmobilealliance.pres-rules\2pres-rules!}); } else if ($hu=~"^/xcap-root/oma_status-icon/users/.*/.*$") { $var(hu) = $(hu{re.subst,!(^/xcap-root/)oma_status-icon(/users/.*/).*$!\1org.openmobilealliance.pres-content\2oma_status-icon/icon_document!}); # Bria... } else if ($hu=~"^/xcap-root/resource-lists/users/.*/contacts-resource-list.xml$") { $var(hu) = $(hu{re.subst,!(^/xcap-root/resource-lists/users/.*/).*$!\1generallist.xml!}); } else if ($hu=~"^/xcap-root/resource-lists/users/.*/resource-list.xml$") { $var(doc_uri) = $(hu{re.subst,!(^/xcap-root/resource-lists/users/.*/).*$!\1generallist.xml!}); # No modification required... } else { $var(hu) = $hu; } #!endif return; } -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013 - more details about Kamailio trainings at http://www.asipto.com -

1 0

Kamailio v4.0.4 Released
by Daniel-Constantin Mierla 02 Oct '13

02 Oct '13

Hello, Kamailio SIP Server v4.0.4 stable release is out. This is a maintenance release of the latest stable branch, 4.0, that includes fixes since release of v4.0.0. There is no change to database schema or configuration language structure that you have to do on installations of v4.0.0. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.0.4. For more details about version 4.0.4 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2013/10/kamailio-v4-0-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

2 1

debugging some error logs
by arun Jayaprakash 02 Oct '13

02 Oct '13

Hello, I am seeing some error logs as follows in my log file and would like to know what this means? Could someone help me with this: Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=592 a=5 n=route Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=742 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=737 a=25 n=alias_db_lookup Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=752 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=742 a=25 n=is_method Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=752 a=63 n=assign Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=770 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=753 a=25 n=lookup Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=775 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=770 a=25 n=is_method Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=775 a=5 n=route Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=610 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=607 a=25 n=is_method Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=613 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=610 a=25 n=is_method Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=617 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=613 a=25 n=is_method Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=620 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=617 a=24 n=t_relay Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=620 a=2 n=exit Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=1071 a=16 n=if Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=1062 a=26 n=xlog Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=1063 a=2 n=return Oct 1 21:46:34 ip-172-10-30-30 /usr/local/sbin/kamailio[2215]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio//kamailio.cfg] l=592 a=5 n=route Below is a portion on my config file: kamailio.cfg file route(LOCATION); <---line 592 ...................... if(alias_db_lookup("dbaliases")) <---line 737 route(SIPOUT); #!endif #!ifdef WITH_ASTERISK if(is_method("INVITE") && (!route(FROMASTERISK))) { <---line 742 # if new call from out there - send to Asterisk # - non-INVITE request are routed directly by Kamailio # - traffic from Asterisk is routed also directy by Kamailio route(TOASTERISK); exit;} #!endif $avp(oexten) = $rU; <---line 752 if (!lookup("location")) {; ................................ if (is_method("INVITE")) <---line 770 Regards, Arun

2 2

Presence issue between XMPP-SIP clients.
by Nandini madhu 02 Oct '13

02 Oct '13

Dear All, I am working on XMPP module of kamailio server (V-4.0.2), intended to achieve File transfer, IM features. Firstly my Kamailio and Jabberd2 servers are on the same machine. I managed to separately make them work. Call setup between SIP clients is working and so with messaging/presence, File transfer functions for Jabberd clients. But when i integrate both the servers by using xmpp module, i can only send messages to SIP clients from XMPP client (one way) but i cannot send messages to xmpp clients from SIP clients. Off course the *presence is not sharing* between these SIP and XMPP clients. My clients URI and JID syntax are looking like this: ---> SIP client (registered to kamailio server): *112@sip_domain* ---> XMPP client (registered to Jabberd server): * 114*sip_domain@jabber_server *(Is this syntax is correct?) And in SIP client contact list ,added an XMPP user which look like this: *sip:114*sip_domain*jabber_server@gateway_domain * In XMPP clients buddy list, added a SIP client which looks like this: * 112*sip_domain@xmpp_domain* Is the above syntaxes are correct ? Following are my working domain names(for your reference): sip_domain ---> kamailio.kamailio.test xmpp_server host ---> xmpp.kamailio.test gateway_domain ---> sip-xmpp.kamailio.test xmpp_domain ---> xmpp-sip.kamailio.test. And my syslog is giving the errors like this: Oct 1 18:40:57 kamailio /usr/local/sbin/kamailio[18710]: INFO: pua_usrloc [ul_publish.c:221]: ul_publish(): not marked for publish Oct 1 18:41:21 kamailio /usr/local/sbin/kamailio[18714]: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Duplicate entry '112-kamailio.kamailio.test-presence-*#-OFFLINE-#*' for key 'presentity_idx' Oct 1 18:41:21 kamailio /usr/local/sbin/kamailio[18714]: ERROR: <core> [db_query.c:337]: db_do_update(): error while submitting query Oct 1 18:41:21 kamailio /usr/local/sbin/kamailio[18714]: ERROR: presence [presentity.c:1281]: mark_presentity_for_delete(): unsuccessful sql update operation Oct 1 18:41:21 kamailio /usr/local/sbin/kamailio[18714]: ERROR: presence [publish.c:171]: msg_presentity_clean(): Marking presentity Oct 1 18:41:21 kamailio /usr/local/sbin/kamailio[18723]: INFO: presence [notify.c:1601]: send_notify_request(): NOTIFY sip:114*kamailio.kamailio.test*xmpp.kamailio.test@sip-xmpp.kamailio.testvia sip:114*kamailio.kamailio.test*xmpp.kamailio.test@sip-xmpp.kamailio.teston behalf of sip:112@kamailio.kamailio.testfor event presence. Please below find the attachment of my kamailio configuration file. What could be the wrong ? How can i solve this issue ? And why the presence is not visible between the clients even after integrated pua_xmpp module in script ? PS: set-up credentials are : XMPP client ---> pidgin SIP client ---> Jitsi Any help will greatly appreciate. Regards, Nandini

2 1

Planing to release v4..0.4
by Daniel-Constantin Mierla 02 Oct '13

02 Oct '13

Hello, I am planing to release Kamailio v4.0.4 this week on Wednesday, Sep 2. If anyone has patching to push in branch 4.0, do it before noon GMT in that day. Also, if any developer is preferring another release day, just present the option on the mailing lists. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013 - more details about Kamailio trainings at http://www.asipto.com -

1 1

Phones losing registration.
by arun Jayaprakash 01 Oct '13

01 Oct '13

Hello, I am running into a problem with my set up. I have Kamailio 4.0 set up with an Asterisk server (ARA). Initially I had three machines; one for Kamailio, one for Asterisk and one for my db. The set up worked fine for about a week after which I saw that my phones were losing registration for prolonged periods and then would re-register after a few hours. So what I did was to move Asterisk and Kamailio on the same server and only had my DB on a separate machine. All worked well for about a week and now I am facing the same issue. At any given time all my services ( kamailio, Asterisk, RTPproxy) are all running. My question is where and how do I start to trouble shoot this issue? I have not really done any debugging in the past so I would appreciate any pointers as to where to start? Thank you for your help. Regards, Arun

2 4

Nathelper Error Message
by Kethzer Docteur 01 Oct '13

01 Oct '13

Any help solving this error message from kamailio server 4.0 Oct 1 00:31:07 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 00:31:07 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 03:09:14 kmlsvr /usr/local/sbin/kamailio[27169]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 03:09:14 kmlsvr /usr/local/sbin/kamailio[27169]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 03:09:23 kmlsvr /usr/local/sbin/kamailio[27167]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 03:09:23 kmlsvr /usr/local/sbin/kamailio[27167]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 03:09:26 kmlsvr /usr/local/sbin/kamailio[27168]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 03:09:26 kmlsvr /usr/local/sbin/kamailio[27168]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 04:24:24 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 04:24:24 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 06:28:11 kmlsvr /usr/local/sbin/kamailio[27168]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 06:28:11 kmlsvr /usr/local/sbin/kamailio[27168]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 06:37:08 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 06:37:08 kmlsvr /usr/local/sbin/kamailio[27166]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Oct 1 08:22:55 kmlsvr /usr/local/sbin/kamailio[27169]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Oct 1 08:22:55 kmlsvr /usr/local/sbin/kamailio[27169]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! -- Kethzer Docteur

2 1

kamailio registering on back-end asterisk with username and password
by Paul Penev 01 Oct '13

01 Oct '13

I'm trying to implement a load balancer for asterisk servers using kamailio and the tutorial at http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb I must fit the balancer in an infrastructure without touching the other media servers (asterisk) which require a username/password authentication. The sample implementation constructs a register request from scratch, but does not handle authorization and thus fails. I cannot change the current sip servers and their configuration as these are a live system and I'm not allowed to touch it. I would really appreciate some hints on how to proceed. # 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(); } Thank you, Paul.

2 4

Re: [SR-Users] regarding topoh hiding
by Daniel-Constantin Mierla 01 Oct '13

01 Oct '13

Hello, On 10/1/13 8:09 AM, Premchandiran wrote: > > Hi All, > > I have query/observation w.r.t topoh I hiding, before loading topoh > module rr module must be loaded . I found that methods like > record_route() in rr module must be present in the cfg then only topoh > hiding is taking place. Otherwise tough rr module and topoh module is > loaded topoh hiding is not taking place. Is that right? Please clarify > the same. > there is no relation between rr module and topoh. Can you get the log messages with debug=3 in config file? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013 - more details about Kamailio trainings at http://www.asipto.com -

2 1

Communicate with Kamailio through external application
by Grant Bagdasarian 01 Oct '13

01 Oct '13

Hello, When adding rows to the dispatcher table, the table in memory needs to be refreshed. Since we have multiple Kamailio instances running on different machines, I'd like to automate the process of reloading the table. Is there an easy way of doing this with an already existing module, which provides easy connectivity from the outside? Or do I need to write an application which basically sets up a SSH socket connection with the machine and sends the command "kamctl dispatcher reload" then exit? Not that hard either, but there might be a finer solution available. Regards, Grant

3 18

regarding topoh hiding
by Premchandiran 01 Oct '13

01 Oct '13

Hi All, I have query/observation w.r.t topoh I hiding, before loading topoh module rr module must be loaded . I found that methods like record_route() in rr module must be present in the cfg then only topoh hiding is taking place. Otherwise tough rr module and topoh module is loaded topoh hiding is not taking place. Is that right? Please clarify the same. Thanks, Prem Chandiran M

1 0

unsubscribe
by Pablo R. Digonzelli 30 Sep '13

30 Sep '13

Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714

1 0

potential memory leak
by Dragos Oancea 30 Sep '13

30 Sep '13

Hello We've put Kamailio on a machine with a SIP-Proxy role, we replaced another SIP proxy implementation. We started with the default 4Mb of PKG Memory and 1024 Mb of Shared Memory but we had messages like these in the logs: 2013-09-26 13:48:26,939 ERROR: app_perl [kamailioxs.xs:371]: pv_sprintf(): pv_sprintf: Memory exhausted! 2013-09-26 13:48:50,267 ERROR: app_perl [kamailioxs.xs:371]: pv_sprintf(): pv_sprintf: Memory exhausted! 2013-09-26 13:48:51,822 ERROR: <core> [data_lump.c:197]: insert_subst_lump_after(): ERROR: insert_new_lump_after: out of memory 2013-09-26 13:48:51,823 ERROR: <core> [parser/contact/contact.c:194]: parse_contacts(): parse_contacts(): No memory left 2013-09-26 13:48:51,823 ERROR: memcached [../../parser/../ut.h:736]: pkg_str_dup(): could not allocate private memory from available pool 2013-09-26 13:48:51,823 ERROR: <core> [data_lump.c:373]: anchor_lump(): ERROR: anchor_lump: out of memory 2013-09-26 13:48:51,823 ERROR: <core> [dset.c:525]: rewrite_uri(): No memory left to rewrite r-uri 2013-09-26 13:48:51,823 ERROR: <core> [action.c:810]: do_action(): ERROR: do_action: memory allocation failure 2013-09-26 13:48:51,823 ERROR: <core> [msg_translator.c:2164]: build_res_buf_from_sip_req(): ERROR: build_res_buf_from_sip_req: out of memory ; needs 357 2013-09-26 13:48:51,823 ERROR: <core> [msg_translator.c:2164]: build_res_buf_from_sip_req(): ERROR: build_res_buf_from_sip_req: out of memory ; needs 376 Then we started kamailio like below, with 1024Mb of private memory (per process) : /opt/kamailio/sbin/kamailio -f /opt/kamailio/etc/kamailio//kamailio.cfg -w /opt/kamailio/core_dir/corefiles -P /opt/kamailio/var/run//kamailio.pid -m 1024 -M 1024 -u kamailio -g kamailio Then after about 4 days we realized that we have a steady increase of used memory ( in the output of free command the '-/+ buffers/cache:' row ), and we simply restarted the kamailio process. The machine has 12 Gb of RAM , we run with children=32 . 1gb of memory per process x 32 child processes means that we are over the physical capacity of the machine. The question is , are we in any danger of running out of memory on this box where we only run kamailio ? We don't want to reach the point where the kernel starts killing processes. Shall we suspect some memory leak in the app_perl module ? (we do some http queries over SSL from a perl script) Thank you. Regards, Dragos Oancea

2 4

A Question kamailio & SEMS
by Camilo Bozo 30 Sep '13

30 Sep '13

Hello! I want configure kamailio & sems, but i dont know where configure the modules read ¿ as load modules so that one can read Kamailio? Thanks!

1 0

next irc devel meeting - proposed for Sep 12, 2013
by Daniel-Constantin Mierla 30 Sep '13

30 Sep '13

Hello, I'm considering to have a new IRC devel meeting to plan a bit the development for the near future (among them, nail down goals and dates for next major release). The proposed date is next week on Thursday, at 14:00UTC, on #kamailio channel from irc.freenode.net. I create a wiki page for it at: - https://www.kamailio.org/wiki/devel/irc-meetings/2013b First thing to decide is the date and time, if it is something convenient for many people. If not, propose other dates and we will chose the one when most of the people are available. Also, feel free to add to agenda. For now I just created a basic list, I will add more myself as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013 - more details about Kamailio trainings at http://www.asipto.com -

3 8

DNS SRV when no NAPTR
by Øyvind Kolbu 30 Sep '13

30 Sep '13

Hi, I'm having problems connecting to a videoservice at seevia.no, because they have no NAPTR nor _sip._udp.seevia.no entry. They do have for tcp and sips: % host -t NAPTR seevia.no seevia.no has no NAPTR record % host -t SRV _sip._udp.seevia.no Host _sip._udp.seevia.no not found: 3(NXDOMAIN) % host -t SRV _sip._tcp.seevia.no _sip._tcp.seevia.no has SRV record 1 0 5060 vcse.vcn.no. % host -t SRV _sips._tcp.seevia.no _sips._tcp.seevia.no has SRV record 1 0 5061 vcse.vcn.no. % host -t A vcse.vcn.no. vcse.vcn.no has address 85.19.200.18 vcse.vcn.no has address 62.92.46.211 % host -t A seevia.no seevia.no has address 93.89.34.42 Ref an old thread on sr-dev, <http://lists.sip-router.org/pipermail/sr-dev/2012-October/016969.html> this should have been fixed by <http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=63ef5f0…>. From tcpdump: 65177+ NAPTR? seevia.no. (27) 65177 0/1/0 (86) 31896+ SRV? _sip._udp.seevia.no. (37) 31896 NXDomain 0/1/0 (96) 54304+ A? seevia.no. (27) 54304 1/2/2 A 42.93-89-34.enivest.net (119) Trivial to see it does not attempt to lookup anything after a NXDOMAIN for _sip._udp.seevia.no. % host -t A 42.93-89-34.enivest.net 42.93-89-34.enivest.net has address 93.89.34.42 Any idea why my INVITEs are being sent to 93.89.34.42 instead one of vcse.uio.no's IPs? My dns settings: use_dns_cache=on use_dns_failover=on dns_try_ipv6=no dns_retr_time=1 dns_retr_no=2 dns_use_search_list=no dns_try_naptr = yes dns_srv_lb = yes I'm running latest 4.0: % kamailio -V version: kamailio 4.0.3 (i386/linux) a331af flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_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 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: a331af compiled on 11:30:24 Sep 17 2013 with gcc 4.1.2 -- Øyvind Kolbu

3 20

Xcap_server error in kamailio 4.0.0
by Kethzer Docteur 27 Sep '13

27 Sep '13

Error in SIP contact list storage Resouce cannot be reade http://Server_ip:80/xcap-root/xcap-caps/global/index Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:gsysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: INFO: presence [notify.c:1601]: NOTIFY sip:sysadmin@67.*.*.* via sip:sysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:dsysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:ksysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:sysadmin@67.*.*.* via sip:sysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:jksysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 09:58:43 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 7 times Sep 26 10:01:13 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:13 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 8 times Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:41 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 7 times Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:05 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). -- Kethzer Docteur

2 1

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