- sr-users - kamailio.org

Create ISUP Body
by Duarte Rocha 20 Feb '18

20 Feb '18

Hey Everyone I'm setting up a load testing scenario for my Kamailio. In order to do that i've created another Kamailio to answer "200 OK" to an Invite in order to simulate a call being answered. One of the scenarios I need to test is reading values from the ISUP IAM or ACM body. Here's the code on the Kamailio that replies with 200 : $var(acm) = "06 02 04 01 2c 01 fb 0c 08 83 10 19 7c 82 12 15 00 36 01 19 40 01 00 39 06 2c c0 36 c0 40 c0 00"; set_reply_body("$var(acm)","application/isup;base=itu-t92+;version=etsi356"); if( is_method("INVITE") && !has_totag() ) { · xnotice("First Invite"); send_reply("200","OK"); } However, when i use this and i do a pcap i get a "Message Type: Overload", which doesn't support optional parameters. What am i doing wrong ? Are there other methods to setup a simple ISUP part without hex ? Thanks in advance

1 0

Kamailio mod ALIAS_DB: multiple aliases
by Stefan Rüetschli 20 Feb '18

20 Feb '18

Hello Kamailio-Users I'm using kamailio 5.1 with Alias_DB module. My subscribers register with a username like 0000001, 0000002 etc... Every user has a list of multiple aliases which they can use on their SIP-Trunk. I want to avoid that the user can use any alias for outgoing calls, only the aliases which are boud to his username in the aliases-db. So, if the user uses an alias which does not belong to him, i want to overwrite it to the first alias for his username in the aliases-db. At the moment, the function alias_db_find returns me the last alias found in the db. Is there any way to do it? Or is there a way to extend the dbaliases with a new column marking the "primary" alias for an account?|||| This would be the perfect solution. Regards Stefan

2 2

Info: Kamailio World 2018 - Preview With 15 Sessions
by Daniel-Constantin Mierla 20 Feb '18

20 Feb '18

Hello, less than 3 months till the start of the 6th edition of Kamailio World Conference, time if flying fast! About one week ago we published the details for a group of accepted speakers, today we made a selection of sessions at the Kamailio World 2018. We had more proposals than we could accommodate, we are trying hard to fit in as many as possible, taking also in consideration the feedback from the participants at the past editions. For now you can head to the Schedule page and see the details of 15 sessions, from both workshops and conference days: https://www.kamailioworld.com/k06/schedule/ A very divers range of topics, from using Kamailio for emergency services (112/911), scaling with Redis backend, deploying in a containerized environment with Docker and Kubernetes, how to migrate the SIP routing logic to rich KEMI languages such as Lua, Python or Javascript, unit testing for Kamailio and test driven deployments, to blockchains in telephony, using Kamailio and FreeSwitch together, or latest updates from Asterisk PBX. The IMS/VoLTE workshop is going to show what you can do with latest Kamailio in mobile networks. And, of course, we have the very popular two sessions that never missed a Kamailio World edition: Dangerous Demos with James Body and VUC Visions with Randy Resnick. The details for other speakers and sessions will be published in the near future, stay tuned! Do not miss Kamailio World Conference 2018, it is going to be another great edition! You can register now at: https://www.kamailioworld.com/k06/registration/ Looking forward to meeting many of you at the next Kamailio World Conference, during May 14-16, 2018, in Berlin, Germany! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

IMS: maybe a bug in S-CSCF: should we create an issue?
by Valentin Christoph 20 Feb '18

20 Feb '18

Hi all, We are using kamailio 5.1.0 as S-CSCF as follows: We have two machines and two kamailio instances, one on each machine, both working on the same database (together they build one highly available S-CSCF). After registering a user via the first kamailio instance, then the first instance is stopped (simulating an outage), and the HSS sends an RTR to the second instance. However, the second instance does not find the registered user in its cache and it does not access the database --> the deregistration fails. Configuration: kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "enable_debug_file", 0) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "matching_mode", 0) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "db_url", DB_URL) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "db_mode", 2) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "timer_interval", 10) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "timer_procs", 4) Does anyone immediately "see" a mis-configuration, or should we create an issue? Details in the mail below. Thanks, Christoph From: Friedrich Peter Sent: Friday, February 16, 2018 6:38 PM To: Valentin Christoph <Christoph.Valentin(a)kapsch.net> Cc: Onic Roman <Roman.Onic(a)kapsch.net>; Habashizadeh Mahmoud <Mahmoud.Habashizadeh(a)kapsch.net> Subject: AW: Kein RTR Message nachdem SCSCF-1 outage Hello, following scenario at REGISTER of catt subscriber: start with empty db and empty usrloc cache node1(.23): MariaDB [scscf]> select * from impu; Empty set (0.00 sec) [root@vict-ims ~]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net [root@vict-ims ~]# [root@vict-ims2 etc]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net [root@vict-ims2 etc]# After catt REGISTER: catt_subscriber visible in DB and usrloc cache of .23 but missing in usrloc cache of .24 MariaDB [scscf]> select * from impu; +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ | id | impu | barring | reg_state | ccf1 | ccf2 | ecf1 | ecf2 | ims_subscription_data | +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ | 196 | sip:catt178@vict-ims.net | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | | 197 | sip:+4350255872178@vict-ims.net | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | | 198 | tel:+4350255872178 | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ 3 rows in set (0.00 sec) MariaDB [scscf]> [root@vict-ims ~]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net { impu: sip:catt178@vict-ims.net state: registered barring: 0 ccf1: ccf2: ecf1: ecf2: subscription: { impi: catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> service profiles: { 1: { impus: { 1: sip:catt178@vict-ims.net 2: sip:+4350255872178@vict-ims.net 3: tel:+4350255872178 } } } } contacts: { sip:catt178@193.154.113.40:5060;transport=UDP;rinstance=317-catt178: { expires: 3542 client: n/a } } } [root@vict-ims ~]# [root@vict-ims2 etc]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net [root@vict-ims2 etc]# After kamctl stop + kamctl start of .24 catt_subscriber is visible in usrloc cache of (.24): preload_data loads data from db at module init [root@vict-ims2 ~]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net { impu: sip:catt178@vict-ims.net state: registered barring: 0 ccf1: ccf2: ecf1: ecf2: subscription: { impi: catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> service profiles: { 1: { impus: { 1: sip:catt178@vict-ims.net 2: sip:+4350255872178@vict-ims.net 3: tel:+4350255872178 } } } } contacts: { sip:catt178@193.154.113.40:5060;transport=UDP;rinstance=317-catt178: { expires: 2949 client: n/a } } } [root@vict-ims2 ~]# Now deregister catt_subscriber from HSS1: catt_subscriber disappears from db and usrloc cache of (.23) but persists on (.24) as registered in usrloc cache HSS >hss.deregister_subscriber catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> 0 [root@vict-ims ~]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net [root@vict-ims ~]# MariaDB [scscf]> select * from impu; Empty set (0.00 sec) MariaDB [scscf]> [root@vict-ims2 ~]# kamctl kamcmd ulscscf.showimpu sip:catt178@vict-ims.net { impu: sip:catt178@vict-ims.net state: registered barring: 0 ccf1: ccf2: ecf1: ecf2: subscription: { impi: catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> service profiles: { 1: { impus: { 1: sip:catt178@vict-ims.net 2: sip:+4350255872178@vict-ims.net 3: tel:+4350255872178 } } } } contacts: { sip:catt178@193.154.113.40:5060;transport=UDP;rinstance=317-catt178: { expires: 2571 client: n/a } } } [root@vict-ims2 ~]# Scenario of RTR from HSS after REGISTER of catt_subscriber at (.23) and outage of (.23): subscr. visible in db but not visible in usrloc cache of .24 HSS sends diameter RTR message to (.24) and deregister callback in (.24) searches in usrloc cache and does not find catt_subscriber and fails. MariaDB [scscf]> select * from impu; +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ | id | impu | barring | reg_state | ccf1 | ccf2 | ecf1 | ecf2 | ims_subscription_data | +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ | 196 | sip:catt178@vict-ims.net | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | | 197 | sip:+4350255872178@vict-ims.net | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | | 198 | tel:+4350255872178 | 0 | 1 | NULL | NULL | NULL | NULL | catt178(a)vict-ims.net<mailto:catt178@vict-ims.net> sip:catt178@vict-ims.net sip:+4350255872178@vict-ims.net tel:+4350255872178 | +-----+---------------------------------+---------+-----------+------+------+------+------+----------------------------------------------------------------------------------------------------------------------+ 3 rows in set (0.00 sec) Cfg file of (.24): kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "enable_debug_file", 0) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "matching_mode", 0) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "db_url", "cluster://cluster1") kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "db_url", DB_URL) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "db_mode", 2) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "timer_interval", 10) kamailio-scscf/kamailio-scscf-modules.cfg:modparam("ims_usrloc_scscf", "timer_procs", 4) lg P The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

2 4

issue with running kamailio
by justin barnes 20 Feb '18

20 Feb '18

I am installing from githum kamailio 5.0 on my ubuntu-16.04-x86_64 VPS. when I start the kamailio server I get this error : /# /etc/init.d/kamailio start [....] Starting kamailio (via systemctl): kamailio.serviceJob for kamailio.service failed because the control process exited with error code. See "systemctl status kamailio.service" and "journalctl -xe" for details. failed! Ilooking up the status, I get this kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/etc/systemd/system/kamailio.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-02-19 15:23:41 EST; 4h 10min ago Process: 18969 ExecStart=/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GR Feb 19 15:23:41 khynepassion systemd[1]: Starting Kamailio (OpenSER) - the Open Source SIP Server... Feb 19 15:23:41 khynepassion systemd[18969]: kamailio.service: Failed at step EXEC spawning /usr/sbin/kamailio: No such file or directory Feb 19 15:23:41 khynepassion systemd[1]: kamailio.service: Control process exited, code=exited status=203 Feb 19 15:23:41 khynepassion systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Feb 19 15:23:41 khynepassion systemd[1]: kamailio.service: Unit entered failed state. Feb 19 15:23:41 khynepassion systemd[1]: kamailio.service: Failed with result 'exit-code'.

1 0

LCR options as of 2018
by Francisco Valentin Vinagrero 19 Feb '18

19 Feb '18

Hello, I am configuring a Kamailio node that will interface with 3 carriers and will implement Least Cost Routing for around 900 destinations. I have already implemented a quick prototype with the LCR module and I have been reading the CarrierRoute doc and the CGrates site. I don't really need advanced functionality, just: - Re-routing to a backup carrier when the main one is not available. - Ping with OPTIONS to all carriers so I can detect if any of them is not available (à la Dispatcher) - Translate prices from a central DB to routing priorities. - Get some accounting post-call info about the routing decision (acc module) So far, while testing the LCR module I have had some issues with the rule IDs being integers that auto-increment, so the LCR rules need to be referenced from the rule_target table using this numeric ID. I can see some issues when scaling this to 900 lcr_rules and 2700 lcr_rule_targets with 3 priorities. In addition to that, I think the OPTIONS mechanism is just used by the lcr module when a gateway is marked as defunct, but the gateways are not actively monitored in the normal status. Is this correct? I have been considering CarrierRoute, which has a slightly simpler table structure, but I can't find any other advantage for my use case. Regarding CGrates, it looks great but it looks like it exceeds my current needs. For those who have implemented LCR in your kamailios, am I missing something regarding performance, scalability, etc? Are there any newer modules that can implement this, or maybe just a dispatcher-on-steroids setup will do the trick? Cheers, Francisco.

3 6

User state
by Magnus Löfqvist 19 Feb '18

19 Feb '18

Hi, We are running for a customer a kamailio server for user registration and routing of calls. Also using Asterisk for queue management and IVR. Now we are in the progress of writing a web portal where the customers users should be able to see if there collueges are busy in phone or availible. In asterisk I would use hints and listing in events in AMI. But what way are the best in Kamailio? Best Regards Magnus Sent from Nine<http://www.9folders.com/>

2 1

PR1447: first attempt at app_python3
by Anthony Alba 18 Feb '18

18 Feb '18

Hi Daniel and kamailio contributors, I have submitted a PR for app_python3 here: https://github.com/kamailio/kamailio/pull/1447. It is very rough, but would appreciate your feedback. Notes: 1. Almost a verbatim port of app_python; just changing obvious semantics. String->Unicode is practically the only large change. No change to symbol names and export functions so the two modules cannot coexist. (Don't loadmodule "app_python.so" and loadmodule "app_python3.so) 2. Module initialization semantics in Py3 have changed: add the top level modules to the inittab before calling Py_Initialize(). I have done this for KSR and Router. I.e. PyImport_AppendInittab() is called for Router and KSR *before* Py_Initialize() 3. Makefile looks for a python3 binary (PYTHON3 in the Makefile) to get include paths and link libraries. Here is an example compile line for IUS Python 3.6 on CentOS 7 (no native Python3 from RHEL) ## default: needs to find python3 and python3-config ## needs to find both python3.6 and python3.6-config make -C src/ PYTHON3=python3.6 SKIP_MODULES="${SKIP_MODULES}" quiet=verbose module_group_py="app_python3" group_include=py every-module 4. The semantics for GIL and thread management are too different for one-to-one replacements. I have therefore decided to comment out all threading calls. Fortunately, kamailio does not used threads at the moment. This is more complicated than it seems: even with Py2+thread management: there would be deadlocks if kamailio->python2 script->Cython extension with threads(e.g. grpcio). For an MVP it would be best to get it in without thread management. 5. It should backport to 5.1. 6. Tested locally, with a routing scripting making many python_exec() calls Thank you. Anthony Alba

1 1

PUBLISH and ETag
by Cyrille Demaret 16 Feb '18

16 Feb '18

Hi, I'm using Kamailio with presence enabled and Asterisk PJSIP and outbound-publish. My problem is happening when I place 2 consecutive calls from Asterisk : When I make a first call Asterisk sent the following: PUBLISH sip:201@192.168.100.37 SIP/2.0 Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPj4f9c19eb-26d8-4bb1-8f00-e69723a610 82 From: sip:201@mydomain.com;tag=a560e088-9e8a-49f2-a9b1-4a0ec31340bf To: sip:201@mydomain.com Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183 CSeq: 10697 PUBLISH Event: dialog Expires: 180 Max-Forwards: 70 User-Agent: Asterisk PBX 14.6.0 Content-Type: application/dialog-info+xml Content-Length: 247 <?xml version="1.0" encoding="UTF-8"?> early.. Kamailio replies : SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.100.37:5080;rport=5080;branch=z9hG4bKPj4f9c19eb-26d8-4bb1-8f00-e6972 3a61082;received=192.168.100.37 From: sip:201@mydomain.com;tag=a560e088-9e8a-49f2-a9b1-4a0ec31340bf To: sip:201@mydomain.com;tag=b596189c6de9c38f624fd84638f43be6-ff39 Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183 CSeq: 10697 PUBLISH Expires: 180 SIP-ETag: a.1518775074.19863.16.0 Server: kamailio (5.0.5 (x86_64/linux)) Content-Length: 0 When the call is done, Asterisk sent another PUBLISH telling that the call if terminated : PUBLISH sip:201@192.168.100.37 SIP/2.0 Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPja93efb01-a518-445e-9e9b-f6f97ab8c7 52 From: sip:201@mydomain.com;tag=165fb3b2-ec0e-4786-889f-eb194ad456ce To: sip:201@mydomain.com Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183 CSeq: 10698 PUBLISH Event: dialog SIP-If-Match: a.1518775074.19863.16.0 Expires: 180 Max-Forwards: 70 User-Agent: Asterisk PBX 14.6.0 Content-Type: application/dialog-info+xml Content-Length: 230 <?xml version="1.0" encoding="UTF-8"?> terminated.. And Kamailio replies : SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.100.37:5080;rport=5080;branch=z9hG4bKPja93efb01-a518-445e-9e9b-f6f97 ab8c752;received=192.168.100.37 From: sip:201@mydomain.com;tag=165fb3b2-ec0e-4786-889f-eb194ad456ce To: sip:201@mydomain.com;tag=b596189c6de9c38f624fd84638f43be6-48b4 Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183 CSeq: 10698 PUBLISH Expires: 180 SIP-ETag: a.1518775074.19873.18.1 Server: kamailio (5.0.5 (x86_64/linux)) Content-Length: 0 Here, the SIP ETag is a.1518775074.19873.18.1. The problem is if I make a new call before the expiration of the previous SUBSCRIBE, Asterisk reuse this SIP ETag according to the RFC : PUBLISH sip:201@192.168.100.37 SIP/2.0 Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPj9d13bb82-31d9-48db-9672-bd4b6b4f22 f0 From: sip:201@mydomain.com;tag=33e6b028-0444-4b3a-8bc2-4a987a291528 To: sip:201@mydomain.com Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183 CSeq: 10699 PUBLISH Event: dialog SIP-If-Match: a.1518775074.19873.18.1 Expires: 180 Max-Forwards: 70 User-Agent: Asterisk PBX 14.6.0 Content-Type: application/dialog-info+xml Content-Length: 247 <?xml version="1.0" encoding="UTF-8"?> early. Kamailio refuse it with this error : "Trying to update an already terminated state. Skipping update." because the call is considered as terminated. The RFC is stating : When updating previously published event state, PUBLISH requests MUST contain a single SIP-If-Match header field identifying the specific event state that the request is refreshing, modifying or removing. This header field MUST contain a single entity-tag that was returned by the ESC in the SIP-ETag header field of the response to a previous publication. Why Kamailio is acting like that? Best regards, Cyrille

