- sr-users - kamailio.org

WebRTC bad message (offset: 22)
by Ilie Soltanici 28 May '19

28 May '19

Hello, Can someone help me to discard those messages from kamailio log files? ERROR: <core> [core/parser/parse_fline.c:262]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TLS 212.2.161.34:60477#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: VeiXbJClWneIrIyYgM5v3XKYHLA=#015#012Server: WebRTC GW#015#012Content-Length: 0#015#012#015#012> As I understand this is just an HTTP response to the first request, and shouldn't go through config file execution, but I don't understand why it is getting through it. Thank you

1 0

kamailio webrtc 183 early media.
by Zhan Bazarov 28 May '19

28 May '19

Hello! I have setup kamailio+rtpengine+asterisk.. And I have issue with early media for WEBrtc endpoints... As I understood right, for this case I need to use rel100(PRACK) for sending early media... But I didn't find any example for solve this issue... Can you help me with it? It would be greatly appreciated!

1 0

mem leak on 5.1.2?
by Andrew Chen 27 May '19

27 May '19

Hey guys, Need some help with possible run away memory issue on my 5.1.2 Kamailio. I noticed I'm getting this memory error from kam logs: May 24 13:47:52 ashintgtpsg51 /usr/sbin/kamailio[1857]: WARNING: http_client [functions.c:298]: curL_query_url(): Curl library out of memory (url:https://<some url>) my -m on kamailio startup is currently set to 64 but there is only 1 call going through. In our check_mk, I noticed the memory usage is ramping up: [image: image.png] What's the cause of this? -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

4 8

Getting the following error when sending INVITE request for calling
by Mohit Chawla 27 May '19

27 May '19

Hi , I am getting the following error in trying to send INVITE message from SIP client. {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} NOTICE: acc [acc.c:281]: acc_log_request(): ACC: transaction answered: timestamp=1558902843;method=INVITE;from_tag=69588468;to_tag=ebd29a60;call_id=4_Do2VIMWLR6Wf5ubiBxgg..;code=200;reason=OK;src_user=1016;src_domain=172.25.22.23;src_ip=172.25.22.40;dst_ouser=1015;dst_user=1015;dst_domain=172.25.22.40 May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: <core> [db_query.c:243]: db_do_insert_cmd(): error while submitting query May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: acc [acc.c:477]: acc_db_request(): failed to insert into database May 27 02:04:10 epc-srv-03 /usr/sbin/kamailio[17229]: {2 3 BYE 4_Do2VIMWLR6Wf5ubiBxgg..} NOTICE: acc [acc.c:281]: acc_log_request(): ACC: transaction answered: *Can anyone help me understand the reason for this error.* *I am attaching the used kamailio.cfg file in this message.* *Thanks and Regards,* *Mohit* -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

2 6

remove_hf() leaves junk in the headers?
by Oded Arbel 27 May '19

27 May '19

I'm trying to rewrite the `From` header in an invite going out to an external system (*), by calling remove_hf("From"); followed by append_hf("From: <some value>\r\n"); but the result is an invalid SIP message, because apparently after `remove_hf()` finishes, it leaves the content of $fU in place of the `From` header - just the raw text, without a header name or even a "\r\n" - and that eats the next header line and breaks the INVITE. Here is how the INVITE originally looks (without either `remove_hf()` or `append_hf()`): ---8<--- INVITE sip:972522353283@10.20.30.40:5060 SIP/2.0 Record-Route: <sip:10.90.80.70;lr;did=649.f0b> Via: SIP/2.0/UDP 10.90.80.70:5060;branch=z9hG4bK6188.ff5c4fd855bd2970fdf32d4807b114c2.0 Via: SIP/2.0/UDP 10.90.80.71:5066;received=10.90.80.71;branch=z9hG4bK581897a4;rport=5066 Max-Forwards: 69 From: <sip:972515340014@example.com:5066>;tag=as0bcee217 To: <sip:972522353283@10.20.30.40:5060> Contact: <sip:972515340014@10.90.80.71:5066> Call-ID: 722299dc15aad53d28172d433e8665f4@10.90.80.71:5066 CSeq: 102 INVITE User-Agent: Asterisk PBX 14.7.2 Date: Sun, 26 May 2019 14:42:52 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: ad199638-4df3-4aef-81f1-1b50581032a7 Content-Type: application/sdp Content-Length: 280 v=0 o=root 817636675 817636675 IN IP4 10.50.60.70 s=Asterisk PBX 14.7.2 c=IN IP4 10.50.60.70 t=0 0 m=audio 39064 RTP/AVP 8 0 18 9 a=maxptime:60 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:39065 a=ptime:20 ---8<--- and here is another call with the same setup, with just `remove_hf("From");` being invoked (without calling `append_hf()` - this is just for reproduction): ---8<--- INVITE sip:972522353283@10.20.30.40:5060 SIP/2.0 Record-Route: <sip:10.90.80.70;lr;did=f45.91b1> Via: SIP/2.0/UDP 10.90.80.70:5060;branch=z9hG4bK024d.2690ebf7a809edca2208e6b2561ccf9e.0 Via: SIP/2.0/UDP 10.90.80.71:5066;received=10.90.80.71;branch=z9hG4bK79ae3073;rport=5066 Max-Forwards: 69 972515340014To: <sip:972522353283@10.20.30.40:5060> Contact: <sip:972515340014@10.90.80.71:5066> Call-ID: 7b20ba5a549f6f886c22985146765736@10.90.80.71:5066 CSeq: 102 INVITE User-Agent: Asterisk PBX 14.7.2 Date: Sun, 26 May 2019 14:44:20 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: ffbb4ac1-3a0f-4dd6-9ce9-7ad24361081a Content-Type: application/sdp Content-Length: 280 v=0 o=root 509740923 509740923 IN IP4 10.50.60.70 s=Asterisk PBX 14.7.2 c=IN IP4 10.50.60.70 t=0 0 m=audio 39102 RTP/AVP 8 0 18 9 a=maxptime:60 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:39103 a=ptime:20 ---8<--- As you can see, the `From` header is indeed gone, but it left the $fU just before the `To` header. WTF? I'm running Kamailio 5.2.2 built locally. Notes: *) the problem I'm trying to solve is that I can't get my Asterisk installation to generate the `From` header I want, the reason is out of scope of this question, so I'm sending custom SIP headers over to Kamaiio and I want to rewrite the header in Kamailio to the "correct" value. -- Oded Arbel

6 8

PRE-PAY update timer
by Steve Bucklin 25 May '19

25 May '19

Hello all (again), I am looking at a 'good' method to start a call with "chunks" of time allocated. I wish the initial call to check a credit, and if credit is good, allow a small amount of time (say 30 seconds). I have enabled DIALOG and have looked at CNXCC, but am confused! When the initial 30 seconds runs out, I want to authorise another 30 seconds, etc, etc, etc. I have started to play and set a dialog timer that expires to a route, and then can 'return' allowing the call to continue - BUT was not able to reset the dialog timer to trip again after another 30 seconds. I tried to 'set_max_time' on cnxcc, but this did not seem to trip the event route upon timeout? Does anyone have a pointer to any examples? I also am unsure of how to update the timer and keep a call in play! Steve

5 4

No Private memory left using usrloc with db_redis in mode 3
by José Seabra 24 May '19

24 May '19

Hello there, i have stored ~200 000 registrations contacts in redis database and when kamailio starts looking for expired contacts in redis then it starts giving these errors: WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1099]: db_redis_perform_query(): performing full table scan on table 'location' while performing query WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 0 is 'expires' *WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 1 is 'expires'* *ERROR: PR_LOG: 123: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7ff80922b010, 3055920); Free fragment not found!* *ERROR: PR_LOG: 123: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7ff80922b010, 3055920) called from core: db_res.c: db_allocate_rows(183), module: core; Free fragment not found!* *ERROR: PR_LOG: 123: <core> [db_res.c:185]: db_allocate_rows(): no private memory left* *ERROR: PR_LOG: 123: db_redis [redis_dbase.c:1115]: db_redis_perform_query(): Failed to allocate memory for rows * I have configured the private memory to 128 MB but seems that isn't enough to handle with all these contacts. Is the only option here increase the private memory or there is any other kind of configuration(in redis or kamailio) that i can make to avoid this? Best Regards José Seabra -- Cumprimentos José Seabra

2 1

Re: [SR-Users] Kamailio IMS installation from pacakges
by Mohit Chawla 24 May '19

24 May '19

Hi, My name is Mohit Chawla working on LTE Network integration with Kamailio IMS server. We are facing issues in installation & Configuring of kamailio IMS on CentOS 7 due to no documentation is available on web (or at least I am not able to find one). Primarily I am interested in installing packages (not building from source code as of now) and use it for further testing. I can go with building the package from source if its more easier and quick. Can you guys help me share any document/wiki which is helpful for my cause ? I will be really grateful if someone can reply me by today. Thanks and Regards, Mohit From: Mohit Chawla [mailto:mohit.chawla@azcom.in] Sent: Wednesday, May 22, 2019 5:57 PM To: 'sr-users(a)lists.kamailio.org' Subject: Kamailio IMS installation from pacakges Hi, My name is Mohit Chawla working on LTE Network integration with Kamailio IMS server. We are facing issues in installation & Configuring of kamailio IMS on CentOS 7 due to no documentation is available on web (or at least I am not able to find one). Primarily I am interested in installing packages (not building from source code as of now) and use it for further testing. I can go with building the package from source if its more easier and quick. Can you guys help me share any document/wiki which is helpful for my cause ? I will be really grateful if someone can reply me by today. Thanks and Regards, Mohit -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

2 3

Use of kamailio as IMS server to integrate with LTE Core Network
by Mohit Chawla 24 May '19

24 May '19

Hi , We have successfully installed the kamailio IMS server on centOS 7 using the following link (http://www.kamailio.org/wiki/tutorials/ims/installation-howto) with appropriate changes for command in CentOS 7. We are currently trying to integrate the PCSCF module with LTE Core network , but I don't have any idea how to do this. Neither I am able to find any tutorials which I can use to understand how kamailio works. Can anyone share any reference document to help me understand the kamailio working in my use case. Thanks and Regards, Mohit -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

1 0

listen (bind) to variable ip and port
by Roiss-Weiss, Roman 23 May '19

23 May '19

Hi guys, is it somehow possible to bind to a variable ip-address and port? e.g. getting the ip and port from a database? Kind regards, Roman

3 2

Kamailio CDRs for calls interrupted without BYE
by Ildar Mukhametzhanov 23 May '19

23 May '19

Hello! I am using dialog+acc modules to write CDRs in kamailio. Everything works great except one test. During active call I switched off both UACs preventing them to send BYE. Rtpengine reported about call interruption, but kamailio thinks that this call is in-progress for a long time. What is the right way to make kamailio know about calls interrupted without BYE. Thanks. -- Sincerely, *Ildar Mukhametzhanov* Head of software development VoiceON Telecom Services GmbH im(a)voice-on.net <mailto:im@voice-on.net> t. +49 30 398 20 500-77

3 8

warning logs - DB_Redis and usrloc in mode 3
by José Seabra 22 May '19

22 May '19

Hello there, I'm testing the db_redis with usrloc module in mode 3 and i have been noticing that every time that kamailio checks if there is contacts expired then it logs the following warning messages: *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1099]: db_redis_perform_query(): performing full table scan on table 'location' while performing query* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 0 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 1 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1274]: db_redis_perform_delete(): performing full table scan on table 'location' while performing delete* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 0 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 1 is 'expires'* I'm not sure what is the rational behind of this, but having these logs being written when we have log level equal 2 in production is something unnecessary, so i'm asking if it shouldn't be better we have it as debug instead of warning? or do you forecast any performance issues using usrloc module in mode 3 with db_redis? Thank you for your support Cheers José -- Cumprimentos José Seabra

2 1

Re: [SR-Users] Modern SIP Trunking, Route on To: or INVITE Headers?
by JR Richardson 22 May '19

22 May '19

Benoit, Alex, I appreciate the feedback, confirming my assumptions. Good news is the Vendor finally responded positively and agreed to add in configuration option to route on INVITE R-URI in next SDK release, expected later this year. In the meantime I added 'uac_replace_to' function to my proxy to re-write To: header with R-URI, so far so good. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope > > The To header is a cosmetic, purely logical commentary on the intended ultimate destination of the call, and no routing should ever be done on it. The RURI of the INVITE is the appropriate vehicle for that. > > When dealing with proxies, however, one will encounter from time to time the grim reality that there are user agents which expect the To URI and the INVITE RURI to be in alignment. For that scenario, you can use ‘uac’ module’s stateful rewriting functionally (uac_replace_to()) to modify To with Kamailio in a way that displays fidelity and esteem for protocol formalities. > > — > Sent from mobile, with due apologies for brevity and errors. > > > On May 21, 2019, at 9:32 AM, JR Richardson <jmr.richardson(a)gmail.com> wrote: > > > > Hey Folks, > > > > I could use some feedback to see if my mind is right on this topic.I'm > > in a discussion with a software Vendor (respectfully unnamed) with > > terminal software routing on To: header info. It's my contention any > > modern SIP software should use INVITE header to retrieve DID info and > > route from there. > > > > My reasoning is due to the To: header should contain the original > > intended DID, Extension, Name, AoR or whatever else the original SIP > > transaction wanted to contact, but being in a multi-carrier, > > multi-hop, call forwarding environment, the INVITE header contains the > > hop-to-hop true intention of where the call should route at any given > > transaction. So in the case of terminal software the To: header could > > likely be irrelevant where as the INVITE header is accurate. > > > > My most recent response from the Vendor suggest I put a SIP Proxy in > > front of the terminal software and transform the To: header to > > whatever I need for this application. Although I can do this, I'm > > concerned with breaking RFC for CANCEL and BYE transaction sent back > > from the terminal software that may not be recognized by upstream > > origination carriers. > > > > Plus modifying To: header is widely frowned upon by most folks. > > > > Thanks. > > > > JR

1 0

Kamailio v5.2.3 Released
by Daniel-Constantin Mierla 22 May '19

22 May '19

Hello, Kamailio SIP Server v5.2.3 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.3. For more details about version 5.2.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/05/kamailio-v5-2-3-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.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Kamailio IMS installation from pacakges
by Mohit Chawla 22 May '19

22 May '19

Hi, My name is Mohit Chawla working on LTE Network integration with Kamailio IMS server. We are facing issues in installation & Configuring of kamailio IMS on CentOS 7 due to no documentation is available on web (or at least I am not able to find one). Primarily I am interested in installing packages (not building from source code as of now) and use it for further testing. I can go with building the package from source if its more easier and quick. Can you guys help me share any document/wiki which is helpful for my cause ? I will be really grateful if someone can reply me by today. Thanks and Regards, Mohit -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

1 0

Releasing Kamailio v5.2.3
by Daniel-Constantin Mierla 22 May '19

22 May '19

Hello, I am considering to release Kamailo v5.2.3 out of latest git branch 5.2 next week, likely on Wednesday, May 22. As usual, if you are aware of issues not reported to the github bug tracker, fill a report there as soon as possible to give a chance to be analyzed and fixed. Also, if there was a fix for an issue that you were reporting, check to see if it was backported to be sure it is not forgotten. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

remove_hf inside of onreply_route
by Володимир Іванець 21 May '19

21 May '19

Hello! I was wondering if someone is using remove_hf in onreply_route and if yes on which Kamailio version? I'm using Kamailio v5.2.1 and as soon as I add remove_hf function to onreply_route Kamailio will fail to start with following error messages: ERROR: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7fc1dc044010, 27120); Free fragment not found! ERROR: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7fc1dc044010, 27120) called from core: core/io_wait.c: init_io_wait(524), module: core; Free fragment not found! Thank you for any suggestions!

2 2

Modern SIP Trunking, Route on To: or INVITE Headers?
by JR Richardson 21 May '19

21 May '19

Hey Folks, I could use some feedback to see if my mind is right on this topic.I'm in a discussion with a software Vendor (respectfully unnamed) with terminal software routing on To: header info. It's my contention any modern SIP software should use INVITE header to retrieve DID info and route from there. My reasoning is due to the To: header should contain the original intended DID, Extension, Name, AoR or whatever else the original SIP transaction wanted to contact, but being in a multi-carrier, multi-hop, call forwarding environment, the INVITE header contains the hop-to-hop true intention of where the call should route at any given transaction. So in the case of terminal software the To: header could likely be irrelevant where as the INVITE header is accurate. My most recent response from the Vendor suggest I put a SIP Proxy in front of the terminal software and transform the To: header to whatever I need for this application. Although I can do this, I'm concerned with breaking RFC for CANCEL and BYE transaction sent back from the terminal software that may not be recognized by upstream origination carriers. Plus modifying To: header is widely frowned upon by most folks. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

4 3

$snd(proto) mapping?
by Andrew Chen 21 May '19

21 May '19

Hey guys, Is there a numeric mapping for $snd(proto)? Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 1

How to get started (configuring an interconnection)
by Benoit Panizzon 21 May '19

21 May '19

Dear Kamailio Users I might need a bit help with starting. We are a TSP and at the moment we use a commercial carrier grade voice switch, which is very VERY inflexible and where bugs we find either don't get fixed, or only with a large delay. As everywhere else we embrace opensource and enjoy the possibility to quickly fix bugs ourselves (we have a software development department) we are evaluating Kamailio. Basically, if we have a centralized SIP routing engine, which can record CDRS for Billing and do some Number Translations (lookup on external service or database) for (location based emergency numbers, call forwarding services, ported numbers, call spam blacklisting) we could do way more than our actual $$$ carrier switch is capable of. Kamailio sounds like perfect for this task. First step: Get a machine up and running with Kamailio and Siremis, done, that was easy. Next: Connect his SIP wise via what I would call a 'SIP carrier interconnecton', ip based authenticated trunk between our carrier switch and Kamailio so we can route some number ranges from our carrier switch to Kamailio and then continue to test with subscribers, subscriber trunks and all else we need on Kamailio. I'm quite fluent in Asterisk (our Voicemail and Announcement Services are based on Asterisk) and SIP and have come across many different PBX, but after reading parts of the documentation, and trying myself to understand how Kamailio talks to other SIP endpoints I am a bit at a loss. I would have expected that I would configure our carrier switch as 'remote SIP gateway' or whatever it would be called. But I start fearing, Kamilio works completely differently. So I might need a bit of pointing the right direction to get started. I did try with the 'CarrierRoute Management' or 'Dispatcher' functions, but I only find very little documentation on this. So how do I get started? How do I, for starters, tell Kamailio what the Hostname or IP of my Carrier switch is and how do I set a 'default' call route to this? Kind regards -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Storing an integer value into AVP from REDIS string
by Stephen Bucklin 21 May '19

21 May '19

Hi, Any quick thoughts. I am using a REDIS "GET" to retrieve a JSON obj as a string from REDIS and then the JANSSON get value to extract a key value from the string and pop it into an AVP ($avp(val)) and wish to ensure the value is an integer in the AVP. New to this, be kind :-) Steve

