We are using AOD 7.2 & JDBC driver sqljdbc42.jar..

We are trying to connect to database through AOD 7.2 which expect protocol TSLv1.2.

We get following error
The driver could not establish a secured connection to SQL server by using secured socket layer (SSL) encryption. Error: "The server
selected protocol version TSL10 is not accepted by client preferences [TLS12]".

We have tried setting ;sslProtocol=TSLv1.2 in connection string, but still get same error. Looks like AOD is using TSL10. How do we setup AOD to use TSL1.2?

We have already tried adding Accept in header and still get same error.

We have a REST API with GET request which expects Content-Type in header with value as 'application/json'. We have required setup on AOD and when we test we get error "415 Error: Unsupported Media Type".

As per backend team, Server is receiving the content-type as "application/x-www-form-urlencoded; charset=UTF-8".

We are not sure where Content-Type is getting changed even though e set it to 'application/json'.

NOTE: Request works fine if tested from SOAPUI. We see issue only when called from AOD.

Can we know what could be issue and how it can be resolved? How do we make sure AOD sends Content-Type as 'application/json'?

After going through different post on setting UUI realised we need to have 04 followed with HEX(data). Also tried using Prepare UUI operation to arrive at UUI.

This is on AEP 7, AOD 7, Tomcat7.

We are unable to pass UUI in right format to CM when UUI mode is set to service provider.

We have 2 application where UUI is getting passed. It works fine on one application and fails in other. Both are configured for service provider mode.

1 working: We have CCXML outbound application where UUI is set directly with customer phone number while createcall in CCXML application. This is sending UUI data as required and we see AES having userinfo type as UUIInAscii.

2 not working: We have AOD application where we need to set customer phone number as UUI. We tried setting UUI with C8,HEX(data), CM receives it in right format but on AES its passing userinfo type as UUIUserSpecific.

Is there different format we need to use for service provider? We also tried 'PD,00;C8,HEX(data)' and also 'PD,04;C8,HEX(data)'

Is there anything in AOD application which lets MPP know that UUI need to be in ASCII. Is there something wrong we are doing here?

Certificates are installed locally and application was working fine when authentication on server end was disabled. Now client has installed certificates on server end and now we have issue.

Is this issue with local certificate authentication or from server end?

We get error when we try to execute WS. Can we know what could be issue...

Transport error: 403 Error: Client Certificate missing or invalid.


