- sr-users - kamailio.org

(no subject)
by gui 10 Mar '23

10 Mar '23

Hello I have an issue with Rx in my VolTE call Flow. Please refer to picture and pcap in annex. I am using same rtp engine at origination and termination. I am sending rtpmanage for invite and 183 session progress at both origination and termination. My issue is that Rx is not sending for the proper media flow component to PCRF. At origination it is considering a media flow between A 50034 and RTPEngine 49186 (instead of considering RTP Engine Port 49152) At Termination it is considering a media flow between B 50054 and RTPEngine 49132 (instead of considering RTP EnginePort 49170) Any idea why?

3 4

use_dns_failover and dispatcher
by Lars Jansson 10 Mar '23

10 Mar '23

Hi, I had the intention to route calls to some SRV destinations via dispatcher and to other SRV destinations via DNS lookup and 'use_dns_failover=on'. Currently in a route block using dispatcher two out of three targets within the SRV destination are unavailable (by intention). During my tests to the dispatcher destination I have found that: A) If I have 'use_dns_failover=on' this setting "overrules" the dispatcher routing and the unavailable targets are also tried before DNS failover finds the available target. B) If I have 'use_dns_failover=off' the dispatcher routing logic works as expected and the call is always routed to the only available target directly, making use of the result of the dispatcher OPTIONS pinging. -- So my conclusion is now that you have to choose: Either use dispatcher routing, or use DNS failover based routing. - I'm fine with this, but I just would like to know if my conclusion is correct, or if there is actually a way to use dispacther for some SRV destinations and DNS failover for other SRV destinations. Regards, Lars

1 0

New 'reverse' transaction not using correct transport protocol
by Benoit Panizzon 10 Mar '23

10 Mar '23

Hi CPE registering with TCP (or TLS). 2nd leg is UDP. Within one transaction (INVITE to OK including all ACK and PRACK) transport is kept as desired for both legs. But when the B side disconnects (sending BYE, new reverse transaction), this is sent via UDP to the A CPE which initially talked TCP and thus ignored. record_route() is called on each leg. What could I be missing? Mit freundlichen Grüssen -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 ______________________________________________________

4 6

Silo extra_hdrs duplication
by Dr. Barabás Péter 10 Mar '23

10 Mar '23

Hi, I’m using kamailio’s silo module to store offline messages in it. I set extra_hdrs modparam to e.g. : ‘Resent-from-silo’ so the clients get information that the message has arrived directly (immediatelly) from the sender or it was stored offline and comes from silo. So the problem is the following: * if receiver’s socket is broken (e.g. airplane mode on mobile) and kamailio ‘thinks’ it is registered, server tries to send the message * message will be timed out and based on config it will be stored in silo. * the next step is to check if receiver is registered or not (since the client can re-register during 30sec until the message has timed out) * If client is registered, kamailio tries to send the message immediately with m_dump(). * If the receiver’s connection is still broken, the message will be timed out and store in silo. * In every store, a new ‘resent’ extra_hdrs value is appended. When extra_hdrs length reaches 1024 bytes, the m_dump will fail and it blocks the dumping of messages to the given receiver. Question: can extra_hdrs value be removed before store? Or what can be the solution not to duplicate the extra_hdrs value in some bad network situation? Peter

3 2

Re: [sr-dev] KEMI python 'KSR' has no attribute 'sanity'
by Henning Westerholt 10 Mar '23

10 Mar '23

(adding sr-users) Hello, maybe because you're spelling it wrong? Compare e.g., to here: https://kamailio.org/docs/tutorials/5.6.x/kamailio-kemi-framework/modules/#… Cheers, Henning -----Original Message----- From: agural5(a)gmail.com <agural5(a)gmail.com> Sent: Freitag, 10. März 2023 08:32 To: sr-dev(a)lists.kamailio.org Subject: [sr-dev] KEMI python 'KSR' has no attribute 'sanity' Hello, I am trying to use KEMI KSR.sanity in python but got error: AttributeError: module 'KSR' has no attribute 'sanity' appreciate your help for solve this. Thanks! _______________________________________________ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-leave(a)lists.kamailio.org

2 1

webrtc from public internet have no voice
by mail4arunkr＠gmail.com 10 Mar '23

10 Mar '23

