On 07.10.10 11:35, Антон Загорский wrote:
For your scenario, the following steps should be enough:
- create/start as many AmB2[A]BCalleeSession instances as
destinations, save the callee session id list in the caller session.
- when a positive final callee reply is received in the caller
session, set other_id to that callee session id, and send
B2BTerminateLeg events to the other sessions (just like
terminateOtherLeg() does, but for more than one session).
- when a negative final callee reply is received, just remove that
callee session id from your list on the caller side.
Ok, tnanks.
Do you think parallel forking should be native added to AmB2*BCallerSession ?
(As a parameter of connectCallee or as a class field)
Yes, it does, as a parameter to connectCallee().
-Raphael.
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