2 2

Problem with "transport=tcp" and rtpproxy
by Pau Giralt 16 Feb '18

16 Feb '18

Hi! I'm working with kamailio and rtpproxy. When I configure the clients to send sip messages through TCP adding the ";transport=tcp" in the sip message the rtpproxy is not working anymore. The code is never passing the point pasted below, inside route[NATMANAGE] in kamailio.cfg if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; Therefore, rtpproxy_manage("co"); is never reached. Could it be a parsing problem? ( check_route_param("nat=yes") ) The config file is exactly the same as the one provided in the kamailio repository (the default one) Thanks!

2 7

Raspberry Pi deb packages -> built
by Mititelu Stefan 15 Feb '18

15 Feb '18

Hi people! After a bit of research and lib installations, I've managed to build the full kamailio deb packages for a raspberry pi 3 (version B) running raspbian stretch (lite) that can be found at [1] (with a really few module exceptions that might be used in really specific scenarios -> I think) Just for fun, I'm planning to do some CPS stats tomorrow (if I got the time), with a basic config and also share here, but, if someone else tried it before and is able to share some stats/benchmarks, would be greatly appreciated (and interesting to compare, given my "decent" rpi overclock), because I'm also curious about VoIP stuff on raspberry pi! :D [1] https://github.com/smititelu/rpi/tree/master/kamailio/5.1.1 Thank you, Stefan

2 3

KEMI
by Aleksandar Sosic 15 Feb '18

15 Feb '18

Hi everyone, we're valuating on rewriting our kamailio routes in python. We're doing a lot of string manipulation and GraphQL API queries so the kamailio scripting language is a little bit limited for this use case. Can someone tell us if the KEMI framework is stable enough for production? Kind regards, -- Aleksandar Sosic mail: alex.sosic(a)timenet.it skype: alex.sosic cell: +385 91 2505 146

5 11

Re: [SR-Users] RTPEngine Transcoding
by Social Boh 15 Feb '18

15 Feb '18

Hello, I'm trying to use this configuration: Softphone A audio codec g722 and Opus Softphone B audio codec PCMA and PCMU Kamailio with rtpengine_manage with codec-transcode-PCMU codec-transcode-PCMA in the request Softphone A call Softphone B The RTPEngine DEBUG show many Decoder Error: https://pastebin.com/k1Zhw8HS Thank you Regards --- I'm SoCIaL, MayBe El 13/02/2018 a las 20:05, Richard Fuchs escribió: > On 2018-02-13 07:22 PM, Social Boh wrote: >> Thank you. >> >> which is the best way to implement ir >> >> codec-strip-all and the add codecs? >> >> Is there a document about how work the transcoding? > It's really up to you and depends on what you want to achieve. Doing a > strip-all and then adding codecs you want to offer is definitely one > way. Another is to just add codecs that you know or think the peer may > want to see. > > Cheers >

2 2

Invalid payload location
by Soltanici Ilie 15 Feb '18

15 Feb '18

Hi All, Can someone explain why i'm receiving such errors in syslog: [4839]: {INVITE (1)] | Seq=101 | Source IP=46.166.139.7 (udp)} ERROR: <core> [core/parser/sdp/sdp.c:212]: set_sdp_payload_attr(): Invalid payload location [4839]: {INVITE (1)] | Seq=101 | Source IP=46.166.139.7 (udp)} ERROR: <core> [core/parser/sdp/sdp.c:212]: set_sdp_payload_attr(): Invalid payload location [4839]: {INVITE (1)] | Seq=101 | Source IP=46.166.139.7 (udp)} ERROR: <core> [core/parser/sdp/sdp.c:228]: set_sdp_payload_fmtp(): Invalid payload location [4839]: {INVITE (1)] | Seq=101 | Source IP=46.166.139.7 (udp)} ERROR: <core> [core/parser/sdp/sdp.c:212]: set_sdp_payload_attr(): Invalid payload location This is how the SIP Packet is looking: 2018/02/15 10:51:40.916040 46.166.139.7:30189 -> X.X.X.X:5060 INVITE sip:01031203697179@X.X.X.X:5060 SIP/2.0 Via: SIP/2.0/UDP 46.166.139.7:30189;branch=z9hG4bK-5342365299746297160962993236828333618949;rport=30189 From: <sip:88893855391@46.166.139.7:30189>;tag=0vkn019bur To: <sip:01031203697179@X.X.X.X:5060> Contact: <sip:88893855391@46.166.139.7:30189> Call-ID: 0889633580294714035892119863939070195463 CSeq: 101 INVITE User-Agent: Hello Annonymous Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 356 v=0 o=SIP-Session 950029666 1307322426 IN IP4 46.166.139.7 s=SIP c=IN IP4 46.166.139.7 t=0 0 m=audio 5075 RTP/AVP 18 0 8 101 a=fmtp:101 0-15 a=rtpmap:18 G729/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:9 G722/8000 a=fmtp:9 bitrate=64000 a=rtpmap:104 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=sendrecv Thank You.

1 0

python_exec return 0 causes script hangs; return -1 is treated like 0
by Anthony Alba 15 Feb '18

15 Feb '18

5.1.1: if python_exec method returns 0, then the script hangs If the python_exec method return -1, then expressions treat it as if it returned zero. Somewhere there seems to be an offset by 1 issue. if (!python_exec("method")) { # if you return -1, the script does not hang but treated like zero } ################## Example 1: class kamailio(object): def hello(self, msg): KSR.info("hello, world\n") return 0 Calling: python_exec("hello") will cause script hang ################### Example 2: class kamailio(object): def hello(self, msg): KSR.info("hello, world\n") return -1 Calling python_exec("hello") if (!python_exec("hello")) { ## method returns -1 ## why did we get here? xlog("L_INFO","method return zero!\n"); } shows INFO: <script>: method return zero!

2 1

[IGNORE] 5.1.1 python_exec, extra chars ' 0' appended to args
by Anthony Alba 15 Feb '18

15 Feb '18

Apologies for the noise; it is working now. Not sure how I got the extra " 0" appended to the method arguments for python_exec(). AAlba

1 0

[BUG?] 5.1.1 python_exec, extra chars ' 0' appended to args
by Anthony Alba 15 Feb '18

15 Feb '18

Using 5.1, the python_exc args string is getting an extra [_0' appended When I call python_exec("method", "string"); In python: def method(self, msg, args): KSR.info("DBG: {} {} {}".format(msg, args)) This will show 'string 0'; instead of string. AAlba

1 0

RTPEngine Transcoding
by Social Boh 14 Feb '18

14 Feb '18

Hi List, I just read on the RTPEngine page the Proxy RTP now support transcoding: https://github.com/sipwise/rtpengine#transcoding is there a plan to support it? Regards -- --- I'm SoCIaL, MayBe

5 10

RTPEngine QoS statistics and leg labelling
by Alex Balashov 14 Feb '18

14 Feb '18

Hello, I am excited about the new media statistics from RTPEngine, exposed conveniently into PVs, e.g. jitter, packet loss, MOS, time offset of lowest and highest MOS scores, etc. Great work! I am, however, having a bit of trouble understanding how to properly apply this new functionality, as it is not clearly documented (IMHO): 1. What is the meaning of "global" statistics which do not take into account an "A" and a "B" side? That is to say, if I have a packet loss or a jitter or MOS score statistic using just the generic toplevel values, e.g. https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.… What does that mean? A functional call ordinarily consists of an inbound and outbound RTP stream direction relative to the endpoints on both sides of RTPEngine. Inbound A --> server --> Outbound A Outbound B <-- server <--- Inbound B Where do the "global" stats situate themselves in relation to all this? 2. I am given to understand that the statistics for the "A" and "B" sides of a bidirectional RTP stream can be separated based on an arbitrary label, using these PVs: https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.… https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.… How do I use it properly? My intuition was to try something like this: rtpengine_offer("replace-origin replace-session-connection ICE=remove label=outbound"); And in the answer/manage handler on the SDP answer: rtpengine_answer("replace-origin replace-session-connection ICE=remove label=inbound"); Later, when processing a BYE and obtaining subsequent media statistics, I tried this: if(check_route_param("proxy_media=yes")) { $avp(rtpengine_a_label) = 'outbound'; $avp(rtpengine_b_label) = 'inbound'; rtpengine_delete(); route(LOG_RTPENGINE_STATS); } But this only gets me stats for the "A" leg in the JSON object I emit: { "server_addr": "udp:127.0.0.1:5050", "a_label": "outbound", "b_label": "inbound", "a_leg": { "min": { "mos": "4.4", "at": "0:04", "packetloss": "0", "jitter": "0", "roundtrip": 0 }, "max": { "mos": "4.4", "at": "0:04", "packetloss": "0", "jitter": "0", "roundtrip": 0 }, "avg": { "mos": "4.4", "packetloss": "0", "jitter": "0", "roundtrip": 0, "samples": 2 } }, "b_leg": { "min": { "mos": "<null>", "at": "<null>", "packetloss": "<null>", "jitter": "<null>" }, "max": { "mos": "<null>", "at": "<null>", "packetloss": "<null>", "jitter": "<null>" }, "avg": { "mos": "<null>", "packetloss": "<null>", "jitter": "<null>" } } } I also tried rtpengine_delete("label=inbound") (and outbound) individually. Some clarity on how this all fits together would be appreciated. :-) Many thanks to Sipwise for great work on it! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 14

How to add a new module to existing Kamailio Server?
by Arun NV 14 Feb '18

14 Feb '18

I am using a *Kamailio 4.4* server. And I would like to install *http_async_client* module to this server. I have looked in the module directory(*/usr/local/lib64/kamailio/modules*) to check whether this *http_async _client* module already exists there, but it was not there. And I searched for a solution and only found <http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-modular-install> the method to include new module at the compile time. I could find the modules source code on GitHub <https://github.com/sipwise/kamailio/tree/master/modules/http_async_client>. But I don't know the steps to install a new module to the existing Kamailio Thank you, Arunbalan

2 1

Use RTPProxy in 302 scenario
by Fabian Borot 13 Feb '18

13 Feb '18

I have this scenario Customer --> Kamailio --> Provider1 The route where l route the call to Provider1 is called route["INCOMING"] and I "arm" the replies and failures to : t_on_reply("INCOMING") and t_on_failure("INCOMING"). Provider1 always replies with a 302 Redirect and in the failure_route["INCOMING'] I have this code: if (t_check_status("302")) { get_redirects("*"); t_on_branch("REDIRECT_BRANCH"); t_load_contacts(); t_next_contacts(); t_on_failure("SERIAL_FORKING"); t_relay(); exit; } In the t_on_failure("SERIAL_FORKING") block I do t_relay() as long as there are more contacts to be processed. Lets say I need to try Provider_2 and Provider_3 failure_route["SERIAL_FORKING"] { xlog("L_INFO","mylog: In Failure Route SERIAL_FORKING. Reply [$rs]\n"); if (!t_next_contacts()) { exit; } xlog("L_INFO","mylog: In Failure Route SERIAL_FORKING. Trying next Contact.\n"); t_on_failure("SERIAL_FORKING"); t_relay(); } I want to use RTPProxy in this scenario and I am using the function rtpproxy_manage() to let kamailio handle it automatically. RTPProxy ↑ | | Customer --> Kamailio --> Provider1 | | ↓ Provider N After the 302 response is processed I would like to have the signaling flow "Customer -> Kamailio --> ProviderN" and the RTP flow "Customer --> RTPProxy --> ProviderN" I have tried inserting the function in several places but can't make it work and what I mean is that sometimes the rtpproxy creates the 1st session and then deletes it as soon as I call it the 2nd time with a message similar to this one (log of rtpproxy) : "INFO:416f20b74a58fb75168175e61b2edece@192.168.1.61:5060:rtpp_cmd_delete_ematch: forcefully deleting session 1 on ports 63502/0". Sometimes the kamailio log shows this message: "ERROR: rtpproxy [rtpproxy.c:2536]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy" I think I must call rtpproxy_manage() before I send the INVITE to each of the Providers in the Contact list so they receive a SDP offer with an IP:Port combination provided by the RTPProxy (instead of the ones coming from the Customer). That would be in my route["INCOMING'] Then once Provider_N replies with a 183 with SDP or a 200 OK I would call it again to get a new session to be passed on the reply to my customer. But is the part I am struggling with. Should I add a new reply route inside the failure_route["INCOMING'] only if I am dealing with 302 and do it there ? I am out of ideas guys and any idea is welcome

2 2

Can rtpengine change network interface of estabished call?
by Yufei Tao 13 Feb '18

13 Feb '18

Hi, Is it possible to define two pairs of network interfaces for rtpengine, e.g. int/ext and up/down? If so during a call established between interfaces 'int' and 'ext', is it possible to send a re-INVITE from the calling party on interface 'ext', to update the RTP destination to an IP on a different interface 'up', for example? Or does the updated RTP destination have to be on the same interface as when the call was established? I have some success updating the RTP destination if it is on the same interface (different IP:port) however haven't managed to divert it to a different interface. I wonder if it is possible at all or me missing something? Cheers, Yufei

1 0

(no subject)
by Tihomir Culjaga 13 Feb '18

13 Feb '18

Hi, Im new to Kamailio so im sorry if some of my questions will sound a bit wierd :=) i have a setup like this: (Kamailio version 5.1) UA > Kamailio > Freeswitch Kamailio forwards registration to freeswitch without saving location. I have configured sip over websockets and im able to register to Freeswitcha via kamailio. Also, i use add_path_received() so kamailio adds a path header to register messages recv 945 bytes from udp/[192.168.50.60]:5060 at 22:38:07.283809: ------------------------------------------------------------------------ REGISTER sip:192.168.50.60 SIP/2.0 Via: SIP/2.0/UDP 192.168.50.60;branch=z9hG4bKa929.0f66d60c4333f4a3a9d83d41a63295d9.0 Via: SIP/2.0/WSS 192.0.2.110;rport=63296;received=192.168.200.77;branch=z9hG4bK6931435 Max-Forwards: 69 To: <sip:1001@192.168.50.60> From: <sip:1001@192.168.50.60>;tag=vq30modpgd Call-ID: dlnrna9o4ngn25fb9d1vi2 CSeq: 196 REGISTER Authorization: Digest algorithm=MD5, username="1001", realm="192.168.50.60", nonce="744aaa14-4a86-4ce3-b6d6-419b0a34ee90", uri="sip:192.168.50.60", response="9b592b874474d4ffe5769f2410baceef", qop=auth, cnonce="sf7ff0fp8tm5", nc=00000001 Contact: <sip:1001@192.0.2.110 ;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:587f4694-7e55-46dc-a858-579a82556a20>";expires=600 Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER Supported: path, gruu, 100rel, outbound User-Agent: SIP.js/0.7.0 BB Content-Length: 0 Path: <sip:192.168.50.60;lr;received=192.168.200.77~63296~6> ------------------------------------------------------------------------ send 719 bytes to udp/[192.168.50.60]:5060 at 22:38:07.329444: ------------------------------------------------------------------------ SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.50.60;branch=z9hG4bKa929.0f66d60c4333f4a3a9d83d41a63295d9.0 Via: SIP/2.0/WSS 192.0.2.110;rport=63296;received=192.168.200.77;branch=z9hG4bK6931435 From: <sip:1001@192.168.50.60>;tag=vq30modpgd To: <sip:1001@192.168.50.60>;tag=Spya88DKU9gSQ Call-ID: dlnrna9o4ngn25fb9d1vi2 CSeq: 196 REGISTER Contact: <sip:1001@192.0.2.110;transport=ws>;expires=600 Date: Fri, 09 Feb 2018 21:38:07 GMT User-Agent: FreeSWITCH-mod_sofia/1.6.19+git~20171120T163416Z~b1b21d0695~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Path: <sip:192.168.50.60>;lr;received=192.168.200.77~63296~6 Content-Length: 0 ------------------------------------------------------------------------ Once, registered, im trying to originate a call to the registered endpoint from freeswitch this results in an invite like this: send 1757 bytes to udp/[192.168.50.60]:5060 at 22:46:21.252549: ------------------------------------------------------------------------ INVITE sip:1001@192.0.2.110;transport=ws SIP/2.0 Via: SIP/2.0/UDP 192.168.50.65:15060;rport;branch=z9hG4bKXHcX316pDgXZB Route: <sip:192.168.50.60>;lr;received=192.168.200.77~63296~6 Max-Forwards: 70 From: "" <sip:1002@192.168.50.65>;tag=tZQ393yprj7BK To: <sip:1001@192.0.2.110;transport=ws> Call-ID: 8212b700-8885-1236-08b3-000c293ae94e CSeq: 118770326 INVITE Contact: <sip:mod_sofia@192.168.50.65:15060> User-Agent: FreeSWITCH-mod_sofia/1.6.19+git~20171120T163416Z~b1b21d0695~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 891 X-FS-Support: update_display,send_info Remote-Party-ID: <sip:1002@192.168.50.65 >;party=calling;screen=yes;privacy=off Freeswitch appends a route header to the invite specifying kamailio as route and a received with original uri. well, here is the issue ... im failing to hit the SIP over websocket client... Kamailio my RELAY route is like this route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) { xlog("L_ALERT", "Its a Branch, go manage that !!! <$ru>\n"); t_on_branch("MANAGE_BRANCH"); } } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) { xlog("L_ALERT", "its onreply_route, go manage !!! <$ru>\n"); t_on_reply("MANAGE_REPLY"); } } if (is_method("INVITE")) { if(!t_is_set("failure_route")) { xlog("L_ALERT", "Its failure_route, go manage !!! <$ru>\n"); t_on_failure("MANAGE_FAILURE"); } } $fs = "udp:192.168.50.60:5060"; xlog("L_ALERT", "Trying to rely !!! <$ru>\n"); if (!t_relay()) { xlog("L_ALERT", "failed to rely !!! <$ru>\n"); sl_reply_error(); } exit; } here is a part of the log: Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: WARNING: <core> [core/forward.c:231]: get_send_socket2(): protocol/port mismatch (forced udp:192.168.50.60:5060, to ws:192.0.2.110:5060) Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: DEBUG: <core> [core/msg_translator.c:424]: clen_builder(): content-length: 916 (916) Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: WARNING: <core> [core/msg_translator.c:2765]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: ERROR: <core> [core/msg_translator.c:1980]: build_req_buf_from_sip_req(): could not create Via header Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: ERROR: tm [t_fwd.c:476]: prepare_new_uac(): could not build request Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: ERROR: tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: DEBUG: tm [t_funcs.c:334]: t_relay_to(): t_forward_nonack returned error -2 (-2) Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: DEBUG: tm [t_funcs.c:352]: t_relay_to(): -2 error reply generation delayed Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=744 a=26 n=xlog Feb 9 22:48:48 incfskamtest01 /usr/sbin/kamailio[14896]: ALERT: <script>: failed to rely !!! <sip:1001@192.0.2.110;transport=ws> is that because i set a $fu before t_relay() ? any idea how to approach the issue ?

