[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.ellison at voxox.com
+1 (213) 285-0555

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


On Thu, Mar 11, 2021 at 9:13 AM Donat Zenichev <donat.zenichev at gmail.com>
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 <calvin.ellison at voxox.com>
> 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.ellison at 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 <vinayak.makwana at 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 at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
>
> Best regards,
> Donat Zenichev
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210312/11bfb6e7/attachment.html>