- sr-users - kamailio.org

msilo config
by Peter Villeneuve 05 Mar '14

05 Mar '14

Hi, Can someone share a working msilo config for 4.1.1? I've tried following older tutorials out there but they no longer seem to apply. I just want to test out msilo with the default kamailio config in 4.1.1, but the current example in http://kamailio.org/docs/modules/4.1.x/modules/msilo.html doesn't work for me. Specifically, I get an error regarding the syntax in t_on_failure("1"); Any help or pointers appreciated. Thanks

2 5

Incorrect Contact address
by Marc Soda 05 Mar '14

05 Mar '14

I have Kamailio setup as a proxy in front of a backend server (Asterisk). When I make a call through the proxy, the Contact header in the 200 OK that is returned to the client has the IP of the backend server in it. Thus, the client is sending it's ACK directly to the backend server. Is there a special method to rewrite the Contact header to be Kamailio's IP? Where is a good place in the config to do this? (my config is loosely based on this: http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb) Thanks! Marc

4 5

Re: [SR-Users] [Kamailio-Business] [sr-dev] New official Debian and Ubuntu repository
by Vik Killa 05 Mar '14

05 Mar '14

Can someone update the wiki page? I was confused for days on this: http://www.kamailio.org/dokuwiki/doku.php/packages:debs On Wed, Mar 5, 2014 at 8:21 AM, Vik Killa <vipkilla(a)gmail.com> wrote: > Can someone update the wiki page? I was confused for days on this: > http://www.kamailio.org/dokuwiki/doku.php/packages:debs > > > On Tue, Mar 4, 2014 at 6:54 AM, Klaus Darilion < > klaus.mailinglists(a)pernau.at> wrote: > >> Thanks to all involved >> >> >> On 03.03.2014 14:16, Victor Seva wrote: >> >>> 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 >>> >>> _______________________________________________ >>> sr-dev mailing list >>> sr-dev(a)lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev >>> >>> >> _______________________________________________ >> Kamailio (OpenSER) - Business mailing list >> Business(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/business >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/business >> > >

3 3

Reload memory leaks issues.
by Uri Shacked 05 Mar '14

05 Mar '14

Hi, kamailio ver 3.3.6. I load approximately 100Mb of data into memory. And my shared memory size is 4Gb. It is CARRIERROUTE, DIALPLAN, MTREE and HTABLE combimations. My system has to be synced with DB that is being updated frequently. So, I reload the data every 1-2 minutes. I notice that the shared memory usage is increasing at 1% every 18-19 reloads. I use mem_join = 1 and no mem_join at all. I compiled with C_DEFS+= -DMEM_JOIN_FREE and even with -DF_MALLOC. Tried different options, still, the issue keeps on going and it is very frustrating... Anyone has the same problem? BR, Uri

1 1

MSRP Relay
by Nandini madhu 05 Mar '14

05 Mar '14

Dear All, Can anybody please tel me, are there any MSRP relay (RFC 4976) compliant SIP clients for Android Platform ? Sorry for asking this question which is out of relevant here. Waiting for somebody's comments on this Regards, Nandini

1 0

Kamailio World 2014 - Exhibitors
by Daniel-Constantin Mierla 05 Mar '14

05 Mar '14

During Kamailio World 2014, the companies IT Center, Digium, Sipgate, NG Voice, Asipto and FhG Fokus will provide all day long demos and presentations of their products and services. You can contact them in advance to schedule an appointment if you want to reserve proper time to discuss about their offerings: - http://conference.kamailio.com/k02/exhibitors/ It is less than one month till the start of the event, the agenda is pretty much finalized: - http://conference.kamailio.com/k02/schedule/ It has over 30 sessions presented by world wide speakers, from technical tutorials to business use cases, with topics such WebRTC, IMS, anti-fraud & VoIP security, scalability with OpenStack, real time charging, various Kamailio use cases, Asterisk, FreeSwitch and SEMS. Once again we are grateful to event sponsors -- Asipto, FhG Fokus, Sipwise, IT Center, Sipgate, Simwood, Digium, NG Voice -- without their contributions is impossible to bring such an excellent group of speakers and support event logistics: - http://conference.kamailio.com/k02/sponsors/ Hurry up if you don't want to miss this event, it is no alternative in Europe for meeting professionals in large real time communications deployments and open source telephony. Registration details are available at: - http://conference.kamailio.com/k02/registration/ See you in Berlin! -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

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

