TopBanner

[News] Microsoft Lync Public IM Connectivity to Yahoo Messenger Goes End-Of-Sale Today (Dec 14, 2012)

httpallcomputers.usimage1107Federation

According to Yahoo and Microsoft, PIC to Yahoo Messenger (Lync to Yahoo Messenger federation) can no longer be purchased as of today. (Dec 14, 2012) This is the beginning of the process to shut down ahoo PIC. Microsoft says the exact date is TBD but will be no sooner than June 2013.

Considering that the lights are being turned on for Skype, I am more than happy with the trade.

Sources:
http://blogs.technet.com/b/lync/archive/2012/11/26/lync-and-yahoo-federation-end-of-life.aspx

http://www.ymessengerblog.com/blog/2012/11/30/updates-to-yahoo-messenger-features/

Skype Federation:
http://windowspbx.blogspot.com/2012/11/how-to-enable-skype-to-lync-20102013.html

#Lync User QuickTip #26: Lync Instant Message to Any SMS Enabled USA Mobile Phone (for Free, In 1 Minute)

 

Note: You do not need an AOL account but you do need your Lync PIC AOL Federation.
Note: You need Lync 2010 or Lync Windows Store App to use this  (more details below)

Due to the fact that SMS has recently hit its 20th anniversary, many are wondering what IM solution will replace SMS. Well, with this solution, or another solution using this concept, any IM/P solution could render test messaging less relevant. (Actually I’m quite interested in the subject of moving past SMS so if you have more ideas, please comment or twitter me @matthewlandis )

Steps to setup: 1-Configure AOL PIC Federation, 2-Type in SMS number @AOL.com, 3-IM to SMS!

#1-Get PIC federation for AOL/AIM work correctly. Here are some tips on how to enable AIM/AOL PIC.

#2-Now just type in the phone number, prefixed by +1 and suffixed by @aol.com (e164 format) into Lync client. (Example: +18001112222@aol.com)

type in sms number

#3-If everything is working alright (with your PIC AOL federation) the contact should light up as "online" as shown below. (note, AOL doesn’t verify the sms # until you send the message) Now just send your message! That’s it!

aol presence lit up

Below is what the SMS mobile sees: The sms will come from a 6 digit number. Each sms will include the Lync URI so the person knows who the IM is coming from. And as clearly noted on each sms, the mobile user can reply.

mobile-receiving-sms

Of course you can save a contact and give the SMS contact a nice name.

save as a contact with name

More details about your AOL to SMS Instant Message Account

A good way to think about this service is that every USA mobile phone already has a corresponding AOL account. Identity/Authentication is done via the mobile phone number.  Management of this account is done by sending SMS msgs to 26519. To get started send HELP to 26519. The mobile device can easily STOP this service.

Some question I still have about this service and maybe some AOL/AIM guru can help me?

  • Is there a way from the mobile/via sms to change your AOL/AIM “presence” to away/offline?
  • Is there any statements/sources on if AOL/AIM is planning to continue to support AOL IM?
  • This is an excellent way to bridge the Instant Message / SMS divide, are there any other vendors doing this? (just in case AOL goes away)

 

Pros

  • You do not need to have any AOL account for this to work
  • Amazingly it is not all that clear that the sms is actually coming from AOL!
  • You handle txt message communication JUST like an peer to peer IM in Lync
  • This includes using the same Lync window, and you IM history is saved
  • You can same the contact in Outlook and Pin on Lync just like any other contact

 

Cons

  • txt phone number can not be a part of an IM conference
  • IM is the only modality supported

 

Notes:

  • no cost per text (just what the recieving mobile pays)
  • if the IM you send is longer than 1 SMS it will split the message.
  • Works for USA mobile numbers
  • No need to know which mobile operator

 

Which Lync clients work with this Solution?

Since this solution depends on simple federation it should work with any Lync client---unfortunately there is a snafu related to the URI starting with a +. It seems in some newer Lync clients any URI that starts with a + is hardwired to consider this a telephone number. This limitation means that you cannot federate with any contact/URI that starts with a + . (thanks to @tompacyk for pointing this out)

Lync 2010 Works
Lync Attendant Works
Lync 2013 Windows Store App (RT) Works
Lync 2013 Basic Doesn’t Work
Lync 2013 Doesn’t Work
Lync Mobile for Windows Phone Doesn’t Work
Lync Mobile for Android Doesn’t Work
Lync Mobile for iPhone Untested
Lync Mobile for iPad Untested
Pidgin 2.10.0 w/SIPE Works

 

Other Microsoft Lync to SMS Gateways:
http://www.geomant.com/microsoft-solutions/microsoft-1/microsoft-child-page-1/

