<div dir="ltr">Hi All<div><br></div><div>We are two on our side looking at this issue, and bumping our heads over it. Is it not a supported situation? (Perhaps there is a different way to achieve this)</div><div><br></div><div>Kind Regards</div></div><div hspace="streak-pt-mark" style="max-height:1px"><img alt="" style="width:0px;max-height:0px;overflow:hidden" src="https://mailfoogae.appspot.com/t?sender=abWF0dGhld0BnYXBwLnRlbmFjaXQubmV0&type=zerocontent&guid=79df6647-0114-40a4-a939-d567faed19cf"><font color="#ffffff" size="1">ᐧ</font></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 25 Jun 2019 at 16:51, <<a href="mailto:morne@tenacit.net">morne@tenacit.net</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">Anyone?
<hr>
<br>
Date: 2019-06-24 03:38:16 PM<br>
Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original destination when forwarding<br>
From: <a href="mailto:morne@tenacit.net" target="_blank">morne@tenacit.net</a><br>
To: <a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>,<a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a><br>
<br>
Hi,<br>
<br>
Just want to bump this thread.<br>
<br>
Anyone have some suggestions?<br>
 
<p class="MsoNormal">
<span lang="EN-ZA" style="font-size:10pt;color:gray">Kind Regards,</span>
</p>

<p class="MsoNormal">
<span lang="EN-ZA" style="color:rgb(31,73,125)"> </span>
</p>

<p class="MsoNormal">
<b><span lang="EN-ZA" style="color:rgb(121,174,82)">Morne du Plessis</span></b>
</p>

<p class="MsoNormal">
<span style="font-size:10pt;color:gray">Senior Network/Voice Engineer / Department Manager</span>
</p>

<p class="MsoNormal">
<span style="font-size:24px"><b><span lang="EN-ZA" style="color:rgb(121,174,82)">TenacIT</span></b></span><span style="font-size:22px"><strong> </strong></span>
</p>

<p class="MsoNormal">
<b><span lang="EN-ZA" style="color:rgb(31,73,125)">Strategic IT Consulting </span></b><span lang="EN-ZA" style="color:rgb(121,174,82)">•</span><b><span lang="EN-ZA" style="color:rgb(31,73,125)"> Advanced Networking </span></b><span lang="EN-ZA" style="color:rgb(121,174,82)">•</span>
</p>

<p class="MsoNormal">
<b><span lang="EN-ZA" style="color:rgb(31,73,125)">Custom Development </span></b><span lang="EN-ZA" style="color:rgb(121,174,82)">•</span><b><span lang="EN-ZA" style="color:rgb(31,73,125)"> Hosting </span></b><span lang="EN-ZA" style="color:rgb(121,174,82)">•</span><b><span lang="EN-ZA" style="color:rgb(31,73,125)"> Syspro Support </span></b>
</p>

<p class="MsoNormal">
<span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Tel: </span><span lang="EN-ZA" style="font-size:9pt;color:gray">041 10 10 100 </span>
</p>

<p class="MsoNormal">
<span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Web: </span><span lang="EN-ZA"><a href="http://www.tenacit.net/" target="_blank"><span style="font-size:9pt;color:rgb(188,226,146)">http://www.tenacit.net</span></a></span>
</p>
<span lang="EN-ZA" style="font-size:13.5pt;font-family:Webdings;color:green">P</span><span lang="EN-ZA" style="font-size:10pt;font-family:Calibri,sans-serif;color:navy"> </span><span lang="EN-ZA" style="font-size:10pt;font-family:Calibri,sans-serif;color:green">Before printing this email please think about the environment</span><span lang="EN-ZA" style="font-size:10pt;font-family:Calibri,sans-serif;color:navy">  </span><br>
 
<hr>
<br>
Date: 2019-06-21 08:54:13 AM<br>
Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original destination when forwarding<br>
From: <a href="mailto:morne@tenacit.net" target="_blank">morne@tenacit.net</a><br>
To: <a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>,<a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a><br>
<br>
Hi,<br>
<br>
<br>
>> Our client PBX uses the RURI by default, and I changed it to use the<br>
>> "To:" section of the invite<br>
<br>
<br>
>Why that? It should route calls via R-URI not To header.<br>
<br>
The "outbound_to_user" option only modifies the To header and not the R-URI, even if "e164_to_r-uri" is enabled. So the only way for me to get it working on the client PBX was with the To header<br>
<br>
>><br>
>> What I have noticed now is that the 1st failover works as expected,<br>
>> but the 2nd failover ends up with the RURI of the 1st failover in its "To:"<br>
>><br>
<br>
>Is this a peering failover or a CF scenario ?<br>
<br>
Its a peering failover scenario<br>
 