REGISTER failure_route 401 problem
by Marc Soda 03 Mar '14

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

XAVP in 3.1.6
by Jijo 01 Mar '14

01 Mar '14

Hi I'm trying to use XAVP but the script is showing parsing error. Do i need to include any module? I rebuild kamailio using the flag WITH_XAVP but didn' help. route[0] { $xavp(a=>bar) = 'bar'; } S-154:~ # /usr/sbin/kamailio -c -f /etc/kamailio/kam86x2.cfg loading modules under /usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ 0(20184) ERROR: <core> [pvapi.c:516]: error searching pvar "xavp" 0(20184) ERROR: <core> [pvapi.c:720]: wrong char [a/97] in [$xavp(a=>bar)] at [6 (5)] 0(20184) : <core> [cfg.y:3461]: parse error in config file /etc/kamailio/kam86x2.cfg, line 555, column 5-17: unknown script pseudo variable $xavp(a=>bar) ERROR: bad config file (1 errors) Segmentation fault (core dumped) S-154:~ # /usr/sbin/kamailio -V version: kamailio 3.1.6 (i386/linux) af51bc 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, DBG_QM_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, PKG_SIZE 25MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: af51bc compiled on 14:11:43 Feb 28 2014 with gcc 4.7.1 THANKS

1 0

How to configure Kamailio + Asterisk (on same server) to route between several disjoint networks?
by Alex Villacís Lasso 01 Mar '14

01 Mar '14

