Docstoc

MWI 2007

Document Sample
MWI 2007 Powered By Docstoc
					MWI 2007
Deployment Guide for version 3.0

      www.geomant.com
Document date: October 21, 2011
                                                         Table of Contents

OVERVIEW ................................................................................................................................................. 4
    Summary ................................................................................................................................................ 4
    Technical Components ..................................................................................................................... 5
    References ............................................................................................................................................. 6

AUTOMATIC INSTALLATION ............................................................................................................... 8
    Installation prerequisites .................................................................................................................. 8
        Software Prerequisites.................................................................................................................. 8
        Hardware prerequisites .............................................................................................................. 10
    MWI Service installation ................................................................................................................. 11
    Web Interface installation.............................................................................................................. 13
    IIS v6 ...................................................................................................................................................... 14
    IIS v7 ...................................................................................................................................................... 16
        Specific installation steps for Windows Server 2008 ....................................................... 19

MANUAL INSTALLATION .................................................................................................................. 22
    Web Interface installation.............................................................................................................. 22
    Service installation ........................................................................................................................... 23

INTEGRATION WITH LYNC ............................................................................................................... 35
    Certificate request ............................................................................................................................ 35

WEB BASED CONFIGURATION ........................................................................................................ 41
    Web-based administration ........................................................................................................... 41

IP GATEWAY CONFIGURATION ...................................................................................................... 47
    Tested IP gateways........................................................................................................................... 47
        Intel NetStructure PIMG80PB .................................................................................................. 49
        MWI though SMDI ....................................................................................................................... 49
        MWI though in-band DTMF ..................................................................................................... 49
        AudioCodes Mediant 2000 ....................................................................................................... 50


2/74                                                                                    SERVICE DEPLOYMENT GUIDE
        MWI though SMDI ....................................................................................................................... 51
        MWI though in-band DTMF ..................................................................................................... 51
        Cisco CallManager 5.0 ................................................................................................................ 51

SMS GATEWAY CONFIGURATION ................................................................................................. 52
    Mobiline Email/SMS gateway ...................................................................................................... 52

MULTIPLE MWI SERVICE INSTANCES ........................................................................................... 53

TROUBLESHOOTING ........................................................................................................................... 55
        Failed to access web admin pages ........................................................................................ 55
        Event subscription failure .......................................................................................................... 55
        Failed to retrieve IP gateways .................................................................................................. 56
        Failed to retrieve UM users ...................................................................................................... 56
        Mailbox access error ................................................................................................................... 57
        Message received from gateway: 504 DNS Timeout ...................................................... 58
        “General Access Denied” Error ................................................................................................ 58
        Failed to monitor the CPU Usage at this moment ........................................................... 58
        (Failed to monitor the Page File at this moment) ............................................................ 58
        No service logs.............................................................................................................................. 58
        No web application logs............................................................................................................ 59
        Failed to connect to the MWI service ................................................................................... 59
        Failed to initialize HTTP listener object ................................................................................ 59
        Web form is disabled .................................................................................................................. 61

SCALABILITY ........................................................................................................................................... 62
    Memory requirement ...................................................................................................................... 62
    CPU requirement .............................................................................................................................. 62
    Gateway port requirement ............................................................................................................ 62
    Average synch time ......................................................................................................................... 64

FREQUENTLY ASKED QUESTIONS .................................................................................................. 66

CHECK LIST ............................................................................................................................................. 73


3/74                                                                               SERVICE DEPLOYMENT GUIDE
ABBREVIATIONS ................................................................................................................................... 74


OVERVIEW

The subject of this document is an application which can be used in order to
extend the Microsoft UM solution with MWI service. The primary purpose of
the MWI application is to synchronize the user’s voice-mailbox content and
the lamp state on the user’s physical phone. More precisely, if the number of unread
voicemail messages in the Exchange 2007 mailbox is greater than zero, the lamp will be lit.



Summary
Figure I. shows the basic processes of MWI2007 application. The application receives
information about UM enabled users from Active Directory by predefined searching criteria,
and then subscribes them for the service. When user receives voicemail (or other type of
message defined by administrator) Exchange server sends notification to the MWI service. In
addition, MWI also requests OCS 2007 for the user’s presence. Then the service sends SIP
message to PBX or gateway, which lights up MWI lamp on the user’s phone. At the same
time MWI2007 sends notification message to the SMS Server, which forwards it to SMS
Provider. User gets SMS message about unread Voice mail or missed event.




                                                         Figure I. MWI 2007


4/74                                                                           SERVICE DEPLOYMENT GUIDE
Technical Components

The figure below shows the processes of MWI2007 followed by step-by-step explanations.




                  Figure II. Technical components of the MWI service

   1. MWI service requests UM enabled users from AD for subscribing (later, the user
      search criteria can be defined by administrator in the MWI web administration page).
      When response received the service subscribes the users.
   2. User receives Voice Mail. The service gets notification from Exchange server (via
      EWS).
   3. Optionally, the MWI service synchronizes with OCS 2007 in order to get the user’s
      presence status from it.
   4. MWI2007 sends SIP NOTIFY message directly to PBX or gateway.
   5. PBX lights up the lamp on user’s phone.
   6. If the SMS notification option is enabled, the service sends an SMS it to the SMS
      Provider through SMS Server. User gets notification about Voice Mail received to the
      cell phone.
   7. All these events are synchronized with the web administration interface of the MWI
      service.
   8. The service administrator interactively receives notifications about all the events
      through the web administration page.


5/74                                            SERVICE DEPLOYMENT GUIDE
Geomant support

Geomant provides e-mail support for questions and problems with MWI 2007. The support
email address is

       mwi-support@geomant.com

For additional information see the Geomant Web site:

       http://www.mwi2007.com


References
This document is strongly based on information from the following resources:


   [1] MWI2007 – System Manual – MWI Service for Microsoft Unified Messaging – System
   Manual

       http://www.mwi2007.com



    [2] RFC 3261 – SIP: Session Initiation Protocol

       http://www.ietf.org/rfc/rfc3261.txt?number=3261



    [3] RFC 3842 – A Message Summary and Message Waiting Indication Event Package for
   the Session Initiation Protocol

       http://www.ietf.org/rfc/rfc3842.txt?number=3842



   [4] RFC 3458 – Message Context for Internet Mail

       http://www.ietf.org/rfc/rfc3458.txt?number=3458



   [5] Intel NetStructure PBX/IP Media Gateway – SIP Compliance

       http://download.intel.com/network/csp/applnots/8911app.pdf



   [6] Intel NetStructure PBX/IP Media Gateway – User Guide – 2005 July


6/74                                                  SERVICE DEPLOYMENT GUIDE
       http://resource.intel.com/telecom/support/pimg/manuals/1947-01.pdf



   [7] AudioCodes – CPE Configuration Guide for Voice Mail



   [8] Mediant 2000 VoIP Media Gateway

       http://www.audiocodes.com/objects/mediant2000_wireline.pdf



   [9] Mobiline E-mail SMS gateway Install Guide

       http://www.mobiline.hu



   [10] Cisco CallManager Administration Guide

       http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/sys_ad/5_0_1/
       ccmcfg/bccm.pdf

Document History


Version       Author                Changes
1.87          Csaba Vegso           Original public version
1.92          Imre Kovacs           Reviewed, new functions added
1.96          Artur Lenart          Reviewed and Edited
2.00          Robert Simon          Reviewed and Edited based on the new GUI




7/74                                               SERVICE DEPLOYMENT GUIDE
Automatic Installation

This section describes installation steps for MWI service. Please note that installing PBXs, IP
gateways, Exchange and UM is beyond the scope of this document.




Installation prerequisites

    Software Prerequisites


       Microsoft Exchange 2007:

            o   Version 08.00.0685.9 or greater has to be installed;
            o   Autodiscovery feature is configured and available on intranet [REF.11].
                Verify that one of the following URLs can be loaded:
                https://[fully qualified domain name]/autodiscover/autodiscover.xml

                https://autodiscover.[fully qualified domain
                name]/autodiscover/autodiscover.xml



       DNS: Each IP gateway is administered in the DNS (both in the forward and reverse
        lookup zones);
         Important! Please keep in mind that MWI 2007 service will not function properly if
         any kind of DNS load-balancing is used. This also applies for hardware NLB of
         Exchange CAS roles.


       IIS: the ’Microsoft Exchange Client Access Server’ IIS web service extension is in
        allowed state on boxes where Exchange client access role is installed.
        On the MWI application server:
        -   IIS v6: Active Server Pages web extension is allowed;
        -   IIS v6: ASP.NET v2.0.50727 web extension is allowed;




8/74                                               SERVICE DEPLOYMENT GUIDE
       -   IIS v7: “Common HTTP Features” module and all its features are included;
       -   IIS v7: “Application Development” module and all its features are included;
       -   IIS v7: “Security” module and its “Windows Authentication” module are included;




      User Rights: the user performing installation has to be Domain Administrator.
       Depending on the structure of the forest – it is enough to be Domain Administrator
       in case of the person being capable to modify the security in the AD’s configuration
       naming context; if the Domain Administrator has no right to do this due to any
       policy restrictions; Enterprise Administrator rights are required for the successful
       installation. In addition, it is highly recommended to set the membership of the
       following user groups for the service user account (to avoid any troubleshooting
       later due to insufficient permissions): Exchange Read-Only Administrators or
       Exchange Recipient Administrators. The MWI service user account has to be Local
       Administrator on the server where the MWI service will be installed in order to run
       the service. For detailed steps of granting permissions for the MWI service account
       see pages 27-34.


      Windows Server and Exchange Server: It is strongly recommended to keep the
       Windows Server up to date, and apply all the MS Windows Server patches. Besides, if

