Today it's possible to dial from a Microsoft Lync 2013 or Skype for Business client to a Lifesize Cloud connected system, client or virtual meeting room using the "email@example.com" convention. Some customers have expressed the desire to dial using email address (URI) formats, as this is simpler and more intuitive for users who're familiar with the normal "federated calling" capabilities and associated workflows when communicating with other organisations via Microsoft Lync 2013 and/or Skype for Business.
e.g. Skype for Business user dials "firstname.lastname@example.org" from their client instead of dialing using the "email@example.com" convention to connect to a Lifesize Cloud connected system, client or VMR.
Suggested dialing conventions to be added:
- firstname.lastname@example.org - Full email address, correlates with the cloud email address defined for the user or cloud connected Icon/220 system.
- email@example.com - Customer domain, allows the customer to use their own domain name instead of lifesizecloud.com.
Obviously there are further technical considerations, but this would be a useful incremental capability for customers who're using Skype for Business, or regularly communicate with other organisations who do.
There are two types of customers who've expressed that this functionality would be desirable; customers who have extensive Microsoft Lync 2013 / Skype for Business environments and those who don't, but may commonly work with other organisations that do.
One limitation that I can foresee is that the DNS SRV record entries required for Skype for Business can clash with those required to enable this functionality via Lifesize Cloud. Obviously this could present a challenges for customers who have both Skype for Business and Lifesize Cloud solutions, so it's an accepted limitation that the "lifesize Cloud" devices in this case will likely require the use of a separate/different domain to avoid this potential clash. For organisations who only don't have Skype for Business environments, this would not be an issue.
Example DNS SRV records:
Here's an example DNS record that could apply...
priority = 10
weight = 10
port = 5061
svr hostname = lync.lifesizecloud.com
Please vote if you feel this would be a useful capability for you or your customers.