As part of a project, I have installed a CentOS 6 test system (a virtual machine) with Asterisk 11.7.0 and Kamailio 4.1.1 downloaded from http://download.opensuse.org/repositories/home:/kamailio:/telephony/CentOS_…. I am trying to setup a combination of Kamailio and Asterisk that will route SIP calls between all the configured networks in the test setup, in addition to being capable of using Asterisk in order to handle PSTN and IAX2 calls. I am using the following online guide to modify my kamailio.cfg: http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb . Based on this, I generated the attached patch for my Kamailio configuration My test setup has the following network interfaces: eth0: 10.1.0.3, on network 10.1.0.0/24 eth1: 192.168.5.18, on network 192.168.0.0/16 eth2: 10.0.0.2, on network 10.0.0.0/24 lo: 127.0.0.1, on network 127.0.0.0/8 I first configured Asterisk with SIP realtime support (with no Kamailio), and tested that all configured accounts could register from all interfaces, and that Asterisk could properly route media between any two disjoint networks. After installing Kamailio, the guide called for disabling Asterisk SIP authentication by setting passwords to NULL, and moving Asterisk SIP to a different port (I chose 5080) so that Asterisk and Kamailio could run on the same machine. At this point, the SIP clients (one softphone and one VoIP phone) can now register at port 5080 without authentication. In the process of changing my Kamailio configuration according to the attached patch, the guide says that I should configure the IP of the network interface as the value of asterisk.bindip and kamailio.bindip. After performing all required changes, Kamailio does take over authentication at the default port of 5060. Testing shows that for all SIP clients with IPs belonging to the same network as the configured asterisk.bindip, both registration and media exchange work correctly, and that the SIP clients are still capable of calling into the Asterisk dialplan, and therefore, routing into Asterisk resources. For SIP clients in disjoint networks, the failure mode depends on whether mhomed is enabled or disabled in kamailio.cfg. For mhomed=0 (or unset), I have the following situation between the two SIP clients (one at 10.1.0.1, the other at 10.0.0.3), as shown by "sip show peers" in Asterisk (when asterisk.bindip is set to 192.168.5.18): Privilege escalation protection disabled! See https://wiki.asterisk.org/wiki/x/1gKfAQ for more details. Name/username Host Dyn Forcerport ACL Port Status Description Realtime gatitoscomx64am_100/gatit 10.1.0.3 D N A 5060 OK (16 ms) Cached RT gatitoscomx64am_101/gatit 10.0.0.2 D N A 5060 OK (36 ms) Cached RT gatitoscomx64am_IM101 (Unspecified) D N A 0 UNREACHABLE Cached RT 3 sip peers [Monitored: 2 online, 1 offline Unmonitored: 0 online, 0 offline] If I try to call from one SIP client to an extension in the Asterisk dialplan that does NOT map to a SIP client in a disjoint network, the media exchange works (with negotiatied media IP in the same network as the SIP client), regardless of whether the calling client belongs in the same network as asterisk.bindip. If I try to call from the same SIP client to an extension that maps to a SIP client in a disjoint network, the call fails, and I get the spoken message about the user at extension such-and-such being unavailable. Additionally, I get the following error message in the Asterisk logs: [Feb 25 16:53:14] NOTICE[13807][C-00000003] chan_sip.c: Call from 'gatitoscomx64am_101' (10.0.0.2:5060) to extension 'gatitoscomx64am_101' rejected because extension not found in context 'gatitoscomx64am-from-internal'. For mhomed=1, the output of "sip show peers" changes to the following (when asterisk.bindip is set to 192.168.5.18): Privilege escalation protection disabled! See https://wiki.asterisk.org/wiki/x/1gKfAQ for more details. Name/username Host Dyn Forcerport ACL Port Status Description Realtime gatitoscomx64am_100/gatit 192.168.5.18 D N A 5060 OK (19 ms) Cached RT gatitoscomx64am_101/gatit 192.168.5.18 D N A 5060 OK (34 ms) Cached RT gatitoscomx64am_IM101 (Unspecified) D N A 0 UNREACHABLE Cached RT 3 sip peers [Monitored: 2 online, 1 offline Unmonitored: 0 online, 0 offline] From wireshark sniffing, I can see that the SDP payload sent from the client to Kamailio contains the IP address of the client, which is accessible by both Kamailio and Asterisk. However, the SDP payload in the OK response sent back to the client contains a media port with the IP address of asterisk.bindip (the one that appears in the "Host" column in the "sip show peers" report), not the IP address of the interface that received the INVITE. This results in broken media negotiation for all SIP clients belonging to networks other than the one that contains asterisk.bindip. In either case, I have to hardcode an IP address in kamailio.cfg, which is not satisfactory. IPs assigned to interfaces can and do change, especially if the interface is managed with DHCP. To escape this, I tried setting asterisk.bindip to 127.0.0.1, but since apparently localhost is also a disjoint network, all of the above described problems apply. Related to these issues, I am not satisfied with leaving Asterisk running unauthenticated SIP at the nonstandard port. Somebody suggested blocking the port with iptables, but I do not want to rely on this alone. I tried setting bindaddr=127.0.0.1 so that only Kamailio gets to talk to Asterisk, but this also has the side effect of restricting the media negotiation to localhost only. I am asking for help in building a Kamailio/Asterisk configuration that will support all of the networks and route media between all of them, just as if Asterisk were the only program running. Ideally, the configuration should not encode the current IP of any interface (except, maybe, localhost). What is the official name (if any) for the setup I am describing above? Does it have a standard setup procedure? How is Asterisk secured so that clients cannot bypass authentication using the Asterisk SIP port directly?

2 4

Replacing an ACME Packet Net-Net SBC
by Francesco Maria Magnini 01 Mar '14

01 Mar '14

Hi, I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly: - it is used as a SIP endpoint for SIP client registrations - it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks - it is used for NAT traversal In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?

13 22

prevent relaying to myself
by Henry Fernandes 01 Mar '14

01 Mar '14

Is there a way to prevent relaying requests to myself in route[RELAY]? -H

3 3

fresh kamailio installation unable to connect through jitsi
by Michelle Jun 01 Mar '14

01 Mar '14

