Tag Archives: Lync Mobile

Using an iPod Touch as a Wi-Fi #Lync endpoint i.e. “DECT replacement”

At the MCSM I needed an extra Lync endpoint and I had talked with a customer earlier about the possibility to use a iPod touch as a cheap DECT replacement.

So I wanted to test it and its been a great device for Lync, however I did not test it “live” yet but rather answering some (20+) of my calls (both voice and video) at home from the iPod rather than answering from Lync on the PC.
But I need to test it more with regards to how far I can walk out from my WIFI Access Point and how it handles WIFI roaming between access points (cant test that at home though)

Anyway, so far the call quality is great, video is great when watching on the iPod but sending is not great but well over OK (if not maximized on the receiving side it really looks ok but full screen can be worse, still watchable though).
Since its WIFI only it should really not be that much to worry about I figured, at least not when using it for some controlled testing.

But why not use an iPhone? well, one thing – money! The price on an new iPod is something like 250$ and the use case here is as an extra endpoint for the receptionist or as the title said, to replace DECT phones. And one good thing with the apple stuff is the endless flora of accessories so if you want it rugged, or waterproof or use it as a credit card reader or a scanner in a warehouse etc. you could use it for that as well.

One thing to notice though is that the iPod does only have an built in speaker and not the first speaker like a phone has, that you can put to your ear, so its just the speaker meaning that like the only practical way of using it, is with a Bluetooth headset.


I have used it together with a Plantronics Blackwire C720-M but any Bluetooth headset would work.

So my setup looks like this. The Blackwire is connected to my Windows 8 PC and then connected to the iPod via Bluetooth.



One cool thing with the Blackwire is that it can be disconnected from the pc so if I need to walk away I just keep the headset on and disconnect it at the volume controller.



Another cool thing is to use the iPod with an Apple TV and instead of a Bluetooth headset use a wireless speakerphone like the Plantronics Calisto 620 and then do Airplay mirroring over to a TV / Projector!



Tech specs Blackwire C720-M http://www.plantronics.com/us/product/blackwire-700?skuId=sku6120014

  • Talk time: Up to 10 hours, up to 10 days standby time, up to 6 hours listening time (A2DP)
  • Wireless frequency: Bluetooth v2.1 + EDR
  • Audio performance: Dynamic EQ, microphone frequency response 100 Hz–8kHz optimal for wideband voice telephony (up to 6,800 Hz), hi-fi stereo output from 20 Hz–20 kHz (C720 only), enhanced digital signal processing (DSP), noise-canceling microphone, A2DP

Tech specs iPod Touch:  http://www.apple.com/ipod-touch/specs.html

  • 802.11a/b/g/n Wi-Fi (802.11n 2.4GHz and 5GHz)
  • Bluetooth 4.0
  • 4-inch (diagonal) widescreen display with Multi-Touch IPS technology
  • Retina display
  • 1136-by-640-pixel resolution at 326 pixels per inch
  • FaceTime HD camera with 1.2MP photos and HD video (720p) up to 30 frames per second
  • 5-megapixel iSight camera
  • Autofocus
  • 3.5-mm stereo headphone jack
  • Built-in speaker
  • Microphone
  • Music playback time: Up to 40 hours when fully charged
  • Video playback time: Up to 8 hours when fully charged
  • Charging times: Fast charge in about 2 hours (80% capacity), full charge in about 4 hours
  • AirPlay mirroring and video out to Apple TV (2nd and 3rd generation)
  • Video mirroring and video out support: Up to 1080p through Lightning Digital AV Adapter and Lightning to VGA Adapter (adapters sold separately)

Telia starts to charge extra for using mobile VoIP

One of the arguments to why there wasn’t support for VoIP in the Lync mobile client was that some (all) of the carriers don’t like VoIP. Now one of the largest carrier in Sweden has announced that they will start to charge a monthly extra fee on all new plans where you simply pay to use free VoIP apps.

When you use Lync on a mobile phone today and use the call via work feature the Lync server calls your cell phone and your mobile will not be charged for a outgoing call. This is actually also something that some carriers have expressed some negative thoughts about, but its technically not possible for them to stop so I guess why bother. But there will probably be some sorts of network limitations on using some apps like Skype and I hope that they wont try to block Lync.



Lync for iOS and certificates

Ok so Lync for iOS are out, and I think that some people will have problems logging in at first (at least I had) and its because those ipads are on the corporate WIFI don’t have the CA certificate installed. So just a quick pointer on where to start troubleshooting before your crowd goes crazy and spamming your IT department with angry emails Winking smile

Ok I’m back to my Office 365 lab and will post my take on all this mobile stuff after the Christmas break Winking smile

Lync Server 2010 Protocol Workloads Poster updated with some mobile goddies – #Lync

But not that much mobile stuff in it? It still missing a lot of stuff when it comes to mobile workloads… so we could probably expect another update in the future Winking smile

Anyway, this poster shows each workload in Microsoft Lync Server 2010 communications software, describing relationships, dependencies, flow of information, and certificate requirements. Version 5.10 incorporates Mobility Services and corrections in the IM and Presence workload. Download http://www.microsoft.com/download/en/details.aspx?id=6797

