sr-users

sr-users@lists.kamailio.org

35 participants
37544 discussions

R: Re: RTPPROXY & BRANCH
by marino.mileti＠alice.it 24 Sep '14

24 Sep '14

Because I've more than 1 client behind NAT (1,2,3 mobile phones) and I would like to reach all of them in parallel mode. I can't use for all of them same ports because all mobile clients have early media (the receive video media before they answer) So at the moment this scenario is not possible? Is there any possible turnaround? ----Messaggio originale---- Da: rfuchs(a)sipwise.com Data: 24-set-2014 1.15 A: <sr-users(a)lists.sip-router.org> Ogg: Re: [SR-Users] RTPPROXY &amp; BRANCH On 23/09/14 04:35 AM, marino.mileti(a)alice.it wrote: > I've a problem with rtpproxy during a parallel ring scenario. > I've two client behind NAT (192.168.10.20 & 192.168.10.50) and when I > try to call them in parallel mode (ringall) rtpproxy module sends in to > the INVITE the same RTP ports. > > Is it possible to manage rtpproxy in order to generate a couple of new > port for each branch? Not at the moment. The logic is that one endpoint advertised by the client is mapped to one endpoint advertised by rtpengine. Why would you like a separate set of ports? cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

RTPPROXY & BRANCH
by marino.mileti＠alice.it 23 Sep '14

23 Sep '14

Hi I've a problem with rtpproxy during a parallel ring scenario. I've two client behind NAT (192.168.10.20 & 192.168.10.50) and when I try to call them in parallel mode (ringall) rtpproxy module sends in to the INVITE the same RTP ports. Is it possible to manage rtpproxy in order to generate a couple of new port for each branch? My rtpproxy string in the kamailio conf (in manage branch section): rtpproxy_manage("bFAIE","192.168.10.10"); Brief extract of 2 SIP INVITE message send by kamailio to natted clients: 192.168.10.10 --> 192.168.10.20 User Datagram Protocol, Src Port: sip (5060), Dst Port: 6090 (6090) Session Initiation Protocol (INVITE) Request-Line: INVITE sip:1001@192.168.10.20:6090 SIP/2.0 Message Header Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 1004 1476 1657 IN IP4 192.168.10.10 Session Name (s): Talk Connection Information (c): IN IP4 192.168.10.10 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 62910 RTP/AVP 111 110 0 8 101 Media Description, name and address (m): video 47160 RTP/AVP 102 Media Attribute (a): nortpproxy:yes 192.168.10.10 --> 192.168.10.50 User Datagram Protocol, Src Port: sip (5060), Dst Port: 6090 (6090) Session Initiation Protocol (INVITE) Request-Line: INVITE sip:1002@192.168.10.50:6090 SIP/2.0 Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 1004 1476 1657 IN IP4 192.168.10.10 Session Name (s): Talk Connection Information (c): IN IP4 192.168.10.10 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 62910 RTP/AVP 111 110 0 8 101 Media Description, name and address (m): video 47160 RTP/AVP 102 Media Attribute (a): nortpproxy:yes

2 1

Wrong from/to header compose way in print_to and print_from
by dongwf 23 Sep '14

23 Sep '14

Hi kamailio dev: I am writing a module to implement some features, my version is 4.1.2, I am not sure if it is a known issue, I found: 1. When I get a INVITE request with from/to like from:"display"<aaa(a)sip.com>, then I call tm's new_dlg_uas with the sip req, now the dlg's rem_uri set as value: "display"<aaa(a)sip.com>; 2. After that, when I need use the dlg to send BYE with tm's req_within with the above saved dlg, the print_to function will check the rem_uri's first value if "<" or not, now my uri has display name, so the outgoing BYE's to header becomes to:<"display"<aaa(a)sip.com>>, is it wrong? Should we check the last char in the rem_uri as ">"? The detail code is : static inline char* print_to(char* w, dlg_t* dialog, struct cell* t) { t->to.s = w; t->to.len = TO_LEN + dialog->rem_uri.len + CRLF_LEN + ((dialog->rem_uri.s[0]!='<')?2:0); memapp(w, TO, TO_LEN); if(dialog->rem_uri.s[0]!='<') memapp(w, "<", 1); memapp(w, dialog->rem_uri.s, dialog->rem_uri.len); if(dialog->rem_uri.s[0]!='<') memapp(w, ">", 1); ....

