Web Client Install

[kepetersen]

I loaded the Web Client disk on the Avaya DL360 server that was delivered for this server type.
I paused for discovery if the customer wanted to load the East Asian prompts then looking back the server was rebooting.
It shows the Avaya MM Web Client in the Control Panel under Add/Remove Programs. I see under Start>Programs>Avaya Modular Messaging Web Client Tools with Connectivity Test, Install Verify Test - Ivy, MMLogViewer, Reset Web Server,
Start Web Server and Stop Web Server. I also see the Avaya Modular Messaging menus of About Avaya Modular Messaging, Dialogic Line Tester, Languages, Operational History Viewer, Port Monitor, Reporting Tool.

The connectivity test shows a green square with Web Server, IIS - Pass and Generic - 7B293C1 connected to a square of DNS and a square with a phone in it.

In the Services screen the following services are started and set to Automatic: Avaya Modular Messaging Web Client Daemon, IIS Admin Service, MMPhoneService. What other services run the MM Web Client?

The Web Client disk loaded the 5.0 version and it is at base build 9.0.203.0. I have the server connected, in my office, to a dummy hub. The customer site is in another state where the 5.2 MSS storage system on SP11 resides. What is needed to get this server at this same level?

The installation guide is pretty sparse. Where in the install do you define the name and IP of the Web Client server?

 

[KenMeans]

First off if you have any of the MM services set to auto disable them. You do need the MMPhoneservice and the webclient daemon as well as the IIS running.

The name of the Webclient is the name of the FQDN of the server and the IP is what you assign to the NIC. To config the webclient so it can point to the right MSS you need to bring up the IP of the server /webmsg/admin so you can config it.

Then the end user will point thier broswer to the server name /webmsg or the customer can put a redirect from a name that they would like to use MMWEB = IP/webmsg.


to get it up to the 5.2 just use the following. Its the same application if you were upgrade a 5.0 MAS but the screen will show that it is a WEB Client server and it takes like 4 nano seconds to do. But it take 30 minutes to unpack the dam thing.

Upgrading Web Client server software from Release 5.0 or
Release 5.1 to Release 5.2
If you are upgrading from Release 5.0 or Release 5.1 to Release 5.2, use the Modular
Messaging 5.2 Upgrade application. For more information about how to use the Modular
Messaging 5.2 Upgrade application for upgrading your Modular Messaging software, see the
Modular Messaging 5.2 Upgrade application online help.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)