Re: [OpenSIPS-Users] How to manage REFER Packet

[Calvin Ellison]

Hi Donat

You're right, I did mean a 3xx response, not a made-up redirect method. My
apologies, we use Redirect internally as the text of our 3xx codes and I
confused myself. I blame the rest on, um, brain fog?

My point to the original question of the author is whether REFER is really
what they want, or if a 3xx is a better solution for their scenario. As you
pointed out, there's a lot more involved in supporting REFER. If that's
all Freeswitch will give them, they have a bit of a hill to climb, but it's
doable.

Sorry again for creating any confusion.


Regards,

*Calvin Ellison*
Systems Architect
calvin.elli...@voxox.com
+1 (213) 285-0555

---
*voxox.com  *
5825 Oberlin Drive, Suite 5
San Diego, CA 92121
[image: Voxox]


On Thu, Mar 11, 2021 at 9:13 AM Donat Zenichev 
wrote:

> Good day Calvin.
> There is no SIP method called "REDIREDCT" as you say.
> Currently there are 6 general methods defined in RFC 3261, you can see
> them here: https://tools.ietf.org/html/rfc3261#section-27.4
>
> And of course a list of SIP specifications (documents) including following
> methods: PRACK, SUBSCRIBE, NOTIFY, PUBLISH, REFER, MESSAGE, UPDATE
> which are defined in the list of other RFC documents.
>
> But there is no method which you called. So that, please do not confuse
> the community with a wrong terminology.
>
> The thing you are referring to (if I managed to understand this correctly)
> is just a basic processing of 3XX type of responses (Redirection server).
> This block of response codes is commonly called as redirection responses.
> Response codes are not the same thing as SIP methods.
> And most of all would be "302 Moved Temporarily" used, to provide Contact
> information where to find the requested side. Depends on setup.
>
> This however seems to be completely not related to the original question
> of the author.
>
> Best regards.
>
>
> On Thu, Mar 11, 2021 at 6:26 PM Calvin Ellison 
> wrote:
>
>> Is it your intention to transfer an established call, or do you really a
>> redirect?
>>
>> In the case of a redirect you're actually looking for the REDIREDCT
>> method not the REFER method. Instead of returning a 200 OK then REFER, you
>> would return a 300 REDIRECT with the new URI in the Contact header. That
>> completes the first dialogue and then you start a new dialogue to the
>> destination provided by the REDIRECT.
>>
>>
>> Regards,
>>
>>
>> Calvin Ellison
>> Systems Architect
>> calvin.elli...@voxox.com
>> +1 (213) 285-0555
>>
>> ---
>> voxox.com
>> 5825 Oberlin Drive, Suite 5
>> San Diego, CA 92121
>>
>> On Sun, Mar 7, 2021, 23:12 Vinayak Makwana 
>> wrote:
>>
>>> Hello Everyone,
>>>  I would like to manage REFER packet with opensips script
>>>  In my case i want manage REFER packet like whenever i opensips proxy
>>> getting REFER packet from freeswitch at that time i need to convert this
>>> REFER packet into INVITE packet from opensips script and send to the
>>> endpoint.
>>> Is their  any possibilities where I can manage this thing in opensips
>>> 3.1.x ?
>>> Please suggest me.
>>>
>>> My scenario like this:
>>>
>>> AopensipsB(Freswitch)
>>>   |   -INVITE --->|   ---INVITE-->   |
>>>
>>>   |   <-200OK ---|  <---200OK--|
>>>   |  <-INVITE ---   |   <---REFER|
>>>
>>> *Disclaimer*
>>> In addition to generic Disclaimer which you have agreed on our website,
>>> any views or opinions presented in this email are solely those of the
>>> originator and do not necessarily represent those of the Company or its
>>> sister concerns. Any liability (in negligence, contract or otherwise)
>>> arising from any third party taking any action, or refraining from taking
>>> any action on the basis of any of the information contained in this email
>>> is hereby excluded.
>>>
>>> *Confidentiality*
>>> This communication (including any attachment/s) is intended only for the
>>> use of the addressee(s) and contains information that is PRIVILEGED AND
>>> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
>>> of this communication is prohibited. Please inform originator if you have
>>> received it in error.
>>>
>>> *Caution for viruses, malware etc.*
>>> This communication, including any attachments, may not be free of
>>> viruses, trojans, similar or new contaminants/malware, interceptions or
>>> interference, and may not be compatible with your systems. You shall carry
>>> out virus/malware scanning on your own before opening any attachment to
>>> this e-mail. The sender of this e-mail and Company including its sister
>>> concerns shall not be liable for any damage that may incur to you as a
>>> result of viruses, incompleteness of this message, a delay in receipt of
>>> this message or any other computer problems.
>>> ___
>>> Users mailing 

Re: [OpenSIPS-Users] How to manage REFER Packet

[johan]

302 you mean ?

