Hi everyone,

We've installed a co-resident appserver, using InstallAppServer.sh script (single server AEP), but runtimeconfig was not deployed.
Is there any missing step which we need to do?

Thanks!

Customer needs to change the IP range, so is there any procedure to change the WAS IP address?

Hi Everyone, we have a customer with the error showed in the subject (and other ones).
Below te complete set of messages from AES Connector trace.log, when Tomcat starts. It's running on Windows Server 2012 R2.
Please, help us to know what happens. Thanks!!!!!

24/08/2021 16:04:09:932 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:18:319 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:26:698 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:33:855 DEBUG - CTIConnectorManager.ProviderMonitor: Exiting
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79419 is 1
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent 79419: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent:79419: got Call Observation Ended Event
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79419 is null MRCR: MRCC:
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79419
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79419
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79420 is 1
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent 79420: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:886 DEBUG - CTICallObserver.callChangedEvent:79420: got Call Observation Ended Event
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79420 is null MRCR: MRCC:
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79420
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79420
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 79430 is 1
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent 79430: Event: 0 is 103 for call Provider:can't obtain
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.callChangedEvent:79430: got Call Observation Ended Event
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:79430 is null MRCR: MRCC:
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:79430
24/08/2021 16:04:33:902 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:79430
24/08/2021 16:04:33:902 DEBUG - shutting down CTI-JTAPI Providers
24/08/2021 16:04:33:917 DEBUG - CTI-JTAPI Providers are shut down, CTI Connector is terminating
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent: got provider shutdown event:112
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent:aes1 is added to list of downed providers
24/08/2021 16:04:33:933 DEBUG - ProviderObserver.providerChangedEvent: JTAPI Provider is down
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.init: AES Connector Version is 07.23.08.03
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
24/08/2021 16:04:44:377 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
24/08/2021 16:04:44:392 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#SWLINK1#CSTA#AES1-ETH0
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
24/08/2021 16:04:44:924 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 0, give small delay
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 13
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
24/08/2021 16:04:45:033 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: requestPrivileges failure: com.avaya.jtapi.tsapi.TsapiPlatformException: ACS Error: 120)
24/08/2021 16:04:45:033 DEBUG - CTIConnectorManager.initProvider: Will retry with a non secure connection.
24/08/2021 16:04:45:677 DEBUG - CTICallObserver.CTICallObserver:added 79419 observer
24/08/2021 16:04:45:927 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:04:45:927 DEBUG - CTIConnectorManager.getProviderObserver: received provider in service event
24/08/2021 16:04:47:333 DEBUG - CTICallObserver.CTICallObserver:added 79420 observer
24/08/2021 16:04:47:427 DEBUG - CTICallObserver.CTICallObserver:added 79430 observer
24/08/2021 16:04:54:599 DEBUG - ProviderMonitor: Checking:aes1 for availability
24/08/2021 16:05:03:200 DEBUG - ProviderMonitor: Checking:aes1 for availability

Hi Team,

Were you able to see my question? I really need to provide an answer to our customer.

Thanks!!

How does it work the "Desired Value" for a skill based campaign, using EWT option?

I supposed that the campaign start dialing when the real EWT is lower than the "Desired Value", but I performed some tests and the campaign dials to the entire contact list.

So, i think I need to know how to use it.

Thanks a lot in advance!

Thanks a lot MikeMalcorINI! It is clear.
I'll put later a new post asking some more details for "Desired Value" for EWT Parameter.

Best regards,

I'm trying to setup a strategy using Call Pacing Type based on skill. It only shows inbound skills.
I have configured the Nailer application but I run the campaign but I'm not able to get Nailed. See attachment.

I'm not sure how should it work. The official documentation is not clear enough to me.

After upgrading to 3.1.3.2 we stop POM services, and when we check the status, each one of them show stopped but the overall status says: POM is partially running.
This situation does not allow to run the commad do_UpdatePOMCerts. See bellow.
Any idea?
Thanks a lot!!

[root@aaep-pom-01 bin]# service POM status
Checking POM <version POM.03.01.03.02.02.070> Status at Tue Dec 1 05:26:14 PST 2020
Checking individual components:
STATE=STOPPED
Agent Manager is stopped


