sr-users July 2021

sr-users@lists.kamailio.org

54 participants
53 discussions

Guidance tracking down "qm_free(): BUG: freeing already freed pointer"
by Anthony Joseph Messina 29 Jul '21

29 Jul '21

I'm seeking guidance on how to track down "qm_free(): BUG: freeing already freed pointer" which occurs only on branched calls. These errors don't crash so I don't get any core dumps. The different log entries below are the result of me selectively disabling sections of the script that apply in branch route, all to no avail. I'm running Kamailio on the current tip of the 5.5 branch (1f9f6fff6e). I'm reviewing https://www.kamailio.org/wiki/tutorials/troubleshooting/memory in the meantime as a place to start. version: kamailio 5.5.1-5.git1f9f6fff6e.fc34 (x86_64/linux) 7abebb flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f04b8f47e90), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f04b8f06c70), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f08e8f9cf80), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f2afafa60d8), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/sdp/sdp.c: init_p_payload_attr(183) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f2afae2a018), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f2afae431e8), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f2afafa3900), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f5fd4044ef0), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7ffbb2d2e2f0), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f6d1a50b1d8), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc19c165c70), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc19c17adb8), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc19c125790), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4d969c9d48), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc29bdca3d0), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc2c2eccc80), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fc2c2ec52c0), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f910c04e240), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fa351286b18), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fa3512a7ae8), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fa0777d9e70), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fa0777d7a80), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4f2c92cf20), called from core: core/data_lump.c: free_lump(470), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4f2c8afa00), called from core: core/data_lump.c: free_lump(470), first free textops: textops.c: add_hf_helper(3474) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4f2c92aa48), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fe55825eb30), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/sdp/sdp.c: init_p_payload_attr(183) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f6526db8378), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fcd9b465980), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/hf.c: free_hdr_field_lst(217) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7ff7ca92ff60), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f978a2dc938), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f978a2b7eb8), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fa1556c1610), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fd81dfbba78), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fb2750d9988), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fb2750e1b28), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/parse_addr_spec.c: free_to_params(895) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f32f7b45d30), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/hf.c: free_hdr_field_lst(217) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f35849e1940), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/hf.c: free_hdr_field_lst(217) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7fd3a2c04280), called from core: core/parser/sdp/sdp.c: free_sdp(825), first free core: core/parser/msg_parser.c: reset_ua(994) - ignoring CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f5de857a040), called from core: core/parser/msg_parser.c: reset_instance(916), first free core: core/parser/hf.c: free_hdr_field_lst(217) - ignoring -- Anthony - https://messinet.com CCED 8BFB 88D9 18F6 9F68 93DC 45C4 A8CE A64E 88E3

2 6

BYE not accepted by MS TEAMS
by João Vitor Arruda 29 Jul '21

29 Jul '21

