-- Update Solution --

Using URL parameter to parse the callId to voiceXML script, i.e. https://135.9.39.61/services/NotifyMeRecordService/resources/voice.jsp?callId=callId

In the voice.jsp, get the parameter by request.getParameter(“callId”), assign it to a variable by expr="'<%=callId%>'".

Then this variable can be submitted together with the record file.

Thanks for all help.

Hi all,

We are implementing an EDP snap-in including these steps:

1. generate a one party call
2. in callAnswered method, invoke the media service for playing an announcement
3. in callTerminated method, detect the callTerminationCause and check if it is dropped by the users.

However, now if the user drop the call when it is playing the announcement, callTerminated method cannot be invoked.
Am I missing something for this functionality?

Thanks for any suggestion.

Qian

Hi Joel,

I opened a DevConnect Ticket for technical support of EDP this morning, but it shows closed now.
The ticket number is 21328.
Is the ticket type "technical support" the right one?

Thanks,
Qian

Thanks for the information Bob!

How can we associate the call which makes record with the recorded wav file?

we have a callID for each call and a fileID for each recorded wav file.
But it seems I cannot locate the call object or any other identifier (like mediaID, vxmlRequestID) in the JSP file, which I use for receive data from voiceXML and save them. In this case, I cannot connect the callID with the fileID together.

Thanks all.

Now we can use voiceXML for recording and sending the audio file to other servers.

It is strange that sometime when I change the "type" value for the "record" tag in voiceXML, AMS will throw an "unsupported.format" error. But several munutes after(20 minutes longer), there is no error. No code changes.

<record name="msg" beep="true" maxtime="20s" finalsilence="4000ms" dtmfterm="true" type="audio/wav">
I switch the "type" value among "audio/basic", "audio/wav" and "audio/x-wav";

Does anybody know details about the voiceXML part in AMS? Is there a delay for this switch of audio types?


Regards,
Qian

Hi,

Here is my VoiceXML script:

<?xml version="1.0" encoding="UTF-8"?>
<vxml version="2.1" xmlns="http://www.w3.org/2001/vxml">
<form id="play0">
<record name="R_1" beep="true" dtmfterm="true" finalsilence="5s" maxtime="100s">
<prompt>
Here you will hear a beep indicating
that you should start your recording.
</prompt>
</record>
</form>
</vxml>


and here is some of the AMS log:

==========Data Start==========
(05-13 13:53:22.544)<I,Plat,main,00000000-0000-0000-0000-000000000000>
Dialog.Start:( private:( callid:"2b9b0f35-32b9-3f04-8e80-3826de02d461" url:(0:"https://135.9.39.61/services/NotifyMeRecordService/resources/voice.vxml" )
defpath:"file:///opt/avaya/app/amsinst/ma/MAS/platdata/CStore/StorageRoot/n-1408721378-4/defaults-gen-1/"))
==========Data End ==========

Also the log said "Fail request since no resource attached" in AMS.

Is the defpath that AMS will save .wav files in? how can I modified this path to our http server ?

Appreciate for any help.

Qian

Hi,

Is there any sample for me to learn how voiceXML worked in EDP?
All samples I can found in EDP API have only JAVA code, no voiceXML sample code.

I am even not clear how to assign a path for AMS to save those .wav files in voiceXML script.

Thanks,
Qian

Thanks Bob.

I create a file as voice.vxml on my http server and this time AMS error saying "Invalid document structure".
I tried to write sample simple lines in vxml format, but AMS error saying "Unknown element 'vxml'".
Do I need to create a vxml file manually and write in a specific format?


(05-12 15:46:53.957)<I,Interp,95214448,90ce9579-5646-38db-b788-0bfd04884b8b> (40)8000|com.avaya.vxi|DocumentParser::FetchDocument - Parse error in file "https://135.9.39.61/services/NotifyMeRecordService/resources/voice.vxml", line 1, column 1 - Invalid document structure
(05-12 15:46:53.957)<I,Interp,95214448,90ce9579-5646-38db-b788-0bfd04884b8b> (40)|com.avaya.OSBlog|308||

(05-12 15:46:53.957)<I,Interp,95214448,90ce9579-5646-38db-b788-0bfd04884b8b> (40)|com.avaya.vxi|990||URL=https://135.9.39.61/services/NotifyMeRecordService/resources/voice.vxml

(05-12 15:46:53.957)<I,Interp,95214448,90ce9579-5646-38db-b788-0bfd04884b8b> (40)|com.avaya.vxi|205||URL=https://135.9.39.61/services/NotifyMeRecordService/resources/voice.vxml

(05-12 15:46:53.957)<I,Interp,95214448,90ce9579-5646-38db-b788-0bfd04884b8b> (40)|com.avaya.vxi|999||message=fail to prepare document|URL=https://135.9.39.61/services/NotifyMeRecordService/resources/voice.vxml

Regards,
Qian

Thanks, now I have the right log...
Here is the vxml log:


