sr-users June 2018

sr-users@lists.kamailio.org

88 participants
121 discussions

Re: [SR-Users] configuring websockts in kamilio
by Konstantin Polyakov 02 Jun '18

02 Jun '18

Hello Vinod, We used Doubango sipML5 web phone https://www.doubango.org/sipml5/call.htm?svn=252 It was quite good for debugging and testing webrtc calls. Most of work in kamailio config I made by using that client. Best regards. Konstantin > >Message: 8 >Date: Fri, 1 Jun 2018 23:50:50 +0530 >From: vinod mn < vinodmn.dbit(a)gmail.com > >To: sr-users(a)lists.kamailio.org >Subject: [SR-Users] configuring websockts in kamilio >Message-ID: >< CAHeWXy7h4Tcp4Sg9_eM3teCHBdJ5bwHa9TYSJy+7P4e+bm1hqQ(a)mail.gmail.com > >Content-Type: text/plain; charset="utf-8" > >hi configured websockets on kamilio 5.1.3 >I am trying to register the client based on webrtc client ,(sip.js) > the registration is fine but i am not getting the correct address if i >run "*kamctl ul show"* > > >* In the address filed I want the sip:<id>@<ip>:<port>ex: >sip:12345@127.0.0.1:12345 < http://sip:12345@127.0.0.1:12345 > * >output shows: >{ > "jsonrpc": "2.0", > "result": { > "Domains": [{ > "Domain": { > "Domain": "location", > "Size": 1024, > "AoRs": [{ > "Info": { > "AoR": "1xxxxxxxxx", > "HashID": 1xxxxx, > "Contacts": [{ > "Contact": { > *"Address": >"sip:eg84vjhr@p6ggglrk0gsh.invalid;transport=ws"*, > "Expires": 397, > "Q": 1, > "Call-ID": "ma4feu2i43bnu6ophe4k78", > "CSeq": 86, > "User-Agent": "SIP.js/0.5.0-devel BB", > "Received": "sip:X.X.X.X:56087;transport=ws", > "Path": "[not set]", > "State": "CS_NEW", > "Flags": 0, > "CFlags": 192, > "Socket": "tcp:X.X.X.X:8080", > "Methods": 783, > "Ruid": "uloc-5b116457-1dc1-03", > "Instance": >"<urn:uuid:0e879ebf-0a31-45a8-9fd9-6b937d3328d4>", > "Reg-Id": 1, > "Server-Id": 0, > "Tcpconn-Id": 259, > "Keepalive": 1, > "Last-Keepalive": 1527876355, > "Last-Modified": 1527876355 > } > }] > } > } > ], > "Stats": { > "Records": 1, > "Max-Slots": 1 > } > } > }] > }, > "id": 18958 >} > >In the address filed I want the sip:<id>@<ip>:<port> >ex: sip:12345@127.0.0.1:12345 > >Please give me any suggestions on this, which webrtc client can i use to >register to kamailio and able to receive on the client and to make outbound >calls from the client. > >-- >Thanks and regards >Vinod.M.N >

1 0

CDRs
by David Villasmil 02 Jun '18

02 Jun '18

Hello guys, I setup the CDRs according to the instructions on https://kb.asipto.com/siremis:install40x:accounting I get CDRs nicely, but the cdrs, even though they have a src_ip, there's no dest_ip, I mean I need the IP where the call was forwarded to... What do i need to do to get that in the cdr? Thanks! David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 1

Upgrade issue from 4.4.7 to 5.1.3
by Kevin Greene 01 Jun '18

01 Jun '18

Hello List users: I am trying to upgrade to the current version of Kamailio from the older 4.4 version to the current version. The 4.4 is functional but there are some features of 5.1 that we wanted to test with. It seems that my version of Linux (RHEL 6.9 or Oracle 6.9) has an issue with a library file. Any help would be useful. Thank you. Kevin Notes: I used the "yum update kamailio" function. (edited for clarity - it showed a long list of modules to be updated) "--> Finished Dependency Resolution Error: Package: kamailio-http-utils-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) Requires: kamailio = 4.4.7 Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) kamailio = 4.4.7-1.1 Updated By: kamailio-5.1.3-1.el6.x86_64 (home_kamailio_v5.1.x-rpms) kamailio = 5.1.3-1.el6 Error: Package: kamailio-http-utils-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) Requires: libkmi.so.1()(64bit) Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) libkmi.so.1()(64bit) Updated By: kamailio-5.1.3-1.el6.x86_64 (home_kamailio_v5.1.x-rpms) Not found Error: Package: kamailio-xml-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) Requires: kamailio = 4.4.7 Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms) kamailio = 4.4.7-1.1 Updated By: kamailio-5.1.3-1.el6.x86_64 (home_kamailio_v5.1.x-rpms) kamailio = 5.1.3-1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest" However the "missing" library is there in /usr/lib64. [root@sipserver tmp]# find / -name libkmi.so.1 /usr/lib64/kamailio/libkmi.so.1 /usr/lib64/libkmi.so.1 /lib64/libkmi.so.1 To provide additional help, See: [root@sipserver tmp]# kamailio -version version: kamailio 4.4.7 (x86_64/linux) 35d8ab flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 35d8ab compiled on 15:38:14 Feb 26 2018 with gcc 4.4.7