Hello all, I recently built an SBC to integrate Kamailio with MS Teams following Henning Westerholt blob post and all the other awesome tips I was able to find here in the list. Everything is working great. The only missing piece I would like some thoughts on is about why MS Teams is not accepting the BYE sent from Kamailio. It eventually replies with "504 Server Time-out" The below trace shows the entire call. |||||||||||||||||||| ==================== tag: rcv pid: 3381 process: 63 time: 1627070235.086307 date: Fri Jul 23 19:57:15 2021 proto: tls ipv4 srcip: 52.114.76.76 srcport: 4672 dstip: SBC_IP_ADDR dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ INVITE sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone;transport=tls SIP/2.0 FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 TO: <sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone> CSEQ: 1 INVITE CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e MAX-FORWARDS: 70 VIA: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bK60895c91 RECORD-ROUTE: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> CONTACT: <sip:api-du-b-usea2.pstnhub.microsoft.com:443 ;x-i=a82f1d71-4e21-42a8-8389-2ae26e54610f;x-c=c9b2aa4f658f5788aa7090bef0f5e35e/d/8/b14037a741dd46a79c74dce15912782c> CONTENT-LENGTH: 1103 MIN-SE: 300 SUPPORTED: timer USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.6.15.17 i.EUNO.0 CONTENT-TYPE: application/sdp ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY PRIVACY: id SESSION-EXPIRES: 3600 v=0 o=- 599625 0 IN IP4 127.0.0.1 s=session c=IN IP4 52.113.58.181 b=CT:10000000 t=0 0 m=audio 50122 RTP/SAVP 104 9 103 111 18 0 8 97 101 13 118 c=IN IP4 52.113.58.181 a=rtcp:50123 a=ice-ufrag:fTy/ a=ice-pwd:tQKGN0Szi7Q/vTdf6SiXUSpj a=rtcp-mux a=candidate:1 1 UDP 2130706431 52.113.58.181 50122 typ srflx raddr 10.0.33.230 rport 50122 a=candidate:1 2 UDP 2130705918 52.113.58.181 50123 typ srflx raddr 10.0.33.230 rport 50123 a=candidate:2 1 tcp-act 2121006078 52.113.58.181 49152 typ srflx raddr 10.0.33.230 rport 49152 a=candidate:2 2 tcp-act 2121006078 52.113.58.181 49152 typ srflx raddr 10.0.33.230 rport 49152 a=label:main-audio a=mid:1 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:PC00Mgk39GjTYJ+mUSNQg++TU6zJKar4VYDj4/ET|2^31 a=sendrecv a=rtpmap:104 SILK/16000 a=rtpmap:9 G722/8000 a=rtpmap:103 SILK/8000 a=rtpmap:111 SIREN/16000 a=fmtp:111 bitrate=16000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:97 RED/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:13 CN/8000 a=rtpmap:118 CN/16000 a=ptime:20 |||||||||||||||||||| ==================== tag: snd pid: 3381 process: 63 time: 1627070235.089106 date: Fri Jul 23 19:57:15 2021 proto: tls ipv4 srcip: SBC_IP_ADDR srcport: 5061 dstip: 52.114.76.76 dstport: 4672 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 100 trying -- your call is important to us FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 TO: <sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone> CSEQ: 1 INVITE CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e VIA: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bK60895c91;rport=4672 Server: kamailio (5.3.7 (x86_64/linux)) Content-Length: 0 |||||||||||||||||||| ==================== tag: snd pid: 3291 process: 18 time: 1627070235.111825 date: Fri Jul 23 19:57:15 2021 proto: tls ipv4 srcip: SBC_IP_ADDR srcport: 5061 dstip: 52.114.76.76 dstport: 4672 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 180 Ringing FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 t:<sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone>;tag=e55N8paBUgZac CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e CSEQ: 1 INVITE m:<sip:+5515XXXXXXXXX@192.168.1.254:5060;transport=udp> User-Agent:FreeSWITCH-mod_sofia/1.10.3-release~64bit Accept:application/sdp Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY k:path,replaces u:talk,hold,conference,refer l:0 Via: SIP/2.0/TLS 52.114.76.76:5061;rport=4672;branch=z9hG4bK60895c91 Record-Route: <sip:192.168.1.253:5060 ;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on>,<sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on> Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> P-SR-XBranch: z9hG4bKe7d4.5ae277881edb9c04a7ac65af016e582e.0 |||||||||||||||||||| ==================== tag: snd pid: 3298 process: 21 time: 1627070245.043621 date: Fri Jul 23 19:57:25 2021 proto: tls ipv4 srcip: SBC_IP_ADDR srcport: 5061 dstip: 52.114.76.76 dstport: 4672 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 183 Session Progress FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 t:<sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone>;tag=e55N8paBUgZac CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e CSEQ: 1 INVITE m:<sip:+5515XXXXXXXXX@192.168.1.254:5060;transport=udp> User-Agent:FreeSWITCH-mod_sofia/1.10.3-release~64bit Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY k:path,replaces u:talk,hold,conference,refer c:application/sdp Content-Disposition:session l:323 Via: SIP/2.0/TLS 52.114.76.76:5061;rport=4672;branch=z9hG4bK60895c91 Record-Route: <sip:192.168.1.253:5060 ;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on>,<sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on> Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> P-SR-XBranch: z9hG4bKe7d4.5ae277881edb9c04a7ac65af016e582e.0 v=0 o=FreeSWITCH 1627045233 1627045234 IN IP4 SBC_IP_ADDR s=FreeSWITCH c=IN IP4 SBC_IP_ADDR t=0 0 m=audio 49692 RTP/SAVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:eMGqj0jubamtvLsI/E/YSj8UqNKgUB5DTHGWc7PY a=nortpproxy:yes |||||||||||||||||||| ==================== tag: snd pid: 3293 process: 19 time: 1627070255.938770 date: Fri Jul 23 19:57:35 2021 proto: tls ipv4 srcip: SBC_IP_ADDR srcport: 5061 dstip: 52.114.76.76 dstport: 4672 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 200 OK FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 t:<sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone>;tag=e55N8paBUgZac CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e CSEQ: 1 INVITE m:<sip:+5515XXXXXXXXX@192.168.1.254:5060;transport=udp> User-Agent:FreeSWITCH-mod_sofia/1.10.3-release~64bit Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY k:path,replaces u:talk,hold,conference,refer c:application/sdp Content-Disposition:session l:323 Via: SIP/2.0/TLS 52.114.76.76:5061;rport=4672;branch=z9hG4bK60895c91 Record-Route: <sip:192.168.1.253:5060 ;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on>,<sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on> Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> P-SR-XBranch: z9hG4bKe7d4.5ae277881edb9c04a7ac65af016e582e.0 v=0 o=FreeSWITCH 1627045233 1627045234 IN IP4 SBC_IP_ADDR s=FreeSWITCH c=IN IP4 SBC_IP_ADDR t=0 0 m=audio 49692 RTP/SAVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:eMGqj0jubamtvLsI/E/YSj8UqNKgUB5DTHGWc7PY a=nortpproxy:yes |||||||||||||||||||| ==================== tag: rcv pid: 3370 process: 57 time: 1627070255.957735 date: Fri Jul 23 19:57:35 2021 proto: tls ipv4 srcip: 52.114.76.76 srcport: 4672 dstip: SBC_IP_ADDR dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ ACK sip:+5515XXXXXXXXX@192.168.1.254:5060;transport=udp SIP/2.0 FROM: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 TO: <sip:+5515XXXXXXXXX@SBC-FQDN:5061>;user=phone;tag=e55N8paBUgZac CSEQ: 1 ACK CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e MAX-FORWARDS: 70 VIA: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bKe3747d68 CONTACT: <sip:api-du-b-usea2.pstnhub.microsoft.com:443 ;x-i=a82f1d71-4e21-42a8-8389-2ae26e54610f;x-c=c9b2aa4f658f5788aa7090bef0f5e35e/d/8/b14037a741dd46a79c74dce15912782c> CONTENT-LENGTH: 0 USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.6.15.17 i.EUNO.0 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY Route: <sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on> Route: <sip:192.168.1.253:5060 ;r2=on;ftag=bafa0f5a573749a7b494917c0309f544;lr=on> P-SR-XUID: atpsh-60fb1b5d-d35-1 |||||||||||||||||||| ==================== tag: snd pid: 3302 process: 23 time: 1627070275.228363 date: Fri Jul 23 19:57:55 2021 proto: tls ipv4 srcip: SBC_IP_ADDR srcport: 5061 dstip: 52.114.75.24 dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ BYE sip:52.114.76.76:4672;x-i=a82f1d71-4e21-42a8-8389-2ae26e54610f;x-c=c9b2aa4f658f5788aa7090bef0f5e35e/d/8/b14037a741dd46a79c74dce15912782c SIP/2.0 Record-Route: <sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=e55N8paBUgZac;lr=on> Record-Route: <sip:192.168.1.253:5060;r2=on;ftag=e55N8paBUgZac;lr=on> Via: SIP/2.0/TLS SBC_IP_ADDR:5061;branch=z9hG4bK92fc.fcb147cf8e5e6e6e960d0f2401ad6383.0 v:SIP/2.0/UDP 192.168.1.254;received=192.168.1.254;rport=5060;branch=z9hG4bKgvXrQrcNjNj3m f:<sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone>;tag=e55N8paBUgZac t:"Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 i:c9b2aa4f658f5788aa7090bef0f5e35e CSeq:38981345 BYE User-Agent:FreeSWITCH-mod_sofia/1.10.3-release~64bit Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY k:path,replaces Reason:Q.850;cause=16;text="NORMAL_CLEARING" Max-Forwards: 64 l:0 Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> P-SR-XUID: atpsh-60fb1b5d-d35-1 |||||||||||||||||||| ==================== tag: rcv pid: 3385 process: 65 time: 1627070300.423499 date: Fri Jul 23 19:58:20 2021 proto: tls ipv4 srcip: 52.114.75.24 srcport: 5061 dstip: SBC_IP_ADDR dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 504 Server Time-out FROM: <sip:+5515XXXXXXXXX@SBC-FQDN:5061;user=phone>;tag=e55N8paBUgZac TO: "Last, First Name"<sip:+8979994;ext=01180@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=bafa0f5a573749a7b494917c0309f544 CSEQ: 38981345 BYE CALL-ID: c9b2aa4f658f5788aa7090bef0f5e35e VIA: SIP/2.0/TLS SBC_IP_ADDR:5061;branch=z9hG4bK92fc.fcb147cf8e5e6e6e960d0f2401ad6383.0 CONTENT-LENGTH: 0 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY SERVER: Microsoft.PSTNHub.SIPProxy v.2021.6.15.17 i.EUWE.3 Via: SIP/2.0/UDP 192.168.1.254;received=192.168.1.254;rport=5060;branch=z9hG4bKgvXrQrcNjNj3m Record-Route: <sip:SBC-FQDN:5061;transport=tls;r2=on;ftag=e55N8paBUgZac;lr=on>,<sip:192.168.1.253:5060 ;r2=on;ftag=e55N8paBUgZac;lr=on> P-SR-XBranch: z9hG4bK92fc.fcb147cf8e5e6e6e960d0f2401ad6383.0