2 6

Kamailio fronting Freeswitch authentication
by Ashwin Jain 23 Sep '14

23 Sep '14

Hi all, I am using Kamailio to front my freeswitch servers and it is working great. I am getting some problems with authentication, sometimes users which are not registered with kamailio are also able to make calls. I have a feeling that I am doing something really silly with kamailio routing. Following is the AUTH route that I am using, please let me know I am missing something very obvious. route[AUTH] { #!ifdef WITH_AUTH #!ifdef WITH_FREESWITCH if(route(FSINBOUND)) return; #!endif #!ifdef WITH_IPAUTH if((!is_method("REGISTER")) && allow_source_address()) { # source IP allowed return; } #!endif if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; } #!endif return; } route[FSINBOUND] { if($si== $sel(cfg_get.freeswitch.bindip) && $sp==$sel(cfg_get.freeswitch.bindport)) return 1; return -1; } I have set "WITH_AUTH" and "WITH_FREESWITCH". Let me know, if any more details are required. System configuration: Ubuntu: 12.04 LTS Kamailio: 4.1.5 (x86_64/linux) Freeswitch: 1.4.7 stable release -- Thanks and Regards, Ashwin Jain

2 1

Siremis v4.1.0 Questions.
by Mahmoud Ramadan Ali 23 Sep '14

23 Sep '14

Hello everyone, Please i want more clarification about what i can do with the Siremis v4.1.0 Can i configure Kamailio to load balance between multiple Asterisk servers and RTP proxy using the Siresmis web interface or i have to interface with the Kamailio configuration file and do that manually...? Thanks in advance.

4 6

User definable Ring Duration before forwarding
by Tim Chubb 23 Sep '14

23 Sep '14

Hi I was wondering if the following scenario is possible and if it is how I would go about implementing it: I would like to be able read from a database a list of destinations associated with a given dialled number which are tried in order of priority with each destination having a user definable ring duration before the next destination is tried. i.e. A Call is received from the PSTN, the number the caller dialled is looked up, it has 3 destinations attached to it, the users deskphone which is configured to ring for 10 seconds before the call is forwarded to their Mobile phone with a ring duration of 15 seconds, which if unanswered would be redirected to the main switchboard IVR. I think im looking for the equivalent of the Asterisk Dial app, where you can specify a timeout as an argument, is this possible to do with kamailio? All examples I have seen use a global timer value, which is unsuitable for this requirement, as each user could define n failover routes each with a distinct timeout before the next route is tried. Currently I have got as far as querying the database to retrieve the data but im a bit stumped as to how to handle the timeout variable. Any ideas? Tim Chubb

2 1

Kamailio - Separated Servers
by Bruno Emer 22 Sep '14

22 Sep '14

Hello! I am relatively new to Kamailio and I'm trying to create a new enviroment using it in my company. I am thinking about use Amazon to host the servers and use OpsWorks to automatically escalate then if necessary. To accomplish this, my idea is to separate the servers, using one dedicated server to run as WebSocket, one to run as proxy and one as a Registrar. I'll be using just one database to store informations to all of my servers. With this, if I need more resources later, I can just create new servers with the specific roles (WebSockets, Proxy, Registrar). By now, the idea is clear, but the point is that I don't know how to separate the WebSockets server from the proxy server. Actually, I can do this, but when I have one agent using a regular softphone and one agent using WebSockets (with JSSIP) they are not able to establish a session if the softphone user starts it. Now, I want to know if is there a way to use two websockets servers, register users using both of then and start sessions between then, with a separated proxy and registrar. Has anyone done this before? Is possible to use kamailio like this? Thanks. *Bruno Emer* Mobile: +55 11 96540-0044 email: brunoemer(a)gmail.com <https://www.facebook.com/bruno.emer.5> <https://www.linkedin.com/profile/view?id=86461237&trk=spm_pic> <https://twitter.com/brunoemer_> <https://www.flickr.com/photos/122070309@N03/> <http://google.com/+BrunoEmer> <http://instagram.com/brunoemer_>

3 4

R: Re: Kamailio multihomed - BYE problem
by marino.mileti＠alice.it 22 Sep '14

22 Sep '14

This is SIP capure. Kamailio listen on 172.20.11.172 & 192.168.10.10Caller is 172.20.11.208Called user that pickup call is 192.168.10.20Other group member is 172.20.11.152 Callee (172.20.11.208) make a call to group number 5000172.20.11.208 --> 172.20.11.172--------------Session Initiation Protocol (INVITE)Request-Line: INVITE sip:5000@172.20.11.172 SIP/2.0Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rportFrom: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172CSeq: 20 INVITECall-ID: q0KGluu3SrContact: <sip:1004@172.20.11.208:6090>;+sip.instance="<urn:uuid:a6e51976-8d02-4f51-a065-0f836be30038>" Kamailio replies with 100 Trying172.20.11.172 --> 172.20.11.208--------------Session Initiation Protocol (100)Status-Line: SIP/2.0 100 trying -- your call is important to usVia: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172CSeq: 20 INVITECall-ID: q0KGluu3SrServer: kamailio (4.1.5 (i386/linux))Content-Length: 0 Kamailio lookup db and send 1st INVITE to 1st group member (1000(a)172.20.11.152)172.20.11.172 --> 172.20.11.152--------------Session Initiation Protocol (INVITE)Request-Line: INVITE sip:1000@172.20.11.152:5090 SIP/2.0Record-Route: <sip:172.20.11.172;lr=on;nat=yes>Via: SIP/2.0/UDP 172.20.11.172;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.0Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172CSeq: 20 INVITECall-ID: q0KGluu3SrMax-Forwards: 69Contact: <sip:1004@172.20.11.208:6090>;+sip.instance="<urn:uuid:a6e51976-8d02-4f51-a065-0f836be30038>" Kamailio sends 2nd INVITE to 2nd group member (1001(a)192.168.10.20) using another network interface192.168.10.10 --> 192.168.10.20--------------Session Initiation Protocol (INVITE)Request-Line: INVITE sip:1001@192.168.10.20:6090 SIP/2.0Record-Route: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Record-Route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Record-Route: <sip:172.20.11.172;lr=on;nat=yes>Via: SIP/2.0/UDP 192.168.10.10;branch=z9hG4bK208d.ba27ec12b58ce991e5f589b977bb7075.0Via: SIP/2.0/UDP 172.20.11.172;rport=5060;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.1Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172CSeq: 20 INVITECall-ID: q0KGluu3SrContact: <sip:1004@172.20.11.172:5060>;+sip.instance="<urn:uuid:a6e51976-8d02-4f51-a065-0f836be30038>" Kamailio receive 100 trying from 172.20.11.152172.20.11.152 --> 172.20.11.172--------------Session Initiation Protocol (100)Status-Line: SIP/2.0 100 TryingVia: SIP/2.0/UDP 172.20.11.172;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.0Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172Call-ID: q0KGluu3SrCSeq: 20 INVITE Kamailio receive 180 ringing from 172.20.11.152172.20.11.152 --> 172.20.11.172--------------Session Initiation Protocol (180)Status-Line: SIP/2.0 180 RingingVia: SIP/2.0/UDP 172.20.11.172;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.0Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=puL7wn8Call-ID: q0KGluu3SrCSeq: 20 INVITERecord-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio sends 180 ringing to caller 172.20.11.172 --> 172.20.11.208--------------Session Initiation Protocol (180)Status-Line: SIP/2.0 180 RingingVia: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=puL7wn8Call-ID: q0KGluu3SrCSeq: 20 INVITERecord-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio receive 100 trying from 192.168.10.20192.168.10.20 --> 192.168.10.10--------------Session Initiation Protocol (100)Status-Line: SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.10.10;branch=z9hG4bK208d.ba27ec12b58ce991e5f589b977bb7075.0Via: SIP/2.0/UDP 172.20.11.172;rport=5060;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.1Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: sip:5000@172.20.11.172Call-ID: q0KGluu3SrCSeq: 20 INVITE Kamailio receive 180 ringing from 192.168.10.20192.168.10.20 --> 192.168.10.10--------------Session Initiation Protocol (180)Status-Line: SIP/2.0 180 RingingVia: SIP/2.0/UDP 192.168.10.10;branch=z9hG4bK208d.ba27ec12b58ce991e5f589b977bb7075.0Via: SIP/2.0/UDP 172.20.11.172;rport=5060;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.1Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=-iPr1gnCall-ID: q0KGluu3SrCSeq: 20 INVITERecord-route: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio sends 180 ringing to caller 172.20.11.172 --> 172.20.11.208--------------Session Initiation Protocol (180)Status-Line: SIP/2.0 180 RingingVia: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=-iPr1gnCall-ID: q0KGluu3SrCSeq: 20 INVITERecord-route: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio receive 200 OK from 192.168.10.20192.168.10.20 --> 192.168.10.10--------------Session Initiation Protocol (200)Status-Line: SIP/2.0 200 OkVia: SIP/2.0/UDP 192.168.10.10;branch=z9hG4bK208d.ba27ec12b58ce991e5f589b977bb7075.0Via: SIP/2.0/UDP 172.20.11.172;rport=5060;branch=z9hG4bK208d.8d88bd630566a8d23640dbb14fa4f9ef.1Via: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=-iPr1gnCall-ID: q0KGluu3SrCSeq: 20 INVITEContact: <sip:1001@192.168.10.20:6090>;+sip.instance="<urn:uuid:6382d45f-042d-4be8-b6bd-1621911e88a9>"Record-route: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio sends 200 OK to caller172.20.11.172 --> 172.20.11.208--------------Session Initiation Protocol (200)Status-Line: SIP/2.0 200 OkVia: SIP/2.0/UDP 172.20.11.208:6090;branch=z9hG4bK.BLejEhqfD;rport=6090From: <sip:1004@172.20.11.172>;tag=TNzDNgaNNTo: <sip:5000@172.20.11.172>;tag=-iPr1gnCall-ID: q0KGluu3SrCSeq: 20 INVITEContact: <sip:1001@192.168.10.20:6090>;+sip.instance="<urn:uuid:6382d45f-042d-4be8-b6bd-1621911e88a9>"Record-route: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Record-route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio CANCEL other leg (messages removed...not so useful)-------------- Kamailio receive BYE from 192.168.10.20192.168.10.20 --> 192.168.10.10--------------Internet Protocol Version 4, Src: 192.168.10.20 (192.168.10.20), Dst: 192.168.10.10 (192.168.10.10)User Datagram Protocol, Src Port: 6090 (6090), Dst Port: sip (5060)Session Initiation Protocol (BYE)Request-Line: BYE sip:1004@172.20.11.172:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.10.20:6090;branch=z9hG4bK.20aa9gXIY;rportFrom: <sip:5000@172.20.11.172>;tag=-iPr1gnTo: <sip:1004@172.20.11.172>;tag=TNzDNgaNNCSeq: 111 BYECall-ID: q0KGluu3SrRoute: <sip:192.168.10.10;r2=on;lr=on;nat=v46>Route: <sip:172.20.11.172;r2=on;lr=on;nat=v46>Route: <sip:172.20.11.172;lr=on;nat=yes> Kamailio replies with 404 Not Here192.168.10.10 --> 192.168.10.20--------------Internet Protocol Version 4, Src: 192.168.10.10 (192.168.10.10), Dst: 192.168.10.20 (192.168.10.20)User Datagram Protocol, Src Port: sip (5060), Dst Port: 6090 (6090)Session Initiation Protocol (404)Status-Line: SIP/2.0 404 Not hereMessage HeaderVia: SIP/2.0/UDP 192.168.10.20:6090;branch=z9hG4bK.20aa9gXIY;rport=6090From: <sip:5000@172.20.11.172>;tag=-iPr1gnTo: <sip:1004@172.20.11.172>;tag=TNzDNgaNNCSeq: 111 BYECall-ID: q0KGluu3SrServer: kamailio (4.1.5 (i386/linux))Content-Length: 0 ----Messaggio originale---- Da: davy.van.de.moere(a)gmail.com Data: 22-set-2014 13.52 A: "marino.mileti(a)alice.it"<marino.mileti(a)alice.it>, "Kamailio (SER) - Users Mailing List"<sr-users(a)lists.sip-router.org> Ogg: Re: [SR-Users] Kamailio multihomed - BYE problem Could you show us some SIP headers? 2014-09-22 13:50 GMT+02:00 davy van de moere <davy.van.de.moere(a)gmail.com>: A very long shot, look into handle_ruri_alias(). 2014-09-22 12:58 GMT+02:00 marino.mileti(a)alice.it <marino.mileti(a)alice.it>: Hi, I'm having a problem with routing of BYEs in my multi homed Kamailio. My setup is a Kamailio v4.1.5 with two NIC (172.20.11.0 & 192.168.10.0) and three phones. Two phones (1 for each LAN) are in a group, so using alias_db I can call them in parallel mode. Caller is on 172.20 network...When I answer from phone on 192.168.10.0, RTP is ok ... but on BYE Kamailio replies with 404 Not Here...and the RURI of BYE has the IP of Kamailio instead the IP of the callee.When I answer from phone on 172.20.11.0, RTP is still ok and also BYE is managed correctly from Kamailio and the RURI of BYE has the IP of the callee. How can i solve this issue?Many thanks _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

Kamailio multihomed - BYE problem
by marino.mileti＠alice.it 22 Sep '14

22 Sep '14

Hi, I'm having a problem with routing of BYEs in my multi homed Kamailio. My setup is a Kamailio v4.1.5 with two NIC (172.20.11.0 & 192.168.10.0) and three phones. Two phones (1 for each LAN) are in a group, so using alias_db I can call them in parallel mode. Caller is on 172.20 network...When I answer from phone on 192.168.10.0, RTP is ok ... but on BYE Kamailio replies with 404 Not Here...and the RURI of BYE has the IP of Kamailio instead the IP of the callee.When I answer from phone on 172.20.11.0, RTP is still ok and also BYE is managed correctly from Kamailio and the RURI of BYE has the IP of the callee. How can i solve this issue?Many thanks

2 2

Re: [SR-Users] [OT] Accounting Drouting Gateway Selection
by Dan Christian Bogos 22 Sep '14

22 Sep '14

Hi Spencer, We use a similar approach as yours and use 302 Redirects coming from Kamailio instead of proxying the call (in our case we do it via LCR module in Kamailio). In FreeSWITCH you can then manually route these redirects and get your CDR data out of it. Cheers, DanB On 22.09.2014 12:00, sr-users-request(a)lists.sip-router.org wrote: > On 18/09/14 17:34, Spencer Thomason wrote: >> >Hello all, >> >I have a need to determine which calls go to which gateway. The challenge is that CDRs are produced by a FreeSWITCH instance upstream of a provider side Kamailio proxy that handles route selection via drouting module. The topology is like this: >> > >> >customer proxy -> FS [1-N] (accounting) -> carrier proxy (route selection) >> > >> >Does anyone have any ideas how to make the FreeSWITCH instances aware of which gateway actually received the call?

1 0

Jump to page:

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