Hi ,

Thanks for your response . We can use the elements node as well and it's also helpful for development but RDM module purpose is different.

As per my understanding .

RDM module provide the property file where you can put prompt name , grammar name and other configuration like digit time out etc and it is useful to make the application configurable and easy to development.

From application , just need to pass property file name, global property file name as input instead of prompt and collect and all configuration controlled by the property file.

Regards
Tarun Jain

Hi Wilson,

Thank you for your input . What I understand , just need to add voice grammar file in Prompt and collect node and EP is responsible to send the link of grammar file to nuance for execution .

I was thinking we need to call external grammar (full url of Nuance server and put the grammar file in nuance server directory).So now this part is clear .

Thanks for your support.

Tarun Jain

Hi Team,

We have a new requirement to integrate our application with Nuance speech . Could you please share some sample application for understanding how to call Nuance (External Grammar file) from Avaya OD and how to extract response from grammar file in prompt and collect node.

Thanks & Regards
Tarun

Hi RossYakulis,

I have created one bot in AWS LEX but don't know how to call from OD application . Could you please share me the sample code to call the bot.

Thanks & Regards
Tarun Jain

HI Team,

I need to download RDM module .Could you please share the URL

Thanks & Regards
Tarun Jain

HI Wilson,

I have downloaded the latest version 7.2.3.0803 but still facing same issue.

Could you please help me for some work around.


URL:https://api.datamuse.com/words?rel_rhy=book

Output Format : JSON

Use Java Object

Thanks always for your support.

Regards
Tarun

Hi Team,

I am trying to execute below url from rest web service operation in OD 7.2.3

https://restcountries.eu/rest/v2/name/eesti

But I am getting below error.