hi i just finished installation of kamailio on centos 6 64 bit following the docs on http://www.fredposner.com/voip/1457/kamailio-behind-nat/ the user able to chat through jitsi just fine, but when calling, one user able to connect, while the other showing only "connecting" (audio/video) any idea what did i do wrong? here is the /var/log./messages thank you Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tag 2d9e2107;1 requested, type strong Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session on a port 25982 created, tag 2d9e2107;1 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: pre-filling caller's address with 192.168.168.1:5000 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tag 2d9e2107;2 requested, type strong Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session on a port 25192 created, tag 2d9e2107;2 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: pre-filling caller's address with 192.168.168.1:5002 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: pre-filling callee's address with 192.168.168.1:5000 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: pre-filling callee's address with 192.168.168.1:5002 Feb 26 17:43:39 black96 /usr/local/sbin/kamailio[4456]: NOTICE: acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1393465419;method=INVITE;from_tag=2d9e2107;to_tag=7175e4ad;call_id=2f6e045de764ae9e9252352d952359ae@0 :0:0:0:0:0:0:0;code=200;reason=OK;src_user=handy;src_domain=184.105.148.231;src_ip=192.168.168.1;dst_ouser=harri;dst_user=harri;dst_domain=192.168.113.2 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:40 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:40 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:42 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:42 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:process_rtp: session timeout Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: session on ports 25982/27044 is cleaned up Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:process_rtp: session timeout Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: session on ports 25192/22432 is cleaned up Feb 26 17:45:23 black96 rtpproxy[4293]: INFO:handle_command: delete request failed: session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tags 2d9e2107/7175e4ad not found Feb 26 17:45:53 black96 /usr/local/sbin/kamailio[4460]: NOTICE: acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1393465553;method=BYE;from_tag=2d9e2107;to_tag=7175e4ad;call_id=2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0;code=408;reason=Request Timeout;src_user=handy;src_domain=184.105.148.231;src_ip=192.168.168.1;dst_ouser=harri;dst_user=;dst_domain=184.105.148.231

3 7

What is required to enable TLS on non-standard port?
by info＠vintageelectronics.ca 01 Mar '14

01 Mar '14

Kamailio running in Fedora 19 box. The client (Jitsi) can only connect over TCP. If connecting over UDP, the clients connect, but cannot send/receive messages. Cannot connect over TLS at all. Ultimately I will need to run with TLS over 5065 port or higher. Tried using different listen directives, different port directive, but kamailio either does not start, or only listening on one TCP port. I've set up two SRV records, one for _sip on port 5065 and another for _sips on port 5066. Both pointing to the Fedora box. In Jitsi I have to specify port # and when I set it to 5065 over TCP it works, but 5066 over TLS never connects. What am I doing wrong? Thank you.

3 8

Kamailio crashes with double qm_free
by Tuan Viet Nguyen 28 Feb '14

28 Feb '14

