Hi, René (ALT-0233

),
thank you for your reply.
Yes, it does have it, but I simply do not see a reason why they would not have a unified SIP/CTI library, because to me it seems like it is a very logical step in expanding Genesys CTI signalling. [b][color=red]Especially if they are planning on people using their SIP Server[/color][/b]
I am also using RTC and Genesys ActiveX, but you know, sometimes, it is really frustrating, because basic things refuse to work. Develping an attended transfer provides to be a total nightmare!
Here how it is according to Cisco:
[attach=1]
And interestingly enough, it is not working like that when we are attempting to do it with RTC 1.3 and SIP Server 7.2. I am sure that probably we are not having the right tag or CallID or SDP parameter, but, what is the point of using TTransferInit for example, if we still need to handle INVITE, SDP and the rest of the commands using a Microsoft-based library? We might as well start the whole call control routing (including transfer) using Microsoft RTC and just use Genesys CTI for popup and Agent state control. And if we are to do that, I might as well be coding for Asterisk or whatever other SIP server is out there. If Genesys is really serious about its SIP line, it should get its act together and come up with a complete solution and not ask us to put together bits and pieces of technologies from three different vendors. I feel like I am back using Aspect CTI which was all about scripting and required deep knowledge of SQL, Java Script, and pretty much made you feel like you were a Web developer using Notepad to develop a company homepage!