<hr>
<br>
Date: 2019-06-21 08:47:53 AM<br>
Subject: FW: [Spce-user] Incident [#SRY04139] Carrying original destination when forwarding<br>
From: <a href="mailto:morne@tenacit.net" target="_blank">morne@tenacit.net</a><br>
To: <a href="mailto:linksilent@tenacit.net" target="_blank">linksilent@tenacit.net</a><br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Spce-user <<a href="mailto:spce-user-bounces@lists.sipwise.com" target="_blank">spce-user-bounces@lists.sipwise.com</a>> On Behalf Of Daniel Grotti<br>
Sent: Thursday, June 20, 2019 11:48 AM<br>
To: <a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a><br>
Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original destination when forwarding<br>
<br>
Hi,<br>
<br>
<br>
On 6/20/19 10:44 AM, <a href="mailto:morne@tenacit.net" target="_blank">morne@tenacit.net</a> wrote:<br>
> Hi,<br>
><br>
> I managed to get it semi working (After successfully upgrading my<br>
> servers from prehistoric versions).<br>
><br>
> Our client PBX uses the RURI by default, and I changed it to use the<br>
> "To:" section of the invite<br>
<br>
<br>
Why that? It should route calls via R-URI not To header.<br>
<br>
<br>
><br>
> What I have noticed now is that the 1st failover works as expected,<br>
> but the 2nd failover ends up with the RURI of the 1st failover in its "To:"<br>
><br>
<br>
Is this a peering failover or a CF scenario ?<br>
<br>
<br>
<br>
> *Examples:*<br>
> ########################################## ORIGINAL<br>
> ###################################################<br>
><br>
> INVITE <a href="mailto:sip%3A01xxxxxxx9@2.2.2.2" target="_blank">sip:01xxxxxxx9@2.2.2.2</a>;user=phone SIP/2.0'<br>
> Via: SIP/2.0/UDP 1.1.1.1:2049;branch=z9hG4bK-li82baliyyct;rport'<br>
> From: "27xxxxxxxx2" <<a href="mailto:sip%3Atest@2.2.2.2" target="_blank">sip:test@2.2.2.2</a>>;tag=5xiqh2lj6c'<br>
> To: <<a href="mailto:sip%3A01xxxxxxx9@2.2.2.2" target="_blank">sip:01xxxxxxx9@2.2.2.2</a>;user=phone>'<br>
> Call-ID: 313536303935383439353536393239-davtmohvrxwe'<br>
> CSeq: 1 INVITE'<br>
> Max-Forwards: 70'<br>
> User-Agent: '<br>
> Contact: <sip:test@1.1.1.1:2049;line=beoci8wp>;reg-id=1'<br>
> X-Serialnumber: 0xxx1xxxxxx8'<br>
> P-Key-Flags: keys="3"'<br>
> Accept: application/sdp'<br>
> Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,<br>
> PRACK, MESSAGE, INFO, UPDATE'<br>
> Allow-Events: talk, hold, refer, call-info'<br>
> Supported: timer, 100rel, replaces, from-change'<br>
> Session-Expires: 3600'<br>
> Min-SE: 90'<br>
> Content-Type: application/sdp'<br>
> Content-Length: 427'<br>
><br>
> ######################################### 1st Failover<br>
> ##################################################<br>
><br>
> INVITE sip:Tenant-Failover1@ClientIP1:5060 SIP/2.0'<br>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKka512a6U;rport'<br>
> From:<br>
> <<a href="mailto:sip%3A27xxxxxxxx2@exampledomain.com" target="_blank">sip:27xxxxxxxx2@exampledomain.com</a>>;tag=4532BC27-5D0A53F4000EA445-83A95700'<br>
> To: <<a href="mailto:sip%3A01xxxxxxx9@exampledomain.com" target="_blank">sip:01xxxxxxx9@exampledomain.com</a>>'<br>
> CSeq: 10 INVITE'<br>
> Call-ID: 313536303935373933363238313932-lxxe06we83v8_b2b-1'<br>
> Route: <sip:127.0.0.1:5060;lr;lr>'<br>
> Max-Forwards: 70'<br>
> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,<br>
> MESSAGE, UPDATE'<br>
> Supported: 100rel, replaces, from-change'<br>
> P-NGCP-Caller-Info:<br>
> <<a href="mailto:sip%3ATenant@exampledomain.com" target="_blank">sip:Tenant@exampledomain.com</a>>;ip=127.0.0.1;port=5080;primary=27xxxxxxxx3'<br>
> P-NGCP-Callee-Info:<br>
> <<a href="mailto:sip%3ATenant-Failover1@exampledomain.com" target="_blank">sip:Tenant-Failover1@exampledomain.com</a>>;ip=127.0.0.1;port=5060;primary=27xxxxxxxx4'<br>
> P-D-Uri: sip:127.0.0.1:5060;lr'<br>
> Content-Type: application/sdp'<br>
> Contact: <sip:127.0.0.1:5080;transport=udp>'<br>
> Content-Length: 455'<br>
><br>
> ######################################### 2nd Failover<br>
> ##################################################<br>
><br>
> INVITE sip:Tenant-Failover2@ClientIP2:5060 SIP/2.0'<br>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKka512a6U;rport'<br>
> From:<br>
> <<a href="mailto:sip%3A27xxxxxxxx2@exampledomain.com" target="_blank">sip:27xxxxxxxx2@exampledomain.com</a>>;tag=4532BC27-5D0A53F4000EA445-83A95700'<br>
> To: <<a href="mailto:sip%3ATenant-Failover1@exampledomain.com" target="_blank">sip:Tenant-Failover1@exampledomain.com</a>>'<br>
> CSeq: 10 INVITE'<br>
> Call-ID: 313536303936363439373236333036-f8f5lkiwc31n_b2b-1'<br>
> Route: <sip:127.0.0.1:5060;lr;lr>'<br>
> Max-Forwards: 70'<br>
> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,<br>
> MESSAGE, UPDATE'<br>
> Supported: 100rel, replaces, from-change'<br>
> P-NGCP-Caller-Info:<br>
> <<a href="mailto:sip%3ATenant-Failover1@exampledomain.com" target="_blank">sip:Tenant-Failover1@exampledomain.com</a>>;ip=127.0.0.1;port=5080;primary=27xxxxxxxx3'<br>
> P-NGCP-Callee-Info:<br>
> <<a href="mailto:sip%3ATenant-Failover2@exampledomain.com" target="_blank">sip:Tenant-Failover2@exampledomain.com</a>>;ip=127.0.0.1;port=5060;primary=27xxxxxxxx4'<br>
> P-D-Uri: sip:127.0.0.1:5060;lr'<br>
> Content-Type: application/sdp'<br>
> Contact: <sip:127.0.0.1:5080;transport=udp>'<br>
> Content-Length: 455'<br>
><br>
><br>
> As you can see in the 2nd Failover, the "To:" is the RURI of the 1st<br>
> failover.<br>
><br>
> Is there a way that I can carry it over? Maybe change the RURI at the<br>
> first failover? Do I need to change something in the template files? I<br>
> have enabled the "e164_to_ruri" but it doesnt make a difference to the<br>
> invite.<br>
<br>
<br>
<br>
You can try to pay with the preferences "outbound_to_user".<br>
<br>
<br>
<br>
><br>
> Kind Regards,<br>
><br>
> *Morne du Plessis*<br>
><br>
> Senior Network/Voice Engineer / Department Manager<br>
><br>
> *TenacIT***<br>
><br>
> *Strategic IT Consulting *•*Advanced Networking *•<br>
><br>
> *Custom Development *•*Hosting *•*Syspro Support *<br>
><br>
> Tel: 041 10 10 100<br>
><br>
> Web: <a href="http://www.tenacit.net" target="_blank">http://www.tenacit.net</a> <<a href="http://www.tenacit.net/" target="_blank">http://www.tenacit.net/</a>><br>
><br>
> PBefore printing this email please think about the environment<br>
><br>
> ----------------------------------------------------------------------<br>
> --<br>
><br>
> Date: 2018-10-22 12:02:13 PM<br>
> Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original<br>
> destination when forwarding<br>
> From: <a href="mailto:apogrebennyk@sipwise.com" target="_blank">apogrebennyk@sipwise.com</a><br>
> To: <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
> Cc: <a href="mailto:linksilent@app.tenacit.net" target="_blank">linksilent@app.tenacit.net</a><br>
><br>
> Hi,<br>
><br>
> On 10/18/2018 01:57 PM, <a href="mailto:linksilent@app.tenacit.net" target="_blank">linksilent@app.tenacit.net</a> wrote:<br>
> > The part that I want to stay the same after the forward is the "To:"<br>
> > number before the @<br>
><br>
> as explained try setting the preference outbound_to_user to "Original<br>
> (Forwarding) called user" or "Received To header" - on the call<br>
> receiving side (user/domain).<br>
><br>
> This should help.<br>
> Andrew<br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
<br>
<br>
<br>
Daniel Grotti<br>
<br>
Head of Customer Support Sipwise GmbH<br>
e: <a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a> Europaring F15<br>
t: +43(0)130120332 A-2345 Brunn Am Gebirge<br>
w: <a href="http://www.sipwise.com" target="_blank">www.sipwise.com</a> FN: 305595f FG: LG Wiener Neustadt<br>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user______________________________" target="_blank">https://lists.sipwise.com/listinfo/spce-user______________________________</a>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><p> </p>

<p><span style="font-size:10pt;color:gray"><img src="http://www.tenacit.net/googlesig/tenacit.png" width="200" height="65"></span><span lang="EN-ZA" style="font-size:10pt;color:gray"></span></p>

<p><span lang="EN-ZA" style="font-size:10pt;color:black"> </span></p>

<p><b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">Matthew Ogden</span></b></p>

<p><span style="font-size:10pt;color:gray">Management</span></p>

<p><span style="font-size:10pt;color:gray">TenacIT
</span></p>

<p><span style="font-size:10pt;color:gray"> </span></p>

<p><span style="color:gray;font-size:10pt"> </span><br></p>

<p><b><span lang="EN-ZA">Strategic IT Consulting </span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">•</span><b><span lang="EN-ZA"> Advanced Networking </span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">• </span><b><span lang="EN-ZA">Virtualisation</span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)"> </span><b><span lang="EN-ZA"></span></b></p>

