Eric,
you are aware of of the recent license fix you did along with Glenn Boxell. Thx.

We are running DD5.1 under tomcat under solaris m/c with MPS3.5. I got our first very simple application to work yesterday once the license issue was resolved.

Just for further testing, I deployed the same application under another solaris m/c running tomcat and got the following error:
7139 Apr 29 14:32:55.71|526|47|8002|com.nortelnetworks.vxi|VXI::PushExecutionContext - platform defaults initialized
7140 Apr 29 14:32:55.71|526|47|8002|com.nortelnetworks.vxi|VXI::RunDocumentLoop - loading initial document.
7141 Apr 29 14:32:55.71|526|47|8002|com.nortelnetworks.vxi|VXI::PerformTransition(https://10.170.52.197:8282/PoundTec/Start)
7142 Apr 29 14:32:55.71|526|47|8002|com.nortelnetworks.vxi|DocumentParser::FetchDocument(https://10.170.52.197:8282/PoundTec/Start)
7143 Apr 29 14:32:55.78|526|47|8002|com.nortelnetworks.vxi|DocumentParser::FetchBuffer(https://10.170.52.197:8282/PoundTec/Start, { (inet.urlEncod
ing, UTF-8) })
7144 Apr 29 14:33:15.82|526|47||com.nortelnetworks.SBinet|700||Func=SSL_write|SSL_get_error=1
7145 Apr 29 14:33:15.82|526|47||com.nortelnetworks.SBinet|217||URL=https://10.170.52.197:8282/PoundTec/Start
7146 Apr 29 14:33:15.82|526|47|8000|com.nortelnetworks.vxi|DocumentParser::FetchBuffer - could not retrieve absolute path of document at URL: http
s://10.170.52.197:8282/PoundTec/Start
7147 Apr 29 14:33:15.82|526|47|8000|com.nortelnetworks.vxi|DocumentParser::FetchDocument - exiting with error result 2
7148 Apr 29 14:33:15.82|526|47||com.nortelnetworks.vxi|203||URL=https://10.170.52.197:8282/PoundTec/Start
7149 Apr 29 14:33:15.82|526|47|8002|com.nortelnetworks.vxi|VXI::DoEvent(error.badfetch)

It could not fetch the first page. Could you give some guidance on where I should look. Both tomcat are 6x versions. The above trace says SSL-get_error=1. Please help.

Thanks
Deepak

The vxml browser on MPS can not seem to load the start page of the DD app using this URL https://10.170.52.197:8282/PoundTec/Start. You have to configure from the MPS side first. It could be the network issue. Does http (no SSL) work instead of https?

Wilson,

I have MPS installed on m/c A and the dialog designer application installed on m/cs DDA and DDB.

From A to DDA: using https works but not http

From A to DDB: using http works but not https

I can't understand the rational. Any comments.
Deepak

http should work automatically once you install Tomcat. Did you disable it on purpose?

There are different people who installed the tomcat on these m/cs. If you tell me where you can enable or disable http , I can check it out in tomcat.

Deepak

Thanks for the clue.

on one m/c, the tomcat in on port 8443 which has SSL security enabled and on the other tomcat installation, it is port 8282 where https is not enabled, so http works.

Deepak

All the configuration is in the config/server.xml file.

Hello Team,

Till date i have received good support from you guys and was able to integrate MPS Peripro app to AOD app.

Everything was fine till we implemented ssl. Below is complete details.

Issue : Communicating on SSL from MPS to AOD application on IBM WAS.

Setup: We have MPS500 with mps3.5. IBM WAS 7.

Detail: When we call the WAS application from MPS app everything is fine if the URl in peri app is defined as http://x.x.x.x:1234/IVR_test/Start.

When we use https:/x.x.x.x:1221/IVR_test/Start then we can reach to some extent in depth of application. I mean we can hear welcome..then take other inputs and proceed to certain menus as well.

But then it stops to go further.

We have installed the WAS certs on MPS and MPS certs on WAS. Made changesin OSBclient.cfg for SSL.
but those seems to be meaningless because when in file OSBclient.cfg i keep ssl flag to 1 and dont give the cert path and hash path, the behaviour is same.

What's strange is if we are able to reach start of the application and navigate through some menus that means SSL is through. But why it stucks after that. When we change back to URL on mps app to http everything works again.

We get the error as SSL write failed.


Any suggestions and help would be highly appreciated.


Thanks...!!!

Amit chirgania
amit.chirgania@gmail.com

Most likely the issue is from the MPS side (not the applicaiton). You would need to contact Avaya support on this one. They would need to take a look at the MPS logs to see what is going on when calling into the app on SSL.