sr-users December 2020

sr-users@lists.kamailio.org

67 participants
91 discussions

Re: [SR-Users] Dialog profile not defined
by Gertjan Wolzak 10 Dec '20

10 Dec '20

Hello Kamailions, Well, I think I found the cause of my issue where the Dialog profile was not defined.. Well it was. I had not enabled antiflood, by not enabling antiflood, the htable module was also not loaded... I guess the us of profiles_with_value parameter needs htable? Is that correct? If so, that means the htable is a dependency for the dialog module...., then it would be sometihng that could be added to the documentation of the dialog module. When this is not the case, then I have to dig deeper, as I do not get an error anymore about the profile not being known... Thank you. Gertjan

2 2

REGINFO events not sending
by Adrian Tabacioiu 10 Dec '20

10 Dec '20

Hello, Does anybody has used with success the reginfo modules ? I added lines bellow in configuration, and tried different variations, Even if my subscribe for "reginfo" events is accepted (with 202 OK), I receive no notification when respective user registers. Nor do I get the xml body in the first notification. Added in my config: loadmodule "presence_reginfo.so" loadmodule "pua_reginfo.so" modparam("pua_reginfo", "default_domain", "192.168.60.65") modparam("pua_reginfo", "server_address", "sip:reginfo@192.168.60.65") modparam("pua_reginfo", "publish_reginfo", 1) Thank you in advance, Adrian

2 3

SLA presence not working proper with (SCA module)
by Aatif Shaikh 10 Dec '20

10 Dec '20

Aatif Shaikh <aatif.shaikh(a)ecosmob.com> Mon, Dec 7, 11:00 AM (3 days ago) to sr-users Hello All I configure my kamailio.cfg to handle SLA using (SCA module) and shared presence is working but still facing some issue in case of hold invite and BYE and the reason behind of that issue is following error Nov 26 07:38:40 SBC-4-1 /usr/local/sbin/kamailio[104107]: ERROR: sca [sca_call_info.c:1008]: sca_call_info_invite_request_handler(): Failed to update sip:4569@test.sip.abcd.com appearance-index 0 to active actually, in Kamailio appearances, I can see the entry for this call but the index is 1 instead of 0, and Kamailio going to update with a 0 index [root@SBC-4-1 ntcarfte-kamailio]# kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 active 1606376289 sip:4569@10.xx.xx.xx :5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120MTQ5OTcyZjFhMjMyNmI1ZGE1MWY4ODc2M2RkN2VmZmQ 45dc18d8 H6cS9vecZ248B if I manually update appearances using RPC command with index 1 then the phone started blinking as I change state to held # kamcmd sca.update_appearance sip:4569@sc4test.sip.teledge.com 1 held # kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 held 1606376516 sip:4569@10.xx.xx.xx :5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120NzE5MDgyZDc1NjJiYjcwMWFlYmI3NzM3NjE2OTRhZjU 08f005cb eK9ratm83g92e kamailio.cfg route[SCA] { if(is_method("SUBSCRIBE")) { if ($hdr(Event) == "call-info" || $hdr(Event) == "line-seize") { xlog("L_INFO","(MAIN) :HELLO ($avp(uuid)) : $avp(rsi) $sp $hdr(Event)"); xdbg("SCA: $hdr(Event) SUBSCRIBE $ru from $si:$sp"); sca_handle_subscribe(); exit; } return; } if (!is_method("BYE|CANCEL|INVITE|PRACK|REFER")) { return; } sca_call_info_update(); } route[RELAY_OUTBOUND_FS] { xlog("L_INFO","(RELAY_OUTBOUND_FS) : ($avp(uuid)) : INSIDE ROUTE "); if (!has_totag()){ $avp(set_h) = 1; } t_on_reply("REPLY_OUTBOUND_FS"); route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } route[RELAY_INBOUND_FS] { if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { $avp(s:puburis_caller) = $fu; setflag(8); dlg_manage(); } if(is_method("REGISTER")) { t_on_reply("REPLY_REGISTER"); } else { t_on_reply("REPLY_INBOUND_FS"); } route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } onreply_route[REPLY_INBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } onreply_route[REPLY_OUTBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } can someone help me with this Did I missed something to handle SLA?

1 0

NAT problem with recvonly calls
by David Cunningham 10 Dec '20

10 Dec '20

