- sr-users - kamailio.org

SIP Packet identifier
by jay binks 19 May '15

19 May '15

So im logging lots of information to Syslog to assist our helpdesk in diagnosing customer issues. Im seeing LOTS of user agents that re-use the sip Call-ID ( especially in registers ). What im wanting to be able to do is link a log message ( that I log at some point in my dialplan ) to a specific SIP packet ( viewed from voipmonitor, HOMER, wireshark ). I cant REALLY see anything in the SIP to uniquely identify a packet, however if kamailio provided the UDP packet checksum in a pseudo variable then we could combine that with the sip call-id to hopefully do what im after. does anyone else have any ideas about how do what im after ? -- Sincerely Jay

4 3

Planning to release Kamailio v4.2.5
by Daniel-Constantin Mierla 19 May '15

19 May '15

Hello, I am considering to release a new maintenance version from latest stable branch - to be v4.2.5 - next week, most likely on Tuesday (May 19) or Wednesday (May 20). If there is anything important to get in and not discussed yet, bring the topic on development mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 1

NO VOICE AFTER MSILO
by sscc 19 May '15

19 May '15

i have configured msilo module successful but there isn't any voice with msilo. i debug and compare the call flow with and without msilo. with msilo in call flow it didn't follow to relay and consequently didnt activate rtpproxy befor the call is answered. due to which during call there isn't any voice. please help -- View this message in context: http://sip-router.1086192.n5.nabble.com/NO-VOICE-AFTER-MSILO-tp137430.html Sent from the Users mailing list archive at Nabble.com.

3 8

sems-rtpengine-webrtc client audio problem
by Juha Heinanen 19 May '15

19 May '15

