sr-users March 2014

sr-users@lists.kamailio.org

101 participants
166 discussions

invalid xmlrpc response from pkg.stats?
by Juha Heinanen 05 Mar '14

05 Mar '14

i tried make xmlrpc query on pkg.stats, but my xmlrpc lib was not able to parse the response (below). according to xmlrpc spec: The body of the response is a single XML structure, a <methodResponse>, which can contain a single <params> which contains a single <param> which contains a single <value>. according to the spec <value> is scalar value or <struct> or <array>. in sip proxy response below, there a several <struct>s in the <value>, which according to my understanding is violation of the spec. instead, the response should be like this: <?xml version="1.0"?> <methodResponse> <params> <param> <value> <array> <data> <value> <struct>...</struct> </value> <value> <struct>...</struct> </value> ... </data> </array> </param> </methodResponse> comments? -- juha -------------------------------------------------------------------------- Received the following response: HTTP/1.0 200 OK Via: SIP/2.0/TCP 127.0.0.1:36643 Server: OpenXg SIP Proxy (4.1.1-2 (i386/linux)) Content-Length: 6311 <?xml version="1.0"?> <methodResponse> <params> <param> <value><struct><member><name>entry</name><value><int>0</int></value></member><member><name>pid</name><value><int>5846</int></value></member><member><name>rank</name><value><int>0</int></value></member><member><name>used</name><value><int>4553004</int></value></member><member><name>free</name><value><int>559936</int></value></member><member><name>real_used</name><value><int>5731520</int></value></member></struct> <struct><member><name>entry</name><value><int>1</int></value></member><member><name>pid</name><value><int>5848</int></value></member><member><name>rank</name><value><int>1</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>2</int></value></member><member><name>pid</name><value><int>5849</int></value></member><member><name>rank</name><value><int>2</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>3</int></value></member><member><name>pid</name><value><int>5850</int></value></member><member><name>rank</name><value><int>3</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>4</int></value></member><member><name>pid</name><value><int>5851</int></value></member><member><name>rank</name><value><int>4</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>5</int></value></member><member><name>pid</name><value><int>5852</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556356</int></value></member><member><name>free</name><value><int>556296</int></value></member><member><name>real_used</name><value><int>5735160</int></value></member></struct> <struct><member><name>entry</name><value><int>6</int></value></member><member><name>pid</name><value><int>5853</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556356</int></value></member><member><name>free</name><value><int>556296</int></value></member><member><name>real_used</name><value><int>5735160</int></value></member></struct> <struct><member><name>entry</name><value><int>7</int></value></member><member><name>pid</name><value><int>5854</int></value></member><member><name>rank</name><value><int>4294967294</int></value></member><member><name>used</name><value><int>4563012</int></value></member><member><name>free</name><value><int>549112</int></value></member><member><name>real_used</name><value><int>5742344</int></value></member></struct> <struct><member><name>entry</name><value><int>8</int></value></member><member><name>pid</name><value><int>5857</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556368</int></value></member><member><name>free</name><value><int>556236</int></value></member><member><name>real_used</name><value><int>5735220</int></value></member></struct> <struct><member><name>entry</name><value><int>9</int></value></member><member><name>pid</name><value><int>5863</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556368</int></value></member><member><name>free</name><value><int>556236</int></value></member><member><name>real_used</name><value><int>5735220</int></value></member></struct> <struct><member><name>entry</name><value><int>10</int></value></member><member><name>pid</name><value><int>5873</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4557616</int></value></member><member><name>free</name><value><int>554844</int></value></member><member><name>real_used</name><value><int>5736612</int></value></member></struct> <struct><member><name>entry</name><value><int>11</int></value></member><member><name>pid</name><value><int>5876</int></value></member><member><name>rank</name><value><int>5</int></value></member><member><name>used</name><value><int>4642360</int></value></member><member><name>free</name><value><int>467988</int></value></member><member><name>real_used</name><value><int>5823468</int></value></member></struct> <struct><member><name>entry</name><value><int>12</int></value></member><member><name>pid</name><value><int>5877</int></value></member><member><name>rank</name><value><int>6</int></value></member><member><name>used</name><value><int>4618200</int></value></member><member><name>free</name><value><int>493396</int></value></member><member><name>real_used</name><value><int>5798060</int></value></member></struct> <struct><member><name>entry</name><value><int>13</int></value></member><member><name>pid</name><value><int>5878</int></value></member><member><name>rank</name><value><int>7</int></value></member><member><name>used</name><value><int>4618200</int></value></member><member><name>free</name><value><int>493396</int></value></member><member><name>real_used</name><value><int>5798060</int></value></member></struct> <struct><member><name>entry</name><value><int>14</int></value></member><member><name>pid</name><value><int>5884</int></value></member><member><name>rank</name><value><int>4294967292</int></value></member><member><name>used</name><value><int>4035956</int></value></member><member><name>free</name><value><int>497228</int></value></member><member><name>real_used</name><value><int>5307880</int></value></member></struct> </value> </param> </params> </methodResponse>

