<div dir="ltr"><div dir="ltr">Hi Cumhur,<br><div><br></div><div>ruri.hostport won't return the de-facto IPv[4,6] address if the RURI contains a domain name, that's why ppl have suggested to use the <b>onsend_route</b>, as it's the only route where the IP is exposed after DNS resolver is performed following the t_relay() or forward().</div><div><br></div><div>Cheers. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 21, 2020 at 8:16 AM CUMHUR KARAHAN <<a href="mailto:cumhur.karahan@consultant.turkcell.com.tr">cumhur.karahan@consultant.turkcell.com.tr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi again,<br>
<br>
I used $sel(ruri.hostport) for Kamailio1 after t_relay in Relay route. So I managed to get the request-line URI's IP and port parameters of the outgoing INVITE that is leaving the first Kamailio box.<br>
<br>
Thank you very much.<br>
<br>
-----Original Message-----<br>
From: sr-users <<a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank">sr-users-bounces@lists.kamailio.org</a>> On Behalf Of CUMHUR KARAHAN<br>
Sent: 17 Ocak 2020 Cuma 15:23<br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: Re: [SR-Users] Get destination IP from forwarded invite<br>
<br>
Hi Joel,<br>
<br>
Thank you for your response. <br>
<br>
In fact, I want to get Request-line URI's parameters of the outgoing INVITE that is leaving the first Kamailio box, briefly. Unfortunately "du - destination URL" or "sndto(name)" pseudo-variables indicate the next hope's information. And in this case, the next hope's information is not same as the ClientB's information.<br>
<br>
As I tried to tell before, our setup is like that:<br>
<br>
ClientA -> Kamailio1 -> Kamailio2 -> ClientB<br>
<br>
I need the request line URI parameters of the invite message sent by Kamailio1 to Kamailio2. And these parameters contain ClientB's ip and port information such as <a href="http://10.252.180.51:36945" rel="noreferrer" target="_blank">10.252.180.51:36945</a> as you can see below:<br>
<br>
INVITE <a href="mailto:sip%3A905364167881@10.252.180." target="_blank">sip:905364167881@10.252.180.</a>51:36945;transport=tls SIP/2.0<br>
Record-Route: <sip:gearbox11.turkcell.tgc:5060;r2=on;lr;did=7f5.f572;nat=yes><br>
Record-Route: <sip:testsip05.tvoip.turkcell.com.tr:443;transport=tls;r2=on;lr;did=7f5.f572;nat=yes><br>
Via: SIP/2.0/UDP gearbox11.turkcell.tgc:5060;branch=z9hG4bK67ad.4e8e863f2475ab8d3053af0593548557.1;i=f<br>
Via: SIP/2.0/TLS 100.64.13.139:56993;received=212.252.34.165;branch=z9hG4bK.1SYkXD1Me;rport=32980<br>
From: <<a href="mailto:sip%3A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905368601286@testsip.tvoip.turkcell.com.tr</a>>;tag=WbINy0ypx<br>
To: <a href="mailto:sip%3A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr</a><br>
CSeq: 21 INVITE<br>
Call-ID: 1wF-vjzGIX<br>
...<br>
<br>
And, your question: no, we don't use the dispatcher mechanism. We just check the DB to find out Kamailio server which the number registered into and send the messages to this server basically. <br>
<br>
Thanks for all...<br>
<br>
<br>
-----Original Message-----<br>
From: sr-users <<a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank">sr-users-bounces@lists.kamailio.org</a>> On Behalf Of <a href="mailto:sr-users-request@lists.kamailio.org" target="_blank">sr-users-request@lists.kamailio.org</a><br>
Sent: 17 Ocak 2020 Cuma 14:00<br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: sr-users Digest, Vol 176, Issue 17<br>
<br>
Send sr-users mailing list submissions to<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sr-users-request@lists.kamailio.org" target="_blank">sr-users-request@lists.kamailio.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sr-users-owner@lists.kamailio.org" target="_blank">sr-users-owner@lists.kamailio.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Get destination IP from forwarded invite (CUMHUR KARAHAN)<br>
2. Re: Kamalio + RTP Engine + SIP Client behind NAT (Richard Fuchs)<br>
3. Re: Get destination IP from forwarded invite (Joel Serrano)<br>
4. Re: Kamalio + RTP Engine + SIP Client behind NAT<br>
(Nuno Miguel Reis)<br>
5. Re: Kamailio/RTC dinner at Fosdem 2020 (Federico Santulli)<br>
6. Re: http_client interface (Daniel-Constantin Mierla)<br>
7. Re: Kamailio stop to process incoming SIP traffic via TCP.<br>
(adeykunov)<br>
8. Question about xhttp module kamailio 5.2.x (Jimmy Rodley)<br>
9. Trouble with 302 Redirect (Jim Leahy)<br>
10. Re: Kamalio + RTP Engine + SIP Client behind NAT (Richard Fuchs)<br>
11. Re: http_client interface (Fred Posner)<br>
12. Re: Trouble with 302 Redirect (Alex Balashov)<br>
13. UCaaS Platform (Dario Vargas)<br>
14. Re: [commercial announcement] (Henning Westerholt)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 16 Jan 2020 11:45:15 +0000<br>
From: CUMHUR KARAHAN <<a href="mailto:cumhur.karahan@consultant.turkcell.com.tr" target="_blank">cumhur.karahan@consultant.turkcell.com.tr</a>><br>
To: "<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>" <<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: [SR-Users] Get destination IP from forwarded invite<br>
Message-ID:<br>
<<a href="mailto:319901a90d17413292ad249eb56df2ec@consultant.turkcell.com.tr" target="_blank">319901a90d17413292ad249eb56df2ec@consultant.turkcell.com.tr</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Hi all,<br>
<br>
I'm a newbie for Kamailio and working on a feature needs end-users' destination IP in the first transferred/forwarded invite message.<br>
<br>
Basically, our system/call flow is like:<br>
ClientA -> Kamailio1 -> Kamailio2 -> ClientB<br>
<br>
Invite from the clientA:<br>
<br>
tls:<a href="http://212.252.34.165:32980" rel="noreferrer" target="_blank">212.252.34.165:32980</a><br>
tls:<a href="http://172.21.193.100:5061" rel="noreferrer" target="_blank">172.21.193.100:5061</a><br>
INVITE <a href="http://sip:905364167881@testsip.tvoip.turkcell.com.tr:443" rel="noreferrer" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr:443</a> SIP/2.0<br>
Via: SIP/2.0/TLS 100.64.13.139:56993;branch=z9hG4bK.GoiTxA4Ee;rport<br>
From: <<a href="mailto:sip%3A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905368601286@testsip.tvoip.turkcell.com.tr</a>>;tag=WbINy0ypx<br>
To: <a href="mailto:sip%3A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr</a><br>
CSeq: 20 INVITE<br>
...<br>
<br>
Needed Ip (Client B's IP 10.252.180.51 for this case) is in the INVITE row of the forwarded message.<br>
<br>
Invite to the Kamailio2 :<br>
<br>
udp:<a href="http://172.21.193.100:5060" rel="noreferrer" target="_blank">172.21.193.100:5060</a><br>
udp:<a href="http://172.21.193.98:5060" rel="noreferrer" target="_blank">172.21.193.98:5060</a><br>
INVITE <a href="mailto:sip%3A905364167881@10.252.180." target="_blank">sip:905364167881@10.252.180.</a>51:36945;transport=tls SIP/2.0<br>
Record-Route: <sip:gearbox11.turkcell.tgc:5060;r2=on;lr;did=7f5.f572;nat=yes><br>
Record-Route: <sip:testsip05.tvoip.turkcell.com.tr:443;transport=tls;r2=on;lr;did=7f5.f572;nat=yes><br>
Via: SIP/2.0/UDP gearbox11.turkcell.tgc:5060;branch=z9hG4bK67ad.4e8e863f2475ab8d3053af0593548557.1;i=f<br>
Via: SIP/2.0/TLS 100.64.13.139:56993;received=212.252.34.165;branch=z9hG4bK.1SYkXD1Me;rport=32980<br>
From: <<a href="mailto:sip%3A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905368601286@testsip.tvoip.turkcell.com.tr</a>>;tag=WbINy0ypx<br>
To: <a href="mailto:sip%3A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr</a><br>
CSeq: 21 INVITE<br>
...<br>
<br>
When the first invite message receives, the dialog variables or sel(msg...) parsed values belong to this first received message, as far as I understand during the tests. However I need the forwarded invite message's variables. Even after t_relay in RELAY route, it looks the message I have is the first one. So, I cannot reach this later IP in the forwarded invite message. As far as I understand, bear with me here please, this IP manipulation executes in t_relay function and in the C side of Kamailio. So, I cannot find a way to do that in the our native scripts.<br>
<br>
Is there any way to get it without diving C code's abyss? Do you have any idea about it? I would appreciate it, if I can get any help or any clue.<br>
<br>
Thanks for all...<br>
<br>
S. Cumhur Karahan<br>
<br>
<br>
<br>
[<a href="http://s.turkcell.com.tr/SiteAssets/Genel/mail-imza.jpg" rel="noreferrer" target="_blank">http://s.turkcell.com.tr/SiteAssets/Genel/mail-imza.jpg</a>] <<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fturkcell.li%2fncfYh&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-bbcefdc4443d64fef548126bd3c5f932d722a0a4" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fturkcell.li%2fncfYh&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-bbcefdc4443d64fef548126bd3c5f932d722a0a4</a>><br>
<br>
Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.<br>
<br>
TURKCELL bu mesajin icerdigi bilgilerin do?rulu?u veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir<br>
<br>
Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir.<br>
<br>
________________________________<br>
<br>
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted.<br>
<br>
TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL.<br>
<br>
This e-mail has been scanned for all known computer viruses.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/37a3c32b/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/37a3c32b/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.gif<br>
Type: image/gif<br>
Size: 92 bytes<br>
Desc: image001.gif<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/37a3c32b/attachment-0001.gif" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/37a3c32b/attachment-0001.gif</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 16 Jan 2020 08:23:21 -0500<br>
From: Richard Fuchs <<a href="mailto:rfuchs@sipwise.com" target="_blank">rfuchs@sipwise.com</a>><br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: Re: [SR-Users] Kamalio + RTP Engine + SIP Client behind NAT<br>
Message-ID: <<a href="mailto:4686712f-d865-c6c9-11ac-649966b867b1@sipwise.com" target="_blank">4686712f-d865-c6c9-11ac-649966b867b1@sipwise.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
On 15/01/2020 13.39, Nuno Miguel Reis wrote:<br>
> Hi guys.<br>
><br>
> I'm replacing a environment where I was using kamailio + freeswitch by <br>
> another where I'm adding rtpengine to the mix.<br>
> One of the issues I'm having now is when I have a SIP Client behind NAT:<br>
><br>
> When I send the INVITE from the SIP Client, the SDP is using the <br>
> private LAN IP address + the advertised media port, let's admit it's<br>
> <a href="http://10.10.10.10:5000" rel="noreferrer" target="_blank">10.10.10.10:5000</a> <<a href="http://10.10.10.10:5000" rel="noreferrer" target="_blank">http://10.10.10.10:5000</a>> when the call establishes <br>
> with a public server running kamailio + rtpengine, the actual RTP <br>
> arrives from the home router public IP on a natted port, let's admit <br>
> it's <a href="http://100.100.100.100:65100" rel="noreferrer" target="_blank">100.100.100.100:65100</a> <br>
> <<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt</a><br>
> p%3a%2f%2f100.100.100.100%3a65100&umid=39581E1E-9C53-E505-96A6-E057F22<br>
> BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-193c6dfa2da7d1ac0c<br>
> 93d1a002e73781a0a22d9e>, event though, RTPENGINE assumes that RTP<br>
> stream is coming from<br>
> 100.100.100.100<br>
> <<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt</a><br>
> p%3a%2f%2f100.100.100.100&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&au<br>
> th=cbd2d006abdb2241308511f72807fe0bc6594b4a-9e365df6d282d7bf1e79e91e70<br>
> 73c5a94aed6d82>:5000.I'm using the '--sip-source' with RTPENGINE to<br>
> make it use the received ip address instead of the private IP coming in the SDP but I'm not finding anything to make RTPENGINE adapt an start sending the RTP FLOW to the port where he starts receiving the RTP flow from, discarding the SDP media port information.<br>
<br>
Rtpengine does this automatically, unless the `asymmetric` flag is used. <br>
You should see a log message about a `confirmed peer address` as soon as the first RTP is received on a port.<br>
<br>
Cheers<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/483ec5d0/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/483ec5d0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 16 Jan 2020 07:23:28 -0800<br>
From: Joel Serrano <<a href="mailto:joel@textplus.com" target="_blank">joel@textplus.com</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] Get destination IP from forwarded invite<br>
Message-ID:<br>
<CAMtXxQmmRb-ieA9T+0ofxAxiOd23w_0nHos=<a href="mailto:nZOy9-JNRahnfA@mail.gmail.com" target="_blank">nZOy9-JNRahnfA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello,<br>
<br>
If I understand correctly your email, you want the IP/Host of the destination of the outgoing INVITE that is leaving a Kamailio box?<br>
<br>
First of all, how are you forwarding the request? Are you using dispatcher module?<br>
<br>
Here are a couple of options:<br>
<br>
1-<br>
<a href="https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#du_-_destination_uri" rel="noreferrer" target="_blank">https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#du_-_destination_uri</a><br>
(although<br>
this depends on your config, it might not be set)<br>
<br>
2- <a href="https://www.kamailio.org/wiki/cookbooks/5.3.x/core#onsend_route" rel="noreferrer" target="_blank">https://www.kamailio.org/wiki/cookbooks/5.3.x/core#onsend_route</a> + <a href="https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#sndto_name" rel="noreferrer" target="_blank">https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#sndto_name</a><br>
<br>
<br>
If you can describe a little more how you are doing things we might be able to give you more information.<br>
<br>
Joel.<br>
<br>
<br>
On Thu, Jan 16, 2020 at 3:53 AM CUMHUR KARAHAN < <a href="mailto:cumhur.karahan@consultant.turkcell.com.tr" target="_blank">cumhur.karahan@consultant.turkcell.com.tr</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
><br>
><br>
> I’m a newbie for Kamailio and working on a feature needs end-users’<br>
> destination IP in the first transferred/forwarded invite message.<br>
><br>
><br>
><br>
> Basically, our system/call flow is like:<br>
><br>
> ClientA -> Kamailio1 -> Kamailio2 -> ClientB<br>
><br>
><br>
><br>
> Invite from the clientA:<br>
><br>
><br>
><br>
> *tls:<a href="http://212.252.34.165:32980" rel="noreferrer" target="_blank">212.252.34.165:32980</a> <br>
> <<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt</a><br>
> p%3a%2f%2f212.252.34.165%3a32980&umid=39581E1E-9C53-E505-96A6-E057F22B<br>
> D18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-d4b503e38b32fd4dee8<br>
> 59434f30f8c5f3e832496>*<br>
><br>
> *tls:<a href="http://172.21.193.100:5061" rel="noreferrer" target="_blank">172.21.193.100:5061</a> <<a href="http://172.21.193.100:5061" rel="noreferrer" target="_blank">http://172.21.193.100:5061</a>>*<br>
><br>
> *INVITE <a href="http://sip:905364167881@testsip.tvoip.turkcell.com.tr:443" rel="noreferrer" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr:443</a><br>
> <<a href="http://sip:905364167881@testsip.tvoip.turkcell.com.tr:443" rel="noreferrer" target="_blank">http://sip:905364167881@testsip.tvoip.turkcell.com.tr:443</a>> SIP/2.0*<br>
><br>
> *Via: SIP/2.0/TLS 100.64.13.139:56993;branch=z9hG4bK.GoiTxA4Ee;rport*<br>
><br>
> *From: <<a href="mailto:sip%3A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905368601286@testsip.tvoip.turkcell.com.tr</a><br>
> <<a href="mailto:sip%253A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip%3A905368601286@testsip.tvoip.turkcell.com.tr</a>>>;tag=WbINy0ypx*<br>
><br>
> *To: <a href="mailto:sip%3A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr</a><br>
> <<a href="mailto:sip%253A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip%3A905364167881@testsip.tvoip.turkcell.com.tr</a>>*<br>
><br>
> *CSeq: 20 INVITE*<br>
><br>
> *…*<br>
><br>
><br>
><br>
> Needed Ip (Client B’s IP 10.252.180.51 for this case) is in the INVITE <br>
> row of the forwarded message.<br>
><br>
><br>
><br>
> Invite to the Kamailio2 :<br>
><br>
><br>
><br>
> *udp:<a href="http://172.21.193.100:5060" rel="noreferrer" target="_blank">172.21.193.100:5060</a> <<a href="http://172.21.193.100:5060" rel="noreferrer" target="_blank">http://172.21.193.100:5060</a>>*<br>
><br>
> *udp:<a href="http://172.21.193.98:5060" rel="noreferrer" target="_blank">172.21.193.98:5060</a> <<a href="http://172.21.193.98:5060" rel="noreferrer" target="_blank">http://172.21.193.98:5060</a>>*<br>
><br>
> *INVITE sip:905364167881@**10.252.180.51**:36945;transport=tls <br>
> SIP/2.0*<br>
><br>
> *Record-Route:<br>
> <sip:gearbox11.turkcell.tgc:5060;r2=on;lr;did=7f5.f572;nat=yes>*<br>
><br>
> *Record-Route:<br>
> <sip:testsip05.tvoip.turkcell.com.tr:443;transport=tls;r2=on;lr;did=7f<br>
> 5.f572;nat=yes>*<br>
><br>
> *Via: SIP/2.0/UDP<br>
> gearbox11.turkcell.tgc:5060;branch=z9hG4bK67ad.4e8e863f2475ab8d3053af0<br>
> 593548557.1;i=f*<br>
><br>
> *Via: SIP/2.0/TLS<br>
> 100.64.13.139:56993;received=212.252.34.165;branch=z9hG4bK.1SYkXD1Me;r<br>
> port=32980*<br>
><br>
> *From: <<a href="mailto:sip%3A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905368601286@testsip.tvoip.turkcell.com.tr</a><br>
> <<a href="mailto:sip%253A905368601286@testsip.tvoip.turkcell.com.tr" target="_blank">sip%3A905368601286@testsip.tvoip.turkcell.com.tr</a>>>;tag=WbINy0ypx*<br>
><br>
> *To: <a href="mailto:sip%3A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip:905364167881@testsip.tvoip.turkcell.com.tr</a><br>
> <<a href="mailto:sip%253A905364167881@testsip.tvoip.turkcell.com.tr" target="_blank">sip%3A905364167881@testsip.tvoip.turkcell.com.tr</a>>*<br>
><br>
> *CSeq: 21 INVITE*<br>
><br>
> *…*<br>
><br>
><br>
><br>
> When the first invite message receives, the dialog variables or <br>
> sel(msg…) parsed values belong to this first received message, as far <br>
> as I understand during the tests. However I need the forwarded invite message’s variables.<br>
> Even after t_relay in RELAY route, it looks the message I have is the <br>
> first one. So, I cannot reach this later IP in the forwarded invite <br>
> message. As far as I understand, bear with me here please, this IP <br>
> manipulation executes in t_relay function and in the C side of <br>
> Kamailio. So, I cannot find a way to do that in the our native scripts.<br>
><br>
><br>
><br>
> Is there any way to get it without diving C code’s abyss? Do you have <br>
> any idea about it? I would appreciate it, if I can get any help or any clue.<br>
><br>
><br>
><br>
> Thanks for all...<br>
><br>
><br>
><br>
> S. Cumhur Karahan<br>
><br>
><br>
><br>
><br>
> <<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=htt</a><br>
> p%3a%2f%<a href="http://2fturkcell.li" rel="noreferrer" target="_blank">2fturkcell.li</a>%2fncfYh&umid=39581E1E-9C53-E505-96A6-E057F22BD18<br>
> D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-bbcefdc4443d64fef54812<br>
> 6bd3c5f932d722a0a4><br>
><br>
> Bu elektronik posta ve onunla iletilen butun dosyalar sadece <br>
> gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel <br>
> kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu <br>
> elektronik postanin icerigini aciklamaniz, kopyalamaniz, <br>
> yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.<br>
><br>
> TURKCELL bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu <br>
> konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin <br>
> ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve <br>
> saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca <br>
> gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir<br>
><br>
> Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir.<br>
> ------------------------------<br>
><br>
> This e-mail and any files transmitted with it are confidential and <br>
> intended solely for the use of the individual or entity to whom they <br>
> are addressed. If you are not the intended recipient you are hereby <br>
> notified that any dissemination, forwarding, copying or use of any of <br>
> the information is strictly prohibited, and the e-mail should <br>
> immediately be deleted.<br>
><br>
> TURKCELL makes no warranty as to the accuracy or completeness of any <br>
> information contained in this message and hereby excludes any <br>
> liability of any kind for the information contained therein or for the <br>
> information transmission, reception, storage or use of such in any way <br>
> whatsoever. The opinions expressed in this message belong to sender <br>
> alone and may not necessarily reflect the opinions of TURKCELL.<br>
><br>
> This e-mail has been scanned for all known computer viruses.<br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/682b8d5d/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/682b8d5d/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.gif<br>
Type: image/gif<br>
Size: 92 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/682b8d5d/attachment-0001.gif" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/682b8d5d/attachment-0001.gif</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 16 Jan 2020 17:29:53 +0000<br>
From: Nuno Miguel Reis <<a href="mailto:nmreis@student.dei.uc.pt" target="_blank">nmreis@student.dei.uc.pt</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] Kamalio + RTP Engine + SIP Client behind NAT<br>
Message-ID:<br>
<CAGTw3V7Y8pHD+a8psPL7Tah=<a href="mailto:HTgrmvVRPhPBKB9VCuoujX_Nnw@mail.gmail.com" target="_blank">HTgrmvVRPhPBKB9VCuoujX_Nnw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi again.<br>
<br>
Thanks for all the help and suggestions. I realized the issue happens if using kernel forwarding only. If I change rtpengine to start at userspace without the kernel module enabled everything works fine as expected.<br>
Do you have any hints on why this could be happening with the kernel module?<br>
<br>
I'm running rtpengine like this:<br>
<br>
usersapece: $ rtpengine -f -L 7 --interface=100.100.100.100 --listen-ng=<br>
<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">127.0.0.1:2223</a> --tos=184 --sip-source<br>
<br>
kernel: $ rtpengine -f -L 7 --table=0 --interface=100.100.100.100<br>
--listen-ng=<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">127.0.0.1:2223</a> --tos=184 --no-fallback --sip-source<br>
<br>
<br>
when using kernel module, I'm also setting this rules on chain INPUT under<br>
iptables:<br>
<br>
-A INPUT -p udp -m udp --dport 5000:16383 -j RTPENGINE --id 0 -A INPUT -p udp -m udp --dport 16384:32768 -j RTPENGINE --id 0 -A INPUT -p udp -m udp --dport 49152:65535 -j RTPENGINE --id 0<br>
<br>
<br>
Looking forward to hear from you guys.<br>
<br>
Regards,<br>
<br>
--<br>
Nuno Miguel Reis<br>
Departamento de Engenharia Informática<br>
Faculdade de Ciências e Tecnologia<br>
Universidade de Coimbra<br>
<br>
<br>
On Thu, Jan 16, 2020 at 1:23 PM Richard Fuchs <<a href="mailto:rfuchs@sipwise.com" target="_blank">rfuchs@sipwise.com</a>> wrote:<br>
<br>
> On 15/01/2020 13.39, Nuno Miguel Reis wrote:<br>
><br>
> Hi guys.<br>
><br>
> I'm replacing a environment where I was using kamailio + freeswitch by <br>
> another where I'm adding rtpengine to the mix.<br>
> One of the issues I'm having now is when I have a SIP Client behind NAT:<br>
><br>
> When I send the INVITE from the SIP Client, the SDP is using the <br>
> private LAN IP address + the advertised media port, let's admit it's<br>
> <a href="http://10.10.10.10:5000" rel="noreferrer" target="_blank">10.10.10.10:5000</a> when the call establishes with a public server <br>
> running kamailio + rtpengine, the actual RTP arrives from the home <br>
> router public IP on a natted port, let's admit it's <br>
> <a href="http://100.100.100.100:65100" rel="noreferrer" target="_blank">100.100.100.100:65100</a>, event though, RTPENGINE assumes that RTP stream is coming from <a href="http://100.100.100.100:5000" rel="noreferrer" target="_blank">100.100.100.100:5000</a>.<br>
> I'm using the '--sip-source' with RTPENGINE to make it use the <br>
> received ip address instead of the private IP coming in the SDP but <br>
> I'm not finding anything to make RTPENGINE adapt an start sending the <br>
> RTP FLOW to the port where he starts receiving the RTP flow from, <br>
> discarding the SDP media port information.<br>
><br>
> Rtpengine does this automatically, unless the `asymmetric` flag is used.<br>
> You should see a log message about a `confirmed peer address` as soon <br>
> as the first RTP is received on a port.<br>
><br>
> Cheers<br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/d61a6989/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/d61a6989/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 16 Jan 2020 20:45:04 +0100<br>
From: Federico Santulli <<a href="mailto:kam.list@nhm.it" target="_blank">kam.list@nhm.it</a>><br>
To: <a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>, "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Cc: "<a href="mailto:business@lists.kamailio.org" target="_blank">business@lists.kamailio.org</a>" <<a href="mailto:business@lists.kamailio.org" target="_blank">business@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] Kamailio/RTC dinner at Fosdem 2020<br>
Message-ID: <<a href="mailto:54CDD921-48D2-47F0-935E-0B181F037774@nhm.it" target="_blank">54CDD921-48D2-47F0-935E-0B181F037774@nhm.it</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi Daniel,<br>
<br>
We would like to join the dinner, 3 people from US.<br>
<br>
Kind regards.<br>
<br>
Federico Santulli<br>
<br>
NHM - S.R.L.<br>
Via Raffaello Sanzio, 88<br>
81031 Aversa (CE)<br>
Italy<br>
<br>
<br>
> Il giorno 9 gen 2020, alle ore 09:52, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>> ha scritto:<br>
> <br>
> Hello,<br>
> <br>
> Fosdem 2020 is approaching, there will be a talk from Henning about <br>
> Kamailio, many other friends and related projects are presenting in <br>
> the RTC Devroom (Giacomo Vacca and Federico Cabiddu, Wazo, Asterisk, <br>
> Homer, Janus, Jitsi, CGRateS, Linphone, ...):<br>
> <br>
> * <a href="https://fosdem.org/2020/schedule/track/real_time_communications/" rel="noreferrer" target="_blank">https://fosdem.org/2020/schedule/track/real_time_communications/</a><br>
> <br>
> I plan to be at the event and wondering if there are enough interested <br>
> participants for having the traditional Kamailio/RTC dinner. If yes, <br>
> Torrey will help to book a place to accommodate us (first choice could <br>
> be the same restaurant like the last year, if available).<br>
> <br>
> Reply if you want to join the dinner and say how many other people are <br>
> joining you.<br>
> <br>
> Cheers,<br>
> Daniel<br>
> <br>
> --<br>
> Daniel-Constantin Mierla -- <a href="http://www.asipto.com" rel="noreferrer" target="_blank">www.asipto.com</a> <a href="http://www.twitter.com/miconda" rel="noreferrer" target="_blank">www.twitter.com/miconda</a> -- <br>
> <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">www.linkedin.com/in/miconda</a> Kamailio World Conference - April 27-29, <br>
> 2020, in Berlin -- <br>
> <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www</a>.<br>
> <a href="http://kamailioworld.com" rel="noreferrer" target="_blank">kamailioworld.com</a>&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d<br>
> 006abdb2241308511f72807fe0bc6594b4a-ac4b2b5016612d36d9bf3bf438b6b436b1<br>
> f1ae8e<br>
> <br>
> <br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 16 Jan 2020 22:56:03 +0100<br>
From: Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>>, Fred Posner <<a href="mailto:fred@palner.com" target="_blank">fred@palner.com</a>><br>
Subject: Re: [SR-Users] http_client interface<br>
Message-ID: <<a href="mailto:4ab3422e-c3d6-7d85-fb3e-53b09bfa6c1a@gmail.com" target="_blank">4ab3422e-c3d6-7d85-fb3e-53b09bfa6c1a@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
The libcurl seems to offer an option for that as well:<br>
<br>
- <a href="https://curl.haxx.se/libcurl/c/CURLOPT_INTERFACE.html" rel="noreferrer" target="_blank">https://curl.haxx.se/libcurl/c/CURLOPT_INTERFACE.html</a><br>
<br>
So it can be a small patch to the module and support it in the future.<br>
<br>
If you look for a solution on current stable, maybe one of the embedded scripting languages can help, you can execute inline a small script in Lua/Python/Perl with app_lua_run() & equivalents. In the past I used the http client from lua to do more complex http api queries (e.g., with specific headers, ...).<br>
<br>
Cheers,<br>
Daniel<br>
<br>
On 13.01.20 17:00, Fred Posner wrote:<br>
> I'd never had a reason to before, but on a deployment I need http <br>
> messages to go out a specific interface. Curl has an --interface <br>
> option, but I don't see how to do the same with http_client. Unless <br>
> I'm missing something...<br>
><br>
> Anyone ever do something like this?<br>
><br>
--<br>
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" rel="noreferrer" target="_blank">www.asipto.com</a> <a href="http://www.twitter.com/miconda" rel="noreferrer" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">www.linkedin.com/in/miconda</a> Kamailio World Conference - April 27-29, 2020, in Berlin -- <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www.kamailioworld.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-ac4b2b5016612d36d9bf3bf438b6b436b1f1ae8e" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www.kamailioworld.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-ac4b2b5016612d36d9bf3bf438b6b436b1f1ae8e</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 16 Jan 2020 09:49:40 -0700 (MST)<br>
From: adeykunov <<a href="mailto:adeykunov@intermedia.net" target="_blank">adeykunov@intermedia.net</a>><br>
To: <a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
Subject: Re: [SR-Users] Kamailio stop to process incoming SIP traffic<br>
via TCP.<br>
Message-ID: <<a href="mailto:1579193380553-0.post@n5.nabble.com" target="_blank">1579193380553-0.post@n5.nabble.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Daniel,<br>
<br>
Got the same issue on 5.3.1 with openssl1.1, debian9.<br>
After 3 working days of tests (about ~30-50 wss clients), suddenly we've got<br>
a lot of connections stucked in CLOSE_WAIT state. Kamailio called<br>
sig_alarm_abort() when we try to reboot.<br>
<br>
Thanks,<br>
Andrey<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a href="http://sip-router.1086192.n5.nabble.com/Users-f3.html" rel="noreferrer" target="_blank">http://sip-router.1086192.n5.nabble.com/Users-f3.html</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Thu, 16 Jan 2020 22:02:40 +0000 (UTC)<br>
From: Jimmy Rodley <<a href="mailto:jimmyrodley@yahoo.com" target="_blank">jimmyrodley@yahoo.com</a>><br>
To: "<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>" <<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: [SR-Users] Question about xhttp module kamailio 5.2.x<br>
Message-ID: <<a href="mailto:443353431.8467378.1579212160245@mail.yahoo.com" target="_blank">443353431.8467378.1579212160245@mail.yahoo.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
I am on kamailio 5.2.4 and want to use the xhttp module for certain management operations.<br>
The request involves some DB queries . The DB is remote and via ODBC and might have some delay.The documentation on the xhttp module states about latency <a href="http://kamailio.org/docs/modules/devel/modules/xhttp.html" rel="noreferrer" target="_blank">http://kamailio.org/docs/modules/devel/modules/xhttp.html</a> mentioning that the request is handled in an asynchronous manner. <br>
However, the JSONRPC-S module documentation says that this module implements the support for asynchronous RPC commands only for HTTP and HTTPS transports.<br>
<br>
<a href="https://www.kamailio.org/docs/modules/devel/modules/jsonrpcs.html#idm1049416972" rel="noreferrer" target="_blank">https://www.kamailio.org/docs/modules/devel/modules/jsonrpcs.html#idm1049416972</a><br>
<br>
I am confused about the process under whose context the xttp request . Can there be a dedicated process to handle certain management requests which do some custom instructions like certain DB operations or initiate certain http requests ?<br>
Thanks,Rupesh<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/f581f9a0/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/f581f9a0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Thu, 16 Jan 2020 15:54:54 -0500<br>
From: Jim Leahy <<a href="mailto:rickfromsunnyvale@gmail.com" target="_blank">rickfromsunnyvale@gmail.com</a>><br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: [SR-Users] Trouble with 302 Redirect<br>
Message-ID:<br>
<CAH3xi0-AEEj_bwLYd4OzSH96Cz8=<a href="mailto:qyrdsNWTjWnf5Sm1efrvhg@mail.gmail.com" target="_blank">qyrdsNWTjWnf5Sm1efrvhg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi All,<br>
I'm having some issues trying to properly send a '302 Moved Temporarily'<br>
reply to the calling UAC (UAC1) when the remote UAC (UAC2) returns a 486<br>
status (Do Not Disturb). The goal is to redirect UAC1 to a voicemail server<br>
when UAC2 is in DND.<br>
Here are the pertinent parts of my config:<br>
<br>
route {<br>
# drop some things right away<br>
route(DROP);<br>
<br>
# perform sanity check<br>
route(SANITYCHECK);<br>
<br>
# handle registrations<br>
if(is_method("REGISTER")) {<br>
route(REGISTRATION);<br>
exit;<br>
}<br>
<br>
# handle invites<br>
if(is_method("INVITE")) {<br>
route("INVITE");<br>
exit;<br>
}<br>
<br>
route(RELAY);<br>
}<br>
<br>
route[INVITE] {<br>
# add this proxy to the record-route so it stays in the loop<br>
record_route();<br>
<br>
# if we can find this user in the location DB...<br>
if(lookup("location")) {<br>
# relay the invite to the new dURI<br>
t_on_failure("FOURDIGITFAIL");<br>
t_on_reply("FOURDIGITREPLY");<br>
route(RELAY);<br>
# go back to the main route<br>
return;<br>
}<br>
<br>
onreply_route[FOURDIGITREPLY] {<br>
if(t_check_status("4[0-9]{2}")) {<br>
t_reply("302", "Moved Temporarily");<br>
}<br>
}<br>
<br>
I'm having issues with the t_reply in the onreply_route. It successfully<br>
sends the reply, but I can't seem to set the Contact header properly. I'm<br>
trying to set it to the location of the user's mailbox on the voicemail<br>
sever (ie <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>), but nothing I try works. I've tried:<br>
remove_hf("Contact");<br>
insert_hf("Contact: <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>");<br>
t_reply("302", "Moved Temporarily");<br>
<br>
But as I understand it, that just changes the header in the reply from<br>
UAC2, not the reply I'm sending to UAC1<br>
<br>
Then I tried:<br>
append_to_reply("Contact: <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>" );<br>
t_reply("302", "Moved Temporarily");<br>
<br>
But I can't use append_to_reply in an onreply block.<br>
How can I change the Contact header in the reply that's sent? Am I just<br>
going about this the wrong way? Any help would be appreciated. Thanks<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/66fc8ba2/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/66fc8ba2/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Thu, 16 Jan 2020 17:10:06 -0500<br>
From: Richard Fuchs <<a href="mailto:rfuchs@sipwise.com" target="_blank">rfuchs@sipwise.com</a>><br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: Re: [SR-Users] Kamalio + RTP Engine + SIP Client behind NAT<br>
Message-ID: <<a href="mailto:0b704a3c-afc4-3ca0-8d8b-38e2d70bcae9@sipwise.com" target="_blank">0b704a3c-afc4-3ca0-8d8b-38e2d70bcae9@sipwise.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
On 16/01/2020 12.29, Nuno Miguel Reis wrote:<br>
> Hi again.<br>
><br>
> Thanks for all the help and suggestions. I realized the issue happens <br>
> if using kernel forwarding only. If I change rtpengine to start at <br>
> userspace without the kernel module enabled everything works fine as <br>
> expected.<br>
> Do you have any hints on why this could be happening with the kernel <br>
> module?<br>
><br>
> I'm running rtpengine like this:<br>
><br>
> usersapece: $ rtpengine -f -L 7 --interface=100.100.100.100 <br>
> --listen-ng=<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">127.0.0.1:2223</a> <<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">http://127.0.0.1:2223</a>> --tos=184 --sip-source<br>
><br>
> kernel: $ rtpengine -f -L 7 --table=0 --interface=100.100.100.100 <br>
> --listen-ng=<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">127.0.0.1:2223</a> <<a href="http://127.0.0.1:2223" rel="noreferrer" target="_blank">http://127.0.0.1:2223</a>> --tos=184 <br>
> --no-fallback --sip-source<br>
><br>
The kernel module receives its instructions from the userspace daemon, <br>
so there's no reason there should be a difference. Can you post 1) logs <br>
and 2) the flags you use for your offers/answers?<br>
<br>
Cheers<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/70d3b6de/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200116/70d3b6de/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Thu, 16 Jan 2020 17:11:23 -0500<br>
From: Fred Posner <<a href="mailto:fred@palner.com" target="_blank">fred@palner.com</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] http_client interface<br>
Message-ID: <<a href="mailto:9808e784-3d56-d100-4c46-b136cc09ef08@palner.com" target="_blank">9808e784-3d56-d100-4c46-b136cc09ef08@palner.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On 1/16/20 4:56 PM, Daniel-Constantin Mierla wrote:<br>
> The libcurl seems to offer an option for that as well:<br>
> <br>
> - <a href="https://curl.haxx.se/libcurl/c/CURLOPT_INTERFACE.html" rel="noreferrer" target="_blank">https://curl.haxx.se/libcurl/c/CURLOPT_INTERFACE.html</a><br>
> <br>
> So it can be a small patch to the module and support it in the future.<br>
> <br>
> If you look for a solution on current stable, maybe one of the embedded<br>
> scripting languages can help, you can execute inline a small script in<br>
> Lua/Python/Perl with app_lua_run() & equivalents. In the past I used the<br>
> http client from lua to do more complex http api queries (e.g., with<br>
> specific headers, ...).<br>
> <br>
> Cheers,<br>
> Daniel<br>
> <br>
<br>
Thank you Daniel,<br>
<br>
I implemented a work around (little proxy in go) but would love if the<br>
option was added for the future.<br>
<br>
Fred Posner<br>
<a href="mailto:fred@qxork.com" target="_blank">fred@qxork.com</a><br>
<a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fqxork.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-a38bc2851524c5b967bfb1f129c9240c6587a15aDirect/SMS" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fqxork.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-a38bc2851524c5b967bfb1f129c9240c6587a15a<br>
Direct/SMS</a>: +1 (336) 439-3733<br>
<br>
Need Fred? Call Fred. 336-HEY-FRED<br>
Matrix: @fred:<a href="http://matrix.lod.com" rel="noreferrer" target="_blank">matrix.lod.com</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Thu, 16 Jan 2020 17:31:43 -0500<br>
From: Alex Balashov <<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>><br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: Re: [SR-Users] Trouble with 302 Redirect<br>
Message-ID: <20200116223143.GA857@typhoon><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Try doing this in a failure_route[]; onreply_route[] isn't really meant<br>
to transform replies, just to passively observe or drop them.<br>
<br>
Also, you'll want to use append_to_reply():<br>
<br>
<a href="https://kamailio.org/docs/modules/5.3.x/modules/textops.html#textops.f.append_to_reply" rel="noreferrer" target="_blank">https://kamailio.org/docs/modules/5.3.x/modules/textops.html#textops.f.append_to_reply</a><br>
<br>
Note that the conditions that give rise to the invocation of a<br>
failure_route are broader and somewhat more abstract than any given SIP<br>
reply -- e.g. transaction reply timeouts. So, you would want to<br>
structure your failure_route like this:<br>
<br>
failure_route[REDIRECT_HANDLE] {<br>
if(t_is_canceled())<br>
exit;<br>
<br>
if(t_branch_timeout()) {<br>
# Handle the timeout case...<br>
<br>
exit;<br>
}<br>
<br>
# Use $T_rpl to access reply code ($rs) and reply reason if needed<br>
# ($rs), per:<br>
#<br>
# <a href="https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#t_rpl_pv" rel="noreferrer" target="_blank">https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#t_rpl_pv</a><br>
<br>
if($T_rpl($rs) == 486) {<br>
append_to_reply("Contact: <sip:...>\r\n");<br>
t_reply("302", "Moved Temporarily");<br>
exit;<br>
}<br>
<br>
# Some other case.<br>
}<br>
<br>
-- Alex<br>
<br>
On Thu, Jan 16, 2020 at 03:54:54PM -0500, Jim Leahy wrote:<br>
<br>
> Hi All,<br>
> I'm having some issues trying to properly send a '302 Moved Temporarily'<br>
> reply to the calling UAC (UAC1) when the remote UAC (UAC2) returns a 486<br>
> status (Do Not Disturb). The goal is to redirect UAC1 to a voicemail server<br>
> when UAC2 is in DND.<br>
> Here are the pertinent parts of my config:<br>
> <br>
> route {<br>
> # drop some things right away<br>
> route(DROP);<br>
> <br>
> # perform sanity check<br>
> route(SANITYCHECK);<br>
> <br>
> # handle registrations<br>
> if(is_method("REGISTER")) {<br>
> route(REGISTRATION);<br>
> exit;<br>
> }<br>
> <br>
> # handle invites<br>
> if(is_method("INVITE")) {<br>
> route("INVITE");<br>
> exit;<br>
> }<br>
> <br>
> route(RELAY);<br>
> }<br>
> <br>
> route[INVITE] {<br>
> # add this proxy to the record-route so it stays in the loop<br>
> record_route();<br>
> <br>
> # if we can find this user in the location DB...<br>
> if(lookup("location")) {<br>
> # relay the invite to the new dURI<br>
> t_on_failure("FOURDIGITFAIL");<br>
> t_on_reply("FOURDIGITREPLY");<br>
> route(RELAY);<br>
> # go back to the main route<br>
> return;<br>
> }<br>
> <br>
> onreply_route[FOURDIGITREPLY] {<br>
> if(t_check_status("4[0-9]{2}")) {<br>
> t_reply("302", "Moved Temporarily");<br>
> }<br>
> }<br>
> <br>
> I'm having issues with the t_reply in the onreply_route. It successfully<br>
> sends the reply, but I can't seem to set the Contact header properly. I'm<br>
> trying to set it to the location of the user's mailbox on the voicemail<br>
> sever (ie <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>), but nothing I try works. I've tried:<br>
> remove_hf("Contact");<br>
> insert_hf("Contact: <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>");<br>
> t_reply("302", "Moved Temporarily");<br>
> <br>
> But as I understand it, that just changes the header in the reply from<br>
> UAC2, not the reply I'm sending to UAC1<br>
> <br>
> Then I tried:<br>
> append_to_reply("Contact: <a href="mailto:sip%3A1000@vmpbx.domain.com" target="_blank">sip:1000@vmpbx.domain.com</a>" );<br>
> t_reply("302", "Moved Temporarily");<br>
> <br>
> But I can't use append_to_reply in an onreply block.<br>
> How can I change the Contact header in the reply that's sent? Am I just<br>
> going about this the wrong way? Any help would be appreciated. Thanks<br>
<br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
-- <br>
Alex Balashov | Principal | Evariste Systems LLC<br>
<br>
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) <br>
Web: <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.evaristesys.com%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-ab557c94242e133aecb84497292656f0d65f2e0e" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.evaristesys.com%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-ab557c94242e133aecb84497292656f0d65f2e0e</a>, <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.csrpswitch.com%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-19a051a2187eac59a96885fd6635f5c3e5b9561d" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.csrpswitch.com%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-19a051a2187eac59a96885fd6635f5c3e5b9561d</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Fri, 17 Jan 2020 00:58:49 -0500<br>
From: Dario Vargas <<a href="mailto:dariovargas.gcs@gmail.com" target="_blank">dariovargas.gcs@gmail.com</a>><br>
To: <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Subject: [SR-Users] UCaaS Platform<br>
Message-ID:<br>
<CAHqy4U_jecJALyvoZM6p6oGB5VyC_kZN=<a href="mailto:Sj3_vqjEhkO-tmORw@mail.gmail.com" target="_blank">Sj3_vqjEhkO-tmORw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Take the LEAD in Unified Communications as a Service! We can help you get<br>
started in the next Telco Disruptive Business.<br>
<br>
White Label Hosted Cloud Platform as a Service (CPaaS) will enable you to<br>
offer all of the below products under your own brand -<br>
<br>
Hosted Contact Center (CCaaS)<br>
Hosted Unified Communications (UCaaS)<br>
Hosted PBX (Full Feature Set)<br>
SIP Trunk<br>
Ai Chat Bots<br>
Caller Profile Solutions (Display your clients' corporate identity on cell<br>
phones) to improve phone answer ratio.<br>
Video Surveillance (VSaaS integrated with AWS)<br>
Web Conferencing<br>
Virtual FAX<br>
Business SMS<br>
<br>
Software developed in the USA to have all the routing features required to<br>
connect with US and Canadian carriers for inbound and outbound (LRN, LNP,<br>
TF, SMS, Push, Video etc).<br>
Use our existing contracts and pricing for telco services or BYOC (bring<br>
your own carrier model).<br>
Alternately we can provide you with introductions to the carriers of choice<br>
below to get started -<br>
<br>
Nuwave.com - Number 1 in TF 8XX Inbound<br>
Voipinvite.com - 1000s of MPS and CPS for SMS and Voice Broadcast<br>
Voxbone.com - World Wide DiDs - Low Monthly minimum<br>
Peerlessnetwork.com - Outbound / Inbound Business calling<br>
Centurylink.com / Level 3 - USA DiDs and outbound and inbound - minimum<br>
volumes required<br>
Verizon.com - Outbound and Inbound enterprise business calls - minimum<br>
volumes required<br>
<br>
Dario Vargas<br>
<a href="mailto:info@dnl-switch.com" target="_blank">info@dnl-switch.com</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200117/943422d8/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200117/943422d8/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Fri, 17 Jan 2020 07:46:13 +0000<br>
From: Henning Westerholt <<a href="mailto:hw@skalatan.de" target="_blank">hw@skalatan.de</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>>, Dario Vargas<br>
<<a href="mailto:dariovargas.gcs@gmail.com" target="_blank">dariovargas.gcs@gmail.com</a>><br>
Subject: Re: [SR-Users] [commercial announcement]<br>
Message-ID: <<a href="mailto:2dcadf18-240a-1eb4-4a46-89d1d84c6007@skalatan.de" target="_blank">2dcadf18-240a-1eb4-4a46-89d1d84c6007@skalatan.de</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello Dario,<br>
<br>
this type of content is not appropriate for the sr-users lists, please post it here.<br>
<br>
Please use our dedicated business list for this kind of commercial announcements.<br>
<br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/business" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/business</a><br>
<br>
Regards,<br>
<br>
Henning<br>
<br>
Am 17.01.20 um 06:58 schrieb Dario Vargas:<br>
commercial announcement<br>
<br>
<br>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><mailto:<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
--<br>
Henning Westerholt - <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fskalatan.de%2fblog%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-e3709a77a2e08cc7e9654b6f4a5353ca23af4429" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fskalatan.de%2fblog%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-e3709a77a2e08cc7e9654b6f4a5353ca23af4429</a><br>
Kamailio services - <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgilawa.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-a187531eefe27344ba655db8d03ef71a41ad9b49" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgilawa.com&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-a187531eefe27344ba655db8d03ef71a41ad9b49</a><br>
Kamailio Merchandising - <a href="https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fskalatan.de%2fmerchandising%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-26d5e5e56523691d4156b2f08200b1019eb4c8f9" rel="noreferrer" target="_blank">https://ddei3-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fskalatan.de%2fmerchandising%2f&umid=39581E1E-9C53-E505-96A6-E057F22BD18D&auth=cbd2d006abdb2241308511f72807fe0bc6594b4a-26d5e5e56523691d4156b2f08200b1019eb4c8f9</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.kamailio.org/pipermail/sr-users/attachments/20200117/fa884666/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kamailio.org/pipermail/sr-users/attachments/20200117/fa884666/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
sr-users mailing list<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of sr-users Digest, Vol 176, Issue 17<br>
*****************************************<br>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div></div>