On 05.10.10 17:21, Антон Загорский wrote:
AmB2ABCallerSession::connectCallee() doesn't terminate (current
callee) session immediately.
Then it's a bug ;-)
Reported, please see at
https://bugtracker.iptel.org/view.php?id=47
Thx!
But could we please try to reformulate your scenario so that I can
understand what you are trying to reach?
Is that something like:
- A calls.
- B& C (etc...) are called.
- the first to answer gets connected to A.
Yes, you are right. Also, there is a serial fork in plans.
Ok, serial forking is quite easy and should work by now (as Juha
demonstrated).
Parallel forking is somehow more complex, due to the fact that SEMS
supports only one SIP dialog per session. This means that SEMS does not
behave correctly if the INVITE is forked later on (for example using a
SIP proxy).
To be able to support that, we can either:
- modify the Am*Session classes to support multiple sip dialogs,
- or, create one session instance per dialog and keep there a list of
the other sessions (just like AmB2BSession does, but with more sessions).
The first option would probably allow for simpler application
programming, as you could directly access the other dialogs' pointers.
But in my opinion, the second option would be better suited for your
scenario, and would allow for merging calls as well, as described in
earlier emails.
Cheers
Raphael.
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
