Re: Info on setting up Avaya CTI with Remedy....

[Angus Comber]

** I assume this is an interactive application.  ie an agent will be at a workstation who will 'deal' with this item.  If this is the case then you could use the Remedy User COM API.  There is a COM object model - you can automate the Remedy user tool just as you would automate Word for example.   I have done this sort of thing with CallerID from a ringing phone.  But same principle should apply to IVR scenario.   What programming language are you using/want to use?   If you need some sample code let me know.   Angus   ----- Original Message ----- From: Gray, Alexander Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Sent: Wednesday, July 12, 2006 4:00 PM Subject: Re: Info on setting up Avaya CTI with Remedy.... ** Angus   Basically I am looking to pull the employee ID and company data that comes through the IVR system so that we can pull into Remedy to pop the customer’s info inside the ticket. We are using ITSP 4.0   Any advice would be greatly appreciated   Alex   From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Angus Comber Sent: Wednesday, July 12, 2006 4:43 AM To: arslist@ARSLIST.ORG Subject: Re: Info on setting up Avaya CTI with Remedy....   What exactly are you looking to do?  Surely if you pop a Remedy screen from an IVR you are going to get a LOT of screenpops?   DDE is very naff.  Wouldn't recommend.  There are other ways.   Angus   ----- Original Message ----- From: Gray, Alexander Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Sent: Tuesday, July 11, 2006 10:54 PM Subject: Info on setting up Avaya CTI with Remedy....   ** Folks,   Need some info or help in setting up CTI caller screen pops using the Avaya IVR system. Can you use DDE and runmacro to make it happen or any other way is fine too.   Thanks   Alex __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___