i have not been able to figure out, why i can't hear any audio when i call from webrtc client (using UDP/TLS/RTP/SAVPF profile) to sems echo server (using RTP/AVP profile): 1) webrtc client - UDP/TLS/RTP/SAVPF - rtpengine - RTP/AVP - sems echo server if i call from the same webrtc client to baresip, audio works fine: 2) webrtc client - UDP/TLS/RTP/SAVPF - rtpengine - RTP/AVP - baresip also, if i call from baresip using UDP/TLS/RTP/SAVPF profile to sems, audio works fine: 3) basesip - UDP/TLS/RTP/SAVPF - rtpengine - RTP/AVP - sems echo server below is level 7 debug from the problem case (1). stats at the bottom tell that audio packets were flowing both ways fine. what does not seem correct is that the webrtc client is constantly sending "Successful STUN binding requests" to rtpengine. any advise for further debugging this problem would be highly appreciated. -- juha ------------------------------------------------------------------------------ May 18 11:47:34 box /usr/bin/sip-proxy[18299]: INFO: ===== rtpengine_offer(ICE=force replace-session-connection replace-origin via-branch=1 rtcp-mux-demux RTP/AVP) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'offer' from 127.0.0.1:43378 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'offer' from 127.0.0.1:43378: { "sdp": "v=0#015#012o=- 4880355588178147449 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012m=audio 35551 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126#015#012c=IN IP4 93.106.207.11#015#012a=rtcp:35551 IN IP4 93.106.207.11#015#012a=candidate:1603072777 1 udp 2122260223 192.168.43.146 35551 typ host generation 0#015#012a=candidate:1603072777 2 udp 2122260223 192.168.43.146 35551 typ host generation 0#015#012a=candidate:2861 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... 99801 1 tcp 1518280447 192.168.43.146 0 typ host tcptype active generation 0#015#012a=candidate:286199801 2 tcp 1518280447 192.168.43.146 0 typ host tcptype active generation 0#015#012a=candidate:2466368666 1 udp 1686052607 93.106.207.11 35551 typ srflx raddr 192.168.43.146 rport 35551 generation 0#015#012a=candidate:2466368666 2 udp 1686052607 93.106.207.11 35551 typ srflx raddr 192.168.43.146 rport 35551 generation 0#015#012a=ice-ufrag:U+gG6hyUzfrt859a#015#012a=ice-pwd:FQwGMInhUjWl8bbYIbSJS1pz#015#012a=fingerprint:sha-256 09:D6: ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... AA:5B:F2:9E:D6:A7:CE:69:D3:76:67:EF:36:A6:F4:87:94:B7:37:82:AF:17:9E:4B:E8:B7:F4:F1:8C:A0#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time#015#012a=sendrec… opus/48000/2#015#012a=fmtp:111 minptime=10; useinbandfec=1#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... #012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:2202238380 cname:zcLA/sUaZsuYHC73#015#012a=ssrc:2202238380 msid:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM 2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=ssrc:2202238380 mslabel:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012a=ssrc:2202238380 label:2053b0c2-35f2-48f8-ae79-419a078169f4#015#012", "ICE": "force", "replace": [ "session-connection", "origin" ], "transport-protocol": "RTP/AVP", "rtcp-mux": [ "demux" ], "call-id": "e91aj9gq39qr07b6dn6u", "vi ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... a-branch": "z9hG4bK1294663", "received-from": [ "IP4", "<sip-proxy-rtpengine-ip>" ], "from-tag": "0m9av72lp5", "command": "offer" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Creating new call May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Opened ports 8012..8013 for media relay May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Opened ports 8028..8029 for media relay May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 1603072777:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Created candidate pair MmPVRTRG3mIW6Esg:1603072777:1 between <sip-proxy-rtpengine-ip> and 192.168.43.146:35551, type host May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 1603072777:2 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Created candidate pair MmPVRTRG3mIW6Esg:2466368666:1 between <sip-proxy-rtpengine-ip> and 93.106.207.11:35551, type srflx May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 2466368666:2 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'offer' from 127.0.0.1:43378 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'offer' to 127.0.0.1:43378: { "sdp": "v=0#015#012o=- 4880355588178147449 2 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012m=audio 8012 RTP/AVP 111 103 104 9 0 8 106 105 13 126#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10; useinbandfec=1#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:2202238380 cname:zcLA/sUaZsuYHC73#015#012a=ssrc:2202238380 msid:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM 2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=ssrc:2202238380 mslabel:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012a=ssrc:2202238380 label:2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=sendrecv#015#012a=rtcp:8013#015#012a=ice-ufrag:aEaiKI4d#015#012a=ice-pwd:S0ET0fRwnGLZ6lYSdXuAfvCo9K#015#012a=candidate:MmPVRTRG3mIW6Esg 1 UDP 2130706431 <sip-proxy-rtpengine-ip> 8012 typ host#015#012a=candidate:MmP ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... VRTRG3mIW6Esg 2 UDP 2130706430 <sip-proxy-rtpengine-ip> 8013 typ host#015#012", "result": "ok" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box /usr/bin/sip-proxy[18242]: INFO: ===== rtpengine_answer(ICE=force via-branch=2 trust-address) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'answer' from 127.0.0.1:49396 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'answer' from 127.0.0.1:49396: { "sdp": "v=0#015#012o=sems 1244512444 1372754 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=sems#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012t=0 0#015#012m=audio 8064 RTP/AVP 0 8 126#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=sendrecv#015#012a=direction:both#015#012", "ICE": "force", "flags": [ "trust-address" ], "call-id": "e91aj9gq39qr07b6dn6u", "via-branch": "z9hG4bK1294663", "received-from": [ "IP4", "127.0.0.1" ], "from-tag": "0m9av72lp5", "to-tag": "627A71DC-5559A726000163C1 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... -AA759700", "command": "answer" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Shutting down ICE agent (nothing to do) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'answer' from 127.0.0.1:49396 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'answer' to 127.0.0.1:49396: { "sdp": "v=0#015#012o=sems 1244512444 1372754 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=sems#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012t=0 0#015#012m=audio 8028 UDP/TLS/RTP/SAVPF 0 8 126#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=direction:both#015#012a=sendrecv#015#012a=rtcp:8028#015#012a=rtcp-mux#015#012a=setup:active#015#012a=fingerprint:sha-1 B0:27:8A:76:DE:C4:2A:18:7D:C9:32:F6:78:79:5E:7B:1D:7C:DB:68#015#012a=ice-ufrag:joFSF896#015#012a=ice-pwd:AMtcYr30DYw7PhCsz1LU1Eoi12#015#012a=candidate:MmPVRTRG ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... 3mIW6Esg 1 UDP 2130706431 <sip-proxy-rtpengine-ip> 8028 typ host#015#012", "result": "ok" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] SRTP output wanted, but no crypto suite was negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Triggering check for MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE pair MmPVRTRG3mIW6Esg:2466368666:1 has been nominated by peer May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE not completed yet May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Triggering check for MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Received ICE/STUN response code 0 for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from 93.106.207.11:35551 to <sip-proxy-rtpengine-ip> May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Setting ICE candidate pair MmPVRTRG3mIW6Esg:2466368666:1 as succeeded May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Best succeeded ICE pair with all components is MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE completed, using pair MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Received ICE/STUN response code 0 for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from 93.106.207.11:35551 to <sip-proxy-rtpengine-ip> May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS: Peer certificate accepted May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS handshake successful May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS-SRTP successfully negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, incoming: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key jZlg8WlCjfEiFoilpz7BQg== salt gUcb/yOXBOIuNY1ItSw= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, outgoing: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key e3hQ8pCcc04HD8I7KWdl/g== salt mrNX5VDOk0+Tif2xv5I= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS-SRTP successfully negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, incoming: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key jZlg8WlCjfEiFoilpz7BQg== salt gUcb/yOXBOIuNY1ItSw= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, outgoing: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key e3hQ8pCcc04HD8I7KWdl/g== salt mrNX5VDOk0+Tif2xv5I= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] Confirmed peer address as <sip-proxy-rtpengine-ip>:8064 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Confirmed peer address as 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Kernelizing media stream May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] Kernelizing media stream May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:39 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:39 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:41 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:41 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:42 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:42 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:44 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:44 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:45 box proxy_monitor[24109]: SIP test succeeded with proxy 192.98.100.34! May 18 11:47:45 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:45 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:47 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:47 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:48 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:48 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:49 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:49 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:50 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:50 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:51 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:51 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:52 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:52 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:53 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:53 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:54 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:54 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:56 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:56 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:57 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:57 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:58 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:58 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:00 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:00 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:01 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:01 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:02 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:02 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:03 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:03 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:04 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:04 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:05 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:05 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:08 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:08 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:09 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:09 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:10 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:10 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:11 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:11 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:12 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:12 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:13 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:13 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:14 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:14 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:15 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:15 box proxy_monitor[24109]: SIP test succeeded with proxy 192.98.100.34! May 18 11:48:15 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:16 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:16 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:17 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:17 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:18 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:18 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:19 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:19 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:21 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:21 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:22 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:22 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:23 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:23 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:24 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:24 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Setting ICE candidate pair MmPVRTRG3mIW6Esg:1603072777:1 as failed May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:26 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:26 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:27 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:27 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:28 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:28 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:29 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:29 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:30 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:30 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:31 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:31 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:33 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:33 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:36 box /usr/bin/sip-proxy[18297]: INFO: ===== rtpengine_delete(via-branch=1) May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'delete' from 127.0.0.1:60722 May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'delete' from 127.0.0.1:60722: { "call-id": "e91aj9gq39qr07b6dn6u", "via-branch": "z9hG4bK3605983", "received-from": [ "IP4", "<sip-proxy-rtpengine-ip>" ], "from-tag": "0m9av72lp5", "command": "delete" } May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Scheduling deletion of call branch '0m9av72lp5' in 30 seconds May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'delete' from 127.0.0.1:60722 May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'delete' to 127.0.0.1:60722: { "created": 1431938854, "last signal": 1431938854, "tags": { "0m9av72lp5": { "tag": "0m9av72lp5", "created": 1431938854, "in dialogue with": "627A71DC-5559A726000163C1-AA759700", "medias": [ { "index": 1, "type": "audio", "protocol": "UDP/TLS/RTP/SAVPF", "streams": [ { "local port": 8028, "endpoint": { "family": "IPv4", "address": "93.106.207.11", "port": 35551 }, "advertised endpoint": { "family": "IPv4", "address": "93.106.207.11", "port": 35551 ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... }, "crypto suite": "AES_CM_128_HMAC_SHA1_32", "last packet": 1431938916, "flags": [ "RTP", "RTCP", "filled", "confirmed", "kernelized", "DTLS fingerprint verified" ], "stats": { "packets": 3084, "bytes": 540700, "errors": 0 } }, { "local port": 8029, "endpoint": { "family": "IPv6", "address": "::", "port": 0 }, "advertised endpoint": { "family": "IPv6", "address": "::", "port": 0 }, "crypto suite": "AES_CM_128_HMAC_SHA1_32", "last packet": 1431938854, "flags": [ "RTCP", "fallback RTCP", "filled" ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... ], "stats": { "packets": 0, "bytes": 0, "errors": 0 } } ], "flags": [ "initialized", "send", "recv", "rtcp-mux", "DTLS-SRTP", "DTLS role active", "ICE" ] } ] }, "627A71DC-5559A726000163C1-AA759700": { "tag": "627A71DC-5559A726000163C1-AA759700", "created": 1431938854, "in dialogue with": "0m9av72lp5", "medias": [ { "index": 1, "type": "audio", "protocol": "RTP/AVP", "streams": [ { "local port": 8012, "endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8064 }, "advertised endpoin ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... t": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8064 }, "last packet": 1431938916, "flags": [ "RTP", "filled", "confirmed", "kernelized" ], "stats": { "packets": 3095, "bytes": 533040, "errors": 0 } }, { "local port": 8013, "endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8065 }, "advertised endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8065 }, "last packet": 1431938854, "flags": [ "RTCP", "filled" ], "stats": { "packets": 0, "bytes": 0, "error ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... s": 0 } } ], "flags": [ "initialized", "send", "recv" ] } ] } }, "totals": { "RTP": { "packets": 6179, "bytes": 1073740, "errors": 0 }, "RTCP": { "packets": 0, "bytes": 0, "errors": 0 } }, "result": "ok" } May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Call branch '0m9av72lp5' deleted, no more branches remaining May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Final packet stats: May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --- Tag '627A71DC-5559A726000163C1-AA759700', created 1:32 ago, in dialogue with '0m9av72lp5' May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ------ Media #1 (audio over RTP/AVP) using PCMU/8000 May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8012 <> <sip-proxy-rtpengine-ip>:8064 , 3110 p, 535620 b, 0 e, 1431938917 last_packet May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8013 <> <sip-proxy-rtpengine-ip>:8065 (RTCP), 0 p, 0 b, 0 e, 1431938854 last_packet May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --- Tag '0m9av72lp5', created 1:32 ago, in dialogue with '627A71DC-5559A726000163C1-AA759700' May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using PCMU/8000 May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8028 <> 93.106.207.11:35551, 3101 p, 543584 b, 0 e, 1431938917 last_packet

