DMCC Monitor VDN with CTI Link

[avc876021839702]

Hi - I have an application written in C# .NET using the DMCC API. The application monitors VDN for call events (delivered, establish, connection cleared, etc.) At the start, I was monitoring pre-existing VDNs and I received all the events I needed. However, when a new VDN is created and used in my application, I received no events. We discovered that the CTI link was not associated with the VDN that was newly created. See attachment. VDN 116665 has link 47 associated with it. The screen shot does not show a VDN that was newly created, but the new VDN looks similar to 116790. Everything is the same except there is no CTI link number in the "EventNotif" column. My question is: Once I have my AES session created, got the device, and started the monitor, how do I associate the CTI link with the VDN using the DMCC API. We don't see any place to add it in the CM screen when creating the VDN either. If there is a way to make the association some other way that would be fine too.

Any help with this would greatly appreciated.

Thanks
Tony

[avc876021839702]

Posting a larger attachment

[flynn1]

The attached image is too small to read. What is is? Where does it come from?

When you started the monitor on the new VDN, did you get a positive response or an error?

[avc876021839702]

When starting the monitor on the new VDNs, the responses were the same as the old VDNs - so I would say yes to getting a positive response.


Hopefully you can read this image.

zz0.9c5y3uoe41zz

[flynn1]

The Event Notif field is automatically filled in by Communication Manager when a monitor has been placed on the VDN by an application, using MonitorCallsViaDevice. It contains the CTI Link number of the AE Services used by the application. There is no way to manually fill it in.

So, it looks like the application was NOT actually successful when starting the monitor. I think your next step is to enable TSAPI traces and see if they give any better information. There is some information on enabling TSAPI traces in https://support.avaya.com/forums/for...rking-with-wti

Martin

[avc876021839702]

Martin,

My app was already using the callsViaDeviceEvents monitor but your suggestion to use it validated that I was doing something right. So I checked my code and apparently monitoring the callControlEvents in addition to the callsViaDeviceEvents on the VDNs is what broke the association of the CTI link. I commented the callControlEvents monitor and the VDNs now show the associated CTI link.

THANK YOU for your help !!!
Tony