- sr-users - kamailio.org

DISABLE SDP MEDIA STREAMS
by Patrick Karton 29 May '23

29 May '23

Hello kamailio community, i know its an unusual query but i would like to know if there is a cleaner/proper.right way to disable some (or all) media streams in SDP. i have come with a solution by sdpops module with subst_body function like this. route[SDP_DISABLE_UNAUTHORIZED_MEDIA]{ # disable text,media and video media streams subst_body('#^m=(video|text|audio)[ ]+[0-9/]+(.*)$#m=\1 0 \2#ig'); # update originator ip address subst_body('#^o=([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)$#o=\1 \2 \3 \4 \5 7.7.7.7#ig'); # 1 2 2 4 5 6 # name sid snumber network net-type addr # update connection ip address subst_body('#^c=([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)$#c=\1 \2 7.7.7.7#ig'); # 1 2 3 # network net-type addr #remove all media attributes sdp_remove_line_by_prefix("a=fmtp"); sdp_remove_line_by_prefix("a=X-"); sdp_remove_line_by_prefix("a=rtcp"); sdp_remove_line_by_prefix("a=ssrc"); sdp_remove_line_by_prefix("a=sendrecv"); sdp_remove_line_by_prefix("a=sendonly"); sdp_remove_line_by_prefix("a=recvonly"); sdp_remove_line_by_prefix("a=inactive"); sdp_remove_line_by_prefix("b="); } is it the right way to do it. if not can someone provide me an alternative solution. Thanks :)

3 2

Re: [sr-dev] Troubles with outbound kamailio call to other server
by Henning Westerholt 26 May '23

26 May '23

Hello (added sr-users, as its probably more a usage question). The SIP message (the BYE) cannot be parsed apparently. From the log it looks that there is an invalid character in the first line. Do a network trace to analyse the packets that its actually send and try to get some more clues from that. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com > -----Original Message----- > From: aaron.soto(a)dialapplet.com <aaron.soto(a)dialapplet.com> > Sent: Freitag, 26. Mai 2023 10:44 > To: sr-dev(a)lists.kamailio.org > Subject: [sr-dev] Troubles with outbound kamailio call to other server > > Hi everyone, > I'm having the following errors in kamailio when i try to make an outbound call to > other server, I don't know what does it mean, if some one can help me > > 11(25) ERROR: <core> [core/receive.c:310]: receive_msg(): core parsing of SIP > message failed (XX.XX.XX.XX.5060/1) > 13(27) ERROR: <core> [core/parser/parse_fline.c:271]: parse_first_line(): > parse_first_line: bad message (offset: 65) > 13(27) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: > parse_msg: message=<BY > sip:asterisk@10.0.5.158:4080;alias=10.0.5.158~44730~1 SIP/2.0 > Via: SIP/2.0/UDP 84.127.226.15:5060;branch=z9hG4bK3bc90b47;rport > Route: <sip:34.252.151.179:4060;r2=on;lr;ftag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw; > nat=yes>,<sip:10.0.5.40:4070;r2=on;lr;ftag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw; > nat=yes> > Max-Forwards: 70 > From: <sip:692598435@kamailio.voip.svc.cluster.local>;tag=as6f32aa26 > To: <sip:963441038@192.168.123.66:4060>;tag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a > Call-ID: b9a49c52-7829-4cdf-a88c-0064cc5bb438 > CSeq: 102 BYE > User-Agent: Asterisk PBX 11.2-cert3 > X-Asterisk-HangupCause: No user responding > X-Asterisk-HangupCauseCode: 18 > Content-Length: 0 > > > > _______________________________________________ > Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev- > leave(a)lists.kamailio.org

1 0

Consistent huntable responses based on failure_route question
by John Hardiman 25 May '23

25 May '23

Hi Kamailio list, I hope you are all well? I am looking for some assistance on a specific error I am trying to work around. Kamailio 5.5.3 - Ubuntu 20.04 Kemi Python script (but I think this is more default failure_route behaviour) Dispatcher module which hunts to a group of FreeSWITCH that I have configured to send 503 responses on. My scenario is fairly simple, I am trying to respond back to a carrier for huntable responses (503 specifically) by calling a failure route below: def ksr_failure_manage(self, msg): if KSR.tm.t_any_timeout()>0 : self.ksr_send_reply_clear_rtpengine(msg, 503, "Timeout to destination") KSR.err("Timeout to Invite for %s from IP %s" % (KSR.pv.get("$ci"),KSR.pv.get("$si"))) return 1 else: self.ksr_send_reply_clear_rtpengine(msg, 503, "Unknown error failover to next node") KSR.err("Failed but not timeout for %s from IP %s" % (KSR.pv.get("$ci"),KSR.pv.get("$si"))) return 1 This works and a 503 with the correct message is sent if the invite doesn't get a response after 2 seconds. (My specific test case here) # Timers for call setup 2 minutes for any 1xx provisional response received # If no invite response received in 2 seconds end the call as per failure route. KSR.tm.t_set_fr(120000, 2000) self.ksr_route_relay(msg) KSR.tm.t_on_failure("ksr_failure_manage") return -255 The issue is after a few more milliseconds after my initial 503 a 408 is sent. Also after the failover if the carrier tries the same Kamailio again it gets a 500 rather than a 408. 408: [cid:image001.png@01D98F15.CD07DCB0] 500: [cid:image002.png@01D98F15.CD07DCB0] My steps to get around this have been to change the default tm code to 503 below, but this has not changed the default response and the above behaviour unfortunately: # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # setting default reason code and response for general errors to allow failover. modparam("tm", "default_code", 503) modparam("tm", "default_reason", "Unknown reason try next node") My question is: How can I make sure my failure route is the final response here. Or if I cannot make sure of this, how can I change the default mapped response to be a consistent SIP response (503 specifically) Many thanks in advance as I am scratching my head on this one a bit. John.

2 2

Override listen advertise address
by Calvin E. 25 May '23

25 May '23

Using 5.6.x, a scenario designed for a public IP now needs to support life in the cloud behind NAT. I'd like to avoid having two listeners to separate on-net from off-net traffic. In a HA scenario, it would be nice to have only one floating IP. Is it possible to use the same local address and port for external/public and internal/private traffic? Should set_advertised_address() override the listen advertise address? Initial testing did not produce the expected result. I want to make sure I'm following a sane pattern before going down a rabbit hole. The idea is to toggle the advertised address by checking if the sender or recipient is rfc1918(). For the dispatcher module, is it possible to use socket names like below? In testing it appeared that only one of the two names was valid. listen=udp:10.0.0.10:5060 name "onnet" listen=udp:10.0.0.10:5060 advertise 11.11.11.11:5060 name "offnet"

3 4

lost module: best practice handling delay caused by held / lis procedure?
by Benoit Panizzon 25 May '23

25 May '23

Hi gang In 2024, Switzerland will start using NG112 (NG911) procedures to transmit the caller location via Geolocation URL via LIS Server to a PSAP. So time to start testing this on my devel plattform. Kamailio ships with the lost module which looks promising. In short, the Procedure is as follows: Customer calls emergency number. Kamailio performs a http request to our inhouse HELD server with the identification of the calling customer. HELD server looks up the location of the caller and pushes a HELD XML object to the Swiss LIS Server, which then is queried by the emergency PSAP receiving the call. LIS server return and URL. HELD server returns the URL to Kamailio. Kamailio adds Geolocation Header with that URL and relays the call. This takes some time and as the call is not yet being relayed while waiting for the held request to complete, there is no 100 trying being sent and the emergency call is bound to time out. So, shall I call t_reply("100","Performing HELD lkup") before calling the lost module? Or is there a better way? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 7

cancel at first call after startup kamailio not relay
by Giuseppe Pandolfi 23 May '23

23 May '23

Hi, I have a problem with kamailio v 5.6.1 on mips architecture: version: kamailio 5.6.1 (mips/linux) flags: USE_TCP, USE_TLS, 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-NOSMP, USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES 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. id: unknown compiled on 14:22:18 Apr 27 2023 Using default script for make a call from sip ua to PSTN system (#!define WITH_PSTN), the cancel sent for the first call after start kamailio doesn't relay to PSTN system and I have the trace error beelow: 2(3203) BUG: {1 27018 CANCEL 0tBgb95Z.0eE5VVrAkoP06nvunIknKNz} tm [t_cancel.c:318]: cancel_branch(): local_cancel buffer=(nil) != BUSY_BUFFER (trying to continue) 12(3203) ERROR: {1 27018 CANCEL 0tBgb95Z.0eE5VVrAkoP06nvunIknKNz} tm [t_fwd.c:1434]: e2e_cancel(): cancel error the next calls works fine. Does anyone have any suggestions? Beelow trace at debug level: 37(3695) INFO: <core> [core/cfg/cfg_ctx.c:602]: cfg_set_now(): core.debug has been changed to 3 37(3695) DEBUG: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 23 12(3670) DEBUG: <core> [core/parser/parse_fline.c:250]: parse_first_line(): first line type 1 (request) flags 1 12(3670) DEBUG: <core> [core/parser/msg_parser.c:677]: parse_msg(): SIP Request: 12(3670) DEBUG: <core> [core/parser/msg_parser.c:679]: parse_msg(): method: <CANCEL> 12(3670) DEBUG: <core> [core/parser/msg_parser.c:681]: parse_msg(): uri: <sip:100@192.168.2.238:5060> 12(3670) DEBUG: <core> [core/parser/msg_parser.c:683]: parse_msg(): version: <SIP/2.0> 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Via] type 1 12(3670) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 12(3670) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjLBcUXshEKW2s9T0en9czTYAsciW1vV-W>; state=16 12(3670) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 12(3670) DEBUG: <core> [core/parser/msg_parser.c:555]: parse_headers(): Via found, flags=2 12(3670) DEBUG: <core> [core/parser/msg_parser.c:557]: parse_headers(): this is the first via 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [From] type 4 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [To] type 3 12(3670) DEBUG: <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=9 12(3670) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [23]; uri=[sip:100@192.168.2.238] 12(3670) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (23)[sip:100@192.168.2.238 ], to tag (0)[] 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Call-ID] type 6 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [CSeq] type 5 12(3670) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <17038> <CANCEL> 12(3670) DEBUG: <core> [core/receive.c:394]: receive_msg(): --- received sip message - request - call-id: [CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU] - cseq: [17038 CANCEL] 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [User-Agent] type 28 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Content-Length] type 12 12(3670) DEBUG: <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=0 12(3670) DEBUG: <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:261]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:471]: receive_msg(): preparing to run routing scripts... 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:318]: check_required_headers(): check_required_headers entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:340]: check_required_headers(): check_required_headers passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:348]: check_via1_header(): check via1 header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:506]: check_cseq_method(): check_cseq_method entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:539]: check_cseq_method(): check_cseq_method passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:548]: check_cseq_value(): check_cseq_value entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:576]: check_cseq_value(): check_cseq_value passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:585]: check_cl(): check_cl entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:610]: check_cl(): check_cl passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:622]: check_expires_value(): check_expires_value entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:659]: check_expires_value(): no expires header found 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:758]: check_parse_uris(): check_parse_uris entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:762]: check_parse_uris(): parsing ruri 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:776]: check_parse_uris(): looking up From header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=Jjj1QBeRxydZ5rq.-xKCfcJZhlPANj9N 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=29 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:791]: check_parse_uris(): looking up To header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:837]: check_parse_uris(): check_parse_uris passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:727]: t_lookupOriginalT(): searching on hash entry 10182 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:440]: matching_3261(): RFC3261 transaction matched, tid=PjLBcUXshEKW2s9T0en9czTYAsciW1vV-W 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:823]: t_lookupOriginalT(): canceled transaction found (0x729bff78)! 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:826]: t_lookupOriginalT(): found - lookup completed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [tm.c:1232]: ki_t_lookup_cancel_flags(): lookup_original: t_lookupOriginalT returned: 0x729bff78 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:1348]: t_newtran(): msg (0x771181ec) id=1/3670 global id=0/0 T start=0xffffffff 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:498]: t_lookup_request(): start searching: hash=10182, isACK=0 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:456]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKPjLBcUXshEKW2s9T0en9czTYAsciW1vV-W] 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:675]: t_lookup_request(): no transaction found 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/crypto/md5utils.c:67]: MD5StringArray(): MD5 calculated: dd71ad9d7511b02a5fc83c3c70ce307f 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:727]: t_lookupOriginalT(): searching on hash entry 10182 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:432]: matching_3261(): matched skip method - s:0x2 t:0x2 m:0x2 - continue searching 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:440]: matching_3261(): RFC3261 transaction matched, tid=PjLBcUXshEKW2s9T0en9czTYAsciW1vV-W 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:823]: t_lookupOriginalT(): canceled transaction found (0x729bff78)! 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:826]: t_lookupOriginalT(): found - lookup completed 12(3670) BUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_cancel.c:318]: cancel_branch(): local_cancel buffer=(nil) != BUSY_BUFFER (trying to continue) 12(3670) ERROR: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_fwd.c:1434]: e2e_cancel(): cancel error 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:1763]: cleanup_uac_timers(): RETR/FR timers reset 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:638]: _reply_light(): reply sent out - buf=0x77101e68: SIP/2.0 500 cancel e... shmem=0x729c5b60: SIP/2.0 500 cancel e 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_funcs.c:120]: put_on_wait(): put T [0x729c36d8] on wait 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:648]: _reply_light(): finished 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_funcs.c:373]: t_relay_to(): new transaction forwarded 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:529]: receive_msg(): request-route executed in: 9868 usec 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:628]: receive_msg(): cleaning up 34(3692) DEBUG: tm [timer.c:642]: wait_handler(): finished transaction: 0x729c36d8 (p:0x72866768/n:0x729bff78) 34(3692) DEBUG: tm [h_table.c:132]: free_cell_helper(): freeing transaction 0x729c36d8 from timer.c:650

1 0

mk_proxy(): could not resolve hostname
by ajosebar＠gmail.com 23 May '23

23 May '23

I have Kamailio 5.6 on Debian 11. I need to use the function forward within a routing block in my configuration file: forward("udp:192.168.28.51:5060"); But when I start the kamailio service I got: CRITICAL: [core/proxy.c:264]: mk_proxy(): could not resolve hostname: "udp:192.168.28.51:5060" The same occurs when I use the dns nane : forward("udp:raspberry3.emtelco.co:5060"); Any ideas ? Regards

2 1

DNS resolution with ipops
by harneet singh 22 May '23

22 May '23

Hi Experts, I am planning to use *dns_query*() API from the ipops module, which I understand from some documentation that it internally uses *getaddrinfo*(). I wanted to check if someone can comment on the DNS Cache mechanism in this case. * Does Kamailio retain any *dns cache* while using this API, or would it be actually doing the resolution for each call. * In light of the above, does Kamailio honour the *TTL value i*n response to the DNS Query? Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 1

MySQL duplicate entry error on location after 5.5 => 5.6 upgrade
by Benoit Panizzon 22 May '23

22 May '23

Hi list Since updating 5.5 to 5.6 i often see this message in the logs: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Duplicate entry 'uloc-645ca178-f29e-1' for key 'location.ruid_idx' (1062) ERROR: <core> [db_query.c:244]: db_do_insert_cmd(): error while submitting query ERROR: usrloc [ucontact.c:687]: db_insert_ucontact(): inserting contact in db failed ****** (uloc-645ca178-f29e-1) ERROR: usrloc [urecord.c:420]: wb_timer(): inserting contact into database failed (aor: *******) usrloc is dmq synced between two nodes. Were there some changes which could have caused this issue? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Kamailio v5.7.0 Released - new major version is out
by Daniel-Constantin Mierla 21 May '23

21 May '23

Kamailio v5.7.0 is out – it comes with 4 new modules and a large set of improvements touching again more than 60 existing modules. You can read a bit more detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-7-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.7.0 brings more flexibility and optimizations across many components, new variables and transformations, expression-based preprocessor values and conditions, alternative TLS module using WolfSSL project, improvements to STIR/SHAKEN, IMS/VoLTE, more functions exported to KEMI interface, including a new KEMI Python3 interpreter. ... just to list only a few here. Enjoy Kamailio v5.7.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

2 1

db_redis and ursloc - problem after restarting kamailio
by Koldo Aingeru 18 May '23

18 May '23

Hi, I've encountered a problem using db_redis for location, we recently migrated to redis from mysql and just found out this yesterday. We are using the usrloc module with db_mode = 2, so the location info is written to redis every 60 seconds. When restarting, Kamailio reads all the contacts and loads them into memory, but for some contacts it loads the “methods” key with an incorrect value. If in the REGISTER there are no methods kamailio saves it with methods= -1: { "jsonrpc": "2.0", "result": { "AoR": “zzzzzzz", "Contacts": [{ "Contact": { "Address": "sip:1540305477794@W.X.Y.Z:5060", "Expires": 2752, "Q": -1, "Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z", "CSeq": 11, "User-Agent": “xxxxxxx", "Received": "sip:W.X.Y.Z:5060", "Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>", "State": "CS_SYNC", "Flags": 0, "CFlags": 64, "Socket": “udp:A.B.C.D:5060", "Methods": -1, "Ruid": "uloc-644a176b-6472-4641", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": -1, "Keepalive": 1, "Last-Keepalive": 1684246829, "Last-Modified": 1684246829 } }] }, "id": 19286 } But when restarting kamailio, the same contacts has a methods= 0 { "jsonrpc": "2.0", "result": { "AoR": “zzzzzzz", "Contacts": [{ "Contact": { "Address": "sip:1540305477794@W.X.Y.Z:5060", "Expires": 2697, "Q": -1, "Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z", "CSeq": 11, "User-Agent": “xxxxxxx", "Received": "sip:W.X.Y.Z:5060", "Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>", "State": "CS_SYNC", "Flags": 0, "CFlags": 64, "Socket": “udp:A.B.C.D:5060", "Methods”: 0, "Ruid": "uloc-644a176b-6472-4641", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": -1, "Keepalive": 1, "Last-Keepalive": 1684246829, "Last-Modified": 1684246829 } }] }, "id": 19286 } In the schema file for redis the key is correctly set as int and in redis I can see it saved as -1. So when a call comes in, the lookup() function returns a -2 as it doesn’t support the INVITE method and the call fails. This is happening in kamailio 5.2.8 and kamailio 5.2.1 (old versions, I know, we are working on updating it); with mysql as a backend it works perfectly after a restart. We do have the param method_filtering=1 , changing to 0 makes it works. We seem to have this since forever and for what I can see, is not unusual as is in the default kamailio.cfg provided (even the default value for it is 0). Has anyone else encountered this? Thanks! ======================================== Koldo Aingeru Marcos Fdez. Ingeniería de Sistemas Sarenet S.A.U. 944209470 Parque Tecnológico, Edificio 103 48170 Zamudio, Bizkaia www.sarenet.es ========================================

2 2

Contact changes, caller dialog attributes and NAT traversal
by Alex Balashov 17 May '23

17 May '23

Hi, When I modify INVITEs with set_contact_alias() / add_contact_alias(), this is not preserved in dialog data, and therefore not honoured in BYEs locally generated due to dialog timeout. For example, if the initial INVITE contained: Contact: sip:line1@192.168.1.100 and, after transit, became: Contact: <sip:line1@192.168.1.100>;alias=1.1.1.1~25844~1 There is no ;alias value stored in the caller dialog data, just the original URI + parameters. A related problem: I tried to work around this by storing an alias in dialog user variables, e.g. $dlg_var(alternate_ct) = $_s($si~$sp~$prid) and in fact, I am able to recover this value later: event_route[tm:local-request] { if($dlg_var(alternate_ct) ne $null) { $ru = $ru + ";alias=" + $dlg_var(alternate_ct); handle_ruri_alias(); } } And in fact, if I print the value of $du after calling handle_ruri_alias(), I can see that it is modified. However, this seems to have no effect on where the request actually goes at the network and transport level. I assume this is because the event_route does not actually allow one to overwrite elements of the spoofed request, and that its essential attributes have been pre-populated elsewhere. Nevertheless, the effect is that these BYEs do not reach NAT'd endpoints. Any suggestions are appreciated! Thanks in advance, -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 4

Re: Releasing Kamailio v5.7.0
by Daniel-Constantin Mierla 17 May '23

17 May '23

The header style was wrong for ctl, fixed, thanks. Daniel On 15.05.23 18:55, Дилян Палаузов wrote: > Off-list > > Hello, > > at > https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… there > is a horizonal line after ctl, which shall not be there. > > Greetings > Дилян > > > На 15 май 2023 г. 7:20:55 UTC, Daniel-Constantin Mierla > <miconda(a)gmail.com> написа: > > Hello, with a few public holidays coming soon around here, I am > considering to release 5.7.0 this week on Wednesday, May 17, 2023. > Rather short notice, but there were no major bug reports that need > to be tracked. The list of new features is being built in the > wiki: - > https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… > The other tutorials related to this major release should be ready > by then as well. Should anyone think more time is needed, then it > can be postponed, not a problem at all. Cheers, Daniel > -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Releasing Kamailio v5.7.0
by Daniel-Constantin Mierla 17 May '23

17 May '23

Hello, with a few public holidays coming soon around here, I am considering to release 5.7.0 this week on Wednesday, May 17, 2023. Rather short notice, but there were no major bug reports that need to be tracked. The list of new features is being built in the wiki: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… The other tutorials related to this major release should be ready by then as well. Should anyone think more time is needed, then it can be postponed, not a problem at all. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

2 3

Diameter_authorization_rejected (FHOSS)
by Wilmes, Matthias 16 May '23

16 May '23

Hello sr-users, i use the guide for "how to integrate an IMS using Kamailio with open5gs EPC" from Supreeth Herle. When my CotsUE(ONEPLUS8) try to Register. I get an 403 Forbidden HSS Authorization Rejected (see udp-stream.txt). The output of the fhoss looks like this. de.fhg.fokus.hss.cx.CxFinalResultException: Diameter_Authorization_Rejected at de.fhg.fokus.hss.cx.op.UAR.processRequest(UAR.java:134) at de.fhg.fokus.hss.main.Task.execute(Task.java:169) at de.fhg.fokus.hss.main.Worker.run(Worker.java:66) Insufficient access rights for the mysql hss_db? The user hss@localhost and hss@% have grant access. Maybe someone has had the error and has a hint and can help. Can't find the error. Many thanks in advance for an answer. -M.Wilmes

3 2

How to prevent run-away dialogues?
by Benoît Panizzon 15 May '23

15 May '23

Hi team Is there any way to get correct CDRS when using the dialog module and restarting kamailio? I have configured the dialog timeout to be 12 hours. But today while doing IC billing, we stumbled over a call that lasted for a week. Probably due to a stale entry in the database dialogue tables left over after a kamailio restart. Looking at the logs there definitely was something wrong: dialog [dlg_req_within.c:211]: bye_reply_cb(): inconsistent dlg timer data on dlg 0x7f153f503778 [956:2612] with clid '35BEFD13@7f33ff47' and tags '7f33ff47+1+75300082+dde85140' '3891401256-2097511021' acc [acc_cdr.c:229]: db_write_cdr(): fallback to dlg_only search because of message doesn't exist. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

[auth_radius.c:123]: mod_init(): failed to open configuration file
by Denys Pozniak 12 May '23

12 May '23

Hello! After a major upgrade of Kamailio (5.1 -> 5.6), an error appears that it is not possible to open configuration file (I think this is about /etc/radiusclient/radiusclient.conf), although it exists with the necessary access rights: *0(27075) DEBUG: <core> [core/sr_module.c:969]: init_mod(): auth_radius0(27075) ERROR: auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration file0(27075) ERROR: <core> [core/sr_module.c:975]: init_mod(): Error while initializing module auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)ERROR: error while initializing modules* For the test, I made Kamailio downgrade back to 5.1 and the problem went away. Shortened the Kamailio config to the minimum for reproducing the problem: *#!KAMAILIOmemdbg=5memlog=5children=1log_stderror=nolisten=udp:127.0.0.1:5060 <http://127.0.0.1:5060>loadmodule "kex.so"loadmodule "corex.so"loadmodule "tm.so"loadmodule "sl.so"loadmodule "rr.so"loadmodule "pv.so"loadmodule "maxfwd.so"loadmodule "auth.so"loadmodule "auth_radius.so"modparam("auth_radius", "radius_config", "/etc/radiusclient/radiusclient.conf")request_route { return;}* Could the commit below somehow affect the acceptance of the radius_config module parameter? https://github.com/kamailio/kamailio/commit/f33ba318b20cbd2b34d278a7e2c4e64… -- BR, Denys Pozniak

4 7

kamcmd ul.db_contacts how to specify table name?
by Benoît Panizzon 12 May '23

12 May '23

Good morning. I'm trying to get the number of registered contacts with kamcmd ul.db_contacts. The table has the default name 'location'. But no matter what I try: kamcmd ul.db_contacts location kamcmd ul.db_contacts s:location kamcmd ul.db_contacts database.location kamcmd ul.db_contacts s:database.location Kamcmd complains the table is not found. What would be the correct syntax to provide the table name? Attempted with Kamailio 5.5 and 5.6 -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

ICMP Port Unreachable using loopback interface with ethernet IP
by Calvin E. 11 May '23

11 May '23

The scenario is Kamailio on Debian 11 talking to an external application server that returns a 302 with a Contact that contains Kamailio's own IP and a different port. Kamailio is listening on the correct port via at the given IP address. However, when Kamailio creates the packet to talk to itself, it it send over the loopback adapter "lo" and gets an ICMP port reply: listen=udp:KAMAILIO_INTERNAL_FLOATING_IP:8888 10.z.a.b.5000 > 10.z.x.y.5060: SIP, length: 849 SIP/2.0 302 Moved Temporarily Contact: <sip:44123456...@10.z.x.y:8888> 15:39:00.548722 lo In IP (tos 0x10, ttl 64, id 5431, offset 0, flags [none], proto UDP (17), length 949) 10.z.x.y.5060 > 10.z.x.y.8888: SIP, length: 921 15:39:00.548732 lo In IP (tos 0xd0, ttl 64, id 19038, offset 0, flags [none], proto ICMP (1), length 576) 10.z.x.y > 10.z.x.y: ICMP 10.44.7.136 udp port 8888 unreachable, length 556 Do I need to configure something in the OS or Kamailio to allow the ethernet IP to work via the loopback adapter? I haven't set up any special networking to cause this, it appears to be a Linux kernel behavior.

3 3

where add contact header to ack for fail messages
by mohsen khashei 11 May '23

11 May '23

Hi I want to know where kamailio sends ack messages to faiurel messages (status >=400) so that I I add Contact header to the ack. I tried WITHINDLG with no luck. thanks

5 6

GeoIP2 and KEMI
by Michal Hajek 11 May '23

11 May '23

Hello, why this commit is not in branch 5.6? https://github.com/kamailio/kamailio/commit/21817906853140322c701f8cbb82010… Without this, is KEMI and GeoIP2 incompatible. Thanks Michal

2 1

kamailio/kamailio-ci docker image
by Sergey Safarov 11 May '23

11 May '23

Hi Now "kamailio/kamailio-ci" docker image is pushed to GitHub packages <https://github.com/kamailio/kamailio-ci/pkgs/container/kamailio-ci> only. I have a question should we completely switch to using the GitHub docker repo and remove the "kamailio/kamailio-ci" docker image from Docker Hub <https://hub.docker.com/repository/docker/kamailio/kamailio-ci>? Or required to push the "kamailio/kamailio-ci" docker image to GitHub packages and Docker Hub repos? Sergey

2 1

Re: where add contact header to ack for fail messages
by Henning Westerholt 11 May '23

11 May '23

Understood. Thanks for sharing your final solution, added the list as well that others can benefit from it. Cheers, Henning From: mohsen khashei <mkhashei(a)gmail.com> Sent: Donnerstag, 11. Mai 2023 12:37 To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Re: where add contact header to ack for fail messages I need it for an application server after kamailio. Finally I add contact to the message by ac_extra_hdrs of tm module with a p header. On Thu, May 11, 2023, 15:01 Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello, why you actually need to add the Contact header to the ACK? According to the RFC 3261 is should be an optional header to that message. Cheers, Henning -----Original Message----- From: James Browne <james(a)frideo.com<mailto:james@frideo.com>> Sent: Mittwoch, 10. Mai 2023 14:08 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: [SR-Users] Re: where add contact header to ack for fail messages I made simple tests and it seems that this is a kamailio-TM-internal message being sent, not being processed by the cfg file. If this is simple enough and deterministic, you may consider using the corex module to edit the message as it's being sent "on the wire". I can't think of any other solution. https://kamailio.org/docs/modules/5.6.x/modules/corex.html#corex.evr.networ… You may be able to write some code that manipulates the message to manually add the Contact header. Maybe even the append_hf function may work here, but it seems unlikely. James On Mon, 8 May 2023 at 12:28, mohsen khashei <mkhashei(a)gmail.com<mailto:mkhashei@gmail.com>> wrote: > > thanks for the reply I tried it and it didn't work. also I tried onsend_route with no luck. > > On Sun, May 7, 2023 at 7:00 PM Yuriy G <ovoshlook(a)gmail.com<mailto:ovoshlook@gmail.com>> wrote: >> >> Try here >> https://www.kamailio.org/docs/modules/5.6.x/modules/tm.html#tm.e.loca >> l-request >> >> However I would doubt first do I do something right by adding contact to ACK message wichbasicaly confirmation of the final transaction and contact here is meaningless. >> >> On Sun, 7 May 2023, 16:48 mohsen khashei, <mkhashei(a)gmail.com<mailto:mkhashei@gmail.com>> wrote: >>> >>> Hi I want to know where kamailio sends ack messages to faiurel messages (status >=400) so that I I add Contact header to the ack. >>> I tried WITHINDLG with no luck. >>> thanks >>> __________________________________________________________ >>> Kamailio - Users Mailing List - Non Commercial Discussions To >>> unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> >>> Important: keep the mailing list in the recipients, do not reply only to the sender! >>> Edit mailing list options or unsubscribe: >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions To >> unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> >> Important: keep the mailing list in the recipients, do not reply only to the sender! >> Edit mailing list options or unsubscribe: > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> > Important: keep the mailing list in the recipients, do not reply only to the sender! > Edit mailing list options or unsubscribe: __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

1 0

using kamailio to send invite to webrtc clients (with freeswitch)
by shwetank singh 09 May '23

09 May '23

Hello experts I have a setup where webrtc client registrations (from behind a NAT / VPN) are on kamailio and the INVITE to begin a call is sent by freeswitch to kamailio which is then expected to relay it to the subscribed webrtc client. i understand, from documentation and general thinking, that kamailio cannot open a new connection to such a client and should reuse an open connection (a websocket in my case). i have setup kamailio as generic as it may sound and expect t_relay() to do the magic of forwarding the invite, however, from logs i don't see anything indicating kamailio is using any existing connection and hence my outgoing invite requests are stuck showing pointed towards a vpn gateway which was the registered "location" of client (which is the public ip of VPN gateway) please advise what relevant information can i produce here to make the query more readable and clear. headed here after trying just about all the resources available on the topic. e.g. if my location record looks like AoR: 1004(a)mydomain.com Contacts: - Contact: Address: sip:1004@11.22.33.44:49179 CFlags: 64 CSeq: 3087 Call-ID: 189jss21e24ntve1ggsuli Expires: 593 Flags: 0 Instance: <urn:uuid:8a936bbc-514f-4755-bed0-edc644dd4453> KA-Roundtrip: 0 Keepalive: 1 Last-Keepalive: 1683652755 Last-Modified: 1683652755 Methods: 7071 Path: <sip:10.10.6.196:3040;received=sip:mydomain.com ;lr;nat=yes> Q: -1 Received: sip:11.22.33.44:49179;transport=ws Reg-Id: 1 Ruid: uloc-645601c4-131220-3764 Server-Id: 0 Socket: tls:1.2.3.4:4443 State: CS_SYNC Tcpconn-Id: 3916 User-Agent: JsSIP 3.9.0 i try to lookup the location and find the address, and then route to that address by setting $ru in sngrep it does show that kamailio is trying to send INVITE to 11.22.33.44:port (which is the VPN gateway) but it isn't exactly clear from logs if this is being done over an existing connection. how does kamailio identify if a connection exists for a user (for each contact in AOR, if multiple contacts exist for a user -- i.e. different browser sessions?) if(reg_fetch_contacts("location", "$ru", "caller")) { $var(i) = 0; while($var(i) < $(ulc(caller=>count))) { $ru = $(ulc(caller=>addr)[$var(i)]); $var(i) = $var(i) + 1; setflag(FLT_DLGINFO); dlg_manage(); t_relay(); } } -- Shwetank

3 2

Performing async_http calls on stateless Loadbalancers
by Julius Flohr 09 May '23

09 May '23

Hi List, we are running several stateless SIP Loadbalancers using Kamaillio 5.1 and 5.6. Now we would like to perform an async_http request if an INVITE matches certain criteria. The request itself is performed very similar to how it's described here [1] This uses the transaction module in order to assure that the response can be mapped to the original request. However, this also means that the processing of the entire request becomes stateful which we would like to avoid. We tried to use t_release() in the callback route (in [1] this route is called "RELAY_API_RESPONSE"). However, documentation says that this is only allowed in the REQUEST_ROUTE. Is there an easy way to circumnavigate this issue? Cheers [1]: https://wazo-platform.org/blog/kamailio-routing-with-rtjson-and-http-async-… -- Julius Flohr - Voice Engineer - flohr(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Mobil: +49 (0)1579-000-0205 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

3 3

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