4 6

How to define IP Trunk in kamailio
by Mary Honey 21 May '19

21 May '19

Hello everyone, I install and setup an IMS Network by kamailio-5.2.2 . I have p-cscf, i-cscf and s-cscf in three different systems . my Hss is Fokus. Registration and call between subscribers of network work successfully . now I want to define IP Trunk in my network which can pass external calls through my IMS network. I don't know how to define IP Trunk and changes in which element(pcscf, icscf or scscf) should be done.

2 3

Rewrite contact header
by R, Rajkumar (Raj) 21 May '19

21 May '19

Hello, We are using alias routing from NATHelper module and I've a case where the alias part 'alias=ip~port~transport' needs to be removed from the contact header in 2xx message. There's contact header reference "$ct" pseudo variable but it is read only. Is there any approach available to achieve this as I haven't found anything in the forum archive search so far. thanks, raj

2 2

Unable to CDRs on "Busy Here 486" from remote side and save start and end time on successful call in table
by Shahid Mehmood 21 May '19

21 May '19

Hello, i want to save the status each call into the database. but failed to 1. record CDRs for "Busy Here 486/ service unavailable 503 " from remote side in database. 2. on successful call unable to record total time of call in database. Version of Kamailio Is *version: kamailio 4.4.7 (x86_64/linux) 35d8abflags: 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_RESADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MBpoll method support: poll, epoll_lt, epoll_et, sigio_rt, select.id: 35d8ab* *Also Attached Config File* *Thanks*

1 0

kamailio Early IMS security
by eyas barhouk 20 May '19

20 May '19

hello community Does kamailio support Early IMS security authentication schema to be able to integrate with Huawei HSS ?? and if it's does how to configure it? B.R Eyas

1 0

Plans for next major release - v5.3.0
by Daniel-Constantin Mierla 20 May '19

20 May '19

Hello, a while ago, during the last IRC devel meeting, it was proposed to either do the next major release (5.3.0) before the usual summer holidays or leave it for autumn. Given that time is approaching, we have to decide. If it is going to happen before the summer holidays, probably we should freeze the development in 2-3 weeks, then do 3-4 weeks of testing and release during the first part of July. It would be a shorter development cycle, so I do not expect much needs for testing. Only a few new modules and plenty of work to consolidate and enhance the existing code. Any preference for one of the two options? Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 2

Kamailio usrloc mode 3 using mongodb
by José Seabra 20 May '19

20 May '19

Hello there, I'm testing usrloc module with mongodb and i have a couple of questions to do. What i would like to know/have confirmation is if the fields that are specified in the following link https://kamailio.org/docs/db-tables/kamailio-db-5.2.x.html#gen-db-location-… can be used to create indexes in mongodb? I'm noticing that when a register is updated/deleted or expires kamailio prints the following INFO logs: *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (methods) type id (10), use DB1_STRING as default* *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (instance) type id (10), use DB1_STRING as default* These fields (*methods and **instance*) are stored in mongodb document with a null string, e.g: *{* * "_id" : ObjectId("5cdc775a6472740055289a11"),* * "username" : "x1000",* * "contact" : "sip:x1000@192.168.1.1:5674;transport=UDP",* * "expires" : ISODate("2019-05-15T20:33:26Z"),* * "q" : -1,* * "callid" : "sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61 <sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61>",* * "cseq" : 2,* * "flags" : 0,* * "cflags" : 0,* * "user_agent" : "sipp",* * "received" : "sip:191.30.10.23:8888 <http://191.30.10.23:8888>",* * "path" : "<sip:172.31.2.61:5060;received=sip:191.30.10.23:8888;lr>",* * "socket" : "udp:172.31.2.11:5060 <http://172.31.2.11:5060>",* * "methods" : null,* * "last_modified" : ISODate("2019-05-15T20:32:26Z"),* * "ruid" : "uloc-15-5cdc7756-55-1",* * "instance" : null,* * "reg_id" : 0,* * "server_id" : 21,* * "connection_id" : -1,* * "keepalive" : 0,* * "partition" : 0* *}* Should i be concerned about that log msg? how can i avoid it? Thanks Regards -- Cumprimentos José Seabra

2 5

BYE relays Digest and others in Proxy-Authorization header
by Sergiu Pojoga 19 May '19

19 May '19

Hi ppl, Noticed BYE requests relayed from caller to callee have the *Proxy-Authorization* header including *Digest*, *nonce* and *response*. Is that by SIP definition or am I doing something wrong? My concern is the callee gets to see caller's authentication credentials. Thanks.

4 6

Centos7 Packages
by Matt Lamer 18 May '19

18 May '19

I am trying to install the kam server on centos7. When running the install I get the following: Install 5 Packages (+2 Dependent packages) Total size: 14 M Total download size: 14 M Installed size: 63 M Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. kamailio-debuginfo-5.2.2-7.el7 FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.2.x-rpms/C…: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Anyone else having this issue?

2 1

"If you're struggling with your Tele callers to improve sales? you're not alone.
by Prakash 17 May '19

17 May '19

http://www.doocti.com +919790776655 Doocti Next Generation CTI for Smarter Sales Teams http://www.doocti.com Dear Customer, Greeting from Tevatel. Hope this mail finds you well. We are happy to announce the launch of our new product Doocti - Call center connector for crm What is Doocti? Doocti is a Computer telephony integration platform that can integrate your communication devices with your Helpdesk, CRM, and Other Key Tools. Increase agent productivity, improve customer experience and enable personalized service through deep customer insights at the point of interaction. Features of Doocti Single click Dial On-Screen Customer Profile Build on the Customer Profile Efficient Call Disposition Auto Dial Sticky Agent Feedback from the clients Reduce call time by 10-20 seconds per call Instantly retrieves and screen-pops customer related information Provides a better and more immediate response to the customers Offers a more personalized experience to the caller Dials out automatically and faster with a single mouse click Handles higher call volumes Increases first call resolution Intergrated with Currently we have associated with more than 20 brands. Curious to see what's under the hood? Enjoy a detailed look at the Doocti experience in a demo guided by a member of our team. Get a meeting on the calendar today. mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti Request for a Demo [ mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti ] Communications Simplified Contact Us: +919790776655 | prakash.n(a)tevatel.com No:76, Swamibakthan Street, Nammalwarpet, Chennai - 600012. www.tevatel.com | www.doocti.com http://viewstripo.email/?utm_source=templates&utm_medium=email&utm_campaign… ---------------------------------------------------------------------- This email was sent by prakash.n(a)tevatel.com to sr-users(a)lists.sip-router.org Not interested?Unsubscribe - https://tihk.maillist-manage.com/ua/optout?od=27218d28c96aa859ed0ac1287be0e… Update profile - https://tihk.maillist-manage.com/ua/upc?upd=164d3589027540e5&r=164d35890275… Asterfone technologies pvt ltd | Swamibakthan St, Thiruvalluvar Nagar, Nammalwarpet, Ayanavaram, Chennai, Tamil Nadu 600010 Our Privacy Policy [ ] and Terms of Use. [ ]

2 1

rtpengine sessions on timeout not freeing up RTP ports
by Istvan Mogyorosi 17 May '19

17 May '19

Hello Another rtpengine related question after having successfully implemented a dispatcher configuration. Call flow is ok, everything works well until I tried to increase call volume. Kamailio log showing "proxy replied with error: Ran out of ports" In the beginning both channels are up, then I can see a teardown on the incoming channel loosing the ability to collect DTMF. Using the CLI tool I have statistics showing that none (!) of the calls are "regular terminated", they are on timeout. After experimenting with handling BYE, I ended up could getting a "regular terminated" call by using route[RELAY] .... if (is_method("BYE")) { rtpengine_delete(); } and then I can see some good things! Received command 'delete' from 127.0.0.1:58538 Scheduling deletion of call branch 'as65b95845' (via-branch '') in 5 seconds Replying to 'delete' from 127.0.0.1:58538 (elapsed time 0.000216 sec) Please correct me if I'm doing wrong this way! cheers Istvan

1 0

RFC: Kamailio command line parameters
by Daniel-Constantin Mierla 17 May '19

17 May '19

Hello, a while ago I added support for long format parameter names for Kamailio command line. That's opening the door for more options to be set via command line arguments and I discovered that especially in a containerized environment, it is a trend to start applications using more command line parameters, than relying on config files. The current command line parameters are listed by: kamailio -h Use the master branch for it, because has many more than 5.2.x. Anyhow, the purpose of this message is to see if anyone else considers useful to add other command line parameters, and if yes, which ones. A typical candidate will be a global parameter that you have to change when relocating to/spinning up another Kamailio environment and you need to change the kamailio.cfg. Those that generate the interest of many people, can be easily added now. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Testing the KEMI interpreters for functions with 4 and 5 parameters
by Daniel-Constantin Mierla 17 May '19

17 May '19

Hello, because there were many variants not handled for KEMI functions with 4 and 5 parameters, I made a script to generate the code in order to be sure none is missing. The script was pushed in Kamailio repo at: * https://github.com/kamailio/kamailio/tree/master/misc/tools/kemi You don't have to use it, I listed it for reference, just in case the code needs adjustments in the future. If anyone is using a KEMI interpreter and has functions exported by Kamailio with 4 or 5 parameters, it would be appreciated if you can run some tests with master branch and report the results. All kemi interpreter modules were updated, so it doesn't matter which one you test. If the results are good, then the patches will be backported to branch 5.2, so there will be no case of unhanded functions with these numbers of parameters. The cases with up to 3 parameters were not affected. For 6 params, still only string values are handled. The other variants can be added, but I think they are not needed for the moment, so I tried to keep it small for the moment. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Kamailio World thanks
by Daniel Pocock 16 May '19

16 May '19

Hi Daniel and Kamailio team, Well done on another successful Kamailio World in 2019. As usual, it was a great opportunity to meet people and learn new things. Regards, Daniel

2 1

siputils add_uri_param not available in KEMI python3
by Patrick Murphy 15 May '19

15 May '19

Hello, I am using the following version of Kamailio and using app_python3 with KEMI but I cannot find any exported function of add_uri_param from the siputils module. Any idea how I can perform: KSR.siputils.add_uri_param("name=value") ? version: kamailio 5.2.2 (x86_64/linux) 9260a2 Cheers, Pat.

1 1

Using a single virtual domain in a multi-domain setup
by Rhys Hanrahan 15 May '19

15 May '19

Hi All, I am trying to setup Kamailio to allow me to have multiple different domains (and IPs) treated as one. I am using the domain module for this. As an example I have: * A handset registered to Kamailio by IP address. * A SIP trunk between Asterisk and Kamilio using an FQDN that uses SRV records for redundancy on Asterisk's side. I have added all domains and IPs under the same "domain identifier". It seems the "old" domain module now uid_domain had this capability of a single virtual domain, but is this possible with the more current domain.so module? From what I've said the uid_* modules older modules from the SIP Router project, and should be replaced by more recent Kamailio modules? - https://www.kamailio.org/docs/modules/5.0.x/modules/uid_domain.html VS. - https://kamailio.org/docs/modules/5.1.x/modules/domain.html MariaDB [kamailio]> select * from domain; +----+------------------------------------+------------+---------------------+ | id | domain | did | last_modified | +----+------------------------------------+------------+---------------------+ | 1 | 12.34.56.53 | vocalpoint | 2000-01-01 00:00:01 | | 2 | 23.34.56.54 | vocalpoint | 2000-01-01 00:00:01 | | 3 | sbc.foo | vocalpoint | 2000-01-01 00:00:01 | | 4 | sbc.nsw.foo | vocalpoint | 2000-01-01 00:00:01 | | 5 | sbc.vic.foo | vocalpoint | 2000-01-01 00:00:01 | | 6 | sbc.foo2 | vocalpoint | 2000-01-01 00:00:01 | | 7 | sbc.nsw.foo2 | vocalpoint | 2000-01-01 00:00:01 | | 8 | sbc.vic.foo2 | vocalpoint | 2000-01-01 00:00:01 | +----+------------------------------------+------------+---------------------+ 8 rows in set (0.000 sec) I managed to get registrations working by hardcoding a static realm in the config, but when when usrloc does a lookup on a handset, Kamailio can't find user(a)sbc.nsw.foo and Kamailio returns 404. It looks like this is because in the locations table it is listed with a domain of 12.34.56.53 (because the handset is registered by IP). How should this work normally? Or is it even possible? Thanks, Rhys.