2 3

INVITE proxy auth
by Marc Soda 04 Mar '14

04 Mar '14

Hey all, I have a pretty general SIP question that I'm hoping some of you can shed some light on. I hope this ok for the list. I am setting up a SIP proxy with Kamailio. The backend server (Asterisk in my case) requires authentication. Is it standard/best practice to require a proxy to authenticate to a backend server for INVITEs? I am already registering, with authentication, on behalf of the client, i.e, the client registers to the proxy, then the proxy registers to the backend server, all with authentication. I was hoping not to have to do this on INVITEs, but if I don't I'm left with the following: client proxy backend | -------INVITE-------> | | | <--------407--------- | | | ---------ACK--------> | | | ----INVITE(auth)----> | | | <--------100--------- | | | | -------INVITE-------> | | | <--------401--------- | | | ---------ACK--------> | | <--------401--------- | | | ---------ACK--------> | | | ----INVITE(auth)----> | | | <--------100--------- | | | | ----INVITE(auth)----> | | | <--------100--------- | | | <---------OK--------- | | <---------OK--------- | | | ---------ACK--------> | | | | ---------ACK--------> | It works, but, it's terrible... Before I try to make it work differently, what do you all think it should do? Marc

2 1

New official Debian and Ubuntu repository
by Victor Seva 04 Mar '14

04 Mar '14

The new build system for Debian and Ubuntu packages is now in place. This service is kindly sponsored by SipWise [0] thanks to Andreas Granig [1]. Sipwise is providing the hosting and man power to create and manage this new system. deb.kamailio.org is based on jenkins-debian-glue[2] project running on AWS EC2 environment thanks to Michael Prokop [3] and myself. All the needed files, scripts and info to reproduce this system is kept public at [4]. In [5] is described all the repositories available. * nightly builds are been built if a change is detected in the branch, once by night. - kamailiodev-nightly branch: - 'master' distributions: jessie, wheezy, squeeze, precise - kamailio41-nightly branch: - '4.1' distributions: jessie, wheezy, squeeze, precise - kamailio40-nightly branch: - '4.0' distributions: lenny, squeeze, wheezy, lucid, precise - kamailio33-nightly branch: - '3.3' distributions: lenny, squeeze, wheezy, lucid, precise * tags are been built if a new tag is detected once by night. - kamailio41 branch: - '*/tags/4.1*' distributions: jessie, wheezy, squeeze, precise - kamailio40 branch: - '*/tags/4.0*' distributions: lenny, squeeze, wheezy, lucid, precise - kamailio33 branch: - '*/tags/3.3*' distributions: lenny, squeeze, wheezy, lucid, precise Now there is no 4.1.1 package built so the default kamailio repository is pointing to a empty repository. As soon as we release 4.1.2 this will be fixed. Regards, Victor Seva ( kamailio admin hat on ) [0] http://www.sipwise.com/ [1] http://www.kamailio.org/w/andreas-granig/ [2] https://github.com/mika/jenkins-debian-glue [3] http://michael-prokop.at/ [4] https://github.com/sipwise/kamailio-deb-jenkins [5] http://deb.kamailio.org/index.html

4 3

Re: [SR-Users] Regd. Stored procedure support in Kamailio
by Alex Balashov 04 Mar '14

04 Mar '14