1/10/2018 15:15:22:300 INFO - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Calling method [{http://trizetto.com/fxi/isl/FaWsvcInpSearchMember_v3}SearchMember_v3_SubscriberId] on web service [WebSvcSearchMember_v3] at [https://hznfxitest.tzghosting.net/FacetsWebServiceLibrary/FaWsvcInpSearchMember_v3.asmx]
31/10/2018 15:15:22:300 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Collecting [connectivity.ws.beans.service1.WebSvcSearchMember_v3Stub$Config@1115f81] from:pConfig
31/10/2018 15:15:22:300 INFO - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Signing soap message using keystore at C:\Program Files (x86)\Java\jdk1.7.0_05\jre\lib\security\cacerts.jks, alias: 1, provider: SUN, and a password with a length of 7
31/10/2018 15:15:22:347 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Web Service Request -> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="Signature-7">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
<ds:Reference URI="#id-8">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>THgnvujbzHOW+pfgZZ2lYCyn/LE=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
oZRrEDH/LAKGxCFwF1Im0UDwWPqoz28++sLMp0BRQwjaRtb2fHpY9oHBSETMuDMWI1CgPAZzR9WU
QJF+u4nRQlEhGmv99WK51X7J6ZlhAFPJ0gtAk/CJQ6iUSxcQeh6Vcimxcw1a90o8gXWYgz5gqWuy
YEfODfXCOJnzk13qNggPeIF2n6tEaBvdQkeXWmozFQjeZG2OT40IvsjCMyZvZVjnQjAav8e8RX7l
BSg+WihLHwLzD0DbDBEPcPxrSlhxLsCwM/BfDEm+R675Effo5y4ekKCQX6S3f14eJe4I5/TyYKXP
Q6ERdrl/YluAF4nqIrEzopbS4qN+hPP8xt3J5w==
</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-84D87974C25FFB3262154101332231611">
<wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-84D87974C25FFB3262154101332231612"><ds:X509Data>
<ds:X509IssuerSerial>
<ds:X509IssuerName>CN=Network Solutions DV Server CA 2,O=Network Solutions L.L.C.,L=Herndon,ST=VA,C=US</ds:X509IssuerName>
<ds:X509SerialNumber>72625881272025579392681492028232541315</ds:X509SerialNumber>
</ds:X509IssuerSerial>
</ds:X509Data></wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature></wsse:Security></soapenv:Header><soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-8"><ns1:SearchMember_v3_SubscriberId xmlns:ns1="http://trizetto.com/fxi/isl/FaWsvcInpSearchMember_v3"><ns1:pConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:Config"><ns1:FacetsIdentity>ResultsTel</ns1:FacetsIdentity><ns1:CallingSystemName>IVR_ResultsTel</ns1:CallingSystemName><ns1:CallingSystemUserId>TRC1</ns1:CallingSystemUserId><ns1:CallingSystemUserName>ResultsCompanies</ns1:CallingSystemUserName><ns1:CallingSystemTransactionId>907I0000XAP1</ns1:CallingSystemTransactionId></ns1:pConfig><ns1:pSBSB_ID>40001221</ns1:pSBSB_ID></ns1:SearchMember_v3_SubscriberId></soapenv:Body></soapenv:Envelope>
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Axis Fault message <- Transport error: 403 Error: Client Certificate missing or invalid.
31/10/2018 15:15:22:566 ERROR - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Got AxisFault during web service call: Transport error: 403 Error: Client Certificate missing or invalid.
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Fault action <- null
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Fault node <- null
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Fault role <- null
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Fault type <- 0
31/10/2018 15:15:22:566 DEBUG - 6A1BCDF9E146EB6BEAC17A365EF5BF63:/HORIZON_MEM_509 : Fault message <- Transport error: 403 Error: Client Certificate missing or invalid.

Does AOD supports X.509 cert on Axis1? If so how can be accomplish the same?

We have application build on AOD7.2. Even after enabling trace logging we are not seeing trace file getting updated. When we call we see just report log file with call details, trace file is always 0 bytes.

This happens to only 1 application. Other applications are creating both trace & report logs..

Any idea what could be issue.

Tried both and still get same error...

Using \\

29/08/2018 09:08:04:232 INFO - BD4F3CC1FCDCEC4A851AD26C587F6657:/HORIZON_MEM_509 : Calling method [{http://trizetto.com/fxi/isl/FaWsvcInpSearchMember_v3}SearchMember_v3_SubscriberId] on web service [WebSvcSearchMember_v3] at [https://hznfxitest.tzghosting.net/FacetsWebServiceLibrary/FaWsvcInpSearchMember_v3.asmx]
29/08/2018 09:08:04:263 DEBUG - BD4F3CC1FCDCEC4A851AD26C587F6657:/HORIZON_MEM_509 : Collecting [connectivity.ws.beans.service1.WebSvcSearchMember_v3Stub$Config@b3b817] from:pConfig
29/08/2018 09:08:04:263 INFO - BD4F3CC1FCDCEC4A851AD26C587F6657:/HORIZON_MEM_509 : Signing soap message using keystore at C:\\Program Files (x86)\\Java\\jdk1.7.0_05\\jre\\lib\\security\\cacerts.jks, alias: devfxifhg, provider: Network Solutions DV Server CA 2, and a password with a length of 8
29/08/2018 09:08:04:544 ERROR - BD4F3CC1FCDCEC4A851AD26C587F6657:/HORIZON_MEM_509 : Failed opening key store for signing soap message: Failed to load credentials.
29/08/2018 09:08:04:544 ERROR - BD4F3CC1FCDCEC4A851AD26C587F6657:/HORIZON_MEM_509 : Failed signing envelope: Failed to load credentials.


Using /

29/08/2018 08:57:02:606 INFO - B7792EDBBF42A0102E1BEA00C045BEBD:/HORIZON_MEM_509 : Calling method [{http://trizetto.com/fxi/isl/FaWsvcInpSearchMember_v3}SearchMember_v3_SSN] on web service [WebSvcSearchMember_v3] at [https://hznfxitest.tzghosting.net/FacetsWebServiceLibrary/FaWsvcInpSearchMember_v3.asmx]
29/08/2018 08:57:02:637 DEBUG - B7792EDBBF42A0102E1BEA00C045BEBD:/HORIZON_MEM_509 : Collecting [connectivity.ws.beans.service1.WebSvcSearchMember_v3Stub$Config@12617ef] from:pConfig
29/08/2018 08:57:02:637 INFO - B7792EDBBF42A0102E1BEA00C045BEBD:/HORIZON_MEM_509 : Signing soap message using keystore at C:/Program Files (x86)/Java/jdk1.7.0_05/jre/lib/security/cacerts.jks, alias: devfxifhg, provider: Network Solutions DV Server CA 2, and a password with a length of 8
29/08/2018 08:57:02:637 ERROR - B7792EDBBF42A0102E1BEA00C045BEBD:/HORIZON_MEM_509 : Failed opening key store for signing soap message: Failed to load credentials.
29/08/2018 08:57:02:637 ERROR - B7792EDBBF42A0102E1BEA00C045BEBD:/HORIZON_MEM_509 : Failed signing envelope: Failed to load credentials.

Does it mean we need to copy trusted_weblm_certs.jks with different name and try using it?

We have application built using AOD7. WS are configured with X509 soap message signaling.

Certificates are installed through runtime config and same details has been provided in WSOP in AOD application.

Please find attached screenshot of cert installed. We use default password "password". When we call WS we get following error. Any idea what could be issue?


/08/2018 04:47:10:890 INFO - 8DAFD55480EF6D2968B3A8CA6E50B5F8:/HOZON_MEM : Signing soap message using keystore at C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\lib\trusted_weblm_certs.jks, alias: devfxifhg, provider: Network Solutions DV Server CA 2, and a password with a length of 8
23/08/2018 04:47:11:187 ERROR - 8DAFD55480EF6D2968B3A8CA6E50B5F8:/HOZON_MEM : Failed opening key store for signing soap message: Failed to load credentials.
23/08/2018 04:47:11:187 ERROR - 8DAFD55480EF6D2968B3A8CA6E50B5F8:/HOZON_MEM : Failed signing envelope: Failed to load credentials.

We have CCXML outcall application deployed on AEP6 which has H323. We use MakePartyToPartyCall to place call in agent queue. We are passing parameter to set ANI to be displayed but its never shown on agent screen. Agent always sees IVR port# instead of value set by us. Same logic works fine on SIP setup.

Is there a way to set UUI using MakePartyToPartyCall function? Can we have documentation related to MakePartyToPartyCall?

Is there a way to set UUI in CCXML application on H323 setup?

We are trying to install AOD6 on Windows 64-bit 2012 system.

We installed Java, Tomcat6, Eclipse, MSSpeech which are part of installation files.

But tomcat didn't start as it expected Java 64-bit version.

So, we uninstalled Java & installed Java 64-bit. Now we were able to start Tomcat but eclipse started complaining about missing JRE files. So, we ended up installing both 64 & 32 bit version of Java.

Now we are able to start tomcat as well as eclipse. But when we start eclipse we don't see Tomcat in Windows-Preferences.

Are we supposed to install something to have Tomcat included in eclipse->windows->preference.

Please let us know is we have missed anything during installation process.

Our client has multiple versions of AVP like AVP3, AVP5, AVP6 & AEP7. Can we have single application server which can work for all AVP's? If so what should be version of AOD to be used and what should be version of Java & Tomcat?