2 4

Sip proxy for Asterisk with RFC3966 and 100Rel
by paolo.visnoviz＠vipcomputers.it 15 May '19

15 May '19

Dear Sirs, a telco provider give us a trunk that require 100rel and TEL RFC 3966. Usually we use Asterisk. Now Asterisk 16 with PJSIP support 100Rel, but not RFC3966, and they don't actually works to implement it. Asterisk chan_sip, instead, support RFC3966, but not 100Rel and is not actively developed on by Digium or Sangoma. So I'm stuck. Now, do you think it was possible to use Kamailio to act like a proxy sip but implementing RFC3966 for incoming and outgoing calls and RFC3966 and 100Rel for outgoing calls? And it is possible to connect all to an Asterisk server? Thank you in advance Best regards. Paolo Visnoviz

3 9

Possible memory leak in siptrace module in kamailio 5.1/5.2
by davy van de moere 15 May '19

15 May '19

Dear, I'm using siptrace within a python handler in the KEMI framework. KSR.siptrace.sip_trace_dst("sip:<myhomerip>:9060") I notice an ever increasing usage of memory, until the system runs out of memory. (definition of a memory leak :) ). Looking at the memory information kamailio is giving me I notice this: May 14 05:49:48 server kamailio[36452]: NOTICE: PYT {INVITE} {1769595029-1513210001-1955500877} {1} : qm_sums: count= 79286 size= 5812048 bytes from siptrace: siptrace.c: ki_sip_trace_dst_cid(729) May 14 05:51:17 server kamailio[36452]: NOTICE: PYT {REGISTER} { 4_1419955802(a)192.168.0.153} {2582} : qm_sums: count= 79335 size= 5814840 bytes from siptrace: siptrace.c: ki_sip_trace_dst_cid(729) I notice this on kamailio 5.1.8 (from a debian repo), and on kamailio 5.2.2 (from source). I can reproduce the problem very easily, and I can apply patches in the source to try out things. Could I be wrongly using siptrace? Can I give you more debugging info? Kind regards, Davy

3 4

define a DBURL with SLQOPS fails
by David Villasmil 14 May '19

14 May '19

Hello guys, So, i'm defining: DBURL "mysql://user:password@dbhost/dbname" and later on... modparam("sqlops","sqlcon","cb=>"DBURL) and this fails miserably.. What do do on this case? Thanks all! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 12

Npdi question
by Duarte Rocha 14 May '19

14 May '19

Greetings, Regarding portability issues, is there a difference between "npdi" and "npdi=yes" ? Are there any more possible values besides "yes" and no value? Best Regards, Duarte Rocha

1 0

sdp_remove_codecs_by_id does not remove 101
by Juha Heinanen 14 May '19

14 May '19

I tried to use sdp_remove_codecs_by_id("101") to remove "codec" 101 (dtmf) from sdp, but nothing happened. It is still there: m=audio 31128 UDP/TLS/RTP/SAVPF 101 96. c=IN IP4 192.168.43.88 a=label:1. a=rtcp-rsize. a=ssrc:2880178656 cname:sip:test@test.tutpro.com. a=rtpmap:101 telephone-event/8000. a=rtpmap:96 opus/48000/2. a=fmtp:101 0-15. Is that by design or a bug? If not a bug, is there some other means to remove 101? -- Juha

2 2

sip trunk with kamailio
by arish haque 14 May '19

14 May '19

Hi, I am trying the SIP trunk from kamailio with following configurations - cfg_get.pstn.gw_ip="10.0.x.y route[PSTN] { #!ifdef WITH_PSTN # check if PSTN GW IP is defined if (strempty($sel(cfg_get.pstn.gw_ip))) { xlog("SCRIPT: PSTN rotuing enabled but pstn.gw_ip not defined\n"); return; } if(!($rU=~"^(\+|00)918884978235")) return; # only local users allowed to call if(from_uri!=myself) { sl_send_reply("403", "Not Allowed"); exit; } $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip); route(RELAY); exit; #!endif return; } I am able to see kamailio sending INVITE to SIP Provider but no response back. Any other, configuration is required which I'm missing. I have attached the tcpdump snapshot of the above scenario. Thanks, Arish

2 1

Theoritical Anycast Setup
by Daniel Oakes 14 May '19

14 May '19

Hi there, Long time user, 1st time poster - apologies if someone has posted this previously. We have a product from a vendor that utilizes Kamailio as a SIP router - but we're wanting to extend it a little bit by the use of anycast (we're a small ISP). Basically the scenario is that we want to utilize Quagga via BGP to anycast an address, which addresses a glaring load balancing issue with have with people who use only A records. Problem is anycast doesn't work so well in this scenario, just by adding the Anycast as a listen address on the proxy. What we'd want to do is rewrite the SIP so that all responses come back out saying to use the 'real ip'. So I have two variables - say REAL_IP_ADDRESS and ANYCAST_IP_ADDRESS - request will come in via ANYCAST, but I want all responses from then on to be via REAL_IP_ADDRESS. We have six Kamailio boxes in various geographical locations, so the idea is they hit one based on closest, and we rewrite it so they end up with the real ip address to talk to. Anyone done something similar? I'm guessing possibly, but I can't find anything specific enough for me to use. Help appreciated! Regards, Daniel

2 1

No audio after IP address change
by Chris Scheid 11 May '19

11 May '19

