Mino – The UC Guy

Microsoft Unified Communications Blog

Archive for the ‘Lync 2010 Client’ Category

Lync by LINK , Full Lab Setup at Microsoft Egypt premises

Posted by Mino on November 16, 2010

Last week we built Lab setup for Lync at Microsoft Egypt premises , Fady Eskander from our technical team in LINK Development was responsible for it and I was helping. The aim of this setup was to showcase Lync up and running fully featured but more from the end user  experience .

For this we simulated 6 different types of users , each on his desk with different endpoints even for the same user. I can tell you that whoever walked in that room to give it a try was really impressed and mostly with the wide range of endpoints and how flexible it is to just unplug and plug devices between different users … Yes Lync rocks and that’s a Fact .

I just thought to share with you some photos of the setup , excuse us if it was not yet clean but these shots were taken at the testing stage and not the final one 🙂

For our setup we used the following :

  • IBM Server ( 24 GB RAM ) , holding all VMs ( DC, Exchange, SQL , Lync FE , Lync Monitor, SharePoint)
  • 6 Notebooks ,for 6 types of users where each is on his desk
  • NET media gateway , VX1200 mainly for the SIP server built in on that box. we used SIP to register non Lync sip phones and also we used it for Nokia & Blackberry phones to make Wifi VOIP calls through SIP clients ( Ooooh that was really worth testing )
  • NET media gateway , Tenor AF mainly for FXS and FXO ports . we connected Old Analog phone ( my favorite Old Phone 🙂 )
  • Ericson PrimaCell gateway , this is a GSM gateway where u just put your mobile SIM card and connect it on FXO port. we used it to place inbound and outbound calls ( very useful for moving demos , u don’t need to ask the client for testing line )
  • Polycom Phones ( CX700 , CX500 , VVX ,RoundTable  )
  • Aastra Phone (6725ip)
  • Plantronics endpoints (Savi W430-M Bluetooth , Blackwire C420-M USB headset ,Calisto P420 USB speaker ,Calisto P210-M USB handset)
  • Jabra endpoints ( Jabra GO™ 6400 , Jabra GN9300e , Jabra M5390 )
  • Microsoft Web Cams ( HD Cams & 2MP Cams )

Now I can leave you with the photos


This user got Polycom CX500 , also 2 Plantronics endpoints ( External Speaker ) , ( Bluetooth headset )


This user got Aastra phone , Polycom ( RoundTable ) ,also connected to it Plantronics Savi W430-M( Bluetooth headset ) , ( Handset lifter ) Oooh that lifter really looked cool when you answer the calls through the Bluetooth headset it just lifts the handset up to pickup the call and once you finish it places it back down..


This user simulated the call center agent , he is part of Lync response group which we created for helpdesk. as an agent he is using Polycom ( CX300 ) USB phone and connected to it is Plantronics Blackwire C420-M ( Headset )


This user got Polycom ( CX700 ) touch screen phone with Lync firmware installed , also connected to it is Jabra GN9300e  (Bluetooth headset )



This user is using Polycom Video phone ( VVX ) , this phone is not optimized to Lync usage however it is registered through SIP over the media gateway and also it can provide point to point video calls. The user also is using Plantronics Calisto P210-M ( USB handset )


This is just to show you the round table on full screen , the quality is really great and I wanted so much to give it a try on Plazma screen.


And Finally , the backstage setup with the Macaroni cables 🙂 . yes we all know that look and somehow we got used to it.

Lync launch is tomorrow and I am so excited for it just like all of you , cuz I know its gonna be a great year and we will definitely give hard time for Cisco and Avaya ….Booo 🙂

Posted in Lync 2010 Client, Lync Phone, Lync Server 2010, Lync Telephony | Tagged: , , , , , , , | 9 Comments »

Lync Voice Deployment User Experience Comparison

Posted by Mino on November 11, 2010

During a very recent engagement with Microsoft Corp. competition team , they shared with me a new customer ready document for Lync voice deployments user experience comparison and I took the permission to share it on my blog.

There are three primary deployment scenarios for Microsoft® Lync™ Server 2010 customers. The three options, which differ in the user capabilities provided and the required infrastructure, are:

· Replace PBX phones with Lync to improve communications and collaboration, and to reduce infrastructure costs. This is the preferred Lync deployment scenario as it allows customers to simplify their communications infrastructure and rely exclusively on Lync Server 2010 for voice, conferencing, instant messaging and presence.

· Enhance PBX phones with the option to use Lync to improve communications and collaboration. This scenario is useful for organizations that are not yet ready to remove their existing PBX systems, but who want to provide their users either with the option to use Lync for phone calls instead of their PBX phone, or with the option to control their PBX phone with the Lync desktop client. The former approach is useful for providing seamless communications for employees working at home and on the road, and as a transitional approach while PBX systems are amortized and decommissioned. The latter approach is useful for providing desktop “Click-to-call” capability with existing PBX phones.

· Add instant messaging, presence, and conferencing to existing phone capabilities.This scenario is useful for customers that want to add Lync capabilities other than enterprise voice.





