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. > 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