Hello, I have installed Kamailio 5.6 in debian 11 and RTPengine 11.3 also in the same server. I have configured kamailio to work as webrtc server and it forwards the registration to asterisk. Now when I am trying call from jssip webrtc client it reaches kamailio and route it through private interface to asterisk server. Asterisk then route it to the provider server. When i make a call asterisk server recives rtp from the provider and convert the rtp to srtp and sending back to kamailio. but there is no sound for webrtc from public internet . Also i am getting warning (SRTCP /RTP output wanted, but no crypto suite was negotiated) webrtc from Local network works fine with VPN For normal udp call without webrtc works fine. Kamailio having two interfaces, interface1 is private 10.13.1.140 and interface 2 is publi ip 100.x.x.x webrtc client sends calls to the public ip interface 100.x.x.x and kamaiio routes the call to the asterisk via private interface 10.13.1.140. asterisk server sends the call to remote server and gets the rtp back from that Asterisk server ---converts RTP to SRTP and forward to ----> kamailio 10.13.1.140 but there is nothing happens after that, please help me on this i am new to kamailio and rtpengine. The issue is only for webrtc from public internet. But when using webrtc from LAN works fine below are the logs Mar 9 20:21:02 debian /usr/local/sbin/kamailio[11778]: INFO: <script>: from domain recived is 10.13.1.152 Mar 9 20:21:02 debian /usr/local/sbin/kamailio[11778]: INFO: <script>: 09496381412 has fromDomain recived is 10.13.1.152 Mar 9 20:21:02 debian /usr/local/sbin/kamailio[11778]: INFO: <script>: Request going to srtp customied arun Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [control] Adding a proxy for control ng stats:127.0.0.1 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Received command 'offer' from 127.0.0.1:53374 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Dump for 'offer' from 127.0.0.1:53374: { "supports": [ "load limit" ], "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 7377619262916888262 2 IN IP4 127.0.0.1 Mar 9 20:21:02 debian rtpengine[11823]: s=- Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=group:BUNDLE 0 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap-allow-mixed Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic: WMS mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB Mar 9 20:21:02 debian rtpengine[11823]: m=audio 9 UDP/TLS/RTP/SAVPF 111 63 9 0 8 13 110 126 Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 0.0.0.0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp:9 IN IP4 0.0.0.0 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:NM2h Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:BF2WmB5sOZZWVIFppZ3YTiSH Mar 9 20:21:02 debian rtpengine[11823]: a=ice-options:trickle Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:sha-256 9F:FA:18:B0:8D:17:A5:14:FE:22:BA:1E:73:1E:3E:02:6F:17:EC:B5:FC:77:BD:E1:0B:51:DF:7F:61:B0:2F:55 Mar 9 20:21:02 debian rtpengine[11823]: a=setup:actpass Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=msid:mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB 6f36294e-5d92-4f0c-8ea2-ba415d0ec125 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:111 transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:111 minptime=10;useinbandfec=1 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:63 red/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:63 111/111 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:9 G722/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:0 PCMU/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:8 PCMA/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:13 CN/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:110 telephone-event/48000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=ssrc:2480159127 cname:FJAL1TGxCcnDMPXY Mar 9 20:21:02 debian rtpengine[11823]: a=ssrc:2480159127 msid:mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB 6f36294e-5d92-4f0c-8ea2-ba415d0ec125 Mar 9 20:21:02 debian rtpengine[11823]: ", "call-id": "ui7jc53b9lfbt9lf4nu7", "received-from": [ "IP4", "223.190.206.123" ], "from-tag": "7n38ig1acl", "command": "offer" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Using default bitrate of 32000 bps for 2-channel Opus Mar 9 20:21:02 debian rtpengine[11823]: NOTICE: [ui7jc53b9lfbt9lf4nu7]: [core] Creating new call Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Subscribing '7n38ig1acl' to '' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Subscribing '' to '7n38ig1acl' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating codecs for offerer 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec red/48000/2 (63) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec G722/8000 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec PCMU/8000 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec PCMA/8000 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec CN/8000 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/48000 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating codecs for answerer #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec red/48000/2 (63) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec G722/8000 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec PCMU/8000 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec PCMA/8000 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec CN/8000 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/48000 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF 110, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec red/48000/2 (63) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for red/48000/2 (63) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] No codec support for red/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for red/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec G722/8000/1 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for G722/8000 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for G722/8000 is G722/8000/1 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec G722/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for G722/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec PCMU/8000/1 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for PCMU/8000 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for PCMU/8000 is PCMU/8000/1 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec PCMU/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for PCMU/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec PCMA/8000/1 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for PCMA/8000 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for PCMA/8000 is PCMA/8000/1 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec PCMA/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for PCMA/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec CN/8000/1 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for CN/8000 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for CN/8000 is CN/8000/1 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec CN/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for CN/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/48000/1 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for telephone-event/48000 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/48000 is telephone-event/48000/1 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/48000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/48000 with DTMF 110, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF 110, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec red/48000/2 (63) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] No codec support for red/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for red/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec G722/8000/1 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for G722/8000 is G722/8000/1 (9) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec G722/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for G722/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec PCMU/8000/1 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for PCMU/8000 is PCMU/8000/1 (0) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec PCMU/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for PCMU/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec PCMA/8000/1 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for PCMA/8000 is PCMA/8000/1 (8) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec PCMA/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for PCMA/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec CN/8000/1 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for CN/8000 is CN/8000/1 (13) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec CN/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for CN/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/48000/1 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/48000 is telephone-event/48000/1 (110) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/48000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/48000 with DTMF 110, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN 13 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] set FILLED flag for stream, local 10.13.1.127:30020 remote 0.0.0.0:9 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] Creating active DTLS connection context Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] Creating active DTLS connection context Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] set FILLED flag for stream, local 10.13.1.127:30021 remote 0.0.0.0:9 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [10.13.1.127:30000] Initialized incoming SRTP with SDES crypto params: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [1] Initialized outgoing SRTP with SDES crypto params: suite AEAD_AES_256_GCM, tag 1, key czR43Q05Tlky5pj/m6BomEKXh+b5okz/iSUDQqgvHDI= salt Vov9BA7SKter2Ajj Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] Creating passive DTLS connection context Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] Creating passive DTLS connection context Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [10.13.1.127:30001] Initialized incoming SRTP with SDES crypto params: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [2] Initialized outgoing SRTP with SDES crypto params: suite AEAD_AES_256_GCM, tag 1, key czR43Q05Tlky5pj/m6BomEKXh+b5okz/iSUDQqgvHDI= salt Vov9BA7SKter2Ajj Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Replying to 'offer' from 127.0.0.1:53374 (elapsed time 0.022450 sec) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Response dump for 'offer' to 127.0.0.1:53374: { "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 7377619262916888262 2 IN IP4 127.0.0.1 Mar 9 20:21:02 debian rtpengine[11823]: s=- Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap-allow-mixed Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic: WMS mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB Mar 9 20:21:02 debian rtpengine[11823]: m=audio 30000 UDP/TLS/RTP/SAVPF 111 63 9 0 8 13 110 126 Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01 Mar 9 20:21:02 debian rtpengine[11823]: a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid Mar 9 20:21:02 debian rtpengine[11823]: a=msid:mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB 6f36294e-5d92-4f0c-8ea2-ba415d0ec125 Mar 9 20:21:02 debian rtpengine[11823]: a=ssrc:2480159127 cname:FJAL1TGxCcnDMPXY Mar 9 20:21:02 debian rtpengine[11823]: a=ssrc:2480159127 msid:mP5OKOsd0Yb5JQystk9oCQJVA8LOp4pWhuJB 6f36294e-5d92-4f0c-8ea2-ba415d0ec125 Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:111 minptime=10;useinbandfec=1 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:111 transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:63 red/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:63 111/111 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:9 G722/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:0 PCMU/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:8 PCMA/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:13 CN/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:110 telephone-event/48000 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp:30001 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:1 AEAD_AES_256_GCM inline:czR43Q05Tlky5pj/m6BomEKXh+b5okz/iSUDQqgvHDJWi/0EDtIq16vYCOM Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:2 AEAD_AES_128_GCM inline:5abyoU5PKLg1lNfmLg1aBLIqyNAgmKNEEo8J1w Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:3 AES_256_CM_HMAC_SHA1_80 inline:i4O28fJjCyvBVQmwjCb7dySy5K20yeg5n1ky+uhPNSpbqkv8vxkcIaerkO9Gbg Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:4 AES_256_CM_HMAC_SHA1_32 inline:OOydiBrJ9nMu23yaBP7JuYNddpbXX8sN/V9Ab/psnTZIBRZKXenHWVPvJSM9Fw Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:5 AES_192_CM_HMAC_SHA1_80 inline:UtkHFdpsaZSO0nwvmEotIoGN+paLt3LHt7yMG4MfDv5rueBsb80 Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:6 AES_192_CM_HMAC_SHA1_32 inline:hgFJ9vS9Roz1vAMhnrCyviKC/TwCPgrk5jeKbxHlIEKtqSvLdK4 Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:7 AES_CM_128_HMAC_SHA1_80 inline:07Q9Z/8DguM0HJgDHv5HF3YDWHdp23hbz+TepHa8 Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:8 AES_CM_128_HMAC_SHA1_32 inline:djpscuSL/05sVtFNocQpHmr1x+NTcLXKu8ePb0q+ Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:9 F8_128_HMAC_SHA1_80 inline:5FqC2VY+q3vqaju3JwroIJO/OlCM1i6TNRE/3Atj Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:10 F8_128_HMAC_SHA1_32 inline:kUfTs7OFD6ltRNpDi1dSG5ZjuQAFDeEQD5IvOwme Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:11 NULL_HMAC_SHA1_80 inline:JZ2ruS0914NL4mmS7jxg+ngz0IQaE6FBRlet8abd Mar 9 20:21:02 debian rtpengine[11823]: a=crypto:12 NULL_HMAC_SHA1_32 inline:h21D+oGRkr1dDEoMm1+vEKmKsn+4GxNBwgIew2qA Mar 9 20:21:02 debian rtpengine[11823]: a=setup:actpass Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:sha-256 0C:67:09:6B:AE:6B:30:09:81:C5:9C:65:C6:EC:9E:CE:C2:6E:E2:EA:67:B4:B5:B3:40:C4:F1:0C:3E:05:96:79 Mar 9 20:21:02 debian rtpengine[11823]: a=tls-id:8100c85eb1c58be3580e8acd7f097000 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:hcqW22Sc Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:QjHJKT4qNsfZm80zrcyh8SfI76 Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:GtpEjl9r4IzNpiXr 1 UDP 2130706431 10.13.1.127 30000 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:GtpEjl9r4IzNpiXr 2 UDP 2130706430 10.13.1.127 30001 typ host Mar 9 20:21:02 debian rtpengine[11823]: ", "result": "ok" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7//1 port 30000]: [ice] Created candidate pair GtpEjl9r4IzNpiXr:6b1875839eb037b0:1 between 10.13.1.127 and 10.13.1.152:14450, type prflx Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7//1 port 30000]: [ice] Triggering check for GtpEjl9r4IzNpiXr:6b1875839eb037b0:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7//1 port 30000]: [core] Successful STUN binding request from 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Received command 'answer' from 127.0.0.1:60024 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Dump for 'answer' from 127.0.0.1:60024: { "supports": [ "load limit" ], "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 2654832326 4 IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: s=Asterisk Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic:WMS * Mar 9 20:21:02 debian rtpengine[11823]: m=audio 14450 UDP/TLS/RTP/SAVPF 111 126 Mar 9 20:21:02 debian rtpengine[11823]: a=connection:new Mar 9 20:21:02 debian rtpengine[11823]: a=setup:active Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:SHA-256 62:AD:7E:86:4D:FF:87:6B:44:5A:F0:62:A2:37:D6:56:5C:D4:F4:A8:03:88:A6:E1:DD:2A:15:69:75:1B:04:3C Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:7706bb5e0317151b5749cc8550354244 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:4af879c44cb99216424536fa5defd9d5 Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:Ha0d0198 1 UDP 2130706431 10.13.1.152 14450 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:H6719a439 1 UDP 2130706431 103.25.164.57 14450 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:126 0-16 Mar 9 20:21:02 debian rtpengine[11823]: a=ptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=maxptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=msid:d5be09fd-dce5-4d96-879e-f34f22f54ef1 a3f22c04-6988-4464-a458-5abc099e7bc0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:* transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: ", "call-id": "ui7jc53b9lfbt9lf4nu7", "received-from": [ "IP4", "10.13.1.152" ], "from-tag": "7n38ig1acl", "to-tag": "a5935482-3f00-4dd0-b98c-0b4726da777d", "command": "answer" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Using default bitrate of 32000 bps for 2-channel Opus Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unconfirming peer address for local 10.13.1.127:30000 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unconfirming peer address for local 10.13.1.127:30020 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unconfirming peer address for local 10.13.1.127:30001 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unconfirming peer address for local 10.13.1.127:30021 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unsubscribing '7n38ig1acl' from 'a5935482-3f00-4dd0-b98c-0b4726da777d' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Unsubscribing 'a5935482-3f00-4dd0-b98c-0b4726da777d' from '7n38ig1acl' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Subscribing 'a5935482-3f00-4dd0-b98c-0b4726da777d' to '7n38ig1acl' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Subscribing '7n38ig1acl' to 'a5935482-3f00-4dd0-b98c-0b4726da777d' Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating codecs for answerer a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for a5935482-3f00-4dd0-b98c-0b4726da777d #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Codec answer for a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Reverse codec for opus/48000/2 (111) is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Reverse codec for telephone-event/8000 (126) is telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] telephone-event/8000/1 payload type 126 already present, skip Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for 7n38ig1acl #1 -> a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Creating codec handler for telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for 7n38ig1acl #1 -> a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for a5935482-3f00-4dd0-b98c-0b4726da777d #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] set FILLED flag for stream, local 10.13.1.127:30000 remote 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] set FILLED flag for stream, local 10.13.1.127:30001 remote 10.13.1.152:14451 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [10.13.1.127:30001] Initialized incoming SRTP with SDES crypto params: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [crypto] [2] Initialized outgoing SRTP with SDES crypto params: suite AEAD_AES_256_GCM, tag 1, key czR43Q05Tlky5pj/m6BomEKXh+b5okz/iSUDQqgvHDI= salt Vov9BA7SKter2Ajj Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Replacing previously learned prflx ICE candidate with Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Learning new ICE candidate H6719a439:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Created candidate pair GtpEjl9r4IzNpiXr:H6719a439:1 between 10.13.1.127 and 103.25.164.57:14450, type host Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Recalculating all ICE pair priorities Mar 9 20:21:02 debian rtpengine[11823]: WARNING: [ui7jc53b9lfbt9lf4nu7]: [ice] Priority collision between candidate pairs GtpEjl9r4IzNpiXr:H6719a439:1 and GtpEjl9r4IzNpiXr:Ha0d0198:1 - ICE will likely fail Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Sending ICE/STUN request for candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 from 10.13.1.127 to 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Shutting down ICE agent (nothing to do) Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Replying to 'answer' from 127.0.0.1:60024 (elapsed time 0.003226 sec) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Response dump for 'answer' to 127.0.0.1:60024: { "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 2654832326 4 IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: s=Asterisk Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic:WMS * Mar 9 20:21:02 debian rtpengine[11823]: m=audio 30020 UDP/TLS/RTP/SAVPF 111 126 Mar 9 20:21:02 debian rtpengine[11823]: a=connection:new Mar 9 20:21:02 debian rtpengine[11823]: a=maxptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=msid:d5be09fd-dce5-4d96-879e-f34f22f54ef1 a3f22c04-6988-4464-a458-5abc099e7bc0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:* transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:126 0-16 Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp:30020 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=setup:active Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:sha-256 0C:67:09:6B:AE:6B:30:09:81:C5:9C:65:C6:EC:9E:CE:C2:6E:E2:EA:67:B4:B5:B3:40:C4:F1:0C:3E:05:96:79 Mar 9 20:21:02 debian rtpengine[11823]: a=tls-id:ac2907348568344c9743f21fa1383e08 Mar 9 20:21:02 debian rtpengine[11823]: a=ptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:4xVkmu6h Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:kc54UEYL25S4UjgSjVKJdcEiAR Mar 9 20:21:02 debian rtpengine[11823]: a=ice-options:trickle Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:GtpEjl9r4IzNpiXr 1 UDP 2130706431 10.13.1.127 30020 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=end-of-candidates Mar 9 20:21:02 debian rtpengine[11823]: ", "result": "ok" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Processing incoming DTLS packet Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Sending DTLS packet Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] Received ICE/STUN response code 0 for candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 from 10.13.1.152:14450 to 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] Setting ICE candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 as succeeded Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] Best succeeded ICE pair with all components is GtpEjl9r4IzNpiXr:Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE not completed yet, but can use pair GtpEjl9r4IzNpiXr:Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE negotiated: peer for component 1 is 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE negotiated: local interface 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Processing incoming DTLS packet Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [crypto] DTLS: Peer certificate accepted Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [crypto] DTLS handshake successful Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [crypto] DTLS-SRTP successfully negotiated using AES_CM_128_HMAC_SHA1_80 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] SRTP keys, incoming: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] --- AES_CM_128_HMAC_SHA1_80 key AtAWESyBg5e6Ub3EPRQ5ag== salt rgwpYXp6KpHCmfjMxVA= Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] SRTP keys, outgoing: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] --- AES_CM_128_HMAC_SHA1_80 key 8+zHcQ5a1Bv5L0dv2AfKyg== salt 7YaPNc68d5ALtKKIOCQ= Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [crypto] DTLS-SRTP successfully negotiated using AES_CM_128_HMAC_SHA1_80 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] SRTP keys, incoming: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] --- AES_CM_128_HMAC_SHA1_80 key AtAWESyBg5e6Ub3EPRQ5ag== salt rgwpYXp6KpHCmfjMxVA= Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] SRTP keys, outgoing: Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] --- AES_CM_128_HMAC_SHA1_80 key 8+zHcQ5a1Bv5L0dv2AfKyg== salt 7YaPNc68d5ALtKKIOCQ= Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Sending DTLS packet Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Successful STUN binding request from 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1]: [ice] Start nominating ICE pairs Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1]: [ice] Nominating ICE pair GtpEjl9r4IzNpiXr:Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1]: [ice] Sending nominating ICE/STUN request for candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 from 10.13.1.127 to 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] Received ICE/STUN response code 0 for candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 from 10.13.1.152:14450 to 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] Setting nominated ICE candidate pair GtpEjl9r4IzNpiXr:Ha0d0198:1 as valid Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE completed, using pair GtpEjl9r4IzNpiXr:Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE negotiated: peer for component 1 is 10.13.1.152:14450 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [ice] ICE negotiated: local interface 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Received command 'answer' from 127.0.0.1:60024 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Dump for 'answer' from 127.0.0.1:60024: { "supports": [ "load limit" ], "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 2654832326 4 IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: s=Asterisk Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic:WMS * Mar 9 20:21:02 debian rtpengine[11823]: m=audio 14450 UDP/TLS/RTP/SAVPF 111 126 Mar 9 20:21:02 debian rtpengine[11823]: a=connection:new Mar 9 20:21:02 debian rtpengine[11823]: a=setup:active Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:SHA-256 62:AD:7E:86:4D:FF:87:6B:44:5A:F0:62:A2:37:D6:56:5C:D4:F4:A8:03:88:A6:E1:DD:2A:15:69:75:1B:04:3C Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:7706bb5e0317151b5749cc8550354244 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:4af879c44cb99216424536fa5defd9d5 Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:Ha0d0198 1 UDP 2130706431 10.13.1.152 14450 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:H6719a439 1 UDP 2130706431 103.25.164.57 14450 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:126 0-16 Mar 9 20:21:02 debian rtpengine[11823]: a=ptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=maxptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=msid:d5be09fd-dce5-4d96-879e-f34f22f54ef1 a3f22c04-6988-4464-a458-5abc099e7bc0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:* transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: ", "call-id": "ui7jc53b9lfbt9lf4nu7", "received-from": [ "IP4", "10.13.1.152" ], "from-tag": "7n38ig1acl", "to-tag": "a5935482-3f00-4dd0-b98c-0b4726da777d", "command": "answer" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [core] Using default bitrate of 32000 bps for 2-channel Opus Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating codecs for answerer a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Adding codec telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for a5935482-3f00-4dd0-b98c-0b4726da777d #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Codec answer for a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Reverse codec for opus/48000/2 (111) is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Reverse codec for telephone-event/8000 (126) is telephone-event/8000 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] telephone-event/8000/1 payload type 126 already present, skip Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for 7n38ig1acl #1 -> a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Updating supplemental codecs for a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for 7n38ig1acl #1 -> a5935482-3f00-4dd0-b98c-0b4726da777d #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Setting up codec handlers for a5935482-3f00-4dd0-b98c-0b4726da777d #1 -> 7n38ig1acl #1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Default sink codec is opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for opus/48000/2 is opus/48000/2 (111) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec opus/48000/2 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for opus/48000/2 with DTMF -1, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Checking receiver codec telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink codec for telephone-event/8000 is telephone-event/8000/1 (126) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Sink supports codec telephone-event/8000 for passthrough Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [codec] Using passthrough handler for telephone-event/8000 with DTMF 126, CN -1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Dropping new ICE candidate Ha0d0198 in favour of Ha0d0198:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Dropping new ICE candidate H6719a439 in favour of H6719a439:1 Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [ice] Shutting down ICE agent (nothing to do) Mar 9 20:21:02 debian rtpengine[11823]: INFO: [ui7jc53b9lfbt9lf4nu7]: [control] Replying to 'answer' from 127.0.0.1:60024 (elapsed time 0.002244 sec) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7]: [control] Response dump for 'answer' to 127.0.0.1:60024: { "sdp": "v=0 Mar 9 20:21:02 debian rtpengine[11823]: o=- 2654832326 4 IN IP4 10.13.1.152 Mar 9 20:21:02 debian rtpengine[11823]: s=Asterisk Mar 9 20:21:02 debian rtpengine[11823]: c=IN IP4 10.13.1.127 Mar 9 20:21:02 debian rtpengine[11823]: t=0 0 Mar 9 20:21:02 debian rtpengine[11823]: a=msid-semantic:WMS * Mar 9 20:21:02 debian rtpengine[11823]: m=audio 30020 UDP/TLS/RTP/SAVPF 111 126 Mar 9 20:21:02 debian rtpengine[11823]: a=connection:new Mar 9 20:21:02 debian rtpengine[11823]: a=maxptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=msid:d5be09fd-dce5-4d96-879e-f34f22f54ef1 a3f22c04-6988-4464-a458-5abc099e7bc0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-fb:* transport-cc Mar 9 20:21:02 debian rtpengine[11823]: a=mid:0 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:111 opus/48000/2 Mar 9 20:21:02 debian rtpengine[11823]: a=rtpmap:126 telephone-event/8000 Mar 9 20:21:02 debian rtpengine[11823]: a=fmtp:126 0-16 Mar 9 20:21:02 debian rtpengine[11823]: a=sendrecv Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp:30020 Mar 9 20:21:02 debian rtpengine[11823]: a=rtcp-mux Mar 9 20:21:02 debian rtpengine[11823]: a=setup:active Mar 9 20:21:02 debian rtpengine[11823]: a=fingerprint:sha-256 0C:67:09:6B:AE:6B:30:09:81:C5:9C:65:C6:EC:9E:CE:C2:6E:E2:EA:67:B4:B5:B3:40:C4:F1:0C:3E:05:96:79 Mar 9 20:21:02 debian rtpengine[11823]: a=tls-id:ac2907348568344c9743f21fa1383e08 Mar 9 20:21:02 debian rtpengine[11823]: a=ptime:20 Mar 9 20:21:02 debian rtpengine[11823]: a=ice-ufrag:4xVkmu6h Mar 9 20:21:02 debian rtpengine[11823]: a=ice-pwd:kc54UEYL25S4UjgSjVKJdcEiAR Mar 9 20:21:02 debian rtpengine[11823]: a=ice-options:trickle Mar 9 20:21:02 debian rtpengine[11823]: a=candidate:GtpEjl9r4IzNpiXr 1 UDP 2130706431 10.13.1.127 30020 typ host Mar 9 20:21:02 debian rtpengine[11823]: a=end-of-candidates Mar 9 20:21:02 debian rtpengine[11823]: ", "result": "ok" } Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] New ingress SSRC for: 10.13.1.152:14450 SSRC: 46ca8abf Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Handling packet: remote 10.13.1.152:14450 (expected: 10.13.1.152:14450) -> local 10.13.1.127:30000 (RTP seq 31783 TS 528 SSRC 46ca8abf) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Generated session key: master key f3ecc771..., master salt ed868f35..., label 00, length 16, result 6806f5cc... Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Generated session key: master key f3ecc771..., master salt ed868f35..., label 01, length 20, result 044b0cce... Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [srtp] Generated session key: master key f3ecc771..., master salt ed868f35..., label 02, length 14, result 4426c95d... Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] New egress (direct) SSRC for: 0.0.0.0:9 SSRC: 46ca8abf Mar 9 20:21:02 debian rtpengine[11823]: ERR: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] SRTP output wanted, but no crypto suite was negotiated Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Error when sending message. Error: Inappropriate ioctl for device Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Handling packet: remote 10.13.1.152:14450 (expected: 10.13.1.152:14450) -> local 10.13.1.127:30000 (RTP seq 31784 TS 1488 SSRC 46ca8abf) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Handling packet: remote 10.13.1.152:14450 (expected: 10.13.1.152:14450) -> local 10.13.1.127:30000 (RTP seq 31785 TS 2448 SSRC 46ca8abf) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Handling packet: remote 10.13.1.152:14450 (expected: 10.13.1.152:14450) -> local 10.13.1.127:30000 (RTP seq 31786 TS 3408 SSRC 46ca8abf) Mar 9 20:21:02 debian rtpengine[11823]: DEBUG: [ui7jc53b9lfbt9lf4nu7/a5935482-3f00-4dd0-b98c-0b4726da777d/1 port 30000]: [core] Handling packet: remote 10.13.1.152:14450 (expected:

2 1

Re: Kamailio stops processing the calls - restart fixes it.
by Henning Westerholt 10 Mar '23

10 Mar '23

Hello, please keep the list in the mail flow. Have you tried to set the acc_function modparam to an empty string, as commented in the linked issue? modparam("uac_redirect","acc_function","") If you don't need the acc function from the uac_redirect. Regarding the other warnings, they should be fixed - but different compilers can report different warnings, so it's sometimes happening. If they are just warnings, they should not create an issue. If you are using Debian/Ubuntu you can just use the prebuild packages from deb.kamailio.org - you don't need to build by yourself. Cheers, Henning -----Original Message----- From: Muhammad Danish Moosa <danishmoosa(a)gmail.com> Sent: Donnerstag, 2. März 2023 14:25 To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Kamailio stops processing the calls - restart fixes it. Hi, I tried to install 5.6.4 (https://www.kamailio.org/pub/kamailio/5.6.4/src/) and get this error. Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR: uac_redirect [../../modules/acc/acc_api.h:191]: acc_load_api(): cannot find bind_acc Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR: uac_redirect [uac_redirect.c:259]: redirect_init(): cannot bind to ACC API Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR: <core> [core/sr_module.c:975]: init_mod(): Error while initializing module uac_redirect (/usr/local/lib64/kamailio/modules/uac_redirect.so) It seems this issue was reported earlier and supposed to be fixed but apparently it's not. https://github.com/kamailio/kamailio/issues/3188 Besides that , I had seen warnings during compilation. What should be the most tested and supported version ? Example Warnings: dmq_funcs.c: In function ‘ki_dmq_send_message’: dmq_funcs.c:303:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:303:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] dmq_funcs.c: In function ‘ki_dmq_bcast_message’: dmq_funcs.c:373:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:373:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] CC (gcc) [M dmq.so] notification_peer.o CC (gcc) [M dmq.so] dmq.o dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces] sip_uri_t dmq_server_uri = {0}; On Wed, Mar 1, 2023 at 7:26 PM Henning Westerholt <hw(a)gilawa.com> wrote: > > Hello, > > better take the latest one, e.g. 5.6.4 released yesterday. Minor releases only contains bugfixes, documentation enhancements and similar. Only rarely regressions happen. But you should of course test it. > > Cheers, > > Henning > > -----Original Message----- > From: Muhammad Danish Moosa <danishmoosa(a)gmail.com> > Sent: Mittwoch, 1. März 2023 09:22 > To: Henning Westerholt <hw(a)gilawa.com> > Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > Subject: Re: [SR-Users] Kamailio stops processing the calls - restart fixes it. > > Thank you for your email. > > Is v5.6.1 (July 6, 2022) stable? > > obtained from > > https://www.kamailio.org/pub/kamailio/latest-stable-version-number > > > On Wed, Mar 1, 2023 at 5:50 PM Henning Westerholt <hw(a)gilawa.com> wrote: > > > > Hello, > > > > hard to say without more information, a backtrace etc... As I first step, I would suggest you to update the system to one of the supported releases, e.g. the latest 5.6.x or 5.5.x. > > > > Cheers, > > > > Henning > > > > -----Original Message----- > > From: Muhammad Danish Moosa <danishmoosa(a)gmail.com> > > Sent: Mittwoch, 1. März 2023 01:39 > > To: sr-users(a)lists.kamailio.org > > Subject: [SR-Users] Kamailio stops processing the calls - restart fixes it. > > > > Hi, > > > > I have a very simple proxy (stateful) where kamailio acts as a proxy between 2 endpoints. Everything works fine for weeks and suddenly I see kamailio stops responding. From pcap I can see kamailio is not proxying the session progress and bombarding invites to one endpoint without any reason. Even that invite was stripped on the Body part. > > > > Restarting kamailio fixes it immediately. Unfortunately I could not take bt full yet. > > > > Version is > > > > kamailio 5.5.3 (x86_64/linux) 473cef > > > > configuration is very simple , routing is based on tm.t_relay ( based on KEMI). > > > > Any help will be welcome. > > > > Danish > > > > > > > > -- > > Muhammad Danish Moosa > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to the sender! > > Edit mailing list options or unsubscribe: > > > > -- > Muhammad Danish Moosa > > " The core of mans' spirit comes from new experiences. "___ > Christopher McCandless -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

4 21

WebRTC Error
by Social Boh 09 Mar '23

09 Mar '23

Hello, I have this error when trying to register this softphone: https://github.com/InnovateAsterisk/Browser-Phone 61096#015#012Host: sip1.kamailio.xyz:8443#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012Upgrade: websocket#015#012Origin: https://campus.voztovoice.org#015#012Sec-WebSocket-Version: 13#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: es-419,es;q=0.6#015#012sec-gpc: 1#015#012Sec-WebSocket-Key: uj5cXle8zzBFUzv4kWB2pg==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012> Mar 9 08:10:55 sip1 /sbin/kamailio[194807]: WARNING: <script>: HTTP request received on 8443 Mar 9 08:10:55 sip1 /sbin/kamailio[194807]: DEBUG: xhttp [xhttp_mod.c:426]: xhttp_send_reply(): sending out response: 403 Forbidden Any help is really apreciated -- --- I'm SoCIaL, MayBe

1 1

Location / Registrar, TCP: Use existing TCP connection
by Benoit Panizzon 09 Mar '23

09 Mar '23

Hi List CPE behind Firewall, registering to Kamailio via TCP (or TLS). When a call is sent to the CPE, kamailio attemts to open a new TCP connection and is blocked by Firewall. Is there an option to tell kamailio to use the existing registered TCP connection? Mit freundlichen Grüssen -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 2

Call recovery for HA with sems
by Patrick Karton 09 Mar '23

09 Mar '23

1 0

TLS -> UDP ReInvite
by Social Boh 08 Mar '23

08 Mar '23

hello, I'm configuring Kamailio to permite calls like: UDP -> UDP TLS -> TLS UDP -> TLS TLS -> UDP Until now all is ok; the only problem is with Microsip SoftPhone. When make a call from Microsip TLS to another phone UDP, when the callee answer, Microsip send a new INVITE and Kamailio don't delete all references to SRTP so the call happens but without audio. I know I have to process the reINVITE where I do has_totag stuff but I don't know how. Regards -- --- I'm SoCIaL, MayBe

1 0

Re: sr-users Digest, Vol 213, Issue 52
by Mohamed SADIK 08 Mar '23

08 Mar '23

Hello, Thank you for your reply! I've used your suggestion to accomplish some amazing things. However, I'm having an issue when calling the *"sl.stats"* or any other procedures. I've noticed that the number of "200" responses gets incremented by 2, which is not the case when using the `*kamcmd*` tool. I suspect that this may be due to jsonrpc using *http/https*, which is causing Kamailio to treat it as a "200" response code. Could you advise on how to avoid this issue? Is there any further configuration that needs to be done? Best regards. On Sat, Feb 25, 2023 at 12:00 PM <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..."Today's Topics: > > 1. Kamailio RPC configuration (sadik.oualla.mohamed(a)gmail.com) > 2. Re: Kamailio RPC configuration (Alex Balashov) > > > > ---------- Forwarded message ---------- > From: sadik.oualla.mohamed(a)gmail.com > To: sr-users(a)lists.kamailio.org > Cc: > Bcc: > Date: Fri, 24 Feb 2023 17:07:33 -0000 > Subject: [SR-Users] Kamailio RPC configuration > Dear Kamailio community, > > I am a newbie in Kamailio and I am currently working on a project that > involves communicating with Kamailio using Python. I have been exploring > the Kamailio documentation and I have come across RPC, JSONRPCS..., which I > believe can help me achieve my goal. > > However, I am not sure about the steps to follow in the Kamailio > configuration file to create my own script to communicate with Kamailio > using Python (the script is on an other machine on the same LAN). I would > be grateful if someone could guide me through the process. > > I have already set up Kamailio (builed it from the source code 5.5.5) and > Python on my machines and I have basic knowledge of Kamailio configuration. > I just need some guidance on how to set up the RPC module in Kamailio and > how to create a Python script to communicate with it. I found that I can > use RPyC library of python. > > I would appreciate any help or suggestions from the Kamailio community. > Thank you in advance for your time and assistance. > > Best regards, > Wild Coder. > > > > ---------- Forwarded message ---------- > From: Alex Balashov <abalashov(a)evaristesys.com> > To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> > Cc: > Bcc: > Date: Fri, 24 Feb 2023 13:22:16 -0500 > Subject: [SR-Users] Re: Kamailio RPC configuration > Hi, > > The easiest way to communicate with the JSONRPCS module is probably to use > HTTP, in the form of the `xhttp` module: > > https://kamailio.org/docs/modules/5.6.x/modules/xhttp.html > > You will need... > > 1) To enable the HTTP transport in the `jsonrpcs` module; > > 2) A TCP or TLS listener (listen= config directive) to accept the traffic; > > 3) An xhttp `event_route[xhttp:request]` route, as detailed in that > module's docs: > > > https://kamailio.org/docs/modules/5.6.x/modules/xhttp.html#xhttp.f.xhttp_re… > > 4) Probably some measure of security / authentication for #3. > > The example from jsonrpc_dispatch() is perfectly sufficient to get you > started: > > > https://kamailio.org/docs/modules/5.6.x/modules/jsonrpcs.html#jsonrpcs.f.js… > > You should then be able to do things like: > > # curl \ > -X POST \ > -d '{"jsonrpc": "2.0", "id": "abc123", "method": "ul.dump"}' \ > http://${KAMAILIO_IP}:5060/RPC <http://${kamailio_ip}:5060/RPC> > > -- Alex > > > On Feb 24, 2023, at 12:07 PM, sadik.oualla.mohamed(a)gmail.com wrote: > > > > Dear Kamailio community, > > > > I am a newbie in Kamailio and I am currently working on a project that > involves communicating with Kamailio using Python. I have been exploring > the Kamailio documentation and I have come across RPC, JSONRPCS..., which I > believe can help me achieve my goal. > > > > However, I am not sure about the steps to follow in the Kamailio > configuration file to create my own script to communicate with Kamailio > using Python (the script is on an other machine on the same LAN). I would > be grateful if someone could guide me through the process. > > > > I have already set up Kamailio (builed it from the source code 5.5.5) > and Python on my machines and I have basic knowledge of Kamailio > configuration. I just need some guidance on how to set up the RPC module in > Kamailio and how to create a Python script to communicate with it. I found > that I can use RPyC library of python. > > > > I would appreciate any help or suggestions from the Kamailio community. > Thank you in advance for your time and assistance. > > > > Best regards, > > Wild Coder. > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions > > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to > the sender! > > Edit mailing list options or unsubscribe: > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com > Tel: +1-706-510-6800 e > > _______________________________________________ > sr-users mailing list -- sr-users(a)lists.kamailio.org > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org >

1 0

Using jsonrpc_dispatch in xhttp:request - is it possible to restrict the RPC that can be invoked ?
by Chaigneau, Nicolas 07 Mar '23

07 Mar '23

Hello, I'm using jsonrpc_dispatch in a "xhttp:request" section (with xhttp and jsonrpcs modules), e.g.: event_route[xhttp:request] { if ($hu =~ "^/RPC") { jsonrpc_dispatch(); exit; } xhttp_reply("404", "Not Found", "", ""); exit; } This works, but I would like to restrict the RPC functions that can be invoked this way. Any advice on how I could do that ? The xhttp module provides "url_skip" and "url_match" but this is not useful because in the URL I only have something like "RPC". And the method is in the JSON body. I could parse the JSON body before calling jsonrpc_dispatch, but it's a bit complicated (I don't know if it's feasible in Kamailio script ?), and seems redundant because jsonrpc_dispatch already does that... Maybe somehow this could be checked from the "void *" second argument passed to the RPC function ? Thanks. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 4

Info: Kamailio World 2023 - Announcing First Group Of Speakers
by Daniel-Constantin Mierla 06 Mar '23

06 Mar '23

Hello, it's now like 3 months till the start of the next Kamailio World Conference (taking place in Berlin, Germany, during June 5-8, 2023) and the first group of speakers has just been published, the details are available at: - https://www.kamailioworld.com/k2023/speakers/ Not all proposals were reviewed and Call for Speakers is still open, therefore if you want to share your interesting experiences or knowledge in the RTC space, submit it via: - https://www.kamailioworld.com/k2023/call-for-speakers/ All together, expect another edition of Kamailio World conference with great content covering topics such as RTC scalability, security, cloud-based deployments and elasticity, NG112/911, IoT, WebRTC, VoLTE and 4G/5G. Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 0

Remove silo extra_hdrs before store
by Dr. Barabás Péter 06 Mar '23

06 Mar '23

Hi, I’m using kamailio’s silo module to store offline messages in it. I set extra_hdrs modparam to e.g. : ‘Resent-from-silo’ so the clients get information that the message has arrived directly (immediatelly) from the sender or it was stored offline and comes from silo. So the problem is the following: * if receiver’s socket is broken (e.g. airplane mode on mobile) and kamailio ‘thinks’ it is registered, server tries to send the message * message will be timed out and based on config it will be stored in silo. * the next step is to check if receiver is registered or not (since the client can re-register during 30sec until the message has timed out) * If client is registered, kamailio tries to send the message immediately with m_dump(). * If the receiver’s connection is still broken, the message will be timed out and store in silo. * In every store, a new ‘resent’ extra_hdrs value is appended. When extra_hdrs length reaches 1024 bytes, the m_dump will fail and it blocks the dumping of messages to the given receiver. Question: can extra_hdrs value be removed before store? Or what can be the solution not to duplicate the extra_hdrs value in some bad network situation? Peter

1 0

How to access rtpengine rtcp-metrics?
by Benoit Panizzon 06 Mar '23

06 Mar '23

Hi all I'm trying to incorporate rtcp data from rtpengine into our CDRS. So trying with the first interesting value, the average mos. modparam("rtpengine", "mos_average_pv", "$avp(mos_average)") If I understood right, to get this variable set, I need to call rtpengine_manage() on the message that terminates the call. So on an established call, that is either BYE or the 200 OK to the BYE. Right? if ($rm == "BYE") { rtpengine_manage(); xlog("L_INFO", "$cfg(route): $rm: MOSS: $avp(mos_average)\n"); } onreply_route[MANAGE_REPLY] { [...] rtpengine_manage(); xlog("L_INFO", "$cfg(route): $rm reply MOS: $avp(mos_average)\n"); } Messages pass those blocks, $avp(mos_average) is 'null' no mater what. What am I missing? In the syslog output of rtpengine I see there is rtcp data. Mit freundlichen Grüssen -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 ______________________________________________________

3 2

tcp_set_connection_lifetime => in respect to 'idle' connection?
by Benoit Panizzon 06 Mar '23

06 Mar '23

Hi List Digging further into my tcp/tls issues... Upon successful authentication I call: tcp_keepalive_enable("60", "5", "5"); tcp_set_connection_lifetime("120"); I tought, this would do to keep the connection alive. I noticed, despite keepalive packets being exchanged, kamailio is closing the connection after a bit more than 2 minutes. I am right at assuming, that tcp_set_connection_lifetime is not related to how long the connection is idle, but is counted from the SYN, no matter if keepalives were successfully exchanged? Does calling tcp_set_connection_lifetime() again restart the lifetime like for 2 more minutes like in this example? Or would I have to keep increase the value of the lifetime on each successful re-register to keep it open? Mit freundlichen Grüssen -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 ______________________________________________________

1 0

Kamailio v5.6.3 Released
by Daniel-Constantin Mierla 05 Mar '23

05 Mar '23

Hello, Kamailio SIP Server v5.6.3 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.3. For more details about version 5.6.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/01/kamailio-v5-6-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 Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

5 10

Kamailio v5.5.6 Released
by Daniel-Constantin Mierla 02 Mar '23

02 Mar '23

Hello, Kamailio SIP Server v5.5.6 stable release is out. This is a maintenance release of the stable branch 5.5 that includes fixes since the release of v5.5.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.6. Note that 5.5 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.6, with v5.6.4 being release out of it. For more details about version 5.5.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/03/kamailio-v5-5-6-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 Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 0

Releasing Kamailio v5.5.6
by Daniel-Constantin Mierla 02 Mar '23

02 Mar '23

Hello, I am considering to release Kamailio v5.5.6 soon, branch on branch 5.5, likely on Thursday or Wednesday next week (Mar 2/3, 2023). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 1

Websocket closing
by David Villasmil 01 Mar '23

01 Mar '23

Hello guys, We're seeing corner cases where the following happens: On proxy-ws - IP1:PORT1 connects via websocket from Client1 - Registration happens on an upstream kamailio - for any reason, the TCP socket closes or times out. - IP1:PORT1 (same IP:PORT combination) connects via websocket from Client2 - Registration happens on an upstream kamailio Now a call comes in to Client1. Because the first connection was never cleaned up, it is sent to the proxy-ws and the proxy will send it to the IP1:PORT1 where Client2 is connected. Short story, proxy-ws doesn't check the IP1:PORT1 where it is sending the INVITE is the actual client it is supposed to be sending... It seems that when a socket is closed, the mapping IP:PORT to Address (i.e.: sip:d4f27e34@994f31243be9.invalid;transport=ws) doesn't seem to be cleared... is this by design? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 6

Kamailio stops processing the calls - restart fixes it.
by Muhammad Danish Moosa 01 Mar '23

01 Mar '23

Hi, I have a very simple proxy (stateful) where kamailio acts as a proxy between 2 endpoints. Everything works fine for weeks and suddenly I see kamailio stops responding. From pcap I can see kamailio is not proxying the session progress and bombarding invites to one endpoint without any reason. Even that invite was stripped on the Body part. Restarting kamailio fixes it immediately. Unfortunately I could not take bt full yet. Version is kamailio 5.5.3 (x86_64/linux) 473cef configuration is very simple , routing is based on tm.t_relay ( based on KEMI). Any help will be welcome. Danish -- Muhammad Danish Moosa

3 5

Kamailio v5.6.4 Released
by Daniel-Constantin Mierla 27 Feb '23

27 Feb '23

Hello, Kamailio SIP Server v5.6.4 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.4. For more details about version 5.6.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/02/kamailio-v5-6-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. An additional note to say that call for speakers and registration for Kamailio World Conference 2023 are now open, more details at: * https://www.kamailioworld.com 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 Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 0

Kamailio MS Teams TLS Issue
by iliusha.md＠gmail.com 27 Feb '23

27 Feb '23

Hello, We have one Kamailio Instance connected with MS Teams (based on this instruction: https://skalatan.de/en/blog/kamailio-sbc-teams), which worked fine for a while until recently we noticed that calls from teams are not working anymore. When I looked through the logs I found that Microsoft cannot establish a TLS connection to our server because of the cipher: TLS accept:error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher (sni: sbc.example.com - domain is obfuscated). Certificate is valid, the configuration is below: [server:default] method = TLSv1.2+ verify_certificate = no require_certificate = no private_key = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.key certificate = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.crt server_name = sbc1-teams.example.net ca_list = /usr/local/etc/kamailio/certs/sectigo_ca.pem #ca_list=/etc/ssl/certs/ca-bundle.crt [client:default] method = TLSv1.2+ verify_certificate = no require_certificate = no private_key = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.key certificate = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.crt ca_list = /usr/local/etc/kamailio/certs/sectigo_ca.pem #ca_list=/etc/ssl/certs/ca-bundle.crt We use a certificate from Sectigo, but I've tried with Let's Encrypt - and it's the same. Any idea what could be the reason?

5 7

Releasing v5.6.4
by Daniel-Constantin Mierla 27 Feb '23

27 Feb '23

Hello, I am considering to release Kamailio v5.6.4 (out of branch 5.6) next week (likely on Monday or Tuesday, Feb 27/28, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 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