2 4

onend_route() ?
by Wilkins, Steve 13 Feb '18

13 Feb '18

I meant to reply to Kamailio mailing list. From: Wilkins, Steve Sent: Friday, February 9, 2018 12:40 PM To: 'miconda(a)gmail.com' <miconda(a)gmail.com> Subject: RE: [SR-Users] t_relay()? Hi Daniel, I am not sure what I am doing wrong but I cannot get the forwarded message to print. I am using onend_route() and trying to print the results using xdbg. I have searched for examples and have had no luck. Thank you From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, February 9, 2018 7:48 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>; Wilkins, Steve <swwilkins(a)mitre.org<mailto:swwilkins@mitre.org>> Subject: Re: [SR-Users] t_relay()? Hello, before t_relay() you can't see what is going to the network, because some headers are added when knowing target address and local socket (e.g, Via, Record-Route). You can use onsend_route for seeing the request just before writing to the network. https://www.kamailio.org/wiki/cookbooks/devel/core#onsend_route $snd(buf) will give outgoing buffer -- for more see $sndfrom(...) and $sndto(...) vars. Cheers, Daniel On 09.02.18 11:24, Wilkins, Steve wrote: Hi All, Could someone please tell me, what variable to I use to see what t_relay() fowarding in its message? Thank you, -Steve _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com<http://www.asipto.com> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com<http://www.kamailioworld.com>

2 1

Request Timeouts
by Wilkins, Steve 13 Feb '18

13 Feb '18

Hello, This is actually a follow up to my last question about some providers calls being dropped. I noticed that when calls are dropped, I see a Kamailio log message "Request Timeout" about 5-10 seconds before the call is dropped. I am wondering what could cause this while a call is in progress. Does Kamailio need to respond to Asterisk with a '200 OK' for an INFO request sent to Kamailio from Asterisk? I am not sure what else could cause this call dropping behavior. Note: It does not appear to be caused from a missing 'ACK'. Thank you, -Steve

3 6

What is the mechanism used for sending push notification from Kamailio, For both IOS and Android?
by Arun NV 13 Feb '18

13 Feb '18

I am creating custom phone client, which uses *Kamailio *as a proxy and it's required to send *push notification* from *Kamailio *to the clients when a call towards the client reached on *Kamailio*. I found a module for APNS here* https://github.com/tvntsr/push <https://github.com/tvntsr/push>*. But I am developing both Android and IOS clients. So What mechanism I can use for the Android side? Is there any module available for *GCM*(Google Cloud Messaging) in Kamailio? Thank you, Arunbalan

2 1

is_audio_on_hold() doesn't support rfc3264
by Julia Boudniatsky 13 Feb '18

13 Feb '18

FYI, After some tests found, that function "*is_audio_on_hold()*" (textops) *supports only rfc 254*3, where "hold" is indicated by setting the "c" destination addresses for the media streams to zero (0.0.0.0). The newest *rfc3264*, where "hold" is indicated by a=sendonly/inactive, *is not supported*. Kamailio version 4.4.6. Best regards, Julia

4 8

Load testing: Taking CPU & MEM stats
by jeevan Chaitanya 12 Feb '18

12 Feb '18

Hi All, Found python library to take system stats during the load. >>> from getstats import GetStats >>> stat_obj = GetStats.getstats(dur=300,rate=10) >>> stat_obj.run_stats() Running.......... ***** Completed capturing the STATS ***** ######################################## # stats_2018-02-12_16-47-47_.csv # ######################################## Doc URL: http://getstats.readthedocs.io/en/latest/ If you require use and let me know. Thanks, K.Jeevan.

1 0

Very inconsistent calls
by Wilkins, Steve 12 Feb '18

12 Feb '18

Hello, I have found that calls are very inconsistent. I use Kamailio 5, Asterisk 14. When certain Providers like (Sorenson, ZVRS) make calls into a WebRTC client (tryit-jssip), sometime the calls stay up until I close them (10-15 minutes), others times those calls drop in 30 seconds. This is extremely confusing...does anyone else experience this type of behavior? -Steve

4 7

t_suspend usage in branch_route
by Aymeric Moizard 09 Feb '18

09 Feb '18

Hi, I'm trying to use t_suspend in my kamailio.cfg from a branch_route. I'm using kamailio 5.1.1 on debian jessie from http://deb.kamailio.org/kamailio51 >From the documentation: http://www.kamailio.org/docs/modules/5.1.x/modules/tmx.html#tmx.f.t_suspend i can see that "This function can be used from ANY_ROUTE ." However, the INVITE is still forwarded for this branch. So obviously the "outgoing transaction" is not suspended. May be "t_suspend" is only suspending "incoming transactions"? I tried to call "drop()". This prevent the INVITE from being sent. But in such case, i have an answer is sent immediatly to the caller (SIP/2.0 500 I'm terribly sorry, server error occurred (6/SL)) I want the script to wait as expected after my "t_suspend". And in the block indicated by t_continue, i want to append a new branch. Any way to do this? Otherwise, do you advise me to control the list of branch before t_relay? I guess I can access the list. Not sure how.. so if you have any tips... Tks Aymeric -- Antisip - http://www.antisip.com

3 9

I: - w_ro_ccr(): Unable to find dialog and cannot do Ro charging without it
by Angelo Colucci 09 Feb '18

09 Feb '18

Hello Everyone, I've been resolved the problem. It was the setflag(FLT_ACC) at the beginning of the block if (is_method("INVITE")) { setflag(FLT_ACC); <----- using instead following function now the dialog is correctly created. setflag(FLT_DIALOG); Best Regards Angelo Da: Angelo Colucci Inviato: giovedì 8 febbraio 2018 18:33 A: 'sr-users(a)lists.kamailio.org' <sr-users(a)lists.kamailio.org> Oggetto: [SR-Users] - w_ro_ccr(): Unable to find dialog and cannot do Ro charging without it Hello Everyone, I'm new in Kamailio environment. We trying to setup a IMS Credit Control Client as per RFC 4006. We've trying to implement the suggesting configuration in ims_charging module doc. The Kamailio version is 5.1.1 Stable. The Server is configured with two local users (A and B) registered on local mysql database. The scenario is the following: 1. In the request_route object we trying to intercept the first INVITE and trigger a diameter credit control request using Ro_CCR function. 2. When A calls B without triggering mechanism the call is fine. 3. When A calls B with credit control triggering, the calls failed and the diamater request is not generated. In the debug we find the following error: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=540 a=25 n=xlog ERROR: <script>: Individuato primo INVITE: generata nuova transazione exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=541 a=63 n=assign exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=541 a=29 n=Ro_CCR DEBUG: ims_charging [ims_charging_mod.c:494]: w_ro_ccr(): Ro CCR initiated: direction:orig, reservation_units:30, route_name:CHARGING_CCR_REPLY, incoming_trunk_id:1 outgoing_trunk_id:1 DEBUG: ims_dialog [dlg_hash.c:926]: internal_get_dlg(): no dialog callid='yH5kdBGSrM6CowdkkRHTUw..' found DEBUG: ims_dialog [dlg_hash.c:956]: get_dlg(): no dialog callid='yH5kdBGSrM6CowdkkRHTUw..' found DEBUG: ims_dialog [dlg_handlers.c:1950]: dlg_get_msg_dialog(): dlg with callid 'yH5kdBGSrM6CowdkkRHTUw..' not found ERROR: ims_charging [ims_charging_mod.c:511]: w_ro_ccr(): Unable to find dialog and cannot do Ro charging without it The error indicates that w_ro_ccr function doesn't find any dialog. Following you can find the relative configuration of kamailio.cfg. The request_route block is equal to default configuration except the following command: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_DEBUG loadmodule "cdp" loadmodule "cdp_avp" loadmodule "ims_charging" loadmodule "ims_dialog" modparam("ims_charging", "origin_host", "kcc-t-lu-03.mnc049.mcc222.3gppnetwork.org") modparam("ims_charging", "origin_realm", "mnc049.mcc222.3gppnetwork.org") modparam("ims_charging", "destination_realm", "mnc049.mcc222.3gppnetwork.org") modparam("ims_charging","interim_update_credits",30) modparam("ims_charging","timer_buffer",5) # -- ims_dialog params -- modparam("ims_dialog", "dlg_flag", FLT_DIALOG) request_route { ... if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting t_newtran(); $var(cc_ret) = Ro_CCR("CHARGING_CCR_REPLY", "orig", 30, "1", "1"); if ($var(cc_ret) < 0) { xlog("Chiamata a Ro_CCR() fallita\n"); sl_send_reply("402","Payment required"); exit; } } ... } route[CHARGING_CCR_REPLY]{ xlog("cca_return code is $avp(s:cca_return_code): $avp(s:cca_result_code)\n"); switch ($avp(s:cca_return_code)){ case 1: #success break; case -1: #failure switch ($avp(s:cca_result_code)){ case 4010: send_reply("402", "Payment required - Unsufficient funds"); break; case 5006: send_reply("486", "Line limit exceeded"); break; default: send_reply("402","Payment required ($avp(s:cca_result_code))"); break; } default: xlog("L_ERR", "Unknown return code from CCR: [$avp(s:cca_return_code)] \n"); send_reply("500", "Charging Error"); break; } } What's goes wrong? Thanks in advance Angelo Colucci

1 0

Regular exepression issue in permissions module
by Paulo Ferreira 09 Feb '18

09 Feb '18

Hi list, I'm testing permissions module with kamailio 5.1.1 and I was struggling with regular expressions in trusted requests part of module. I noticed that 9[0-9]{4} doesn't work as expected so I had to change it for 9[0-9][0-9][0-9][0-9] to work. Is it supposed to be like that? Is there other way in this module to simplify the expression since it is not accepting the POSIX way? Thanks, Paulo -- ------------------------------------------- Paulo Ferreira VoIP@RCTS - Área de Infraestruturas Aplicacionaisz FCCN http://www.fccn.pt/ Av. do Brasil, n.º 101 1700-066 Lisboa - Portugal Telefone|Phone: +351 218440100; Fax: +351 218472167 Aviso de Confidencialidade/Disclaimer Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha rececionado indevidamente esta mensagem,solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.

2 4

t_relay()?
by Wilkins, Steve 09 Feb '18

09 Feb '18

Hi All, Could someone please tell me, what variable to I use to see what t_relay() fowarding in its message? Thank you, -Steve

3 2

- w_ro_ccr(): Unable to find dialog and cannot do Ro charging without it
by Angelo Colucci 08 Feb '18

08 Feb '18

Hello Everyone, I’m new in Kamailio environment. We trying to setup a IMS Credit Control Client as per RFC 4006. We’ve trying to implement the suggesting configuration in ims_charging module doc. The Kamailio version is 5.1.1 Stable. The Server is configured with two local users (A and B) registered on local mysql database. The scenario is the following: 1. In the request_route object we trying to intercept the first INVITE and trigger a diameter credit control request using Ro_CCR function. 2. When A calls B without triggering mechanism the call is fine. 3. When A calls B with credit control triggering, the calls failed and the diamater request is not generated. In the debug we find the following error: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=540 a=25 n=xlog ERROR: <script>: Individuato primo INVITE: generata nuova transazione exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=541 a=63 n=assign exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=541 a=29 n=Ro_CCR DEBUG: ims_charging [ims_charging_mod.c:494]: w_ro_ccr(): Ro CCR initiated: direction:orig, reservation_units:30, route_name:CHARGING_CCR_REPLY, incoming_trunk_id:1 outgoing_trunk_id:1 DEBUG: ims_dialog [dlg_hash.c:926]: internal_get_dlg(): no dialog callid='yH5kdBGSrM6CowdkkRHTUw..' found DEBUG: ims_dialog [dlg_hash.c:956]: get_dlg(): no dialog callid='yH5kdBGSrM6CowdkkRHTUw..' found DEBUG: ims_dialog [dlg_handlers.c:1950]: dlg_get_msg_dialog(): dlg with callid 'yH5kdBGSrM6CowdkkRHTUw..' not found ERROR: ims_charging [ims_charging_mod.c:511]: w_ro_ccr(): Unable to find dialog and cannot do Ro charging without it The error indicates that w_ro_ccr function doesn’t find any dialog. Following you can find the relative configuration of kamailio.cfg. The request_route block is equal to default configuration except the following command: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_DEBUG loadmodule "cdp" loadmodule "cdp_avp" loadmodule "ims_charging" loadmodule "ims_dialog" modparam("ims_charging", "origin_host", "kcc-t-lu-03.mnc049.mcc222.3gppnetwork.org") modparam("ims_charging", "origin_realm", "mnc049.mcc222.3gppnetwork.org") modparam("ims_charging", "destination_realm", "mnc049.mcc222.3gppnetwork.org") modparam("ims_charging","interim_update_credits",30) modparam("ims_charging","timer_buffer",5) # -- ims_dialog params -- modparam("ims_dialog", "dlg_flag", FLT_DIALOG) request_route { … if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting t_newtran(); $var(cc_ret) = Ro_CCR("CHARGING_CCR_REPLY", "orig", 30, "1", "1"); if ($var(cc_ret) < 0) { xlog("Chiamata a Ro_CCR() fallita\n"); sl_send_reply("402","Payment required"); exit; } } … } route[CHARGING_CCR_REPLY]{ xlog("cca_return code is $avp(s:cca_return_code): $avp(s:cca_result_code)\n"); switch ($avp(s:cca_return_code)){ case 1: #success break; case -1: #failure switch ($avp(s:cca_result_code)){ case 4010: send_reply("402", "Payment required - Unsufficient funds"); break; case 5006: send_reply("486", "Line limit exceeded"); break; default: send_reply("402","Payment required ($avp(s:cca_result_code))"); break; } default: xlog("L_ERR", "Unknown return code from CCR: [$avp(s:cca_return_code)] \n"); send_reply("500", "Charging Error"); break; } } What's goes wrong? Thanks in advance Angelo Colucci

1 0

Feature/help android fcm and ios related push notification module
by Dipen Patel 08 Feb '18

08 Feb '18

hello.. Now most sip soft client in required push wakeup phone. So for that required android, ios push notifications module. I have seen some one have developed 'Tsilo' module based on GCM but it is old. So if possible so please upgrade for Android FCM so it iwll supported for Android and ios both. Thanks