You can executed any SQL statements you want through 'sqlops', including invocation of stored procedures. Our Kamailio-based Class 4 routing/trunking product is built almost entirely on Postgres stored procedures. We have dozens of them. As to whether they are "really needed", I don't know how to answer that. :-) In our case, we decided they were really needed because they offer the opportunity to execute complex business logic beyond what Kamailio's relatively primitive route scripting language can offer, while eliminating unnecessary back-and-forth data interchange between Kamailio and the database. Stored procedures and triggers also execute in a transactional manner, which is additionally beneficial. Shankar <shankar.rk(a)plintron.com> wrote: >Hello All, > > > >Does Kamailio support invoking stored procedures instead of sending >plain DB >queries already? > > > >We have been asked to migrate to stored procedures. I am trying to >estimate >the effort involved in migrating Kamailio code to support stored >procedure. > > > >Other question that comes to my mind is whether stored procedures are >really >needed in Kamailio. Can someone please clarify? > > > >Regards, > >Shankar > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >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 -- Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0671 Web: http://www.evaristesys.com/, http://www.alexbalashov.com

1 0

Regd. Stored procedure support in Kamailio
by Shankar 04 Mar '14

04 Mar '14

Hello All, Does Kamailio support invoking stored procedures instead of sending plain DB queries already? We have been asked to migrate to stored procedures. I am trying to estimate the effort involved in migrating Kamailio code to support stored procedure. Other question that comes to my mind is whether stored procedures are really needed in Kamailio. Can someone please clarify? Regards, Shankar

1 0

03 Mar '14

I have a Kamailio server setup which is registers to a back end server on behalf of endpoints. The endpoints can register to Kamailio but Kamailio is failing to register to the server when I put a NAT device in front of it. Without the NAT device it works fine. The problem is the 401 that comes back seems to be ignored by Kamailio. I have a failure route setup to auth, but it is never hit. I see the 401 in onrely_route, but not the failure_route. I'm assuming it's a NAT issue because removing the device fixes the issue. Anyone have any ideas? The 401 being ignored: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.0.10.11;branch=z9hG4bKe5d6.178378f7.0;received=198.XXX.XXX.XXX Via: SIP/2.0/UDP 127.0.0.1:12354 ;rport=6545;received=198.XXX.YYY.YYY;branch=z9hG4bK-1879-1-3 From: <sip:sip7878_spqa@64.YYY.YYY.YYY>;tag=1 To: <sip:sip7878_spqa@64.YYY.YYY.YYY>;tag=as00e32130 Call-ID: 1-1879(a)127.0.0.1 CSeq: 2 REGISTER User-Agent: CoreDialPBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="fe-c7c5-9o.domain.com", nonce="151e4f60" Content-Length: 0 Thanks, Marc

2 6

usrloc preload
by Victor V. Kustov 03 Mar '14

03 Mar '14

Hi all! Please give expanded tips about usrloc preload(). What exactly it doing? modparam("usrloc", "db_mode", 0) modparam("usrloc", "preload", "location") This case kamailio load from db on startup and operate in memory after? -- WBR, Victor JID: coyote(a)bks.tv JID: coyote(a)bryansktel.ru I use FREE operation system: 3.12.9-calculate GNU/Linux

3 5

Ubuntu precise apt repositories unavailable
by Josef Stautner 03 Mar '14

03 Mar '14

Goor morning community, I received a notification that the repositories for Ubuntu Precise are not available anymore. /W: Failed to fetch //http://deb.kamailio.org/kamailio/dists/precise/Release.gpg// Could// //not connect to deb.kamailio.org:80 (87.106.140.63). - connect (110: Connection timed out)// / / //W: Failed to fetch //http://deb.kamailio.org/kamailio/dists/precise/main/source/Sources//// //Unable to connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/binary-i386/Packages// Unable to// //connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/i18n/Translation-en_US// Unable to// //connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/i18n/Translation-en// Unable to// //connect to deb.kamailio.org:http:// / After I tried manually to fetch new updates I got a connection and downloaded some data but then the connection timed out. Is this just a temporary probleme and are there any fallback mirrors? Thanks in advance Josef Stautner

2 2

Adding Path header for the current request.
by MAXX ... 02 Mar '14

02 Mar '14

I found the solution myself, anyone having a similar issue in the future can use msg_apply_changes() from textopsx module after append_hf line.

1 0

Adding Path header for the current request.
by MAXX ... 02 Mar '14

02 Mar '14

Hello, I need to add a Path header to the current request so the save method of registrar module will save the location with the path value to the db. I made the necessary settings for the registrar module but I couldn't be able to add the header. Neither "append_hf" nor "add_path" of path module works since they don't add the header to the currently processing request. $hdr pseudovariable is readonly so I couldn't modify it as well. What can I do to make this happen? Also the reason I need this is to let people registered to different registrars to be able to call each other via their current tls connections to their respective registrars. Thanks In Advance.

1 0

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