|
This FAQ page provides you with the most frequently asked questions about MWI2007. If you can't find the answer you're looking for, please email us at mwi2007@geomant.com with your question. Thank you. Last Update: 16/07/2007 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. For a list of available partners please see the Partners section. Q3: How can I install MWI2007? A3: 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. Q4: Can I change the size of the volume license? A4: Yes, it takes just a few minutes. The reseller partners can re-generate the license files with added licenses. Q5: How can I upgrade the application? A5: You have to request for the newest patch from your partner. Q6: What are the differences between the versions of MWI2007, when can I upgrade and how? A6: 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. Q7: What are the minimum hardware and software requirements for MWI2007? A7: As described in the MWI deployment guide, the hardware and software requirements are the following:
Q8: Can MWI2007 be installed on the same server where Exchange 2007 is located? A8: 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. Q9: Can I install multiple instances from the MWI application? A9: 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. Q10: What is the maximum capacity of an MWI service instance? A10: 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. Q11: Symptom: the MWI related flags are cleared each time the MWI service is restarted. What is the main reason of this strange behavior? A11: 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. Q12: Symptom: It takes ~20 minutes until the MWI lamp is synchronized to the voice-mailbox state. What is the main reason for this? A12: 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. 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. Q13: 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? A13: 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. To setup Autodiscovery please use the document Setting Up E12 Autodiscover. This document is included in the MWI documentation package. Q14: What data should I send when reporting faults to mwi2007 support team? A14: The following files should be attached to the email:
[MWI Service Install Directory]/Config/geomant.mwi.config.xml Q15: Which specific IP gateways, PBXs and telephony protocols are supported? A15: 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 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 Mediant 2000 - Alcatel OmniPCX 4400 - T1 QSIG, In-band DTMF
AudioCodes Mediant 2000 - Nortel Meridian 81C - T1 QSIG, In-band DTMF
AudioCodes Mediant 2000 - Siemens HiPass 4000 - T1 QSIG, In-band DTMF
AudioCodes MP-11x - NEC NEAX 2400 IPX - Analog SMDI (MCI)
AudioCodes Mediant 1000 - Mitel 3300 - T1 QSIG, In-band DTMF
AudioCodes Mediant 2000 - Inter-Tel Axxess - T1 CAS, In-band DTMF Q16: What kinds of SMS sending methods are supported? A16: 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]. Q17: How can I enable/disable MWI service for multiple UM users at the same time? A17: 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. Q18: Why doesn't MWI work with my Dialogic gateway? A18: 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. 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. 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. 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. Q19: Can the MWI service be installed on virtual machines? A19: The MWI service is supported on both Microsoft Virtual Server and VMWare machines. Q20: Should I enable MWI service for users one by one? A20: 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 Q21: Should I grant fullaccess permission to the MWI service account on UM users' mailboxes one by one? A21: 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 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] -extendedRight 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] -extendedRight ms-Exch-EPI-May-Impersonate -InheritanceType none
Or you can simply run the following script on Exchange Management Shell: Get-MailboxDatabase | Add-ADPermission -User DOMAIN/MWISERVICEUSER -extendedRights ms-Exch-EPI-May-Impersonate -InheritanceType none Get-ExchangeServer | Add-ADPermission -User DOMAIN/MWISERVICEUSER -extendedRights ms-Exch-EPI-Impersonation -InheritanceType none |
