<div dir="ltr"><div>Good day Calvin.</div><div>There is no SIP method called "REDIREDCT" as you say.</div><div>Currently there are 6 general methods defined in RFC 3261, you can see them here: <a href="https://tools.ietf.org/html/rfc3261#section-27.4">https://tools.ietf.org/html/rfc3261#section-27.4</a></div><div><br></div><div>And of course a list of SIP specifications (documents) including following methods: PRACK, SUBSCRIBE, NOTIFY, PUBLISH, REFER, MESSAGE, UPDATE</div><div>which are defined in the list of other RFC documents.</div><div><br></div><div>But there is no method which you called. So that, please do not confuse the community with a wrong terminology.</div><div><br></div><div>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).</div><div>This block of response codes is commonly called as redirection responses. Response codes are not the same thing as SIP methods.</div><div>And most of all would be "302 Moved Temporarily" used, to provide Contact information where to find the requested side. Depends on setup.<br></div><div><br></div><div>This however seems to be completely not related to the original question of the author.</div><div><br></div><div>Best regards.<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 11, 2021 at 6:26 PM Calvin Ellison <<a href="mailto:calvin.ellison@voxox.com">calvin.ellison@voxox.com</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"><div dir="auto">Is it your intention to transfer an established call, or do you really a redirect?<div dir="auto"><br></div><div dir="auto">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.<br><br><div dir="auto"><br>Regards,<br><br><br>Calvin Ellison<br>Systems Architect<br><a href="mailto:calvin.ellison@voxox.com" target="_blank">calvin.ellison@voxox.com</a><br>+1 (213) 285-0555<br><br>-----------------------------------------------<br><a href="http://voxox.com" target="_blank">voxox.com</a> <br>5825 Oberlin Drive, Suite 5<br>San Diego, CA 92121</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 7, 2021, 23:12 Vinayak Makwana <<a href="mailto:vinayak.makwana@ecosmob.com" target="_blank">vinayak.makwana@ecosmob.com</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"><div dir="ltr">Hello Everyone,<br> I would like to manage REFER packet with opensips script <br> 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.<br>Is their any possibilities where I can manage this thing in opensips 3.1.x ?<br>Please suggest me.<div><br><div>My scenario like this:<br><div><br></div><div>A opensips B(Freswitch)</div><div> | -----INVITE -------> | -------INVITE------> | </div><div> | <-----200OK ------- | <-------200OK------ | <br></div><div> | <-----<span id="gmail-m_-2977136051711314196m_5938821853500788218gmail-docs-internal-guid-d3012b6f-7fff-7b34-5195-4686b4524475"><span style="font-size:11pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:rgb(255,255,0);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">INVITE</span></span> ------- | <-------<font face="Times New Roman" color="#000000"><span style="font-size:14.6667px;white-space:pre-wrap;background-color:rgb(255,255,0)">REFER</span></font>---- |<br></div></div></div></div>
<br>
<div><font style="background-color:white" size="2" face="Arial" color="#808080"><b>Disclaimer</b></font></div><div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small">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.</span></div></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><br></span></div><div><font style="background-color:white" size="2" face="Arial" color="#808080"><b>Confidentiality</b></font></div><div><font style="background-color:white" size="2" face="Arial" color="#808080">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.</font></div><div><font style="background-color:white" size="2" face="Arial" color="#808080"><br></font></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><b>Caution for viruses, malware etc.</b></span></div><div><font style="background-color:white" size="2" face="Arial" color="#808080">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. </font></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" rel="noreferrer" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr"><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">Best regards,<br></font></div><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">Donat Zenichev<br><br></font></div></div></div></div></div></div></div></div>