Archive

Archive for the ‘Exchange 2010’ Category

Using Exchange 2010/2013 UM for voice mail for either Lync users or legacy PBX users at the same time

November 13, 2012 Leave a comment

Exchange 2010 SP1 supports what are known as Secondary Dial Plans.

These are very useful for a situation where Exchange UM may be taking messages for Lync, but you also have users who are not on Lync, or Lync is not yet their primary phone. However, you wish to have Exchange UM be their voice mail provider, (i.e. as part of the process of decommissioning your existing legacy voicemail).

To create a Secondary Dial Plan on your Exchange UM server, do the following steps here:

  •  http://technet.microsoft.com/en-us/library/ff629383.aspx
  •  http://voipnorm.blogspot.com/2011/06/using-exchange-unified-messaging.html

Note: make sure that prior to these steps you have performed the Lync to Exchange UM integration so that Lync can act as a “PBX” to route the un-answered calls from your Legacy PBX to Exchange UM.

To enable a user for Exchange UM, and allow your legacy PBX to utilize Exchange UM, (i.e. take messages for that user’s extension), the following steps should be performed. This is for a user who has not been enabled for Lync.

  •  Have the user provide their Legacy 4/5 digit extension and AD logon
  •  Sample: Alexander Bell – AD = abell.local.ad Legacy PBX Ext: 5-2145
  •  Start the Exchange Management Console, (EMC)
  •  Locate Alexander’s mailbox
  •  Right click on Alexander’s entry and select “Enable Unified Messaging
  •  Click Browse, (for UM Policy)
  •  Select Legacy DialPlan and OK
  •  Select Next, (you may also enter their UM PIN but not necessary since Exchange will provide that PIN in an email that is auto generated)
  •  Click Next again
  •  Click Enable
  •  Instruct your telecom admin to “program” this extension on the Legacy “side” so that if a call is placed to this user’s extension, or they are on the phone, (“busy”), that it is not answered. Then needs to be routed to Exchange UM. Your telecom admin will know how to implement that routing. Just make sure to provide them with the IP address of the media gateway or Direct SIP trunk that routes to Lync. In the case of a Direct SIP, the Lync server(s) will route the transferred call to Exchange UM. This is because you will have already done the Lync/UM integration that allows Lync to route un-answered calls to UM.

 

Advertisements

Title: Exchange and Lync 2010 IM Integration with OWA

March 8, 2012 Leave a comment

Jeff Schertz has an extremely useful article on his blog that provides the steps needed to add Lync IM integration, (aka CWA from OCS R2) to your OWA users: http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/

During a recent deployment for Lync it was discovered that if the “InstantmessagingEnabled” attribute is already set to “true”, then when you run the Exchange PS CmdLet described in Jeff’s blog you will get an error message that appears to be complaining about parameter syntax not being correct. 

If you come across this situation there is a simple and easy work around. All you need to do is break out the Set-OwaVirtualDirectory statement in to several individual Set-OwaVirtualDirectory statements. If you issue the –InstantMessagingType line as shown below with the attribute set you will get a warning from PS indicating that the value is set. Executing the other three PS Cmdlets will result in the setting of the required attributes as described in Jeff’s blog.

If you need to quickly see which of the InstantMessaging attributes set issue this Cmdlet:

Get-OwaVirtualDirectory | fl instant* [From the CAS Server]

Example of breaking out the PS Cmdlets for setting the InstantMessaging attributes:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingType OCS
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled:$true
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingCertificateThumbprint 851588624951A8181DAB0CB6A52C19AC4C15DFA4
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingServerName lab1ls.csmvp.net

Thanks to David Sayer at Dell for helping discover this tip.

Categories: Exchange 2010, Lync

Forrester Exchange 2010 Case Study

June 29, 2010 Leave a comment
Categories: Exchange 2010