STATE=STOPPED
Campaign Manager is stopped


STATE=STOPPED
Campaign Director is stopped


STATE=STOPPED
POM ActiveMQ is stopped


STATE=STOPPED
Rule Engine is stopped


STATE=STOPPED
Advance list Management is stopped


STATE=STOPPED
zookeeper is stopped

STATE=STOPPED
kafka is stopped



Overall Status: POM is partially running

[root@aaep-pom-01 bin]# ./do_UpdatePOMCerts
Validating environment .. Please stop POM service to continue !!
[root@aaep-pom-01 bin]#
[root@aaep-pom-01 bin]#

Thanks a lot massimo__croci,

I think ith quiete different here because we don't have the message:

java.io.FileNotFoundException: trustedcert.properties

So, we configured again the license server and it worked. The thing is to know how the licens server configuration was lost from OD.

Best regards!

Hi guys,

We have found the field "License URL" empty, in an OD Runtime Config. The Tomcat logs showed:

01-Jul-2020 23:43:11.121 INFO [http-nio-7080-exec-8] org.apache.tomcat.util.http.parser.Cookie.logInvalidHeader A cookie header was received [/PY_IVR_111; $Domain=10.101.20.148] that contained an invalid cookie. That cookie will be ignored.Note: further occurrences of this error will be logged at DEBUG level.
Current Retry Count : 1
***** Saw exception, tracing before report
com.avaya.sce.runtimecommon.SCERuntimeException: Invalid runtime license
at com.avaya.sce.runtimecommon.SCESession.throwRTException(SCESession.java:2601)
at com.avaya.sce.runtime.Entry.handleRequest(Entry.java:268)
at com.avaya.sce.runtime.AppDocument.processRequest(AppDocument.java:343)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:247)

After completed again that field with the correct URL the service was recovered OK.

Is there any way in which the field information had been be lost itself? Or, is there any way to look how or when that configuration was lost?

Thank you so much in advance!

Hi everyone,

We have OD IVR applications. The problem is that avrest-rt-07.20.09.04.jar library sends two invocations to the same service since it does not contain text/plain. It needs a seccond request with application/json.

Below part of logs:

02/01/2020 11:06:19:325 DEBUG - C94981DD32C12DCEBFFABF84A9C6587B:/AR_MESA_DESPACHO : Web Service Request -> https://wfm-ivr-middleware-wfm.osep01-apps.claro.amx/wfm/ivr/notification
02/01/2020 11:06:19:538 INFO - C94981DD32C12DCEBFFABF84A9C6587B:/AR_MESA_DESPACHO : Response had content type: text/plain. Retrying call with new type...
02/01/2020 11:06:19:754 DEBUG - C94981DD32C12DCEBFFABF84A9C6587B:/AR_MESA_DESPACHO : Storing [OK] to: returnValueFromWFM
02/01/2020 11:06:19:754 DEBUG - C94981DD32C12DCEBFFABF84A9C6587B:/AR_MESA_DESPACHO : Web Service Reply <- OK

Complete information at:

https://belltech-my.sharepoint.com/:f:/g/personal/sebastian_canete_belltech_la/ElHewXE4YclKrfBO99SUCc0BZW6bi29haOns32HqznNk-Q?e=09yoAe

Our customer requests a new library which contains text/plain or it send just a request.

I have the same problem. A common issue is related to the amount of applications in which axis2 has limitations.
The other issue is related to DB sync. A possible solution for this is to remove POM server and create it again, but it didn't work in my case.

Thank you so much MikeMalcorINI. I really appreciate your help!
So, as I have POM 3.1.0, I think the only option is to use $TODAY, and I could filter contacts which were attempted more than 1 day ago.
But we need to filter contacts which were attempted more than 40 minutes ago (it can be 1 hour if it supports just integers).

Do you know any other way to implement this condition in POM 3.1.0?

Best regards!

The following syntax works. I put just the number (10) but I dont know if they are 10 minutes, 10 seconds, 10 hours, etc.

$TODAY - 10

Thanks a lot MikeMalcorINI!
So, what about the rest (interval '40' min)? Is it OK?

The complete sentence will be something like this:

$NOW - interval '40' min


Maybe you know if there is some documment wich explain this.

Regards!