1 1

Issue with Asterisk interconnection for VoiceMail
by Igor Potjevlesch 18 May '15

18 May '15

Hello, I experienced a strange issue with some of VoIP accounts. When the INVITE comes into MANAGE_FAILURE, after timeout, the config identifies, with "dialplan", the right Asterisk instance that should handle the call for voicemail. This part is okay, and results in a new INVITE with the Request-URI formed with the right domain (eg. sip: <sip:%3cNUMBER%3e@asterisk3> <NUMBER>@asterisk3). Then, the request goes to RELAY. Here is the issue: sometimes, the request is forwarded to the IP of the UA (the one initially contacted) instead of the IP of Asterisk. I can't figure out the difference between a succeeded call and a failed one. If someone has an idea. Here is the config that handles the VoiceMail: failure_route[MANAGE_FAILURE] { [.] if (isflagset(24)) { $avp(s:inv_timeout) = "5"; t_set_fr($avp(s:inv_timeout)*1000); if (avp_db_load("$to/username","$avp(s:vm_uri)/usr_vm")) { resetflag(24); avp_pushto("$ruri","$avp(s:vm_uri)"); # Dynamic routing if (avp_db_load("$ruri/username","$avp(s:client)/usr_fai")) { if (dp_translate("2","$avp(s:client)/$avp(s:dest)") == 1) { $ru = "sip:" + $rU + "@" + $avp(s:dest); } else { # Load default voicemail $avp(s:client) = "DEFAULT_VM"; dp_translate("2","$avp(s:client)/$avp(s:dest)"); $ru = "sip:" + $rU + "@" + $avp(s:dest); }; } else { # Load default voicemail $avp(s:client) = "DEFAULT_VM"; dp_translate("2","$avp(s:client)/$avp(s:dest)"); $ru = "sip:" + $rU + "@" + $avp(s:dest); } } else { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], User have no mail box\n"); exit; }; prefix("710"); xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], failure route to Voice Mail\n"); route(RELAY); exit; } Regards, Igor.

3 5

dbtext why is my user not recognised
by jaflong jaflong 18 May '15

18 May '15

cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) user1:user1:xxx:10.1.1.1:xxx 9350) DEBUG: auth_db [authorize.c:498]: auth_check(): realm [10.31.8.1] table [subscriber] flags [1] 2(9350) DEBUG: auth [api.c:96]: pre_auth(): auth: digest-algo: MD5 parsed value: 1 2(9350) DEBUG: db_text [dbt_file.c:102]: dbt_load_file(): request for table [subscriber] 2(9350) DEBUG: db_text [dbt_file.c:109]: dbt_load_file(): db is [/usr/local/etc/kamailio/dbtext] 2(9350) DEBUG: db_text [dbt_file.c:124]: dbt_load_file(): loading file [/usr/local/etc/kamailio/dbtext/subscriber] 2(9350) DEBUG: db_text [dbt_tb.c:187]: dbt_table_new(): mtime is 1431951381 2(9350) DEBUG: db_text [dbt_file.c:480]: dbt_load_file(): error at row=0 col=0 c= 2(9350) ERROR: db_text [dbt_lib.c:307]: dbt_db_get_table(): could not load database from file [subscriber] 2(9350) ERROR: db_text [dbt_base.c:200]: dbt_query(): table subscriber does not exist! 2(9350) ERROR: auth_db [authorize.c:187]: get_ha1(): failed to query database 2(9350) exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=498 a=26 n=auth_challenge 2(9350) DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.31.8.1' 2(9350) DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'Proxy-Authenticate: Digest realm="10.31.8.1", nonce="VVnqGlVZ6O4l1T62BGADuI2p8uAnUYeu" regards

1 1

Setting up a presence AS with Kamailio IMS.
by Mihail Dakov 18 May '15

18 May '15

Hi all, I have successfully setup a Kamailio IMS environment using just a single machine running three kamailio instances. I am using kamailio 4.2.4 compiling it myself. I followed this guide: http://nil.uniza.sk/instant-messaging/simple/configuring-im-and-presence-ka… to setup a presence AS using the scscf instance. I used kamdbctl script to create the presence tables with one inconsistence with the guide. I had to create a db in which I created a couple of columns (table_name, table_version) to satisfy the kamdbctl script as it was failing when running "kamdbctl presence". At the moment the problem is that my kamailio instance is failing with the following error: scscf/scscf[5256]: ERROR: <core> [db.c:422]: db_table_version(): invalid type (3) or nul (0) version columns for presentity ... and then some time later: scscf/scscf[5256]: ERROR: <core> [db.c:440]: db_check_table_version(): querying version for table presentity scscf/scscf[5256]: ERROR: presence [presence.c:322]: mod_init(): error during table version check scscf/scscf[5256]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module presence (/home/ng40/kamailio-4.2.4/modules/presence/presence.so) scscf/scscf[5256]: DEBUG: cdp_avp [mod.c:224]: cdp_avp_destroy(): Destroying module cdp_avp I suspect that the problem relays on creating manually the db where I inserted the two columns mentioned above (table_name, table_version) so that I could execute "kamdbctl presence". Could someone assist me into solving this issue? br, md.

1 0

critical crash with dbtext
by jaflong jaflong 18 May '15

18 May '15

HI When using dbtext setup I receive a CRITICAL error and shut down. This is the debug log. My config settings are described below. Please advise how I should fo the correct dbtext config 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): acc 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): auth_db 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): debugger 9(21196) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-4) 9(21196) DEBUG: <core> [local_timer.c:74]: init_local_timer(): init_local_timer: timer_list between 0x9e7268 and 0xa2b268 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 8, 4, 0x7f5aaa402364), fd_no=0 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 9, 4, 0x7f5aaa4023f0), fd_no=1 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 10, 4, 0x7f5aaa40247c), fd_no=2 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 11, 4, 0x7f5aaa402508), fd_no=3 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 12, 4, 0x7f5aaa402594), fd_no=4 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 13, 4, 0x7f5aaa402620), fd_no=5 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 14, 4, 0x7f5aaa4026ac), fd_no=6 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 15, 4, 0x7f5aaa402738), fd_no=7 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 8 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 1, pid 21188 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 8, -1, 0x0) fd_no=8 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 9 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 2, pid 21189 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 9, -1, 0x0) fd_no=7 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 10 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 3, pid 21190 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 10, -1, 0x0) fd_no=6 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 11 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 4, pid 21191 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 11, -1, 0x0) fd_no=5 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 12 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 5, pid 21192 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 12, -1, 0x0) fd_no=4 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 13 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 6, pid 21193 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 13, -1, 0x0) fd_no=3 called 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sruid.c:101]: sruid_init(): root for sruid is [ulcx-5555c137-52cb-] (0 / 19) 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): acc 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): auth_db 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): debugger 8(21195) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-2) 8(21195) DEBUG: ctl [ctl.c:325]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x2682080 8(21195) DEBUG: ctl [ctl.c:332]: mod_child(): ctl: 0 io_listen_loop(1, 0x2682080) 8(21195) INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 8(21195) DEBUG: ctl [io_listener.c:257]: io_listen_loop(): io_listen_loop: adding socket 4, type 2, transport 3 (/tmp/kamailio_ctl) 8(21195) DEBUG: ctl [../../io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x7f5aaf2a36c0, 4, 2, 0x2682080), fd_no=0 --------------------------------------------- cd /usr/local/etc/kamailio mkdir dbtext cd dbtext --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/version table_name(str) table_version(int) subscriber:6 location:6 aliases:6 --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/location username(str) contact(str) expires(int) q(double) callid(str) cseq(int) --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) testuser:testuser:xxx:10.1.1.5:xxx --------------------------------------------- #!define DBURL "text:///usr/local/etc/kamailio/dbtext" #!endif --------------------------------------------- # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) ---------------------------------------------

2 3

Repeated 200 OK from Enswitch
by Darren Campbell (Primar) 18 May '15

18 May '15