Hello, I have another kamailio crash with 4.1.1. The scenario is simple: + call a number, fail + retry on another peer, fails In this case, I use t_reply("404", "Not found") then exit. It seems that we have a double qm_free. Log file Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29595]: WARNING: tm [t_lookup.c:1536]: t_unref(): WARNING: script writer didn't release transaction Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29583]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f9dedb3e110), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29627]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19 Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29576]: ALERT: <core> [main.c:775]: handle_sigs(): child process 29583 exited by a signal 6 Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29576]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated core.kamailio.29583 (gdb) bt full #0 0x00007f9df6afb475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f9df6afe6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7f9ded878000, p=0x7f9dedb3e110, file=0x7f9df515b62d "tm: h_table.c", func=0x7f9df515b7d8 "free_cell", line=157) at mem/q_malloc.c:470 f = 0x7f9dedb3e0e0 size = 140316274568736 next = 0x0 prev = 0x0 __FUNCTION__ = "qm_free" #3 0x00007f9df50ee2b3 in free_cell (dead_cell=0x7f9dedb39490) at h_table.c:157 b = 0x0 i = 2 rpl = 0x0 tt = 0x177dd596e30 foo = 0x7fffdd597400 cbs = 0x7f9dedb39490 cbs_tmp = 0x7fffdd596f10 __FUNCTION__ = "free_cell" #4 0x00007f9df511c662 in t_unref (p_msg=0x7f9df68bfdb0) at t_lookup.c:1546 kr = 12 __FUNCTION__ = "t_unref" #5 0x00007f9df5146f4d in w_t_unref (foo=0x7f9df68bfdb0, flags=2147483649, bar=0x0) at tm.c:765 No locals. #6 0x00000000004d6f27 in exec_post_script_cb (msg=0x7f9df68bfdb0, type=REQUEST_CB_TYPE) at script_cb.c:195 cb = 0x7f9df68a97d0 flags = 2147483649 #7 0x00000000004a6e24 in receive_msg (buf=0x921620 "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"..., len=375, rcv_info=0x7fffdd5970d0) at receive.c:228 msg = 0x7f9df68bfdb0 ctx = {rec_lev = -581341280, run_flags = 32767, last_retcode = 5, jmp_env = {{__jmpbuf = {8857080, 0, 0, 0, 0, 140316433164786, 17179869189, 0}, __mask_was_saved = 8856992, __saved_mask = {__val = {1, 140316271892032, 1656210553, 3713626240, 1024, 8008593472, 140316271892032, 140736907014208, 5472467, 1577608202, 140316271892032, 50195, 140316271892032, 140316426284544, 8282899704, 140736907014272}}}}} ret = 0 inb = {s = 0x921620 "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"..., len = 375} __FUNCTION__ = "receive_msg" #8 0x000000000053c0d8 in udp_rcv_loop () at udp_server.c:536 len = 375 buf = "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"... tmp = 0x13e0751a0eb8aa4f <Address 0x13e0751a0eb8aa4f out of bounds> from = 0x7f9df68a5408 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {1577608202, 4290224}, addr32 = {1577608202, 0, 4290224, 0}, addr16 = {25610, 24072, 0, 0, 30384, 65, 0, 0}, addr = "\nd\b^\000\000\000\000\260vA\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = { 117990410, 0}, addr32 = {117990410, 0, 0, 0}, addr16 = {25610, 1800, 0, 0, 0, 0, 0, 0}, addr = "\nd\b\a", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304\nd\b^\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 1577608202}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1577608202, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7f9df6704da8, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #9 0x000000000046ec98 in main_loop () at main.c:1617 i = 5 pid = 0 si = 0x7f9df6704da8 si_desc = "udp receiver child=5 sock=10.100.8.7:5060\000\000\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000y\304\267b\000\000\000\000\260vA\000\000\000\000\000\000tY\335\377\177", '\000' <repeats 18 times>, "@rY\335\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #10 0x0000000000471c38 in main (argc=5, argv=0x7fffdd597408) at main.c:2533 cfg_stream = 0x164c010 c = -1 r = 0 tmp = 0x7fffdd597438 "\211~Y\335\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 4192398120 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" core.kamailio.29576 (gdb) bt full #0 0x00007f9df6afb475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f9df6afe6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7f9ded878000, p=0x7f9dedb3e110, file=0x7f9df515b62d "tm: h_table.c", func=0x7f9df515b7d8 "free_cell", line=157) at mem/q_malloc.c:470 f = 0x7f9dedb3e0e0 size = 140316274568736 next = 0x0 prev = 0x0 __FUNCTION__ = "qm_free" #3 0x00007f9df50ee2b3 in free_cell (dead_cell=0x7f9dedb39490) at h_table.c:157 b = 0x7f9df464b480 "dialog: dlg_cb.c" i = 0 rpl = 0x7f9df464b8e0 tt = 0x7f9df4a8cc75 foo = 0x5000548a29 cbs = 0xd000000001 cbs_tmp = 0x1edb086c8 __FUNCTION__ = "free_cell" #4 0x00007f9df50ef480 in free_hash_table () at h_table.c:441 p_cell = 0x7f9dedb39490 tmp_cell = 0x7f9deda23d90 i = 36299 __FUNCTION__ = "free_hash_table" #5 0x00007f9df5102d35 in tm_shutdown () at t_funcs.c:122 __FUNCTION__ = "tm_shutdown" #6 0x00000000004f8101 in destroy_modules () at sr_module.c:817 t = 0x7f9df670fd50 foo = 0x7f9df670f588 __FUNCTION__ = "destroy_modules" #7 0x00000000004689b2 in cleanup (show_status=1) at main.c:560 memlog = 32669 __FUNCTION__ = "cleanup" #8 0x0000000000469aab in shutdown_children (sig=15, show_status=1) at main.c:702 __FUNCTION__ = "shutdown_children" #9 0x000000000046b146 in handle_sigs () at main.c:793 chld = 0 chld_status = 134 memlog = 0 __FUNCTION__ = "handle_sigs" #10 0x000000000046f549 in main_loop () at main.c:1746 i = 8 pid = 29627 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000y\304\267b\000\000\000\000\260vA\000\000\000\000\000\000tY\335\377\177", '\000' <repeats 18 times>, "@rY\335\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x0000000000471c38 in main (argc=5, argv=0x7fffdd597408) at main.c:2533 cfg_stream = 0x164c010 c = -1 r = 0 tmp = 0x7fffdd597438 "\211~Y\335\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 4192398120 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" Thanks for your help

2 2

kamailio crashes
by Tuan Viet Nguyen 28 Feb '14

28 Feb '14

