Hi
Proxy is behaving properly in this scenario by forwarding all 18X responses
to UA .
So your client should do these things on getting multiple 18X responses on
diff legs
1. Create 3 differnent early dialogs and play early media if SDP present
2. When user cancels call from UI ,then your client will send a single
Cancel to terminate all probable early dialogs.
Thats why Cancel is designed to go without To-Tag so that it can
cancel all legs .
3. In Case user not pressing Cancel from UI and your client wants to
cancel some particular early dialog due to some use-case
Client can trigger BYE with to-tag of that early dialog and other 2
early dialogs would still be there .
Thanks & regards
Ankur Bansal
On Tue, Sep 10, 2013 at 12:29 PM, isshed <isshed....@gmail.com> wrote:
> *Hi All,*
> *
> *
> *Below is the scenario we need to implement for our client. This is a
> forking scenario.*
> *
>
> UA Proxy
> **| INVITE |
> **|———————--------—>|
> **| 100 Trying |
> **|<————————--------|
> **| 180 Ringing: To tag=A |
> **|<———————-------—-|
> **| 180 Ringing: To tag=B |
> **|<———————-------—-|
> **| 180 Ringing: To tag=C |
> **|<——————------——-|*
> *
> *
> *
> *
> *
> *
> *
> *
> *As soon as we get 180 ringing we are cancelling call by pressing Cancel
> button. how should my phone behave? Does it need to send cancel to all
> three dialogs? Is proxy misbehaving by sending the 180s (with Tag B and
> C)?
> *
> *
> *
> *Please comment on the implementation?*
> *
> *
> *Thanks.*
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
