sr-users February 2021

sr-users@lists.kamailio.org

56 participants
78 discussions

unsupported sip invite request-uri format ??
by lgl_hust＠sina.com 01 Mar '21

01 Mar '21

In sip register: Request-URI: sip:ims.mnc001.mcc310.3gppnetwork.org , sip register is ok.In sip invite: Request-URI: tel:310010120073501;phone-context=ims.mnc001.mcc310.3gppnetwork.org, return 478 Unresolvable destination .I saw issue #2287 and #1173 . #2287 deals with register, and #1173 has no result.I want to know how to support such RURI in sip invite, does it need a patch in code ? If so , where and how to modified it . Should i modified kamailio.cfg such as bellows ??? I don't know how modified the kamailio.cfg . if (is_method("INVITE")) {$ru = "sip:ims.mnc008.mcc460.3gppnetwork.org"; # rewrite the "Request-URI"$du= "sip:ims.mnc008.mcc310.3gppnetwork.org"; } Thanks a lot.The following is the log:2021-02-23T03:12:08.391838+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:610]: parse_msg(): SIP Request:2021-02-23T03:12:08.391838+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:612]: parse_msg(): method:2021-02-23T03:12:08.392017+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:614]: parse_msg(): uri: tel:888555;phone-context=ims.mnc008.mcc310.3gppnetwork.org2021-02-23T03:12:08.392190+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0>2021-02-23T03:12:08.392358+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=102021-02-23T03:12:08.392556+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:171]: get_hdr_field(): [70]; uri=[tel:888555;phone-context=ims.mnc008.mcc310.3gppnetwork.org]2021-02-23T03:12:08.392732+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:174]: get_hdr_field(): to body (70)["888555"tel:888555;phone-context=ims.mnc008.mcc310.3gppnetwork.org#15#012], to tag (0)[]2021-02-23T03:12:08.392904+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:152]: get_hdr_field(): cseq : <1>2021-02-23T03:12:08.393072+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, = ; state=62021-02-23T03:12:08.393243+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, = <n/a>; state=172021-02-23T03:12:08.393419+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=52021-02-23T03:12:08.393615+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=22021-02-23T03:12:08.393814+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:500]: parse_headers(): this is the first via2021-02-23T03:12:08.393975+08:00 10-164 kamailio[238089]: DEBUG: [core/receive.c:319]: receive_msg(): --- received sip message - request - call-id: [tBfcbAf2y(a)10.45.0.101] - cseq: [1 INVITE]2021-02-23T03:12:08.394132+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=7702021-02-23T03:12:08.394289+08:00 10-164 kamailio[238089]: DEBUG: [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header2021-02-23T03:12:08.394455+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/receive.c:379]: receive_msg(): preparing to run routing scripts...2021-02-23T03:12:08.394623+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 702021-02-23T03:12:08.394782+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered2021-02-23T03:12:08.394942+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed2021-02-23T03:12:08.395104+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered2021-02-23T03:12:08.395274+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed2021-02-23T03:12:08.395439+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:318]: check_required_headers(): check_required_headers entered2021-02-23T03:12:08.395594+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:340]: check_required_headers(): check_required_headers passed2021-02-23T03:12:08.395748+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:348]: check_via1_header(): check via1 header2021-02-23T03:12:08.395905+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:506]: check_cseq_method(): check_cseq_method entered2021-02-23T03:12:08.396100+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:539]: check_cseq_method(): check_cseq_method passed2021-02-23T03:12:08.396261+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:548]: check_cseq_value(): check_cseq_value entered2021-02-23T03:12:08.396416+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:576]: check_cseq_value(): check_cseq_value passed2021-02-23T03:12:08.396570+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:585]: check_cl(): check_cl entered2021-02-23T03:12:08.396725+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:610]: check_cl(): check_cl passed2021-02-23T03:12:08.396882+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:622]: check_expires_value(): check_expires_value entered2021-02-23T03:12:08.397037+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:659]: check_expires_value(): no expires header found2021-02-23T03:12:08.397198+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:759]: check_parse_uris(): check_parse_uris entered2021-02-23T03:12:08.397352+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:763]: check_parse_uris(): parsing ruri2021-02-23T03:12:08.397521+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:777]: check_parse_uris(): looking up From header2021-02-23T03:12:08.397683+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:791]: check_parse_uris(): parsing From header2021-02-23T03:12:08.397846+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=qCfcbAf2021-02-23T03:12:08.398012+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=292021-02-23T03:12:08.398192+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:817]: check_parse_uris(): parsing From URI2021-02-23T03:12:08.398356+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:835]: check_parse_uris(): looking up To header2021-02-23T03:12:08.398510+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:857]: check_parse_uris(): check_parse_uris(): parsing To URI2021-02-23T03:12:08.398668+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity.c:902]: check_parse_uris(): check_parse_uris passed2021-02-23T03:12:08.398829+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 12021-02-23T03:12:08.398997+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:1034]: t_check_msg(): msg (0x7f648b13dd60) id=3/238089 global id=0/0 T start=0xffffffffffffffff2021-02-23T03:12:08.399156+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:497]: t_lookup_request(): start searching: hash=36710, isACK=02021-02-23T03:12:08.399309+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:455]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKrDfcbAf2yakh41vbaiuY]2021-02-23T03:12:08.399481+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:675]: t_lookup_request(): no transaction found2021-02-23T03:12:08.399669+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:1104]: t_check_msg(): msg (0x7f648b13dd60) id=3/238089 global id=3/238089 T end=(nil)2021-02-23T03:12:08.399832+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} siputils [checks.c:120]: has_totag(): no totag2021-02-23T03:12:08.399989+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/socket_info.c:630]: grep_sock_info(): checking if host==us: 0==13 && [] == [192.168.12.99]2021-02-23T03:12:08.400145+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/socket_info.c:637]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 50602021-02-23T03:12:08.400303+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1808]: str2ip6buf(): invalid name, no conversion to IP address possible2021-02-23T03:12:08.400465+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/name_alias.h:62]: grep_aliases(): matching (0::5060) vs. (0:ims.mnc008.mcc310.3gppnetwork.org:0)2021-02-23T03:12:08.400625+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/forward.c:423]: check_self(): host (0::5060) != me2021-02-23T03:12:08.400792+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:1328]: t_newtran(): msg (0x7f648b13dd60) id=3/238089 global id=3/238089 T start=(nil)2021-02-23T03:12:08.400952+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:497]: t_lookup_request(): start searching: hash=36710, isACK=02021-02-23T03:12:08.401109+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:455]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKrDfcbAf2yakh41vbaiuY]2021-02-23T03:12:08.401266+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_lookup.c:675]: t_lookup_request(): no transaction found2021-02-23T03:12:08.401420+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_hooks.c:336]: run_reqin_callbacks_internal(): trans=0x7f648403f798, callback type 1, id 0 entered2021-02-23T03:12:08.401590+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 589961c517bb910457d06701844fbbd42021-02-23T03:12:08.401768+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_funcs.c:325]: t_relay_to(): new INVITE2021-02-23T03:12:08.401934+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_reply.c:614]: _reply_light(): reply sent out. buf=0x7f648b1439c0: SIP/2.0 100 trying -..., shmem=0x7f6484043b78: SIP/2.0 100 trying -2021-02-23T03:12:08.402096+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_reply.c:625]: _reply_light(): finished2021-02-23T03:12:08.402250+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} <script>: new branch [0] to tel:888555;phone-context=ims.mnc008.mcc310.3gppnetwork.org2021-02-23T03:12:08.402406+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1740]: str2ipbuf(): invalid name, no conversion to IP address possible2021-02-23T03:12:08.402573+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1808]: str2ip6buf(): invalid name, no conversion to IP address possible2021-02-23T03:12:08.402735+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/dns_cache.c:527]: _dns_hash_find(): (_sip._udp.(10), 33), h=9562021-02-23T03:12:08.402891+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1808]: str2ip6buf(): invalid name, no conversion to IP address possible2021-02-23T03:12:08.403081+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1740]: str2ipbuf(): invalid name, no conversion to IP address possible2021-02-23T03:12:08.403245+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/dns_cache.c:521]: _dns_hash_find(): invalid name, no cache lookup possible2021-02-23T03:12:08.403415+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} [core/resolve.c:1715]: sip_hostport2su(): could not resolve hostname: ""2021-02-23T03:12:08.403577+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [ut.h:309]: uri2dst2(): failed to resolve ""2021-02-23T03:12:08.403737+08:00 10-164 kamailio[238089]: ERROR: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_fwd.c:1738]: t_forward_nonack(): failure to add branches2021-02-23T03:12:08.403898+08:00 10-164 kamailio[238089]: DEBUG: {1 1 INVITE tBfcbAf2y(a)10.45.0.101} tm [t_funcs.c:335]: t_relay_to(): t_forward_nonack returned error -478 (-478)

