Hey gang,
I was able to create a working cti application using the wti socket endpoints with make a call, take a call, put a call on hold and most importantly, retrieve a call. I used the avaya document found here: https://support.avaya.com/css/public...ents/101036842 to get the recommendations for agent polling, and now I'm looking for best practices for dialing a call. So, I think a good place to start is to mimic Avaya One-X, and I see when I press any digit on the pad I hear a dialtone, and the agent state goes to "agentBusy, talkState: onCall, loggedOn: true".. then I didn't touch anything for 30 seconds and I got wave off. The question is how a CTI client can get the same effect: mark the agent unavailable while composing a number, and return to Ready if it's abandoned. I've tried SetHookswitchStatus and GetHookswitchStatus, and both returned {"unspecified": ""}.
Thanks for any help!
Dave Morrison
Software Engineer
I was able to create a working cti application using the wti socket endpoints with make a call, take a call, put a call on hold and most importantly, retrieve a call. I used the avaya document found here: https://support.avaya.com/css/public...ents/101036842 to get the recommendations for agent polling, and now I'm looking for best practices for dialing a call. So, I think a good place to start is to mimic Avaya One-X, and I see when I press any digit on the pad I hear a dialtone, and the agent state goes to "agentBusy, talkState: onCall, loggedOn: true".. then I didn't touch anything for 30 seconds and I got wave off. The question is how a CTI client can get the same effect: mark the agent unavailable while composing a number, and return to Ready if it's abandoned. I've tried SetHookswitchStatus and GetHookswitchStatus, and both returned {"unspecified": ""}.
Thanks for any help!
Dave Morrison
Software Engineer