Hi all Experiencing a commonly reported issue where calls drop out after 30 seconds or so. Mainly because the provider hangs up after not recognising/receiving ACK in response to 200 OK. Unfortunately (or maybe fortunately), I haven't had much experience with Enswitch so was hoping someone in the community might help guide me as to which rules Enswitch might be using to match ACKs to calls in progress. Maybe there is another avenue I should be investigating. Here's a sample of the 200 OK and ACK that repeats. 13:44:04.155646 IP PROVIDERIP.5060 > 172.21.0.226.5060: SIP, length: 1058 E..>.M..?..Ug.v..........*J.SIP/2.0 200 OK^M Via: SIP/2.0/UDP 172.21.0.226;rport=5060;branch=z9hG4bKfe94.efbf7fbcaf8bd15243a61fdc9d6d1e78.0^M Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK65f00a0c;rport=5080^M Record-Route: <sip:PROVIDERIP;lr=on>^M Record-Route: <sip:172.21.0.226;r2=on;lr=on;ftag=as65919d92;nat=yes>^M Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=as65919d92;nat=yes>^M From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M CSeq: 103 INVITE^M Server: Enswitch^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH^M Supported: replaces^M Contact: <sip:PHONENUMBER@PROVIDERMEDIAIP:5060>^M Content-Type: application/sdp^M Content-Length: 286^M ^M v=0^M o=root 2110894460 2110894461 IN IP4 PROVIDERMEDIAIP^M s=Asterisk PBX 11.3.0^M c=IN IP4 PROVIDERMEDIAIP^M t=0 0^M m=audio 15594 RTP/AVP 0 8 3 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8 PCMA/8000^M a=rtpmap:3 GSM/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-16^M a=ptime:20^M a=sendrecv^M 13:44:04.164519 IP 172.21.0.226.5060 > PROVIDERIP.5060: SIP, length: 525 E..)!A..@..v....g.v.......T.ACK sip:PHONENUMBER@PROVIDERIP:5060 SIP/2.0^M Via: SIP/2.0/UDP 172.21.0.226;branch=z9hG4bKfe94.472e9fc0479de79b4f176cc9585d8880.0^M Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK752b5264;rport=5080^M Route: <sip:PROVIDERIP;lr=on>^M Max-Forwards: 69^M From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M Contact: <sip:PROVIDERUSER@127.0.0.1:5080>^M Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M CSeq: 103 ACK^M User-Agent: Elastix 3.0^M Content-Length: 0^M

2 8

RADIUS Digest Problem
by Sanaii, Maziar 18 May '15

18 May '15

Hello there, I'm trying to configure Kamailio 4.2.4 to authenticate client REGISTERs against a test FreeRADIUS on the localhost, however I have yet to succeed. My installation includes Kamailio 4.2.4, radiusclient 1.1.6, FreeRADIUS 2.2.5 and all of them on a Debian 8.0 machine. I believe I have got all the configurations correct in kamailio.cfg, radiusclient.conf, radius servers file, and freeradius server since the communication between the components are ok. My problem is that when I use a SIP Client such as 3CX SoftPhone, FreeRADIUS gives me an answer included in SIPClient-LOCAL-RADIUS-NOK.txt. I have isolated the problem being in the Digest-Response part since I have ran some other tests that I have included in the zip file attached, but can't figure out why this shouldn't work. From what I have figured out, my SIP Client does not calculate the correct Digest-Response and I have seen this in all the clients I have tested so far. For example, my client sends "5f8dfe8aa4e13994b4ceade49ee0d3d4" although it's supposed to send "528f22527e9cf003df29ede9c243e615". I would really appreciate if you would point out what I did wrong in setting things up. I have done so much googling but have not found anything useful. Regards, Maziar Sanaii Ashtiani

2 1

XLOG To STDERR Not Working
by Nahum Nir 18 May '15

18 May '15

Hi All, I am using Kamailio 4.0.3 and can't logs. .cfg: #!define WITH_DEBUG ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 When the server starts there outputs about xlog: 0(20266) DEBUG: <core> [cfg.y:1791]: yyparse(): loading module xlog.so 0(20266) DEBUG: <core> [sr_module.c:499]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:522]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:564]: load_module(): load_module: trying to load </usr/lib64/kamailio/modules/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:343]: register_module(): register PV from: xlog 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20268) DEBUG: <core> [sr_module.c:935]: init_mod(): DEBUG: init_mod: xlog 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() At the beginning of the Main routing block I put: log("~~~~~~~~~~~~route~~~~~~~~~~~~~~~~~~~~\n"); xdbg("~~~~~~~~~ xdbg - route~~~~~~~~~~~~~~~~~~~~\n"); xlog("L_ALERT","~~~~~~~~~ xlog - route~~~~~~~~~~~~~~~~~~~~\n"); But nothing is logging when I send INVITEs Any help? Thanks, Nir

2 1

How to Change IP on Kamailio
by Mudasar Choudhary 18 May '15

18 May '15

Hi, Hope you are doing fine. Can you please assist me how can I change the IP for Kamailio. Right now its up on this IP: loading modules under /usr/lib/kamailio/modulesListing onudp: 98.212.180.96 [98.212.180.96] :5060tcp: 192.168.18.99 [192.168.18.99] :8888 I want to change both upd and tcp. Please advise. ThanksMudasar

2 1

Kamailio Load balancing multiple asterisk boxes
by Eric Koome 15 May '15

15 May '15

Hi I have two boxes with internal and external interfaces. Each has Kamailio at the public interface and asterisk on the internal one. Making calls within a box is fine but would like to load balance using the other asterisk box. However using dispatcher I have noticed packets are not being routed from Kamailo to the second asterisk. Packets from Kamailo are originating from the external interface and sent to the second asterisk box using private ip address. Off course this is not routable. I have tried masquerading but no joy. Do I need to change kamailio configuration? I want to have a set of asterisk boxes behind Kamailio using dispatcher. I'm I missing a trick? Eric

2 1

misc_radius and auth_radius configuration question
by Yasin CANER 15 May '15