Hello, We have a problem with a SIP doorbell device which sends media one way only, and NAT at the receiving device. When the doorbell button is pressed it makes a call to a configured destination. Since the doorbell only sends and doesn't receive it sends the INVITE with sendonly in the SDP, and the destination then replies with a 200 OK with recvonly in the SDP. The problem is that the destination is behind NAT, and its reply contains a private network IP in the SDP. Normally Asterisk when nat=yes works around that by adjusting the destination for RTP to be the address it actually receives audio from, however because this device is recvonly Asterisk never receives audio from it. This means Asterisk keeps trying to send the doorbell's RTP to the private network IP which of course fails, and the destination never gets the RTP from the doorbell. We haven't found a solution in Asterisk to this, so are now looking to Kamailio which acts as a load-balancing proxy in front of Asterisk for one. For example, maybe we could use fix_nated_sdp, but only on 200 OK's with recvonly. Has anyone else encountered this, and are there any recommended solutions? Thank you in advance! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

4 8

Re: [SR-Users] NAT problem with recvonly calls
by Ovidiu Sas 09 Dec '20

09 Dec '20

The doorbell is the caller. ICE support would be required on the callee side (between NATed callee and asterisk). There's no need for ICE support on the doorbell/caller side. -ovidiu On Wed, Dec 9, 2020 at 2:42 AM Alex Balashov <abalashov(a)evaristesys.com> wrote: > > ICE support just doesn't seem to me to be something a SIP doorbell would > have. > > On 12/9/20 2:39 AM, Olle E. Johansson wrote: > > > > > >> On 8 Dec 2020, at 18:55, Richard Fuchs <rfuchs(a)sipwise.com > >> <mailto:rfuchs@sipwise.com>> wrote: > >> > >> Use IPv6 > > > > While I like that proposal, assuming that IPv6 will not have a stateful > > firewall is propably not a good assumption. > > So I suspect that an IPv6 firewall would not let the packets in if there > > is not outbound traffic first. I do like Ovidius > > ICE-based solution and would like to add RTCP - if muxed it would open > > the port, but the likelyhood that it’s > > implemented is propably low. > > > > IPv6 greetings! > > /O :-) > >> > >> Cheers > >> > >> On 07/12/2020 23.01, David Cunningham wrote: > >>> Hello, > >>> > >>> We have a problem with a SIP doorbell device which sends media one > >>> way only, and NAT at the receiving device. > >>> > >>> When the doorbell button is pressed it makes a call to a configured > >>> destination. Since the doorbell only sends and doesn't receive it > >>> sends the INVITE with sendonly in the SDP, and the destination then > >>> replies with a 200 OK with recvonly in the SDP. The problem is that > >>> the destination is behind NAT, and its reply contains a private > >>> network IP in the SDP. > >>> > >>> Normally Asterisk when nat=yes works around that by adjusting the > >>> destination for RTP to be the address it actually receives audio > >>> from, however because this device is recvonly Asterisk never receives > >>> audio from it. This means Asterisk keeps trying to send the > >>> doorbell's RTP to the private network IP which of course fails, and > >>> the destination never gets the RTP from the doorbell. > >>> > >>> We haven't found a solution in Asterisk to this, so are now looking > >>> to Kamailio which acts as a load-balancing proxy in front of Asterisk > >>> for one. For example, maybe we could use fix_nated_sdp, but only on > >>> 200 OK's with recvonly. > >>> > >>> Has anyone else encountered this, and are there any recommended > >>> solutions? > >>> > >>> Thank you in advance! > >>> > >>> -- > >>> David Cunningham, Voisonics Limited > >>> http://voisonics.com/ <http://voisonics.com/> > >>> USA: +1 213 221 1092 > >>> New Zealand: +64 (0)28 2558 3782 > >>> > >>> _______________________________________________ > >>> Kamailio (SER) - Users Mailing List > >>> sr-users(a)lists.kamailio.org > >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- VoIP Embedded, Inc. http://www.voipembedded.com

1 0

GitHub discussion
by Sergey Safarov 09 Dec '20

09 Dec '20

GitHub release new feature - discussion. Example https://github.com/vercel/vercel/discussions

2 1

Kamailio as an LCR based on prices but also signaling quality indicators
by Abdoul Osséni 08 Dec '20

08 Dec '20

Hello, I am trying to configure kamailio as an LCR based on prices but also signaling quality indicators like ASR and ACDR. Can you please help me and tell me where to start? Regards Abdoul

4 3

kamailio-5.2.0 Crash - udp_send failed
by Hamid Hashmi 07 Dec '20

07 Dec '20