(05-11 14:57:04.679)<I,Plat,NWLoResTimer,00000000-0000-0000-0000-000000000000> NWIniConfig: Handle notification: ANY_CHANGED_CONFIG 0
(05-11 14:57:14.223)<I,Plat,main,00000000-0000-0000-0000-000000000000> (31) Recv Evt:[MX_EVENT_GET_LINE_COMPLETE] MxReqID:[31] LnState:[call_state_connected] lnHnd:[53477377] CallDir:[1] ANI:[<sip:6898391f-980f-4f38-b83d-64fb46155fce@mediaserver>;tag=d94d4d62-6bae-3c80-8a04-5c1d0205c90d] DNIS:[<sip:dialog@135.9.39.73:5060;voicexml=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml>] sa:[:-3] VarDataLen:[2235]
(05-11 14:57:14.224)<I,Plat,main,00000000-0000-0000-0000-000000000000> (31) Dump AppData AppDataLen:[265]
(05-11 14:57:14.224)<I,Plat,main,00000000-0000-0000-0000-000000000000> (31) ==========Data Start==========
(05-11 14:57:14.224)<I,Plat,main,00000000-0000-0000-0000-000000000000> Dialog.Start:( private:( callid:"629da459-f213-3107-b7fb-28a79cbc4965" url:(0:"https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml" ) defpath:"file:///opt/avaya/app/amsinst/ma/MAS/platdata/CStore/StorageRoot/n-1408721378-4/defaults-gen-1/"))
(05-11 14:57:14.224)<I,Plat,main,00000000-0000-0000-0000-000000000000> (31) ==========Data End ==========
(05-11 14:57:14.224)<I,Plat,main,00000000-0000-0000-0000-000000000000> (31) AppId=c8dcbefd-66f9-1029-a199-9e50b495d05
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) CallID Session Gslid - [629da459-f213-3107-b7fb-28a79cbc4965]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) DialogID Gslid - [629da459-f213-3107-b7fb-28a79cbc4965]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) UCID - []
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Trace Diagnostics Disabled
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Change Line State [Wait for Dialog]===>[Idle]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Change Call Status [INACTIVE]===>[ACTIVE]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Issue mx_SetDTMFSequence() termchar:[#] Enable:[Yes]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Send Msg:[Dialog Prep Wait Rsp] TranID:[3] Result:[0]
(05-11 14:57:14.224)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Send Msg:[Dialog Start] TranID:[0] Result:[0]
(05-11 14:57:14.224)<I,Integ,82258800,00000000-0000-0000-0000-000000000000> (31) Recv Msg:[Dialog Prep Wait Rsp] TranID:[3]
(05-11 14:57:14.224)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Preparing dialog
(05-11 14:57:14.224)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Trying URL[https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml]
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|VXI::Prepare - loading defaultDoc.
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchDocument()
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchBufferFromDB(, NULL)
(05-11 14:57:14.224)<I,Plat,82258800,00000000-0000-0000-0000-000000000000> getAppDefaultsDoc() : Success!
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchBufferFromDB - success
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchDocument - latency in microseconds min 39, max 39, avg 39, count 1
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::Memory Cache Statistics: Hits=0, Misses=0, TotalBytes=5323, MaxBytes=1048576
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::Memory Cache: Hit
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchDocument(): Default document - success
(05-11 14:57:14.224)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8005||URL: , contentFile: /opt/avaya/app/amsinst/ma/MAS/common/log/vxidump/mps1_vxmli/00000031/com.avaya.vxi.00000000
(05-11 14:57:14.225)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|VXI::Prepare(https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml)
(05-11 14:57:14.225)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchDocument(https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml)
(05-11 14:57:14.226)<I,Plat,main,629da459-f213-3107-b7fb-28a79cbc4965> (31) Recv Evt:[MX_EVENT_SET_DTMF_SEQ_COMPLETE] MxReqID:[342]
(05-11 14:57:14.245)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchBuffer(https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml, { (inet.timeoutDownload, 15000), (inet.urlEncoding, UTF-8) })
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31)|com.avaya.SBinet|219||URL=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml|Method=GET|HTTPStatus=404|HTTPStatusDescription=Not found
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8000|com.avaya.vxi|DocumentParser::FetchBuffer - could not retrieve absolute path of document at URL: https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8002|com.avaya.vxi|DocumentParser::FetchDocument - latency in microseconds min 39, max 8275, avg 4157, count 2
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) 8000|com.avaya.vxi|DocumentParser::FetchDocument - exiting with error result 2
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31)|com.avaya.vxi|203||URL=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml
(05-11 14:57:14.254)<I,Interp,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31)|com.avaya.vxi|999||message=fail to prepare document|URL=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Prepare failure rc=-100
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Wait for dialog start
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Waiting for message ReqId:[0]
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Recv Msg:[Dialog Start] TranID:[0]
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) uuiSharedMode = false
(05-11 14:57:14.254)<I,Integ,82258800,629da459-f213-3107-b7fb-28a79cbc4965> (31) Session ECMAScript:
var connection = {local:{uri:'<sip:dialog@135.9.39.73:5060;voicexml=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml>'},remote:{uri:'<sip:6898391f-980f-4f38-b83d-64fb46155fce@mediaserver>;tag=d94d4d62-6bae-3c80-8a04-5c1d0205c90d'},protocol:{name:'sip',version:'2.0',sip:{headers:{'to':'<sip:dialog@135.9.39.73:5060;voicexml=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml>','from':'<sip:6898391f-980f-4f38-b83d-64fb46155fce@mediaserver>;tag=d94d4d62-6bae-3c80-8a04-5c1d0205c90d','call-id':'ea6da8c8-49270987-13c4-6006-7eb521-6157363d-7eb521','cseq':'1 INVITE','content-length':'407','content-type':'application/sdp','via':'SIP/2.0/UDP 135.9.39.73:5060;branch=z9hG4bK-7eb521-eef38ad9-1856aaab-eb0ee5a8-0xea6da8c8','accept':'application/sdp, text/*, application/msml+xml, application/moml+xml','user-agent':'Avaya Media Server 7.6.0.959','max-forwards':'70','supported':'100rel,replaces,sdp-anat','x-nt-gslid':'d94d4d62-6bae-3c80-8a04-5c1d0205c90d','allow':'INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,REFER,NOTIFY,PRACK,UPDATE,MESSAGE','contact':'<sip:6898391f-980f-4f38-b83d-64fb46155fce@135.9.39.73;nt_service=6898391f-980f-4f38-b83d-64fb46155fce>','user-to-user':''},requesturi:{'transport':'udp','voicexml':'https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml'}}},aai:'',uui:'',ccxml:'',originator:undefined};
session.connection.uui=session.connection.protocol.sip.headers["user-to-user"];
session.connection.ccxml=session.connection.protocol.sip.requesturi["ccxml"];
session.connection.protocol.sip.requesturi.toString = function() { return "sip:dialog@135.9.39.73:5060;transport=udp;voicexml=https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml"; };

