Message |
[+]
Avaya Orchestration Designer
» REST service GET method - DOCTYPE is not allowed issue coming in response , 04/12/2020 00:54:41
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» REST service GET method - DOCTYPE is not allowed issue coming in response , 03/12/2020 08:51:24
» Go to message
|
|
Hi,
Thanks for your info.
Can we replace this DOCTYPE to empty in response parameter received using any Override method in REST API.
If so please let me know that override method to change the extracted response.
Just to remove this <DOCTYPE> from Response . something like that.
Thanks
|
|
[+]
Avaya Orchestration Designer
» REST service GET method - DOCTYPE is not allowed issue coming in response , 27/11/2020 08:27:31
» Go to message
|
|
Hi Team ,
I am receiving an error " DOCTYPE not allowed" on calling a inbuild REST API - GET method. Below is the error message
.............................................................................................................................................................................
.... INFO - XXXXX:/XXXXXX: Response had content type: text/xml. Retrying call with new type...
.... ERROR - XXXXX:/XXXX : AXISFAULT during web service call: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
.... ERROR - XXXXX:/XXXX: EXCEPTION: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
.... INFO - XXXX:/XXXX: Capturing exception [org.apache.axis2.AxisFault]. Message [javax.xml.stream.XMLStreamException: DOCTYPE is not allowed]
EXCEPTION>
java.lang.Exception: org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:130)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:285)
at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:743)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:485)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:410)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:337)
....
Caused by: org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
at com.avaya.sce.runtime.connectivity.restws.Axis2RestStub.run(Axis2RestStub.java:190)
at com.avaya.sce.runtime.connectivity.restws.Axis2RestStub.execute(Axis2RestStub.java:156)
at com.avaya.sce.runtime.connectivity.restws.CallService.execute(CallService.java:370)
at com.avaya.sce.runtime.Data.evaluateActions(Data.java:191)
at flow.CheckPhone.executeDataActions(CheckPhone.java:79)
at com.avaya.sce.runtime.Data.handleRequest(Data.java:104)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96)
... 156 more
Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.buildNext(OMDocumentImpl.java:153)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.getFirstOMChild(OMDocumentImpl.java:242)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:113)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
at org.apache.axis2.builder.ApplicationXMLBuilder.processDocument(ApplicationXMLBuilder.java:67)
at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:179)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)
... 170 more
Caused by: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:36)
at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:668)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
Actual response which we are trying to extract is [ from SOAP UI ]
<!DOCTYPE xgdresponse SYSTEM "xgdresponse.dtd">
<!--nsr: snd1-->
<xgdresponse version="1.0">
<errorcode>0</errorcode>
<response>
<result>
<errorcode>0</errorcode>
</result>
</response>
</xgdresponse>
Could you please help us in resolving this issue ?
Thanks
|
|
[+]
Avaya Orchestration Designer
» wave files not playing when calling direct line : Calling AAOD speech project from Peripro, 19/06/2019 01:48:55
» Go to message
|
|
Thanks , Will Look on it .
Please let me know if there any other ways where we can access on it .
|
|
[+]
Avaya Orchestration Designer
» wave files not playing when calling direct line : Calling AAOD speech project from Peripro, 07/06/2019 01:12:08
» Go to message
|
|
Hi
Thanks , Please let me know if this information helps
135:<block>
136:<prompt bargein="true" bargeintype="speech" timeout="8000ms">
137:Test Sample TTS
138:</prompt>
139:<prompt bargein="true" bargeintype="speech" timeout="8000ms">
140:Wave readout Start
141:<audio src="http://MACHINE:8080/test_tts/data/english/phrases/1990.wav">:sil.050</audio>
142:<audio src="http://MACHINE:8080/test_tts/data/english/phrases/0802.wav">:02 pounds</audio>
143:Readout End
144:</prompt>
145:</block>
146:<catch event="connection.disconnect">
in above log... when i call from peripro ":sil.050" read as 'colon sil zero five zero' and ":02 pounds" read as 'colon zero two pounds '
wave files are not been played .
|
|
[+]
Avaya Orchestration Designer
» wave files not playing when calling direct line : Calling AAOD speech project from Peripro, 04/06/2019 02:25:08
» Go to message
|
|
Hi ,
I am hosting AAOD speech project from my machine using tomcat and I am calling an speech project application from peripro using INVOKE Vxml block .
When i dial through phone line , the AAOD application which I created is picked successfully and TTS messages and logic over there were working as expected . But the wave-file which loaded in AAOD speech project are not playing .
TTS also is not playing as same as played in simulator . ' for Sil 50 ' it is playing as such when called from peripro.
Those wave file prompts and TTS are playing as expected when i simulate in AAOD but not playing when i call from peripro.
Could you please help me to get it resolved.
Thanks
|
|
[+]
Avaya Orchestration Designer
» Windows TTS does not work with Simulator , 04/06/2019 02:03:06
» Go to message
|
|
Hi ,
I am also facing same problem , [ AAOD 7.2.1]
When i simulate Speech project , I could able to hear only content of the wave files, TTS messages are not playing in my machine .
I kept en-gb as TTS , ASR and Localization (en-gb 3.1.4). here wave files are playing and TTS not played
when i use en-us , TTS messages were playing , could not able to identify where the issue was.
I tried MSSpeech also , it is working ..
Could you please help?
|
|