9/74                                             SERVICE DEPLOYMENT GUIDE
         you apply any updates on Exchange Server please make sure that other Exchange
         servers which the application will contact/use has same updates installed. Main
         reason to do so is the fact that patches which modify low level communication (after
         server restart) can break low level connections with the servers which have no the
         patches applied and, as result, there can be problems with the MWI service to
         communicate with those servers.


        Windows Server 2003 Support Tools: It is strongly recommended that Windows
         Support Tools being installed in case the MWI service is installed on Windows Server
         2003;




        NET Framework v3.5 (or higher)




    Before the start of the installation please do the followings:

            Select the user’s name (From this point on, the installation will be referred to
             as [MWIServiceLogonAccount])
            Select the IP address (your computer can have more IP addresses).
            Verify that you have domain admin permissions.



Hardware prerequisites


Processor                     2 GHz, Intel Xeon or Intel Pentium Family (both 32 and 64-Bit),

                              AMD x64 Opteron or Athlon (AMD64)

Operating system              Windows Server 2008

                              Windows Server 2008 R2

                              Windows Server 2003 R2 x64 editions;

                              Windows Server 2003 Service Pack 1

Memory                        1 GB RAM

Available hard-disk space     700 MB

Other                         Open TCP ports 15200-15202 (inclusive)



10/74                                             SERVICE DEPLOYMENT GUIDE
MWI Service installation

There are two main steps to installing MWI: (1) installing the MWI service and (2) installing its
web-based interface. This section simply lists the installation steps. Additional information
about user credentials and security restrictions can be found in [REF.1]



There are no specific server requirements; MWI can run on any server: on separate server,
Exchange server, virtual server (e.g. VMWare) etc.

To install the MWI service, perform the following steps with domain administrator rights
(or, if any problem occurs during the installation, it’s better to install the service with new
service user account for faster troubleshooting).

In downloaded installation package you can find 3 types of installation media:

   -   Automated Installer packages (separately for x86 and x64 systems). This package
       includes combo installer, which allows to install both the MWI service and its web
       interface simultaniously;
   -   Manual Installer packages (separately for x86 and x64 systems);
   -   Files for upgrading previous versions of the MWI service (“Upgrade” folder).

Main difference between automated and manual installers is that manual installer simply
installs the service and web interface, while with automated installers it is possible to set local
and AD permissions for MWI service user account.

If you want to install the MWI service and its web interface on one server the easiest way to
do that is to use automated combo installer, which installs both at once. Also you can use
separate installers for the service and the web GUI:




Before you begin the installation please make sure that all the installation prerequisites are
considered! For permission setup please see pages 27-34.




11/74                                                SERVICE DEPLOYMENT GUIDE
  1. Execute     the      install    wizard       from     the     installation    media
     (MWIServiceInstall\MWIComboInstaller.msi).
        a. If necessary, modify the default settings for MWI web administration interface:




         b. Specify credentials of the MWI service account:




         c. Specify the permissions that will be set for the MWI service account:




     From this point on, the installation path will be referred to as MWIServiceHome;

12/74                                           SERVICE DEPLOYMENT GUIDE
Web Interface installation


If you choose to install the MWI web interface separately from the service, you will need to
start MWISrvAdmin.msi installer

The MWI web application can be collocated with the MWI service. The following table lists
the additional system requirements.

  Memory                          60 MB RAM

  Available hard-disk space       50 MB

  Software prerequisite           NET Framework v3.5, IIS 6.0+



To install the web-based administering and monitoring interface, perform the following
steps with domain administrator rights:

   1. Execute the install wizard from the installation media               (MWIWebInstall\
      MWISrvAdmin.msi). Leave the default parameters unmodified.




                           Figure 1. Installing the MWI web application
       From now on, the installation path

                              C:\Inetpub\wwwroot\MWISrvAdmin

       will be referred as MWIWebHome in the following description;


13/74                                            SERVICE DEPLOYMENT GUIDE
  2. Check the default content of the configuration file


                                 [MWIWebHome]\web.config




     The     values   of   the   following   parameters:   MWIServiceHost,   MWIServicePort,
     AdminMembership, ConfiguratorMembership and ViewerMembership may be changed
     from the defaults to fit into your environment.

IIS v6
  3. Start the IIS Manager
         a. Click on the Web Service Extensions. Verify that the ‘ASP.NET v2.0.50727’ and
             ‘Active server Pages’ ISAPI extensions are in Allowed state;




                                   Figure 2. ASP.NET 2.0 in allowed state



           b. Right click on the Web Sites\Default Web Site\MWISrvAdmin, select properties.

14/74                                             SERVICE DEPLOYMENT GUIDE
        i. Verify that the Execute permission application property is set to Scripts
           only or Scripts and Executables ;




                              Figure 3. Enabling script execution



        ii. Select the Directory Security tab and edit the Authentication and access
            control option. Uncheck the Enable anonymous access option, check
            the Integrated Windows authentication and uncheck Digest, Basic and
            .NET Passport authentication types;




15/74                                  SERVICE DEPLOYMENT GUIDE
                                     Figure 4. Setting IIS authentication



                iii. Select the ASP.NET tab and verify that ASP.NET 2.0.50727 or a later
                     version is used to execute the web application;




                                   Figure 5. Setting the required runtime

IIS v7


  4. In Windows Explorer, right click on the folder [MWIWebHome]\Log, select Sharing and
     Security. Click on the Security tab. If the executing user account (of the default
     application pool in the IIS) is not listed in Group or user names, then add it by

16/74                                         SERVICE DEPLOYMENT GUIDE
     clicking the Add button. Give Write permission for this user account on the folder
     [MWIWebHome]\Log.




                            Figure 6. Permission to create log files



  5. Verify that the executing user account has Modify permission on the directory where
     temporary files are stored by the IIS. This directory on x86:
       C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files;

     on x64:

      C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files;




17/74                                          SERVICE DEPLOYMENT GUIDE
                       Figure 7. Permission to compile web application



  6. If changes to the defaults were made in steps 4 or 5, IIS Admin Service should be
     restarted;
  7. Navigate to the


                                       https://

             [IP Address assigned to Default Web Site on the localhost]

                            /MWISrvAdmin/Default.aspx

                                           OR

                                       http://

             [IP Address assigned to Default Web Site on the localhost]

                            /MWISrvAdmin/Default.aspx



  in order to perform administrative, monitoring and reporting tasks. For administrative
  purposes, the user should be in the AD group specified in step 2 (as the
  AdminMembership parameter). Follow the next section in order to configure the MWI
  system through these web forms;




18/74                                           SERVICE DEPLOYMENT GUIDE
Specific installation steps for Windows Server 2008


The following list of the installation steps above slightly differs in case of Windows Server
2008. The differences are mostly affected by the fact that Windows Server 2008 uses IIS 7 by
default; however the list of the settings below can be used on older versions of the server if
the IIS 7 is used there too. The presented here steps are has to be considered as concrete
steps that should be performed for the successful service installation.

NOTE. For flawless and successful installation in Windows Server 2008 with UAC enabled
right-click on cmd, select “Run As Administrator” and add the location path of the installers
to run those from cmd with administrator priviledges.



   1. To check the allowed web extensions open the “ISAPI and CGI Restrictions” in the
      IIS 7




19/74                                              SERVICE DEPLOYMENT GUIDE
  2. To define the authentication method for the MWI WebGUI open the Sites, then
     Default Web Site drop-down menu and select MWISrvAdmin:




20/74                                        SERVICE DEPLOYMENT GUIDE
  3. Disable Anonymous Authentication method and enable Windows Authentication:




21/74                                       SERVICE DEPLOYMENT GUIDE
Manual installation




Web Interface installation

Before you begin the manual installation please make sure that the service user account is
created and has all required permissions (see page 8.). The steps for manual installation of
the MWI web interface are identical to the steps for automated installation, so please check
pages 13-21.




22/74                                            SERVICE DEPLOYMENT GUIDE
Service installation

During the manual installation you need to concider the fact that this will install the MWI
service only and that you will need to set all the required permissions manually. This means
that the MWI service account requires:

   1. Local permissions – it has to be local administrator on the target machine;
   2. Permissions in AD – see pages
   3. Permissions in Exchange




23/74                                            SERVICE DEPLOYMENT GUIDE
  1. After the install wizard is finished, open the license file
              [MWIServiceHome]\Lic\geomant.mwi.license.signed.xml

     with Internet Explorer and verify that the license is not restricted to other domains
     than the one the service is installed (check the Domain XML element). Check the
     maximum number of MWI enabled UM users and expiration of the license file
     (Volume XML element);




24/74                                          SERVICE DEPLOYMENT GUIDE
                        Figure 8. Checking the license file content



  2. Check the default content of the configuration file


                [MWIServiceHome]\Config\geomant.mwi.config.xml



     Set the value of the ‘Base DN’ parameter (located in the ActiveDirectoryConnector
     section) to that of the distinguished name of your Exchange domain.

     ‘Use Forest Root’ parameter’s value is set to “yes” by default. If you need to retrieve
     UM users from one particular OU, change the value to ‘no’ and then specify the
     distinguished name of the OU in the ‘BaseDN’ parameter.




                      Figure 9. Specifying base distinguished name



25/74                                            SERVICE DEPLOYMENT GUIDE
   3. Verify that the MWI service account has all the following permissions:

       a. Write permission on the [MWIServiceHome] directory;




                            Figure 10. Permission to create log files and backup



       b. Permission to read UM configuration data and read/write UM user data from the
          Active Directory (AD). To grant this, perform the following steps:


              I.
                   Click on Start->Run, type in adsiedit.msc. You can always open this utility
                    from Domain Controller. If you have no access to DC and the command
                    command cannot be executed on Windows 2003, then Windows Support
                    Tools need to be installed. In case of Windows 2008 you need to install
                    Active Directory Lightweight Directory Services role from server manager.


             II.
                   Locate the Configuration Naming Context folder;


