[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.ellison at voxox.com <mailto:calvin.ellison at voxox.com>
> +1 (213) 285-0555
>
> -----------------------------------------------
> voxox.com <http://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 <mailto: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 <mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210311/480681d2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xD7D896F7DDA70EC3.asc
Type: application/pgp-keys
Size: 2456 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20210311/480681d2/attachment-0001.key>