<p><b><span lang="EN-ZA">Custom Development </span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">•</span><b><span lang="EN-ZA"> </span></b><b><span lang="EN-ZA">Hosting </span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">•</span><b><span lang="EN-ZA"> </span></b><b><span lang="EN-ZA">Syspro Support  </span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)">• </span><b><span lang="EN-ZA">MS Licensing</span></b><span lang="EN-ZA" style="font-size:12pt;color:rgb(121,174,82)"> </span><b><span lang="EN-ZA"></span></b></p>

<p><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">National Tel: </span><span lang="EN-ZA" style="font-size:9pt;color:gray">041 10 10 100
| </span><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Cell: </span><span lang="EN-ZA" style="font-size:9pt;color:gray">084 205 4445 | </span><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Email: </span><a href="mailto:matthew@tenacit.net" target="_blank"><span style="font-size:9pt;color:gray;text-decoration:none">matthew@tenacit.net</span></a><span style="font-size:9pt;color:rgb(68,84,106)">  </span><span style="font-size:9pt;color:gray"></span></p>

<p><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">CT Tel: </span><span lang="EN-ZA" style="font-size:9pt;color:gray">021 201 0333 | </span><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Skype Name: </span><span lang="EN-ZA" style="font-size:9pt;color:gray">matthew.ogden | </span><span lang="EN-ZA" style="font-size:9pt;color:rgb(166,166,166)">Web: </span><span lang="EN-ZA" style="font-size:9pt;color:rgb(188,226,146);text-decoration:none"><a href="http://www.tenacit.net/" target="_blank">http://www.tenacit.net</a></span></p><p>    <img src="http://www.tenacit.net/googlesig/bottom.png"></p></div></div>