On 11/03/2021 17:24, Calvin Ellison wrote:
> Is it your intention to transfer an established call, or do you really
> a redirect?
>
> In the case of a redirect you're actually looking for the REDIREDCT
> method not the REFER method. Instead of returning a 200 OK then REFER,
> you would return a 300 REDIRECT with the new URI in the Contact
> header. That completes the first dialogue and then you start a new
> dialogue to the destination provided by the REDIRECT.
>
>
> Regards,
>
>
> Calvin Ellison
> Systems Architect
> calvin.elli...@voxox.com 
> +1 (213) 285-0555
>
> ---
> voxox.com  
> 5825 Oberlin Drive, Suite 5
> San Diego, CA 92121
>
> On Sun, Mar 7, 2021, 23:12 Vinayak Makwana
> mailto:vinayak.makw...@ecosmob.com>> wrote:
>
> Hello Everyone,
>  I would like to manage REFER packet with opensips script 
>  In my case i want manage REFER packet like whenever i opensips
> proxy getting REFER packet from freeswitch at that time i need to
> convert this REFER packet into INVITE packet from opensips script
> and send to the endpoint.
> Is their  any possibilities where I can manage this thing in
> opensips 3.1.x ?
> Please suggest me.
>
> My scenario like this:
>
> A                            opensips                B(Freswitch)
>   |   -INVITE --->    |   ---INVITE-->   |       
>                      
>   |   <-200OK ---    |  <---200OK--    | 
>   |  <-INVITE ---   |   <---REFER    |
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our
> website, any views or opinions presented in this email are solely
> those of the originator and do not necessarily represent those of
> the Company or its sister concerns. Any liability (in negligence,
> contract or otherwise) arising from any third party taking any
> action, or refraining from taking any action on the basis of any
> of the information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only
> for the use of the addressee(s) and contains information that is
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination,
> distribution, or copying of this communication is prohibited.
> Please inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of
> viruses, trojans, similar or new contaminants/malware,
> interceptions or interference, and may not be compatible with your
> systems. You shall carry out virus/malware scanning on your own
> before opening any attachment to this e-mail. The sender of this
> e-mail and Company including its sister concerns shall not be
> liable for any damage that may incur to you as a result of
> viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems. 
> ___
> Users mailing list
> Users@lists.opensips.org 
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


0xD7D896F7DDA70EC3.asc
Description: application/pgp-keys
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to manage REFER Packet

[Donat Zenichev]

Good day Calvin.
There is no SIP method called "REDIREDCT" as you say.
Currently there are 6 general methods defined in RFC 3261, you can see them
here: https://tools.ietf.org/html/rfc3261#section-27.4

And of course a list of SIP specifications (documents) including following
methods: PRACK, SUBSCRIBE, NOTIFY, PUBLISH, REFER, MESSAGE, UPDATE
which are defined in the list of other RFC documents.

But there is no method which you called. So that, please do not confuse the
community with a wrong terminology.

The thing you are referring to (if I managed to understand this correctly)
is just a basic processing of 3XX type of responses (Redirection server).
This block of response codes is commonly called as redirection responses.
Response codes are not the same thing as SIP methods.
And most of all would be "302 Moved Temporarily" used, to provide Contact
information where to find the requested side. Depends on setup.

This however seems to be completely not related to the original question of
the author.

Best regards.


On Thu, Mar 11, 2021 at 6:26 PM Calvin Ellison 
wrote:

> Is it your intention to transfer an established call, or do you really a
> redirect?
>
> In the case of a redirect you're actually looking for the REDIREDCT method
> not the REFER method. Instead of returning a 200 OK then REFER, you would
> return a 300 REDIRECT with the new URI in the Contact header. That
> completes the first dialogue and then you start a new dialogue to the
> destination provided by the REDIRECT.
>
>
> Regards,
>
>
> Calvin Ellison
> Systems Architect
> calvin.elli...@voxox.com
> +1 (213) 285-0555
>
> ---
> voxox.com
> 5825 Oberlin Drive, Suite 5
> San Diego, CA 92121
>
> On Sun, Mar 7, 2021, 23:12 Vinayak Makwana 
> wrote:
>
>> Hello Everyone,
>>  I would like to manage REFER packet with opensips script
>>  In my case i want manage REFER packet like whenever i opensips proxy
>> getting REFER packet from freeswitch at that time i need to convert this
>> REFER packet into INVITE packet from opensips script and send to the
>> endpoint.
>> Is their  any possibilities where I can manage this thing in opensips
>> 3.1.x ?
>> Please suggest me.
>>
>> My scenario like this:
>>
>> AopensipsB(Freswitch)
>>   |   -INVITE --->|   ---INVITE-->   |
>>
>>   |   <-200OK ---|  <---200OK--|
>>   |  <-INVITE ---   |   <---REFER|
>>
>> *Disclaimer*
>> In addition to generic Disclaimer which you have agreed on our website,
>> any views or opinions presented in this email are solely those of the
>> originator and do not necessarily represent those of the Company or its
>> sister concerns. Any liability (in negligence, contract or otherwise)
>> arising from any third party taking any action, or refraining from taking
>> any action on the basis of any of the information contained in this email
>> is hereby excluded.
>>
>> *Confidentiality*
>> This communication (including any attachment/s) is intended only for the
>> use of the addressee(s) and contains information that is PRIVILEGED AND
>> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
>> of this communication is prohibited. Please inform originator if you have
>> received it in error.
>>
>> *Caution for viruses, malware etc.*
>> This communication, including any attachments, may not be free of
>> viruses, trojans, similar or new contaminants/malware, interceptions or
>> interference, and may not be compatible with your systems. You shall carry
>> out virus/malware scanning on your own before opening any attachment to
>> this e-mail. The sender of this e-mail and Company including its sister
>> concerns shall not be liable for any damage that may incur to you as a
>> result of viruses, incompleteness of this message, a delay in receipt of
>> this message or any other computer problems.
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 