More stuff on AOL / SMS:
http://www.tech-recipes.com/rx/116/send-sms-text-messages-from-aim/
http://infrastructurehelp.wordpress.com/2012/04/28/troubleshooting-pic-federation/
http://support.microsoft.com/kb/897567?wa=wsignin1.0
Test AOL PIC/Federation: sipcheck@aol.com
http://help.aol.com/help/microsites/search.do?cmd=displayKC&docType=kc&externalId=185634

http://blogs.technet.com/b/messaging_with_communications/archive/2011/09/27/lync-and-aol-pic-issues.aspx

Polycom VVX500/600 #Lync Qualified IP Phone Supports Direct USB Headset Integration

 

Just saw a twitter post by fellow Lync MVP Adam Jacobs that the Polycom VVX500 Lync Qualified device supports USB headsets! I tried it with a Plantronics Blackwire S720 and I am quite impressed!

Shortly after you plug in the USB headset a small messaage will appear on the VVX screen letting you know a “digital headset connected”. Not only does the headset audio work, the mute, pickup/hangup and  “wearing sensor” works and will answer via this sensor.

Below is a quick demo:

After seeing this I thought maybe I’ve been missing the fact that Lync Phone Edition also does this since various LPE devices DO have an extra USB port: but a quick test on a Polycom CX600 proved that I was not missing anything. Smile with tongue out

And, while I was at it I tested the newly Lync Qualified snom 760. While the 760 supports Bluetooth headsets via a separately purchased dongle it does not seem to support a USB headset. I have a question in at snom whether this will be supported.

What USB Headsets are supported by VVX500?
http://support.polycom.com/global/documents/support/technical/products/voice/Compatible_USB_headset_EA62760.pdf

snom 710, 720 and 760 Now Qualified Lync Qualified


snom has just released snom UC Edition firmware version 8.8.2.8 which has passed Lync Qualified for the snom 710, 720 and 760. snom now has 6 Lync Qualified IP phones.

snom760_anthgrey_high_right_CallsOnHold_WEB_01

snom 760 Hands on First Impression Review:
http://windowspbx.blogspot.com/2012/01/snom-760-first-impression-hands-on.html

snom 710 Hands on First Impression Review:
http://windowspbx.blogspot.com/2012/09/first-impression-review-snom-710-ip.html

snom 710 Video First Impression Review:

snom 720 Video First Impression Review

Snom press release:
http://www.snom.com/en/news/archive/article/2012/en/snom-delivers-complete-portfolio-of-ip-phones-tested-and-qualified-for-microsoft-lync/

Can I Still Buy & Install Lync Server 2013 in a Standard Edition Scenario? Yes!

lync-2103-server-clarification

There is considerable confusion and misunderstanding floating around about Microsoft Lync Server 2013 editions because of Microsoft’s recent licensing/pricing changes and the verbiage used to communicate these changes. The short answer to much of the confusion is this:

Yes, you can still deploy your choice of Lync Enterprise or Lync Standard Edition, but they now cost the same and there is only 1 Microsoft part number (or license) to buy.

So buy a Microsoft Lync Server 2013 license and use it for 1 FE server in either a Standard Edition Server scenario or an Enterprise Edition Pool scenario---you can choose.

Lync Server 2013 Licensing Change FAQ:

Q. Do I need to get special media for Standard vs. Enterprise scenarios?
A. No, just like before, you decide this when defining the Lync topology. So for non-technical people this means that provision for both scenarios is on one CD image.

Q. Does a Lync Server 2013 license for 1 Front End server in a Standard Edition scenario cost exactly the same as 1 Front End for an Enterprise Edition scenario?
A. Yes, that is the main change Microsoft is making. You buy ONE Lync Server license and use it how you see fits you best.

Q. Does this mean licensing a Lync Server for a Standard Edition scenario has increased dramatically?
A. Yes, before this licensing change a Std. Edition server was approximately $699USD. Now it is approximately $3646USD. Microsoft notes that several things are now included in this licensing to increase it value: #1-added redundancy and resiliency features #2-external connector rights are now included with this license

Q. If a Standard Edition server costs the same as an Enterprise Edition Server, why wouldn’t we install an Enterprise Edition server?
A. A Standard Edition scenario can be implemented with a minimum of OS, Servers and SQL licenses for small implementations.

So yes, Lync Standard Edition is still here and you can install it, it just costs the same as Enterprise Edition.

Read Mary Jo Foley’s new article on this as well:
http://www.zdnet.com/microsoft-provides-more-details-on-office-2013-pricing-and-licensing-changes-7000008235/