Hi, we are using rtpengine with Kamailio using DTLS-SRTP and SRTP making audio calls from two Android devices. Regular audio calls work fine but we have issues with the following scenario: 1. Device 1 (72.66.83.8, on WiFI) calls Device 2 (174.204.14.29). SIP server has IP 209.182.216.71. 2. Device 2 switches networks from WiFI to 3G (new IP: 97.47.70.223). Re-invite flow completes. 3. Any audio from Device 2 cannot be heard on Device 1. But audio from the Device1 can be heard on the Device 2. In the rtpengine stats I see that there were some packets sent from the SIP server to the Device 1 after network change: [1557513316.000308] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: ------ Media #1 (audio over UDP/TLS/RTP/SAVP) using iLBC/8000 [1557513316.000318] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20052 <> 97.47.70.223:4667 , SSRC 77c38349, 55 p, 3410 b, 0 e, 32 ts [1557513316.000325] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20053 <> 97.47.70.223:4640 (RTCP), SSRC 77c38349, 12 p, 1120 b, However, in my UDP trace, I don't see any communication between the SIP server and the Device 1 after network change (IP 97.47.70.223). This seems to be the reason why we don't get audio on Device 1. I'm looking for direction on how to troubleshoot this issue. I'm not so familiar with rtpengine. Any assistance greatly appreciated. Thanks! RTP Engine Config: [rtpengine] #####table = 0 listen-ng = 127.0.0.1:5050 timeout = 60 silent-timeout = 3600 tos = 184 port-min = 20000 port-max = 60000 interface = 209.182.216.71 log-level = 7 log-stderr = false log-facility = local0 START CALL --------------------------------------------------------------------------------------------------------------------- [1557513231.973294] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Received command 'offer' from 127.0.0.1:45431 [1557513231.973357] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Dump for 'offer' from 127.0.0.1:45431: { "sdp": "v=0 o=- 3766502030 3766502030 IN IP4 192.168.1.200 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 5095 UDP/TLS/RTP/SAVP 104 98 97 99 3 0 8 9 96 c=IN IP4 192.168.1.200 b=TIAS:64000 a=rtcp:5096 IN IP4 192.168.1.200 a=sendrecv a=rtpmap:104 iLBC/8000 a=fmtp:104 mode=30 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:99 speex/32000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=ssrc:2009301833 cname:32ababda5d2c847b a=setup:actpass a=fingerprint:SHA-256 4F:69:B6:89:51:98:6C:A4:63:CF:F7:CD:22:D2:BE:FD:6E:3F:F4:2A:8B:39:AD:E4:C0:8D:AE:BD:A3:70:12:49 ", "ICE": "remove", "DTLS": "passive", "replace": [ "origin", "session-connection" ], "transport-protocol": "UDP/TLS/RTP/SAVP", "call-id": "05c7dcfe-06f3-4630-9 799-0557b76cc340", "received-from": [ "IP4", "72.66.83.8" ], "from-tag": "2684eff8-3602-41ed-aca2-9f7938362462", "command": "offer" } [1557513231.973444] NOTICE: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating new call [1557513231.973496] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Default sink codec is speex/16000 [1557513231.973503] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for iLBC/8000 [1557513231.973508] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for speex/16000 [1557513231.973512] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/16000 [1557513231.973515] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for speex/8000 [1557513231.973519] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/8000 [1557513231.973523] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for speex/32000 [1557513231.973526] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/32000 [1557513231.973530] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for GSM/8000 [1557513231.973534] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec GSM/8000 [1557513231.973538] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for PCMU/8000 [1557513231.973542] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec PCMU/8000 [1557513231.973545] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for PCMA/8000 [1557513231.973549] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec PCMA/8000 [1557513231.973545] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for PCMA/8000 [1557513231.973549] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec PCMA/8000 [1557513231.973552] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for G722/8000 [1557513231.973556] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec G722/8000 [1557513231.973560] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for telephone-event/8000 [1557513231.974291] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 192.168.1.200:5095 [1557513231.974561] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 192.168.1.200:5096 [1557513231.974874] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: offer time = 0.001488 sec [1557513231.974882] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Replying to 'offer' from 127.0.0.1:45431 [1557513231.974900] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Response dump for 'offer' to 127.0.0.1:45431: { "sdp": "v=0 o=- 3766502030 3766502030 IN IP4 209.182.216.71 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 20032 UDP/TLS/RTP/SAVP 104 98 97 99 3 0 8 9 96 c=IN IP4 209.182.216.71 b=TIAS:64000 a=ssrc:2009301833 cname:32ababda5d2c847b a=rtpmap:104 iLBC/8000 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:99 speex/32000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:104 mode=30 a=fmtp:96 0-16 a=sendrecv a=rtcp:20033 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:G9MvyRPBAVFsrMypvr1EAunZiX/vc04sXEq4mXvl a=setup:actpass a=fingerprint:sha-1 EE:4A:ED:7D:5A:94:A2:FF:F2:09:64:07:41:FC:15:80:D3:F9:C0:B4 ", "result": "ok" } [1557513232.077386] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: Processing incoming DTLS packet [1557513232.078219] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: Sending DTLS packet [1557513232.189220] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: Processing incoming DTLS packet [1557513232.189868] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: DTLS handshake successful [1557513232.189899] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: DTLS-SRTP successfully negotiated [1557513232.189905] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: SRTP keys, incoming: [1557513232.189914] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: --- AES_CM_128_HMAC_SHA1_80 key q67B3h3GP/dhbQeKsgBnvA== salt EcoNJ6Hqj0lRtvZ8Z+Y= [1557513232.189919] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: SRTP keys, outgoing: [1557513232.189923] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: --- AES_CM_128_HMAC_SHA1_80 key 0nTo2gy4XJ2GXlroyyH6nA== salt fbIfUIa4IPiYLvn5CkI= [1557513232.189929] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: Sending DTLS packet confirmed [1557513243.648460] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SRTCP output wanted, but no crypto suite was negotiated [1557513243.648486] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 201 [1557513243.648496] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about 9fda818d: FL 205 TL 6486816 HSR 613804890 J 3100337071 LSR 1419186059 DLSR 531075031 [1557513243.648505] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513243.649142] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 201 [1557513243.649158] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about d4b1278d: FL 23 TL 2271802 HSR 278642673 J 2408385537 LSR 3 653820601 DLSR 1701759944 [1557513243.649169] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513243.777813] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Received command 'answer' from 127.0.0.1:47861 [1557513243.777860] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Dump for 'answer' from 127.0.0.1:47861: { "sdp": "v=0 o=- 3766502031 3766502032 IN IP4 100.81.62.76 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 5079 UDP/TLS/RTP/SAVP 104 96 c=IN IP4 100.81.62.76 b=TIAS:64000 a=rtcp:5080 IN IP4 100.81.62.76 a=sendrecv a=rtpmap:104 iLBC/8000 a=fmtp:104 mode=30 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=ssrc:2006816651 cname:1c0965113e9b1046 a=setup:active a=fingerprint:SHA-256 AD:2D:0F:A6:11:DD:75:CC:3C:50:3A:9A:F0:29:20:8D:95:BC:3E:2A:A0:34:F6:67:14:A7:87:EB:8D:66:77:B1 ", "ICE": "remove", "replace": [ "origin", "session-connection" ], "transport-protocol": "UDP/TLS/RTP/SAVP", "call-id": "05c7dcfe-06f3-4630-9799-0557b76cc340", "received-from": [ "IP4", "174.204.14.29" ], "from-tag": "2684eff8-3602-41ed-aca2-9f7938362462", "to-tag": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00", "command": "a nswer" } [1557513243.777998] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for iLBC/8000 [1557513243.778010] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Creating codec handler for telephone-event/8000 [1557513243.778088] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 100.81.62.76:5079 [1557513243.778117] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: DTLS: Peer certificate accepted [1557513243.778123] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 100.81.62.76:5080 [1557513243.778166] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: answer time = 0.000267 sec [1557513243.778175] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Replying to 'answer' from 127.0.0.1:47861 [1557513243.778187] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Response dump for 'answer' to 127.0.0.1:47861: { "sdp": "v=0 o=- 3766502031 3766502032 IN IP4 209.182.216.71 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 20052 UDP/TLS/RTP/SAVP 104 96 c=IN IP4 209.182.216.71 b=TIAS:64000 a=ssrc:2006816651 cname:1c0965113e9b1046 a=rtpmap:104 iLBC/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:104 mode=30 a=fmtp:96 0-16 a=sendrecv a=rtcp:20053 a=setup:passive a=fingerprint:sha-1 EE:4A:ED:7D:5A:94:A2:FF:F2:09:64:07:41:FC:15:80:D3:F9:C0:B4 ", "result": "ok" } [1557513243.864786] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Processing incoming DTLS packet [1557513243.865568] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Sending DTLS packet [1557513243.912858] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Processing incoming DTLS packet [1557513243.913111] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: DTLS: Peer certificate accepted [1557513243.913627] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: DTLS handshake successful [1557513243.913668] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: DTLS-SRTP successfully negotiated [1557513243.913675] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: SRTP keys, incoming: [1557513243.913682] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: --- AES_CM_128_HMAC_SHA1_80 key +C2ck1NPvsfHYoKflimqaA== salt xM4aFoL60/ePpmQJsT8= [1557513243.913686] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: SRTP keys, outgoing: [1557513243.913689] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: --- AES_CM_128_HMAC_SHA1_80 key VvTNUyescFh+vNj16/fePw== salt m3EuTJjAesJHaSXfqKU= [1557513243.913694] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Sending DTLS packet [1557513244.475362] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 200 [1557513244.475405] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SR from 779d978b: RTP TS 3873048209 PC 2516599107 OC 673505029 NTP TS 1161195675/4 008032614=1161195675.933193 [1557513244.475412] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about bb94938e: FL 243 TL 11665253 HSR 1302964504 J 2830082235 LS R 1964993324 DLSR 1625750139 [1557513244.475422] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513244.492749] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SRTCP output wanted, but no crypto suite was negotiated [1557513244.492775] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513244.492791] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 2981125880 PC 4052113656 OC 2653921327 NTP TS 4076801750/ 1160081551=4076801750.270103 [1557513244.492797] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 3813d27e: FL 75 TL 11393233 HSR 1719559869 J 944495881 LSR 790240102 DLSR 447292567 [1557513244.492804] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513247.217290] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20032]: Confirmed peer address as 174.204.14.29:10523 [1557513248.958592] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 200 [1557513248.958638] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SR from 779d978b: RTP TS 3148803183 PC 137367242 OC 1506652935 NTP TS 3606800652/1 621372750=3606800652.377505 [1557513248.958647] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about 468fa6ae: FL 57 TL 15596558 HSR 3764947872 J 3769875796 LSR 4259175195 DLSR 3903464346 [1557513248.958657] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513248.958667] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Confirmed peer address as 174.204.14.29:10496 i[1557513249.259063] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513249.259108] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 3424021083 PC 3823893658 OC 584056375 NTP TS 3244065141/3 391763074=3244065141.789706 [1557513249.259117] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about e7313af6: FL 98 TL 10263186 HSR 2762600672 J 838876573 LSR 3367219470 DLSR 50549698 [1557513249.259131] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513249.259142] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Confirmed peer address as 72.66.83.8:5096 t[1557513249.562239] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Confirmed peer address as 72.66.83.8:5095 SWITCH NETWORKS [1557513253.843937] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 200 [1557513253.844019] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SR from 779d978b: RTP TS 1364757765 PC 1063357287 OC 2194907961 NTP TS 2472417766/ 1884000851=2472417766.438653 [1557513253.844029] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about 77b8933: FL 163 TL 2305413 HSR 2377964402 J 118139039 LSR 2 460485565 DLSR 3416921415 [1557513253.844040] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513254.590466] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513254.590508] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 2527484095 PC 1878948628 OC 3882176963 NTP TS 213338522/6 38146641=213338522.148580 [1557513254.590517] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about b7800717: FL 93 TL 16503124 HSR 338254320 J 1043490285 LSR 801212789 DLSR 2849120558 [1557513254.590530] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513258.679347] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SRTCP output wanted, but no crypto suite was negotiated [1557513258.679385] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 200 [1557513258.679411] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SR from 779d978b: RTP TS 1747525463 PC 239751946 OC 2859161225 NTP TS 3835334254/3 577221347=3835334254.832887 [1557513258.679418] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about e03bd142: FL 40 TL 11515285 HSR 3870936491 J 4150119236 LSR 2903910302 DLSR 700479064 [1557513258.679427] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513259.940740] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SRTCP output wanted, but no crypto suite was negotiated [1557513259.940770] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513259.940793] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 2745657868 PC 580822102 OC 4072320279 NTP TS 252333929/20 93935903=252333929.487532 [1557513259.940801] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 476ec510: FL 61 TL 5399464 HSR 3682903462 J 1600791504 LSR 497094189 DLSR 826539320 [1557513259.940814] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513263.532695] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 200 [1557513263.532722] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: SR from 779d978b: RTP TS 301750475 PC 2434799802 OC 863475295 NTP TS 3625503376/30 14095725=3625503376.701774 [1557513263.532729] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about 228989b7: FL 148 TL 10638176 HSR 2137788972 J 2678688015 LS R 2118438561 DLSR 1024262683 [1557513263.532738] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513264.051305] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513264.051352] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 1190725747 PC 3072491822 OC 537479863 NTP TS 817717026/42 82321058=817717026.997056 [1557513264.051359] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 920db8ff: FL 98 TL 6598240 HSR 2045142812 J 3171281598 LSR 2224002690 DLSR 2514604823 [1557513264.051369] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513264.058891] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 201 [1557513264.058920] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 5c8f2711: FL 24 TL 1700303 HSR 2993289918 J 618517078 LSR 1 835926259 DLSR 3106454771 [1557513264.058891] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 201 [1557513264.058920] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 5c8f2711: FL 24 TL 1700303 HSR 2993289918 J 618517078 LSR 1 835926259 DLSR 3106454771 [1557513264.058934] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513264.266612] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Received command 'offer' from 127.0.0.1:60736 [1557513264.266654] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Dump for 'offer' from 127.0.0.1:60736: { "sdp": "v=0 o=- 3766502030 3766502031 IN IP4 192.168.1.200 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 5097 UDP/TLS/RTP/SAVP 104 98 97 99 3 0 8 9 96 c=IN IP4 10.255.81.66 b=TIAS:64000 a=rtcp:5098 IN IP4 10.255.81.66 a=sendrecv a=rtpmap:104 iLBC/8000 a=fmtp:104 mode=30 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:99 speex/32000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=ssrc:2009301833 cname:32ababda5d2c847b a=setup:actpass a=fingerprint:SHA-256 4F:69:B6:89:51:98:6C:A4:63:CF:F7:CD:22:D2:BE:FD:6E:3F:F4:2A:8B:39:AD:E4:C0:8D:AE:BD:A3:70:12:49 ", "ICE": "remove", "DTLS": "passive", "replace": [ "origin", "session-connection" ], "transport-protocol": "UDP/TLS/RTP/SAVP", "call-id": "05c7dcfe-06f3-4630-9 799-0557b76cc340", "received-from": [ "IP4", "97.47.70.223" ], "from-tag": "2684eff8-3602-41ed-aca2-9f7938362462", "to-tag": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d 00", "command": "offer" } [1557513264.266814] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Default sink codec is speex/16000 [1557513264.266826] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/16000 [1557513264.266831] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/8000 [1557513264.266835] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec speex/32000 [1557513264.266838] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec GSM/8000 [1557513264.266842] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec PCMU/8000 [1557513264.266846] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec PCMA/8000 [1557513264.266850] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sink supports codec G722/8000 [1557513264.267614] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sending DTLS packet [1557513264.268089] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sending DTLS packet [1557513264.268146] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sending DTLS packet [1557513264.268220] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 10.255.81.66:5097 [1557513264.268627] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: set FILLED flag for stream 10.255.81.66:5098 [1557513264.269072] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: offer time = 0.002384 sec [1557513264.269084] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Replying to 'offer' from 127.0.0.1:60736 [1557513264.269098] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Response dump for 'offer' to 127.0.0.1:60736: { "sdp": "v=0 o=- 3766502030 3766502031 IN IP4 209.182.216.71 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 20064 UDP/TLS/RTP/SAVP 104 98 97 99 3 0 8 9 96 c=IN IP4 209.182.216.71 b=TIAS:64000 a=ssrc:2009301833 cname:32ababda5d2c847b a=rtpmap:104 iLBC/8000 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:99 speex/32000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:104 mode=30 a=fmtp:96 0-16 a=sendrecv a=rtcp:20065 a=setup:actpass a=fingerprint:sha-1 EE:4A:ED:7D:5A:94:A2:FF:F2:09:64:07:41:FC:15:80:D3:F9:C0:B4 ", "result": "ok" } [1557513264.355109] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SRTCP output wanted, but no crypto suite was negotiated [1557513264.355140] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 201 [1557513264.355150] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 511a36de: FL 144 TL 3729734 HSR 2556650506 J 4034165594 LSR 900570716 DLSR 3118967760 [1557513264.355166] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513264.355186] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 201 [1557513264.355193] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about aea81208: FL 180 TL 10378624 HSR 1586287909 J 2246375086 LS R 3231023203 DLSR 4073439206 [1557513264.355201] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513264.355210] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Switching local interface to 209.182.216.71:20033 [1557513264.358206] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: Calling handler for RTCP packet type 201 [1557513264.358229] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: RR from 779d978b about b59d47bc: FL 242 TL 13886413 HSR 3966401064 J 2679493971 LS R 3040876731 DLSR 2668321392 [1557513264.358239] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20033]: No payload type known for RTCP RR, discarding [1557513264.358262] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20064]: SRTP output wanted, but no crypto suite was negotiated [1557513264.425636] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Received command 'answer' from 127.0.0.1:45431 [1557513264.425679] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Dump for 'answer' from 127.0.0.1:45431: { "sdp": "v=0 o=- 3766502031 3766502033 IN IP4 100.81.62.76 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 5079 UDP/TLS/RTP/SAVP 104 96 c=IN IP4 100.81.62.76 b=TIAS:64000 a=rtcp:5080 IN IP4 100.81.62.76 a=sendrecv a=rtpmap:104 iLBC/8000 a=rtpmap:104 iLBC/8000 a=fmtp:104 mode=30 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=ssrc:2006816651 cname:1c0965113e9b1046 a=setup:active a=fingerprint:SHA-256 AD:2D:0F:A6:11:DD:75:CC:3C:50:3A:9A:F0:29:20:8D:95:BC:3E:2A:A0:34:F6:67:14:A7:87:EB:8D:66:77:B1 ", "ICE": "remove", "replace": [ "origin", "session-connection" ], "transport-protocol": "UDP/TLS/RTP/SAVP", "call-id": "05c7dcfe-06f3-4630-9799-0557b76cc340", "received-from": [ "IP4", "174.204.14.29" ], "from-tag": "2684eff8-3602-41ed-aca2-9f7938362462", "to-tag": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00", "command": "a nswer" } [1557513264.426806] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: answer time = 0.001099 sec [1557513264.426820] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Replying to 'answer' from 127.0.0.1:45431 [1557513264.426831] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Response dump for 'answer' to 127.0.0.1:45431: { "sdp": "v=0 o=- 3766502031 3766502033 IN IP4 209.182.216.71 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 20052 UDP/TLS/RTP/SAVP 104 96 c=IN IP4 209.182.216.71 b=TIAS:64000 a=ssrc:2006816651 cname:1c0965113e9b1046 a=rtpmap:104 iLBC/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:104 mode=30 a=fmtp:96 0-16 a=sendrecv a=rtcp:20053 a=setup:passive a=fingerprint:sha-1 EE:4A:ED:7D:5A:94:A2:FF:F2:09:64:07:41:FC:15:80:D3:F9:C0:B4 ", "result": "ok" } [1557513264.700442] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Processing incoming DTLS packet [1557513264.701235] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Sending DTLS packet [1557513264.892393] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Processing incoming DTLS packet [1557513264.893153] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: DTLS handshake successful [1557513264.893193] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: DTLS-SRTP successfully negotiated [1557513264.893202] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: SRTP keys, incoming: [1557513264.893211] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: --- AES_CM_128_HMAC_SHA1_80 key dob4sywpHJJ8qNgFzemlzQ== salt y7/1RgzeAtPkG+GfMLI= [1557513264.893216] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: SRTP keys, outgoing: [1557513264.893222] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: --- AES_CM_128_HMAC_SHA1_80 key ontM1nC56XojOkmzb8520g== salt Hom6TrHovUBUaF1g6Iw= [1557513264.893228] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Sending DTLS packet [1557513269.223923] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20052]: Confirmed peer address as 97.47.70.223:4667 [1557513269.337491] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513269.337543] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 402044265 PC 1976845075 OC 2962195809 NTP TS 1329245270/2 977782988=1329245270.693319 [1557513269.337552] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about c1e9445b: FL 196 TL 15740765 HSR 1231260891 J 3373413243 LS R 2989889476 DLSR 1721296716 [1557513269.337562] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513269.337571] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Confirmed peer address as 97.47.70.223:4640 [1557513269.355712] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 200 [1557513269.355744] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SR from 779d978b: RTP TS 46888194 PC 1178262997 OC 1943197043 NTP TS 748304878/374 [1557513269.355749] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 4d78530a: FL 59 TL 15587360 HSR 641166863 J 455122196 LSR 2 981586141 DLSR 1538485973 [1557513269.355755] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513269.355763] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Confirmed peer address as 174.204.14.29:10496 [1557513269.355768] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Switching local interface to 209.182.216.71:20065 [1557513269.376119] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 201 [1557513269.376149] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 60b442ee: FL 185 TL 2381849 HSR 1868471658 J 3454737373 LSR 3540730944 DLSR 753951698 [1557513269.376164] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513269.967467] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20064]: Confirmed peer address as 174.204.14.29:10523 s[1557513274.064040] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SRTCP output wanted, but no crypto suite was negotiated [1557513274.064063] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513274.064084] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 2043506601 PC 348629863 OC 1509649344 NTP TS 4002640369/1 330623176=4002640369.309810 [1557513274.064090] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 1b7ce7ec: FL 17 TL 10773844 HSR 2006802227 J 3496394774 LSR 1855863287 DLSR 207902258 [1557513274.064105] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SSRC hash table exceeded size limit (trying to add 1b7ce7ec) - deleting SSRC 9fda8 18d [1557513274.064114] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding w[1557513274.337285] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 200 [1557513274.337341] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SR from 779d978b: RTP TS 3588538011 PC 4113250253 OC 3762757735 NTP TS 3675530209/ 2088363704=3675530209.486235 [1557513274.337352] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 1904c0d9: FL 190 TL 1277330 HSR 3700606795 J 2076634040 LSR 2826708796 DLSR 3084916091 [1557513274.337367] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SSRC hash table exceeded size limit (trying to add 1904c0d9) - deleting SSRC d4b12 78d [1557513274.337378] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding itch complete[1557513278.796840] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513278.796890] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 1179546147 PC 253436483 OC 401514196 NTP TS 591585900/307 4094117=591585900.715743 [1557513278.796900] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about f25fab39: FL 196 TL 1861219 HSR 1237831119 J 2726348211 LSR 3841137799 DLSR 843496811 [1557513278.796913] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SSRC hash table exceeded size limit (trying to add f25fab39) - deleting SSRC bb949 38e [1557513278.796921] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513279.310594] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SRTCP output wanted, but no crypto suite was negotiated [1557513279.310626] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 200 [1557513279.310646] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SR from 779d978b: RTP TS 624630617 PC 1167418798 OC 2870042862 NTP TS 2807429790/9 64181525=2807429790.224491 [1557513279.310652] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about bb84140b: FL 193 TL 5406510 HSR 1470777656 J 207786249 LSR 3684806947 DLSR 307709608 [1557513279.310669] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SSRC hash table exceeded size limit (trying to add bb84140b) - deleting SSRC 3813d 27e [1557513279.310679] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513279.678189] ERR: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20064]: SRTP output wanted, but no crypto suite was negotiated [1557513283.537471] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513283.537514] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 1085702245 PC 129819128 OC 1350967259 NTP TS 967851883/21 63508869=967851883.503731 [1557513283.537521] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 169e1507: FL 46 TL 3777017 HSR 3092777669 J 3495001522 LSR 3630093505 DLSR 120738828 [1557513283.537537] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SSRC hash table exceeded size limit (trying to add 169e1507) - deleting SSRC 468fa 6ae [1557513283.537546] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513284.300047] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 200 [1557513284.300094] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SR from 779d978b: RTP TS 3660274611 PC 3339904092 OC 976632286 NTP TS 3250964209/2 354170892=3250964209.548123 [1557513284.300103] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about a9cab1ac: FL 9 TL 7152183 HSR 1071025251 J 612018816 LSR 12 43749409 DLSR 721434160 [1557513284.300119] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SSRC hash table exceeded size limit (trying to add a9cab1ac) - deleting SSRC e7313 af6 [1557513284.300130] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding bye [1557513286.941239] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Received command 'delete' from 127.0.0.1:49479 [1557513286.941278] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Dump for 'delete' from 127.0.0.1:49479: { "call-id": "05c7dcfe-06f3-4630-9799-0557b76cc340", "received-from": [ "IP4", "174.204.14.29" ], "from-tag": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00", "command": "delete" } [1557513286.941434] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Scheduling deletion of call branch 'c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00' (via-branch '') in 3 0 seconds [1557513286.941444] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: delete time = 0.000152 sec [1557513286.941474] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Replying to 'delete' from 127.0.0.1:49479 [1557513286.941618] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Response dump for 'delete' to 127.0.0.1:49479: { "created": 1557513231, "created_us": 973175, "last signal": 1557513264, "SSRC": { "3046983612": { }, "2450372863": { }, "1622426350": { }, "2930250248": { }, "419741913": { }, "579439031": { }, "136 0672478": { }, "3145995275": { }, "125536563": { }, "2848633260": { }, "3762016578": { }, "379458823": { }, "1552885521": { }, "3078620951": { }, "12997 31210": { }, "461170668": { }, "2009301833": { }, "3253290075": { }, "1198441744": { }, "4066356025": { }, "2006816651": { } }, "tags": { "c71ac9de-9bf5- 4f39-9fda-6bd3aaf97d00": { "tag": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00", "created": 1557513231, "in dialogue with": "2684eff8-3602-41ed-aca2-9f7938362462", "me dias": [ { "index": 1, "type": "audio", "protocol": "UDP/TLS/RTP/SAVP", "streams": [ { "local port": 20064, "endpoint": { "family": "IPv4", "address": "174.204. 14.29", "port": 10523 }, "advertised endpoint": { "family": "IPv4", "address": "100.81.62.76", "port": 5079 }, "crypto suite": "AES_CM_128_HMAC_SHA1_80", "last packet": 1557513286, "flags": [ "RTP", "filled", "confirmed", "kernelized", "no kernel support", "DTLS fingerprint verified" ], "SSRC": 2006816651, "stats": { " packets": 595, "bytes": 40090, "errors": 0 } }, { "local port": 20065, "endpoint": { "family": "IPv4", "address": "174.204.14.29", "port": 10496 }, "advertised endpoint": { "family": "IPv4", "address": "100.81.62.76", "port": 5080 }, "crypto suite": "AES_CM_128_HMAC_SHA1_80", "last packet": 1557513284, "flags": [ "RTCP ", "filled", "confirmed", "kernelized", "no kernel support" ], "SSRC": 2006816651, "stats": { "packets": 15, "bytes": 1306, "errors": 0 } } ], "flags": [ "initi alized", "send", "recv", "DTLS-SRTP", "DTLS role passive", "ICE controlling" ] } ] }, "2684eff8-3602-41ed-aca2-9f7938362462": { "tag": "2684eff8-3602-41ed-aca2- 9f7938362462", "created": 1557513231, "in dialogue with": "c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00", "medias": [ { "index": 1, "type": "audio", "protocol": "UDP/TL S/RTP/SAVP", "streams": [ { "local port": 20052, "endpoint": { "family": "IPv4", "address": "97.47.70.223", "port": 4667 }, "advertised endpoint": { "family": " IPv4", "address": "10.255.81.66", "port": 5097 }, "crypto suite": "AES_CM_128_HMAC_SHA1_80", "last packet": 1557513284, "flags": [ "RTP", "filled", "confirmed", "kernelized", "no kernel support", "DTLS fingerprint verified" ], "SSRC": 2009301833, "stats": { "packets": 55, "bytes": 3410, "errors": 0 } }, { "local port": 20053, "endpoint": { "family": "IPv4", "address": "97.47.70.223", "port": 4640 }, "advertised endpoint": { "family": "IPv4", "address": "10.255.81.66", "port": 5098 }, "last packet": 1557513283, "flags": [ "RTCP", "filled", "confirmed", "kernelized", "no kernel support" ], "SSRC": 2009301833, "stats": { "packets": 10, "bytes": 936, "errors": 0 } } ], "flags": [ "initialized", "send", "recv", "DTLS-SRTP", "DTLS role passive" ] } ] } }, "totals": { "RTP": { "packets": 650, "bytes": 43500, "errors": 0 }, "RTCP": { "packets": 25, "bytes": 2242, "errors": 0 } }, "result": "ok" } [1557513287.087244] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513287.087244] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 200 [1557513287.087282] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SR from 77c38349: RTP TS 1725021880 PC 1560319321 OC 3364521432 NTP TS 1121433750/3398500622=1121433750.791275 [1557513287.087290] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 9ba3be3b: FL 18 TL 4080170 HSR 3714308681 J 2085763389 LSR 1453166610 DLSR 3867570679 [1557513287.087303] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SSRC hash table exceeded size limit (trying to add 9ba3be3b) - deleting SSRC 77b8933 [1557513287.087311] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513287.087324] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: Calling handler for RTCP packet type 201 [1557513287.087328] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: RR from 77c38349 about 477b6daa: FL 136 TL 7495912 HSR 3723043622 J 76729872 LSR 791112841 DLSR 2264873880 [1557513287.087332] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: SSRC hash table exceeded size limit (trying to add 477b6daa) - deleting SSRC b7800717 [1557513287.087338] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20053]: No payload type known for RTCP RR, discarding [1557513287.165301] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 200 [1557513287.165344] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SR from 779d978b: RTP TS 4203649664 PC 1900914033 OC 1842228915 NTP TS 2577169143/1958584749=2577169143.456018 [1557513287.165355] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 643dc91f: FL 113 TL 8548413 HSR 913668020 J 2977588542 LSR 2353716277 DLSR 1468396047 [1557513287.165370] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SSRC hash table exceeded size limit (trying to add 643dc91f) - deleting SSRC e03bd142 [1557513287.165382] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513287.165396] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: Calling handler for RTCP packet type 201 [1557513287.165403] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: RR from 779d978b about 7d2457ab: FL 45 TL 2024736 HSR 174032952 J 3137856066 LSR 2564654212 DLSR 844577710 [1557513287.165410] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: SSRC hash table exceeded size limit (trying to add 7d2457ab) - deleting SSRC 476ec510 [1557513287.165418] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340 port 20065]: No payload type known for RTCP RR, discarding [1557513316.000248] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Call branch 'c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00' (via-branch '') deleted, no more branches remaining [1557513316.000290] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Final packet stats: [1557513316.000297] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --- Tag '2684eff8-3602-41ed-aca2-9f7938362462', created 1:25 ago for branch '', in dialogue with 'c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00' [1557513316.000308] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: ------ Media #1 (audio over UDP/TLS/RTP/SAVP) using iLBC/8000 [1557513316.000318] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20052 <> 97.47.70.223:4667 , SSRC 77c38349, 55 p, 3410 b, 0 e, 32 ts [1557513316.000325] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20053 <> 97.47.70.223:4640 (RTCP), SSRC 77c38349, 12 p, 1120 b, 0 e, 29 ts [1557513316.000330] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --- Tag 'c71ac9de-9bf5-4f39-9fda-6bd3aaf97d00', created 1:25 ago for branch '', in dialogue with '2684eff8-3602-41ed-aca2-9f7938362462' [1557513316.000339] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: ------ Media #1 (audio over UDP/TLS/RTP/SAVP) using iLBC/8000 [1557513316.000347] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20064 <> 174.204.14.29:10523, SSRC 779d978b, 595 p, 40090 b, 0 e, 30 ts [1557513316.000355] INFO: [05c7dcfe-06f3-4630-9799-0557b76cc340]: --------- Port 209.182.216.71:20065 <> 174.204.14.29:10496 (RTCP), SSRC 779d978b, 17 p, 1490 b, 0 e, 29 ts [1557513316.000521] DEBUG: [05c7dcfe-06f3-4630-9799-0557b76cc340]: Sending DTLS packet