Best regards,
Donat Zenichev
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to manage REFER Packet

[Calvin Ellison]

Is it your intention to transfer an established call, or do you really a
redirect?

In the case of a redirect you're actually looking for the REDIREDCT method
not the REFER method. Instead of returning a 200 OK then REFER, you would
return a 300 REDIRECT with the new URI in the Contact header. That
completes the first dialogue and then you start a new dialogue to the
destination provided by the REDIRECT.


Regards,


Calvin Ellison
Systems Architect
calvin.elli...@voxox.com
+1 (213) 285-0555

---
voxox.com
5825 Oberlin Drive, Suite 5
San Diego, CA 92121

On Sun, Mar 7, 2021, 23:12 Vinayak Makwana 
wrote:

> Hello Everyone,
>  I would like to manage REFER packet with opensips script
>  In my case i want manage REFER packet like whenever i opensips proxy
> getting REFER packet from freeswitch at that time i need to convert this
> REFER packet into INVITE packet from opensips script and send to the
> endpoint.
> Is their  any possibilities where I can manage this thing in opensips
> 3.1.x ?
> Please suggest me.
>
> My scenario like this:
>
> AopensipsB(Freswitch)
>   |   -INVITE --->|   ---INVITE-->   |
>
>   |   <-200OK ---|  <---200OK--|
>   |  <-INVITE ---   |   <---REFER|
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to manage REFER Packet

[Donat Zenichev]

Good day Vinayak.

Firstly you'd better take into account that a sequence for processing REFER
is much different from how the INVITE method is being processed.
So it's known that so called hand-shake consists of the following messages
exchange: INVITE - 100 - 180/183 (optionally) - 200OK/202 Accepted - ACK
There is no complexity here and the way how it works is clear.

Now getting to the REFER method.
The REFER method likely falls in the category of in-dialog requests.
And in the predominant majority of cases can only be used within the
existing dialog (to implement an attended/unattended transfer).

The superficial view/sequence of messages will be as follows:
- firstly A side (who makes a transfer) sends REFER (to local proxy/B2B)
and awaits the arrival of 202.
(and by doing this also subscribes for an event)
- secondly local proxy/B2B invites a third party into the call (the further
behavior depends on if this is an attended/unattended transfer)
- (let's say it's unattended) then as soon as third party takes a call,
local proxy/B2B notifies (with NOTIFY method) the A party about the
happened event.
So: NOTIFY - 200OK
Which begets in its turn a normal call clearing from the A side (BYE -
200OK)
- while A side was processing the happened event, local proxy/B2B took
charge of re-invitation of the B party (with newer signaling/media
information).
- a call between B and C side is now established (through the proxy/B2B)

You might as well read this RFC document:
https://tools.ietf.org/html/rfc3515
which is dedicated to the REFER method in particular.

Personally I haven't ever faced such a scenario, which would require such a
conversion of REFER to INVITE.
Is there a good reason for doing that?

It sounds entirely quite tricky, since a normal logic for processing REFER
already entails usage of INVITE.
But not to convert REFER into INVITE, but to engage a third party into the
call. Meanwhile REFER method keeps on doing its job.

Even if you still want to do that,
you need to write an OpenSIPS logic, which would be capable of handling the
full sequence for the REFER method (your leg with FreeSWITCH).
Keep it proper all the way during the call.
And on the other hand would be capable of conversion and processing the
usual INVITE sequence (the leg with A side).
Which doesn't look to me like a simple thing to do.

Best regards


On Mon, Mar 8, 2021 at 9:13 AM Vinayak Makwana 
wrote:

> Hello Everyone,
>  I would like to manage REFER packet with opensips script
>  In my case i want manage REFER packet like whenever i opensips proxy
> getting REFER packet from freeswitch at that time i need to convert this
> REFER packet into INVITE packet from opensips script and send to the
> endpoint.
> Is their  any possibilities where I can manage this thing in opensips
> 3.1.x ?
> Please suggest me.
>
> My scenario like this:
>
> AopensipsB(Freswitch)
>   |   -INVITE --->|   ---INVITE-->   |
>
>   |   <-200OK ---|  <---200OK--|
>   |  <-INVITE ---   |   <---REFER|
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 

Best regards,
Donat Zenichev
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users