But I also updated the Deepzoom version to the latest one and the link to it is http://zoom.it/36Qq

And of course embedded as always Winking smile

Configuring the Reverse Proxy for Lync Mobility: by using Port 80 (the not recommended way of doing it)

When publishing the services for Lync mobility there are two ways of doing it, HTTP or HTTPS.
If you decide to use HTTPS for the Lync Server 2010 Autodiscover Service it requires you to update the subject alternative names lists on the reverse proxy certificates, i.e. buy a new certificate with a SAN name for every sip domain on your Lync Server.
But if you don’t want to do this, you could enable this service over port 80 (its only the autodiscover information that are being sent here so no authentication information are being sent or anything else. but this is still not the recommended way of doing this.)

This post will guide you through the settings for HTTP and a later post will guide you through the settings for HTTPS.

This information is originally from http://technet.microsoft.com/en-us/library/hh690011.aspx but edited and with screen dumps for LyncLab.org

To create a web publishing rule for port 80

  1. Create a New Web Publishing Rule page, type a display name for the new publishing rule (LyncDiscoveryURL (HTTP)).
  2. Select Allow, on the Select Rule Action page.
  3. Select Publish a single Web site or load balancer, on the Publishing Type page.
  4. Use non-secured connections to connect to the published Web server or server farm.
  5. Type the pool FQDN for your Front End or Director pool (for example, pool01.lynclab.org) on the Internal Publishing Details page. (This should point to the External virtual directory on the IIS and will be redirected to port 8080 later in step 15)
  6. In Path, on the Internal Publishing Details page type /* as the path of the folder to be published, and then select Forward the original host header instead of the one specified in the Internal site name field.
  7. On the Public Name Details page, do the following:
    1. Under Accept Requests for, select This domain name.
    2. In Public Name, type something like lyncdiscover.lynclab.org (the external Autodiscover Service URL)
    3. In Path, type /
  8. On Select Web Listener page, in Web Listener, select the same Web Listener that you used to publish Lync external webservices or create a new one.
    (To find your reverse proxy FQDN use this PowerShell one-liner on your Front End server Get-CsService -WebServer | ft ABHandlerExternalUri )
  9. If you reused your old rule, select it and then click Edit and make sure that Enable HTTP connections on port 80 are checked and that No authentication are selected.
  10. Click Ok on the listener. And then Next on the Select Web Listener page
  11. On the Authentication Delegation page, select No delegation, and client cannot authenticate directly.
  12. Select All Users, on the User Set page
  13. And then click Finish.
  14. Now double-click the new rule you just added and open Properties for it.
  15. On the Bridging tab, configure the following:
    1. Select Redirect requests to HTTP port, and type 8080 for the port number.
    2. Verify that Redirect requests to SSL port is not selected.
  16. Click OK. and Apply the new rules

Microsoft Lync Server 2010 Mobility Service and Microsoft Lync Server 2010 Autodiscover Service for your weekend installation – #Lync

The bits for the mobility service is now live on download.microsoft.com

These new services for Microsoft Lync Server 2010 support Lync 2010 functionality, such as instant messaging (IM), presence, management of contacts and groups, Call via Work, Single Number Reach, and Single-click Conference Join on mobile and slate devices.


Lync PowerShell tip #7 – #Lync

get-help New-CsMobilityPolicy –full

This will give some interesting reading IF you have deployed CU4 that got released today (or yday)

Lync 2010 Mobile is a client application that enables users to run Microsoft Lync 2010 on their mobile phones. Call via Work provides a way for users to make calls on their mobile phone and yet have it appear as though the call originated from their work phone number instead of their mobile phone number. Users who have been enabled for Call via Work can achieve this either by dialing directly from their mobile phone or by using the dial-out conferencing option. With dial-out conferencing, a user effectively asks the Microsoft Lync Server 2010 Mobility Service server to make a call for them. The server will set up the call, and then call the user back on their mobile phone. After the user has answered, the server will then dial the party being called.

Both of these capabilities – the ability to run Lync 2010 Mobile and the ability to use Call via Work – are managed using mobility policies. When youinstall Microsoft Lync Server 2010, you will have a single, global mobility policy that applies to all your users. However, administrators can use the New-CsMobilityPolicy cmdlet to create custom policies at either the site or the per-user scope.

Other than a description of the policy, mobility policies have only two properties. The first, EnableOutsideVoice, determines whether or not Call via Work is enabled; the second, EnableMobility, determines whether or not users are allowed to use Lync Mobile. Both of these properties must be set to true before a user can take advantage of Call via Work. If EnableMobility is set to True and EnableOutsideVoice is set to False, the user can run Microsoft Lync Mobile but will not be able to use Call via Work. If EnableMobility is set to False and EnableOutsideVoice is set to True the user will not be able to run Microsoft Lync Mobile. In turn, that means that the user will not be able to use Call via Work, regardless of the value of the EnableOutsideVoice property.

Note that users must also be enabled for Enterprise Voice before they can use Lync 2010 Mobile. To use Call via Work, users must be managed by a voice policy that allows simultaneous ringing.Who can run this cmdlet: By default, members of the following groups are authorized to run the New-CsMobilityPolicy cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have
created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets -match “New-CsMobilityPolicy”}