2 1

more help needed, - Regisraion failed.
by Daniel Siemens 01 Mar '21

01 Mar '21

I have a asterisk server on an internal network 10.123.245.18. I have a kamailio server at 10.123.244.193 On this server is nginx coturn & rtpengine. The kamailio also has an elastic IP from AWS When I connect from a raspberry phone app servered by nginx The phone reports Registration failed The log entries are START:REGISTER from sip:32897@dnsname (IP:127.0.0.1:38014) What do I need to do to get the registration to happen? ------------------------------------------------------------------ This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ------------------------------------------------------------------

2 1

kamailio debug build
by Sergey Safarov 01 Mar '21

01 Mar '21

I looked at Makefiles and can see instruction # WARNING: do not add mode=debug or mode=release anymore in the Makefile, # use make mode=debug all instead. By default Kamailio is compiled with # debugging symbols in all cases (-g) and without optimization (-O0). https://github.com/kamailio/kamailio/blob/master/src/Makefile.defs#L749-L751 I do not understand how properly build Kamailio with disabled optimization. Could you let me know how to use "mode=debug"? Sergey

2 1

Parse multiple URI
by Duarte Rocha 01 Mar '21

01 Mar '21

Greetings, I have a Kamailio proxy where i'm doing some operations over multiple History-Infos and they come in two forms : Scenario 1 -> History-Info : URI1 History Info : URI2 Scenario 2 -> History-Info : URI1 , URI2. On scenario 1 i iterate between headers using $(hdr(name)[N]). However, i can't seem to find a similar tool to apply on scenario 2. In the case Kamailio doesn't have it, what would be the best way to iterate the URIS? I was thinking of parsing them using the comma ",", is that safe? Best Regards,

