How does actually Lync mobility works In Lync 2010 it came along with CU4 where we had to run the bootstraper from shell, In lync server 2013 there is no need to install lync mobility separately, it is built in installation. With Lync server and client both being 2013 Push notifications are not required for apple and android phones but as per the technet the push notification is created. Requirements for Lync Mobility -DNS Internal DNS Lyncdiscoverinternal.<sipdomain> note: Even the Lync 2013 clients use this record External DNS Lyncdiscover.<sipdomain> -Certificate Ensure the certificates must have the DNS entries in it -Configure push notification support New-CsHostingProvider –Identity “LyncOnline” –Enabled $True –ProxyFqdn “sipfed.online.lync.com” –VerificationLevel UseSourceVerification New-CsAllowedDomain –Identity “push.lync.com” Set-CsPushNotificationConfiguration –EnableApplePushNotificationService $True –EnableMicrosoftPushNotificationService $True Set-CSAccessEdgeConfiguration -AllowFederatedUsers $True The public cert applied to the reverse proxy and Lync FE server (External Web Site) should include at least the following CN and Subject Alternative Names: lyncweb.domain.com (External FQDN) lyncdiscover.domain.com (Lync Autodiscover URL) meet.domain.com (Meeting Simple URL) dialin.domain.com (Dial-in Simple URL for phone dial-in) (Note: SANs such as Dial-in, Meet, and the Edge service URLs are only necessary if these features are deployed but are not required for basic mobility to work.) It’s recommended to have difference addresses for internal web services and for external web services. after installation front end server you need to check mobility service, in lync 2010 checking way was to browse ulr https://lyncdiscover.doamain/autodiscover/autodiscover.svc from external andhttps://lyncdiscoverinternal.domain/autodiscover/autodiscover.svc from internal note port 443 & 4443 is used for each you should be able to download a file autodiscover.svc To test person-to-person instant messaging (IM) for Lync 2010 Mobile Test-CsMcxP2PIM -TargetFqdn <FQDN of Front End pool> -Authentication <TrustedServer | Negotiate | ClientCertificate | LiveID> -SenderSipAddress sip:<SIP address of test user 1> -SenderCredential <test user 1 credentials> -ReceiverSipAddress sip:<SIP address of test user 2> -ReceiverCredential <test user 2 credentials> -v To test conferencing for Lync 2013 Mobile clients Test-CsUcwaConference -TargetFqdn <FQDN of Front End pool> -Authentication <TrustedServer | Negotiate | ClientCertificate | LiveID> -OrganizerSipAddress sip:<SIP address of test user 1> -OrganizerCredential <test user 1 credentials> -ParticipantSipAddress sip:<SIP address of test user 2> -ParticipantCredential <test user 2 credentials> -v
Single Number Reach and Call Via work EV feature supported by mobile clients are: 1. single number reach - User receives a call on this mobile device even though the call was dialed to the their work number. 2. Call via work - It is something like replacement of RCC, now Lync does not talks to CSTA Gateway rather it calls the PBX and PBX calls the user other party and same time the calles desk phone also rings
in the Set-CsMobilityPolicy, the parameter EnableOutsideVoice When set to True, enables users to take advantage of Call via Work. When set to False, users cannot use Call via Work. The default value is True.
====================================================================== Lync client signin https://technet.microsoft.com/en-us/library/gg398758(v=ocs.15).aspx Though both Lync desktop and mobile client do look for Lyncdiscoverinternal.domain.com Lyncdiscover.domain.com which always points to the reverse proxy and both the clients can sign in. But in a situation if there is some issue with the reverse proxy then mobile clients as well the desktop clients will not be able to sign in if you do not have the other records such as SRV, etc. so always have all the records. Mobile clients never use the Edge servers, Edge servers are only required by the mobile clients when they have to make any AV calls, which requires the candidate discovery SO, what happens when both the clients are able to resolve the Lyncdiscover.domain.com and hit the reverse proxy Mobile Client > Lyncdiscover.domain.com > RP > Autodiscover Virtual directory in the FE > UCWA Desktop Client > Lyncdiscover.domain.com > RP > Autodiscover Virtual directory in the FE > Edge Server ======================================================================
No comments:
Post a Comment