Message |
[+]
Avaya Orchestration Designer
» Phrase Missing Call disconnect, 13/10/2020 23:58:26
» Go to message
|
|
Hi ,
we have an OD application using runtime of scert-07.00.18.01 and when the phrase URL is wrong or the phrase is missing the call is getting disconnected abruptly by voicing out the technical error message. we have handled exception error.runtime in Approot. is there any way for such scenarios call would continue instead of call is getting disconnected.
|
|
[+]
Avaya Orchestration Designer
» JWS tomcat Unable to connect WEB LM Server, 28/08/2020 03:15:53
» Go to message
|
|
also i have the below error report.log the problem is looks like to do java supported TLS protocols. we are using latest version of JRE 1.8.0_262 and the HTTPS us not working looks like towards the weblm and application
28/08/2020 15:27:30:408 WARN - In Progress | channel:unknown | ITSC:Start | null | Runtime License Error :com.avaya.weblm.LicenseException: Problem with connection to server: java.security.cert.CertificateException: Certificates do not conform to algorithm constraints | null | null |
|
|
[+]
Avaya Orchestration Designer
» JWS tomcat Unable to connect WEB LM Server, 28/08/2020 03:12:39
» Go to message
|
|
we tried with the JBoss and tomcat 9 since this is JWS tomcat not the JBoss application server. both the runtimeconfig wars are having below issue with the web.xml
Element type "http-only" must be declared.
org.xml.sax.SAXParseException; systemId: file:/jboss/tomcat/jws5/instances/DEV_GO2GFIVR_GG_01/webapps/runtimeconfig/WEB-INF/web.xml; lineNumber: 40; columnNumber: 17; Element type "http-only" must be declared.
org.xml.sax.SAXParseException; systemId: file:/jboss/tomcat/jws5/instances/DEV_GO2GFIVR_GG_01/webapps/runtimeconfig/WEB-INF/web.xml; lineNumber: 42; columnNumber: 19; The content of element type "session-config" must match "(session-timeout)?".
org.xml.sax.SAXParseException; systemId: file:/jboss/tomcat/jws5/instances/DEV_GO2GFIVR_GG_01/webapps/runtimeconfig/WEB-INF/web.xml; lineNumber: 39; columnNumber: 19; Element type "cookie-config" must be declared.
and unable to bring up the runtimeconfig application itself.
|
|
[+]
Avaya Orchestration Designer
» JWS tomcat Unable to connect WEB LM Server, 27/08/2020 12:09:40
» Go to message
|
|
HI Team,
we are using linux 8 with JWS tomcat 5 where we deployed runtimeconfig and application war files and we see that the runtime config is unable to reach the webLM server.
in the catalina.out file i can see the below error not sure what's the impact of this and we kept all the runtime jar files in jws/lib folder whatever generated by OD. is that good or any custom steps required for JWS tomcat.
28-Aug-2020 00:38:21.268 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 2466 ms
INFO: Using path [/jboss/tomcat/jws5/instances/DEV_GO2GFIVR_GG_01/lib/ddconfig.xml] to configuration file
INFO: No runtimeconfigextensions.xml file found, skipping.
Warning, stored hash did not match computed hash, Config file may have been tampered with, please verify your configuration
OD CALL THIS======VPAppLogClientBase.setEPMWebSErviceClient() is calling...
VPAppLogClientBase:setEPMWebServicesClient: setting epmWebSErvicesClientBase instance first time
VPAppLogClientBase:getAxis2PrimaryUrl: axis2 vpms primary url: null
VPAppLogClientBase:constructor initialize log4j properties
VPAppLogClientBase:getLogFilePath - /jboss/tomcat/jws5/instances//webapps/go2gfivr//../../logs
VPAppLogClient:initLog4j: log4j log file path: /jboss/tomcat/jws5/instances//webapps/go2gfivr//../../logs
log4j:ERROR A "org.apache.log4j.RollingFileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
log4j:ERROR [java.net.URLClassLoader@6477463f] whereas object of type
log4j:ERROR "org.apache.log4j.RollingFileAppender" was loaded by [ParallelWebappClassLoader
context: go2gfivr
delegate: false
----------> Parent Classloader:
java.net.URLClassLoader@6477463f
].
log4j:ERROR Could not instantiate appender named "VPAppLogClient".
log4j:WARN No appenders could be found for logger (com.avaya.vp.applog.client).
log4j:WARN Please initialize the log4j system properly.
getClassPath():cpath: /jboss/tomcat/jws5/instances//lib/VPAppLogClient_7.1.0.jar
getClassPath():decodePath: /jboss/tomcat/jws5/instances//lib/VPAppLogClient_7.1.0.jar
getClassPath():location: file:/jboss/tomcat/jws5/instances//lib/VPAppLogClient_7.1.0.jar
getClassPath():logpath2: /jboss/tomcat/jws5/instances//lib
VPAppLogClientBase:getClassPath - return path: /jboss/tomcat/jws5/instances//lib
Current Retry Count : 1
|
|
[+]
Web Services
» Endpoint Password Change, 18/07/2019 02:40:27
» Go to message
|
|
hi,
myserver is actually having valid IP which i masked it. regarding the 403 error am trying the simillar request using soap UI and it says 403 it means mostly access forbidden however am using the default admin account which is the highest in terms of access.
<body>
<font style="font-size:9pt; font-family:arial,sans-serifclass">
<font style="font-size:9pt; font-family:arial,sans-serif; font-weight:bold; color:#CC0000">
You have been denied access to the requested resource.
</font>
<br>
<br>
This may be because:
<br>
<ul>
<li>You do not have a valid Single Sign-On ID in your request, or</li>
<li>The account you used to log in is not granted the privileges to access the requested resource.</li>
</ul>
Click the following link to go back to the main navigation page. You may be asked to log in again.
<br>
<br>
|
|
[+]
Web Services
» Endpoint Password Change, 16/07/2019 00:08:57
» Go to message
|
|
Endpoint Password Change is not working when we invoke the SMGR API. can you please help to check. we are using the sample application provided as part of the SDK. we are using admin account details of SMGR to change the password for the extension.
the error says very limited information. please let us know anyway we can enable the logging.
com.sun.jersey.api.client.UniformInterfaceException: PUT https://myserver/NavigationManagerServlet?action=error403 returned a response status of 405
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:565)
at com.sun.jersey.api.client.WebResource.put(WebResource.java:198)
at com.avaya.mgmt.smgr.webservice.client.WebServiceClient.passwordChange(WebServiceClient.java:270)
at com.avaya.mgmt.smgr.webservice.client.WebServiceClient.passwordChange(WebServiceClient.java:241)
at com.avaya.mgmt.smgr.webservice.jaxb.impl.CMPasswordChangeProcess.processOepration(CMPasswordChangeProcess.java:16)
at com.avaya.mgmt.smgr.webservice.jaxb.impl.AbstractProcess.process(AbstractProcess.java:108)
at com.avaya.mgmt.smgr.webservice.jaxb.client.UserMgmtClient.process(UserMgmtClient.java:29)
at com.avaya.mgmt.smgr.webservice.jaxb.client.UserMgmtClient.main(UserMgmtClient.java:71)
|
|
[+]
Web Services
» List users in CM, 17/04/2019 20:44:29
» Go to message
|
|
hi,
Yes agree we can't do using SMS web service. how about SMGR web services if the CM is synch with SM.
|
|
[+]
Web Services
» List users in CM, 08/04/2019 20:33:00
» Go to message
|
|
is there any chance to get the login users list from CMS using SM web servcies?
|
|
[+]
Web Services
» List users in CM, 07/04/2019 22:59:50
» Go to message
|
|
hi,
is there any way to list CM login users by using the SMS web service api. i have seen Logins model as per the documentation not sure it gives the login users of that speific time or all the logins applicable.
|
|
[+]
JTAPI
» ACD Address, 20/03/2019 21:45:24
» Go to message
|
|
Hi Martin,
you mean these errors are related to the environment nothing to do with the API?
|
|
[+]
JTAPI
» ACD Address, 19/03/2019 21:04:01
» Go to message
|
|
Hi Martin,
can you please also clarify why am receiving this errors frequently and how to avoid the same.
2019-03-19 10:41:08,204 | [Thread-64] | ERROR | CSTA Error: 12
com.avaya.jtapi.tsapi.TsapiPlatformException: CSTA Error: 12
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:100)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:539)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:448)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.snapshotDevice(Tsapi.java:1421)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.doCallSnapshot(TSDevice.java:2891)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2688)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2561)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:446)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addAddressListener(TsapiAddress.java:1105)
2019-03-19 10:41:07,865 | [Thread-64] | ERROR | CSTA Error: 41
com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 41
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:95)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:539)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:448)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDoNotDisturb(Tsapi.java:1238)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.doAddressSnapshot(TSDevice.java:2821)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2687)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2561)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:446)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addAddressListener(TsapiAddress.java:1105)
|
|
[+]
JTAPI
» ACD Address, 18/03/2019 21:46:29
» Go to message
|
|
hi, am receiving the below error when am trying to monitor the ACD Address or hunt group. even if the error is there am able to receive the events for the below two methods on login and logout. any idea why we have this error. and also found that this method is not given any event when agent goes to different AUX .
working fine: acdAddressLoggedOff and acdAddressLoggedOff,
not working: acdAddressBusy, acdAddressWorkNotReady,
2019-03-19 10:41:08,204 | [Thread-64] | ERROR | CSTA Error: 12
com.avaya.jtapi.tsapi.TsapiPlatformException: CSTA Error: 12
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:100)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:539)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:448)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.snapshotDevice(Tsapi.java:1421)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.doCallSnapshot(TSDevice.java:2891)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2688)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2561)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:446)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addAddressListener(TsapiAddress.java:1105)
2019-03-19 10:41:07,865 | [Thread-64] | ERROR | CSTA Error: 41
com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 41
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:95)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:539)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:448)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDoNotDisturb(Tsapi.java:1238)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.doAddressSnapshot(TSDevice.java:2821)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2687)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2561)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:446)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addAddressListener(TsapiAddress.java:1105)
|
|
[+]
JTAPI
» Extension Login- JTAPI, 14/03/2019 21:17:02
» Go to message
|
|
is there any API in JTAPI to force the user to login in extension (Hard Phone).
|
|
[+]
JTAPI
» Extension Login- JTAPI, 14/03/2019 02:58:02
» Go to message
|
|
Using JTAPI before the Agent login is there any way we can enforce the extension login.
|
|
[+]
JTAPI
» aux reason code of each agent, 27/02/2019 21:32:35
» Go to message
|
|
|
|