3 2

Using t_relay_to_tcp()
by Wilkins, Steve 08 Feb '18

08 Feb '18

Hi All, Some providers only allow tcp so I switched from t_relay to t_relay_to_tcp(); however, nothing now gets relayed. Has anyone else had luck switching? Thank you, -Steve

3 2

Random 'BYE" sent?
by Wilkins, Steve 08 Feb '18

08 Feb '18

Hello All, I am running Kamailio 5 and using Asterisk 14 as PBX. I have a strange issue. When I receive calls from some providers to a WebRTC client, calls hang up after about 25 seconds. This does not happen with all providers and does not happen with WebRTC client to WebRTC client calls. It appears the "BYE" is coming from Kamailio. Any ideas? Thank you, -Steve

3 2

Re: [SR-Users] How to avoid automatic string to int conversion?
by Yuriy Gorlichenko 08 Feb '18

08 Feb '18

Hi. Yep! I found issue was in if. Fixed it. thx for response! On Feb 8, 2018 18:44, "Daniel-Constantin Mierla" <miconda(a)gmail.com> wrote: It looks like you are using it in some conditional expression (like if(...)) or some assignment with integer expression. Can you paste here the part of the config where you use it? Cheers, Daniel On 08.02.18 04:08, Yuriy Gorlichenko wrote: Hi im using kamailio 5.1 with native cfg file and using json_get_value( method) form jsonso module When i get json string that contains strings and i need to have these strings kamailio tries to convert string i find into int and affcource it can't then i see warning and can't get vaules of the string i have rval_expr_eval_int(): rval expression conversion to int failed (24,6-24,14) How to say kamailio to not convers strng to int? _______________________________________________ Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Info: Kamailio World 2018: First Group Of Speakers Announced
by Daniel-Constantin Mierla 08 Feb '18

08 Feb '18

Hello, the details for the first group of speakers at Kamailio World 2018 have been published: - https://www.kamailioworld.com/k06/speakers/ So far they come from three continents: Europe, North America and Asia, many presenting for the first time at our event. The two sessions present at all editions so far will be there also in 2018, at our 6th edition, respectively Dangerous Demos with James Body and VUC Visions with Randy Resnick. Besides covering various use cases for Kamailio, Asterisk or FreeSwitch, the sessions go into WebRTC, VoLTE/IMS, IoT, blockchains for telecommunications or scalability using NoSQL data storage systems. Definitely another edition with very interesting content – soon we will publish more details about the sessions as well. You can register now to benefit of the early registration price: - https://www.kamailioworld.com/k06/registration/ Looking forward to meeting many of you at Kamailio World Conference, May 14-16, 2018, in Berlin, Germany! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

How to avoid automatic string to int conversion?
by Yuriy Gorlichenko 08 Feb '18

08 Feb '18

Hi im using kamailio 5.1 with native cfg file and using json_get_value( method) form jsonso module When i get json string that contains strings and i need to have these strings kamailio tries to convert string i find into int and affcource it can't then i see warning and can't get vaules of the string i have rval_expr_eval_int(): rval expression conversion to int failed (24,6-24,14) How to say kamailio to not convers strng to int?

2 1

dmq_usrloc - which server?
by Alex Balashov 07 Feb '18

07 Feb '18

Hi, The Socket parameter of location entries is not replicated under dmq_usrloc. To make matters worse, the technical characteristics of the registrar module are such that I cannot straightforwardly modify the incoming Contact to add a rider indicating the server on which the register was received. The AoR domain is the same for all registrations received on any server in the DMQ mesh. To reach the registrants, I need to forward the registration to the correct server that corresponds to the true provenance of the registration. What is a reasonable way of finding out what that is? I don't see any method of injecting such values into the replicated contacts, as dmq_usrloc does not provide hooks for this. Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 19

any interest in segmentation fault at startup ?
by Jean Cérien 07 Feb '18

07 Feb '18

Hi I guess I'm a bit too creative when it comes to kamailio syntax.... just edited the cfg file and got the following error upon startup: kamctl start INFO: Starting Kamailio : /usr/sbin/kamctl: line 1915: 5294 Segmentation fault $OSERBIN -P $PID_FILE -f $ETCDIR/kamailio.cfg $STARTOPTIONS > /dev/null 2> /dev/null ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed I assume it is my syntax in cfg that creates this, I just need to correct it, but if there is interest, I can provide the faulty cfg file J.

4 4

Re: [SR-Users] Blind Transfer WS Error
by Matteo Campana 07 Feb '18

07 Feb '18

Dear Kamailians, does anyone have any idea on the issue below? Alessio told me that is always reproducible, and he can also provide captures and more logs. Thanks in advance! Matteo *From: *sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of Alessio Miranda <smirolandia(a)gmail.com> *Reply-To: *"Kamailio (SER) - Users Mailing List" < sr-users(a)lists.kamailio.org> *Date: *Tuesday, 16 January 2018 at 14:18 *To: *"sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> *Subject: *[SR-Users] Blind Transfer WS Error Hi, I have a problem with the blind transfer via WebSocket, debugging from the browser we see that in some cases when the REFER is done and the sip message "202 Accepted" arrives, the message "180 Ringing" arrives first and then the "100 Trying" and the transfer goes in error with "500 JsSIP Internal Error" I have an architecture with Kamailio in frontend and asterisk in backend on the same network, the sip dialogue between FE and BE is in SIP / UDP. The WebRTC client connects to WebSocket at Kamailio's public address. We have verified that the sip messages exchanged between kamailio and asterisk are always correct. Kamailio Ver. 4.4.4 Asterisk Ver. 13.18.3 PJSIP Ver. 2.6 JSSIP Ver. 3.2.2 Thanks Alessio

2 2

Contact and Record-Route are using Private IP Address- is this correct?
by Wilkins, Steve 07 Feb '18

07 Feb '18

Hello All, Contact and Record-Route are using Private IP Address - is this correct? I though the Public IP should be used. I do not know what setting is causing this to happen. Does anyone have any ideas? Thank you, -Steve

3 4

Info: Markus Monka replacing Marcus Hunger in management group
by Daniel-Constantin Mierla 07 Feb '18

07 Feb '18

Hello, Markus Monka has just replaced Marcus Hunger in Kamailio project management group. Marcus (still at sipgate) has moved to work more on frontend applications than backend, no longer interacting with Kamailio project. Markus Monka has managed the VoIP operations at sipgate for more than 15 years, helping the project over the years with various resources, mainly in respect of organizing events and testing infrastructure, sipgate being one of the oldest VoIP services using Kamailio (since first releases of SER). The change is reflected now on the website: * https://www.kamailio.org/w/management/ Warm welcome to Markus and many thanks to both of them for what they did so far for Kamailio project! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Info: Kamailio project administration updates
by Daniel-Constantin Mierla 07 Feb '18

07 Feb '18

Hello, after several discussions at some of the past IRC devel meetings, finally we started to build a team to be involved more actively in the administration of Kamailio. The project has grown steadily, not only in terms of code, but also packaging, continuous integration, social networking interactions as well as participation to events world wide. For a better coordination and ability to handle related tasks, I invited the most active developers and community members to join so called Kamailio Administration Team, the initial details about it are published as part of management page on kamailio.org: * https://www.kamailio.org/w/management/ Some more details about its rules and purpose: * https://www.kamailio.org/w/kadmin/ It will still take some time to get it properly rolling, more or less now looking to see if the community has suggestions/improvements on what can be done in these aspects. I wrote to all mailing lists for the initial announcement, but you can just reply to sr-users, if you are subscribed there, otherwise it's fine to write back to any of the lists. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Re: [SR-Users] Contact and Record-Route are using Private IP Address- is this correct?
by Ammar Tinawi 07 Feb '18

07 Feb '18

Is it mandatory to have an interface with public ip in order to overcome NAT problems ?

1 0

Issue with Socket selection on Forwarding ACK message
by Thomas Carvello 06 Feb '18

06 Feb '18

