Ok, so let's recap this one for my poor small brain:
What do you guys expect from connectCallee()?
As far as I could understand, Juha is quite happy about what the method
does, and likes to use it from the ivr plug-in.
What you want, Anton, is still not very clear to me... except from the
fact that you seem to like C++ more than Juha does ;-)
Just as a small hint in the background: as designed and implemented by
the mighty devs (in this case, it was me), it is supposed to allow for
only one call at a time.
This means that if you call connectCallee() more than once in a row,
only the last call should work. However, there might be some flaws,
depending on how fast the next call to connectCallee() happens.
If this is not what you expected, then there is not much I can do about
that. But we could create another method, doing what you like, if it is
generic enough.
If this is not the way it works for real, then we obviously have a bug.
Cheers
Raphael.
On 05.10.10 16:24, Антон Загорский wrote:
-----Original Message-----
From: Juha Heinanen [mailto:[email protected]]
Sent: Tuesday, October 05, 2010 6:19 PM
To: Антон Загорский
Cc: 'Raphael Coeffic'; 'sems mailing list'
Subject: Re: [Sems] Transferring a session
writes:
I'm getting both ringing UAC2 and UAC3. In fact, UAC3 ringing early.
using ivr plugin, i don't get both ringing. my app has been running
fine for years. so forget c++ and code your app in dsm or ivr.
This can't be =) IVR plug-in is just C++ wrapper and self.connectCallee points
to AmB2BCallerSession.connectCallee
Raphael, please pay a more attention on this - Juha talks about _parallel
forking_ by means of _serial calling_ of connectCallee
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