1. Entries marked “*” in the “Enhance, using Lync as phone” column apply when the user uses the Lync soft-phone only, not the PBX phone. Using the soft-phone in this scenario is the Lync default.

2. Entries marked “+” in the “Enhance, using Lync to control PBX phone” column apply when the user uses the Lync soft-phone only, not the PBX phone. Usng the soft-phone in this scenario requires that the user manually select “Lync call” in a drop-down menu each time a call is initiated.


As shown in the table above, with the Replace option, Lync is the only communications system used and provides the full set of unified communications capabilities to users inside and outside the office. With the Enhance option, users have both Lync and a PBX phone, and choose which phone to use at any given time. When Lync is chosen as the primary phone, as in the “Enhance, using Lync as phone” variant, users have the full set of unified communications capabilities inside and outside the office; when the PBX phone is chosen as the primary phone, as in the “Enhance using Lync to control the PBX phone” variant, users have a rich but reduced set of unified communications capabilities.


The Replace, Enhance, and Add options enable organizations to standardize on Lync as the only desktop software client for real time communications, but require different supporting infrastructure. In particular:

· The Replace option allows customers to eliminate separate PBX and conferencing systems and the associated user databases and management tools in favor of Lync Server, Active Directory, PowerShell, and Systems Center Operations Manager. This enables significant capital and operational cost savings, and takes advantage of existing skills in these areas.

· The Enhance and Add options require ongoing maintenance of existing PBX systems until those systems are retired. They also require the interconnection of the existing PBX systems with Lync Server, using Direct SIP or a third party gateway qualified via the Unified Communications Open Interoperability Program.This interconnection enables calls to be carried between Lync Server and the PBX systems.

The Enhance, using Lync to control the PBX phone additionally requires the deployment and maintenance of a connection to the PBX. This connection may require a PBX software upgrade and per user PBX software license fees, depending on the PBX manufacturer, and requires associated configuration and management.


The table below summarizes the key infrastructure differences for the deployment options.


As shown in the table above, the Replace option requires the minimum amount of infrastructure. This enables significant cost savings for organizations: for example, Sprint projects annual savings of over $9 million based on its replacement of nearly 500 PBX systems with Microsoft unified communications technology.

Posted in Lync 2010 Client, Lync Server 2010, Lync Telephony | Tagged: , , , , , , , , , | 1 Comment »

Lync Server 2010 Media Traffic Network Usage

Posted by Mino on November 5, 2010

“This is RTM pre-release documentation information and subject to change in General Availability (GA) release by December 2010 , I will update this post if any changes are required ”

When planning for media bandwidth usage per scenario, use the following tables, which describe the average amount of bandwidth used per media type.

Audio/Video Capacity Planning, Peer-to-Peer Sessions


Audio/Video Capacity Planning, Conferences


Audio Capacity Planning, PSTN


The network bandwidth numbers in these tables represent one-way traffic only and take silence suppression into account.

When you calculate the actual bandwidth usage for a certain scenario, it is important to understand the actual media flows, which are as follows:

In a two-party scenario:

  • Users send audio streams only while they speak.
  • Both participants receive audio streams.
  • If video is used, both users send and receive video streams during the entire call.

