Lync Phone Edition Gets Transfer to Voicemail in Oct 2013 Update

This has been a busy week for me but it looks like Microsoft has completed another top requested feature at http://lync.ideascale.com ---Transfer to Voicemail Functionality.

In this new update you can select a contact card and arrow down to the voicemail and transfer directly to voicemail.

NOTE: You might be hoping that you can call a contact’s voicemail directly as well, but currently you can only Transfer To voicemail.

Video Demo of New Feature:

4.0.7577.4414 - Transfer to Voicemail Functionality Explained by KB:
http://support.microsoft.com/kb/2890842

Get the Update:
http://support.microsoft.com/kb/2889246

Interesting: Variou Lync Pro’s didn’t think Microsoft Would Update LPE With This Feature:
http://lync.ideascale.com/a/dtd/Lync-Phone-Edition-should-have-transfer-to-voicemail-option/54936-16285

Update all your devices with Pat Richard’s excellent powerhsell:
http://www.ehloworld.com/1217

Or manually:
http://blog.schertz.name/2011/01/updating-lync-phone-edition-devices/

All Lync Users Need a Destination on No Answer: Call Forwarding When No Endpoint Registered

If you are implementing Lync users that don't have voicemail you might be forgetting about the caller experience when a Lync client or phone is not registered.  Have you thought about what the caller will experience when no IP phone or Lync client is registered? (or if they have portable WIFI phone and it is powered off?)

When a Lync endpoint is registered and that Lync user is called things will work as you expect: the call will ring for the length of time defined in the “Call Forwarding” dialog (up to 60 seconds) and then fail.

Where it gets more confusing and inconsistent for the caller is when the Lync user in question has a DID and external/PSTN users are calling the Lync user directly. If the Lync user has no IP phone/Lync client registered the caller can get various messages depending on their own telco:

• The number you have reached is not in service. This is a recording (SIP trunk provider)
• sorry, this mobile number is not available at this time. (mobile
• this number is no longer connected
• busy
• etc. (in other words, a very inconsistent and confusing caller experience)

Technically What is Happening?

Lync to Lync User: The caller is getting a SIP 480 “Temporarily Unavailable” (below)

PSTN to Lync DID

So this brings up the point that every Lync user needs to have a destination on no answer even if there is no voicemail (voicemail is effectively a global destination on no answer) for this user.

What are several options?

• setup the Lync user(s) to forward to a Response Group (RGS will need an extension# or DID to configure this in Lync client call forwarding settings) that says something like “Sorry, no one is available at this time.” and then disconnects  (you can set this up centrally using SEFAUtil)
  • Notes
    • with this method, if there is no voicmail and no client registered the call will be answered immediately by the “message” RGS
  • Cons
    • if call forwarding is enabled for this user they could change call forwarding to nothing and forget to set it back reintroducing the problem
    • if they have a snom UC Edition phone forward and clear forward, the forward on no answer is cleared
    • If you disable call forwarding using a Voice Policy obviously user can no longer forward to distination *they* want to forward it to and they may be confused by fact that Lync client still presents forwarding options (see: Click Here)
• another possible option: have SBC/Gateway reroute call on message from Lync
  • cons:
    • only calls going through sbc/gateway will be rerouted
• MSPL script
  • I did not sit down and write an MSPL script, but this could be quite elegant. If someone has such a script, I’d be glad to post it/link here.
  • Perhaps this script could be modified? Click Here
    

If you think “Destination on No Answer” functionality should be built into Lync you may want to vote for it here:
http://lync.ideascale.com/a/dtd/Forwarding-incoming-calls-if-user-is-logged-off/160720-16285

The following professionals have contributed to this blog: @lyncdialog @patrichard @Matt_Friedrichs @wangshoulun @jveldh

October 2013 Cumulative Updates for Lync Server 2013 Is Here: What Is New?

 

What are some new features?

• This update enables administrators to provide support for the *0 Dual Tone Multi Frequency (DTMF) command in a public switched telephone network (PSTN) dial-in conference in a Microsoft Lync Server 2013 environment. After the update is installed, a PSTN caller is able to be transferred to an operator number that the administrator defines.
• http://support.microsoft.com/kb/2882802

Fixes

• Mediation server can’t forward call history headers when a forwarded call number has an extension in a Lync Server 2013 environment
• http://support.microsoft.com/kb/2881699
• You can’t dial out or share video in a Lync Web App meeting in a Lync Server 2013 environment
• http://support.microsoft.com/kb/2882800/en-us?sd=rss&spid=924

http://support.microsoft.com/kb/2809243/en-us?sd=rss&spid=924

http://support.microsoft.com/kb/2881688

All Updates: http://support.microsoft.com/kb/2881699

AOL Announces Direct Federation With Microsoft Lync and UC Federation Plans for AIM

Is Microsoft Lync the UC solution that consumer IM providers can not afford to not be connected to? But perhaps even more importantly: does AOL have plans to return AIM to relevancy via an enterprise UC federation exchange service?

Microosft has noted that its support for AIM and Yahoo on it’s PIC (Public IM Connectivity) service is “winding down”. While mindshare for AIM among general users is non-existent, there is a loyal following in trader/financial sector users.

In an interesting move that indicates AOL values Microsoft Lync federation, AOL is offering direct AIM federation with Microsoft Lync:

“AOL is pleased to offer Microsoft Lync customers the opportunity to continue their current federation with AIM and establish new federations if needed. For the first time, we are enabling companies with the ability to establish a direct relationship with AOL to provision and manage their connectivity to the AIM network. This will also allow you to have direct and immediate access to AIM technical support engineers who can quickly identify and resolve any AIM-related issues, thus making the transition to AOL is seamless with no disruption to your company and users.

It is interesting the AOL notes they are offering support from “a dedicated team of enterprise engineers…” and “federation with other companies currently connected to the AIM network”

“Our customers receive technical support from a dedicated team of enterprise engineers. In addition, AOL will soon offer other optional services that will extend the reach of federation with AIM to include federation with other companies currently connected to the AIM network.

Does this mean that AOL is aiming (no pun intended!) to become a Lync/UC federation exchange? Will AIM avoid fading into the sunset by becoming relevant again via some enterprise federation exchange service?

Does this indicate that Microsoft is the party not interested in continuing the relationship with their existing PIC service?

To read more including a detailed AIM-Lync FAQ: Click Here
Lync as the Most Connect UC Solution?: Click Here
Lync Federation Directory Project: Click Here
www.aim.com