NandaKishoreE 71062 wrote:
> hi,
>
> I need to provide a high availability feature for our sip A/S.
> The current idea is to add a parameter into some headers of the sip message
> such as the route header, request-uri etc.(it is added to multiple headers
> because external UA may modify some headers such as request-uri)
>
> The parameter will indicate which A/S in the cluster is handling that dialog.
> This parameter will be used by a router to route in-dialog messages to the
> corresponding A/S.
>
> The problem comes when the A/S has crashed and the router needs to route a
> message to another A/S. It needs to route the message to some A/S2 & the
> parameter for that dialog needs to be modified accordingly.
> However,some header's such as route can be set only for initial requests and
> should not be modified later.
>
> My question is which header can be used/modified reliably for the above
> purpose of storing the parameter?
Is your AS a proxy, or a B2BUA?
If its a B2BUA, then it has a couple of options:
- It can modify its contact address, as this is dialog state that may
be changed.
- It can do an INVITE/Replaces to establish a new dialog replacing the
old one. The new dialog can have new values in Route headers.
(If its an intermediary then it would do this on both legs.)
If its a proxy there is little it can do. I guess maybe it could try
sending a REFER of an INVITE/Replaces to one of the UAs.
Paul
> regards,
> Nanda
>
>
> ******************************************************************************************
> This email and its attachments contain confidential information from HUAWEI,
> which is intended only for the person or entity whose address is listed
> above. Any use of the information contained herein in any way (including, but
> not limited to, total or partial disclosure, reproduction, or dissemination)
> by persons other than the intended recipient(s) is prohibited. If you receive
> this e-mail in error, please notify the sender by phone or email immediately
> and delete it!
>
> *****************************************************************************************
>
> _______________________________________________
> 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
