Windows 10 is not officially supported for AACC Release 6.4. However have you added the CCMA managed host name into compatibility views and trusted sites?

Download the commissioning guide and check the client configuration settings for the browser.

Hi Imraan,

If you intend to use this for internal TFE routing in scripts you wont need a wdsl.
When using AAAD for example click on Display Raw Intrinsics on the lower left Intrinsic tab and you can see the information you might be looking for then Just use ASSIGN CONTACT DATA abc TO xyx_cv in the script.

Search for this in google and open the pdf and it shows a good sample of the contact scripting web service if needed.

avaya aura contact center exposed scripting web service

Regards
Matt

Hi Karen

If you need to be able to report on the calls via Historical reporting then you must have only Primary Applications.
Historical reporting does not list any Secondary applications in the drop down selection in CCMA.

In order to go from 1 primary to another primary you will have to use route call via a new CDN.
If reporting is not an issue then you can just keep everything in 1 script using sections. Just remember scripts can only contain 50,000 characters. So you can go from Primary to secondary using EXECUTE SCRIPT xxx.

As soon as you use EXECUTE SCRIPT that target script becomes a secondary application and you cant report on it.
To determine app type right click on the application in orchestration designer and it will show primary or secondary

Hope some help here
Matt

Hi Lakshmisha


You may find it very difficult to extract the agentid as the call has already left the TFE scripting engine for ASM routing.

All the captured intrinsic data needs to be collected before the Queue to skillset statement in order to populate the contactID and pass to the URL in ccmm. Unfortunately target agent id wont be one of these.

You may like to engage APS to develop reverse engine from the your pop server back into CCMS DB to pull that data based on the cmfContactID. Only issue I foresee is a delay in processing before the agent gets the screen pop.

Regards
Matt

Hi,

Client wants to block a callers CLI from being able to be called back by the agent.

We have been able to successfully manipulate the SIP_CALLER_DISPLAY, AD_CLID and FROM intrinsic data via TFE script using the contact scripting WSDL to show anonymous when agent answers a call on AAAD.

However when the agent opens the phone book and selects call history tab the number field still has the incoming number shown. We see the number in the getaddress within the CCT logs.

Is their any exposed web service we get set this?
If the caller CLI is blocked then off course its fine and agent sees sip:xyb@abc.com in the call history.
I know we can use adaptations in SM but back office wish to see this number.
Only need to block CC agents.

Any ideas?

Cheers
Matt