Hi,

I found that in AACC 7, the reasonCode type has been changed to "xs:string", where as in old version it is "ns1:openNetReason".
Hence, I would like to know what value should be assigned in AACC 7 for reasonCode?


Many thanks

Hi,

I would like to update this post with some new information.

I have removed the failover feature in the AAEP aesconnector application, which previously I suspect was the cause for receiving invalid events.

However, having only 1 AES connection the problem still occurs.

Below are the components versions:
AES version is 6.3 with Super Patch 3
aesconnect is version 07.01.08.04
Tomcat is 7.0.62

Please kindly shed some ideas on what could have caused the problem or provide me information on where to open case or post will be grateful!


Thanks!

Hi Michael,

Actually I was wondering whether this problem relates to our aesconnector is configured with 2 AES connections
1st is Primary whereas the 2nd is set as "failover".


Thanks

Hi Guys,

I am experiencing CTI problems in my AAEP aesconnector when integrated with AES 6.3.3. This happens after we upgraded AES to 6.3.3-sp3 and also upgraded the aesconnector on AAEP to 7.01.08.04.

I have attached the logs for further analysis.


Many thanks!

Hi,

I have a question regarding Avaya EMC 6.4.1. We have developed a DLL which transfer the call to a VDN number after EMC Desktop has established a call between 2 parties.

We found that the function GetCallByCallAppearance returns the "Alert" call state when the call is actually answered. The DLL was running fine in CCE 4 and we expected the call state to be "Connected". Note that, we have already recompile the code using EMC 6.4.1 SDK.

Could anybody provide some hints on this problem?


Below is the code where we check the call state:
m_pASXMLStation.GetCallByCallAppearance(1).CallState



Many thanks!

Hi,

I have a question regarding Avaya EMC 6.4.1. We have developed a DLL which transfer the call to a VDN number after EMC Desktop has established a call between 2 parties.

We found that the function GetCallByCallAppearance returns the "Alert" call state when the call is actually answered. The DLL was running fine in CCE 4 and we expected the call state to be "Connected".

Could anybody provide some hints on this problem?


Below is the code where we check the call state:
m_pASXMLStation.GetCallByCallAppearance(1).CallState



Many thanks!

Noted, thanks for the information!

Hi Ross,

Are there any documents for Avaya support that states the compatibility of VP 5 support MSSQL 2008?

Or do we just need to download the latest version of sqljdbc4.jar file and it will work as normal?


Thanks!

Hi,

Are they official document or statement mentioned if VP 5.0 Speech applications support MSSQL 2008?


Many thanks!

Hi,

I am calling from Experience Portal 7


Thanks!

Hi,

Just wandering if you have any findings or result with this problem, as I am currently experiencing too?



Thanks!

Hi,

I have further found information from Avaya Support page, but I don't really understand what my next action should be:


CAUSE
The Axis 1.4 uses Digest authentication to authenticate web
service client requests while Axis 2.0 uses Basic authentication. Customer need to
use Axis 2 to LaunchVXML. The request URL should be:

The URL format for invoking a method on a web service deployed under axis2 is of
the format:
https://EPM address/axis2/services/VPAppINtfService/LaunchVXML
Please do not use the same instance of the browser to access the web pages and for
invoking the web service method. The browser tries to pass the same user name and
password that was used for the web pages and this might result in a 403.

The Axis 1.4 is using Digest Authentication method, it requires client to produce a
response based on a nonce returned from server. The customer client did not
generate this response.

10.35.0.20 - - [28/Feb/2014:09:47:03 +0100] "POST /axis/services/AppIntfWS
HTTP/1.1" 401 954 "-" "Axis/1.4"
10.35.0.20 - - [28/Feb/2014:09:47:04 +0100] "POST /axis/services/AppIntfWS
HTTP/1.1" 401 954 "-" "Axis/1.4"
10.35.0.20 - - [28/Feb/2014:09:47:05 +0100] "POST /axis/services/AppIntfWS
HTTP/1.1" 401 954 "-" "Axis/1.4"
SOLUTION
Customer need to use Axis 2 to LaunchVXML. The request URL
should be:

The URL format for invoking a method on a web service deployed under axis2 is of
the format:
https://EPM address/axis2/services/VPAppINtfService/LaunchVXML
Please do not use the same instance of the browser to access the web pages and for
invoking the web service method. The browser tries to pass the same user name and
password that was used for the web pages and this might result in a 403.




Thanks!

Hi,

I have just updated my application from DD4 to OD7 (on EP 7) and I found that the Outbound application are having some problems.

I noticed that if 2 outbound calls are triggered at the sametime, the error "(401) Unauthorized" would occur; whereas on the other hand if only 1 outbound call is triggered at any one time there is no problem.

Hope someone could provide some hints on what's causing the problem.



Many thanks!

Hi Ross,

I found from the logs that the second call failed to make was due to no resource. I have checked EPMS settings and found that there was only 1 port configured, so I added a second port.

Now the issue is slightly different, the first call will ring and play "system experiencing technical difficulty". This time I get the second call to dial and ring, however once the "error prompt" has finished both calls are dropped.

I have attached the ccxml log for you to have a look.


Thanks a lot!

Hi Ross,

Thanks for the advice, I'll do that and probably upload the logs tomorrow.


Cheers!