In a Conferencing scenario (that is, a call with more than two participants):

  • Users send audio streams only while they speak.
  • All participants receive audio streams.
  • If video is used, only two participants upload a video stream at a time (that is, the active speaker and the previous active speaker
  • If video is used, all participants receive video streams.

Posted in Lync 2010 Client, Lync Server 2010 | Tagged: , , , , | 6 Comments »

PowerShell Script to create new user, enable for Exchange, UM and Lync Server

Posted by Mino on October 31, 2010

RANDY WINTLE created this PowerShell as a sample of how to create new user, enable for Exchange, UM and Lync Server

There are a couple good takeaways from this script, it remotes into Exchange 2010 and Lync Server 2010 PowerShell sessions, so nothing except PowerShell 2.0 is required on the client side, which is standard with Windows 7. It also shows how you can simultaneously use Exchange and Lync PowerShell commands in the same script to get things done.

This was developed specifically for my internal needs, you will probably have to add/remove variables and requirements.


Posted in Lync 2010 Client, Lync Server 2010 | 2 Comments »

How to Enable HD Video for Lync 2010

Posted by Mino on October 28, 2010

Copied from the below Blog


One that might save a little bit of time for those folks wanting HD video for peer to peer calls between Lync clients…
You have to allow the maximum resolution to support HD 720p video – to do this you need a specific powershell cmdlet. Here’s how:

Set-CsMediaConfiguration -Identity:Global -MaxVideoRateAllowed HD720p15m

Restart the Lync Front End service and video calls can now utilise any 720p webcam that’s attached to the client.
So now you can see your colleague’s face in all its blemish free glory!

Posted in Lync 2010 Client, Lync Server 2010 | Tagged: | 6 Comments »

How to allow domain users to connect to Lync 2010 or OCS 2007 from Clients running on non-domain computers

Posted by Mino on September 15, 2010

I had a situation in our company where we have exceptional few users who got Domain credentials but they are working on Computers that are not joined to the domain.

However these computers run over the LAN or WAN, can communicate with the internal DNS and got the certificate chain of the CA imported to them and they use DOMAIN\UID and password credentials to login to mail , MOSS and everything is working fine.

When I installed the OCS 2007 R2 client on their machines and tried to login with the same behavior as mail using DOMAIN\UID , I was not able to log in and I received the below event log warning:

"Communicator was unable to authenticate because an authenticating authority was not reachable.”
The server may be asking for Kerberos authentication and Communicator is not able to find the Kerberos Domain Controller in order to generate credentials and authenticate.  The network administrator will need to change the configuration on the server to utilize only NTLM authentication before Communicator can login from this location properly, or connectivity will need to be made available to an authenticating authority"


also as for testing I removed the OCS 2007 R2 client and installed the new Lync RC client on the same machine , I know it is not supported scenario but I was just testing it. Now the user was able to login but it disconnects after 10 seconds then reconnects again , it keep in this loop. I also found the same warning in the event log.

I know why this is happening and I know it would have been solved from the beginning if i forced the OCS to use NTLM only rather than Kerberos but this was not something i can force.

So in the end the Solution was this problem was simple :

Ensure that the users when singing in to communicator 2007 or Lync 2010 to include the ".local" in the domain.local\username part of the authentication and not DOMAIN\username.

Posted in Common Errors, communicator client, Lync 2010 Client | Tagged: , , , | 3 Comments »

Microsoft Lync Server 2010 Media Bypass

Posted by Mino on September 14, 2010

What is it?
  • Media Bypass allows for Lync clients to communicate directly with a qualified PSTN voice gateway or qualified IP-PBX without traversing the Mediation server for media transcoding

  • When clients use Media Bypass, the Lync client uses the G.711 codec over SRTP

What are the benefits?
  • Greatly simplifies topology
    • Allows for Mediation server to collocate with Front End server or SBA because of low CPU intensity
    • Greatly reduces the amount of servers needed in deployment resulting in lower TCO
  • Optimizes media flow and quality
    • Eliminates unnecessary hops and potential points of failure
    • Saves WAN bandwidth
    • Improves voice quality with use of G.711 codec

However to enable Media Bypass ,you must ensure that either the Media Gateway ( SBA ) or the IP-PBX does support the Media Bypass feature.

Below are some different scenarios for the Media bypass between 2 sites:

First Scenario :

In this scenario the Client in the main data center dials a PSTN number, so the client communicates directly with the gateway using G.711 codec without the need to used the mediation for transcoding from RTaudio to G.711 Codec.


Second Scenario :

In this scenario the client is located in the branch site where there is no Lync Servers installed , when the client places a PSTN call it communicates directly with the IP-PBX over G.711 without the need for getting back to the Data Center pool mediation for transcoding. However this scenario is only applicable if your IP-PBX does support the new Media Bypass feature.


Third Scenario :

In this scenario we have two clients placing the call , one from the Data Center and the second is in Branch site. you will typically have this case in the international sites where you want to enable the least cost routing for international numbers. Lets say the Main Data Center is in US and the branch Site is in Egypt , and both Clients will dial the same number which is a US number.

So the first client who is in the US data center will communicate to the mediation server directly over G.711 , then the mediation will place the call through the Hosted SIP trunk to the PSTN also over G.711 since there is no local PBX available in the Data Center.

The Second Client who is in the Egypt branch site will dial the US number , the client will communication with the Mediation server place in the US Data center over RT Audio then the mediation will talk to the PSTN over G.711. In this second scenario we used RT Audio because it has got lots of features over the G.711 which consumes more bandwidth  , RT Audio gives much better quality over WAN due to correction mechanisms and the ability to overcome lost packets.


Forth Scenario :

In this scenario we have the same case like the last one , however we have also enabled Call Admission Control ( CAC ) which is a new great feature in Lync Server 2010. It allows call control over WAN to assure the accepted number of call over the allocated bandwidth and to refuse any extra calls over the allowed limit . What makes this CAC feature great also is not only to control calls over the WAN , but also to give alternate route for calls over the PSTN rather than using the WAN.

Ok let me explain it , the Client in the Egypt branch site is placing an international call to US number , so the client tries to place the call through the mediation placed in the US data center over the WAN , however due to WAN full usage and the CAC control ( call admission control ) so the call is not allowed to be placed over the WAN , however in spite of dropping the call we find that the client is redirected with alternate route to his local GW to place the call as international number from his PSTN gateway.


Fifth Scenario :

In this scenario the Client who is placed in the branch site places a call to a PBX legacy endpoint which is placed in the main site data center , this endpoint is connected to the IP PBX where this IP-PBX does not yet support direct Media bypass.

So the Client communicates over the WAN to the mediation server over RT Audio , then the call is routed after transcoding from the Mediation to the IP-PBX over G.711 , and finally the IP-PBX sends the call to the end point directly over G.711.


Posted in Lync 2010 Client | Tagged: , , , , , | 6 Comments »