15 May '15

Hello; i am testing to radius modules. i have found this tutorial http://www.kamailio.org/docs/openser-radius-1.0.x.html . it is old but i changed some variables. i configured radiusclient-ng and free radius. But kamailio cann't start because of 0(17813) ERROR: misc_radius [misc_radius.c:208]: mod_init(): misc_radius: can't get code for the SIP-AVP attribute 0(17813) ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module misc_radius (/usr/local/lib64/kamailio/modules/misc_radius.so) i already defined SIP-AVP in dictionary.kamailio. And when i set radius_config in misc_radius , it try to find in default path (/usr/local/etc/radiusclient-ng). So i linked to path /usr/local/etc/radiusclient-ng to solve this problem. ---- kamailio V 4.2.4 ---- ------------------dictionary.kamailio------------ #### Attributes ### ATTRIBUTE Sip-Method 101 integer # Schulzrinne, acc ATTRIBUTE Sip-Response-Code 102 integer # Schulzrinne, acc ATTRIBUTE Sip-Cseq 103 string # Schulzrinne, acc ATTRIBUTE Sip-To-Tag 104 string # Schulzrinne, acc ATTRIBUTE Sip-From-Tag 105 string # Schulzrinne, acc ATTRIBUTE Sip-Translated-Request-URI 107 string # Proprietary, acc ATTRIBUTE Sip-Src-IP 108 string # Proprietary, acc ATTRIBUTE Sip-Src-Port 109 string # Proprietary, acc ATTRIBUTE Digest-Response 206 string # Sterman, auth_radius ATTRIBUTE Sip-Uri-User 208 string # Proprietary, auth_radius ATTRIBUTE Sip-Group 211 string # Proprietary, group_radius ATTRIBUTE Sip-Rpid 213 string # Proprietary, auth_radius ATTRIBUTE SIP-AVP 225 string # Proprietary, avp_radius ATTRIBUTE Digest-Realm 1063 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce 1064 string # Sterman, auth_radius ATTRIBUTE Digest-Method 1065 string # Sterman, auth_radius ATTRIBUTE Digest-URI 1066 string # Sterman, auth_radius ATTRIBUTE Digest-QOP 1067 string # Sterman, auth_radius ATTRIBUTE Digest-Algorithm 1068 string # Sterman, auth_radius ATTRIBUTE Digest-Body-Digest 1069 string # Sterman, auth_radius ATTRIBUTE Digest-CNonce 1070 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce-Count 1071 string # Sterman, auth_radius ATTRIBUTE Digest-User-Name 1072 string # Sterman, auth_radius ### Acct-Status-Type Values ### #VALUE Acct-Status-Type Start 1 # RFC2866, acc #VALUE Acct-Status-Type Stop 2 # RFC2866, acc #VALUE Acct-Status-Type Failed 15 # RFC2866, acc ### Service-Type Values ### #VALUE Service-Type Call-Check 10 # RFC2865, uri_radius VALUE Service-Type Group-Check 12 # Proprietary, group_radius ##VALUE Service-Type Sip-Session 15 # Schulzrinne, acc, auth_radius VALUE Service-Type SIP-Caller-AVPs 30 # Proprietary, avp_radius VALUE Service-Type SIP-Callee-AVPs 31 # Proprietary, avp_radius ### Sip-Method Values ### VALUE Sip-Method Undefined 0 VALUE Sip-Method Invite 1 VALUE Sip-Method Cancel 2 VALUE Sip-Method Ack 4 VALUE Sip-Method Bye 8 VALUE Sip-Method Info 16 VALUE Sip-Method Options 32 VALUE Sip-Method Update 64 VALUE Sip-Method Register 128 VALUE Sip-Method Message 256 VALUE Sip-Method Subscribe 512 VALUE Sip-Method Notify 1024 VALUE Sip-Method Prack 2048 VALUE Sip-Method Refer 4096 VALUE Sip-Method Other 8192 ---------------------------Kamailio.cfg-------------------------------------------------------- #modparam("acc", "log_flag", FLT_ACC) modparam("acc_radius", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp") modparam("acc_radius", "radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "radius_flag", FLT_ACC) modparam("acc_radius", "radius_missed_flag", FLT_ACCMISSED) modparam("acc_radius", "service_type", 15) modparam("misc_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("misc_radius", "group_service_type", 12) modparam("misc_radius", "uri_service_type", 10) modparam("misc_radius", "caller_extra", "Calling-Station-Id=$fu") modparam("misc_radius", "callee_extra", "SIP-URI-User=$rU;SIP-URI-Host=$rd") modparam("misc_radius", "group_extra", "My-Special=$avp(i:100)") modparam("misc_radius", "uri_extra", "Called-Station-Id=$tu") ------------------------------------------------------------------------------------------------ Thanks

3 6

t_lookup_request()
by Alex Balashov 13 May '15

13 May '15

Hello, From the documentation for t_lookup_request()[1], it is not clear whether it creates a new transaction if one does not exist: "Checks if a transaction exists. Returns a positive value if so, negative otherwise. Most likely you will not want to use it, as a typical application of a look-up is to introduce a new transaction if none was found. However this is safely (atomically) done using t_newtran." This language is quite unclear in the following respects: 1) Why would I not want to use it? 2) Does the "typical application" mean that t_lookup_request() _will_ create a new transaction if one does not exist? 3) Do I have some means of choosing whether to invoke t_lookup_request() in a "typical" or "atypical" application? 4) This statement "this is safely (atomically) done using t_newtran" implies that creating a new transaction using t_lookup_request() (which also implies that yes, it does create a new transaction) is "unsafe" and "non-atomic". Why is this? 5) Does this mean that the effect here would be to create two transactions? if(!t_lookup_request()) t_newtran(); -- Alex [1] http://kamailio.org/docs/modules/4.2.x/modules/tm.html#tm.f.t_lookup_request -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