2 1

DMQ re-ordering concern
by Julien Chavanton 11 May '19

11 May '19

Yesterday at Kamailio World there was an interesting question, raising a concern about replication of user location and DMQ in general, we should track it in the mailing list and use it as a feature request and I can share my initial thoughts on the topic. The concern was about DMQ reordering transactions. With SIP registration this seems like a minor concern, high responsiveness at the cost of potential small inconsistency seems like a good option. Considering that, the state will automatically correct itself and that this can be controlled using the expiration timer. This will become even more insignificant when the replicas can only be used as primary server failover. (it becomes a very small concern only when the primary server fails) With other type of data re-ordering may result in more problematic use cases. My impression is that DMQ should try to be good only with volatile data, data that will expire anyway, like caching with expiration, registration, Dialogs, etc. I think it may be worth looking at adding support for ordering/queuing in DMQ. Performance and simplicity could be maintained by doing mainly transactions in parallel with a configurable re-ordering best effort to minimize the impact of the problem. For example : 1- trying to re-order for a configurable amount of time. (32 seconds to match the RFC for SIP re-transmissions) 2- adding tractability for failed transactions. 3- the possibility to trigger a re-sync. Another option is to look at preserving strict ordering but I can imagine this could add more problems in some cases ...

2 4

Question regarding NAPTR and RURI
by Schneuwly Mathias RUAG 10 May '19

10 May '19

Hi I've a question about NAPTR lockup and rewriting the RURI. Following a little example: - Alice at location A tries to call Bob at location B - location A uses the RURI naptr.locationB.com to reach location B - this NAPTR resolves to hostb.locationB.com and host B is listening on port 5070 hostb has the following alias defined: - udp:hostb.locationB.com:5070 The problem now is, that the incoming RURI is "sip:bob@naptr.locationB.com" and the check to myself is not True. Is there a possibility to rewrite the RURI to the result of the NAPTR query? If I would add a second alias like "udp:naptr.locationB.com:5070" a check to myself would still fail as the RURI does not contain a port. So I would have to add an alias like "udp:naptr.locationB.com" without port, then it would work.? Is this the way to go? Because the documentation says it is important to include the port, otherwise the loose_route() will not work as expected... Thanks for your replies! Mathias

1 0

Help identifying mem leaks
by Duarte Rocha 10 May '19

10 May '19

Greetings, Recently one of my Kamailio's started started answering with a lot of 500 replies to requests because of insufficient private memory. The service Kamailio had been running for 6 months now. In order to solve this i increased the private memory settings and restarted the Kamailio. Before that, when searching a bit about the issue i found an old thread where Daniel suggested using " kamcmd corex.pkg_summary idx 1" to check for pkg leaks in the sip worker process. I ran this before doing the restart in order to identify leaks and found the summary in the logs. However, i am having a hard time interpreting this summary and being able to know if i have or not a mem leak. What should i be looking for? This is the beggining of the summary : qm_status: (0x7ff3c8cef010): qm_status: heap size= 8388608 qm_status: used= 928576, used+overhead=1464080, free=6924528 qm_status: max used (+overhead)= 1488472 qm_status: dumping all alloc'ed. fragments: qm_status: 0. N address=0x7ff3c8d286d8 frag=0x7ff3c8d286a0 size=1024 used=1 qm_status: alloc'd from core: core/str_hash.h: str_hash_alloc(59) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed qm_status: 1. N address=0x7ff3c8d28b40 frag=0x7ff3c8d28b08 size=256 used=1 qm_status: alloc'd from core: core/str_hash.h: str_hash_alloc(59) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed qm_status: 2. N address=0x7ff3c8d28ca8 frag=0x7ff3c8d28c70 size=184 used=1 qm_status: alloc'd from core: core/counters.c: cnt_hash_add(332) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed Any help? Best Regards, Duarte Rocha

1 0

How to configure Kamailio 5.1 with Asterisk pjsip
by przeqpiciel 10 May '19

10 May '19

Hi, There is any working examples how to configure dispatcher module of Kamailio? I have working registrations but working in half dialing function.Signalling are come to asterisk and rtp start sending to my IP but i cant hear anything. Asterisk are doing registrar job - i dont know if it is good idea, maybe not.

5 11

RTP multiplexing, batching and compression (KamailioWorld followup)
by Stefan Sayer 09 May '19

09 May '19

Hi, as a followup to the 5 min 5 slides talk on Tuesday at the Kamailio world conference, I wanted to send links to that implementation, as I did get some interest about this afterwards. This transparent RTP mux gateway implementation in SEMS is a multiplexing, batching and compression mechanism, which can save quite some bandwidth on low bitrate codecs - can be useful if you need to work with very low bitrate links, e.g. on satellite (I tested with 10 G729 calls instead of 5 on a 128kbit sat link). It's a bit like ROHC (RFC3095) but on application level, only for RTP, and by using configuration for IP addresses instead of negotiation. Or as osmux, but without separate negotiation (but in-band), and for all codecs, and SIP. Or iax2 trunking mode, but with normal SIP/RTP. https://github.com/sems-server/sems/blob/sayer/rtp-mux/doc/rtp_mux/rtp_mux_… https://github.com/sems-server/sems/blob/sayer/rtp-mux/doc/rtp_mux/rtp_mux.… For now it's in the sayer/rtp-mux branch, but it's planned to merge it to master, possibly with simplification of the configuration. On another note, many thanks to the organizers of the Kamailio World conference! It's both really nice to meet, and very useful, and I think as well individually as well as for the community as a whole. Best Regards, Stefan

1 0

CRM / Windows integration
by Mark Boyce 09 May '19

09 May '19

Hi All Does anyone have any pointers for integrating Kamailio with CRMs (Dynamics / Salesforce / Zoho) or native Windows? We’re looking for basic click to dial / screen pop. Thanks Mark -- Mark Boyce Dark Origins Ltd

4 5

RE-invite in case of SIP is Active
by Gaurav Bmotra 09 May '19

09 May '19

HI i m gaurav i have installed kamailio 5.1.x on Ubuntu server 18.4 How can i use Re-invite in kamailio if SIP is active so that call can reconnect in case of network loss plz help -- *Regards:* Gaurav Kumar

2 2

Call reconnect in case of loss network
by Gaurav Bmotra 09 May '19

09 May '19

HI i m gaurav i have installed kamailio 5.1.x on Ubuntu server 18.4 when i call from one to another extension , in case of loss network it disconnect the call or stuck there , how can i make it as re-connection when network loss , and it will try to reconnect for some seconds like 30 sec "Example for callingn skype it reconnectcall in case of lossnetwork " plz help -- *Regards:* Gaurav Kumar

1 0

Sending in-dialog requests from custom module's C code
by Ivan Ribakov 09 May '19

09 May '19

I’m working on a custom Kamailio module where I need to send new-dialog and in-dialog requests on timer (hence I’m being forced to generate new messages from C code). So far I’ve been using modules/tm/tm_load.h defined interface to generate messages and handle callbacks. New dialog messages are sent and processed normally. To do that I’m: 1. Calling set_uac_request() to define request parameters 2. Calling tmb.t_request_outside() to send it outside any existing dialog I was able to send in-dialog requests (or so I thought) in a similar fashion, but I soon realised that responses to those requests were dropped because they couldn’t be matched against any known existing transaction. I’m attaching log messages that I believe support this theory and I’ve also observed UDP retransmissions. tm [t_lookup.c:897]: t_reply_matching(): t_reply_matching: hash 50576 label 0 branch 0 tm [t_lookup.c:990]: t_reply_matching(): no matching transaction exists tm [t_lookup.c:993]: t_reply_matching(): failure to match a transaction tm [t_lookup.c:1088]: t_check_msg(): msg (0x5abcb50) id=1 global id=1 T end=(nil) tm [t_reply.c:2195]: reply_received(): transaction not found - (branch -1) The way I’m currently generating in-dialog requests is very similar to what tmb.t_request_outside() does, the main difference being that I do the dialog setup manually, based on the call-ID, cseq and from/to tags (I’m tracking transaction identifiers separately) and then pass resulting uac_req_t to tmb.t_request_within() - https://gist.github.com/IvanRibakov/3302cb286b1f4b786d109b406f2435a2 <https://gist.github.com/IvanRibakov/3302cb286b1f4b786d109b406f2435a2> Now, the question part - does anyone know what I’m doing wrong/missing? As I mentioned, when looking at the generated message bodies, they look ok to me (left - initial request that started the dialog, right - first in-dialog request), so I’m guessing I’m missing some Kamailio internal steps needed to register new transaction. SIP flow (up to the point when first UDP retransmission happens) I apologise in advance for the bulky question and will be extremely thankful for any guidance. Regards, Ivan