2 2

Accessing Transformations in KEMI
by Ben Kaufman 28 Jul '21

28 Jul '21

Sorry to bother on this, but is it possible to access Kamailio transformations in KEMI, and if so, how? In Kamailio's native scripting language I could do: $var(pai_user) = $(hdr(P-Asserted-Identity){tobody.user}); In KEMI, I can easily get the full header like this: KSR.hdr.get("P-Asserted-Identity") But I don't see how to access the transformations. Am I missing it? Ben Kaufman

3 6

Password for pi_framework.xml - Xhttp_pi module
by Abdirahman Osman 27 Jul '21

27 Jul '21

Hello everyone, In the xhttp_pi file of pi_framework.xml,is there a way I can pass the password to the xhttp_pi module as a pre-processing define? <db_url id="postgres">postgres://kamailiorw:kamailiorw@localhost /kamailiorw</db_url> Thank you! Abdirahman

2 1

Info: Kamailio World Online - Sep 1-2, 2021 - Celebrating 20 Years Of Development
by Daniel-Constantin Mierla 26 Jul '21

26 Jul '21

Hello, given the current situation across the world, no physical Kamailio World Conference is planned in 2021. However, this year the project celebrates 20 years of development -- according to commit history, the first one was done on the 3rd of September, 2021: > ❯ git log --reverse > commit 512dcd9838f5aeb0bfccd02cfc156067b7f02b71 > Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> > Date: Mon Sep 3 21:27:11 2001 +0000 > Initial revision To mark this notable milestone, we are going to organize an online event during Sep 1-2, 2021, similar to the one from 2020 -- the website for the event is available at: * https://www.kamailioworld.com/k09-online/ Mark the date in your calendar, more details about the content of the event will be published in the near future! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