2 1

kamailio+rtpengine - number of calls
by marek 27 Feb '21

27 Feb '21

hi, i'm using kamailio+rtpengine as SBC. I need info about - current number of total calls - current number of incoming calls - current number of outgoing calls what's you preferred way? (kamailio snmp, statistics module,rtpengine-ctl list numsessions,...) Marek

3 4

From EXT parameter
by Ilie Soltanici 26 Feb '21

26 Feb '21

Hello, Having the following From header: *<From=sip:+123456789;ext=10@sip.pstnhub.microsoft.com:5061;user=phone>* How can I extract the only extension from it (ext=10)? Is there any variable already for that or I have to use select function? ( {s.select,index,separator} ) Thank you

3 2

webrtc setup
by Daniel Siemens 25 Feb '21

25 Feb '21

I have an asterisk server on an internal network 10.123.245.18. I have a kamailio server at 10.123.244.193 On this server is nginx coturn & rtpengine. The kamailio also has an elastic IP from AWS When I connect from a raspberry phone app served by nginx The phone reports Registration failed The log entries are START:REGISTER from sip:32897@dnsname (IP:127.0.0.1:38014) What do I need to do to get the registration to happen? In the client side using Raspberry phone is says web socket error. Thanks. ------------------------------------------------------------------ This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ------------------------------------------------------------------

2 2

Re: [SR-Users] No ACK from MS Teams
by Phillman25 Kyriacou 25 Feb '21

25 Feb '21

Hi Guys Thanks for all your recommendations. I did the change and rr headers only show the fqdn of Kamailio as you can see below in the 200 OK sent back to MS Teams, however still the same issue no ACK. |||||||||||||||||||| ==================== tag: snd pid: 31232 process: 6 time: 1613047849.768857 date: Thu Feb 11 14:50:49 2021 proto: tls ipv4 srcip: 82.102.42.58 srcport: 5061 dstip: 52.114.132.46 dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bK4f5c9b66 Record-Route: <sip:sbc.intelligentsupport.eu:5060 ;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sbc.intelligentsupport.eu:5061 ;transport=tls;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sip-du-a-us.pstnhub.microsoft.com:5061;transport=tls;lr> From: Phillip Kyriacou<sip:+35722010058@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=dcea3c9546914ff8826afca13260da1c To: <sip:+35796552237@sbc.intelligentsupport.eu:5061 ;user=phone>;tag=as63d965d3 Call-ID: 43f0f0be2fa05b408c81736dbe392aef CSeq: 1 INVITE Server: MediaGW V1.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:+35796552237@82.102.42.52:5060> Content-Type: application/sdp Require: timer Content-Length: 339 v=0 o=root 601931926 601931926 IN IP4 82.102.42.52 s=ASTERISK c=IN IP4 82.102.42.52 t=0 0 m=audio 16360 RTP/SAVP 0 8 101 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:IyrJsjVV0w5ORJQ3OJB0r8iyRZU+1lMjg4i9vzC2 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=maxptime:150 a=sendrecv |||||||||||||||||||| ====================

6 11

Kamailio 5.4.4 extremely slow carrierroute preloading
by sr.maillists＠gmail.com 24 Feb '21

24 Feb '21

Hi Maillist! Does someone have experience with kamailio 5.4.4 and carrierroutes loading? We have about 50'000 carrierroutes, kamailio 4.3.6 loads them in about 10 seconds. Kamailio 5.4.4 needs about 10 minutes (!) to load the routes if I set the parameter modparam("carrierroute", "fetch_rows", 50000); Withous this parameter, v5.4.4 loads only 2000. - Virtual Machine is an ubuntu 20.04 with all current updates - Kamailio is installed from source - The database is postgres on a separate host I tested this with the same database and same VM, I only recompiled kamailio and made neccessary changes in the kamailio.cfg. In 4.3.6 I disabled the modules tls and jsonrpcs and added the module mi_fifo.so instead. Any Idea where to search? Did I miss something in the update-procedure? Regards Stefan

2 5

logging rd/wr queue usage?
by Andrew Chen 24 Feb '21

24 Feb '21

Hi all, I was wondering if there's a way to log rd/wr queue usage when processing a new incoming message? I am currently running 5.2.5 but couldn't find any variables in core cookbook or psudovar page. Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

3 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 February 2021