Hello, i have an issue with my Kamailio 4.1.9 configuration. This configuration is multi-homed, we have*two network* interfaces, one on a private network and on the public Internet. Kamailio is configured to listen on port 5060 and 5066 on both interfaces. We register two users Alice and Bob on the public Internet using port 5066. Both users are behind a NAT and we capture the SIP exchange on the proxy server. We have set the parameter mhomed=1 When Alice calls Bob, we have Alice Proxy Bob src=5063 dst=5066 INVITE ------------------> src=5066 ------ INVITE ---------------> dst=5060 dst=5066 <------- 200 OK -------------- src=5060 dst=5063 <------- 200 OK --------- src=5066 src=5063 dst=5066 -------- ACK -----------> *src=5060 (blocked by NAT)* ------ ACK-----x dst=5060 The ACK packet gets relayed with the wrong source port. Then the NAT rejects the packet and the call cannot be established. For some reason, when Bob calls Alice, the call is correctly established. Could it be because Bob happend to use 5060 as local port? Also, if we set nhomed=0 it works BUT we are not sure that multi homed is handled correctly. I was wondering if you have encounter this issue before? I have investigated the code for selection socket and what is the logic of this selection ? /*How does kamailo knows that it should choose 5066 as src port if the user is registered using port 5066 instead of 5066?* / Thank you for your time. Thomas

4 8

rtpproxy - no media connection
by Steve 05 Feb '18

05 Feb '18

Dear sr-users, I am trying to set up a simple Kamailio server with rtpproxy on the same host computer, behind a NAT router. “Run your own Skype-like service” is my set-up guide, but I’m using Kamailio version 5.1 so I modified the config files that came with the download. My problem is that SIP clients can register over the internet via TLS encryption with the server and establish a call session connection, but the ZRTP media connection is not being made. Once the call session connection is made, both clients send out UDP packets to each other, but neither receives them—the media traffic is one way and being dropped somewhere. I’ve tried different rtpproxy start settings. If I start the rtpproxy service with “sudo /etc/init.d/rtpproxy start” then it uses the default “unix:/var/run/rtpproxy/rtpproxy.sock”. I’ve also tried starting with “sudo rtpproxy –l /my_public_ip/ –s udp:localhost:7722” which then asks for either –F (superuser) or –u (user). I’ve tried it both with options “–F” and “-u kamailio kamailio”. All the variations tried so far have the same result as noted above. The server behind the router is in a DMZ zone that bypasses the router firewall. Is there anything in the user-list archives that addresses this issue? Or some likely place to start troubleshooting the problem? Any suggestions would be greatly appreciated. Thanks in advance. Steve --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

IMS (ng-voice vs github)
by Amar Tinawi 04 Feb '18

04 Feb '18

Hello Dears, can you please tell me what are the differences between the github version of ims modules and the ng-voice modules introduced by Mr Carsten repo ? Thanks in advance

2 1

Fosdem dinner
by Daniel-Constantin Mierla 03 Feb '18

03 Feb '18

Hello, in the past 10 years or so, many of us met at Fosdem conference in Brussels (the edition this year happens during February 3-4) and had a dinner on Saturday evening. I know already couple of people from community that will go there, so the question is if there is any interest to organize again such event. If yes, it will be again on Saturday, on the evening of the 3rd of February. At the past editions, it turned into an all-RTC dinner, but we can consider to have it alone again (eventually with few other invited friends), if there are too many or people want a smaller meeting. Reply this week if you want to join, so we can estimate how many seats we need and have enough time to find a place that can accommodate us. More about Fosdem can be found at: - https://fosdem.org There is a devroom on Sunday with topics covering real time communications. I will have a presentation there. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

10 13

SDP Rewrite issues
by Steven Meyer 02 Feb '18

02 Feb '18

Our topology is: Client <> Client Router <> Internet <> Firewall (NAT) <> Kamailio <> FS Unfortunately, when enabling SDP Rewrite: fix_nated_sdp, 0x08, it rewrites packets to the firewall external IP, not the client router external IP. Right now we have to do a local NATed IP on each phone.

1 0

Routing based on A and B numbers
by Grant Bagdasarian 02 Feb '18

02 Feb '18

Hi, Which module would be best suited for routing calls based on A and B numbers? We're currently using the LCR module, with some additional htables to add this functionality, but I was wondering if there is a module which does exactly this? Or perhaps a combination of modules? Regards, Grant Bagdasarian Senior Developer +31765727054<tel:+31765727054> cm.com<https://cm.com> [cid:image001.png@01D39C36.945A76C0]

2 2

Distributed Registrations.
by Володимир Іванець 02 Feb '18

02 Feb '18

Hello! Yesterday I read email conversation "Distributed Presence between Multiple Kamailios" where it was suggested to use Presence module with new dmq parameter. So was wondering if someone was thinking about approach to share registrations between multiple Kamailio servers without using database? Thanks!

2 1

Contact Header need update?
by Duarte Rocha 02 Feb '18

02 Feb '18

Greetings, My proxy does some number normalization in order to guarantee E164 numeration. It also verifies for valid Calling Numbers and replaces them if needed. In order to this, i'm updating the $fU pseudo-variable. Should i update the "Contact" Header too? I've made some testing and i can get calls to work with keeping the Contact intact and changing it to the new number. What is the most correct approach? Cheers, Duarte Rocha

1 0

Distributed Presence between Multiple Kamailios
by SamyGo 01 Feb '18

01 Feb '18

Hi, I'm working on multiple Kamailios that have users distributed evenly among them, I now need to enable presence in those Kamailio boxes. The scenario is a mesh where any user may have subscribed to BLF of other user registered & calling on any other proxy. What modules can help me achieve this? can this be done without creating a new Presence-Node for the whole environment? Hope to get some suggestions on how experts here have done this. Looking forward to positive response. Regards, Sammy

3 5

Case insensitive regexp in textops::search() function
by Andrey Deykunov 01 Feb '18

01 Feb '18

Hi, I have an htable containing some black list words (i.e. user IDs or phone models). To find matches of the words in every message I use the following script: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { if ( search($shtitval(i1)) ) { // do something } } sht_iterator_end("i1"); How can I modify search($shtitval(i1)) to get case insensitive matching? The example below does not work: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { $var(re) = $shtitval(i1) + "/i"; if ( search($var(re)) ) { // do something } } sht_iterator_end("i1"); Other possible modifications of $var(re) aren't working too. Thanks, Andrey

2 2

Partial/regex match on hash table key?
by Anthony Joseph Messina 31 Jan '18

31 Jan '18

Is is possible (without iterating through all entries in a hash table) to return the value based on a partial or regex match to the key? Something like... $var(one)=$sht(a=>*$var(two)) -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

2 2

question about force_send_socket
by Fabian Borot 31 Jan '18

31 Jan '18

our kamailo has 2 IPs, a public (87.x.x.x) and a private (192.168.1.1). It is listening on all of them. For all calls it listens on the public IP but for some calls I need to forward the incoming INVITE to a server in the private network so I do a " force_send_socket(privateip:port)" before the route that forwards the INVITE to the server in the private network and that works. But then when the server in the private network replies with 302 I have to contact the servers inside the Contact header using the Public IP now so I do this hoping that it will switch back to the public IP: if (t_check_status("302")) { force_send_socket(PUBLIC_IP:5060); get_redirects("*"); t_relay(); } But it stays in the private, so the INVITEs to the servers inside the Contact header are sent from the Private IP and they are blocked. This would be the flow: customer INVITE -> kamailio(publicIP) kamailio (publicIP) 100 trying -> customer kamailio(privateIP) INVITE -> Server(privateIP) Server(privateIP) 302 redirect -> kamailio(privateIP) kamailio(privateIP) ACK -> Server(privateIP) after I would like this to happen kamailio(publicIP) INVITE -> Server1(publicIP) but instead this happens: kamailio(privateIP) INVITE -> Server1(publicIP) how can I switch back to the public IP to continue with this call flow? thank you

2 2

[4.2] how to send out BYE successfully to close a TCP/TLS connection which misses the connection ID?
by Jack Wang 31 Jan '18

31 Jan '18

For some reasons, My settings will cause kamailio to be restarted even if there were connections connected to it. And when one SIP client in a connection wanted to hangup the call with a WebRTC Client (SIP over websocket) after the proxy-restarting, local client was closed, however , the other side was not. >From the log below it seems that the connection missed. Jan 30 18:19:31 ./kamailio[27857]: WARNING: <core> [msg_translator.c:2777]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [t_msgbuilder.c:1365]: assemble_via(): assemble_via: via building failed Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [t_msgbuilder.c:1545]: build_uac_req(): build_uac_req(): Error while assembling Via Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [uac.c:379]: t_uac_prepare(): t_uac: Error while building message So, Is it equivalent to connection ID missing? And is there any way to make Websocket found the connection? Btw, after proxy-restarting for seconds , I typed `sh kamctl stats` : websocket:ws_current_connections = 1 It showed that the WebRTC Client will re-connect automatically, So I think this connection could be found by proxy, Any suggestion? Thanks :)

1 2

Normal behaviour with loose_routing
by Loic Chabert 30 Jan '18

30 Jan '18

Hi list, I have a setup configurered has diagram below: UAC -> Proxy LB (proxy lb) -> Proxy Router/registrar (proxy B) -> Asterisk SBC My UAC is SIPP and sending a classic call scenario: INVITE - ACK - BYE. But i have some trouble to understand which queries should be loose routed and which queries should be dispatched by dispatcher module. My first invite request has been dispatched to proxy B by proxy LB. After that, ACK and BYE request should be loose_routed or should be dispatched as other request ? My proxy B is a statefull proxy, logging cdrs and other stuff ... >From my point of view, subsequent request should be loose_routed to keep dialog informations consistent. My subsequent requests have record-route headers. Should i use theses headers to route my calls ? Loose routing features only work with "Route" header ? What is the difference beetwen Route headers and Record-route headers ? Thanks in advance, Regards.

3 5

rtjson + uac + event - OK, ACK and BYE display name not updated
by Diego Nadares 30 Jan '18

30 Jan '18

Hi Guys, We are modifying "from" and "to" headers with rtjson module via a json struct. It works fine in INVITE, TRYING, RINGING and OK but not in the following messages. Kamailio It's changing ONLY "from" and "to" URI BUT NOT the DISPLAY NAME. I think it's the tm module but I can't figure out how to confirm this. Maybe I need to configure something else in my cfg or could it be a bug? My json struct that is handled by rtjson module response.routing = "serial"; //response.routing = "parallel"; response.routes = []; response.routes[0] = {}; response.routes[0].uri = "sip:1111111111@172.16.213.31:5060"; response.routes[0].headers = { // Headers to be modified "from": { "display": "1111111111", "uri": "sip:111111111@172.16.213.38" }, "to": { "display": "2222222222", "uri": "sip:2222222222@172.16.213.38" }, }; response.routes[0].headers.extra = {};//"X-Hdr-A: abc\r\nX-Hdr-B: bcd\r\n"; This is part of my cfg .... modparam("dialog","dlg_flag", FLD_START) modparam("uac","restore_mode","auto") modparam("uac", "restore_dlg", 1) .... # account only INVITEs if (is_method("INVITE") && !has_totag()) { setflag(FLT_ACC); # do accounting * setflag(FLD_START); # do accounting* setflag(FLT_ACCMISSED); setflag(FLT_ACCFAILED); } ..... >From source/Aleg: *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* To dest/Bleg: *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>.* Incorrect display name in BYE and ACK: *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* interface: any filter: ( port 5060 ) and (ip or ip6) # U 2016/12/06 15:52:13.638731 172.16.213.21:5060 -> 172.16.213.38:5060 INVITE sip:5555555555@172.16.213.38:5060 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: "SIPP" <sip:sipp@172.16.213.21:5060>. Max-Forwards: 70. Subject: Performance Test. Content-Type: multipart/mixed;boundary=uniqueBoundary. Remote-Party-ID: <sip:sipp@172.16.213.21 >:5060;party=calling;id-type=subscriber;privacy=off;screen=no>. Content-Length: 549. . --uniqueBoundary. Content-Type: application/sdp. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.21. s=-. c=IN IP4 172.16.213.21. t=0 0. m=audio 6000 RTP/AVP 8. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-11,16. . --uniqueBoundary. Content-Type: application/gtd. Content-Disposition: signal;handling=optional. . IAM,. CGN,04,y,1,y,4,1143617400. CIC,0000000573. CPC,09. CPN,02,y,1,52381660. FCI,n,n,n,n,y,n,n,u. GCI,f7140cc78a611601838a002128d7e512. NOC,0,n,1,n. PRN,q761*,AR*,oper2,1993. TMR,02. . --uniqueBoundary--. ................ # U 2016/12/06 15:52:13.734159 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Server: kamailio (4.4.4 (x86_64/linux)). Content-Length: 0. . ................ # U 2016/12/06 15:52:13.878600 172.16.213.38:5060 -> 172.16.213.31:5060 INVITE sip:1111111111@172.16.213.31:5060 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Max-Forwards: 69. Subject: Performance Test. Content-Type: multipart/mixed;boundary=uniqueBoundary. Content-Length: 788. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . --uniqueBoundary. Content-Type: application/sdp. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40236 RTP/AVP 8. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-11,16. a=sendrecv. a=rtcp:40237. a=ice-ufrag:QNCzXhUr. a=ice-pwd:Ci90BRpdZH51Hx5BaPgGMrGCeh. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40236 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40237 typ host. . --uniqueBoundary. Content-Type: application/gtd. Content-Disposition: signal;handling=optional. . IAM,. CGN,04,y,1,y,4,1143617400. CIC,0000000573. CPC,09. CPN,02,y,1,52381660. FCI,n,n,n,n,y,n,n,u. GCI,f7140cc78a611601838a002128d7e512. NOC,0,n,1,n. PRN,q761*,AR*,oper2,1993. TMR,02. . --uniqueBoundary--. ................ # U 2016/12/06 15:52:13.879441 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Type: application/sdp. Content-Length: 137. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.31. s=-. c=IN IP4 172.16.213.31. t=0 0. m=audio 6000 RTP/AVP 0. a=rtpmap:0 PCMU/8000. ................ # U 2016/12/06 15:52:13.936565 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 180 Ringing. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Content-Type: application/sdp. Content-Length: 316. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40248 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=sendrecv. a=rtcp:40249. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40248 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40249 typ host. ................ # U 2016/12/06 15:52:20.882165 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Type: application/sdp. Content-Length: 213. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.31. s=-. c=IN IP4 172.16.213.31. t=0 0. m=audio 6000 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. ................ # U 2016/12/06 15:52:21.173798 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 200 OK. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Content-Type: application/sdp. Content-Length: 380. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40248 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. a=rtcp:40249. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40248 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40249 typ host. ................ # U 2016/12/06 15:52:21.174390 172.16.213.21:5060 -> 172.16.213.38:5060 ACK sip:atpsh-58470879-6c61-2@172.16.213.38 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-4. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 ACK. Contact: sip:sipp@172.16.213.21:5060. Max-Forwards: 70. Subject: Performance Test. Content-Length: 0. . ................ # U 2016/12/06 15:52:21.248172 172.16.213.38:5060 -> 172.16.213.31:5060 ACK sip:172.16.213.31:5060;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.98116b5795d4c30f52156187a72059c8.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 ACK. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . ................ # U 2016/12/06 15:52:51.178826 172.16.213.21:5060 -> 172.16.213.38:5060 BYE sip:atpsh-58470879-6c61-2@172.16.213.38 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-7. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Contact: sip:sipp@172.16.213.21:5060. Max-Forwards: 70. Subject: Performance Test. Content-Length: 0. . ................ # U 2016/12/06 15:52:51.468639 172.16.213.38:5060 -> 172.16.213.31:5060 BYE sip:172.16.213.31:5060;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bK7baa.3cb44935b506e759e3418501b0688b08.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . ................ # U 2016/12/06 15:52:51.469153 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bK7baa.3cb44935b506e759e3418501b0688b08.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Length: 0. . ................ # U 2016/12/06 15:52:51.519423 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 200 OK. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Content-Length: 0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-7. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . ................ exit 13 received, 0 dropped Sorry for my english. Thanks in advance! Diego.

2 7

Session Timers
by Duarte Rocha 30 Jan '18

30 Jan '18

Hey guys, I have two issues about Session Timers that need some clarification. 1) I have my Kamailio between my clients CPE's and my GW to the PSTN. I want to configure it in a way that i always try to make the CPE do the refreshing so I can save resources on my kamailio and in the GW. If the CPE doesn't support it, the refresh should be done by the GW. Is it possible to do this test and configuration in every call ? 2) SIP has the MIN-SE mechanic and is well documented, but is it possible to implement a MAX-SE in any way ? Thanks for the help. If you need more details about the issue, please let me know. Cheers

2 1

Re: [SR-Users] Problem to install Kameilio from Ubuntu packages
by Victor Seva 30 Jan '18

30 Jan '18

2018-01-26 17:46 GMT+01:00 Alain Bonnefoy - XOOL <a.bonnefoy(a)xool.fr>: > > > I tried to install Kameilio on Ubuntu 16.04 from what explained in the > wiki <https://www.kamailio.org/wiki/packages/debs>. > Wiki updated. Thanks

1 0

Re: [SR-Users] Problem to install Kameilio from Ubuntu packages
by Bastian Triller 30 Jan '18

30 Jan '18

There another command on http://deb.kamailio.org for people behind firewalls which block port 11371: % wget -O- http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - On Jan 26, 2018 5:46 PM, "Alain Bonnefoy - XOOL" <a.bonnefoy(a)xool.fr> wrote: > Hello, > > > > I tried to install Kameilio on Ubuntu 16.04 from what explained in the > wiki <https://www.kamailio.org/wiki/packages/debs>. > > > > But when I execute the command to add your GPG key, I just get replied > that the timeout occured. > > > > What to do ? > > > > Alain > > Provenance : Courrier <https://go.microsoft.com/fwlink/?LinkId=550986> > pour Windows 10 > > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >

1 0

kamailio tls passthrough
by pavel＠eremina.net 30 Jan '18

30 Jan '18

Hi, All i am trying to load balancing Kamailio with TLS in passthrough mode. is it possible to do it in stateless mode?

2 1

whats happened to iptel.org
by voipspace voipspace 29 Jan '18

29 Jan '18

Anyone know whats happened to iptel.org The webiste is now a wix page iptel.org the sip uri music(a)iptel.org was a useful resource. Now the song has changed and the service is down alot Has it it changed hands or been sold?

1 0

i can not receive BYE after websocket has been closed and reconnected during the call
by Kenan Kocaerkek 29 Jan '18

29 Jan '18

Hi, I have a WebRTC softphone based on JsSIP and kamailio 4.4.7. Generally it works well but sometimes websocket connections interrupt and reconnect immediately (especially running behind proxies). If the interruption occurs during an active call, kamailio tries to send BYE message to softphone over closed websocket. gruu_enabled flag is active on registrar module and JsSIP sends proper sip.instance value. So after ws reconnects, registered contact details do not change on kamailio except Expires value. Is it possible to send BYE message via contact's last active websocket after reconnect? Jan 29 14:35:20 registrar-kenan /usr/local/sbin/kamailio[30357]: WARNING: <script>: WebSocket connection from 195.142.112.66:49086 has closed Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: WARNING: <core> [msg_translator.c:2761]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: <core> [msg_translator.c:1979]: build_req_buf_from_sip_req(): could not create Via header Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: tm [t_fwd.c:462]: prepare_new_uac(): could not build request Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: tm [t_fwd.c:1723]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: No error (2/SL) Regards, Kenan

1 0

Ann: Registration to Kamailio World 2018 is open!
by Daniel-Constantin Mierla 29 Jan '18

29 Jan '18

Hello, a quick note to the community forums to announce that the registration to next Kamailio World Conference (May 14-17, 2018, in Berlin, Germany) is now open! More details are available at: * https://www.kamailioworld.com/k06/registration/ In a matter of several days, we expect to publish the details about the first group of accepted speakers. Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

New module – embedded MSRP relay
by kossivi HOLONOU 28 Jan '18

28 Jan '18

Hello,I would like to develop a project that will allow me to: - voice, video, screen sharing, etc. sessions with content communication via RTP - end to end presence – this is purely SIP routing - SIMPLE-based presence (aka, presence server or presence agent model) via presence* and pua* modules — user presence, dialog states notification (aka, blinking lamps), resource lists service (including OMA/RCS extensions), user location states notification and replication, audio/video conference mixer notifications, a.s.o. - embedded XCAP server – management of user contact lists, presence policies, user agent configuration files, a.s.o. There is also an XCAP client extension - embedded HTTP server – for admin and user interaction with the service via pure HTTP or XMLRPC requests - embedded MSRP relay – for relaying and fine controlling of the message-based content of SIP sessions - IRC-style instant messaging conference via imc module - storage of instant messages for offline users and relay to them when they become again online via msilo module I need your help to start. I went through the document a little without understanding much. Thanks for your help

1 0

Kamailio with asterisk on private lan
by Mark Boyce 28 Jan '18

28 Jan '18

Hi all I’m trying to create a relatively simple setup with Kamailio dual homed on public/private ip and asterisk on private ip only. The idea is load balance / fail over asterisk boxes. Following the real-time tutorial I have clients registering with Kamailio, Kamailio registering on clients behalf with asterisk as well as invites going through. However what I’m seeing is that when an invite occurs asterisk offers media on its private ip, as it would. However this is making its way through Kamailio all the way to the client. After a bit of searching all I can find is people trying to get it working and failing, or putting asterisk on public IP. So questions - am I doing this completely the wrong way? Should Kamailio alter the media ip of asterisk on the way through or do I need to do that by hand? Surely someone somewhere has a write up on this already :-) Thanks Mark

7 8

SEMS with sbc application
by Mojtaba 27 Jan '18

27 Jan '18

Hello, I have a problem today, It's strange for me. Suppose we have this senario: uac1------->SEMS(mo profile)------->Kamailio-------->SEMS(mt profile)---------->uac2 In above topology, we have two interfaces(intern,extern) for SEMS, and just used as SBC (sbc application). if i used port=5060 as external port, every things is right and log file is like this: [#7fed3f9f9700/32820] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 89.165.117.125:42411 vv --++-- REGISTER sip:kava.shatel.ir;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 89.165.117.125:42411;branch=z9hG4bK-d8754z-021bd8b61efc7ac0-1---d8754z- Max-Forwards: 70 Contact: <sip:4000@ 89.165.117.125:42411;rinstance=79011092e56e1a09;transport=UDP> To: <sip:4000@kava.shatel.ir;transport=UDP> From: <sip:4000@kava.shatel.ir;transport=UDP>;tag=82820e1f Call-ID: Y2U4YThiYjEwNTUzMzliZTIwNWZkMDI3MTM4OTZlNWU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 0 but when i changed port=4080 for external port, The Via header and contact header are changed to my public ip, like this: [#7fed3f9f9700/32820] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 89.165.117.125:42411 vv --++-- REGISTER sip:kava.shatel.ir;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 172.1.1.125:42411;branch=z9hG4bK-d8754z-021bd8b61efc7ac0-1---d8754z- Max-Forwards: 70 Contact: <sip:4000@172.1.1.125:42411;rinstance=79011092e56e1a09;transport=UDP> To: <sip:4000@kava.shatel.ir;transport=UDP> From: <sip:4000@kava.shatel.ir;transport=UDP>;tag=82820e1f Call-ID: Y2U4YThiYjEwNTUzMzliZTIwNWZkMDI3MTM4OTZlNWU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 0 Why my public ip address is there here? I just changed external port=4080 in sems server. In SDP protocol i have the same problem when i changed external ip port in sems server. Thanks. --Mojtaba Esfandiari.S

3 3

Transcoding
by Wilkins, Steve 26 Jan '18

26 Jan '18

Hello All, I am currently using Kamailio and Asterisk on Centos 7 servers and trying to enable WebRTC jsSIP clients to be able to do Audio/Video calls with Provider Phones (Purple, Z, Sorenson, etc....), however, the providers do not have vp8 codecs (which is what the WebRTC clients use for Audio) so I believe I will need a media proxy server to resolve the video issues. My question is, can rtpproxy or rtpengine perform this transcoding? If so, and if rtpengine is the way to go, should I use Ubuntu for the rtpengine since it is the only one that seems to have a working installation? Thank you, -Steve

5 5

Problem to install Kameilio from Ubuntu packages
by Alain Bonnefoy - XOOL 26 Jan '18

26 Jan '18

Hello, I tried to install Kameilio on Ubuntu 16.04 from what explained in the wiki. But when I execute the command to add your GPG key, I just get replied that the timeout occured. What to do ? Alain Provenance : Courrier pour Windows 10

1 0

Kamailio log file empty
by Ashutosh chaubey 26 Jan '18

26 Jan '18

Hi, My kamailio.log file is empty, following is my configuration: In Kamailio.cfg- log_facility=LOG_LOCAL0 #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=3 log_stderror=no #!endif Inside rsyslog.conf # don't log messages with LOG_LOCAL0 in /var/log/syslog anymore *.*;auth,authpriv.none,local0.none -/var/log/syslog # # log messages with LOG_LOCAL0 in /var/log/kamailio.log local0.* -/var/log/kamailio.log User has all the privileges to write in log file. Regards, Ashutosh Chaubey

3 2

EOL of geoip module.
by Sergey Okhapkin 26 Jan '18

26 Jan '18

Maxmind just announced EOL of legacy geolite databases used by geoip module, no updates starting this April. See more at https://blog.maxmind.com/ 2018/01/02/discontinuation-of-the-geolite-legacy-databases/ If you use kamailio's geoip module, I suggest to switch to geoip2 module which uses Geolite2 databases and is a plug in replacement for geoip module.

2 1

Behavior of UAC-Redirect module
by Richard Skidmore 26 Jan '18

26 Jan '18

2 2

SIP reply reason and code in dialog
by voipspace voipspace 26 Jan '18

26 Jan '18

within event_route[dialog:end] How do I find out SIP reply reason phrase and SIP reply code $rr $rs and $T_rpl($rs) $T_rpl($rr) are null

3 4

Three core dump bug fixes IMS kamailio 5.1.0 -> Pull Requests will follow
by Valentin Christoph 25 Jan '18

25 Jan '18

Hi all, When switching from kamailio 4.4.5 to kamailio 5.1.0 with the IMS installation in our lab, we detected three bugs, that lead to core dump. We will issue three pull requests in the course of this afternoon. KR ____ Christoph VALENTIN Software Developer | R&D Core / MGW + HLR + MSC P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

2 2

Modify Reply Created
by Duarte Rocha 25 Jan '18

25 Jan '18

Hey everyone. Right now i'm doing a redirect server and i'm trying to sinalize the redirection using a 3xx reply. In order to do that, according the RFC I need to add a Contact and Diversion header. How do i do that ? i'm creating the reply with send_reply() but i can't seem to find a way to add these parameters to the reply. Thanks for the help. Cheers

3 2

kamctl domain reload
by David Villasmil 25 Jan '18

25 Jan '18

Hello guys, This is weird, using kamctl I am able to do things from like: kamctl trusted show +----+--------------+-------+--------------+--------------+------+----------+ | id | src_ip | proto | from_pattern | ruri_pattern | tag | priority | +----+--------------+-------+--------------+--------------+------+----------+ | 1 | 1.2.3.4 | udp | | NULL | | 0 | +----+--------------+-------+--------------+--------------+------+----------+ but reloading, etc doesn't work: kamctl trusted reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 22107 } Other cases: kamctl domain showdb +----+-------------------------------------+------+---------------------+ | id | domain | did | last_modified | +----+-------------------------------------+------+---------------------+ | 1 | proxy.domain.com | NULL | 2018-01-25 00:56:24 | +----+-------------------------------------+------+---------------------+ but show: kamctl domain show { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 22277 } Any ideas why this might be happening? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 1

Re: [SR-Users] Modify Reply Created
by Duarte Rocha 25 Jan '18

25 Jan '18

Thanks for the reply, that works :) What about if I want to delete or overwrite an header ? I need to change to To Header. If i use append_reply() will it overwrite ? Cheers

1 0

Allow Methods and Allow events SIP Headers are missing on SIP Registrtaion
by Suresh Talasaniya 25 Jan '18

25 Jan '18

Hi All, I am facing issue while SIP REGISTER. Allow methods and Allow Event SIP Headers are the mission of 401 Unauthorized and 200 OK on Successful SIP Registered. Please find the attached document in which I mention both working and nonworking SIP Message. It would be appreciable if anyone help figures out this issue on Kamailio server. Thank you. -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 2

Purge htable after dialog termination
by Jean Cérien 24 Jan '18

24 Jan '18

Hello I am following up on the improper sip dialog that has been fixed by storing contact details into a htable. I am trying to delete the key at the end of the call, so the table doesnt grow exponentially. I've added a event_route[dialog:end] {} block, but I see it is processed BEFORE the BYE is processed in the request_route(). Therefore, when I delete the data in the htable, I cant relay this BYE correctly. Is there another event (or technique) I could use to purge the htable ? doing from a cron on the cmd line is not so nice, and can delete data still needed for current calls thanks J.

2 4

Question about [SIP Transaction] Handle Cancel message
by Jacek S 23 Jan '18

23 Jan '18

Hi How you finally solved the problem with "481 Call transaction does not exist"? I have the same problem. Best regards, Jacek Szyszka

1 0

Freeradius Accounting [sql] Unsupported Acct-Status-Type = 15
by Suresh Talasaniya 23 Jan '18

23 Jan '18

Hey Guys, I have faced the issue when I am trying to store answered the call to PostgreSQL database using freeradius. *Mon Jan 22 06:48:39 2018 : Info: [sql] Unsupported Acct-Status-Type = 15* For more details, find here with attached radius.log. # freeradius -v freeradius: FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu, built on Aug 10 2017 at 07:25:15 Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. For more information about these matters, see the file named COPYRIGHT. Can someone help me to resolve this problem? -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

1 0

Kamailio v5.1.1 Released
by Daniel-Constantin Mierla 22 Jan '18

22 Jan '18

Hello, Kamailio SIP Server v5.1.1 stable release is out. This is a maintenance release of the latest stable branch, 5.1, that includes fixes since the release of v5.1.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.1. For more details about version 5.1.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2018/01/kamailio-v5-1-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Already called uac_replace for this dialog
by Евгений Голей 22 Jan '18

22 Jan '18

Tell me please. Logs periodically display messages 2018-01-22T14: 14: 46.7701 "INFO: uac [replace.c: 392]: replace_uri (): Already called uac_replace for this dialog" 2018-01-22T14: 14: 46.7704 "INFO: uac [replace.c: 401]: replace_uri (): Deleted <_uac_funew> var in dialog" The reason I know, the question is how in the dialog to overwrite the previously saved parameter, which was obtained with "uac_replace"? -- С уважением, Евгений Голей

1 0

Planning the release of v5.1.1
by Daniel-Constantin Mierla 22 Jan '18

22 Jan '18

Hello, I am considering to do the first patch release from 5.1 series at the beginning of next week (most likely on Monday or Tuesday), as usual, if there are issues you are aware of and not reported to bug tracker, do it as soon as possible in order to have a chance to be fixed: - https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 1

sip invite proxy-authorization
by Dave & Hazel 21 Jan '18

21 Jan '18

Hello, Sorry, I'm not that familiar with Kamailio. I am trying to figure out how to configure proxy-authorization for incoming sip invites. I've defined WITH_AUTH in the configuration file but I think this only applies to sip register transactions. Any insight is most appreciated. Dave

4 9

Coredump while exchanging diameter capabilities
by Tsvetan Filev 19 Jan '18

19 Jan '18

Hi. I get a coredump which is caused by bad memory handling during the diameter capability exchange process. Here is part of the log file: =================================== 2018-01-16T09:16:39.890992+02:00 linux-o12d kamailio[13298]: 87(13388) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 2018-01-16T09:16:40.296393+02:00 linux-o12d systemd-coredump[13196]: Process 13193 (kamailio) of user 479 dumped core. 2018-01-16T09:16:40.871483+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peermanager.c:263]: peer_timer(): peer_timer(): taking care of peers... 2018-01-16T09:16:40.871545+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State 0 2018-01-16T09:16:40.871596+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Closed Event Start 2018-01-16T09:16:40.871612+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org 2018-01-16T09:16:40.871636+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [receiver.c:869]: peer_connect(): peer_connect(): Trying to connect to 10.82.10.85 port 3868 2018-01-16T09:16:40.871782+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org:3868 connected 2018-01-16T09:16:40.871813+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:697]: receive_loop(): select_recv(): There is something on the fd exchange pipe 2018-01-16T09:16:40.871828+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:706]: receive_loop(): select_recv(): fd exchange pipe says fd [22] for peer 0x7f0626b91c98:[hss.epc.mnc019.mcc425.3gppnetwork.org] 2018-01-16T09:16:40.871910+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Wait_Conn_Ack Event I_Rcv_Conn_Ack 2018-01-16T09:16:40.871933+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:184]: AAANewMessage(): AAANewMessage: param session received null and it's a request!! 2018-01-16T09:16:40.872011+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:81]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=204 2018-01-16T09:16:40.872041+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:994]: peer_send_msg(): peer_send_msg(): Pipe push [0x7f0626c02548] 2018-01-16T09:16:40.872064+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:751]: receive_loop(): select_recv(): There is something on the send pipe 2018-01-16T09:16:40.872084+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:764]: receive_loop(): select_recv(): Send pipe says [0x7f0626c02548] 8 2018-01-16T09:16:40.872104+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7f0626c02548) 257 2018-01-16T09:16:40.872277+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:574]: do_receive(): receive_loop(): [hss.epc.mnc019.mcc425.3gppnetwork.org] Recv Version 1 Length 360 2018-01-16T09:16:40.872322+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:1088]: receive_message(): receive_message(): [hss.epc.mnc019.mcc425.3gppnetwork.org] Recv msg 257 2018-01-16T09:16:40.872345+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Wait_I_CEA Event I_Rcv_CEA 2018-01-16T09:16:40.872372+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:692]: count_Supported_Vendor_Id_AVPS(): Found 4 Supported_Vendor AVPS92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872389+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872405+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872420+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872438+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872453+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872468+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872486+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872504+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872523+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872539+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872554+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872570+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 5535 2018-01-16T09:16:40.872586+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 10415 2018-01-16T09:16:40.872601+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 13019 2018-01-16T09:16:40.872616+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 58637 2018-01-16T09:16:40.872634+02:00 linux-o12d kamailio[13298]: 92(13393) CRITICAL: <core> [core/mem/q_malloc.c:145]: qm_debug_frag(): BUG: qm: prev. fragm. tail overwritten(28af01000000, 0)[0x7f0626c038d0:0x7f0626c03908]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. 2018-01-16T09:16:41.054292+02:00 linux-o12d kamailio[13298]: 0(13298) ALERT: <core> [main.c:746]: handle_sigs(): child process 13393 exited by a signal 6 2018-01-16T09:16:41.054403+02:00 linux-o12d kamailio[13298]: 0(13298) ALERT: <core> [main.c:749]: handle_sigs(): core was generated 2018-01-16T09:16:41.054422+02:00 linux-o12d kamailio[13298]: 0(13298) INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD 2018-01-16T09:16:41.054438+02:00 linux-o12d kamailio[13298]: 0(13298) DEBUG: <core> [main.c:773]: handle_sigs(): terminating due to SIGCHLD 2018-01-16T09:16:41.054464+02:00 linux-o12d kamailio[13298]: 2(13303) INFO: <core> [main.c:826]: sig_usr(): signal 15 received ... =================================== Attached is wireshark trace. Here is my DiameterPeer.xml: =================================== <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="ims110-scscf.epc.mnc019.mcc425.3gppnetwork.org" Realm="epc.mnc019.mcc425.3gppnetwork.org" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="8" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600"> <Peer FQDN="hss.epc.mnc019.mcc425.3gppnetwork.org" Realm="epc.mnc019.mcc425.3gppnetwork.org" port="3868" /> <Acceptor port="3869" bind="10.82.10.56" /> <Auth id="16777216" vendor="10415" />  <DefaultRoute FQDN="ims110-scscf.epc.mnc019.mcc425.3gppnetwork.org" metric="10" /> </DiameterPeer> =================================== It looks like buffer overflow to me but I'm not sure. kamailio version is: =================================== kamailio -v version: kamailio 5.1.0 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 05:30:36 Jan 15 2018 with gcc 4.8.5 =================================== OS is openSUSE Leap 42.3. Kernel: Linux linux-o12d 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux Do you have any idea what might be wrong ? It could be bad config but still it should say something in the log without a crash. Regards.

3 5

Problem Proxy
by Nicolas Breuer 18 Jan '18

18 Jan '18

Hello the list, I have a problem on the proxy with the audio between two calls bridged by a UAC. When I made a normal call, no problems. My UAC is nated. UAC > Router > KAMAILIO Frames arrives with private IP in the SDP. U 2018/01/18 21:50:16.798581 217.112.180.235:1024 -> 217.112.180.10:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 217.112.180.10;branch=z9hG4bK2d06.2f2a1856bde881173a3fc413c4136b83.0. Via: SIP/2.0/UDP 84.14.241.179:5060;rport=5060;branch=z9hG4bK0dBe3143bcf7f60a70b. Record-Route: <sip:217.112.180.10;lr=on;ftag=gK0d4dfe6f;did=227.c0d2;nat=yes>. From: <sip:32XXXXXX87@ >;tag=gK0d4dfe6f. Call-ID: 940401290_111374574(a)84.14.241.179. CSeq: 29328 INVITE. Contact: <sip:32XXXXXX61@192.168.2.2:5060;transport=udp>. Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY. Supported: timer,100rel. Server: IP Office 10.1.0.0.0 build 237. Min-SE: 1800. Require: timer. Session-Expires: 1800;refresher=uas. To: <sip:32XXXXXX61@217.112.180.235>;tag=998e429e819ba686. Content-Type: application/sdp. Content-Length: 202. . v=0. o=UserA 3721571424 1025404311 IN IP4 192.168.2.2. s=Session SDP. c=IN IP4 192.168.2.2. t=0 0. m=audio 49154 RTP/AVP 9 101. a=rtpmap:9 G722/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. I don't understand why but the proxy (in case of an incoming call) succeed to determine the public IP. Jan 18 21:40:08 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: caller's address filled in: 217.112.180.235:49154 (RTP) Jan 18 21:40:08 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: guessing RTCP port for caller to be 49155 Jan 18 21:40:16 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: caller's address latched in: 217.112.180.235:49155 (RTCP) Don't know why because the only information in SDP is 192.168.2.2 The Kamailio didn't send the information of the proxy to the UAC , but to the other end as this is an incoming call. So I have audio in this case. When I setup a bridge on the UAC to a second number, we have an issue. ( Kamailio 4.4.6 ) This is the same frames U 2018/01/18 21:51:26.607270 217.112.180.235:1024 -> 217.112.180.10:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 217.112.180.10;branch=z9hG4bK4181.bb7aab84b6fb0aea5836b4d8874406ec.0. Via: SIP/2.0/UDP 84.14.241.179:5060;rport=5060;branch=z9hG4bK0bB16ee5a3d300fee16. Record-Route: <sip:217.112.180.10;lr=on;ftag=gK0b5d7652;did=cc6.5452;nat=yes>. From: <sip:32XXXXXX87@ >;tag=gK0b5d7652. Call-ID: 940248136_13287504(a)84.14.241.179. CSeq: 21946 INVITE. Contact: <sip:32XXXXXX61@192.168.2.2:5060;transport=udp>. Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY. Supported: timer,100rel. Server: IP Office 10.1.0.0.0 build 237. Min-SE: 1800. Require: timer. Session-Expires: 1800;refresher=uas. To: <sip:32XXXXXX61@217.112.180.235>;tag=559c99f5edcab5d4. Content-Type: application/sdp. Content-Length: 202. . v=0. o=UserA 1781830446 4071482272 IN IP4 192.168.2.2. s=Session SDP. c=IN IP4 192.168.2.2. t=0 0. m=audio 49156 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. But in this case no audio RTCP detected but no the RTP. He took the private ip address "192.168.2.2" and this is the reason of the "no audio". Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rtpp_command_ul_handle:940248136_13287504@84.14.241.179: lookup on ports 11264/10446, session timer restarted Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rtpp_command_ul_handle:940248136_13287504@84.14.241.179: pre-filling callee's address with 192.168.2.2:49156 Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rxmit_packets:e1e387824e0753522b7bc55e02090784: callee's address latched in: 79.137.49.139:39176 (RTP) Jan 18 21:51:32 proxy1 rtpproxy[1314]: INFO:rxmit_packets:e1e387824e0753522b7bc55e02090784: caller's address filled in: 217.112.180.235:49155 (RTCP) Jan 18 21:51:32 proxy1 rtpproxy[1314]: INFO:rxmit_packets:940248136_13287504@84.14.241.179: callee's address filled in: 217.112.180.235:49157 (RTCP) I would like to understand why with the first call, no issues to determine the RTP IP and not in the second case,

1 0

SEMS Site?
by Mark Boyce 18 Jan '18

18 Jan '18

Hi all Could anyone tell me where the current SEMS site is? iptel seem to have lost all references and moved their site to wix. Everything search wise points me back at iptel :-( Or is the copy on github it at the moment? https://github.com/sems-server <https://github.com/sems-server> Cheers Mark

2 2

Problems with probing in dispatcher module
by Paulo Ferreira 18 Jan '18

18 Jan '18

Hi list, I'm using dispatcher module and I'm not able to figure it out how to accomplish a simple task regarding gateways availability and probings. My goal is to probe with SIP OPTIONS my three gatways every, for example, 30 seconds. When one, or more, of them respond with unexpected message or simply do not respond at all, dispatcher module put it/them as inactive automatically. I tried several conf scenarios but without success, all with gateway A off. Fore example: 1 -> I configure the three gateways (A, B and C) in conf file (sip.peers as configuration bellow) with flags 8 setted (probing destination). - When I start kamailio with probing mode equal to 1, all gateways present flags AP (using kamctl dispatcher dump) and nothing change (I only see OPTIONS sent to host B and C). - with probing mode setted to 0, all gateways start with flags AP, after 30 seconds, first OPTIONS are sent (only for B a C again), both B and C pass to AX and after more 30 seconds (ping interval defined) gateway A pass also to AX and OPTIONS stop being sent. 2-> Now I configured the gateways in conf file with flags 1 (inactive destination). - With prob mode 1, all started as IX, 30 seconds later it sends OPTIONS only for gw B and C and both change state to AP and A maintain IX. After more 30 seconds, no more OPTIONS are sent and gw A pass also to AP (hoped it remained IP or IX but not happened). I also tried other combinations of these two parameters, but only the onde I described above make me sense for my purpose. Maybe the solution is simple but I'm not getting there or maybe this it is only possible using failure or timeout routes and setting flags manually to gateways :( Can anyone point out the solution for this if it exists? module configuration used: modparam("dispatcher", "list_file", "sip.peers"); modparam("dispatcher", "flags", 2); modparam("dispatcher", "dst_avp", "$avp(AVP_DST)"); modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)"); modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)"); modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)"); modparam("dispatcher", "ds_ping_method", "OPTIONS"); modparam("dispatcher", "ds_ping_from", "sip:ping@test.tt"); modparam("dispatcher", "ds_ping_interval", 30); modparam("dispatcher", "ds_probing_threshold", 1); modparam("dispatcher", "ds_inactive_threshold", 1); modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=4;class=5;class=3"); modparam("dispatcher", "ds_probing_mode", 1); Thanks in advance, Paulo -- ------------------------------------------- Paulo Ferreira VoIP@RCTS - Área de Infraestruturas Aplicacionaisz FCCN http://www.fccn.pt/ Av. do Brasil, n.º 101 1700-066 Lisboa - Portugal Telefone|Phone: +351 218440100; Fax: +351 218472167 Aviso de Confidencialidade/Disclaimer Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha rececionado indevidamente esta mensagem,solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.

1 1

Dialog KeepAlive
by Duarte Rocha 18 Jan '18

18 Jan '18

Hey! I'm trying to use the KeepAlive options avaliable in the Dialog modules. For that I use the function dlg_set_property() like this : dlg_set_property("timeout-noreset"); dlg_set_property("ka-dst"); dlg_set_property("ka-src"); However, kamailio can't seem to get the answers from "ka-src". I've tried several scenarios and different call directions and i can never get the answer from the "ka-src". Is there any known issue about this feature ? What arguments kamailio uses to build the OPTIONS request? I think i might be albe to solve the issue if i know this. I have some endpoints behind NAT, Kamailio has multiple IP's and i do number normalization so my proxy works in E.164. I've made some tests and those features don't seem to be the problem, but i cannot be sure. The "ka-dst" works all the time under all situations. Thanks in advance, Cheers

1 0

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 18 Jan '18

18 Jan '18

How did you take the backtrace, it's not the usual gdb backtrace. Cheers, Daniel On 17.01.18 13:24, jenus(a)cyberchaos.nl wrote: > Daniel, > > Just tested this on another (centos-release-6-9.el6.12.3.x86_64) > machine and here kamailio crashes as well. Not sure if it helps but it > seems to happen on different linux distro's. > > Last part of the kamailio log: > > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_dset(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_msg(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_avp(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: KSR.exec > (exec) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.lock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.unlock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.trylock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_set_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_reset_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_get_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_event(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.abort(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.pkg_status(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.shm_status(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.pkg_summary(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.shm_summary(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.core_hash(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: > KSR.cfgutils (cfgutils) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.statistics.update_stat(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.statistics.reset_stat(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: > KSR.statistics (statistics) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.dostring(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.dofile(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.runstring(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p1(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p2(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p3(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: KSR.app_lua > (app_lua) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1978]: > lua_sr_kemi_register_libs(): module 'KSR' has been initialized > *** glibc detected *** kamailio: realloc(): invalid next size: > 0x0000000001d5f080 *** > ======= Backtrace: ========= > /lib64/libc.so.6[0x30f2a75dee] > /lib64/libc.so.6[0x30f2a7bcca] > /lib64/libc.so.6(realloc+0x158)[0x30f2a7bf08] > /usr/lib64/liblua-5.1.so[0x30fae0fd2c] > /usr/lib64/liblua-5.1.so[0x30fae0bb99] > /usr/lib64/liblua-5.1.so[0x30fae10765] > /usr/lib64/liblua-5.1.so[0x30fae13331] > /usr/lib64/liblua-5.1.so[0x30fae0bcf3] > /usr/lib64/liblua-5.1.so[0x30fae0c137] > /usr/lib64/liblua-5.1.so[0x30fae0c1b2] > /usr/lib64/liblua-5.1.so[0x30fae0c282] > /usr/lib64/liblua-5.1.so(lua_load+0x43)[0x30fae07ac3] > /usr/lib64/liblua-5.1.so(luaL_loadbuffer+0x1c)[0x30fae17d4c] > /usr/lib64/kamailio/modules/app_lua.so(lua_sr_init_probe+0x339)[0x7f042b343e9a] > > /usr/lib64/kamailio/modules/app_lua.so(+0x5f7e5)[0x7f042b3957e5] > kamailio[0x5c16d3] > kamailio(init_child+0x34)[0x5c1a01] > kamailio(main_loop+0x1e19)[0x422782] > kamailio(main+0x5939)[0x42a264] > /lib64/libc.so.6(__libc_start_main+0xfd)[0x30f2a1ed1d] > kamailio[0x418039] > ======= Memory map: ======== > 00400000-00837000 r-xp 00000000 fd:01 > 160801 /usr/sbin/kamailio > 00a37000-00a42000 rw-p 00437000 fd:01 > 160801 /usr/sbin/kamailio > 00a42000-00aef000 rw-p 00000000 00:00 0 > 01c1a000-01ceb000 rw-p 00000000 00:00 0 > 01ceb000-01d8d000 rw-p 00000000 00:00 0 > 30f2200000-30f2220000 r-xp 00000000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2420000-30f2421000 r--p 00020000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2421000-30f2422000 rw-p 00021000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2422000-30f2423000 rw-p 00000000 00:00 0 > 30f2600000-30f2602000 r-xp 00000000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2602000-30f2802000 ---p 00002000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2802000-30f2803000 r--p 00002000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2803000-30f2804000 rw-p 00003000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2a00000-30f2b8a000 r-xp 00000000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2b8a000-30f2d8a000 ---p 0018a000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d8a000-30f2d8e000 r--p 0018a000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d8e000-30f2d90000 rw-p 0018e000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d90000-30f2d94000 rw-p 00000000 00:00 0 > 30f2e00000-30f2e17000 r-xp 00000000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f2e17000-30f3017000 ---p 00017000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3017000-30f3018000 r--p 00017000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3018000-30f3019000 rw-p 00018000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3019000-30f301d000 rw-p 00000000 00:00 0 > 30f3200000-30f3207000 r-xp 00000000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3207000-30f3406000 ---p 00007000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3406000-30f3407000 r--p 00006000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3407000-30f3408000 rw-p 00007000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3600000-30f3615000 r-xp 00000000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3615000-30f3814000 ---p 00015000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3814000-30f3815000 r--p 00014000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3815000-30f3816000 rw-p 00015000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3a00000-30f3a83000 r-xp 00000000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3a83000-30f3c82000 ---p 00083000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3c82000-30f3c83000 r--p 00082000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3c83000-30f3c84000 rw-p 00083000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3e00000-30f3e1d000 r-xp 00000000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f3e1d000-30f401c000 ---p 0001d000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401c000-30f401d000 r--p 0001c000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401d000-30f401e000 rw-p 0001d000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401e000-30f401f000 rw-p 00000000 00:00 0 > 30f4200000-30f42a1000 r-xp 00000000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f42a1000-30f44a0000 ---p 000a1000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a0000-30f44a3000 r--p 000a0000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a3000-30f44a5000 rw-p 000a3000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a5000-30f44db000 rw-p 00000000 00:00 0 > 30f4600000-30f4616000 r-xp 00000000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4616000-30f4815000 ---p 00016000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4815000-30f4816000 rw-p 00015000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4a00000-30f4a16000 r-xp 00000000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4a16000-30f4c15000 ---p 00016000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c15000-30f4c16000 r--p 00015000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c16000-30f4c17000 rw-p 00016000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c17000-30f4c19000 rw-p 00000000 00:00 0 > 30f4e00000-30f4f3a000 r-xp 00000000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f4f3a000-30f5139000 ---p 0013a000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f5139000-30f513f000 r--p 00139000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f513f000-30f5141000 rw-p 0013f000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f5141000-30f5143000 rw-p 00000000 00:00 0 > 30f5200000-30f5226000 r-xp 00000000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5226000-30f5425000 ---p 00026000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5425000-30f542c000 r--p 00025000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f542c000-30f542d000 rw-p 0002c000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5600000-30f5604000 r-xp 00000000 fd:01 > 7552 /lib64/libplc4.so > 30f5604000-30f5803000 ---p 00004000 fd:01 > 7552 /lib64/libplc4.so > 30f5803000-30f5804000 r--p 00003000 fd:01 > 7552 /lib64/libplc4.so > 30f5804000-30f5805000 rw-p 00004000 fd:01 > 7552 /lib64/libplc4.so > 30f5a00000-30f5a39000 r-xp 00000000 fd:01 > 7551 /lib64/libnspr4.so > 30f5a39000-30f5c39000 ---p 00039000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c39000-30f5c3a000 r--p 00039000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c3a000-30f5c3c000 rw-p 0003a000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c3c000-30f5c3e000 rw-p 00000000 00:00 0 > 30f5e00000-30f5e03000 r-xp 00000000 fd:01 > 7553 /lib64/libplds4.so > 30f5e03000-30f6002000 ---p 00003000 fd:01 > 7553 /lib64/libplds4.so > 30f6002000-30f6003000 r--p 00002000 fd:01 > 7553 /lib64/libplds4.so > 30f6003000-30f6004000 rw-p 00003000 fd:01 > 7553 /lib64/libplds4.so > 30f6200000-30f6216000 r-xp 00000000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6216000-30f6416000 ---p 00016000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6416000-30f6417000 r--p 00016000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6417000-30f6418000 rw-p 00017000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6418000-30f641a000 rw-p 00000000 00:00 0 > 30f6600000-30f6604000 r-xp 00000000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6604000-30f6803000 ---p 00004000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6803000-30f6804000 r--p 00003000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6804000-30f6805000 rw-p 00004000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6a00000-30f6a08000 r-xp 00000000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6a08000-30f6c08000 ---p 00008000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6c08000-30f6c09000 rw-p 00008000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6e00000-30f6fba000 r-xp 00000000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f6fba000-30f71ba000 ---p 001ba000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71ba000-30f71d5000 r--p 001ba000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71d5000-30f71e1000 rw-p 001d5000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71e1000-30f71e5000 rw-p 00000000 00:00 0 > 30f7200000-30f736f000 r-xp 00000000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f736f000-30f756f000 ---p 0016f000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f756f000-30f7574000 rw-p 0016f000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f7574000-30f7575000 rw-p 00000000 00:00 0 > 30f7600000-30f7607000 r-xp 00000000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7607000-30f7806000 ---p 00007000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7806000-30f7807000 r--p 00006000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7807000-30f7808000 rw-p 00007000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7a00000-30f7a15000 r-xp 00000000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7a15000-30f7c14000 ---p 00015000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7c14000-30f7c15000 r--p 00014000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7c15000-30f7c16000 rw-p 00015000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7e00000-30f7e20000 r-xp 00000000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f7e20000-30f8020000 ---p 00020000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f8020000-30f8021000 rw-p 00020000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f8200000-30f8210000 r-xp 00000000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f8210000-30f840f000 ---p 00010000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f840f000-30f8411000 rw-p 0000f000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f8600000-30f8607000 r-xp 00000000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8607000-30f8807000 ---p 00007000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8807000-30f8808000 r--p 00007000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8808000-30f8809000 rw-p 00008000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8809000-30f8837000 rw-p 00000000 00:00 0 > 30f8a00000-30f8a04000 r-xp 00000000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8a04000-30f8c03000 ---p 00004000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8c03000-30f8c04000 rw-p 00003000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8e00000-30f8e02000 r-xp 00000000 fd:01 > 7534 /lib64/libfreebl3.so > 30f8e02000-30f9001000 ---p 00002000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9001000-30f9002000 r--p 00001000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9002000-30f9003000 rw-p 00002000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9200000-30f9228000 r-xp 00000000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9228000-30f9427000 ---p 00028000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9427000-30f942b000 r--p 00027000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f942b000-30f942c000 rw-p 0002b000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9600000-30f9603000 r-xp 00000000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9603000-30f9802000 ---p 00003000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9802000-30f9803000 r--p 00002000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9803000-30f9804000 rw-p 00003000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9a00000-30f9a47000 r-xp 00000000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9a47000-30f9c47000 ---p 00047000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c47000-30f9c4b000 r--p 00047000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c4b000-30f9c4c000 rw-p 0004b000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c4c000-30f9c4d000 rw-p 00000000 00:00 0 > 30f9e00000-30f9f62000 r-xp 00000000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30f9f62000-30fa162000 ---p 00162000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30fa162000-30fa16b000 rw-p 00162000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30fa200000-30fa349000 r-xp 00000000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa349000-30fa548000 ---p 00149000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa548000-30fa552000 rw-p 00148000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa552000-30fa553000 rw-p 00000000 00:00 0 > 30fa600000-30fa664000 r-xp 00000000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa664000-30fa863000 ---p 00064000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa863000-30fa86a000 rw-p 00063000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa86a000-30fa86b000 rw-p 00000000 00:00 0 > 30faa00000-30faa2a000 r-xp 00000000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30faa2a000-30fac2a000 ---p 0002a000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30fac2a000-30fac2d000 rw-p 0002a000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30fac2d000-30fac2f000 rw-p 00000000 00:00 0 > 30fae00000-30fae2b000 r-xp 00000000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fae2b000-30fb02b000 ---p 0002b000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fb02b000-30fb02d000 rw-p 0002b000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fb200000-30fb390000 r-xp 00000000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb390000-30fb58f000 ---p 00190000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb58f000-30fb595000 r--p 0018f000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb595000-30fb59c000 rw-p 00195000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb59c000-30fb6c8000 rw-p 00000000 00:00 0 > 30fb800000-30fb825000 r-xp 00000000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fb825000-30fba24000 ---p 00025000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fba24000-30fba25000 r--p 00024000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fba25000-30fba26000 rw-p 00025000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fbc00000-30fbc48000 r-xp 00000000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbc48000-30fbe48000 ---p 00048000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe48000-30fbe4a000 r--p 00048000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe4a000-30fbe4b000 rw-p 0004a000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe4b000-30fbe4c000 rw-p 00000000 00:00 0 > 30fc000000-30fc00f000 r-xp 00000000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fc00f000-30fc20f000 ---p 0000f000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fc20f000-30fc210000 rw-p 0000f000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fca00000-30fcadc000 r-xp 00000000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fcadc000-30fccdb000 ---p 000dc000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fccdb000-30fcce5000 r--p 000db000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fcce5000-30fcce7000 rw-p 000e5000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fce00000-30fce29000 r-xp 00000000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fce29000-30fd029000 ---p 00029000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd029000-30fd02a000 r--p 00029000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd02a000-30fd02b000 rw-p 0002a000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd02b000-30fd02c000 rw-p 00000000 00:00 0 > 30fd200000-30fd241000 r-xp 00000000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd241000-30fd441000 ---p 00041000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd441000-30fd442000 r--p 00041000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd442000-30fd444000 rw-p 00042000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd600000-30fd60a000 r-xp 00000000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd60a000-30fd809000 ---p 0000a000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd809000-30fd80a000 r--p 00009000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd80a000-30fd80b000 rw-p 0000a000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fda00000-30fda02000 r-xp 00000000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fda02000-30fdc01000 ---p 00002000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fdc01000-30fdc02000 r--p 00001000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fdc02000-30fdc03000 rw-p 00002000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fde00000-30fde62000 r-xp 00000000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fde62000-30fe062000 ---p 00062000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe062000-30fe066000 r--p 00062000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe066000-30fe06c000 rw-p 00066000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe200000-30fe232000 r-xp 00000000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe232000-30fe431000 ---p 00032000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe431000-30fe432000 rw-p 00031000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe600000-30fe619000 r-xp 00000000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe619000-30fe818000 ---p 00019000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe818000-30fe819000 r--p 00018000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe819000-30fe81a000 rw-p 00019000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fea00000-30fea4e000 r-xp 00000000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fea4e000-30fec4d000 ---p 0004e000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fec4d000-30fec4f000 r--p 0004d000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fec4f000-30fec51000 rw-p 0004f000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fee00000-30fee0e000 r-xp 00000000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30fee0e000-30ff00d000 ---p 0000e000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff00d000-30ff00e000 r--p 0000d000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff00e000-30ff00f000 rw-p 0000e000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff200000-30ff227000 r-xp 00000000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff227000-30ff426000 ---p 00027000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff426000-30ff428000 rw-p 00026000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff600000-30ff653000 r-xp 00000000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 30ff653000-30ff852000 ---p 00053000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 30ff852000-30ff855000 rw-p 00052000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 3baec00000-3baec2c000 r-xp 00000000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 3baec2c000-3baee2c000 ---p 0002c000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 3baee2c000-3baee2d000 rw-p 0002c000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 7f03e4000000-7f03e4021000 rw-p 00000000 00:00 0 > 7f03e4021000-7f03e8000000 ---p 00000000 00:00 0 > 7f03eaf22000-7f03eaf27000 r-xp 00000000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eaf27000-7f03eb126000 ---p 00005000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb126000-7f03eb127000 r--p 00004000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb127000-7f03eb128000 rw-p 00005000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb128000-7f03eb135000 r-xp 00000000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb135000-7f03eb334000 ---p 0000d000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb334000-7f03eb335000 r--p 0000c000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb335000-7f03eb336000 rw-p 0000d000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb336000-7f042b336000 rw-s 00000000 00:04 > 30666920 /dev/zero (deleted) > 7f042b336000-7f042b3e0000 r-xp 00000000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b3e0000-7f042b5df000 ---p 000aa000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b5df000-7f042b5e5000 rw-p 000a9000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b5e5000-7f042b5e7000 rw-p 00000000 00:00 0 > 7f042b5e7000-7f042b5ee000 r-xp 00000000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b5ee000-7f042b7ed000 ---p 00007000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b7ed000-7f042b7ee000 rw-p 00006000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b7ee000-7f042b7ff000 r-xp 00000000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042b7ff000-7f042b9ff000 ---p 00011000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042b9ff000-7f042ba00000 rw-p 00011000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042ba00000-7f042ba15000 r-xp 00000000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042ba15000-7f042bc15000 ---p 00015000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042bc15000-7f042bc16000 rw-p 00015000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042bc16000-7f042bc1c000 r-xp 00000000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042bc1c000-7f042be1c000 ---p 00006000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042be1c000-7f042be1d000 rw-p 00006000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042be1d000-7f042be29000 r-xp 00000000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042be29000-7f042c028000 ---p 0000c000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042c028000-7f042c029000 rw-p 0000b000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042c029000-7f042c038000 r-xp 00000000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c038000-7f042c237000 ---p 0000f000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c237000-7f042c238000 rw-p 0000e000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c238000-7f042c23a000 r-xp 00000000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c23a000-7f042c439000 ---p 00002000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c439000-7f042c43a000 r--p 00001000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c43a000-7f042c43b000 rw-p 00002000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c43b000-7f042c443000 r-xp 00000000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c443000-7f042c643000 ---p 00008000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c643000-7f042c644000 r--p 00008000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c644000-7f042c645000 rw-p 00009000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c645000-7f042c646000 rw-p 00000000 00:00 0 > 7f042c646000-7f042c677000 r-xp 00000000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c677000-7f042c876000 ---p 00031000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c876000-7f042c87a000 rw-p 00030000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c87a000-7f042c889000 r-xp 00000000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042c889000-7f042ca89000 ---p 0000f000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042ca89000-7f042ca8a000 rw-p 0000f000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042ca8a000-7f042ca8f000 r-xp 00000000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042ca8f000-7f042cc8e000 ---p 00005000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042cc8e000-7f042cc8f000 rw-p 00004000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042cc8f000-7f042cca1000 r-xp 00000000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cca1000-7f042cea1000 ---p 00012000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cea1000-7f042cea2000 rw-p 00012000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cea2000-7f042cf58000 r-xp 00000000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042cf58000-7f042d157000 ---p 000b6000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042d157000-7f042d15a000 rw-p 000b5000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042d15a000-7f042d183000 r-xp 00000000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d183000-7f042d382000 ---p 00029000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d382000-7f042d383000 rw-p 00028000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d383000-7f042d38d000 r-xp 00000000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d38d000-7f042d58d000 ---p 0000a000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d58d000-7f042d58e000 rw-p 0000a000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d58e000-7f042d5c2000 r-xp 00000000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d5c2000-7f042d7c2000 ---p 00034000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d7c2000-7f042d7c3000 rw-p 00034000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d7c3000-7f042d7df000 r-xp 00000000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d7df000-7f042d9df000 ---p 0001c000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d9df000-7f042d9e0000 rw-p 0001c000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d9e0000-7f042da3a000 r-xp 00000000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042da3a000-7f042dc3a000 ---p 0005a000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042dc3a000-7f042dc3c000 rw-p 0005a000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042dc3c000-7f042dc47000 rw-p 00000000 00:00 0 > 7f042dc47000-7f042dc8e000 r-xp 00000000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042dc8e000-7f042de8d000 ---p 00047000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042de8d000-7f042de8f000 rw-p 00046000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042de8f000-7f042de9c000 r-xp 00000000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042de9c000-7f042e09b000 ---p 0000d000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042e09b000-7f042e09c000 rw-p 0000c000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042e09c000-7f042e0e8000 r-xp 00000000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e0e8000-7f042e2e8000 ---p 0004c000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e2e8000-7f042e2ea000 rw-p 0004c000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e2ea000-7f042e303000 r-xp 00000000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e303000-7f042e503000 ---p 00019000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e503000-7f042e504000 rw-p 00019000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e504000-7f042e505000 rw-p 00000000 00:00 0 > 7f042e505000-7f042e549000 r-xp 00000000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e549000-7f042e748000 ---p 00044000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e748000-7f042e74a000 rw-p 00043000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e74a000-7f042e74b000 rw-p 00000000 00:00 0 > 7f042e74b000-7f042e764000 r-xp 00000000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e764000-7f042e964000 ---p 00019000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e964000-7f042e965000 rw-p 00019000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e965000-7f042e998000 r-xp 00000000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042e998000-7f042eb97000 ---p 00033000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042eb97000-7f042eb99000 rw-p 00032000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042eb99000-7f042ebd2000 r-xp 00000000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042ebd2000-7f042edd2000 ---p 00039000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042edd2000-7f042edd4000 rw-p 00039000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042edd4000-7f042ee07000 r-xp 00000000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042ee07000-7f042f006000 ---p 00033000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042f006000-7f042f008000 rw-p 00032000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042f008000-7f042f018000 rw-p 00000000 00:00 0 > 7f042f018000-7f042f02a000 r-xp 00000000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f02a000-7f042f22a000 ---p 00012000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f22a000-7f042f22b000 rw-p 00012000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f22b000-7f042f241000 r-xp 00000000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f241000-7f042f441000 ---p 00016000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f441000-7f042f442000 rw-p 00016000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f442000-7f042f482000 r-xp 00000000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f482000-7f042f681000 ---p 00040000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f681000-7f042f683000 rw-p 0003f000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f683000-7f042f684000 rw-p 00000000 00:00 0 > 7f042f684000-7f042f699000 r-xp 00000000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f699000-7f042f899000 ---p 00015000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f899000-7f042f89a000 rw-p 00015000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f89a000-7f042f8c5000 r-xp 00000000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042f8c5000-7f042fac4000 ---p 0002b000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042fac4000-7f042fac6000 rw-p 0002a000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042fac6000-7f042fad2000 r-xp 00000000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fad2000-7f042fcd2000 ---p 0000c000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fcd2000-7f042fcd3000 rw-p 0000c000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fcd3000-7f042fcdf000 r-xp 00000000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fcdf000-7f042fede000 ---p 0000c000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fede000-7f042fedf000 rw-p 0000b000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fedf000-7f042ff17000 r-xp 00000000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f042ff17000-7f0430117000 ---p 00038000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f0430117000-7f0430118000 rw-p 00038000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f0430118000-7f043013c000 rw-p 00000000 00:00 0 > 7f043013c000-7f0430177000 r-xp 00000000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430177000-7f0430377000 ---p 0003b000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430377000-7f0430378000 rw-p 0003b000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430378000-7f043037d000 r-xp 00000000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043037d000-7f043057c000 ---p 00005000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043057c000-7f043057d000 rw-p 00004000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043057d000-7f04305c9000 r-xp 00000000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04305c9000-7f04307c9000 ---p 0004c000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04307c9000-7f04307ca000 rw-p 0004c000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04307ca000-7f04307db000 rw-p 00000000 00:00 0 > 7f04307db000-7f04307f2000 r-xp 00000000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04307f2000-7f04309f1000 ---p 00017000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04309f1000-7f04309f2000 rw-p 00016000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04309f2000-7f04309fe000 r-xp 00000000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f04309fe000-7f0430bfe000 ---p 0000c000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f0430bfe000-7f0430bff000 rw-p 0000c000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f0430bff000-7f0430c3a000 r-xp 00000000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430c3a000-7f0430e3a000 ---p 0003b000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430e3a000-7f0430e3c000 rw-p 0003b000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430e3c000-7f0430e88000 r-xp 00000000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f0430e88000-7f0431087000 ---p 0004c000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f0431087000-7f043108a000 rw-p 0004b000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f043108a000-7f04310c8000 r-xp 00000000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04310c8000-7f04312c7000 ---p 0003e000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04312c7000-7f04312c9000 rw-p 0003d000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04312c9000-7f043130d000 r-xp 00000000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043130d000-7f043150d000 ---p 00044000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043150d000-7f043150f000 rw-p 00044000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043150f000-7f0431549000 r-xp 00000000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f0431549000-7f0431748000 ---p 0003a000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f0431748000-7f043174a000 rw-p 00039000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f043174a000-7f0431793000 r-xp 00000000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431793000-7f0431992000 ---p 00049000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431992000-7f0431995000 rw-p 00048000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431995000-7f04319e0000 r-xp 00000000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f04319e0000-7f0431be0000 ---p 0004b000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f0431be0000-7f0431be2000 rw-p 0004b000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f0431be2000-7f0431be8000 r-xp 00000000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431be8000-7f0431de8000 ---p 00006000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431de8000-7f0431de9000 rw-p 00006000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431de9000-7f0431e8c000 r-xp 00000000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f0431e8c000-7f043208b000 ---p 000a3000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f043208b000-7f0432090000 rw-p 000a2000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f0432090000-7f0432091000 rw-p 00000000 00:00 0 > 7f0432091000-7f04320c1000 r-xp 00000000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04320c1000-7f04322c0000 ---p 00030000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04322c0000-7f04322c2000 rw-p 0002f000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04322c2000-7f04322db000 r-xp 00000000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04322db000-7f04324da000 ---p 00019000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04324da000-7f04324dc000 rw-p 00018000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04324dc000-7f04324f8000 r-xp 00000000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04324f8000-7f04326f8000 ---p 0001c000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04326f8000-7f04326fa000 rw-p 0001c000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04326fa000-7f04326fb000 rw-p 00000000 00:00 0 > 7f04326fb000-7f0432829000 r-xp 00000000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432829000-7f0432a29000 ---p 0012e000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432a29000-7f0432a2e000 rw-p 0012e000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432a2e000-7f0432a40000 rw-p 00000000 00:00 0 > 7f0432a40000-7f0432a55000 r-xp 00000000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432a55000-7f0432c55000 ---p 00015000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432c55000-7f0432c56000 rw-p 00015000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432c56000-7f0432c65000 r-xp 00000000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432c65000-7f0432e65000 ---p 0000f000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432e65000-7f0432e66000 rw-p 0000f000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432e66000-7f0432e75000 r-xp 00000000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0432e75000-7f0433074000 ---p 0000f000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0433074000-7f0433076000 rw-p 0000e000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0433076000-7f04330a4000 r-xp 00000000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04330a4000-7f04332a4000 ---p 0002e000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04332a4000-7f04332a5000 rw-p 0002e000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04332a5000-7f04332b1000 r-xp 00000000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04332b1000-7f04334b0000 ---p 0000c000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04334b0000-7f04334b1000 rw-p 0000b000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04334b1000-7f04335e7000 r-xp 00000000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f04335e7000-7f04337e6000 ---p 00136000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f04337e6000-7f0433834000 rw-p 00135000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f0433834000-7f0433835000 rw-p 00000000 00:00 0 > 7f043383c000-7f043386f000 r-xp 00000000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f043386f000-7f0433a6e000 ---p 00033000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f0433a6e000-7f0433a70000 rw-p 00032000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f0433a70000-7f0434274000 rw-p 00000000 00:00 0 > 7f0434278000-7f043427a000 rw-p 00000000 00:00 0 > 7f043427a000-7f043427c000 rw-p 00000000 00:00 0 > 7ffe9e90c000-7ffe9e921000 rw-p 00000000 00:00 > 0 [stack] > 7ffe9e9cc000-7ffe9e9cd000 r-xp 00000000 00:00 > 0 [vdso] > ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 > 0 [vsyscall] > > [...] -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Kamailio 5.0.4 WebSocket failover to secondary
by James Aylett 18 Jan '18

18 Jan '18

Hello, I am testing failover scenarios between two Active/Active kamailios for Sip over WebSockets and WebRTC. In my test scenario, I have setup the call through proxy-a, then stopped the kamailio service so that the sip client reconnects to proxy-b. Dialogs and registrations are shared across both instances using MariaDB and Galera. When the SIP client reconnects to proxy-b, I send a BYE and see the following errors in the logs: Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: Connection ID: 1 Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: WITHINDLG Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: RELAY Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: WARNING: <core> [core/msg_translator.c:2765]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <core> [core/msg_translator.c:1980]: build_req_buf_from_sip_req(): could not create Via header Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: tm [t_fwd.c:476]: prepare_new_uac(): could not build request Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: tm [t_fwd.c:1732]: t_forward_nonack(): failure to add branches Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: No error (2/SL) It seems that core/msg_translator.c is using the wrong WebSocket connection ID (0 rather than 1). Is this a bug in Kamailio or a limitation that I do not understand? I have assumed that the BYE is a new transaction for the existing dialog so t_relay() should be able to forward the message. I can provide config and any additional error logs if required. Any help is much appreciated. Thanks, James

1 0

exec warning
by voipspace voipspace 17 Jan '18

17 Jan '18

exec_msg gives the following warning. Even when no variables are used in the parameters 8(29619) WARNING: exec [exec_hf.c:464]: append_fixed_vars(): uri not parsed 8(29619) WARNING: exec [exec_hf.c:482]: append_fixed_vars(): orig URI not parsed

2 2

kamailio 5.1 from git compile error
by Abdul Basit 17 Jan '18

17 Jan '18

Hi, I am trying to compile kamailio 5.1 from git following https://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/ on Debian GNU/Linux 8.10 (jessie) I also installed packages after getting dependency errors apt-get install libhiredis-dev libphonenumber6-dev libicu-dev apt-get install unicode unicode-data Kamailio compile stopped at error ..... LD (gcc) [M uid_avp_db.so] uid_avp_db.so CC (gcc) [M pdb.so] pdb.o LD (gcc) [M pdb.so] pdb.so CC (gcc) [M phonenum.so] phonenum_mod.o CC (gcc) [M phonenum.so] phonenum_pv.o Compiling cphonenumber.cpp g++ -fPIC -DPIC -g -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -Wno-write-strings -Wno-deprecated -Wno-unused-f unction -Wno-sign-compare -Wno-strict-aliasing -fPIC -DPIC -g -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -DNA ME='"kamailio"' -DVERSION='"5.1.0"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.9.2"' -D__CPU_x86_64 -D__OS_linux -DSER_VER=5001000 -DCFG_DIR='"/usr/loc al/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS _FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DMEM_JOIN_FREE -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLO C_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_ NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SE LECT -I/opt/local/include -DKAMAILIO_MOD_INTERFACE -DMOD_NAME='"phonenum"' -c cphonenumber.cpp -o cphonenumber.o In file included from /usr/include/phonenumbers/geocoding/phonenumber_offline_geocoder.h:26:0, from cphonenumber.cpp:24: /usr/include/phonenumbers/base/memory/scoped_ptr.h:25:45: fatal error: phonenumbers/base/template_util.h: No such file or directory #include "phonenumbers/base/template_util.h" ^ compilation terminated. Makefile:22: recipe for target 'cphonenumber.o' failed make[2]: *** [cphonenumber.o] Error 1 Makefile:511: recipe for target 'modules' failed make[1]: *** [modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio/src' Makefile:27: recipe for target 'all' failed make: *** [all] Error 2 I googled but couldnt found any resolution or required dependency. Its look like libphonenumber is broken. Kindly suggest way out. Also i don't require libphonenumber for this server. How to get rid off. -- regards, abdul basit

3 5

send LUA logs via HEP to Homer server
by Abdul Basit 17 Jan '18

17 Jan '18

Hi K-team, I am processing incoming INVITE events in my lua script. To print the logs with kamailio syslog, i am using sr.log("info", "-- Collecting data from kamailio -- ") I am searching for a way to send selective logs for an incoming call from lua script through HEP3 towards Homer server. How can I make it work? What utility or library is helpful. *PS:* captagent is configured on the same server for SIP traces. -- regards, abdul basit

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