2 2

GDB debugging Kamailio 5.2.2 IMS authorization failed by the SCSCF
by Woscek, Martin W. 08 May '19

08 May '19

Hi, Looking for some advice running the debugger and setting breakpoints in Kamailio modules such as the SCSCF. Example: We were trying to watch the authenticate() function: 714 int authenticate(struct sip_msg* msg, char* _realm, char* str2, int is_proxy_auth) { Our Kamailio 5.2.2 code was compiled and linked from source with the -g option already enabled by default. We also dropped our Workers to 1 from 16 in the scscf.xml file for the SCSCF to limit the thread count and get the following list of threads below: We tried the first cdp threads: 8462, 8463, and 8464 and while we could set a break point at line 714 for the authenticate() function, it didn't actually break there at all. Question: What pid will we use to catch the authenticate() called during an initial registration from a boghe client? Anything special we may be missing, gdb related or Kamailio settings? kamcmd -s /run/kamailio_scscf/kamailio_ctl kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> ps 8456 main process - attendant 8457 udp receiver child=0 sock=10.0.20.1:6060 8458 slow timer 8459 timer 8460 secondary timer 8461 ctl handler 8462 cdp worker child=0 8463 cdp receiver peer unknown 8464 cdp_receiver_peer=hss522.irisims.org 8465 cdp_acceptor 8466 cdp_timer 8470 notification_worker 8471 notification_worker 8472 notification_worker 8473 notification_worker 8477 JSONRPCS FIFO 8478 JSONRPCS DATAGRAM Any advice appreciated. Thanks, Martin Woscek

2 1

http_client_query module?
by Andrew Chen 08 May '19

08 May '19

Hey guys, Need help here. What module besides tls.so I need to load in order to get http_client_query to work? The module doc says tls.so: #!ifdef WITH_TLS loadmodule "tls.so" #!endif but I keep getting this when doing config check: root@ashmaintpsg51:/etc/kamailio# kamailio -c kamailio.cfg 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 322, column 71: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 323, column 45: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 324, column 42: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 325, column 48: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 326, column 44: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 327, column 71: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 328, column 67: Can't set module parameter 0(12971) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <http_client> found 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 329, column 41: Can't set module parameter 0(12971) ERROR: <core> [core/cfg.y:3309]: yyparse(): cfg. parser: failed to find command http_client_query (params 2) 0(12971) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 859, column 105: unknown command, missing loadmodule? and I have the package installed on my ubuntu 18.04: ii kamailio-*tls*-modules:amd64 5.1.2-1ubuntu2 amd64 TLS support for the Kamailio SIP server (authentication, transport) thoughts? -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 3

Udp errors on High Availability Setup
by Duarte Rocha 08 May '19

08 May '19

Greetings, I have two Machines with Kamailio in a High Availability (HA) configuration. Both machines are active and processing calls and both have one HA IP that can jump to the other machine in case of failure. I also have probing for NAPs configured with each IP as the socket. So, in each machine i have this configuration : listen=udp:HA_Address1 listen=udp:HA_Address2 NAP 1 being probed from socket HA_Address1 NAP 1 being probed from socket HA_Address2 I also have /proc/sys/net/ipv4/ip_nonlocal_bind with value 1. Everything works correctly with this configuration. However when the probing is sent for the NAP' my logs get filled with the same error messages. udp_send(): sendto(sock, buf: 0x7f2d4c91fa18, len: 340, 0, dst: (xxx.xxx.xxx.xxx:xxx), tolen: 16) - err: Invalid argument (22) CRITICAL: <core> [core/udp_server.c:602]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed The error happens because it is trying to probe a NAP using a socket that isn't active at the moment in the machine. Is there a way for this error not to be logged or be disabled without reducing Log Level to suppress CRITICAL errors? I think this is a standard High Availability configuration. Is there some setting that can disable this kind of errors? Best Regards, Duarte Rocha

3 5

HELP ME
by khadime gaye 07 May '19

07 May '19

Good morning, How I can resolve this problem ? << ERROR: Could not load the script in /usr/local/lib64/kamailio//kamctl/kamdbctl.mysql for database engine MYSQL ERROR: database engine not loaded - tried 'MYSQL' >>

2 1

implementing custom authentication method
by Walter.Martín Villalba 03 May '19

03 May '19

Dear list, I'm implementing a custom method for user authentication and would like to kindly ask for some guidance regarding the server side changes that may be needed in order to keep things running smoothly. The idea is to replace the standard user/pass-based digest authentication with a custom one based on Open ID Connect (OIDC) access tokens. I already have some pieces working (receiving access token in REGISTER message, validating the token by calling custom python routine, etc.), but I'm missing the bits needed to keep track of users who have successfully authenticated. While looking at sipcomm.cfg I found calls to *www_authenticate* (defined in modules/auth_db/authorize.c), which in turn calls to *mark_authorized_cred*, *check_auth_hr* (or *auth_check_hdr_md5*), and *generate_avps*,. Some of these functions are indeed changing some values in the DB and/or in memory, and this is where I would like some guidance. Is there any documentation I could look at which hopefully explains what DB values and/or data structures in memory need to be updated in order to keep track of successfully authenticated users? I believe with this last piece I'd be able to wrap up my custom authentication implementation. Thanks in advance! Regards, Walter Martín.

1 0

Kamailio bypassing RTP media
by Ali Taher 03 May '19

03 May '19

Hi everyone, I'm new to kamailio. I plan to setup a sip server cluster, Does someone can give me some suggestions if I can use kamailio as front server, which handle sip message and bypass rtp media message to backendserver, this mean the kamailio handle only sip message, the rtp packets are sent directed to backend server. The sip sequences is 1.softswitch send invite to kamailio 2.kamailio send invite to backend server. 3.backend server return 200 ok to kamailio 4.kamailio return 200 ok to softswitch, the ip and port in sip is from the backend server's msg, this make the softswitch send rtp direct to backend server. 5.rtp packets are transfered between softswitch and backend server. .... 6.backend server send bye to kamailio 7.kamailio send bye to softswitch. Any help is appreciated. Regards, Ali Taher

4 5

forcing socket doesn't work for ACK
by David Villasmil 03 May '19

03 May '19

Hello guys, I have public and private IPs, and i need to force the sending socket replying to internal out externals endpoint, so i'm using this: function to check the destination (i tried using $sndto(ip) but it always returns NULL): route[CHECK_DEST_NET] { if ( $du=~"sip:172\..*" ) { setflag(FLAG_TO_PRIVATE); xlog("L_ERR", "[CHECK_SOURCE] Packet going to PRIVATE -> [$du]\n" ); } else { setflag(FLAG_TO_PUBLIC); xlog("L_ERR", "[CHECK_SOURCE] Packet going to PUBLIC -> [$du]\n" ); } return; } on my relay: route(CHECK_DEST_NET); if (isflagset(FLAG_TO_PRIVATE)) { xlog("L_ERR", "[RELAY] forcing socket to PRIVATE NET\n" ); force_send_socket(LISTEN_INSIDE_IF:LISTEN_INSIDE_PORT); } else { xlog("L_ERR", "[RELAY] forcing socket to PUBLIC NET\n" ); force_send_socket(LISTEN_OUTSIDE_IF:LISTEN_OUTSIDE_PORT); } This works nicely, except for ACKs and potentially other packets sent statelessly? Anyone knows how to fix this? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

6 26

run some extra things before relying message
by Mojtaba 02 May '19

02 May '19

Hello, I have encountered with problem in Kamailio. At first glance it looks simple. Considering the Data Lump feature in Kamailio, All changes in SIP body, does not apply quickly. So if we are using RTPEngine or RTPProxy, How we can get body message (Actually IP and port from SDP after rtpengine_manage function) before relaying message? Suppose i want get some information and run some extra things before relying message? I just added my extra things in t_on_reply block, but it's strange why it doesn't work before relaying! -Mojtaba Esfandiari.S

2 2

Problem with topoh
by Phillman25 Kyriacou 02 May '19

02 May '19

Dear List I have an issue with topoh module. Specifically for in-dialog requests, if the encoded uri is altered i.e. initial encoded contact uri is Contact: <sip:X.X.X.X;line=sr-huAWi7oPBYsF.cC0L2lWOUlPwbSWOUl6wURTw24W> and UAS sends an in-dialog INVITE like this adding tgrp and user=phone: INVITE sip:X.X.X.X;line=sr-huAWi7oPBYsF.cC0L2lWOUlPwbSWOUl6wURTw24W;tgrp=1069912311;user=phone Kamailio cant seem to match/decode this and responds "404 Not Found" I have also set: modparam("topoh", "uri_prefix_checks", 0) As specified here: https://www.kamailio.org/docs/modules/4.4.x/modules/topoh.html#idp37582868 But still doesn't work. Is there a bug with this module? # ==================================================== # ================ TOPOLOGY HIDING =================== # ==================================================== modparam("topoh", "mask_key", "secret") modparam("topoh", "mask_ip", "X.X.X.X") modparam("topoh", "mask_callid", 0) modparam("topoh", "uparam_name", "line") modparam("topoh", "uparam_prefix", "sr-") modparam("topoh", "vparam_name", "branch") modparam("topoh", "vparam_prefix", "z9hG4bKsr-") modparam("topoh", "uri_prefix_checks", 0) Thanks in advance for your support Phillip

2 4

Stack smash error when using auth_ephemeral with KEMI
by Grant Bagdasarian 02 May '19

02 May '19

Hello, I was trying out the auth_ephemeral module inside the xhttp event_route in Python KEMI, and discovered a possible bug. https://pastebin.com/4Ghumfis The following will result in the stack smash error. Whenever I leave out the unixtimestamp the module will complain about not being able to convert to an int, which make sense, but doesn't lead to a stack smash error and a complete crash of Kamailio. KSR.auth_ephemeral.autheph_authenticate("1576734089:grant", "1234"). According to the documentation this module can only be used in REQUEST_ROUTE, but I found a presentation online which also used this module and that particular function in event_route, which is what I need for WebSocket authentication. Hope this helps. Please let me know if you need more information. Regards, Grant

2 1

Kamailio 5.2.2 IMS authorization failed by the SCSCF
by Woscek, Martin W. 02 May '19

02 May '19

Hi, We are getting a SIP 401 Unauthorized -Challenging the UE error originating by the SCSCF. It looks to be related to the nonce/cnonce. Is there something we have misconfigured in our SCSCF module? Log output: May 1 14:01:45 imskamailio /usr/local/sbin/kamailio[18489]: DEBUG: ims_auth [authorize.c:786]: authenticate(): Nonce or response missing: nonce len [-108158976], response16 len[1873606560] May 1 14:01:45 imskamailio /usr/local/sbin/kamailio[18492]: DEBUG: ims_auth [utils.c:168]: get_nonce_response(): Calling find_credentials with realm [ims522.irisims.org] May 1 14:01:45 imskamailio /usr/local/sbin/kamailio[18492]: DEBUG: ims_auth [utils.c:195]: get_nonce_response(): Found nonce response May 1 14:01:45 imskamailio /usr/local/sbin/kamailio[18492]: INFO: ims_auth [authorize.c:827]: authenticate(): uri=sip:irisims.org nonce=9863c63855c8dd888c5c18e79fc61156 response=ce7ce73872b92aff2defa76dd1aff1ac qop=auth-int nc=00000001 cnonce=4fe4daacd69fa3d609c8b396d331eae6 hbody=d41d8cd98f00b204e9800998ecf8427e May 1 14:01:45 imskamailio /usr/local/sbin/kamailio[18492]: DEBUG: ims_auth [rfc2617.c:135]: calc_response(): calc_response(_ha1=7a1b479a0513914e71bcd6d005b3e17d, _nonce=9863c63855c8dd888c5c18e79fc61156, _nc=00000001,_cnonce=4fe4daacd69fa3d609c8b396d331eae6, _qop=auth-int, _auth_int=1,_method=REGISTER,_uri=sip:irisims.org,_hentity=d41d8cd98f00b204e9800998ecf8427e) Thanks, Martin

2 1

New voisonics.com - Kamailio related products and services
by David Cunningham 02 May '19

02 May '19

Hello, Usually it's our client's VoIP technology being updated. Fortunately we found a little spare time to completely revamp the Voisonics website as well! https://voisonics.com/ Voisonics provides products and services in the commercial VoIP and hosted PBX sector; in particular relating to Kamailio, Asterisk, and Enswitch. The business has been specialising in this area for almost 10 years. Please feel free to contact me off-list with any questions. Kind regards, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

1 0

Support for JWT token authentication?
by David Dean 01 May '19

01 May '19

I came across this thread from Jan 2015 discussing the addition of JWT token authentication to Kamailio: https://github.com/kamailio/kamailio/issues/29 Was JWT authentication ever added? Or has anyone else on this list got JWT working somehow?

1 0

CSeq not incrementing - app_ruby
by Andrew White 01 May '19

01 May '19

Hi all, I’m still building with app_ruby and loving it - for the most part! I’m having an issue with one of my providers responding with a 482 on auth invite. Researching, it appears that my CSeq isn’t incrementing and this is the reason for the issue. I already have the relevant flag set in my kamailio.cfg however: modparam("dialog", "track_cseq_updates", 1) During my uac_auth, I’ve tried manually setting the diff, as well as running msg_iflag_reset (as suggested by Daniel - https://github.com/kamailio/kamailio/issues/1359 <https://github.com/kamailio/kamailio/issues/1359> - unfortunately the function isn’t exported in KEMI): if KSR::UAC.uac_auth() then KSR.info("UAC authed, relaying") #KSR::COREX.msg_iflag_reset("UAC_AUTH") KSR::PV.sets("$dlg_var(cseq_diff)", "1") KSR.info("CSeq diff: #{KSR::PV.gete("$dlg_var(cseq_diff)")}") KSR::TM.t_relay() Unfortunately in both cases the actual CSeq doesn’t increment in the second INVITE: INVITE 1 (unauthenticated): > CSeq: 102 INVITE INVITE 2 (with Authorization header): > CSeq: 102 INVITE I’m unsure if I’ve missed something silly around the track_cseq_updates flag, or if app_ruby somehow isn’t interacting with the dialog module when running uac_auth to trigger the increment? Thanks! Kind regards, Andrew

3 6

listening at link local IPv6 address
by Juha Heinanen 01 May '19

01 May '19

My K host is behind a mobile WiFi hotspot and I tried to make K listen at the IPv6 address fe80::6e29:95ff:fe7d:37e6/64 that the host has received from the hotspot. Using that address on listen line gives error: Apr 21 08:55:18 salmon /usr/bin/sip-proxy[6887]: ERROR: <core> [core/udp_server.c:395]: udp_init(): bind(8, 0x7ff97dfb3fe4, 28) on FE80:0:0:0:6E29:95FF:FE7D:37E6: Invalid argument Apr 21 08:55:18 salmon /usr/bin/sip-proxy[6887]: ERROR: <core> [core/udp_server.c:401]: udp_init(): might be caused by using a link local address, try site local or global I can ping that address like this: $ ping6 fe80::6e29:95ff:fe7d:37e6%wlp1s0 PING fe80::6e29:95ff:fe7d:37e6%wlp1s0(fe80::6e29:95ff:fe7d:37e6%wlp1s0) 56 data bytes 64 bytes from fe80::6e29:95ff:fe7d:37e6%wlp1s0: icmp_seq=1 ttl=64 time=0.030 ms I then tried to add %wlp1s0 suffix to the listen address, but got error: Apr 21 09:10:35 salmon sip-proxy[7896]: 0(7948) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 408, column 34: ip address, interface name or hostname expected Did I do something wrong? If not, why is it that K cannot listen at a link local address? It is something that Linux networking stack does not support? -- Juha

6 33

Pipelimit with clean_unused
by Cinthia Leung 30 Apr '19

30 Apr '19

Hello, What is your recommendation on using clean_unused with db defined pipes? >>pl_check("systemwide"); If I leave the system idle, they are eventually "cleaned" as expected. In our use case, that means failed calls unfortunately. I am trying to see if I can mix both db/static pipes with dynamic/run-time pipes. Thanks Cindy

1 1

Next hop of reply, in onreply_route
by Alex Balashov 30 Apr '19

30 Apr '19

I am fairly sure it’s been asked a number of times, but is there a way to know the destination, and more especially the transport, of the next hop of a reply message, viewable from onreply_route? For requests, we have $nh and many other PVs which in some way evidence where it’s going. And yes, I’m aware that this can be previewed from the onsend_routes*, but I need to amalgamate that knowledge with some transaction-specific data. Thanks! — Sent from mobile, with due apologies for brevity and errors.

2 2

"ERROR: reply too big" and ctl binrpc size
by Karsten Horsmann 30 Apr '19

30 Apr '19

Hi all, i use kamailio 5.0.7 in production and i noticed that i cant listen the dialogs after a few days of traffic on this server. Then i got "kamcmd dlg.list_ctx " - "ERROR: reply too big". So now my question - i want to debug my "sleeping dialogs" with dlg.list - how big should it change the values of without knowing the size of the current filled up binrpc stuff? Or is there a better option to debug dialog-module? modparam("ctl", "binrpc_max_body_size", ??) modparam("ctl", "binrpc_struct_max_body_size", ?) -- Cheers and see you in Berlin *Karsten Horsmann*

2 1

Re: [SR-Users] SIP basic flow question: R-URI in ACK
by Yufei Tao 30 Apr '19

30 Apr '19

Hi Daniel, Thank you very much for clarifying! Cheers, Yufei On 30 Apr 2019 at 08:10, <Daniel-Constantin Mierla <miconda(a)gmail.com>> wrote: Hello, there is an errata for that RFC, but it refers only to the BYE, where it adds back the transport=tcp, but the ACK R-URI should follow the same rules, see: * https://www.rfc-editor.org/errata/eid5294 Cheers, Daniel On 28.04.19 22:54, Yufei Tao wrote: Hi, I have a question regarding basic SIP flow for establishing a call session, and wonder if anyone can help me clarify. For normal call set up, INVITE-OK-ACK, from RFC3261, I believe the ACK’s R-URI should be a copy of the Contact header of the OK message. However in RFC3665 sections 3.1 and 3.2 for example, the ACK’s R-URI missed the parameters from the Contact header of the OK, e.g. In OK the Contact header is: Contact: <sip:bob@client.biloxi.example.com;transport=tcp> <sip:bob@client.biloxi.example.com;transport=tcp> And ACK the R-URI is: ACK sip:bob@client.biloxi.example.com SIP/2.0 Which has got the parameter ‘transport=tcp’ removed – why is this? In this case if the proxy connected to Bob handles ACK in the usual way as it would for all in-dialog requests, i.e. based on routing headers only and not extra processing, it’ll try to relay the ACK message to Bob using the default transport UDP which is not expected and will fail. Can anyone help explain why the parameters are removed in RFC3665 examples please? Have I missed anything? Thank you very much! Yufei _______________________________________________ Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com

1 0

docker image for non x86 arch
by Sergey Safarov 30 Apr '19

30 Apr '19

Is the community involved in kamailio docker image for ARM architecture and others not x86 platforms? ARM ARM 64 IBM POWER IBM Z PowerPC 64 LE

3 3

SIP basic flow question: R-URI in ACK
by Yufei Tao 30 Apr '19

30 Apr '19

Hi, I have a question regarding basic SIP flow for establishing a call session, and wonder if anyone can help me clarify. For normal call set up, INVITE-OK-ACK, from RFC3261, I believe the ACK’s R-URI should be a copy of the Contact header of the OK message. However in RFC3665 sections 3.1 and 3.2 for example, the ACK’s R-URI missed the parameters from the Contact header of the OK, e.g. In OK the Contact header is: Contact: <sip:bob@client.biloxi.example.com;transport=tcp> And ACK the R-URI is: ACK sip:bob@client.biloxi.example.com SIP/2.0 Which has got the parameter ‘transport=tcp’ removed – why is this? In this case if the proxy connected to Bob handles ACK in the usual way as it would for all in-dialog requests, i.e. based on routing headers only and not extra processing, it’ll try to relay the ACK message to Bob using the default transport UDP which is not expected and will fail. Can anyone help explain why the parameters are removed in RFC3665 examples please? Have I missed anything? Thank you very much! Yufei

3 2

remove_record_route - bug?
by Sergiu Pojoga 29 Apr '19

29 Apr '19

Hi ppl, After a branch route fails, I need to re-evaluate the next destination and adjust RR parameters, if need be, like for example adjust the nat=yes|priv. failure_route[MANAGE_PSTN_FAILURE] { ... remove_record_route(); record_route(); route(NATMANAGE); ... route(RELAY); } The result is that the new branch is stripped of "Record-Route: <sip:MYIP>", but the params remained. Moreover, record_route hasn't been re-added as instructed in the failure route. Request headers of the initial branch that will eventually timeout and fail: 2019/04/27 18:29:18.034992 10.22.0.1:5060 -> 10.22.0.100:5060 INVITE sip:1514XXXXXXX@10.22.0.100 SIP/2.0 Record-Route: <sip:10.22.0.1;r2=on;lr=on;did=9e2.3dd2;nat=priv> Record-Route: <sip:65.XX.XX.1;r2=on;lr=on;did=9e2.3dd2;nat=priv> New request branch after failure: 2019/04/27 18:29:19.538292 65.XX.XXX.1:5060 -> 65.XX.XX.2:5060 INVITE sip:1514XXXXXXX@65.XX.XX.2 SIP/2.0 ;lr=on;did=9e2.3dd2;nat=priv> kamailio -v version: kamailio 5.1.6 (x86_64/linux) 7d1964 Much obliged. --Sergiu

4 5

Vide SIP conferencing kamailio with freeswitch
by Gaurav Bmotra 28 Apr '19

28 Apr '19

HI i m gaurav i have installed kamailio 5.1.x on Ubuntu server 18.4 i want a solution for video conferencing with kamailio as i am using freeswitch with it is there reference guide for that plz help -- *Regards:* Gaurav Kumar

2 1

Re: [SR-Users] [sr-dev] Vide SIP conferencing kamailio with freeswitch
by Henning Westerholt 28 Apr '19

28 Apr '19

Hello, please ask this usage related questions on our "sr-users" list. Kamailio is not doing much regarding the video calls. E.g. if your calls work for voice with kamailio, they should also work for video. All the setup needs to be done in freeswitch. I found a (outdated) howto with google: https://freeswitch.org/confluence/display/FREESWITCH/FreeSWITCH+1.6+Video Maybe this helps. Henning Am 27.04.19 um 13:22 schrieb Gaurav Bmotra: HI i m gaurav i have installed kamailio 5.1.x on Ubuntu server 18.4 i want a solution for video conferencing with kamailio as i am using freeswitch with it is there reference guide for that plz help _______________________________________________ Kamailio (SER) - Development Mailing List sr-dev(a)lists.kamailio.org<mailto:sr-dev@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

1 0

How to configure ipv6 in kamailio
by Santosh Kumar Dash 28 Apr '19

28 Apr '19

Hi All, I have a kamailio installed in my setup which is working properly in IPV4 configuration. I want to perform IPV6 configuration, I don't have any idea how to configure it, I have tried few things by changing *kamailio.cfg* file but did not work. I am sharing my *kamailio.cfg *file which is working fine in ipv4 Kindly help me to configure for IPV6. lets say my Ipv6 address is : 2402:3a80:d1a:f45a:fe44:2e54:ed2b:9bb2 Thanks,

3 3

Can't set module parameter
by Tmbc 26 Apr '19

26 Apr '19

Hi all Having this issue with kamailio: Can't set module parameter Apr 25 09:57:10 kamailio: ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <dst_avp> of type <1> not found in module <dispatcher> Apr 25 09:57:10 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 119, column 50: Can't set module parameter Apr 25 09:57:10 kamailio: ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <grp_avp> of type <1> not found in module <dispatcher> Apr 25 09:57:10 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 120, column 50: Can't set module parameter Apr 25 09:57:10 kamailio: ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <cnt_avp> of type <1> not found in module <dispatcher> Apr 25 09:57:10 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 121, column 50: Can't set module parameter here is full conf file: https://dpaste.de/bP3E OS: NAME="CentOS Linux" VERSION="7 (Core)" Software version: kamailio 5.2.2 (x86_64/linux) 67f967 Thanks in advance, tmbc

2 1

Re: [SR-Users] Config to control TCP connection reuse
by R, Rajkumar (Raj) 24 Apr '19

24 Apr '19

I think elaborating on the setup may help someone to provide inputs on this. Below is the setup. Client 1 --> Kamailio proxy --> Backend SIP server Client 2 --> Kamailio proxy --> Backend SIP server Client 3 --> Kamailio proxy --> Backend SIP server After I register all three clients, see only one TCP connection is being used between "Kamailio proxy - Backend SIP server". Is there a way to achieve separate TCP connection to Backend SIP server from kamailio. thanks, raj From: R, Rajkumar (Raj) Sent: Monday, April 22, 2019 3:45 PM To: sr-users(a)lists.kamailio.org Subject: Config to control TCP connection reuse Hi, In my setup(kamailio in stateless mode to a backend server), for any number of client registrations kamailio (in stateless mode) is reusing the TCP connection. Let's say if I register 3 different clients through kamailio to my backend server - see only one TCP connection is used, which I do not want. I have gone through the core modules to see if any TCP config param exists to control on this, but couldn't find one. Could anyone help how to achieve different TCP connections to same destination in kamailio? thanks, raj

2 1

DMQ_USRLOC
by Gholamreza Sabery 24 Apr '19

24 Apr '19

Hi, Recently, I started to use dmq_usrloc module. I successfully set it up. Unfortunately, the documentation does not specify the behavior of dmq_usrloc module with other Kamailio modules. For example, I see a bunch of KDMQ messages are exchanged between nodes, but how the lookup() function behaves with dmq_usrloc, or what is it's effect on a db_mode of 3! Regards

5 6

JSON error - control character 0xd
by David Dean 23 Apr '19

23 Apr '19

I'm trying to send an SDP from a SIP client to Janus using JSON over HTTP. The problem is that Janus is erroring on the SDP content with the following error: JANUS HTTP: Get SDP for echo plugin: {#012 "janus": "error",#012 "error": {#012 "code": 454,#012 "reason": "JSON error: on line 9: control character 0xd near '\"v=0'"#012 }#012} Result code 200 I tried using {s.escape.common} to escape any quotations, commas etc but it doesn't appear to replace the control characters with newlines. Any suggestions on how best to remove these control characters so that Janus will accept the SDP over JSON? Here is the relevant section of kamailio.cfg: # HTTP: Request SDP for echo test plugin sdp_get("$avp(sdp)"); $var(res) = http_connect("janus", "/janus/$var(JANUS-ID)/$var(ECHO-ID)", "application/json", "{ \"janus\" : \"message\", \"transaction\" : \"testtesttest99\", \"body\" : { \"audio\" : true }, \"jsep\" : { \"type\" : \"offer\", \"sdp\" : \"$(avp(sdp){s.escape.common})\" }}", "$avp(janus-pluginsession)"); xlog("L_INFO", "JANUS HTTP: Get SDP for echo plugin: $avp(janus-pluginsession) Result code $var(res)\n");

3 6

Direction of replies
by Duarte Rocha 23 Apr '19

23 Apr '19

Greetings, Is there a way to know in reply_route if a reply has direction downstream or upstream regarding the first INVITE? I know there are vars and methods for finding this out on requests, but i can't find anything for replies. Thanks in advance, Best Regards, Duarte Rocha

2 1

CDR start time of a canceled call
by Jan-Hendrik Dörner 23 Apr '19

23 Apr '19

Hello, I just noticed that the logged „start_time" as well as „end_time" of a canceled call is set to the „invite time“. If done this way, it is harder to calculate the „ringing time“. Is there an option to change this behaviour (i.e. to log the time of the received „bye“ instead)? (If done so, the ringing time would always be the time between start and invite …) Or is there a special reason for this behaviour? My CDR settings are as followed: modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_expired_dlg_enable", 1) # log unanswered / open dialogs modparam("acc", "cdr_on_failed", 1) # log also not answered calls modparam("acc", "cdr_extra", "inviteTime=$dlg_var(inviteTime)" modparam("acc", "cdr_log_enable", 1) # activate write to syslog modparam("acc", "cdr_facility", "LOG_LOCAL6") # syslog modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "time_mode", 0) #syslog timestamp modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) modparam("acc", "detect_direction", 0) modparam("acc", "log_flag", FLT_ACC) # needed for syslog modparam("acc", "log_missed_flag", FLT_ACCMISSED) # need for logging missed calls in syslog Regards Jan-Hendrik

1 0

Kamailio-5.2.1 - Issues in NDB_MONGODB module initialisation
by José Seabra 22 Apr '19

22 Apr '19

Hello there, I have NDB_MONGODB loaded in kamailio with following configurations: *loadmodule "ndb_mongodb"* *modparam("ndb_mongodb", "server", "name=mgs1;uri='mongodb://mongodbserver:27017/proxyregistrar'")* Kamailio breaks up on start up and prints the following messages: *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/modparam.c:83]: set_mod_param_regex(): 'ndb_mongodb' matches module 'ndb_mongodb'* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/sr_module.c:711]: find_param_export(): found <server> in module ndb_mongodb [/usr/lib64/kamailio/modules/ndb_mongodb.so]* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/modparam.c:99]: set_mod_param_regex(): found <server> in module ndb_mongodb [/usr/lib64/kamailio/modules/ndb_mongodb.so]* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: ndb_mongodb [mongodb_client.c:155]: mongodbc_add_server(): added server[mgs1]=mongodb://10.225.121.12:27017/proxyregistrar <http://10.225.121.12:27017/proxyregistrar>* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 21 rank 8: ndb_mongodb [tcp receiver (generic) child=3]* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: ALERT: <core> [main.c:739]: handle_sigs(): child process 3181 exited by a signal 11* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: ALERT: <core> [main.c:742]: handle_sigs(): core was generated* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/tcp_main.c:3513]: handle_ser_child(): dead child 16, pid 3181 (shutting down?)* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6d0e0, 23, -1, 0x0) fd_no=23 called* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: ndb_mongodb [ndb_mongodb_mod.c:128]: mod_destroy(): cleaning up * Core dump back trace output: *(gdb) bt full* *#0 0x00007f3daa134f93 in _mongoc_client_new_from_uri () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#1 0x00007f3daa156553 in mongoc_uri_get_ssl () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#2 0x00007f3daa134f88 in _mongoc_client_new_from_uri () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#3 0x00007f3daa135029 in mongoc_client_new () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#4 0x00007f3daae6d75f in mongodbc_init () at mongodb_client.c:63* * rsrv = 0x7f3db0f86728* * __FUNCTION__ = "mongodbc_init"* *#5 0x00007f3daae73c46 in child_init (rank=3) at ndb_mongodb_mod.c:113* * __FUNCTION__ = "child_init"* *#6 0x00000000005470d7 in init_mod_child (m=0x7f3db0f85e88, rank=3) at core/sr_module.c:846* * __FUNCTION__ = "init_mod_child"* *#7 0x00000000005474b6 in init_child (rank=3) at core/sr_module.c:874* * ret = 32573* *#8 0x00000000004b3840 in fork_process (child_id=3, desc=0x7ffecc20c7f0 "udp receiver child=2 sock=10.225.121.93:5060 <http://10.225.121.93:5060>", make_sock=1) at core/pt.c:341* * pid = 0* * child_process_no = 3* * ret = -1* * new_seed1 = 1273263324* * new_seed2 = 1531871627* * sockfd = {14, 15}* * __FUNCTION__ = "fork_process"* *#9 0x0000000000424b9b in main_loop () at main.c:1631* * i = 2* * pid = 3807* * si = 0x7f3db123a988* * si_desc = "udp receiver child=2 sock=10.225.121.93:5060 <http://10.225.121.93:5060>\000\177\000\000P\310 \314\376\177\000\000\000e|\261=\177\000\000 \313 \314\376\177\000\000\063\225{\000\000\000\000\000\027\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\200\000\000\000\000\000\217e|\261=\177\000\000`~x\000\000\000\000\000\230\304\022\261=\177\000"* * nrprocs = 4* * woneinit = 1* * __FUNCTION__ = "main_loop"* *#10 0x000000000042c4e9 in main (argc=11, argv=0x7ffecc20cc08) at main.c:2675* * cfg_stream = 0x2893010* * c = -1* * r = 0* * tmp = 0x7ffecc20e6fd ""* * tmp_len = 0* * port = 0* * proto = 2496* * options = 0x7697a0 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"* * ret = -1* * seed = 173321635* * rfd = 4* * debug_save = 0* * debug_flag = 0* * dont_fork_cnt = 0* * n_lst = 0x7ffecc20cac0* * p = 0x7f3db177497d <intel_check_word+173> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \316>* * st = {st_dev = 19, st_ino = 21919, st_nlink = 2, st_mode = 16832, st_uid = 993, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1551179759, tv_nsec = 561093463}, st_mtim = {tv_sec = 1551179759,* *---Type <return> to continue, or q <return> to quit---* * tv_nsec = 561093463}, st_ctim = {tv_sec = 1551179759, tv_nsec = 561093463}, __unused = {0, 0, 0}}* * __FUNCTION__ = "main"* *(gdb)* NDB_MONGODB configuration is pretty simples and currently i'm not making any mongodb operations, i'm just loading the module and trying to connect against mongodb. Any thoughts on this issue? Thank you Best regards -- Cumprimentos José Seabra

