Search results for query: *

I think it appears under transitions or something similar in the GUI. There are a few radio buttons like Disconnect etc but one of them is Route Call. btw it may not seem like it but scripting is easier & quicker imho than that GUI thing. And you have years of tips via the Nortel Symposium forum...

Hi William, Sure, just "route call <HG number>" in scripting. Not sure what it is in the GUI thing because I refuse to use it.

Hi William, HDX probably easiest/quickest way to do this. Looks straightforward with a single query to the SQL DB with a Yes/No reponse. Use the DIW wizard to create the connection to SQL & generate the query and then deal with the responses in ACCS scripting. Let me know if you need more info...

Hi Brian, I haven't tried it but you should be able to screenpop a URL within Agent Desktop and use the various call intrinsics such as CLI to pop it. Configured in the Multimedia Admin utility, Agent Desktop, Basic & Advanced screenpops. Good luck! Alan

Hi Brian, It's not necessarily a config issue. On startup AAAD looks firstly locally (I think its usually c:\ProgramData\Avaya\Avaya Aura Agent Desktop) and then checks the server either for an updated or a new copy of the AAAD config xml file. That's what the message may be indicating. It...

I'd recommend installing the latest ISO 7.1.2.1 and associated patches rather than 7.0.1.0, which is rather old. Same license as all 7.x releases apply.

Hello, The basic script logic will be fine. Most of the work will be replacing all of the voice processsing scripting (open voice session, give ivr, etc) with the equivalent sip based commands. Also the voice segment variables will have to be changed to string or you could use routes in...

How was AMS 8.0 deployed? If upgraded from 7.7 directly to 8.0 this is unsupported. It must be 7.7->7.8->8.0. It will have to be rebuilt/redeployed, assume there is a db backup.

Try opening AMS EM in Chrome/Firefox rather than IE/Edge. No real need to add cert from IPO into AMS unless you are enabling Security in ACCS. Delete/Edit the accssync account in Partition Mgmt. If you are editing it, let's say change password then the details must be updated in the IPO under...

I would try deleteing the CCMA account & recreating it. Then maake sure to update details in IPO/SystemContact Centre to match it. Is it Prompt Management that is giving 'this page can't be diaplayed' message? When ACCS was upgraded to 7.1.2, was AMS also upgraded? 7.0.3 requires AMS 7.7...

Check/reset the account in IPO it's using to synch.

What I mean is are you using text based scripting e.g. IF THEN ELSE etc or the GUI flow based drag n drop type? By default ACCS will always queue the call until an agent is available but within scripting you have lots of options for changing call handling depending on what you want to acheive.

That CCMA_CCMAAMSService logfile must be there or there is something very wrong going on.

Check FQDN also so AAMS-HA.edco.jo etc. But in those logfiles I mentioned see if it is trying the FQDN or hostname only. If FQDN try changing it to FQDN under Media Servers in ACCS.

One, or all of those steps have fixed it for me whenever it has happened (several times on both ACCS & AACC). It usually fails for some security reason due to servername, fqdn etc. Try accessing Prompt Mgmt from Launchpad & when it fails grab the CCMA_PrompManagement.log on ACCS. Also grab the...

They still apply.

Step 10 there should be pinging from ACCS, not AMS.

I dont think that error is causing the issue & it can be fixed by creating a self signed cert in AMS and applying it (assuming TLS/SSL is not in use). Check the following again: Avaya Aura Media Server Configuration- The following configuration must be carried out on all AAMS servers (VMWare...

It is indeed deployed in Hyper on a physical server, learn something new every day. :-) Check the logfiles in C:\Avaya, it must be failing on prereqs for deployment for some reason. Also the ACCS version is 7.1.2 correct? And have you installed all subsequent patches/bundles?

While ACCS may work on Hyper-V it is not supported and Workspaces is deployed via OVA and is Vmware only. I'm guessing Avaya are assuming a Vmware environment. From the ACCS docs: The Avaya Contact Center Select software appliance is supported only with the following virtualization...