[Spce-user] Incident [#SRY04139] Carrying original destination when forwarding
Andrew Pogrebennyk
apogrebennyk at sipwise.com
Mon Jul 1 03:11:44 EDT 2019
Hi there,
I am not sure if we can follow you. Could you please explain what
exactly you have configured, and on what sipwise version?
Are you setting up multiple SIP peerings, or multiple registrations to a
subscriber, with serial forking by q value, or you are setting call
forwards to multiple numbers? I'm afraid everyone is silent because the
scenario is not described anywhere in this thread.
Andrew
On 6/26/19 7:54 AM, Matthew Ogden wrote:
> Hi All
>
> 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)
>
> Kind Regards
> ᐧ
>
> On Tue, 25 Jun 2019 at 16:51, <morne at tenacit.net
> <mailto:morne at tenacit.net>> wrote:
>
> Anyone?
> ------------------------------------------------------------------------
>
> Date: 2019-06-24 03:38:16 PM
> Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original
> destination when forwarding
> From: morne at tenacit.net <mailto:morne at tenacit.net>
> To: dgrotti at sipwise.com
> <mailto:dgrotti at sipwise.com>,spce-user at lists.sipwise.com
> <mailto:spce-user at lists.sipwise.com>
>>
>>
>>
>>
>>
>> Daniel Grotti
>>
>> Head of Customer Support Sipwise GmbH
>> e: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>> Europaring F15
>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>> w: www.sipwise.com <http://www.sipwise.com> FN: 305595f FG:
>> LG Wiener Neustadt
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user_______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> --
>>
>>
>>
>>>
>>>
>>>
>>>
>>> Daniel Grotti
>>>
>>> Head of Customer Support Sipwise GmbH
>>> e: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>>> Europaring F15
>>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>>> w: www.sipwise.com <http://www.sipwise.com> FN: 305595f FG:
>>> LG Wiener Neustadt
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>> https://lists.sipwise.com/listinfo/spce-user_______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>>
>>>
>>> *Matthew Ogden*
>>>
>>> Management
>>>
>>> TenacIT
>>>
>>>
>>>
>>>
>>>
>>> *Strategic IT Consulting *•*Advanced Networking *•
>>> *Virtualisation***
>>>
>>> *Custom Development *•***Hosting *•***Syspro Support *• *MS
>>> Licensing***
>>>
>>> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>>> matthew at tenacit.net <mailto:matthew at tenacit.net>
>>>
>>> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>>> http://www.tenacit.net <http://www.tenacit.net/>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>>
>> *Matthew Ogden*
>>
>> Management
>>
>> TenacIT
>>
>>
>>
>>
>>
>> *Strategic IT Consulting *•*Advanced Networking *• *Virtualisation***
>>
>> *Custom Development *•***Hosting *•***Syspro Support *• *MS
>> Licensing***
>>
>> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net <mailto:matthew at tenacit.net>
>>
>> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net <http://www.tenacit.net/>
>>
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> Hi,
>
> Just want to bump this thread.
>
> Anyone have some suggestions?
>
>
> Kind Regards,
>
>
>
> *Morne du Plessis*
>
> Senior Network/Voice Engineer / Department Manager
>
> *TenacIT** *
>
> *Strategic IT Consulting *•*Advanced Networking *•
>
> *Custom Development *•*Hosting *•*Syspro Support *
>
> Tel: 041 10 10 100
>
> Web: http://www.tenacit.net <http://www.tenacit.net/>
>
> PBefore printing this email please think about the environment
>
> ------------------------------------------------------------------------
>
> Date: 2019-06-21 08:54:13 AM
> Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original
> destination when forwarding
> From: morne at tenacit.net <mailto:morne at tenacit.net>
> To: dgrotti at sipwise.com
> <mailto:dgrotti at sipwise.com>,spce-user at lists.sipwise.com
> <mailto:spce-user at lists.sipwise.com>
>
> Hi,
>
>
> >> Our client PBX uses the RURI by default, and I changed it to
> use the
> >> "To:" section of the invite
>
>
> >Why that? It should route calls via R-URI not To header.
>
> 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
>
> >>
> >> What I have noticed now is that the 1st failover works as expected,
> >> but the 2nd failover ends up with the RURI of the 1st failover
> in its "To:"
> >>
>
> >Is this a peering failover or a CF scenario ?
>
> Its a peering failover scenario
>
> ------------------------------------------------------------------------
>
> Date: 2019-06-21 08:47:53 AM
> Subject: FW: [Spce-user] Incident [#SRY04139] Carrying original
> destination when forwarding
> From: morne at tenacit.net <mailto:morne at tenacit.net>
> To: linksilent at tenacit.net <mailto:linksilent at tenacit.net>
>
>
>
> -----Original Message-----
> From: Spce-user <spce-user-bounces at lists.sipwise.com
> <mailto:spce-user-bounces at lists.sipwise.com>> On Behalf Of Daniel
> Grotti
> Sent: Thursday, June 20, 2019 11:48 AM
> To: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
> Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original
> destination when forwarding
>
> Hi,
>
>
> On 6/20/19 10:44 AM, morne at tenacit.net <mailto:morne at tenacit.net>
> wrote:
> > Hi,
> >
> > I managed to get it semi working (After successfully upgrading my
> > servers from prehistoric versions).
> >
> > Our client PBX uses the RURI by default, and I changed it to use the
> > "To:" section of the invite
>
>
> Why that? It should route calls via R-URI not To header.
>
>
> >
> > What I have noticed now is that the 1st failover works as expected,
> > but the 2nd failover ends up with the RURI of the 1st failover
> in its "To:"
> >
>
> Is this a peering failover or a CF scenario ?
>
>
>
> > *Examples:*
> > ########################################## ORIGINAL
> > ###################################################
> >
> > INVITE sip:01xxxxxxx9 at 2.2.2.2
> <mailto:sip%3A01xxxxxxx9 at 2.2.2.2>;user=phone SIP/2.0'
> > Via: SIP/2.0/UDP 1.1.1.1:2049;branch=z9hG4bK-li82baliyyct;rport'
> > From: "27xxxxxxxx2" <sip:test at 2.2.2.2
> <mailto:sip%3Atest at 2.2.2.2>>;tag=5xiqh2lj6c'
> > To: <sip:01xxxxxxx9 at 2.2.2.2
> <mailto:sip%3A01xxxxxxx9 at 2.2.2.2>;user=phone>'
> > Call-ID: 313536303935383439353536393239-davtmohvrxwe'
> > CSeq: 1 INVITE'
> > Max-Forwards: 70'
> > User-Agent: '
> > Contact: <sip:test at 1.1.1.1:2049;line=beoci8wp>;reg-id=1'
> > X-Serialnumber: 0xxx1xxxxxx8'
> > P-Key-Flags: keys="3"'
> > Accept: application/sdp'
> > Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,
> > PRACK, MESSAGE, INFO, UPDATE'
> > Allow-Events: talk, hold, refer, call-info'
> > Supported: timer, 100rel, replaces, from-change'
> > Session-Expires: 3600'
> > Min-SE: 90'
> > Content-Type: application/sdp'
> > Content-Length: 427'
> >
> > ######################################### 1st Failover
> > ##################################################
> >
> > INVITE sip:Tenant-Failover1 at ClientIP1:5060 SIP/2.0'
> > Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKka512a6U;rport'
> > From:
> > <sip:27xxxxxxxx2 at exampledomain.com
> <mailto:sip%3A27xxxxxxxx2 at exampledomain.com>>;tag=4532BC27-5D0A53F4000EA445-83A95700'
> > To: <sip:01xxxxxxx9 at exampledomain.com
> <mailto:sip%3A01xxxxxxx9 at exampledomain.com>>'
> > CSeq: 10 INVITE'
> > Call-ID: 313536303935373933363238313932-lxxe06we83v8_b2b-1'
> > Route: <sip:127.0.0.1:5060;lr;lr>'
> > Max-Forwards: 70'
> > Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,
> > MESSAGE, UPDATE'
> > Supported: 100rel, replaces, from-change'
> > P-NGCP-Caller-Info:
> > <sip:Tenant at exampledomain.com
> <mailto:sip%3ATenant at exampledomain.com>>;ip=127.0.0.1;port=5080;primary=27xxxxxxxx3'
> > P-NGCP-Callee-Info:
> > <sip:Tenant-Failover1 at exampledomain.com
> <mailto:sip%3ATenant-Failover1 at exampledomain.com>>;ip=127.0.0.1;port=5060;primary=27xxxxxxxx4'
> > P-D-Uri: sip:127.0.0.1:5060;lr'
> > Content-Type: application/sdp'
> > Contact: <sip:127.0.0.1:5080;transport=udp>'
> > Content-Length: 455'
> >
> > ######################################### 2nd Failover
> > ##################################################
> >
> > INVITE sip:Tenant-Failover2 at ClientIP2:5060 SIP/2.0'
> > Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKka512a6U;rport'
> > From:
> > <sip:27xxxxxxxx2 at exampledomain.com
> <mailto:sip%3A27xxxxxxxx2 at exampledomain.com>>;tag=4532BC27-5D0A53F4000EA445-83A95700'
> > To: <sip:Tenant-Failover1 at exampledomain.com
> <mailto:sip%3ATenant-Failover1 at exampledomain.com>>'
> > CSeq: 10 INVITE'
> > Call-ID: 313536303936363439373236333036-f8f5lkiwc31n_b2b-1'
> > Route: <sip:127.0.0.1:5060;lr;lr>'
> > Max-Forwards: 70'
> > Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,
> > MESSAGE, UPDATE'
> > Supported: 100rel, replaces, from-change'
> > P-NGCP-Caller-Info:
> > <sip:Tenant-Failover1 at exampledomain.com
> <mailto:sip%3ATenant-Failover1 at exampledomain.com>>;ip=127.0.0.1;port=5080;primary=27xxxxxxxx3'
> > P-NGCP-Callee-Info:
> > <sip:Tenant-Failover2 at exampledomain.com
> <mailto:sip%3ATenant-Failover2 at exampledomain.com>>;ip=127.0.0.1;port=5060;primary=27xxxxxxxx4'
> > P-D-Uri: sip:127.0.0.1:5060;lr'
> > Content-Type: application/sdp'
> > Contact: <sip:127.0.0.1:5080;transport=udp>'
> > Content-Length: 455'
> >
> >
> > As you can see in the 2nd Failover, the "To:" is the RURI of the 1st
> > failover.
> >
> > Is there a way that I can carry it over? Maybe change the RURI
> at the
> > first failover? Do I need to change something in the template
> files? I
> > have enabled the "e164_to_ruri" but it doesnt make a difference
> to the
> > invite.
>
>
>
> You can try to pay with the preferences "outbound_to_user".
>
>
>
> >
> > Kind Regards,
> >
> > *Morne du Plessis*
> >
> > Senior Network/Voice Engineer / Department Manager
> >
> > *TenacIT***
> >
> > *Strategic IT Consulting *•*Advanced Networking *•
> >
> > *Custom Development *•*Hosting *•*Syspro Support *
> >
> > Tel: 041 10 10 100
> >
> > Web: http://www.tenacit.net <http://www.tenacit.net/>
> >
> > PBefore printing this email please think about the environment
> >
> >
> ----------------------------------------------------------------------
> > --
> >
> > Date: 2018-10-22 12:02:13 PM
> > Subject: Re: [Spce-user] Incident [#SRY04139] Carrying original
> > destination when forwarding
> > From: apogrebennyk at sipwise.com <mailto:apogrebennyk at sipwise.com>
> > To: Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> > Cc: linksilent at app.tenacit.net <mailto:linksilent at app.tenacit.net>
> >
> > Hi,
> >
> > On 10/18/2018 01:57 PM, linksilent at app.tenacit.net
> <mailto:linksilent at app.tenacit.net> wrote:
> > > The part that I want to stay the same after the forward is the
> "To:"
> > > number before the @
> >
> > as explained try setting the preference outbound_to_user to
> "Original
> > (Forwarding) called user" or "Received To header" - on the call
> > receiving side (user/domain).
> >
> > This should help.
> > Andrew
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> > https://lists.sipwise.com/listinfo/spce-user
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190701/033f2140/attachment-0001.html>
More information about the Spce-user
mailing list