Hello, I have a crash with the following scenario: I try to route an INVITE to a remote host, it fails, I route to the second suing the dispatcher module. It fails the second time and I stop the call. It seems that I did not release the transaction in this case 93454 Feb 28 11:39:08 kamailio23 /usr/local/sbin/kamailio[20225]: WARNING: tm [t_lookup.c:1536]: t_unref(): WARNING: script writer didn't release transaction And then, Kamailio receives BYE of other dialogs and it crashes Here is core bt of 2 kamailio processes (4.1.1) (gdb) bt full #0 0x0000000000534e4e in timer_list_expire (t=1283469267, h=0x7ff9219e99b8, slow_l=0x7ff9219e9c88, slow_mark=12) at timer.c:883 tl = 0x7ff921c6b8f0 ret = 32767 #1 0x00000000005351ba in timer_handler () at timer.c:959 saved_ticks = 1283469267 run_slow_timer = 0 i = 12 __FUNCTION__ = "timer_handler" #2 0x0000000000535453 in timer_main () at timer.c:998 No locals. #3 0x000000000046efa2 in main_loop () at main.c:1688 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000\243Mgf\000\000\000\000\260vA\000\000\000\000\000\020\201\351a\377\177", '\000' <repeats 18 times>, "P\177\351a\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #4 0x0000000000471c38 in main (argc=5, argv=0x7fff61e98118) at main.c:2533 cfg_stream = 0x1970010 c = -1 r = 0 tmp = 0x7fff61e98148 "\211\236\351a\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 519948236 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" (gdb) bt full #0 0x00007ff92abf3475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007ff92abf66f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7ff921970000, p=0x7ff921c3b940, file=0x7ff92925362d "tm: h_table.c", func=0x7ff9292537d8 "free_cell", line=178) at mem/q_malloc.c:470 f = 0x7ff921c3b910 size = 5600 next = 0x7fff61e97ac0 prev = 0x7ff9291e571e __FUNCTION__ = "qm_free" #3 0x00007ff9291e64a9 in free_cell (dead_cell=0x7ff921c6b870) at h_table.c:178 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x5000548a29 cbs = 0x0 cbs_tmp = 0x7ff921c3b940 __FUNCTION__ = "free_cell" #4 0x00007ff9291e7480 in free_hash_table () at h_table.c:441 p_cell = 0x7ff921c6b870 tmp_cell = 0x7ff921a159f0 i = 37066 __FUNCTION__ = "free_hash_table" #5 0x00007ff9291fad35 in tm_shutdown () at t_funcs.c:122 __FUNCTION__ = "tm_shutdown" #6 0x00000000004f8101 in destroy_modules () at sr_module.c:817 t = 0x7ff92a807d50 foo = 0x7ff92a807588 __FUNCTION__ = "destroy_modules" #7 0x00000000004689b2 in cleanup (show_status=1) at main.c:560 memlog = 32761 __FUNCTION__ = "cleanup" #8 0x0000000000469aab in shutdown_children (sig=15, show_status=1) at main.c:702 __FUNCTION__ = "shutdown_children" #9 0x000000000046b146 in handle_sigs () at main.c:793 chld = 0 chld_status = 139 memlog = 0 __FUNCTION__ = "handle_sigs" #10 0x000000000046f549 in main_loop () at main.c:1746 i = 8 pid = 20250 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000\243Mgf\000\000\000\000\260vA\000\000\000\000\000\020\201\351a\377\177", '\000' <repeats 18 times>, "P\177\351a\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x0000000000471c38 in main (argc=5, argv=0x7fff61e98118) at main.c:2533 cfg_stream = 0x1970010 c = -1 r = 0 tmp = 0x7fff61e98148 "\211\236\351a\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 519948236 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" Thank you for your help

2 1

Add Header
by Tony Turner 28 Feb '14

28 Feb '14

Hi, customers PBX----trunk-----kamailio------------freeswitch-------------carrier We already add Trusted IP’s via SIREMIS 4.0 is it possible with Kamailio to have customers calls come in on a trusted IP and when they send calls we add a header with a [client id] which we can remove on the next ip switch upstream So example Call comes in from customer with IP: their trusted IP source xx.xx.xx.xx add header with their client ID route to PSTN Then my upstream switch will process the customers call and remove the header before sending to our voip carrier. Basically my ip switch will evaluate the client id header for billing, process and strip the header back out. Thanks Tony

2 2

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