I am using "kamailio 5.2.0-dev6 (x86_64/linux) 48ed62-dirty" what could be the reason of the crash its usually crash with the following logs Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36eee8c560,418,0,10.100.227.202:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: WARNING: tm [t_reply.c:1581]: t_retransmit_reply(): send pr buffer failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8eb948,358,0,10.100.177.91:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8b4a80,358,0,10.100.72.230:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8ac740,416,0,10.100.72.230:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8b5098,356,0,10.100.56.38:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8e8f18,416,0,10.100.177.91:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20777]: ERROR: <script>: Re-Transmit: REGISTER (sip:410060269353579@ims.mnc006.mcc410.3gppnetwork.org (10.100.236.57:5060) to sip:410060269353579@ims.mnc006.mcc410.3gppnetwork.org, 1SDq5cuY3iDYFKLATTp) Sep 25 16:58:41 pcscf [Proxy-CSCF][20761]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8e8a08,354,0,10.100.2.76:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20761]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20761]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20767]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8ad100,360,0,10.100.144.137:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20767]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20767]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:41 pcscf [Proxy-CSCF][20777]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f36ef8eb860,360,0,10.100.140.226:5060,16): Invalid argument(22) Sep 25 16:58:41 pcscf [Proxy-CSCF][20777]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Sep 25 16:58:41 pcscf [Proxy-CSCF][20777]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Sep 25 16:58:43 pcscf [Proxy-CSCF][20861]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 77 Sep 25 16:58:44 pcscf [Proxy-CSCF][20853]: ERROR: <core> [core/tcp_read.c:301]: tcp_read_data(): error reading: Connection timed out (110) ([10.100.64.49]:32888 -> Sep 25 16:58:44 pcscf [Proxy-CSCF][20853]: ERROR: <core> [core/tcp_read.c:302]: tcp_read_data(): -> [10.161.224.228]:5060) Sep 25 16:58:44 pcscf [Proxy-CSCF][20853]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f36a739fe78 r: 0x7f36a739fef8 Sep 25 16:58:44 pcscf [Proxy-CSCF][20742]: ALERT: <core> [main.c:748]: handle_sigs(): child process 20815 exited by a signal 11 Sep 25 16:58:44 pcscf [Proxy-CSCF][20742]: ALERT: <core> [main.c:751]: handle_sigs(): core was generated Sep 25 16:58:44 pcscf kernel: [52607827.581845] net_ratelimit: 16 callbacks suppressed Sep 25 16:58:44 pcscf [Proxy-CSCF][20742]: CRITICAL: cdp [diameter_peer.c:423]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test Sep 25 16:59:01 pcscf CRON[24805]: (root) CMD (/bin/bash /root/volumes/monitoring/src/services_status.sh -p http://10.161.224.25:9091 -s kamailio_pcscf,sems -n pcscf) Sep 25 16:59:01 pcscf CRON[24804]: (CRON) info (No MTA installed, discarding output) Sep 25 16:59:44 pcscf [Proxy-CSCF][20742]: CRITICAL: <core> [main.c:654]: sig_alarm_abort(): shutdown timeout triggered, dying... but last time its also crashed with the following logs as well Sep 25 18:39:59 pcscf [Proxy-CSCF][28015]: ERROR: <core> [core/tcp_read.c:301]: tcp_read_data(): error reading: Connection timed out (110) ([10.100.183.34]:39022 -> Sep 25 18:39:59 pcscf [Proxy-CSCF][28015]: ERROR: <core> [core/tcp_read.c:302]: tcp_read_data(): -> [10.161.224.228]:5060) Sep 25 18:39:59 pcscf [Proxy-CSCF][28015]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f92ca8d0150 r: 0x7f92ca8d01d0 Sep 25 18:39:59 pcscf [Proxy-CSCF][28010]: ERROR: cdp [authstatemachine.c:404]: auth_client_statefull_sm_process(): auth_client_statefull_sm_process(): Received invalid event 6 while in state Open! Sep 25 18:39:59 pcscf [Proxy-CSCF][28010]: ERROR: cdp [authstatemachine.c:404]: auth_client_statefull_sm_process(): auth_client_statefull_sm_process(): Received invalid event 6 while in state Open! Sep 25 18:40:00 pcscf [Proxy-CSCF][28034]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 77 Sep 25 18:40:01 pcscf [Proxy-CSCF][28026]: ERROR: <core> [core/tcp_read.c:301]: tcp_read_data(): error reading: Connection timed out (110) ([10.100.100.218]:1337 -> Sep 25 18:40:01 pcscf [Proxy-CSCF][28026]: ERROR: <core> [core/tcp_read.c:302]: tcp_read_data(): -> [10.161.224.228]:5060) Sep 25 18:40:01 pcscf [Proxy-CSCF][28026]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f92ca87f070 r: 0x7f92ca87f0f0 Sep 25 18:40:01 pcscf [Proxy-CSCF][27919]: ALERT: <core> [main.c:748]: handle_sigs(): child process 27989 exited by a signal 11 Sep 25 18:40:01 pcscf [Proxy-CSCF][27919]: ALERT: <core> [main.c:751]: handle_sigs(): core was generated Sep 25 18:40:01 pcscf kernel: [52613904.372973] net_ratelimit: 29 callbacks suppressed Sep 25 18:40:01 pcscf [Proxy-CSCF][27919]: CRITICAL: cdp [diameter_peer.c:423]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test Sep 25 18:40:01 pcscf CRON[30581]: (root) CMD (/bin/bash /root/volumes/monitoring/src/services_status.sh -p http://10.161.224.25:9091 -s kamailio_pcscf,sems -n pcscf) Sep 25 18:40:01 pcscf CRON[30580]: (CRON) info (No MTA installed, discarding output) Sep 25 18:40:02 pcscf sems[2858]: [#7f2080044700] [update_uac_request, trans_layer.cpp:2080] WARNING: While sending 200 ACK: no matching transaction Sep 25 18:41:01 pcscf [Proxy-CSCF][27919]: CRITICAL: <core> [main.c:654]: sig_alarm_abort(): shutdown timeout triggered, dying... PS: Kamailio is not listening on localhost. Regards Hamid R. Hashmi

3 4

Kamilio dispatcher not registering with asterisk
by Mihai 07 Dec '20

07 Dec '20

Hi all, i have a problem with kamailio 5.3.x and asterisk 13, i basically forward everything, but i cant manage to make it register. The register arrives on asterisk see the capture bellow: Any help is much appreciated! ---------------- REGISTER sip:oro.sips.nl;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 104.201.100.15;branch=z9hG4bK4d5e.997621d931a2ad9f6423e2ac7782a319.1 Via: SIP/2.0/UDP 34.12.55.102:34626 ;received=34.12.55.102;branch=z9hG4bK-524287-1---0a0bffd64bbd9941;rport=34626 Max-Forwards: 69 Contact: <sip:test-user1@34.12.55.102:34626 ;transport=UDP;rinstance=85c33e976be3dad1> To: <sip:test-user1@oro.sips.nl;transport=UDP> From: <sip:test-user1@oro.sips.nl;transport=UDP>;tag=6d8fd914 Call-ID: h6lkViFgxurpVRkw4Ly-GQ.. CSeq: 1 REGISTER Expires: 60 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.4.9 rv2.10.11.7 Allow-Events: presence, kpml, talk Content-Length: 0 Path: <sip:104.201.100.15;lr;received=sip:34.12.55.102:34626> -------------------the config ------- # - flags # FLT_ - per transaction (message) flags # FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_FS 10 ####### Global Parameters ######### debug=4 log_stderror=yes memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 /* comment the next line to enable TCP */ disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases based on revers DNS on IPs (default on) */ auto_aliases=no /* add local domain aliases */ # alias="mysipserver.com" port=5060 /* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ # listen=udp:127.0.0.1:5060 sip_warning=no ####### Modules Section ######## # set module path #mpath="/usr/local/lib/kamailio/modules/" #loadmodule "db_mysql.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "acc.so" loadmodule "dispatcher.so" loadmodule "path.so" # ----------------- setting module-specific parameters --------------- # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) # ----- rr params ----- # add value to ;lr param to cope with most of the UAs modparam("rr", "enable_full_lr", 1) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- acc params ----- modparam("acc", "log_flag", FLT_ACC) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") # ----- tm params ----- modparam("tm", "fr_timer", 2000) modparam("tm", "fr_inv_timer", 40000) # ----- dispatcher params ----- #modparam("dispatcher", "db_url", DBURL) #modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 2) modparam("dispatcher", "xavp_dst", "_dsdst_") modparam("dispatcher", "xavp_ctx", "_dsctx_") modparam("dispatcher", "ds_ping_from", "sip:proxy@mykamailio") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_probing_threshold", 10) modparam("dispatcher", "ds_inactive_threshold", 5) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") modparam("dispatcher", "ds_probing_mode", 1) modparam("path", "use_received", 1) ####### Routing Logic ######## # main request routing logic request_route { # per request initial checks route(REQINIT); if(ds_is_from_list()) { setflag(FLT_FS); } # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle retransmissions if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); } # handle requests within SIP dialogs route(WITHINDLG); if (isflagset(FLT_FS)) { route(FROM_FS); exit; } ### only initial requests (no To tag) # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) { record_route(); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # dispatch destinations route(DISPATCH); } route[FROM_FS] { record_route(); route(RELAY); exit; } route[RELAY] { if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } route(RELAY); } else { if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; # must be ACK after a 487 or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction ... ignore and discard. exit; } } sl_send_reply("404","Not here"); } exit; } } # Handle SIP registrations route[REGISTRAR] { if(!is_method("REGISTER")) return; add_path_received(); route(DISPATCH); } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } # Dispatch requests route[DISPATCH] { # round robin dispatching on gateways group '1' switch ($fd){ case "oro.sips.nl": send_reply(483, "Ok, Skipper!"); if (!ds_select_dst("1", "4")) { log("ERROR: no active destinations found!\n"); send_reply(503, "Service Unavailable"); exit; } ds_select_dst("1", "4"); log("---- flag value is $dd -- branch $fd \n"); xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); break; case "oro2.sips.nl": send_reply(483, "Ok, Skipper!"); if (!ds_select_dst("2", "4")) { log("ERROR: no active destinations found!\n"); send_reply(503, "Service Unavailable"); exit; } ds_select_dst("2", "4"); log("---- flag value is $dd -- branch $fd \n"); xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); break; default: log("unknow destination?"); send_reply(503, "No service defined"); exit; } xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Try next destionations in failure route failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { if(ds_next_dst()) { xdbg("--- SCRIPT: retrying to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } }

3 4

SLA presence not working proper with (SCA module)
by Aatif Shaikh 07 Dec '20

07 Dec '20

Hello All I configure my kamailio.cfg to handle SLA using (SCA module) and shared presence is working but still facing some issue in case of hold invite and BYE and the reason behind of that issue is following error Nov 26 07:38:40 SBC-4-1 /usr/local/sbin/kamailio[104107]: ERROR: sca [sca_call_info.c:1008]: sca_call_info_invite_request_handler(): Failed to update sip:4569@test.sip.abcd.com appearance-index 0 to active actually, in Kamailio appearances, I can see the entry for this call but the index is 1 instead of 0, and Kamailio going to update with a 0 index [root@SBC-4-1 ntcarfte-kamailio]# kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 active 1606376289 sip:4569@10.xx.xx.xx:5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120MTQ5OTcyZjFhMjMyNmI1ZGE1MWY4ODc2M2RkN2VmZmQ 45dc18d8 H6cS9vecZ248B if I manually update appearances using RPC command with index 1 then the phone started blinking as I change state to held # kamcmd sca.update_appearance sip:4569@sc4test.sip.teledge.com 1 held # kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 held 1606376516 sip:4569@10.xx.xx.xx:5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120NzE5MDgyZDc1NjJiYjcwMWFlYmI3NzM3NjE2OTRhZjU 08f005cb eK9ratm83g92e kamailio.cfg route[SCA] { if(is_method("SUBSCRIBE")) { if ($hdr(Event) == "call-info" || $hdr(Event) == "line-seize") { xlog("L_INFO","(MAIN) :HELLO ($avp(uuid)) : $avp(rsi) $sp $hdr(Event)"); xdbg("SCA: $hdr(Event) SUBSCRIBE $ru from $si:$sp"); sca_handle_subscribe(); exit; } return; } if (!is_method("BYE|CANCEL|INVITE|PRACK|REFER")) { return; } sca_call_info_update(); } route[RELAY_OUTBOUND_FS] { xlog("L_INFO","(RELAY_OUTBOUND_FS) : ($avp(uuid)) : INSIDE ROUTE "); if (!has_totag()){ $avp(set_h) = 1; } t_on_reply("REPLY_OUTBOUND_FS"); route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } route[RELAY_INBOUND_FS] { if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { $avp(s:puburis_caller) = $fu; setflag(8); dlg_manage(); } if(is_method("REGISTER")) { t_on_reply("REPLY_REGISTER"); } else { t_on_reply("REPLY_INBOUND_FS"); } route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } onreply_route[REPLY_INBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } onreply_route[REPLY_OUTBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } can someone help me with this Did I missed something to handle SLA? -- -- Regards, *Aatif Shaikh *| Software Developer +91 9033976268Hangout: aatif.shaikh(a)ecosmob.comSkype : aatif.shaikh(a)ecosmob.com *Ecosmob Technologies Pvt. Ltd. * https://www.ecosmob.com VoIP | Web | Mobile | IoT | Big Data <https://twitter.com/ecosmob> <https://www.facebook.com/Ecosmob> <https://plus.google.com/+Ecosmob> <https://www.linkedin.com/company/ecosmob> <https://in.pinterest.com/ecosmob/> This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. Ecosmob Technologies is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

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 December 2020