On 05.10.10 11:17, Антон Загорский wrote:
Thank you Raphael.
Then, the situation changed: now I have AmB2ABSession (with caller leg) and
AmSession. Is it possible to make AmSession as callee leg of AmB2ABSession?
But maybe I'm going wrong way.. =) There is incoming call UAC1<-> SEMS. Then
SEMS calls a group of numbers, after some call (UAC2) was established UAC1 should
talk with UAC2.
Well, not at the moment. However, I think this is a very interesting
feature, which could be realized in a fairly easy way. The existing
"transfer" function works in a similar way, but between two SEMS
instance instead of within the same server.
Here is how it could work:
1. the session connected to UAC2 should send a serialized version of
the state stored in its SIP dialog to the session connected to UAC1 with
some custom event.
2. UAC1 session picks up the event and injects the dialog state into a
new callee session (see AmB2BSession::createCalleeSession()).
3. UAC1 session sends a confirmation event to UAC2 session.
4. UAC2 session stops itself.
5. UAC1 sends a re-INVITE to takeover the dialog.
Though we don't have it right now, I think this feature would be worth
being included into the core, as this scenario could be very useful for
all sorts of apps, not only for your call center.
Please let us know about your progresses.
Cheers
Raphael.
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