New user checking on SIP proxying use case
by Nick Hurlburt 22 Jul '21

22 Jul '21

Hello all, My name is Nick Hurlburt, and work with a nonprofit tech organization that provides a software platform for child helplines around the world. I am a new user to Kamailio, and I'm interested in figuring out if my use case is appropriate, getting some tips on how to go about it, and possibly enlisting some expert help. Our service is built on top of Twilio, but we are working in some countries where Twilio doesn't have phone numbers. So in those areas, we are working with local telecoms on ways to integrate using a SIP connection. In one particular example, the telecom company can send SIP INVITEs but can only address them to a static IP. However, Twilio needs to receive the invite addressed to a fully-qualified domain name (eg, example-setup.sip.twilio.com). The idea arose to use Kamailio as a proxy to accept the static IP-addressed request and then rewrite the request to pass it along to a domain name. Then once the connection is established between the two endpoints, the media can flow directly between them. I have a software engineering background but still coming up to speed when it comes to VoIP technology. I'd be interested in: - does this sound like a good use case for Kamailio? - is there any specific documentation you could point me to for this use case? (I have been looking at the Kamailio documentation, but a quick pointer could save a lot of time in digging through it) - if anyone from the community would be open to helping us develop a prototype/proof-of-concept instance of this, especially if you're open to contributing to a nonprofit on a volunteer or discounted rate, I'd love to talk more Thank you, Nick