2 1

rtpengine_offer() with ICE not updating o= and m= IP addresses
by David Dean 22 Apr '19

22 Apr '19

I'm using the following rtpengine_offer() to force the use of ICE relay and also replace o= and m= rtpengine_offer("replace-origin replace-session-connection ICE=force-relay RTP"); The SDP is being updated to include an ICE relay candidate, but the IP addresses in the o= and m= lines are not changing to the servers IP address (X.X.X.X). I also tried using the media-address parameter but that didn't change the behaviour. When I use rtpengine_answer() then it's not providing an ICE candidate nor changing o= or m=, which I imagine is expected. What am I missing? INVITE from the client (before rtpengine)------------------------------------------------------ INVITE sip:server.domain.com SIP/2.0Via: SIP/2.0/TCP 154.20.1.8:37520;branch=z9hG4bK-1710993570;rportFrom: <sip:username@server.domain.com>;tag=281751229To: <sip:server.domain.com>Contact: <sip:username@154.20.1.8:37520;transport=tcp>Call-ID: c715a8f9-4dd1-38d8-acbd-54153310f59fCSeq: 1756522847 INVITEContent-Type: multipart/mixed;boundary=7efec5a8-3311-0157-fc8b-9af106265507Content-Length: 1506Max-Forwards: 70Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFERPrivacy: noneSupported: 100rel --7efec5a8-3311-0157-fc8b-9af106265507Content-Type: application/sdp v=0o=organization 1983 678901 IN IP4 154.20.1.8s=-c=IN IP4 154.20.1.8t=0 0a=tcap:1 RTP/AVPFm=audio 15418 RTP/AVP 114 115 0 101i=speecha=ptime:20a=minptime:1a=maxptime:255a=silenceSupp:off - - - -a=rtpmap:114 AMR-WB/16000/1a=imageattr:114 octet-align=0a=fmtp:114 octet-align=0a=rtpmap:115 AMR-WB/16000/1a=imageattr:115 octet-align=1a=fmtp:115 octet-align=1a=rtpmap:0 PCMU/8000/1a=rtpmap:101 telephone-event/8000/1a=fmtp:101 0-16a=pcfg:1 t=1a=sendrecva=rtcp-muxa=ssrc:2047236273 cname:e6dcab7948b70d52cd51b75e505c49eba=ssrc:2047236273 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2a=ssrc:2047236273 label:organization@audio INVITE from the server (after rtpengine)------------------------------------------------------ SIP/2.0 200 OKVia: SIP/2.0/TCP 154.20.1.8:37520;branch=z9hG4bK-1710993570;rport=37520;received=2.221.73.230From: <sip:username@server.domain.com>;tag=281751229To: <sip:server.domain.com>;tag=0ea7681ffd64b0ffcde1bff3393fd505.ae3aCall-ID: c715a8f9-4dd1-38d8-acbd-54153310f59fCSeq: 1756522847 INVITEContact: <sip:X.X.X.X:443;transport=tcp>Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFERPrivacy: noneContent-Type: multipart/mixed;boundary=7efec5a8-3311-0157-fc8b-9af106265507Server: kamailio (5.2.2 (x86_64/linux))Content-Length: 1965 --7efec5a8-3311-0157-fc8b-9af106265507Content-Type: application/sdp v=0o=organization 1983 678901 IN IP4 154.20.1.8s=-c=IN IP4 154.20.1.8t=0 0a=tcap:1 RTP/AVPFm=audio 15418 RTP/AVP 114 115 0 101i=speecha=minptime:1a=maxptime:255a=silenceSupp:off - - - -a=imageattr:114 octet-align=0a=imageattr:115 octet-align=1a=pcfg:1 t=1a=rtcp-muxa=ssrc:2047236273 cname:e6dcab7948b70d52cd51b75e505c49eba=ssrc:2047236273 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2a=ssrc:2047236273 label:organization@audioa=rtpmap:114 AMR-WB/16000/1a=rtpmap:115 AMR-WB/16000/1a=rtpmap:0 PCMU/8000/1a=rtpmap:101 telephone-event/8000/1a=fmtp:114 octet-align=0a=fmtp:115 octet-align=1a=fmtp:101 0-16a=sendrecva=ptime:20a=ice-ufrag:kzgbFAnua=ice-pwd:hnEu9EwTrdIZnTWhYbxtmdugvra=candidate:dzkwmPcB28NPHfRA 1 UDP 16777215 X.X.X.X 30366 typ relay raddr X.X.X.X rport 30366a=candidate:dzkwmPcB28NPHfRA 2 UDP 16777214 X.X.X.X 30367 typ relay raddr X.X.X.X rport 30367a=sendrecva=ice-ufrag:uDE9wbvYa=ice-pwd:dx4CcIjqUNFfnRPJEF8GjatXdU

