Wednesday, April 8, 2015

Skype for Business Readiness Series (12/15)

Today I joined the twelfth session of the Skype for Business Readiness WebCast Series and the topic for today were Lync/Skype Federation (Phase 2). The Webcast was recorded and is available online from the link above.



Kiran Kodali presented the topic and answered questions. Skype for Business is using the SILK codec; SILK is a better codec than RTA and / or G.722 at any network condition. In phase 2 of the Skype-Skype (that is for business with consumer) federation, media can be sent peer-to-peer from consumer Skype clients straight to S4B clients. If this is not possible due to firewalls STUN / TURN servers on both ends will be used. Phase 2 of this federation is already running in the Skype cloud and can be used as soon as on-prem servers and clients have been upgraded to Skype for business. Phase 2 also adds a Skype directory search which requires a S4B Edge server. The S4B Edge connects to a "Skype graph service", which is a service running in Azure delivering search results from the global Skype directory. Searches in the Skype directory can be done on name, location, email, phone and SkypeID, also Skype thumbnail pictures will be visible for S4B users. When we do a search from within the S4B client and have Skype Directory Search enabled, we will have a choice of where to search, in "My Contacts" or in "Skype Directory", with the default being "My Contacts" which is the internal address book. Conferencing or screen sharing capabilities is not a part of phase 2.

Here comes todays QnA session, 17 questions and 13 answers, enjoy!

New features

Will the new Skype for business server allow federation with Skype accounts or will federation only work with MS Skype accounts?
S4B Server/client will allow Search/Federation with both Skype IDs and MS accounts (live accounts)

Do Skype clients gain network efficiencies like SILK during a P2P session when running again an on-prem Lync 2013 server?
Yes, SILK will be used in P2P for both Skype and Lync clients for users homed on Lync 2013 Server on premise.

When will the Skype Directory search be available in the client?
It is already available in the S4B client, but it requires the user to be homed on a S4B server using a S4B Edge.

When Skype search is set to true can you still block this at Site Level?
Yes, Skype-Skype Federation search module works the same as Federation module, so you can disable it for a Site.

In S4B Online, will we be able to control who (by name and/or group) can and cannot (1) search for "public" Skype users and (2) connect with "public" Skype users?
For Online users, you can grant the ability for Skype Public IM at a user level and you can script this via PowerShell to bulk assign to users using the 
Grant-CsExternalAccessPolicy. If a user has Skype Public IM capability then they also have the ability to search the Skype Directory.

How are enterprises approved/enabled for SkypeID search?
No requirement to be approved. We just need to have S4B Client/Pool/Edge, and of course we need to enable Federation with Skype consumer (aka PIC federation.)

Is TCP port 4443 required inbound, outbound, or both?
Client to the Pool (TCP 443 – same as ABWQ) The Pool to the Edge (TCP 4443 – same as CMS replication) Edge to Skype Directory Search in Azure (TCP 443 - Access Edge Interface, and AV Edge Interface for media.)

Are any new external SRV records required or will the federation use the ones we use today?
No new SRV records required, the only infrastructure change will be outbound TCP 443 on the Access Edge server to enable the Skype Directory search feature.


Unchanged features

Do we still need to register every SIP domains Edge server at pic.lync.com?
Yes, for On-Premise deployments, you still need to register your SIP domains and an Edge server to enable Federation between your deployment and Skype consumer, for Online, you just need to enable Skype Federation in the tenant.

If we have currently configured Lync 2013 Server-Skype connectivity and we will not upgrade to S4B server, will the federation still function (without the Skype Provider update)?
Yes, but the Directory search is not available with Lync 2013.

Will the Phase 2 enhancement also be available for Lync 2013?
No, V2 Directory Search requires Skype for Business Edge/Pool/Client.


Features "missing"

Can a Skype consumer client join a Skype4B conference?
No, Skype cannot connect to conferences hosted in Skype for Business over the federation route. However, using the PSTN calling capability in Skype, a Skype user can dial into a Skype for Business CAA and join this way.

If two S4B users are on a P2P call, can they add Skype Federated user in the same call?
No, in this scenario, we would require a conference escalation. They would need to "meet now" then provide the Skype client a CAA to dial in to (assuming the Skype client is setup to use PSTN calling.)

Will there be a new Skype for Mac client to bring it to the S4B level and include the SILK codec?
Not answered.

Will the SILK codec be added to a future firmware update for existing Lync Phone Edition devices?
Not answered.

Will the Federation be extended to more platforms such as Skype Smart TVs and Xbox One?
Not answered.

Will Skype clients use SILK in case of media-bypass with Audiocodes Mediant 1000?
In order for this to happen, Audiocodes would have to update their devices to support the SILK codec. This would be dependent upon Audiocodes and your Audiocodes rep would be able to answer. (Maybe we can get a comment on the plans for this from Audiocodes - I will try…)

1 comment:

  1. have recently upgraded my Front end and edge 2013 Lync installations to SFB 2015 I have followed every step and limited guide out there and so far all is going well.

    The problem I have is when I run this cmd

    New-CsPublicProvider -Identity Skype -ProxyFqdn federation.messenger.msn.com -IconUrl https://images.edge.messenger.live.com/Messenger_16x16.png
    -NameDecorationRoutingDomain msn.com - NameDecorationExcludedDomainList "msn.com,outlook.com,live.com,hotmail.com" -VerificationLevel UseSourceVerification -Enabled $true -EnableSkypeIdRouting $true -EnableSkypeDirectorySearch $true

    no matter what I do -EnableSkypeIdRouting $true -EnableSkypeDirectorySearch $true stays as false






    I have followed this guide https://technet.microsoft.com/en-us/library/dn705313.aspx?f=255&MSPPError=-2147217396 very closely and I believe successfully followed every step.

    I just cant seem to get Skype directory search to be set to $true.

    Many Thanks in advance

    Paul

    ReplyDelete