Microsoft Lync 2010 Custom Status Update

We dont have a lot of guides out there helping with a step by step guide for the migration and coexistence of Exchange 20102007 to. Microsoft Office is an office suite of applications, servers, and services developed by Microsoft. It was first announced by Bill Gates on 1 August 1988, at COMDEX in. Configuring Lync Server 2. Remote Call Control with Mitel 3. Remote Call Control on Lync is still a bit of a dark area. Everything in the server product remains in terms of configuring RCC, but getting it going is a bit of a different story. There is very little PBX vendor advice around regarding support of RCC in Lync with their PBXs although Cisco updated their interoperability statement recently. Plus there are some shortcomings on the client side that will make or break your RCC deployment. One of the biggest pain points is the complete lack of any video capability when Remote Call Control is configured. This will cause dramas for lots of organisations looking to leverage the desktop video capabilities in Lync. Manual/Cawthorne/En/VCC-Voxtron_Client91/VC-Int-MSLync/VC-Int-MSLync_files/image035.jpg' alt='Microsoft Lync 2010 Custom Status Update' title='Microsoft Lync 2010 Custom Status Update' />More on this from Jason Sloan. Im going to dive straight into the thick of it here and concentrate on getting RCC working with a Mitel 3. ICP PBX and what vendor specific things you need to do in Lync. I will touch on the Power. Shell cmdlets to get RCC going in Lync, but for more generic details on how RCC is configured in Lync, check out these otherblogposts. Backyard Football 2008 Free Download For Computer. Infrastructure Requirements. At a high level, here are the basic bits and pieces youll need to get this running. Microsoft Lync 2010 Custom Status Update' title='Microsoft Lync 2010 Custom Status Update' />Active Directory. A functioning Lync Server 2. Environment consisting of at least one Standard Edition Server or an Enterprise Edition Front End Pool and Lync clients. A Mitel 3. 30. 0 ICP IP Communications Platform and Mitel handsets. A Mitel Live Business Gateway. When approaching this kind of integration, you should have an engineer on hand familiar with the Mitel PBX so they can configure the 3. ICP to work with the LBG and outboundinbound digit modification on the LBG. Configuring the Mitel Live Business Gateway. Now lets take a look at the somewhat tricky part configuring the LBG. Heres where youll want to have your Mitel man at the ready to give you a hand, mainly in the configuration of the ICP side of things. Firstly, open up Mitel Business Gateway from Control Panel. This tab will display the IP address of the machine and the SIP port the LBG will use. Unless you have a strict business requirement to encrypt internal communications, dont select TLS this is a big headache, involves lots of stress with certificate, something Ill cover in another post. Next, click the ICP tab. Heres where you specify the Mitel 3. PBX nodes aka ICPs that the LBG will talk to. Specify the IP address of the ICP and the Remote CC URI this is what will become your Line Server URI in Lync should be something like lbghostname. Next, specify the username and password to connect to the Mitel 3. Add. Next click the Licensing tab. Here you need to put in your Service Link ID from Mitel to license your users for RCC using the LBG. Now click the Active Directory tab. You need to configure the LBG to talk to AD so it can check if users are setup with phone numbers that they are attempting to remotely control with Lync. Specify the FQDN of a domain controller, then the username you want to use to query AD and the password and click Add To List. You can add additional DCs for redundancy. Under the ODM and IDM tabs, you can configure how numbers are modified on outbound and inbound calls so you can normalise incoming numbers from, for example only 4 digit extensions to full E. AD user accounts. Finally, on the Log tab, you can setup the log level that will be captured for diagnosis purposes. Once youre all done, return to the Live Business Gateway tab and click the button at the button labelled Start. Configure Lync Server for Remote Call Control. As I mentioned above, configuring the Lync server infrastructure for RCC is a bit different from previous versions. Everything is done in Powershell now, so those familiar with Routing and Authorised Hosts tabs in the OCS 2. R2 GUI will need to pay attention here. Setting up routes and trusted applications. To configure remote call control with Mitel, the following Powershell cmdlets will be run using Lync Server Management Shell on the Lync Front End server. Pardini Sp User Manual'>Pardini Sp User Manual. Replace server FQDNs and IP addresses with your own. Create a new Trusted Application Pool for the Mitel LBG. New Cs. Trusted. Application. Pool Identity mitel lbg. Registrar lyncfe. Site 1 Treat. As. Authenticated true Throttle. As. Server true Requires. Replication false. Create a new Trusted Application which is bound to the Application Pool created in the previous step. New Cs. Trusted. Application Application. Id RCC Trusted. Application. Pool. Fqdn mitel lbg. Port 5. 06. 0 Enable. Tcp. Create a variable called tcp. Route that defines the static route to the IP address of the Mitel LBG when the Server URI is matched. Route New Cs. Static. Route TCPRoute Destination 1. Port 5. 06. 0 Match. Uri mitel lbg. justin morris. Configure the Lync Static Routing Configuration with the new route specified in the previous step. Set Cs. Static. Routing. Configuration Route Addtcp. RouteEnable the modified Lync Server Topology. Enable Cs. Topology. The topology will then need to be exported to XML and a manual workaround applied specific to integration with Mitel. Note that this is NOT RECOMMENDED by Microsoft to EVER manually modify the topology document, but it is required to get RCC working with Mitel in Lync. Test this in an isolated environment before making changes to your production environment. Run the following command to export the topology to XML Get Cs. Topology As. Xml Out File c rcc. Open the rcc. xml document and find the line that refers to the Mitel LBG e. Cluster Fqdnmitel lbg. Requires. Replicationfalse Requires. Setuptrue lt Cluster. Id Site. Id1 Number3 lt Machine Ordinal. In. Cluster1 Fqdnmitel lbg. Net. Interface Interface. SidePrimary Interface. Number1 IPAddress0. Machine lt Cluster Modify the IPAddress field from 0. IP address of the Mitel LBG e. Save the file and exit. Next, publish the modified Lync Server Topology to the CMS. Publish Cs. Topology File. Name c rcc. xml. User Configuration. For each user you want to setup for RCC, go into their account details in the Lync Server Control Panel. From the Telephony drop down menu, select Remote Call Control. Configure them with a Line. URI that looks like this tel 4. And a Line Server URI that looks like this sip lbgmitel lbg. So in the GUI, it should look like this once configured Once youve filled this in, hit Commit. Additionally, each user needs to have the extension field e. AD account in a Telephone field for example so the Mitel LBG can see that the users is setup for that phone number. Configuring each Lync Front End Server to listen on Port 5. Finally, we need to configure our Lync Front End Server to listen on port 5. SIP TCP so it can receive traffic from the Mitel LBG. We do this by running the following cmdlet from Lync Server Management Shell Set Cs. Registrar Registrar lyncfe. Sip. Server. Tcp. Port 5. 06. 0Hat tip to Tom Pacyksblog post for this one again, the guy comes up with the goods. Troubleshooting connectivity on the LBGIf RCC doesnt work straight off the bat for you, you can troubleshoot connectivity by opening the Log Viewer application on the LBG. Navigate to C Program Files x. Mitel NetworksLive Business GatewayTools and open MSPlogs. First, click File then click Connect to MSPLog FileNext, navigate to the Logs directory under Mitel NetworksLive Business GatewayLogs and select appgw.