Locate the following container: “CN=UM IPGateway
Container,CN=Organization_Name,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=local” and right-click on it.
            III.
                   Select the Security tab;


26/74                                                SERVICE DEPLOYMENT GUIDE
27/74   SERVICE DEPLOYMENT GUIDE
        IV.
               Click Advanced;




         V.
               Click Add;




        VI. Type in the [MWIServiceLogonAccount] user, and then click OK;


        VII.
               Click the [MWIServiceLogonAccount] user, and then click Edit;




28/74                                           SERVICE DEPLOYMENT GUIDE
                           Figure 11. Permission to read UM configuration data
        VIII.
                From the Apply onto list-box select the ‘This object and all child object’ (or
                 ‘This object and all descendant objects’)


         IX.
                From the list of permission entries select the ‘List Contents’, ‘Read All
                 Properties’ and ‘Read Permissions’;


          X.
                Make sure that ‘Apply these permission to the objects and containers
                within this container only’ is unchecked;


         XI.
                Click OK;
                 Locate the User(*) folder under the Domain Naming Context folder;
                 Right-click the User(*) folder, and then click Properties;
                 Select the Security tab;
                 Click Advanced;
                 Click Add;
                 Type in the [MWIServiceLogonAccount] user, and then click OK;
                 Click the [MWIServiceLogonAccount] user, and then click Edit;
                 From the Apply onto list-box select the ‘This object and all child
                    object’;
                 From the list of permission entries select the ‘List Contents’, ‘Read All
                    Properties’, ‘Write All Properties’, ‘Read Permissions’ and ‘All
                    Validated Writes’;


29/74                                              SERVICE DEPLOYMENT GUIDE
                   Make sure the ‘Apply these permission to the objects and containers
                    within this container only’ is unchecked;
                   Click OK;




                             Figure 12. Permission to read/write UM user attributes


         (*)
               The MWI service account should have the same permission on each OU where
         at least one UM user is located for whom MWI service will be activated.



  Above permissions are set on the user containers instead of the user objects. To ensure
  that the user objects inherit the specified permissions and the inheritance is not broken,
  please use the adsiedit Windows Support tool and right click on the user object > select
  Properties > select the Security tab > press the Advanced button > and make sure that
  the “Allow inheritable …” property is set to on as shown in Figure 13.




30/74                                             SERVICE DEPLOYMENT GUIDE
                            Figure 13. Inherit permission from parent



    c. Full permission to UM users’ mailboxes for which the MWI service will be
       activated. There are four ways to give full permission to access mailboxes for MWI
       service in the Exchange Management Shell:


           1. User by user you can use the add-mailboxpermission command. For
               example, to give full access to user1’s mailbox, execute


        Add-Mailboxpermission user1 –user [MWIServiceLogonAccount] –accessrights fullaccess




           2. To grant impersonation permission to the MWI service account on a given
               client access server (if you select this way please check the Impersonate
               user check box on the „Settings for Exchange Server Access” page of
               MWI2007 web interface)

             Add-ADPermission -Identity [Exchange Server DN] -User [MWI Service Account] -
                            extendedRights ms-Exch-EPI-Impersonation –InheritanceType none




               To grant permission to the MWI service account to impersonate any user
               in the given mailbox database

            Add-ADPermission -Identity [Mailbox database DN] -User [MWI Service Account] -
                          extendedRights ms-Exch-EPI-May-Impersonate –InheritanceType none