session.connection.redirect = new Array();

session.connection.originator=session.connection.remote;

var com = {avaya:{navigator:{userAgent:'MAS/7.6.0.959'},ivr:{call:{id:'629da459-f213-3107-b7fb-28a79cbc4965'},dialog:{id:'629da459-f213-3107-b7fb-28a79cbc4965'}}}};

(05-11 14:57:14.258)<I,Plat,82258800,00000000-0000-0000-0000-000000000000> omIndexFromVxiStr() - The event string is error.badfetch.http.404


All the error log is focus on the 404 not found for the URI I set for voiceXMLScript.
This URI pattern is supposed to be: https://135.9.39.61/services/NotifyMeRecordService/resources/wav/<resourceID>.vxml
The resourceID is generated in the code for each unique call, and then use this ID for locating voiceXML script.
For sure it will give the 404 not found error on this URI.
So did I misunderstand the logic of creating an voiceXMLDialogItem and startVoiceXMLDialog ?

Yes I did.
And for all the log files which related to vxml, there is no log recorded since April 21st.
I also check other files under this folder, but most of them haven't log anything since April, except the javaDebug.txt.

Hi bob,

I report this issue to the server team and they said this SSL warning should not cause the problem since the URI I used has the System Manager management certificate.

Besides this warning message, there is no other warning or error log related to voiceXML in AMS.
Is is possible that we get this "A severe error has occurred" announcement while no error log in AMS?

Thanks,
Qian

Hi,

There are some SSL connection warning in the AMS log, saying" self signed certificate in certificate chain".
The EDP API voiceXML sample which I followed use HTTP address as URI, while mine is HTTPS. Does the setVoiceXMLScript method support HTTPS uri?

Here is part of my code:
final URI documentUrl = new URI(https://135.9.39.61/services/NotifyMeRecordService/resources/wav/voice.vxml);
voiceXMLDialogItem.setVoiceXMLScript(documentUrl);
final MyVoiceXMLDialogListener voiceXMLDialogListener = new MyVoiceXMLDialogListener(
myCall.getCallingParty());
final UUID vxmlrequestId = SpeechFactory.createSpeechService()
.startVoiceXMLDialog(myCall.getCallingParty(),
voiceXMLDialogItem, voiceXMLDialogListener);
logger.info("After Digit collect, VoiceXML dialog started with requestId "
+ vxmlrequestId.toString());



Also, which log file I should investigate for vxml trace? There are lots of logs in AMS like vxmliDebug.txt, vxmliAppDebug.txt, vxmli1Debug.txt. None of them has the log information related to my test.

Thanks,
Qian

So for AMS log, is it the one use command "ce dlogon" and "ce dlogv" (or "ce dlogt") on our EDP lab server?

Hi Joel,

All the snap-ins are in our EDP lab server.

Hi Bob,

Sorry I don't have access to AMS log. What are the possible reasons could be? Is it related to the URI I set for this voiceXMLDialogItem?

Thank you,
Qian