how to delete key from htable?
by Juha Heinanen 13 May '15

13 May '15

there exists rpc command htable.delete that can be used to delete a key from htable. is there a way to delete a key in the config file like assigning $null to it or do i need to use sht_rm_name_re function that feels like an overkill? -- juha

2 4

Kamailio-4.1.5 memory leak
by Bui Minh Yen 13 May '15

13 May '15

Hi everyone, I am using Kamailio-4.1.5. Sometime kamailio was crash because memory leak. Log when out of mem May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1332]: new_t(): ERROR: new_t: out of mem: May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [ucontact.c:103]: new_ucontact(): no more shm memory May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:155]: mem_insert_ucontact(): failed to create new contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:547]: insert_ucontact(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: registrar [save.c:708]: update_contacts(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1332]: new_t(): ERROR: new_t: out of mem: May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [ucontact.c:103]: new_ucontact(): no more shm memory May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:155]: mem_insert_ucontact(): failed to create new contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:547]: insert_ucontact(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: registrar [save.c:521]: insert_contacts(): failed to insert contact Log when kamailio was crash May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: ALERT: <core> [main.c:775]: handle_sigs(): child process 30821 exited by a signal 11 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: used= 1110960, used+overhead=1663384, free=748068456 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 2. N address=0x7f6af599dae8 frag=0x7f6af599dab8 size=176 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 3. N address=0x7f6af599dbf8 frag=0x7f6af599dbc8 size=240 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 4. N address=0x7f6af599dd48 frag=0x7f6af599dd18 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: init_counters(129) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 5. N address=0x7f6af599de28 frag=0x7f6af599ddf8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: modparam.c: set_mod_param_regex(124) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 6. N address=0x7f6af599de98 frag=0x7f6af599de68 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 7. N address=0x7f6af599df78 frag=0x7f6af599df48 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 8. N address=0x7f6af599e008 frag=0x7f6af599dfd8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 9. N address=0x7f6af599e078 frag=0x7f6af599e048 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 10. N address=0x7f6af599e158 frag=0x7f6af599e128 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 11. N address=0x7f6af599e1e8 frag=0x7f6af599e1b8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 12. N address=0x7f6af599e258 frag=0x7f6af599e228 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 13. N address=0x7f6af599e338 frag=0x7f6af599e308 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 14. N address=0x7f6af599e3c8 frag=0x7f6af599e398 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 15. N address=0x7f6af599e438 frag=0x7f6af599e408 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30827]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 2. N address=0x7f6af599dae8 frag=0x7f6af599dab8 size=176 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 16. N address=0x7f6af599e518 frag=0x7f6af599e4e8 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30822]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30822]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): Could you help me to fix this problem! Thanks so much! -- --------------------------- *Bui Thi Minh Yen*

2 5

Memory leak or bad setting.
by Kjeld Flarup 13 May '15

13 May '15

Hello We experienced a failure on our kamailio (4.2.1+trusty), which required a restart. May 6 07:40:41 rtpproxy01 /usr/sbin/kamailio[5467]: ERROR: <core> [msg_translator.c:2270]: generate_res_buf_from_sip_res(): out of mem Afterwards we inspected all the settings to be using default, but at a much higher level than an other older kamailio which runs much more traffic. The big difference, is that this kamailio works with rtpengine. Does that require more memory? We also observed that the free memory is constantly falling on some instances. They all started with 16MB but after 1½ day some are on 11.6 Is this normal behaviour that will find a natural level or is there something bad going on? We can also see that there are frags. Is that to be worried about, or is this natural? kamcmd pkg.stats | egrep -e 'free|frag' free: 16362760 total_frags: 17 free: 15835176 total_frags: 232 free: 15845760 total_frags: 205 free: 15829288 total_frags: 188 free: 15847456 total_frags: 181 free: 15853024 total_frags: 183 free: 15873232 total_frags: 225 free: 15858584 total_frags: 231 free: 15834592 total_frags: 205 free: 15852520 total_frags: 132 free: 15869048 total_frags: 120 free: 15824872 total_frags: 100 free: 15828448 total_frags: 113 free: 15858216 total_frags: 109 free: 15861992 total_frags: 82 free: 15871712 total_frags: 110 free: 15813824 total_frags: 109 free: 11583736 total_frags: 121 free: 11588896 total_frags: 106 free: 11580448 total_frags: 118 free: 11586312 total_frags: 134 free: 11592840 total_frags: 159 free: 11632536 total_frags: 120 free: 11582368 total_frags: 127 free: 11660104 total_frags: 97 free: 16352192 total_frags: 14 free: 16351088 total_frags: 13 free: 16341248 total_frags: 46 free: 16351184 total_frags: 19 We use 4.2.1+trusty with these modules, is it possible that a newer version has fixed some memory leak? loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "mi_rpc.so" loadmodule "acc.so" loadmodule "dispatcher.so" loadmodule "permissions.so" loadmodule "sdpops.so" loadmodule "rtpengine.so" -- Med venlig hilsen / Best regards Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef Viptel ApS, Benslehøjvej 3, DK-7470 Karup J Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk

2 3

Multi-homed Kamailio Modifies ACK
by SamyGo 13 May '15

13 May '15

Hi all, I'm having a scenario where I'm sending call to CISCO IAD2431. The call establishes with 200OK from CISCO and Kamailio sends back modified ACK. Cisco at this points gives out an error and sends 200OK again, Kamailio replies with ACK, and this cycle goes on until the call drops. Here is the error from CISCO: Failed FROM/TO Request check old_from: "Test Phone" <sip:+14432232221@192.168.1.106>;tag=as370915fc old_to: <sip:+14444812211@sip.iamip.com:5041>;tag=9FEC572E-100F new_from: "Test Phone" <sip:+14432232221@192.168.1.106>;tag=as370915fc new_to: <sip:+14444812211@192.168.1.244:5041>;tag=9FE I've #auto_aliases=no and, listen=udp:44.33.22.11:5041 listen=udp:192.168.1.244:5041 Kamailio sends INVITE through the Public IP to the CISCO gw, but decides to change the ACK header. Any advise please. Best Regards, Sammy.