3 3

Config to control TCP connection reuse
by R, Rajkumar (Raj) 22 Apr '19

22 Apr '19

Hi, In my setup(kamailio in stateless mode to a backend server), for any number of client registrations kamailio (in stateless mode) is reusing the TCP connection. Let's say if I register 3 different clients through kamailio to my backend server - see only one TCP connection is used, which I do not want. I have gone through the core modules to see if any TCP config param exists to control on this, but couldn't find one. Could anyone help how to achieve different TCP connections to same destination in kamailio? thanks, raj

1 0

Best tutorial for beginners kamailio
by Gaurav Bmotra 22 Apr '19

22 Apr '19

Hi Plz sujjest best kamailio tutorial or any source where a beginner can start kamailio.. Thanks

2 1

push to talk over cellular application server and related media server implementation
by Thierry Luo 21 Apr '19

21 Apr '19

Hi All, I don't know if this is the appropriate place to ask the following questions: 1. Anyone please recommend open-source implementation of PoC (Push-to-talk Over Cellular) application server? Kamailio can do this? 2. Anyone please recommend open-source implementation of PoC related media server/replicator? Thierry Luo

3 2

Re: [SR-Users] authentication using auth_db
by arish haque 21 Apr '19

21 Apr '19

Hi David, This can solve the issue but depth(records) of that view would be too much. The architecture is like this: One kamailio fronting multiple asterisk. Each of asterisk boxes have their Specific users databases. Thus, I'm trying to create db connections inside request route or completely write my own authentication service if I get the user's Password. So, that would be great if I would be able to pass the db_url to auth_db module in request route. Let me know what you think. Thanks, Arish

2 1

Re: [SR-Users] authentication using auth_db
by arish haque 20 Apr '19

20 Apr '19

Hi David, Thanks for the reply. I checked out sqlops module, this will solve the problem only when I get the authentication password (secret) of the user inside request route. For this I tried checking kamailio pseudovars but haven't found one. Therefore, I am sticking with auth_db module.If this is possible by any other way do let me know. thanks, Arish

2 1

Kamailio, TLS, and LetsEncrypt
by Gaurav Bmotra 19 Apr '19

19 Apr '19

HI this is Gaurav im using kamailio 5.1.2 on ubuntu 18.4 i am trying to configure LetsEncrypt (tls) for kamailio sing following link https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/ but unable to start kamailio ,i m getting these error ------->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Apr 19 11:23:57 ubuntufresh systemd[1]: Starting Kamailio (OpenSER) - the Open Source SIP Server... Apr 19 11:23:58 ubuntufresh kamailio[5365]: INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Apr 19 11:23:58 ubuntufresh kamailio[5365]: INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) Apr 19 11:23:58 ubuntufresh kamailio[5365]: Listening on Apr 19 11:23:58 ubuntufresh kamailio[5365]: Aliases: Apr 19 11:23:58 ubuntufresh kernel: kamailio[5378]: segfault at 0 ip 00007f8d6fdac646 sp 00007ffe8e2337f8 error 4 in libc-2.27.so [7f8d6fcfb000+1e7000] Apr 19 11:23:58 ubuntufresh kamailio[5365]: ERROR: <core> [core/daemonize.c:303]: daemonize(): Main process exited before writing to pipe Apr 19 11:23:58 ubuntufresh systemd[1]: kamailio.service: Control process exited, code=exited status=255 Apr 19 11:23:58 ubuntufresh systemd[1]: kamailio.service: Failed with result 'exit-code'. Apr 19 11:23:58 ubuntufresh systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<------------------------------------ plz help -- *Regards:* Gaurav Kumar

3 5

auth by IP
by Yu Boot 19 Apr '19

19 Apr '19

Following code snippet from default kamailio.cfg never gives 403 if you smart enough to set "fromdomain" parameter on Asterisk to Kamailio's IP. How to fix it? I want password-based registration (which is OK now) and permit calls via Kamailio only from permitted IPs. # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; }

2 4

TLS implementation for kamailio
by Gaurav Bmotra 19 Apr '19

19 Apr '19

HI this is Gaurav im using kamailio 5.1.2 on ubuntu 18.4 i want to implement TLs for kamailio plz help -- *Regards:* Gaurav Kumar

3 2

Microsoft Direct Routing Assistance And Kamailio Integration
by Phillip Cooper 18 Apr '19

18 Apr '19

Hi All, I am looking for some assistance on setting up Microsoft Direct Routing with Kamailio as an SBC. I have a partial config working, I have rewrote the headers going to Direct routing and can place calls in to and out of Direct routing. I have problems with Call hang ups and choppy audio only on the audio stream from Direct Routing. 1) place a call in to direct routing, Hang the call up from the caller and Direct routing hangs up the call. But If you place a call in to Direct routing and hang up the call from direct routing the direct routing hangs up but the call is still active on the caller. IF you call from direct routing through kamailio to a callee and hang up from direct routing the call is hung up correctly. 2) on some calls made to or from direct routing, the audio stream coming from direct routing is sometimes choppy. Its always the audio from direct routing never the audio going to direct routing. My set up: Asterisk <-> Kamailio <-> Direct Routing SIP: Asterisk <-> Kamailio <-> direct routing RTP: Asterisk <-> Direct Routing Kamailio is rewriting the R-URI, TO, FROM, Contact headers going to Direct routing, as Microsoft need the sbc hostname to be in the contact header in a particular format. I am looking for help on the above or if someone would be kind enough to provide a working config that would be awesome! :) Many Thanks in advance for assistance. :) Phil --- This email has been checked for viruses by AVG. https://www.avg.com

1 0

authentication using auth_db module
by arish haque 18 Apr '19

18 Apr '19

Hi all, I'm trying to establish mysql database connection inside request route (at runtime) based on the type of user, as credentials are stored in multiple databases (may be different servers) for the users. Therefore, I am trying to find out that is there anyway to connect to mysql dynamically in request route or pass 'db_url' parameter dynamically to auth_db module. Hope this explains the requirement. Looking for suggestions. With Regards, Arish

2 1

How to append a body to send_reply() ?
by David Dean 18 Apr '19

18 Apr '19

Hello Kamailio gurus, I'm successfully using send_reply() with append_to_reply() to add some custom headers. Now I need to add some text into the reply body. How can I add a body to send_reply() ? Thx, Dave

2 7

After-parsing config file?
by David Villasmil Govea 18 Apr '19

18 Apr '19

Hello all, Kind of a weird question: is it possible to get a config file AFTER it’s been parsed? I.e: after it’s skipped all non-defined blocks, after substdef have been applied, etc. In the form of a normal config file Is this possible? -- DVG -- Imagination is more important than knowledge Albert Einstein

1 0

Use domain instead of IP in kamailio for register user
by Gaurav Bmotra 18 Apr '19

18 Apr '19

HI this is Gaurav im using kamailio 5.1.2 on ubuntu 18.4 i wan to to use domain instead of IP for registration in kamailio Plz help -- *Regards:* Gaurav Kumar

3 3

Does Kamailio provide any API for other program to create sip account
by Gaurav Bmotra 18 Apr '19

18 Apr '19

Hi i am Gaurav I am developing a sip VoIP app in Android, which want to provide the feature of allowing user to create sip account from client side. I use Kamailio as sip server. My thought is when user register to the the user account system, the user account system can communicate with Kamailio, create a sip account associated with the user and pass the sip account to the client, the client then can configure itself using the sip account. Does Kamailio provide any API or module for me to do this? Thanks! -- *Regards:* Gaurav Kumar

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users