Hi Anton,
despite of the name, AmSipDialog::transfer does not work that way. It is
a proprietary method which is (was?) used to transfer a session from one
SEMS instance to another, without requiring support for REFER at the
client side. The first SEMS instance sends a REFER to the second SEMS,
which will try to re-INVITE the other party, and notify the first SEMS
instance that it can now "forget" the call. In fact, SEMS will in this
case really just forget about the call, and won't send any piece of
signaling anymore for that session.
If you are looking or the normal call tranfser using REFER, I'm afraid
that it is not explicitly supported at the moment. This means that you
can either: stay in the signaling path as a strict B2BUA, just relaying
everything to the other side (this is what the default AmB2BSession does
when the relay mode is turned on), or add support for call transfer in
your application. This should be fairly easy, as you only need to send a
REFER, and then read the NOTIFYs to know whether or not you can tear
down your call legs.
Cheers
Raphael.
On 04.10.10 10:56, Антон Загорский wrote:
There are 2 call sessions: UAC1<->SEMS and SEMS<->UAC2, both are AmSession.
I want to transfer UAC1 to UAC2 and exclude SEMS from any SIP dialogs.
Can I use AmSipDialog::transfer for this purpose? I'm asking because of
AmSipDialog::transfer doesn't include Refer-To header in a REFER request.
[email protected]
www.oyster-telecom.ru
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
