[OpenSIPS-Users] Waiting for 200 OK

Wed Apr 10 06:01:15 UTC 2024

Sorry my bad!
Actually I need to Wait for a specific time after 200 OK received from Bleg.
So in that specific time If I received Re-invite from Aleg then I need to
simply realy or if not received then need to do some other operation.

Regards,
*Parthesh Bhavsar | Software Engineer | VOIP*

On Tue, Apr 9, 2024 at 9:11 PM Ben Newlin <Ben.Newlin at genesys.com> wrote:

> This is a valid point that I missed. You can’t send an INVITE back to the
> UAC while the original INVITE remains unanswered. The UAC should/must
> respond with a 491 Request Pending.
>
>
>
> This is the use case that UPDATE was created for, and that would work if
> the UAC supports it. If it must be INVITE then you would have to be a B2BUA
> because you would have to answer the initial INVITE from the UAC while the
> outgoing INVITE was still in progress, so that you could do the re-INVITE.
>
>
>
> Ben Newlin
>
>
>
> *From: *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Date: *Tuesday, April 9, 2024 at 10:55 AM
> *To: *Parthesh Bhavsar <parthesh.bhavsar at ecosmob.com>, OpenSIPS users
> mailling list <users at lists.opensips.org>, Ben Newlin <
> Ben.Newlin at genesys.com>
> *Subject: *Re: [OpenSIPS-Users] Waiting for 200 OK
>
> * EXTERNAL EMAIL - Please use caution with links and attachments *
>
>
> ------------------------------
>
> Hi,
>
> my 2 cents here - how comes you want to send a RE-INVITE _BEFORE_ having
> the dialog established???
>
> Regards,
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
>   https://www.siphub.com
>
> On 09.04.2024 17:35, Parthesh Bhavsar via Users wrote:
>
> It seems after setting T_fr_timeout parameter it was sending a CANCEL
> request to another leg but for my requirement I need to send Reinvite. Also
> for generating Reinvite I have used  dlg_send_sequential() as I use
> opensips as a proxy server. Any other modules on which I look for?
>
>
>
> Regards,
>
> *Parthesh Bhavsar | Software Engineer | VOIP*
>
>
>
>
>
> On Tue, Apr 9, 2024 at 7:36 PM Ben Newlin <Ben.Newlin at genesys.com> wrote:
>
> The timing requirement can be solved using the $T_fr_timeout parameter [1].
>
>
>
> For sending a re-Invite back to the UAC I believe you’d have to be a B2BUA.
>
>
>
> [1] - https://opensips.org/docs/modules/3.4.x/tm.html#pv_T_fr_timeout
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Parthesh
> Bhavsar via Users <users at lists.opensips.org>
> *Date: *Tuesday, April 9, 2024 at 5:31 AM
> *To: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject: *[OpenSIPS-Users] Waiting for 200 OK
>
> * EXTERNAL EMAIL - Please use caution with links and attachments *
>
>
> ------------------------------
>
> Hello,
>
> I have a requirement where If I get 183 responses then I need to wait for
> a specific period of time for 200 OK and if 200 OK is not received in that
> time then I need to send Reinvte back to UA with some modifications. I have
> gone through the SST module but have not  found anything relevant to match
> my requirements. Can anyone suggest some module or function on which I can
> go further to meet my requirements.
>
>
> Regards,
>
> *Parthesh Bhavsar | Software Engineer | VOIP*
>
>
>
>
>
> * <https://www.ecosmob.com/opensips-summit>*
>
> *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.
>
>
>
> * <https://www.ecosmob.com/opensips-summit/>*
>
> *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
>
>
>

-- 
* <https://www.ecosmob.com/opensips-summit/>
*
*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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240410/6facad96/attachment-0001.html>