Client channels direction is opposite indeed: when you make a call from
UI you send the call to the Yate engine so from the engine's point of
view the client channel it's the incoming call leg.
You log is incomplete.
Please attach one with a full call (start to hangup), message sniffer
Can also explain what is the actual issue?
Keep in mind that in Yate client UI when you make a call transfer what
1. Yate makes another call
2. Media is connected between remote peers: it stays in yate
3. You can always cancel the transfer by picking up the initial call
There is no call transfer request sent to remote party.
On 22.01.2015 10:33, Dragon wrote:
> Thank you reply .The attachment is log and image .
> I find YATE outgoing an incoming is opposite?â
> now i want to write a active control for sip client on YATE Engine. wish
> you support me or give me some
> ------------------ åå§é®ä»¶ ------------------
> *åä»¶äºº:* "Marian Podgoreanu";;
> *åéæ¶é´:* 2015å¹´1æ22æ¥(ææå) ä¸å3:40
> *æ¶ä»¶äºº:* "yate";
> *ä¸»é¢:* Re: [yate] transfer call
> Can you post a log (with message sniffer enabled) to see what happens?
> On 22.01.2015 05:37, Dragon wrote:
> > hi,
> > i have a question that how to transfer call in YATE Client. if
> > transfer a call ,but the call don't transferred.
> > i try to set transfer = true in ysipchan.conf file ,yate client will
> > throw a error. thank you.ââ
> > robben