4 4

Kamailio/rtpengine not populating mos avp stats?
by Anthony Joseph Messina 22 Jul '21

22 Jul '21

I'm using Kamailio compiled from the current 5.5 tip (1f9f6fff6e), and rtpengine compiled from the current master (6e160da4). While rtpengine is working quite well, within the past month or so, I've noticed that Kamailio isn't populating the mos* related AVPs. I see continued upstream rtpengine work stream handling, etc. -- should I wait or try to debug? Thanks -A -- Anthony - https://messinet.com CCED 8BFB 88D9 18F6 9F68 93DC 45C4 A8CE A64E 88E3

3 6

How to get Stir/Shaken certificates
by ryan embgrets 22 Jul '21

22 Jul '21

Greetings. Does someone know where one can get stir/shaken certificates? Are they same as letsencrypt or do I need to obtain them from some other authority. If someone could provide me with a link to that authority it will be very helpful. Thanks again for your help and time. Ryan

4 5

Question about MS Teams integration
by Володимир Іванець 22 Jul '21

22 Jul '21

Hello all! Sorry, this is not a direct Kamailio question. I would like to ask for some help from those who already did this. I'm trying to integrate my testKamailio installation with MS Teams. I added the "mydomain.com" to the Domains section (I kept the " mydomain.onmicrosoft.com"). When I tried to create SBC with a " kamailio-dev2.mydomain.com" FQDN I got this error message: We* can't use the "kamailio-dev2.mydomain.com <http://kamailio-dev2.mydomain.com>" domain as it hasn't be set up in the organization. Try again. If you continue to have problems, contact Microsoft customer support.* There were no issues creating a dummy SBC with a " kamailio-dev2.mydomain.onmicrosoft.com" FQDN. Does anyone know how to set up a domain in the organization from MS perspective? Thank you very much! Regards, Volodymyr Ivanets.

4 9

serial forking kamailio - twilio
by Filippo Graziola 21 Jul '21

21 Jul '21

Hi all, I have a question for my kamailio configuration which works like this: - INVITE arrives to kamailio - HTTP async request to API endpoint - Resume, use of rtjson module for parallel forking and loop to kamailio itself - One of the invite is "transformed" in serial forking with rtjson module and it is sent with a delay to TWILIO SIP Domain (landline/mobile phone numbers) Twilio is giving me some troubles because it answers with a 200 OK but the call it is still in establishing/ringing on the "landline" side and as expected when reaching the timeout (no answer from phone number on TWILIO side) kamailio is receiving a BYE. Now the question, how to handle next number to call through Twilio? I was thinking of using rtjson_next_route() when handling the in-dialog BYE but as it is not a failure route so it does not work, or I'm doing it wrong. Thanks in advance for any help/hint. Filippo

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2021