Message |
[+]
Avaya Orchestration Designer
» Overwritten Fetch timeout is not working, 26/11/2018 01:27:08
» Go to message
|
|
Dear Team,
I have set the fetch timeout property in AEP to 30 Sec however I can change the same at application end by changing the approot property and doing the same I have used different fetch timeout for different request which I am triggering in same node but its not working.
I am triggering 4 requests in same node and after completion of 30 Sec the call is handled by AEP / event handler even though I have set the same value in application and set as 46, 60, 80 Sec for different request.
Need your input on this.
environment: AEP 7.0 and OD 7.0
Regards,
Nilesh
|
|
[+]
Avaya Orchestration Designer
» 404 class not found in OD application, 30/10/2018 23:52:06
» Go to message
|
|
Thank you for the response,
what you are saying that may be correct but here we have not change the war file and only change the flag which is no more related to any internal / external class becasue the same we did in UAT server which is working fine.
again when I revert that flag then application started working here we have not change any class path and no fresh deployment.
is it possible that the flag change reflected but still somewhere IVR application is pointing to old classes or at MPP level any cache is creating an issue.
Regards,
Nilesh
|
|
[+]
Avaya Orchestration Designer
» 404 class not found in OD application, 29/10/2018 23:45:09
» Go to message
|
|
Dear Team,
we are facing very weird issue in production environment, we are having an OD 7.0 developed application and deployed in production which is working fine but when we change the config to point to DR database at some extend we are getting class not found or 404 error while calling to next node (after few steps) where as the application is pointing to DR DB properly and rows are getting affected properly.
1. the same war file we have deployed in test environment with same settings (DR DB) and there its working
2. we have also tested the same scenario in OD simulation mode and that is also working
3. so code could not be an issue as the same war file is working in production but with production DB only.
4. we also found that whatever the recent changes we did those only having 404 error
5. however the old (previous) war file is working in production for both Prod DB and DR DB
is it possible that the new code is not reflected properly in first time deployment or something wrong in the package / deployment process
also we observed that the class files are not there in WEB INF folder which may be because of package process followed during war creation but its working for normal scenario.
there is no change in prod and DR DB so no chance to get any wrong value at any point which is causing the issue.
Regards,
Nilesh
|
|
[+]
Avaya Orchestration Designer
» DR Database Autoswitch incase of Production Database server not reachable, 24/11/2015 03:58:11
» Go to message
|
|
http://www.devconnectprogram.com/forums/posts/list/18610.page --------------reference from this post
http://www.devconnectprogram.com/forums/posts/list/18610.page
Dear Team,
Thanks to reply on this post....
the issue is still there, you might be not clear or we are able to make you understand the issue.
i want to share few points which we are using for OD app context module having following parameters to set,
defaultMaxActive ------- 100
defaultMaxIdle ----------50
defaultMaxWait-----------30000
removeAbandoned----------true removeAbandonedtimeout --60
when the production DB server is in network (reachable) and service is down then OD application is automatically switching to DR DB.
if the production DB server is shutdown (not reachable) then OD application is not automatically switching to DR.
I am suspecting the above parameters may cause to different behaviour in both case.
the removeAbandonedtimeout is for what and what should be the idle value for this parameter.
please rethink on this issue .
Regards,
Nilesh
+91-9920775766
|
|
[+]
Avaya Orchestration Designer
» DB Failover node in OD 7.0 is not working as expected. , 23/11/2015 23:48:03
» Go to message
|
|
Dear Team,
Thanks to reply on this post....
the issue is still there, you might be not clear or we are able to make you understand the issue.
i want to share few points which we are using for OD app context module having following parameters to set,
defaultMaxActive ------- 100
defaultMaxIdle ----------50
defaultMaxWait-----------30000
removeAbandoned----------true removeAbandonedtimeout --60
when the production DB server is in network (reachable) and service is down then OD application is automatically switching to DR DB.
if the production DB server is shutdown (not reachable) then OD application is not automatically switching to DR.
I am suspecting the above parameters may cause to different behaviour in both case.
the removeAbandonedtimeout is for what and what should be the idle value for this parameter.
please rethink on this issue .
Regards,
Nilesh
+91-9920775766
|
|
[+]
Avaya Orchestration Designer
» DB Failover node in OD 7.0 is not working as expected. , 10/07/2015 05:56:36
» Go to message
|
|
Hi Wilson,
Thanks for the response, actually in good call we cant see the DB source,
good call Log
--------------------------------------------------------------
27/06/2015 22:36:52:526 DEBUG - 0640449C29BEF4257818EBBCDBA920AF:/UAE_MAIN_APP : Executing DB statement : [INSERT INTO SCBIVR_AE.CALL_LOG_MASTER_REPORT ( CLI, DNIS, LANG, EXIT_VDN, IVR_HOST, STARTTIME, ENDTIME, UCID, RMN, ACCOUNT_CARD, DISPOSITION_TYPE, DISPOSITION_LOCATION, PRODUCT_ID, TRNF_DISC_CATEGORY, BANK_CARD, LOCATION, AGENT ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )]
27/06/2015 22:36:52:775 DEBUG - 0640449C29BEF4257818EBBCDBA920AF:/UAE_MAIN_APP : Rows affected : [1]
27/06/2015 22:36:52:775 DEBUG - 0640449C29BEF4257818EBBCDBA920AF:/UAE_MAIN_APP : session id:AEXVIPDXBMAEP01-2015178183338-10 | UAE_MAIN_APP:Account_Sel_Contd-Table_A_Call_Log_Master | ///////////////////////////////// Successful Insert //////////////////
---------------------------------------------------------------------------------------------
Bad call Log
--------------------------------------------------------------------------------------
28/06/2015 00:52:58:050 DEBUG - F2E863A55BB949B2B88DFDBA2D94E63F:/UAE_MAIN_APP : Executing DB statement : [SELECT EXIT_VDN.CALLFLOW, EXIT_VDN.PRODUCT_ID, EXIT_VDN.LANGUAGE, EXIT_VDN.VDN, EXIT_VDN.REGION FROM SCBIVR_AE.EXIT_VDN WHERE ( ( ( EXIT_VDN.CALLFLOW = ? ) AND ( EXIT_VDN.PRODUCT_ID = ? ) ) AND ( ( EXIT_VDN.REGION = ? ) AND ( EXIT_VDN.LANGUAGE = ? ) ) )]
28/06/2015 00:52:58:378 ERROR - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : Error executing sql. Exception : java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
28/06/2015 00:52:58:378 DEBUG - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : Execution fails over to data source - DB_Source_Failover
28/06/2015 00:52:59:189 DEBUG - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : set value to variable/field - MESSAGE_ID
28/06/2015 00:52:59:189 DEBUG - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : set value to variable/field - IVR_EMERGENCY_MESSAGE
28/06/2015 00:52:59:189 DEBUG - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : Rows affected : [1]
28/06/2015 00:52:59:189 DEBUG - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : session id:AEXVIPDXBMAEP01-2015178203429-13 | UAE_MAIN_APP:Fetch_ExitVDN | /////////////////////////////// Emergency Msg Details ////////// | Emergency_Msg:IVR_EMERGENCY_MESSAGE : D
28/06/2015 00:52:59:189 INFO - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : Assigning [Emergency_Msg:IVR_EMERGENCY_MESSAGE] to [Details(L)]
28/06/2015 00:52:59:189 INFO - E2932BF8006AA4EA50BF2E25446CB9D9:/UAE_MAIN_APP : Capturing exception [javax.servlet.ServletException]. Message [ EXCEPTION>
java.lang.NullPointerException
at com.avaya.sce.runtime.varoperations.Assign.evaluate(Assign.java:48)
at com.avaya.sce.runtime.Data.evaluateActions(Data.java:218)
at flow.Fetch_Fest_Msg_Details.executeDataActions(Fetch_Fest_Msg_Details.java:103)
at com.avaya.sce.runtime.Data.handleRequest(Data.java:104)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:285)
at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
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:748)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at com.avaya.sce.runtime.SCEServlet.forward(SCEServlet.java:1364)
at com.avaya.sce.runtime.Data.handleRequest(Data.java:153)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:285)
at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
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.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:503)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
]
28/06/2015 00:52:59:220 INFO - 1F1734BD64C50DC0708CF2467507A555:/UAE_MAIN_APP : Using SCESession 1F1734BD64C50DC0708CF2467507A555:/UAE_MAIN_APP servlet : Ann_Sys_Unable
28/06/2015 00:52:59:220 DEBUG - 1F1734BD64C50DC0708CF2467507A555:/UAE_MAIN_APP : *** Reply for [/UAE_MAIN_APP/Ann_Sys_Unable] ***
28/06/2015 00:52:59:220 DEBUG - 1F1734BD64C50DC0708CF2467507A555:/UAE_MAIN_APP : 0:<?xml version="1.0" encoding="UTF-8"?>
1:<vxml version="2.1" xmlns="http://www.w3.org/2001/vxml" xml:lang="en-us">
2:<meta name="author" content="Avaya Aura Orchestration Designer"/>
3:<meta name="runtime-version" content="07.01.08.04"/>
4:<meta name="runtimecommon-version" content="07.01.08.04"/>
5:<meta name="copyright" content="Copyright (c) 2002-2011, Avaya"/>
6:<form id="Ann_Sys_Unable">
7:<block>
8:<prompt bargein="true" bargeintype="speech" timeout="8000ms">
9:<audio src="http://10.145.170.38:8080/UAE_MAIN_APP/data/english/phrases/Sys_Unavailable.wav"/>
10:</prompt>
11:</block>
12:<block>
13:<submit next="Play_Xfer?___DDSESSIONID=1F1734BD64C50DC0708CF2467507A555%3A%2FUAE_MAIN_APP"/>
14:</block>
15:</form>
16:</vxml>
----------------------------------------------------------------------------------------------
so its normal if you are not getting the primary DB source in the logs since its not coming in good call as well.
let me know whether AEP 7.0 supports this feature or not (as per my previous post)
Regards,
Nilesh
|
|
[+]
Avaya Orchestration Designer
» DB Failover node in OD 7.0 is not working as expected. , 09/07/2015 03:58:43
» Go to message
|
|
Dear Team,
I want to highlight following things once again,
DB failover working scenario
1. if the production DB services are stopped then IVR application is communicating with failover DB.
2. through web browser as well we can validate the failover DB source
DB failover Not Working Scenario (for same application) 1. if the production DB is not in network (shut down) then IVR application is not communicating with failover DB (our issue)
2. at the same time if we manually validate through browser then we are able to validate the failover DB through validation option in application.
Regards,
Nilesh
+91-9920775766
|
|
[+]
Avaya Orchestration Designer/Dialog Designer (Archive - Oct 2013 and earlier)
» Outbound POM calls transferred when the first one was connected, 08/09/2012 10:05:07
» Go to message
|
|
Can I directly provide the CCXML or VXML application path to play the campaign....
|
|
[+]
Avaya Orchestration Designer/Dialog Designer (Archive - Oct 2013 and earlier)
» IVVR not working, 03/09/2012 04:58:59
» Go to message
|
|
I am using the sample IVVR application and deployed it on Tomcat server.
giving the URL in VXML application type and setting the parameters as per the documents.
the following errors I am getting.
Session ID: AAEPLAB-2012247130608-2
Dialog ID:
Session Type: CCXML
Session Source: Inbound Call
Media Server: mppsysmgr
Start Date/Time: Sep 3, 2012 6:36:08 PM IST
Duration: 4 seconds
Call Information:
Number of Calls: 1
Originating Number: sip:6004@orange.com
Destination Numbers: sip:4106@orange.com
Server Information:
Application Server:
ASR Server: N/A
TTS Server: N/A
Slot: 2
MRCP Session ID for ASR: N/A
MRCP Session ID for TTS: N/A
Application Details:
Application Name: IVVR
Start Page Name: http://10.1281.125:8080/AvayaIVVR
Customer ID: N/A
Exit Info #1: N/A
Exit Info #2: N/A
Exit Page:
Exit Reason: Application exited. [ERRORS]
Preferred Path: Yes
Topic: N/A
Performance Details:
First Prompt Latency: 170 milliseconds
Number of Utterances: 0
Number of Recognized Utterances: 0
VoiceXML Page Requests: 0
VoiceXML Page CacheHits: 0
Average Prompt Latency: 0
Average Confidence: 0
Number of Latencies < 1 Sec: 0
Number of Latencies Between 1 and < 2 Secs: 0
Number of Latencies Between 2 and < 3 Secs: 0
Number of Latencies Between 3 and < 4 Secs: 0
Number of Latencies >= 4 Secs: 0
Maximum Consecutive Recognition Errors: 0
Highest Page Loading Latency:
URL:
Time: 0 milliseconds
Lowest ASR Recognition:
URL:
Total Number of Utterances: 0
Number of Recognized Utterances: 0
Session Hierarchy:
AAEPLAB-2012247130608-2
AAEPLAB-2012247130608-2-1
Session Transcription: Export
Spoken Barge In Rate: 0.0%
Default ASR Confidence Level:
ASR Engine Type:
TTS Engine Type:
Number of User Inputs: 0
Number of Speech Inputs: 0
Number of DTMF Entries: 0
Expand URL
Start Time Duration Event Details
6:36:08 PM SessionStart
6:36:08 PM CallDetect Call Leg: 1
CalledURI: sip:4106@orange.com
CallingURI: sip:6004@orange.com
UUI:
session.connection.protocol.sip.from.uri: sip:6004@orange.com
session.connection.protocol.sip.requesturi: sip:4106@orange.com
session.connection.protocol.sip.to.uri: sip:4106@orange.com
6:36:08 PM CallAnswer Call Leg: 1
6:36:08 PM DialogStart DialogID: AAEPLAB-2012247130608-2-1
Connection: AAEPLAB-Voiceportal-1-2012247130608
6:36:08 PM CallSignal Call Leg: 1
session.connection.callprogress: first_prompt_start
6:36:12 PM DialogEnd DialogID: AAEPLAB-2012247130608-2-1
6:36:12 PM CallDisconnect Call Leg: 1
AudioCodec: G711MULAW
CallEndDetails: NearEndDisconnect : Application exited. [ERRORS]
CallEndType: NearEndDisconnect
CallMediaEncryptionActive: False
CallReasonCode: nearenddisconnect
FarVideoFmt:
NearVideoFmt:
RTPStats: 0, 0, 224, 0, 2, 216, 8
VideoBitRate:
VideoCodec:
VideoFrameRate:
VideoScreenSize:
session.connection.protocol.sip.respcode: 15004
|
|
[+]
AE Services: JTAPI (Archive - Oct 2013 and earlier)
» Caller Data, 12/09/2011 07:57:27
» Go to message
|
|
Hi This is Nilesh from Orange..
can you please share whic hIVR script you are using.
VXML or GUI through DD.
|
|
[+]
Avaya Orchestration Designer/Dialog Designer (Archive - Oct 2013 and earlier)
» badfetch flow files, 16/07/2011 01:15:28
» Go to message
|
|
Dear All,
I am using the VXML application while calling the java API 3rd , 4th time it is giving me the same error (PAVB_03335) badrfetch. I have not configure the web.xml also since I am using DD environment.
Please help me to resolve this issue.
Regards,
Nilesh
|
|
[+]
Avaya Orchestration Designer
» Cannot Transfer Within "vxml_error.vxml", 16/12/2013 04:40:59
» Go to message
|
|
Hi,
I am also having the same problem; to cross check the vxml file I have tested in application server and the same file is working there.
but when the same file I am putting in event handler then its going blank; call is not landing to agent.
Please confirm whether we have to add all the exception or any other way to transfer the call directly to agent.
Regards,
Nilesh
nilesh.pundkar@orange.com
Orange Business Services
|
|