31/74                                          SERVICE DEPLOYMENT GUIDE
           3. To grant impersonation permission to the MWI service account on all
               client access servers and to enable impersonation for the service user on
               all Exchange servers execute the following commands:


        Get-MailboxDatabase | Add-ADPermission -User DOMAIN\MWISERVICE -extendedRights ms-
                                            Exch-EPI-May-Impersonate -InheritanceType none



    Get-ExchangeServer | Add-ADPermission -User DOMAIN\MWISERVICE -extendedRights ms-Exch-
                                                   EPI-Impersonation -InheritanceType none




           4. To grant impersonation permission and to enable impersonation for the
               service user account on given client access servers:


                      Add-ADPermission -Identity (Get-ExchangeServer “Name of the first CAS
        Server”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                        Impersonation -InheritanceType none

                     Add-ADPermission -Identity (Get-ExchangeServer “Name of the second CAS
        Server”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                        Impersonation -InheritanceType none


                                                                                           …
                        Add-ADPermission -Identity (Get-ExchangeServer “Name of the Xth CAS
        Server”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                        Impersonation -InheritanceType none




                Add-ADPermission -Identity (Get-MailboxDatabase “Name of the first Mailbox
     Database”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                     May-Impersonate -InheritanceType none

               Add-ADPermission -Identity (Get-MailboxDatabase “Name of the second Mailbox
     Database”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                     May-Impersonate -InheritanceType none


                                                                                           …
                  Add-ADPermission -Identity (Get-MailboxDatabase “Name of the Xth Mailbox
     Database”).DistinguishedName -User [MWI Service Account] -extendedRights ms-Exch-EPI-
                                                     May-Impersonate -InheritanceType none




    d. Permission to host the MWIEventSink ASP.NET WebService. Perform the following
       steps:
        Grant access to the ASP.NET resources:
                        C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –ga
                                                                   [MWIServiceLogonAccount]


32/74                                          SERVICE DEPLOYMENT GUIDE
            In case of 64-Bit processor:

                      C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe –ga
                                                                   [MWIServiceLogonAccount]




           Register the “http://*:15201/” URL for the WebService
                    In Windows 2003: verify that the httpcfg utility (Windows Support
                       Tools) is available through the system path. Open a command shell
                       and execute the following:
                      [MWIServiceHome]\Util\createUrlAcl.vbs /user:[MWIServiceLogonAccount]
                                                            /domain:[MWIServiceLogonDomain]


            After having executed the script, use the httpcfg utility to check that the URL is
            registered for the application.




                                   Figure 14. Listing registered URLs
                    In Windows 2008: Run the following command

                                 netsh http add urlacl url=http://*:15201/ user=DOMAIN\user


               To verify if the URL ACL is created run this command
                                                   netsh http show urlacl url=http://*:15201


            1. Start the ‘MWI Service – Geomant’ in the Windows SCM;
            2. Verify that no ERROR entries are created into the log file


                      [MWIServiceHome]\Log\MWIService.log




33/74                                           SERVICE DEPLOYMENT GUIDE
34/74   SERVICE DEPLOYMENT GUIDE
Integration with Lync

Certificate request


  1. On MWI host click Start  Run… , type mmc and click Ok
  2. Select File  Add/Remove Snap-in:




  3. Select Certificates and click Add, then click OK:




35/74                                        SERVICE DEPLOYMENT GUIDE
  4. Select Computer account and click Next:




  5. Select Local computer and click Finish, then click OK




36/74                                       SERVICE DEPLOYMENT GUIDE
  6. Expand the Certificates (Local computer)  Personal  Certificates. Right-
     click on Certificates and select All Tasks  Request New Certificate…




  7. Select Enrollment policy and click Next:




  8. Select Computer, expand Details menu and click Properties:




37/74                                       SERVICE DEPLOYMENT GUIDE
  9. In General tab specify friendly name for the new certificate:




38/74                                        SERVICE DEPLOYMENT GUIDE
  10. In Subject tab specify: Common name (FQDN of MWI host);
     Country;
     Locality;
     Organization;
     Organizational Unit
     Then click OK:




  11. Click Enroll




39/74                                   SERVICE DEPLOYMENT GUIDE
Enable the MWI service user account for Lync and after that open the MWI web
interface at Configuration  Lync Server. On the page:

   1. Check Enable box;
   2. Specify the Lync SIP URI and Lync Display Name of the MWI service user
      account;
   3. Specify Lync Front End FQDN. In case of Lync Enterprise edition – FQDN of
      Lync pool




Click Save and restart MWI service.




40/74                                        SERVICE DEPLOYMENT GUIDE
Web based configuration

MWI parameters can be changed while the service is running, this can be done via the web
based administration forms.



Web-based administration
This section includes several screenshots depicting a typical MWI service configuration.



Figure 18 shows the general system parameters. The periodic re-synchronization (Forced
Synch Period) interval is set to 720 minutes and a supervisor is administered (Supervisor)
having AD display name ‘Supervisor1’.




                              Figure 15. General system properties



As shown in Figure 19, no particular AD host is specified (Host). In this scenario the system
resolves directory services through DNS SRRs. The base distinguished name is filled (Base
DN), so UM users are searched for only in the given AD tree or domain. The LDAP
authentication is set to delegate the credentials of the user account under which the MWI
service is running (Delegate).




41/74                                              SERVICE DEPLOYMENT GUIDE
                         Figure 16. Active Directory related properties
The Refresh period property is set to 3600, so the local cache - containing IP gateways and
UM users – will be synchronized to the AD content in each hour. The user can click to the
Start Synchronization to AD Contact link in order to instruct the MWI service to download
IP gateways and UM user from the Active Directory immediately instead of waiting until the
end of the current Refresh period.
According to the Exchange related parameters (Figure 20), the system uses XML WebService
to access MWI enabled UM users’ mailboxes (Protocol). Exchange authentication is based on
delegated user credentials (Delegate). Since no particular IP address is specified (Event sink
IP), the first address from the local IP address list is used to construct call-back URLs (sent in
push subscription requests to Exchange CASs). By default, the TCP port 15201 (Event sink
port) is used to receive notification events. The MWI service does not create a separate
search folder for voicemails (Create VM folder is unchecked). Instead of creating “own”
folders, the MWI services subscribes to the voicemail search folder created by Exchange
when UM is enabled. The folder is called “Voice Mail” (Exchange VM folder). Note that the
name of this folder might be language dependent. The last parameter (Secure layer)
specifies that accessing IIS virtual directories on client access servers requires SSL. Secure
connections are required in almost every production environment. However, test
environments generally offer unsecured access to these folders. Since the Impersonate user
property is set to no, the MWI service will not instruct the client access server to impersonate
an UM user before accessing his mailbox. Each UM user’s mailbox will be accessed by the
credentials under which the MWI service is running (since the Delegate property is set to
yes). That is why the MWI service account should have fullaccess permission on each UM
users’ mailbox. To get details about how to connect to the mailbox of a given UM user, the
MWI service will turn to the Exchange Autodiscovery service (Use Autodiscovery).
42/74                                               SERVICE DEPLOYMENT GUIDE
Please note, that the Event sink IP field should be filled with local IP address only if Window
Server 2008 is used (as well as Local IP parameter’s value in the configuration
file).




                           Figure 17. Exchange related properties



Figure 21 shows that TCP transport is selected to communicate with each gateway
(Transport). The remote SIP port is 5060 (Gateway Port) and the number of ports or
channels allocated for MWI service is 2 in each gateway (MWI Ports). Finally, each gateway
supports unsolicited NOTIFYs (Subscription is unset). The Local Port has no importance in
this case.




43/74                                              SERVICE DEPLOYMENT GUIDE
                             Figure 18. SIP related properties
Figure 22 shows the system parameters related to email/SMS gateway configuration. The
settings specify several MIME email header parameters (From, Subject, Charset). Since the
Type parameter is set to “Email/SMS gateway with DNS MX query”, the Base DN specifies a
domain name. This domain name is used to retrieve MX records from the DNS. The one
which has the smallest preference number will specify the address of the SMTP server. SMSs
will be sent to this SMTP server in MIME format. The MIME ‘To’ header is constructed as [UM
user’s GSM number]@[Destination DN]. Since the Anonymous option is unchecked, the User
and Password parameters will be used for SMTP authentication purposes. Generally, AUTH
LOGIN authentication method is used. The Notification text property allows specifying the
email body to be sent. To construct message body based on the UM user’s identity, the
following parameters are available:
User   related    AD       attributes:   USER_DISPLAY_NAME,  USER_EMAIL_ADDRESS,
USER_EMAIL_ALIAS,                        USER_PHONE_EXTENSION, USER_PHONE_GSM,
USER_LOGON_NAME;
Voicemail related properties: VM_DATE_CREATED, VM_LOCALTIME, VM_SUBJECT,
VM_DATE_RECEIVED, VM_DATE_SENT, VM_DISPLAY_CC, VM_DISPLAY_TO, VM_IMPORTANCE,
VM_SENSITIVITY, VM_SIZE;
Fax related properties: FX_DATE_CREATED, FX_LOCALTIME, FX_SUBJECT, FX_DATE_RECEIVED,
FX_DATE_SENT, FX_DISPLAY_CC, FX_DISPLAY_TO, FX_IMPORTANCE, FX_SENSITIVITY, FX_SIZE;
Missed call related properties: MC_DATE_CREATED, MC_LOCALTIME, MC_SUBJECT,
MC_DATE_RECEIVED, MC_DATE_SENT, MC_DISPLAY_CC, MC_DISPLAY_TO, MC_IMPORTANCE,
MC_SENSITIVITY, MC_SIZE;




44/74                                            SERVICE DEPLOYMENT GUIDE
                              Figure 19. SMS related properties
Figure 23 lists the phone number mapping rules applied to GSM numbers when sending
SMS notifications. The first rule instructs the system

   1. to delete the first one character from phone numbers starting with ’+3670’;
   2. then remove characters ‘ ’, ‘.’, ‘,’, ‘+’, ‘(’, ‘)’ from the result;
   3. and finally it can insert a prefix into the beginning of the result (e.g. country code);




45/74                                               SERVICE DEPLOYMENT GUIDE
                        Figure 20. Phone number mapping rules


If multiple rules could be applied to a given phone number then the system applies only the
most specific one.




46/74                                           SERVICE DEPLOYMENT GUIDE
IP gateway configuration

The main purpose of this section is not to describe complete configuration of different IP
gateways. The required configuration steps can be found in the documentation provided by
the gateway vendors. This section highlights vendor specific parameter settings which are
relevant to the MWI.



Tested IP gateways
The following table lists the gateway family, gateway firmware version and telephony
protocol type triplets with which the MWI application was internally tested by us. If tests are
performed with multiple firmware versions then the lowest version number is included. If a
given telephony protocol is not supported by a given gateway family, it is indicated with the
‘not available’ (n.a.) phrase.



                     Gateway                                 Telephony Protocol

Gateway name                     Software version   Proprietary   SMDI    In-band     Q.SIG
                                                    VoIP
                                                                           DTMF

Intel PIMG80PB                   Platform 4 v2      n.a.            √         √        n.a.

AudioCodes Mediant               4.60AC.034.003D    n.a.            ×         √            ×
2000

Cisco CallManager                5.0                √               ×        n.a.      n.a.



        √ - tested; ×-not tested; º - not supported; n.a. – not available on the gateway



Asterisk Trixbox 2.2 as PBX solution was tested with a sipX 3.8 gateway for TCP conversion.

To test the interoperability with Intel and AudioCodes gateways, we have used Avaya
Definity ECS. Unfortunately, we did not have the opportunity to test with other types of PBX.
Please note that the MWI service communicates directly only with IP gateways. Declaring
PBX support is generally up to gateway vendors.




47/74                                               SERVICE DEPLOYMENT GUIDE
Special thanks to AudioCodes. They have performed extensive interoperability testing with
our software and theirs gateway family (version 4.8 firmware). We are informed that MWI
service is functioning correctly with the following types of AudioCodes gateways and PBX
environments.

       PBX                        AudioCodes        Telephony Protocol
                                  gateway

       Avaya Merlin Magix         Mediant 2000      T1 QSIG, In-band DTMF

       Avaya Merlin Magix         MP-11x            Analog, In-band DTMF

       Avaya S8300                Mediant 2000      T1 QSIG, In-band DTMF

       Avaya S8300                MP-11x            Analog, In-band DTMF

       Avaya Definity             Mediant 2000      T1 QSIG, In-band DTMF

       Avaya Definity             MP-11x            Analog, In-band DTMF

       Alcatel OmiPCX 4400        Mediant 2000      T1 QSIG, In-band DTMF

       Alcatel OmiPCX 4400        MP-11x            Analog, In-band DTMF

       Nortel Meridian 81C        Mediant 2000      T1 QSIG, In-band DTMF

       Nortel Meridian 81C        Mediant 2000      E1 QSIG, In-band DTMF

       Nortel CS1K                Mediant 2000      T1 QSIG, In-band DTMF

       Nortel CS1K                Mediant 2000      E1 QSIG, In-band DTMF

       Siemens HiPass 4000        Mediant 2000      T1 QSIG, In-band DTMF

       Siemens HiPath 4000        MP-11x            Analog, In-band DTMF

       Siemens HiPath 3550        MP-11x            Analog, In-band DTMF

       Siemens Hicom 150E         MP-11x            Analog, In-band DTMF

       NEC NEAX 2400 IPX          MP-11x            Analog, SMDI (MCI)

       NEC NEAX 2400 IPX          Mediant 2000      CAS SMDI (MCI)

       Mitel 3300                 Mediant 1000      T1 QSIG, In-band DTMF

       Mitel 3300                 Mediant 2000      T1 QSIG, In-band DTMF

       Inter-Tel Axxess           Mediant 2000      T1 CAS, In-band DTMF


48/74                                          SERVICE DEPLOYMENT GUIDE
          Inter-Tel 5000            Mediant 2000        T1 CAS, In-band DTMF




Intel NetStructure PIMG80PB
The MWI application is tested by using the following types of telephony protocols: SMDI,
digital set emulation (in-band DTMF).



To specify TCP transport for SIP messages set the following parameters:

                                  sipTransportType = TCP



The gateway [REF.5], [REF.6] accepts NOTIFY messages without SIP SUBSCRIPTION.




MWI though SMDI
Specify the number of digits in extensions by setting

                                        telSerCpidLen

Set the serial protocol to SMDI

                                    telSerProtocol=SMDI

Set master mode

                                    telSerMode=Master




MWI though in-band DTMF
To configure MWI FACs for the given PBX, the telMwiOnFAC and telMwiOffFAC parameters
should be specified e.g.

                                     telMwiOnFAC = *77

                                    telMwiOffFAC = #77



To allocate gateway ports for the MWI service, the telPortEnabled, telPortCapability and
gwNetworkID parameters should be specified correctly. To allocate e.g. gateway ports 1, 2, 3
specify


49/74                                             SERVICE DEPLOYMENT GUIDE
                                telPortEnabled: Port1 = Yes

                                telPortEnabled: Port2 = Yes

                                telPortEnabled: Port3 = Yes



                           telPortCapability: Port1 = MWIs-Only

                           telPortCapability: Port2 = MWIs-Only

                           telPortCapability: Port3 = MWIs-Only



                gwNetworkID: Port1 = [IP address of the MWI service host]

                gwNetworkID: Port2 = [IP address of the MWI service host]

                gwNetworkID: Port2 = [IP address of the MWI service host]




AudioCodes Mediant 2000
The MWI application is tested by using the following types of telephony protocols: in-band
DTMF.



To enable MWI set

                                        [SIP Params]

                                     ENABLEMWI = 1



To specify TCP transport for SIP messages set the following parameters:

                                        [SIP Params]

                                  SIPTRANSPORTTYPE = 1

The gateway [REF.7], [REF.8] accepts NOTIFY messages without SIP SUBSCRIPTION
(SUBSCRIPTIONMODE = 1). To enable accepting NOTIFY requests from the MWI server, fill
the parameter

                                        [SIP Params]


50/74                                            SERVICE DEPLOYMENT GUIDE
                     MWISERVERIP = ‘[IP address of the MWI service host]’

MWI though SMDI
To enable MWI over SMDI set

                                          [SIP Params]

                                   VOICEMAILINTERFACE = 2

                                        ENABLESMDI = 1

MWI though in-band DTMF
To enable MWI over DTMF set

                                          [SIP Params]

                                   VOICEMAILINTERFACE = 1

To configure MWI FACs for the given PBX, the MWIOnCode and MWIOffCode parameters
should be specified e.g.

                                          [SIP Params]

                                      MWIOnCode = ‘*77’

                                      MWIOffCode = ‘#77’

To allocate gateway channels for the MWI service, specify IP->PSTN routing for the required
telephony channels

                    PSTNPREFIX = *,1,*, [IP address of the MWI service host],1

Cisco CallManager 5.0
The MWI application is tested by using the following types of telephony protocols:
proprietary VOIP.



The SIP trunk requirement on the CallManager [REF.10] depends on the location of the MWI
service. If the MWI service is collocated with the Microsoft UM role, the same trunk may be
used for both of them. Otherwise, a separate SIP trunk should be administered for the MWI
service. The trunk should support the TCP transport and should support unsolicited SIP
NOTIFY. These options can be enabled in the SIP Trunk Security Profile assigned to the trunk.
The supported transport protocols can be specified by using the Incoming Transport Type
and Outgoing Transport Type profile parameters. Specify the TCP parameters. To enable
unsolicited SIP notification, set the Accept Unsolicited Notification parameter to true.


51/74                                               SERVICE DEPLOYMENT GUIDE
SMS gateway configuration

Currently the MWI service supports only email/SMS gateways where gateways receive
messages from the MWI service via the SMTP protocol; it constructs SMS from the email
content and sends that to the GSM network. Destination GSM numbers are included in MIME
‘To’ headers like:

                                 [GSM number]@[Destination DN]



Mobiline Email/SMS gateway
There are several parameters which must be set in order to send outbound SMS through the
gateway. See [REF.9] details on gateway configuration.

Verify that the following MWI service parameter (in the SMSGatewayConnector section) and
SMS gateway parameter values are in synch:

                MWI service parameter              SMS gateway parameter

                Host                               ipaddr

                Port                               smtpport

                From                               user01


                 Table 1. Synchronizing gateway and MWI service parameters
and the following MWI service parameters are specified as follows:

                       MWI service parameter        Value

                       Type                         ‘Email/SMS gateway’

                       Charset                      ‘ISO-8859-2’

                       Anonymous                    Yes

                       User                         Nothing

                       Password                     Nothing

                       Max SMS size                 160


                              Table 2. Setting MWI service parameters


52/74                                               SERVICE DEPLOYMENT GUIDE
Multiple MWI service instances

It is possible to install multiple MWI service instances in the same Active Directory
environment and distribute UM users between these instances. To setup such an
environment the manual installation (section ‘Manual Installation’) steps should be followed.




                        Figure 21. Multiple MWI service instances




53/74                                             SERVICE DEPLOYMENT GUIDE
As can be seen in Figure 24, the same IP gateway or Exchange client access server can be
used by different MWI service instances. Regarding a given UM user, the IP gateway is
specified by the MWI administrator when enabling the MWI service for the user. The client
access server is resolved by the Exchange autodiscovery service based on the UM user’s
primary SMTP address.

The only important thing it to ensure that a given UM user is managed only by one MWI
service instance. To do that there are 2 options:

     creating a separate MWIServiceLogonAccount for each MWI service instance and
        granting permissions to each account to read just a given subset of UM users (step
        4.c on page 14). In our current example this would mean to create a user account
        ‘MWISrvUser1’ for instance 1 and grant permissions to read UM users only from the
        container CN=OU1,DC=exch12,DC=geomant,DC=com. For the second MWI service
        instance we would create another user account ‘MWISrvUser2’ and grant
        permissions      to    read     UM      users    only      from     the    container
        CN=OU2,DC=exch12,DC=geomant,DC=com;
     using the same MWIServiceLogonAccount for each MWI service instance but
        setting the Base DN parameter to different values (Figure 19). In our example this
        would mean to create a user account ‘MWISrvUser’ and setting the Base DN
        parameter to CN=OU1,DC=exch12,DC=geomant,DC=com on the first MWI service
        instance and setting to CN=OU2,DC=exch12,DC=geomant,DC=com on the second
        MWI service instance;
In the first case, the ‘MWISrvUser1’ account should have fullaccess permission only on those
UM users’ mailboxes which are belonging to OU1, while the ‘MWISrvUser2’ account should
have this permission only on those UM users’ mailboxes which are belonging to OU2. In the
second case, the ‘MWISrvUser’ should have fullaccess permissions on both the UM users’
mailboxes belonging to OU1 and OU2.




54/74                                               SERVICE DEPLOYMENT GUIDE
Troubleshooting

Most difficulties with MWI occur as a result of specifying user credential with incorrect
permissions. As such, the most common of these scenarios are presented here.



Failed to access web admin pages
”HTTP Error 404 – File or directory not found.” Error message is displayed by the browser
when trying to access the MWISrvAdmin web application.



Verify that

      the ‘ASP.NET v2.0.50727’ web service extension is in Allowed state in the IIS;
      the user account under which the web application is running (generally the
       NETWORK SERVICE) has Modify permission on the ASP.NET temporary directory:
        C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files;

      the IIS installed with all possible options (for example ASP, remoting services...); if it
       isn’t, then run the following commands:
            o aspnet_regiis.exe –i (re-installing ASP.NET);
            o iisreset (resarts IIS)


Event subscription failure
”HTTP Error 403 – Forbidden” log entries can be found in the service log file. Verify that
the ’Secure layer’ parameter in the service configuration file is specified correctly. These
messages generally results from the fact that the MWI application tries to access IIS virtual
directories on client access servers by using TCP port 80 instead of the SSL port 443.




55/74                                                SERVICE DEPLOYMENT GUIDE
Failed to retrieve IP gateways
No IP gateways could be retrieved by the MWI service from AD.



                          Symptom

              Web         No IP gateways are listed in the Configuration – SIP
              admin       Gateway form.
              GUI

              Alarm       -
              raised

              Service     “WARN – No SIP gateways have been retrieved.
              log         Please make sure that at least one gateway is
                          administered and service credential has correct
                          permissions.”



Verify that

       at least one IP gateway is administered through the Exchange 2007 MMC interface;
       the user credential under which the MWI service is running has the required
        permissions to retrieve IP gateways from AD (see the section ‘Security Perspective’ in
        [REF.1]);


Failed to retrieve UM users
No UM users could be retrieved by the MWI service from AD.



                          Symptom

              Web         No UM users are listed in the Administration – UM
              admin       Users form.
              GUI

              Alarm       -
              raised

              Service     “WARN – No UM users have been retrieved.”
              log




56/74                                             SERVICE DEPLOYMENT GUIDE
Verify that

        UM service is enabled for at least one AD user through the Exchange 2007 MMC
         interface;
        The Base DN parameter is configured correctly on the Configuration – Active
         Directory web form;
        the user credential under which the MWI service is running has the required
         permissions to retrieve UM users from AD (see the section ‘Security Perspective’ in
         [REF.1]);


Note: UM users are queried by the MWI service only if at least one IP gateway is
retrieved from AD. If no gateway could be retrieved, no AD query is executed to
retrieve UM users.



Mailbox access error
No mailbox state can be obtained through Exchange CAS.



                Symptom

   Web          Message counters and timestamps in the Administration – UM User
   admin        form are not refreshed.
   GUI

   Alarm        “Failed to check voicemails for the user: [distinguished name].” or
   raised
                “Failed to subscribe the user: [distinguished name] for Exchange events”

   Service      “ERROR – Failed to check voicemails for the user: [distinguished name].”
   log          or

                “Failed to subscribe the user: [distinguished name] for Exchange events”



Verify that

        Mailbox access URLs are correctly displayed in the Administration – UM User form;
        the user credential under which the MWI service is running has the required
         permissions to the UM user’s mailbox (see the section ‘Security Perspective’ in
         [REF.1]);




57/74                                             SERVICE DEPLOYMENT GUIDE
Note: the mailbox state of a given user is refreshed only if the MWI service is activated for
the UM users.



Message received from gateway: 504 DNS Timeout
The SIP domain name and the AD domain names are different.

Change the value of the “Use FQDN” parameter in the configuration file to ‘no’.




“General Access Denied” Error
Make sure that the service user account has permissions to write on the OU(s) where the UM
enabled users are stored. The user account must have following permissions on users’ OU:
‘List Contents’, ‘Read All Properties’, ‘Write All Properties’, ‘Read Permissions’ and ‘All Validated
Writes’ (see page17.)



Failed to monitor the CPU Usage at this moment

(Failed to monitor the Page File at this moment)
Access to the registry key 'Global' is denied.

Make sure that the MWI service user account is member of the Local administrators group
on the server.



No service logs
No log entries are created in the Logs subdirectory of the MWI service.

Verify that

       the user credential under which the MWI service is running has the required
        permissions on its install directory (see the section ‘Security Perspective’ in [REF.1]);
       the following files are presented in the Log folder: mwiservice.logger.properties,
        mwicmdtool.logger.properties. If any of these files are missing, then you can find them
        in the Upgrade/Log folder of the installation package; simply copy them into the Log
        folder where the service is installed.




58/74                                                 SERVICE DEPLOYMENT GUIDE
No web application logs
No log entries are created in the Logs subdirectory of the web application.



Verify that

       the user account under which the web application is executed has the required
        permissions on the Logs subdirectory (see the section ‘Security Perspective’ in
        [REF.1]);


Failed to connect to the MWI service
The web application cannot connect to the MWI service.



                              Symptom

              Web     admin “Failed to Connect to the MWI Service. Please make
              GUI             sure the service is running.”

              Alarm raised    -

              Service log     -



Verify that

       The MWI service is running at the remote endpoint specified by the MWIServiceHost
        and MWI ServicePort parameters in the web.config file (see the section ‘Web based
        administration’ in [REF.1]);
       The web application has permission to connect to the service. This means that the
        Client hosts and Client identities parameters are specified correctly in the service
        configuration file (see the section ‘System operation’ in [REF.1]);


Failed to initialize HTTP listener object
The error indicates that MWIEventSink web service cannot be started. The origins of this
error may be the following

   -    The user account which runs the MWI service has no permission to bind the
        http://*:15201 local URL (see also page 21.). To check if this is so please run the
        following command in CMD: httpcfg query urlacl (The Windows Support Tools has to
        be installed in order to use httpcfg utility). If you will not find the url with 15201 port
        then you have to execute one of the commands:



59/74                                                SERVICE DEPLOYMENT GUIDE
      C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe                    –ga
      [MWIServiceLogonAccount]



      C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe                  –ga
      [MWIServiceLogonAccount]



  -   The 15201 TCP port is blocked by firewall. Please add this port to your firewall
      exception list.




60/74                                            SERVICE DEPLOYMENT GUIDE
Web form is disabled
User access to the web form is disabled.



                               Symptom

              Web      admin “You have no rights to this administrative page.”
              GUI

              Alarm raised     -

              Service log      -



Verify that

       The user account used to access the web form has MWI system administrator role
        meaning that it is the member of the AD user group specified by the
        AdminMembership parameters in the web.config file (see the section ‘Web based
        administration’ in [REF.1]);




61/74                                              SERVICE DEPLOYMENT GUIDE
Scalability

This section makes some estimation for application scalability by taking the number of UM
users and allocated gateway ports into account.



Memory requirement
There exists an in-memory MWIItem object for each UM user. Assuming the following
average sizes for MWIItem string members, MWIItem has the size of 164 bytes (the table
below does not show some 4 byte items).



                             Member Name            Bytes

                             emailAddress           64

                             extension              16

                             sipGateway             32

                             gsmNumber              16



This means that a system with 10.000 UM users requires ~1.6 MB memory.



CPU requirement
Timers in the application guarantee that there is no significant processor overhead. The
required CPU time in user mode cannot exceed 5% on an Intel Pentium 4 – 1GHz at any
given point.



Gateway port requirement
Measurements with Avaya Definity R11 and Intel NetStructure gateway [REF.4] shows that
2.367 seconds (on average) elapse between sending a SIP NOTIFY message to the gateway
and receiving the OK 2xx message.



Assuming a theoretical MWI system where:


62/74                                             SERVICE DEPLOYMENT GUIDE
      The number of gateway ports allocated for MWI service is c;
      Voice-mailbox state transitions (between: # of unread voicemail messages 0 and >0)
       are occurring randomly as a Poisson process;
    Transitions are queued and each of them is performed on the physical phone;
    Completing each lamp change request on the phone takes D=2.4 seconds;
    The PBX is port insensitive;
then the system can be modeled by an M/D/c queuing system.



By applying the analytical properties of M/D/c queuing model, the average waiting time of
MWI requests can be calculated easily. An example is depicted in Figure 10. The correct
interpretation of the content of this figure is the following: assuming that UM population
results in state transitions occurring with 0.3 [1/secs] intensity, the time elapsed until mailbox
state is reflected on the physical phone:

    3.685 seconds when 1 port is used;
    2.481 seconds when 2 ports are used;
    2.41 seconds when 3 ports are used;
    2.4 seconds when 5 or more ports are used;
Note that these quantities mean upper bounds, since the system does not perform each
state transition on the phone. Multiple transitions may be accumulated and performed
together. Moreover, a given lamp state change request can cancel multiple already queued
ones.

Forgetting this operational difference between the theoretical system and the real one, the
model states the following: if a 10.000 user population generates state transitions with 0.3
[1/secs] intensity, 3 gateway ports are enough to synchronize lamp states. The bottleneck is
the 2.4 seconds taken by the gateway to fulfill SIP NOTIFY requests.




63/74                                               SERVICE DEPLOYMENT GUIDE
                                  Average to time to perform MWI change
                                                 request
                     3.8


                     3.6


                     3.4                                                              1 gateway port
                                                                                      2 gateway ports
                     3.2
                   seconds                                                            3 gateway ports
                     3.0                                                              5 gateway ports

                     2.8


                     2.6


                     2.4


                     2.2
                              0.3      0.25      0.2       0.15       0.1      0.05        0.01

                                                change intensity [1/secs]



                                     Average waiting time of MWI requests

Average synch time



Assuming that the PBX/IP gateway needs 2.4 seconds to perform each SIP NOTIFY request,
the following results are obtained for the average phone lamp synchronization time. The
numerical values are calculated by modelling the system with an M/D/c queuing mechanism,
where MWI lamp change requests coming according to a Poisson process, performing lamp
state change requires constant time and there are c gateway ports dedicated to MWI service.

The average synchronization time is listed as a function of the number of ports and the
average intensity of state change requests. Of course, the average state change intensity
strongly depends on the size of UM user population. Increasing the number of MWI enabled
UM users leads to an increase in the state change intensity.



                                                       # of allocated gateway ports for MWI 2007
                                       1 port          2 ports        3 ports      5 ports       10 ports
                           4.5                    -               -            -              -                -
                           4                      -               -            -              -           3.4856
                           3.5                    -               -            -              -           2.5662
                           3                      -               -            -              -           2.4507
     Mailbox state         2.5                    -               -            -              -           2.4153
      transitions          2                      -               -            -         4.6696           2.4036
       intensity           1.8                    -               -            -         2.9163           2.4017
                           1.6                    -               -            -         2.6242           2.4007
       [1/secs]            1.4                    -               -            -         2.5108           2.4003
                           1.2                    -               -       6.2727         2.4553           2.4000
                           1.1                    -               -       3.5019         2.4383           2.4000
                           1                      -               -       2.9539         2.4259           2.4000
                           0.98                   -               -       2.8937         2.4239           2.4000
                           0.95                   -               -       2.8189         2.4210           2.4000


64/74                                                             SERVICE DEPLOYMENT GUIDE
                               0.9                                 -                      -                  2.7238               2.4169                  2.4000
                               0.85                                -                      -                  2.6536               2.4134                  2.4000
                               0.8                                 -                 8.2934                  2.6001               2.4105                  2.4000
                               0.75                                -                 4.5469                  2.5584               2.4081                  2.4000
                               0.7                                 -                 3.6132                  2.5252               2.4061                  2.4000
                               0.65                                -                 3.1909                  2.4985               2.4045                  2.4000
                               0.6                                 -                 2.9516                  2.4769               2.4032                  2.4000
                               0.55                                -                 2.7985                  2.4593               2.4022                  2.4000
                               0.5                                 -                 2.6930                  2.4450               2.4015                  2.4000
                               0.45                                -                 2.6166                  2.4333               2.4009                  2.4000
                               0.4                           14.4000                 2.5593                  2.4240               2.4005                  2.4000
                               0.35                           5.0250                 2.5155                  2.4166               2.4003                  2.4000
                               0.3                            3.6857                 2.4816                  2.4108               2.4001                  2.4000
                               0.25                           3.1500                 2.4552                  2.4065               2.4000                  2.4000
                               0.2                            2.8615                 2.4349                  2.4035               2.4000                  2.4000
                               0.15                           2.6812                 2.4196                  2.4015               2.4000                  2.4000
                               0.1                            2.5578                 2.4088                  2.4005               2.4000                  2.4000
                               0.05                           2.4681                 2.4022                  2.4000               2.4000                  2.4000
                               0.01                           2.4122                 2.4000                  2.4000               2.4000                  2.4000




The ‘-’ means that no numerical result can be obtained from M/D/c queuing models (due to
stability issues).

Assuming that 4 seconds is the maximum acceptable time to the phone lamp
synchronization, the table above shows critical regions in red.


                             Average to time to perform MWI change request
                        16.000000


                        14.000000                                                                                                     1 gatew ay port
                                                                                                                                      2 gatew ay ports
                        12.000000                                                                                                     3 gatew ay ports
                                                                                                                                      5 gatew ay ports
                        10.000000
                                                                                                                                      10 gatew ay ports
              seconds




                         8.000000


                         6.000000


                         4.000000


                         2.000000


                         0.000000

                                    4.
                                      5
                                          3.
                                            5
                                                2.
                                                  5
                                                      1.
                                                        8
                                                            1.
                                                              4
                                                                  1.
                                                                    1     98   0.
                                                                                 9
                                                                                     0.
                                                                                       8
                                                                                           0.
                                                                                             7
                                                                                                 0.
                                                                                                   6
                                                                                                       0.
                                                                                                         5
                                                                                                              0.
                                                                                                                4
                                                                                                                    0.
                                                                                                                      3
                                                                                                                          0.
                                                                                                                            2
                                                                                                                                0.
                                                                                                                                  1        01
                                                                        0.                                                               0.
                                                                         change intensity [1/secs]



                                                             Average MWI synch time




65/74                                                                                       SERVICE DEPLOYMENT GUIDE
Frequently asked questions

Q1: What does MWI2007 do?

A1: MWI2007 extends Microsoft Exchange 2007 UM solution with the Message Waiting Indicator
(MWI) feature and SMS Text Messaging capabilities.

Q2: How can I buy MWI2007?

A2: MWI2007 is available for purchase through our reseller partners. If you are looking for a reseller,
please contact us at mwi2007@geomant.com. (Some of them did not contribute to show their names
on a website.)

Q3: What is the delivery method of the product?

A3: There is no physical shipping, when you order the final license file you will receive it in e-mail.

Q4: How can I install MWI2007?

A4: The installation of MWI2007 is very easy. As soon as the Exchange 2007 UM environment is
working correctly, it takes ~20 minutes to install MWI2007. To setup the MWI application, the steps
listed in the Manual installation section of the deployment guide should be performed. After the
MWI application is installed, you can test the system with 10 UM users (included in the evaluation
license). If our application satisfies your requirements, you can order licenses for the other users in
your environment through our reseller channel.

Q5: Can I change the size of the volume license?

A5: Yes, it takes just a few minutes. The reseller partners can re-generate the license files with added
licenses.

Q6: How can I upgrade the application?

A6: You have to request for the newest patch from your partner and they will provide you an upgrade
package.

Then you have to do the following steps:

        1., Stop MWI Service

        2., Create backup copies of the following folders:

                 MWIService (Located in C:\Program Files (x86)\Geomant\MWIService\ by default)

                 MWISrvAdmin (Located in C:\Inetpub\wwwroot\MWISrvAdmin)

        3., Extract the files from the following ZIPed archive to their right place by overwriting the old
        files

66/74                                                     SERVICE DEPLOYMENT GUIDE
        4., Restart the MWI Service




If you fail with any of these steps, just restore the backup-files.

Q7: What are the differences between the versions of MWI2007, when can I upgrade and how?

A7: Geomant continuously develops MWI2007 adding new features and modifying methods. The last
version includes the newest features and functions. For installing the newest version you have to
remove the previous one and reinstall the new one.

Q8: What are the minimum hardware and software requirements for MWI2007?

A8: As described in the MWI deployment guide, the hardware and software requirements are the
following:

              Processor               Intel Xeon or Intel Pentium Family (both 32 and 64-Bit) 2 GHz
                                      Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 R2 x64
              Operating System        editions; Windows Server 2003 Service Pack 1; Windows Server
                                      2008
              Memory                  1 GB RAM
              Available Disk Space 700 MB
                                      NET Framework v2.0.50727, Windows PowerShell RC2 (part of
              Software
                                      Exchange 2007 install pack), Windows Support Tools and Microsoft
              Prerequisite
                                      Internet Information Services 6
Q9: Can MWI2007 be installed on the same server where Exchange 2007 is located?

A9: Yes, MWI service can be collocated with any Exchange 2007 server roles. It can be installed on any
host in your environment which meets the minimum hardware and software requirements. Please
avoid installing the MWI application on domain controllers.

Q10: Are there any specific server requirements for MWI2007?

A10: No, MWI can run on any kind of server.

Q11: Can I install multiple instances from the MWI application?

A11: Yes, you can do that. Please read the content of the Multiple MWI service instances section of
the deployment guide. As it describes, multiple instances can be installed in order to provide MWI
service for different subsets of the UM user population. Currently, each UM user can be served only by
one MWI service instance, so there is no application level failover or load balancing.

Q12: Is there an available trial version of the software?

A12: Yes, you only have to sign the Demo License Agreement to get the password to the
downloadable software.

Q12: What is the maximum capacity of an MWI service instance?

67/74                                                      SERVICE DEPLOYMENT GUIDE
A12: The current capacity of an MWI service instance is 15.000 UM users and 50 IP gateways. Besides
the number of UM users, the most important factors which determine the MWI synchronization time
are the following: the response time of the Exchange Autodiscover service, the time required by the IP
gateway to perform an MWI request, and the number of MWI ports available. In a UM environment
with 15.000 users, where the Autodiscover response time is ~300 msecs and an MWI request is
performed within 200 msecs (e.g. Cisco CM), the average MWI syncronization time will be less then 10
secs.

Q13: Does the Geomant software support sending a message to a PBX so that an analog line
can get studdered dial tone to indicate a voice mail message has been left in Exchange UM?

A13: MWI2007 application communicates with the IP/PBX gateways and sends the MWI messages to
those. If the gateway can translate the MWI message to the “language” of the PBX, and if the PBX can
deliver the MWI message to the phone, then our application will work. We suggest you to install the
demo application and test the functionality before buying the product.

Q14: Why do I have this error message: „The system detected an invalid pointer address in
attempting to use a pointer argument in a call 10.1.210.10:5060 [3820]”?

A14: The Windows 2008 Server uses IPv6 by default, but your system needs IPv4. In order to solve the
problem, please fill the below section of the configuration file:

        <Parameter name="Local IP" value="" type="domain name">
            <glconf:Comment>Local IP address included into SIP messages.</glconf:Comment>
        </Parameter>

Q15: Symptom: the MWI related flags are cleared each time the MWI service is restarted. What
is the main reason of this strange behavior?

A15: The service stores several MWI related flags as extensionData Active Directory user attributes. If
the user account under which the MWI service is running has no permission to store data in user
objects, then this information is lost after the service is restarted. In the MWI service log, you can see
several error entries indicating that data cannot be stored in user objects. Above version 1.8.4, the
MWI service raises alarms as well.

The required permissions are described as the 4.c step of the MWI service installation process in the
deployment guide. If these permissions are granted to the MWI service account, then start the
adsiedit Windows Support tool and check the effective permissions on the user object itself. The
permission inheritance might be broken somewhere in the Active Directory tree between the
container (on which the permission is set) and the user object.

Q16: Symptom: It takes ~20 minutes until the MWI lamp is synchronized to the voice-mailbox
state. What is the main reason for this?

A16: In normal circumstances, the synchronization takes only 4-5 seconds. This situation is generally
caused by the fact that the MWI service account has no permission to use the http://*:15201/ local
URL. In this case, you can see several warning entries in the application event log on the client access
server. Each of such entries indicates that notifications cannot be sent to the MWI service.




68/74                                                    SERVICE DEPLOYMENT GUIDE
The 4.e step of the MWI service installation process (deployment guide) describes how to grant the
required permissions to the MWI service account. To check whether the permission is granted or not,
start the httpcfg Windows Support tool and execute the following command: httpcfg query urlacl.

Q17: Symptom: Regarding a given UM user, the MWI service tries to connect to an incorrect
Exchange 2007 client access server. The Unified Messaging User Properties web form also
shows an incorrect value as the Email WebService Access URL. What is the main reason for this?

A17: The MWI service communicates with the Exchange 2007 Autodiscovery service to find client
access servers. It passes the UM user's primary SMTP address to the Autodiscovery service in order to
discover the proper client access server for the given UM user. So, it is very important to setup the
Autodiscovery service before starting to use the MWI service in a production environment. Although
the MWI service is working correctly without Autodiscovery in a single domain test environment, it
needs Autodiscovery in a more complex production environment.

Q18: What data should I send when reporting faults to mwi2007 support team?

A18: The following files should be attached to the email:

                                          [MWI Service Install Directory]/Config/geomant.mwi.config.xml
                                                     [MWI Service Install Directory]/Log/MWIService.log

Q19: Which specific IP gateways, PBXs and telephony protocols are supported?

A19: As the MWI deployment guide describes we had the opportunity to test only with the following
triplets:

        AudioCodes Mediant 2000 (4.60AC.034.003D) - Avaya Definity ECS - In-band DTMF
        Cisco CallManager (5.0) - Cisco CallManager - Proprietary
        Intel PIMG80PB (platform 4 v2) - Avaya Definity ECS - SMDI
        Intel PIMG80PB (platform 4 v2) - Avaya Definity ECS - In-band DTMF

        Asterisk Trixbox 2.2 - sipX 3.8

Special thanks to AudioCodes. They have performed extensive interoperability testing with our
software and their gateway family (version 4.8 firmware). We are informed that MWI service is
functioning correctly with the following types of AudioCodes gateways and PBX environments:

        AudioCodes Mediant 2000 - Avaya Merlin Magix - T1 QSIG, In-band DTMF
        AudioCodes MP-11x - Avaya Merlin Magix - Analog, In-band DTMF
        AudioCodes Mediant 2000 - Avaya S8300 - T1 QSIG, In-band DTMF
        AudioCodes MP-11x - Avaya S8300 - Analog, In-band DTMF
        AudioCodes Mediant 2000 - Avaya Definity - T1 QSIG, In-band DTMF
        AudioCodes MP-11x - Avaya Definity - Analog, In-band DTMF

        AudioCodes Mediant 2000 - Alcatel OmniPCX 4400 - T1 QSIG, In-band DTMF
        AudioCodes MP-11x - Alcatel OmniPCX 4400 - Analog, In-band DTMF

        AudioCodes Mediant 2000 - Nortel Meridian 81C - T1 QSIG, In-band DTMF
        AudioCodes Mediant 2000 - Nortel Meridian 81C - E1 QSIG, In-band DTMF



69/74                                                    SERVICE DEPLOYMENT GUIDE
        AudioCodes Mediant 2000 - Nortel CS1K - T1 QSIG, In-band DTMF
        AudioCodes Mediant 2000 - Nortel CS1K - E1 QSIG, In-band DTMF

        AudioCodes Mediant 2000 - Siemens HiPass 4000 - T1 QSIG, In-band DTMF
        AudioCodes MP-11x - Siemens HiPath 4000 - Analog, In-band DTMF
        AudioCodes MP-11x - Siemens HiPath 3550 - Analog, In-band DTMF
        AudioCodes MP-11x - Siemens Hicom 150E - Analog, In-band DTMF

        AudioCodes MP-11x - NEC NEAX 2400 IPX - Analog SMDI (MCI)
        AudioCodes Mediant 2000 - NEC NEAX 2400 IPX - CAS SMDI (MCI)

        AudioCodes Mediant 1000 - Mitel 3300 - T1 QSIG, In-band DTMF
        AudioCodes Mediant 2000 - Mitel 3300 - T1 QSIG, In-band DTMF

        AudioCodes Mediant 2000 - Inter-Tel Axxess - T1 CAS, In-band DTMF
        AudioCodes Mediant 2000 - Inter-Tel 5000 - T1 CAS, In-band DTMF

Q20: What kind of SMS sending methods are supported?

A20: As the system manual describes, the MWI service is able to send SMS only through SMTP. It
encodes an SMS according to the MIME standard and tries to send the result to an SMTP server. The
administrator can specify the SMTP server explicitly, or can just specify a domain name. In the first
case, the MIME 'To' header is constructed as [UM user's GSM number]@[SMTP server] and the
message is sent directly to the specified server. In the second case, the MWI service tries to retrieve
DNS MX records based on the domain name and according to theirs preference numbers the service
tries to send messages through the different mail exchangers by setting the MIME 'To' header to [UM
user's GSM number]@[domain name].

Q21: How can I enable/disable MWI service for multiple UM users at the same time?

A21: After installing the MWI service, you can find the MWI Custom Command Shell tool in the
Programs menu. This tool basically starts a Microsoft PowerShell environment with the MWI related
cmdlets. Among others, there are cmdlets to enable/disable MWI service for UM users. Execute the
get-MWIHelp cmdlet or read the Command line utilities section in the MWI user manual in order to
get more details about the available functionality. To enable/disable MWI service for multiple users
you can e.g. write simple PowerShell scriplets which invoke the MWI related cmdlets. Moreover, you
can create a unified PowerShell environment where both the UM and MWI related cmdlets are
available. To do that please perform the Shell integration section in the MWI deployment guide.

Q22: Why doesn't MWI work with my Dialogic gateway?

A22: Please visit the following location

http://www.eicon.com/forums/forums/thread-view.asp?tid=367&posts=1

Announcement from Dialogic: Dialogic has identified an issue that exists when using the Dialogic
Media Gateways 1000 and 2000 (PIMG and TIMG) in conjunction with the Geomant MWI 2007
application. This condition causes an issue on the gateway where the IP side of calls starts to fail over
time. Even though the IP interface appears to be locked you can still access gateway via the web or
telnet.



70/74                                                   SERVICE DEPLOYMENT GUIDE
We are making a patch available free to all users that will fix this issue. You can follow the link
provided at the bottom of this email to get a copy of the patch.

The zip file contains 4 files:

         ami_5.1.70_36804N.app - this file is for use on the DNI (digital set) gateways only.
         ls_5.1.70_36804N.app - this file is for use on the LS (analog) gateways only.
         mtl_5.1.70_36804N.app - this file is for use on Rolm and Mitel gateways only.
         t1e1_5.1.70_36804N.app - this file is for use on the TIMG gateways only.

To use these files you must first have a gateway that has the V5.1 firmware loaded on it. If your
gateways are not currently at this level please install that upgrade before installing this patch.

V5.1 Firmware

Patch Package - 36804.zip

To install this patch simply follow standard upgrading procedures. Use the upgrade page of the web
interface, browse to the file you wish to upload, click the Install button and then reboot the unit when
prompted.

Q23: Can the MWI service be installed on virtual machines?

A23: The MWI service is supported on both Microsoft Virtual Server and VMWare machines.

Q24: Should I enable MWI service for users one by one?

A24: No. You can create a unified shell environment where both Exchange and MWI related cmdlets
are available. The required steps to setup such an environment is described in the Shell Integration
chapter of the MWI service deployment guide. In this environment you can e.g. enable/disable
mailbox, UM and MWI for an arbitrary set of users at the same time. An example Power Shell script
can be downloaded by clicking to the link below. Please read the header section in the script file
before executing that.

http://www.geomant.com/download/MWIPowerShellScript.zip

Q25: Should I grant fullaccess permission to the MWI service account on UM users' mailboxes
one by one?

A25: It is not necessary. According to the default settings, UM users' mailboxes are accessed by the
MWI service with the user credential under which the service itself is running. That is why the MWI
service account should have permission (actually fullaccess permission) on each UM user's mailbox.
Unfortunately, this permission should be granted on each mailbox one by one, since it cannot be
granted on storage group or email database level. This fact makes the configuration of the MWI
service difficult. In order to avoid this difficulty, the "Impersonate user" configuration property is
available on the Setting for Exchange Server Access web form. If this property is set to yes, then the
MWI service instructs the client access server to impersonate an UM user before accessing his
mailbox. So each UM user's mailbox is accessed by the UM user's credentials. This has the
consequence that the MWI service account should not have fullaccess permission (and basically any
permission directly granted) on the UM users' mailboxes. Instead of that, the MWI service account
should have permission to impersonate users on the client access servers and should have permission


71/74                                                   SERVICE DEPLOYMENT GUIDE
to impersonate the UM users. However, these permissions can be granted on e.g. mailbox database
level by using the following Exchange cmdlets:

         // to grant impersonation permission to the MWI service account on a given client access
         server

         Add-ADPermission -Identity [Exchange Server DN] -User [MWI Service Account] -
         extendedRights ms-Exch-EPI-Impersonation

         // to grant permission to the MWI service account to impersonate any user in the given
         mailbox database

         Add-ADPermission -Identity [Mailbox database DN] -User [MWI Service Account] -
         extendedRights ms-Exch-EPI-May-Impersonate




Q26: Why does Autodiscover fail: The remote server returned an error: (401) Unauthorized.

A26: When you get this error message:

         2007-10-09 10:47:14,583 WARN Com.Geomant.Exchange12.MWIService.Autodiscover - Error
         while trying to discover email address: abc@test.com at url:
         https://autodiscover.test.com/autodiscover/autodiscover.xml. Reason: The remote server
         returned an error: (401) Unauthorized. [2012]

Please do the followings:

    1.   Click Start, click Run, type regedit, and then click OK.
    2.   In Registry Editor, locate and then click the following registry key:
         HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    3.   If DisableLoopbackCheck field doesn’t exist Right-click Lsa, point to New, and then click
         DWORD Value.
    4.   Type DisableLoopbackCheck, and then press ENTER.
    5.   Right-click DisableLoopbackCheck, and then click Modify.
    6.   In the Value data box, type 1, and then click OK.
    7.   Quit Registry Editor, and then restart your computer.




72/74                                                   SERVICE DEPLOYMENT GUIDE
Check list
STEP 1 - MWI Service Deployment Checklist

            MWI Service installation.

            License file checking.

            Logon account checked for ‘MWI Service – Geomant’. My MWIServiceLogonAccount: ………………………………………………..

            My MWIServiceLogonAccount has write access on the MWIServiceHome directory.

            My MWIServiceLogonAccount has read access to UM configuration.

            My MWIServiceLogonAccount has read/write access to UM users data.

            My MWIServiceLogonAccount has full permission to UM users’ mailboxes.

            My MWIServiceLogonAccount has access to ASP.NET resources.

            ‘MWI Service – Geomant’ started.

            Checking for errors.

STEP 2 - WEB Interface Deployment Checklist

           Web interface installation.

           Configuration file checking.

           ASP.NET Allowed.

           The MWISrvAdmin website has ‘Script and Executables’ Execute permission.

           The MWISrvAdmin website has NOT got anonymous access.

           The MWISrvAdmin website has Integrated Windows authentication.

           The MWISrvAdmin website has NOT got Didgest, Basic and .NET Passport authentication.

           The MWISrvAdmin website uses ASP.NET 2.0.50.727 or later.

           My executing user: ………………………………………...

           The executing user has write permission on [WMIWebHome]|Log folder.

           The executing user has modify permission on Temporary ASP.NET files.

           IIS restarted if something changed at the last two steps.

           The MWISrvAdmin site checked.




73/74                                                                  SERVICE DEPLOYMENT GUIDE
Abbreviations

        ACL      Access Control List
        AD       Active Directory
        ASP      Active Server Pages
        CAS      Client Access Server
        DN       Distinguished Name
        DTMF     Dual Tone Multi-Frequency
        FAC      Feature Access Code
        FSM      Finite State Machine
        GUI      Graphical User Interface
        IP       Internet Protocol
        IIS      Internet Information Services
        ISAPI    Internet Server API
        LDAP     Light-weight Directory Access Protocol
        MIME     Multipurpose Internet Mail Extensions
        MMC      Microsoft Management Console
        MSH      Microsoft “Monad” Shell
        MWI      Message Waiting Indicator
        OU       Organizational Unit
        OWA      Outlook Web Access
        PBX      Private Branch Exchange
        PSTN     Public Switched Telephony Network
        SCM      Service Control Manager
        SDDL     Security Descriptor Definition Language
        SID      Security Identifier
        SIP      Session Initiation Protocol
        SMDI     Simplified Message Desk Interface
        SMS      Short Message Service
        SMTP     Simple Mail Transfer Protocol
        SOAP     Simple Object Access Protocol
        SRR      Service Resource Record
        TAP      Technology Adaptation Program
        TCP      Transmission Control Protocol
        UDP      User Datagram Protocol
        UM       Unified Messaging
        URL      Unified Resource Locatior
        VoIP     Voice over IP
        WebDAV   Web Distributed Authoring and Versioning
        XML      eXtensible Markup Language




74/74                                  SERVICE DEPLOYMENT GUIDE

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:25
posted:2/8/2012
language:English
pages:74