It has been a while since the last tutorial, so it gets time to publish a new one. This one will inform you about the new functionality that’s included in Exchange 2010 SP1 beta and then specifically the Unified Messaging role.
Have fun reading it:
Gepost in Exchange 2010 ~ Geen Reactie
In Exchange 2010 SP1 beta you will find a lot of changes. In this tutorial I will have a closer look at the Unified Messaging Role from Exchange 2010 SP1.
Before starting the installation of the UM role you will need to ensure that you have installed the two prerequisits mentioned below:
This is one of the new things in Service Pack 1, in the RTM version this was not necessary. In RTM you only needed to install the prerequisits using the Excahnge-UM.xml file. The files mentioned above are additional to this. Please pay attention when installing the Unified Communications Managed API 2.0 it might look the installation is done very quickly. But what is only done during the installation is extracting the files to C:\Microsoft UCMA 2.0 RuntimeInstaller Package\amd64 here you can find the file SetupUcmaRuntime which does perform the installation of UCMA 2.0.
After the files have been installed you can start the installation of Exchange and select the Unified Messaging Role. Besides selecting the Unified Messaging Role don’t forget to place a checkmark before automatically install Windows Server Roles and Features required for Exchange Server. This new option will install all Windows Server Roles and Features necessary for the installed Exchange role.
Once installed it’s time to start the Exchange Management Console and selecting the UM Server which can be found under the organizational configuration tree. On the organizational configuration level you can configure the following things:
Let’s begin with creating the dial-plan. First we need to specify the name, the length of the extensions, URI type, VOIP Security and Country/Region code. Depending on what kind of implementation you are performing you might chose other options for the URI type and VOIP security. In this case the dial-plan will be used to attach the Exchange UM server to an OCS 2007 R2 environment.
In the next step we will need to add the servers attached to the dial-plan. In this case it’s only one server but in an environment where you’ve got multiple UM servers you can easily add them all here.
Before the dial-plan is created you will get an overview of the settings which will be used. When pushing the New button the dial-plan will be created.
When the dial-plan is created you will see a warning. This warning is the result of the default configuration of the UM server. The UM Server is default configured to accept traffic using TCP. Since we configured the dial-plan to accept only traffic which is secured we will need to modify this option on server configuration level so that the server will accept TLS traffic.
After the wizard has been closed you will need to get the properties of the dial-plan to configure the subscriber-access. This feature can be used by users to call their mailbox to, for example, check if new mails have arrived. Once you get the properties of the UM server select the subscriber access tab and add the extension which you would like to use fot this functionality.
Next step in the process is to add the gateway to which the Exchange UM server will need to send it’s traffic to.
We will only need to specify a name, IP-address of FQDN of the gateway and the dial-plan which may use this gateway.
During the creation of the gateway a hunt group will be automatically created. In some cases it may be necessary to remove the hunt group and create a new one. This because the pilot identifier will not be configured by default. If want to skip the creation of the hunt group don’t select a dial-plan and attach the gateway manually to the dial-plan.
Default a UM Mailbox policy will be created during the creation of the dial-plan. With this policy you may not have to change things as the settings are OK for your organization. But if you like to make changes to the text of the message which is send to the users when they are UM enabled then modify the policy.
Beside the text there are a lot of other settings which are defined by this policy. For example the pin policies which you would like to apply to users: complexity, minimum pin length and wrong pin attempts.
Optional it’s possible to configure an auto attendant. This is an electronic operator which can transfer calls and play a menu to the caller with options which will transfer him/her to the correct department.
The configuration at organizational configuration level is finished and so it’s to configure some things on server configuration level. Get the properties of the UM server and select the UM Settings tab. Change the value of the startup mode to TLS or Dual and press OK.
A warning will be displayed that the Exchange UM service will need to be restarted and that you will need to verify that a valid certificate is assigned to the service. The certificate is important because we selected secure at the dial-plan. This will ensure that all traffic is secured using certificates for authentication. If an invalid certificate is used by one of the parties the communication will fail.
If you decide to install the certificate later then you may have some issues with restarting the Exchange UM service. This because the self-signed certificate is not assigned to the Exchange UM service.
Configuring UM can be dan a lot easier when using Powershell. Below you will find an overview of commands which you can use to create the configuration exactly as done via the GUI:
New-UMDialplan -Name Utrecht -UriType SipName -NumberOfDigitsInExtension 3 -VoIPSecurity Secured -AccessTelephoneNumbers “110″ -CountryorRegion 030
New-UMIPGateway -Name “Utrecht VOIP Gateway” -Address 192.168.1.250 -UMDialplan “Utrecht”
New-UMAutoAttendant -Name Utrecht_AA -UMDialPlan Utrecht -PilotIdentifierList ”+313012345100″ -SpeechEnabled $true
Set-UMserver -identity “ex” -DialPlans “Utrecht” -UMStartupMode “TLS”
If you like Powershell then I recommend to use it because configuring UM goes a lot faster.
New in SP1 are two additional expensions for the UM role, these can be found under tools in the Exchange Management Console:
First the call statistics, this report utility can be used to generate overviews of calls which are processed by your Exchange UM server. This may be very usefull when you would like to get an overview of how much users will use the UM functionality of Exchange.
Besides to the overall overview you can generate reports per user using the user call log. In this overview you can for example see how much calls a user receives and which quality the call was. This may be very usefull when troubeshooting the quality of calls
But what are the other changes in SP1 when looking at UM:
Remark: all features and screenshots mentioned in this article are based on the beta of SP1 and may change in the final release.
Gepost in ~ Geen Reactie
If you are troubleshooting an issue some logging is really usefull. On the UM server diagnostic logging is enabled by default on the lowest level. In case you need to have more logging you should manually change it to a higher level.
Changing the logging level can be done in two ways:
The first method is really simple
When you don’t want to change things in the registry yourself you can also do it via the Powershell, for example:
This command will change the logging level for the UMService, other valid parameters are:
When you want to know what the current logging level is you need to execute the following Powershell command:
Get-EventlogLevel “UM01\MSExchange Unified Messaging”
Gepost in Exchange 2007 ~ Geen Reactie
Such as most products have, the setup from Exchange 2007 can be made unattented. This can partitially be done by specifying parameters after the setup command.
The first parameter, if you have your forest and domains prepped, is mode, with this parameter you can specify the mode setup will be running in: install, uninstall, upgrade or recover.
/mode:install
/mode:uninstall
/mode:upgrade
/mode:RecoverServer
The next parameter is role, with this parameter you can specify which rol(es) need to be install(ed) on the server:
/role(s):HubTransPort, HT, H installs the HUB Transport role
/role(s):ClientAccess, CA, C installs the Cient Access role
/role(s):MailBox, MB, M installs the HUB Transport role
/role(s):UnifiedMessaging, UM, U installs the Unified Messaging role
/role(s):EdgeTransport, ET, E installs theEdge Transport role
/role(s):ManagementTools, MT, T installs the Management Tools
It is possible to combine the parameters, for example:
/roles:H,C,M,T
The parameters above will install the Hub Transport, Client Access and Mailbox rols + the management tools.
Besided the parameters already mentioned you can give up several other parameters for example to change the install directory, below an overview of a few of them:
Besides the already mentioned parameters there are parameters for preparing the forest and domain for Exchange 2007:
Besides all the parameters mentioned there are a lot of more parameters that you can use, a full overview can be found on this site.
Gepost in ~ Geen Reactie
Search the archives door entering keywords or topic strings.
Titanium de codenaam was voor Exchange 2003
|
|
| Pagerank |
