Message |
[+]
Avaya Orchestration Designer
» IVR Tomcat catalina.out log error related to AAEP URL, 21/03/2024 06:34:37
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» Header details for REST API, 19/03/2024 09:30:43
» Go to message
|
|
Hi.
What Ref ID are you referring to ?
Here https://learn.microsoft.com/en-us/azure/frontdoor/front-door-diagnostics?pivots=front-door-standard-premium
it states
"Access logs, health probe logs, and WAF logs aren't enabled by default. To enable and store your diagnostic logs, see Configure Azure Front Door logs. Activity log entries are collected by default, and you can view them in the Azure portal.
Access log
Information about every request is logged into the access log. Each access log entry contains the information listed in the following table.
Property
TrackingReference
Description
The unique reference string that identifies a request served by Azure Front Door. The tracking reference is sent to the client and to the origin by using the X-Azure-Ref headers. Use the tracking reference when searching for a specific request in the access or WAF logs.
|
|
[+]
Avaya Orchestration Designer
» Not being able to connect to my MS SQL Server database, 15/03/2024 03:53:46
» Go to message
|
|
Hi.
In the general case, on the logs there should be the following exception
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host <name_host>, port <#_port> has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.
In your specific case <name_host> = localhost and <#_port> = 1434, so on the logs you should see
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the localhost, port 1434 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.
The settings on the OD seem fine, I'd say this is not an OD configuration problem. It could be any of the following reasons
- A misconfiguration at the server.
You stated the proper JDBC driver was installed into the OD's host and your MS SQL Server was properly configured to listen to the TCP/IP traffic on the port 1434.
Please double-check if all configurations at the server are fine and also the port 1434 is fine;
- A network problem.
Ex. the perimetric firewall is blocking the incoming connection), please check;
- The SQL Server is not running on the host/ is temporary down.
Please check;
- 'Named Pipes' and 'TCP/IP' in the MS SQL Server not enabled.
If you did not enable them, please follow the six steps below:
a) Open the 'SQL Server Configuration Manager' application.
b) In the left panel, go to 'SQL Server Network Configuration' -> 'Protocols for <name_of_the_instance>'
c) Right-click on both 'Named Pipes' then select 'Enable'.
d) Right-click on 'TCP/IP' then select 'Enable'. Don't forget to assign a static port number for the TCP connection.
e) Save and close the panel.
f) Test if it works.
|
|
[+]
Avaya Orchestration Designer
» AOD 7.10.12.02 Update, 05/03/2024 10:04:52
» Go to message
|
|
Ok, Thanks for clarification.
I'd say '07.10.12.02' refers to the release 7.1.0 build1202.
|
|
[+]
Avaya Orchestration Designer
» AOD 7.10.12.02 Update, 05/03/2024 09:53:24
» Go to message
|
|
Hi.
Sure '7.10.12.02' is an OD version ?
Per my knowledge, the OD 7.x reached out the update 7.2.3 then went Out_of_Support
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_orchestration_designer/releases/7_2/index.gsp#download-3
|
|
[+]
Avaya Orchestration Designer
» AVAAY OD Commit into Bit Bucket, 29/02/2024 05:10:21
» Go to message
|
|
I'm not aware of any document concerning OD and Bitbucket.
|
|
[+]
Avaya Orchestration Designer
» Integrate AVAYA to Dialog Flow CX - Issue, 21/02/2024 10:28:42
» Go to message
|
|
It seems the JSON was received but not recognized:
sys.no-input-default
I need to investigate if a similar behavior was faced before.
|
|
[+]
Avaya Orchestration Designer
» Integrate AVAYA to Dialog Flow CX - Issue, 21/02/2024 02:08:30
» Go to message
|
|
Hi.
Any error message on logs ? Any timeout ?
|
|
[+]
Avaya Orchestration Designer
» Unable to get predefined and custom attributes from POM connector in OD application, 17/02/2024 14:27:45
» Go to message
|
|
Hi.
What API are you using ?
|
|
[+]
Avaya Orchestration Designer
» Outbound Dialer: Do Not Call: ID, 02/02/2024 08:06:57
» Go to message
|
|
Hi Steve.
Unfortunately, it seems the answer is negative. Nothing useful on documentation, no tips from expert guys I asked for that.
I also created a specific thread on the POM forum: https://www.devconnectprogram.com/forums/posts/list/26661.page#p167923
Only idea I had is coming from the document 'Using POM 4.0.1' ( https://support.avaya.com/css/public/documents/101077333 ) but it is complicated and Devconnect never tested such a solution so not sure it can work.
On pages 416-417-418, this doc says it is possible to add a DNC data source list referring to a file (ex. csv file). The only limitation is You can import files having either ANSI or UTF-8 format (see the attached pictures).
A DNC data source as local file can be imported from the laptop or via FTP server and the requested value USER_CONTACT_ID is provided while importing the record in the POM database, maybe it is possible to write a script that automatically retrieves each USER_CONTACT_ID then adds them to the local file before importing as the DNC data source.
Feel free to contact the ACES team in Avaya (formerly APS team) for a customized solution (if it is possible) https://www.avaya.com/en/services/avaya-professional-services/.
Bear in mind this is not a service free of any charge (they will provide a quote).
|
|
[+]
Proactive Outreach Manager
» Add PIM_CONTACT.USER_CONTACT_ID to a DNC list, 02/02/2024 07:38:54
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» Outbound Dialer: Do Not Call: ID, 01/02/2024 11:24:35
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» Outbound Dialer: Do Not Call: ID, 01/02/2024 11:11:20
» Go to message
|
|
Ok, thanks for clarifying.
So you need to add the field (on the picture below) to the DNC of a campaign.
I don't remind this is possible, anyway let me investigate deeper for a final answer (I see this is compulsory basing on the link you provided).
|
|
[+]
Avaya Orchestration Designer
» Outbound Dialer: Do Not Call: ID, 29/01/2024 15:22:34
» Go to message
|
|
Hi Steve.
Might you clarify the 'dialed number's associated ID' ?
Do you mean the 'UCID (Unique Call IDentifier) ?
|
|
[+]
Avaya Orchestration Designer
» Unable to get predefined and custom attributes from POM connector in OD application, 29/01/2024 03:08:11
» Go to message
|
|
Hi .
- What API are you using ?
- Check if the contact information is loaded into outbound Agent (specifically with the "pomInfo:ContactNumber" 08299801614 in this case).
|
|