Anuradha Gupta wrote:
> How to maintain multiple dialogs should be implementation specific.
> RFC 3261 explains about forking at multiple places.
> As the forked reponses differ on "To Tag" therefore multiple dialogs need to
> be maintained on the basis of To Tags till the time forked provisional
> responses are received, and when the first final response is received the
> call should be established with the UAS sending the first final response and
> media should also be applied in accordance with the offer-answer with the UAS
> sending the first final response.
> Once the call is established, then the other dialogs should be released after
> waiting for certain time. This is because if final response is received from
> other UAS then after sending ACK, BYE should be sent to these UAS.
While it might be common to drop additional dialogs by sending BYE, it
is not required that you do so. AFAIK this is just common because many
UAs have no good alternatives. But an example of a UA that would have an
alternative is a conference mixer that is initiating calls to the
conference participants. If one INVITE results in multiple calls, then
it very well might want to keep them all.
Even a "typical" UA could keep them both as a service - treating them
much like a call waiting scenario.
Bottom line: this is an implementation choice.
Thanks,
Paul
> Anuradha
> Aricent
> ________________________________________
> From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Sarvpriya Gupta [EMAIL
> PROTECTED]
> Sent: Friday, October 10, 2008 12:00 PM
> To: [email protected]
> Subject: [Sip-implementors] handle forking of invite at UAC
>
> Hi,
>
>
>
> Can you please suggest a draft or RFC which says how to maintain
> multiple dialogs created with an INVITE in case of forking at UAC or in
> general.
>
>
>
> Thanks in Advance.
>
>
>
> Cheers!!!!
>
> sarvpriya
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received this
> message in error,please notify the originator immediately. If you are not the
> intended recipient, you are notified that you are strictly prohibited from
> using, copying, altering, or disclosing the contents of this message. Aricent
> accepts no responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