2 3

kamailio slow/no response for requests on particular ports
by Karthik Srinivasan 12 May '15

12 May '15

Hi, I have encountered an issue with kamailio and am hoping someone on this email distro can help: Here's my setup and description of the issue: I am running kamailio version 3.1.4. I have the kamailio process bound to ports 5060, 5070, and 5090. all UDP. I have several client devices registering to the kamailio registrar. The issue I have encountered is this: SIP registrations to port 5070 are fine for a period of time; by fine I mean clients send SIP registration requests to kamailio; and kamailio responds promptly to the request. by period of time I mean (this could be somewhat random) that for10 hours; 12 hours; 1 hour; that kamailo has no issue processing requests. after this random time period has elapsed, kamailo isn't able to respond to sip registrations and other messages in timely manner; to the point where the clients timeout and have to resend their registration requests. at times, kamailio does respond to the requests (with a significant delay) and at other times no response is received by the client. the user experience is intermittent registration delays/failures. The same behavior is seen on port 5090. I have not encountered the issue yet on port 5060. During times when kamailio isn't able to respond timely to requests on a particular port, requests to other ports are responded to timely. for ex: if port 5070 encounters the issue; port 5060 and 5090 seem fine. meaning, I can point my client devices to 5060 or 5090 and kamailio processes the requests timely. I have studied a tcp dump on the server end (kamailio side) and noticed that the network layer shows the messages from the client to be received timely while kamailio is encountering this issue. which indicates to me that it probably isn't a network lag related issue. Something at the application layer is probably causing kamailio to not respond timely. Furthermore the issue resolves itself after a period of time; that is, kamailio begins to respond to messages timely on the problematic port. I haven't had a chance yet to determine exactly how long it takes to recover. it certainly takes some time though. at least 30 minutes; maybe more. I can also state that the load on the kamailio system is minimal. far below than what the performance metrics state it can handle. Has anyone encountered this issue where kamalio isn't responding to registration and other requests timely on a particular port but does so fine for other ports? Any help on this would be appreciated. Thanks, Karthik

2 5

Ims_charging lose all charging information when restart
by Yasin CANER 12 May '15

12 May '15

3 4

DMQ htable replication issue.
by José Seabra 12 May '15

12 May '15

Hello there, I'm using DMQ module to replicate an htable between several kamailio servers, what i'm noticing is that DMQ is sending the information from one server to another, but the htable name is not the same, for example: The original htable name is $sht(fscache=>queue:2), this htable is replicated to another server and the name (queue:2) will be replaced to some random value like this: $sht(fscache=>3c34e55ae6f9-rsf8qhhwntvw) What happens is that the other server cannot get the data replicated, because in script kamailio is looking for $sht(fscache=>queue:2) that is the original name. My kamailio version is 4.2.2, i have tested also with version 4.2.4 but I got the same behavior. This is an expected behavior or a bug? In case of expected behavior how I can configure it in order to get the value replicated from one server to another? Thank you for your help -- Cumprimentos José Seabra

3 7

Handling 407 Proxy Authentication, Elastix MT
by Darren Campbell (Primar) 12 May '15

12 May '15

Hi all Have Asterisk listening on 127.0.0.1 and aiming to route all inbound/outbound SIP via Kamailio listening on 127.0.0.1 and external interface. Inbound calls from the SIP PROVIDER work just fine. Have NAT, rtpproxy configured for successful registration and subsequent INVITEs etc. Experiencing some challenges with the outgoing INVITES, primarily authenticating the outbound INVITEs. The current situation is this: Asterisk > INVITE > Kamailio > INVITE > SIP PROVIDER SIP PROVIDER > 407 Proxy Authenticate > Kamailio > Transaction Cancelled. Asterisk then plays number unavailable message. The desired situation is more like this: Asterisk > INVITE > Kamailio > INVITE > SIP PROVIDER SIP PROVIDER > 407 Proxy Authenticate > Kamailio > Asterisk Asterisk > INVITE (with auth digest etc) > Kamailio > INVITE > SIP PROVIDER An attempted solution was made by having Kamailio authenticate using the uac module. However, ideally Kamailio should be mostly transparent and Asterisk should be handling and responding to the 407 Proxy Authentication. If there is someone in the Kamailio community that has addressed this situation before, guidance would be much appreciated. Regards, Darren

2 8

Media Proxy and STUN
by Nahum Nir 11 May '15

11 May '15

Hi All, After reading the docs I got that it is possible to configure the server so it will change the SDP so clients will send the media to the media proxy. But, what if the clients are not behind a symmetric NAT and using ICE where able to get their real IP:port? How can the server be aware to this and not change the SDP? Thanks, Nir

2 1

Kamailio authentication method
by Mathys Frédéric 10 May '15

10 May '15

Hello, In my scenario with a Kamailio server, I have a VOIP client connecting to the server which, for some reasons, cannot calculate MD5 hashes but only SHA. In this situation, would it be possible to change the authentication algorithm by either modifying Kamailio scripts or writing an external module to do that? As far as I know, the authentication response is calculated as follow (standard HTTP Digest authentication) : HA1=MD5(username:realm:password) HA2=MD5(method:digestURI) response=MD5(HA1:nonce:HA2) For that, I have to save ha1 and ha1b values in the DB with the SHA function directly (with a trigger for example), and then change the authentication method too. What is the best solution to do that? Does a module already exists? Thank you! Frederic Mathys System Integration & Validation

3 6

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