2 1

configuring the websocket in kamailio 5.1
by vinod mn 01 Jun '18

01 Jun '18

Hi, I configured the websocket in kamailio and it is running properly, which is the best webrtc client (with proper code as I dont't want to spend more time in writing the codes based on the example snippets ) can I use for registering, and making/ receiving the calls on the webrtc-client . requirement: webrtc-client(??)->register-> kamailio(already configured to use websocket) webrtc-client -> makecall to kamailio webrtc-client receives call from another client(sip not webrtc-client) -- Thanks and regards Vinod.M.N

1 0

Thank You
by Wilkins, Steve 01 Jun '18

01 Jun '18

Hi All, I normally get on this board to ask questions but today I just wanted to take a minute and say - Thank you to all of you who have taken the time to help me. Some of you have spent a lot of time schooling me on Kamailio, its Interactions with a PBX and different clients. I have learned tons from this board and just want to say again, Thank You All! -Steve

2 1

Multiple CDR rate groups using Siremis sql procedures
by Sergiu Pojoga 01 Jun '18

01 Jun '18

Hi, The SQL procedure takes a param, rgroup, which is default (by default). That works fine. In a real case scenario, having multiple rate groups, I wonder what's the best approach to rate CDRs based on the rate group a client belongs to? Do you store the rate_group in the ACC table and then adjust 'kamailio_cdrs' and 'kamailio_rating' procedures to take into account the rate_group of a CDR? If so, does anybody have a working example? Thanks.

1 0

Anybody using 2 instances with topos communicating with each other?
by Daniel Tryba 01 Jun '18

01 Jun '18

Scenario: endpoint (bob) <-> kamailio proxy (5.1.3) <-> kamailio backend (5.1.2) Both kamailio instances are running the topos module (mysql backend). Call setup is fine, but forwarding BYEs fail. With a call from endpoint to kamailio, topos on the proxy scrambles Contact to kamailio backend. But in responses from backend contact remains untouched. In the ACK to the 200, topos on the proxy does nothing. If the caller hangsup, the BYE will loop internally till max hops is exceeded (483 which will be send to caller eventually). When the backend initiates the call to the endpoint, topos appears to work, but the BYE from the endpoint on hangup get a 404 Not here from the proxy (route[WITHINDLG]). Disabling topos on the proxy will result in a functioning proxy (config attached). Is there something wrong with my config? Or is this an unforseen scenario that just doesn't work with topos? * Endpoint to backend scenario endpoint:5060 -> proxy:5060 INVITE sip:callee@sip.pocos.nl;transport=tcp SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Max-Forwards: 70 Route: <sip:proxy:5060;lr> Contact: <sip:bob@endpoint:5060;ob> proxy:5060 -> backend:5060 INVITE sip:callee@sip.itco.nl;transport=tcp SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... CSeq: 29848 INVITE Route: <sip:proxy:5060;lr> Contact: <sip:btpsh-5af5972d-bf5e-2@proxy> backend:5060 -> proxy:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy;branch=... Contact: <sip:atpsh-5af19bf0-9f94-7@backend> proxy:5060 -> endpoint:5060 SIP/2.0 200 OK Contact: <sip:atpsh-5af19bf0-9f94-7@backend> Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Record-Route: <sip:proxy;lr> endpoint:5060 -> proxy:5060 ACK sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Route: <sip:proxy;lr> proxy:5060 -> backend:5060 ACK sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... endpoint:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Max-Forwards: 70 Route: <sip:proxy;lr> proxy:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Max-Forwards: 69 Route: <sip:proxy;lr> proxy:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP proxy;rport=5060;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Max-Forwards: 68 Route: <sip:proxy;lr> [not going to mention the 50+ BYEs adding Vias and decrementing Max-Forwards. * Backend to endpoint scenario backend:5060 -> proxy:5060 INVITE sip:bob@endpoint:5060;ob SIP/2.0 Via: SIP/2.0/UDP backend;branch=... Route: <sip:loadbalancer@proxy;lr;received=sip:endpoint:5060> Contact: <sip:btpsh-5af07a27-72b-502c1@backend> proxy:5060 -> endpoint:5060 INVITE sip:bob@endpoint:5060;ob SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Contact: <sip:btpsh-5af5972d-bf5d-5@proxy> endpoint:5060 -> proxy:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy;received=proxy;branch=... Contact: <sip:bob@endpoint:5060;ob> proxy:5060 -> backend:5060 SIP/2.0 200 OK Contact: <sip:bob@endpoint:5060;ob;alias=endpoint~5060~1> Via: SIP/2.0/UDP backend;rport=5060;branch=... Record-Route: <sip:proxy;lr> endpoint:5060 -> proxy:5060 BYE sip:btpsh-5af5972d-bf5d-5@proxy SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... proxy:5060 -> endpoint:5060 SIP/2.0 404 Not here Via: SIP/2.0/UDP endpoint:5060;rport=5060;branch=...

2 2

Dispatcher module ERROR
by Aleksandar Sosic 01 Jun '18

01 Jun '18

Hi everyone, We have an error using the dispatcher module. In the logs: ```0(107) ERROR: dispatcher [dispatcher.c:815]: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled``` We are running 5.2.0~dev5+0~20180523010152.1118+xenial The configuration file parts regarding dispatcher are as follows: ``` loadmodule "dispatcher.so" ... # ----- dispatcher params ----- modparam("dispatcher", "list_file", "/tmp/dispatcher.list") # Dispatcher: Enable Failover-Support modparam("dispatcher", "flags", 2) # Dispatcher: Overwrite Destination address, if required. modparam("dispatcher", "force_dst", 1) # AVP's required for Fail-Over-Support: modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") # Try to recover disabled destinations every 15 seconds. modparam("dispatcher", "ds_ping_interval", 15) # Actively query the gateways: modparam("dispatcher", "ds_probing_mode",0)# ----- dispatcher params ----- modparam("dispatcher", "list_file", "/tmp/dispatcher.list") # Dispatcher: Enable Failover-Support modparam("dispatcher", "flags", 2) # Dispatcher: Overwrite Destination address, if required. modparam("dispatcher", "force_dst", 1) # AVP's required for Fail-Over-Support: modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") # Try to recover disabled destinations every 15 seconds. modparam("dispatcher", "ds_ping_interval", 15) # Actively query the gateways: modparam("dispatcher", "ds_probing_mode",0)``` What are we doing wrong? What are we missing? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Authenticate against outbound carrier
by Krzysztof Grobelak 01 Jun '18

01 Jun '18

Hello List, I have a working setup with a kamailio + freeswitch where i can register extension and make succesfull calls between them. I added now a "external" path for outbound call to which i can successfully route using the dialplan + dispatcher combo. My problem is that my outbound path requires authentication and i'm struggling to find a way to successfully authenticate with the remote end. I configured the UAC module to register against the remote end with a set of credentials but in the SIP trace i can see that the kamailio simply uses the local user credentials instead of the external ones. I believe that this is because the 401 Unauthorized from the carrier gets proxied to the extension which responds with its own credentials. Can anybody suggest how can i stop forwarding them in this case to extension and instead use the UAC to reply with different set of credentials? Regards, Krzysztof The config: request_route { ... if($rU=~"[0-9]{5,}"){ xlog("L_INFO","Looking up route for $rU\n"); dp_match("1", "$rU"); $var(dsid) = $(var(attrs){s.int}); if(!ds_select_dst("$var(dsid)", "4")) { send_reply("404", "No destination"); exit; } if(!ds_select_domain("$var(dsid)", "4")) { send_reply("404", "No destination"); exit; } xlog("L_INFO", "Looking up $fn in database\n"); $avp(s:auth_realm_avp) = "realm.com"; $avp(s:auth_username_avp) = "username"; $avp(s:auth_password_avp) = "password"; if(uac_reg_request_to("$fn", 1)) { xlog("L_INFO", "Found remote user [$rU] on [$rd] via [$du]"); t_on_failure("REMOTE_AUTH"); xlog("L_INFO", "going to <$ru> via <$du>\n"); route(RELAY); } exit; } failure_route[REMOTE_AUTH] { if ($T_reply_code == 401 or $T_reply_code == 407) { xlog("L_INFO", "Remote asked for authentication"); uac_auth(); } } -- PGP: 9E5D E635 5A03 485C 2E00 4530 EB83 920A 9E21 FBA8

1 0

Acc module and PostgreSQL
by Javohir Maxmarajabov 01 Jun '18

01 Jun '18

Is it possible to enable accounting module with PostgreSQL? All I found is documentation and examples that showing accounting module is used with MySQL module. -- Javokhir M.M. ________________________________________________ Disclaimer: The information in this e-mail is confidential. If you are not addressed recipient then please return and delete this e-mail from your system. Unauthorised use of or disclose the contents of this e-mail may be unlawful.

2 1

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 June 2018