java.lang.RuntimeException: Error obtaining parser from data source:org.codehaus.jettison.json.JSONException: Expected a ':' after a key at character 5 of {"["name"":"Estonia","topLevelDomain":[".

Although url is working fine . I have checked by postman app.

Even any url i am using I am getting same error. Screen shot attached of OD.

Thnaks & regards
Tarun jain

Hi Team,

When I am using Get Contact info variable for POM application then I am getting below error

“The variable selected to hold Result of Getting Contact Info does not contain field PhoneNumber1State”

Could you please guide me how to resolve this error.

OD Version : Version: 7.2 (7.2.1.0502)

POM Connector :PomPDCInstallerSite_3.01.02.028

Hi Team,

The standard OD installation doesn't include the POM connector.

Please help me how to install Avaya POM Connector in Avaya Aura Orchestration Designer application

Hi Team,

We have replaced a new prompt with old prompt but the name remain same. But It is being played with old announcement only near about 30 min and after that automatically new announcement being played.

I think it was playing from cache . Customer requirement it should be play immediately after replacement the prompt.

Could you please guide me how to achieve this .

Hi WilsonYu ,

Thanks for clarification. Actually in my application we have 5 module and each module have good amount of call. Any work around if we can create 5 logs file from root application only and insert the logs based on choose module from root application in each file end to end (one call one session ).

We have multiple module in our project . Call landed in startup application and then based on option routed to the different module and it is working fine. But we are facing one issue call logs only made in startup application . We want module logs in module application only.

Could you please guide us how to achieve it.

Thanks WilsonYu for Your support.

Now we have conclude AES connector stabled the connection with AES server and requesting for information but AES connector return No call information massage back to Aes connector . Now we need to be checked the logs on AES server why AES server return no call information massage to IVR. Please let me know if it is correct

Hi WilsonYu ,

Thank you very much for your prompt response . I have checked the logs for extension 27127 and it had made connection both side NTT-AES and MY-AES and it is getting the event from both side for call 13541 but how can we conclude information is not coming while connection was stabled for both side.

Line 14327: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 27127 is 10
Line 14328: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 0 is 101 for call 13541 Provider:NTT-AES
Line 14329: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Active Event
Line 14330: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 1 is 106 for call 13541 Provider:NTT-AES
Line 14331: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Created Event for id:13541
Line 14332: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: Saving most recent call created:13541
Line 14333: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127: call id is 13541
Line 14334: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127: ucid is 00001132141497510482
Line 14335: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127: setting 13541 to state: initiated
Line 14336: 15/06/2017 15:12:50:251 DEBUG - CallInfoData.CallInfoData:27127: callid 13541
Line 14337: 15/06/2017 15:12:50:251 DEBUG - CallInfoData.CallInfoData:27127: ani 0177668508
Line 14338: 15/06/2017 15:12:50:251 DEBUG - CallInfoData.CallInfoData:27127: dnis 24193
Line 14339: 15/06/2017 15:12:50:251 DEBUG - CallInfoData.CallInfoData:27127: ucid 00001132141497510482
Line 14340: 15/06/2017 15:12:50:251 DEBUG - CallInfoData.CallInfoData:27127: uui 22080
Line 14341: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127: added call to list
Line 14342: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127:cache is:false
Line 14343: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 2 is 105 for call 13541 Provider:NTT-AES
Line 14344: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Connected Event
Line 14345: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 3 is 206 for call 13541 Provider:NTT-AES
Line 14346: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: got Call Control Connection Established Event
Line 14347: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: found 2 connections
Line 14348: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: state of connection 0 is 51
Line 14349: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: state of connection 1 is 50
Line 14350: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: Call is not fully established
Line 14351: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 4 is 106 for call 13541 Provider:NTT-AES
Line 14352: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Created Event for id:13541
Line 14353: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: Saving most recent call created:13541
Line 14354: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.addCall 27127: call id is 13541 is already added, returning call data
Line 14355: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 5 is 104 for call 13541 Provider:NTT-AES
Line 14356: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Alerting Event
Line 14357: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 6 is 203 for call 13541 Provider:NTT-AES
Line 14358: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent:27127: got Call Control alerting Event
Line 14359: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.updateCallState 27127: setting call:13541 to state:ringing
Line 14360: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 7 is 116 for call 13541 Provider:NTT-AES
Line 14361: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Terminal Connection Created Event
Line 14362: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 8 is 119 for call 13541 Provider:NTT-AES
Line 14363: 15/06/2017 15:12:50:251 DEBUG - CTICallObserver.callChangedEvent27127: got Terminal Connection Ringing Event
Line 14364: 15/06/2017 15:12:50:252 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 9 is 218 for call 13541 Provider:NTT-AES
Line 14365: 15/06/2017 15:12:50:252 DEBUG - CTICallObserver.callChangedEvent27127: got Call Control Terminal Ringing Event
Line 14366: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 27127 is 10
Line 14367: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 0 is 101 for call 13541 Provider:MY-AES
Line 14368: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Active Event
Line 14369: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 1 is 106 for call 13541 Provider:MY-AES
Line 14370: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Created Event for id:13541
Line 14371: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: Saving most recent call created:13541
Line 14372: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.addCall 27127: call id is 13541
Line 14373: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.addCall 27127: ucid is 00001132141497510482
Line 14374: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.addCall 27127: setting 13541 to state: initiated
Line 14375: 15/06/2017 15:12:50:486 DEBUG - CallInfoData.CallInfoData:27127: callid 13541
Line 14376: 15/06/2017 15:12:50:486 DEBUG - CallInfoData.CallInfoData:27127: ani 0177668508
Line 14377: 15/06/2017 15:12:50:486 DEBUG - CallInfoData.CallInfoData:27127: dnis 24193
Line 14378: 15/06/2017 15:12:50:486 DEBUG - CallInfoData.CallInfoData:27127: ucid 00001132141497510482
Line 14379: 15/06/2017 15:12:50:486 DEBUG - CallInfoData.CallInfoData:27127: uui 22080
Line 14380: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.addCall 27127: added call to list
Line 14381: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.addCall 27127:cache is:false
Line 14382: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 2 is 105 for call 13541 Provider:MY-AES
Line 14383: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Connected Event
Line 14384: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 3 is 206 for call 13541 Provider:MY-AES
Line 14385: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent:27127: got Call Control Connection Established Event
Line 14386: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent:27127: found 2 connections
Line 14387: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent:27127: state of connection 0 is 51
Line 14388: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent:27127: state of connection 1 is 50
Line 14389: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent:27127: Call is not fully established
Line 14390: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 4 is 106 for call 13541 Provider:MY-AES
Line 14391: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Created Event for id:13541
Line 14392: 15/06/2017 15:12:50:486 DEBUG - CTICallObserver.callChangedEvent27127: Saving most recent call created:13541
Line 14393: 15/06/2017 15:12:50:487 DEBUG - CTICallObserver.addCall 27127: call id is 13541 is already added, returning call data
Line 14394: 15/06/2017 15:12:50:487 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 5 is 104 for call 13541 Provider:MY-AES
Line 14395: 15/06/2017 15:12:50:487 DEBUG - CTICallObserver.callChangedEvent27127: got Connection Alerting Event
Line 14396: 15/06/2017 15:12:50:487 DEBUG - CTICallObserver.callChangedEvent 27127: Event: 6 is 203 for call 13541 Provider:MY-AES

Hi Team,

We are using AESconnector in AAOD IVR application to connect with AES. We have two sites Mytar and NTT and both side we have AES server as well as IVR application.

And both AES connector is configured as failover in runtime configuration.

Last Friday some network issue in NTT site but my mytar application also not able to get response from Mytar AES .

We need to understand how AES connector work internally. We have the log of MYtar AES server . I am attaching in attachment.

issue was continuous from 15:32:45:931 to 16:35:11:644 (Taken only the 'No call info available *' for all calls from the logs).

AAOD Version : Version: 7.0 (7.0.0.1801)