Lync 2013 Problem with IM to federated contacts from branch offices

Qdu1 1 Reputation point
2020-11-10T14:33:46.187+00:00

Hello
We are dealing with the problem that the users which homed on branc site (lync sbs) cannot call or use IM on federated contacts. Also the contact's presense information is unavailable. Only federated contact can see the presence and start a call or IM to internal user, but not vice versa.

At the same time, when particular user is moved to the central enterprise pool, everything is OK.

We have the following topology:

Lync 2013 Enterprise pool: 2 FEs, 1 SQL BE, 1 SQL Monitoring reports, 1 Edge server.
Lync 2013 branch site: 1 server.

Everything is installed from scratch, no previous installations or migrations from Lync 2010 or OCS 2007.

From the branch server i am able to ping or telnet to all enterprise servers (FEs and Edge).

The depoyment was done in the following way:

Domain controller > SQL server 1 > SQL server 2 > FE1 > FE2 > Edge > SBS1

In the report logging i see the following:

"application/sdp;call-type=im" responseCode="404" requestType="INVITE"><diagHeader>1003;reason="User does not exist";destination="FederatedUser@mathieu.company .com";source="lyncsbc01-s2.domain.local";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="6";SourceNetwork="5";RemotePartyCanDoIM="Yes"

Skype for Business
Skype for Business
A Microsoft communications service that provides communications capabilities across presence, instant messaging, audio/video calling, and an online meeting experience that includes audio, video, and web conferencing.
606 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sharon Zhao-MSFT 25,056 Reputation points Microsoft Vendor
    2020-11-11T07:46:55.4+00:00

    @Qdu1 ,

    Can the users in branch site communicate with internal user properly?

    It seems something wrong with configuration on Edge server.

    Please check the following things:

    • Edge Gateway is configured on the external NIC
    • DNS Points to the external DNS
    • Routing entries for the internal Network are done by route add
    • Edge Server can resolve the FQDN names from the internal Lync Server by host entries or DNS
    • The Edge Server FQDN can be resolved by the internal Clients.
    • Firewall are set correct for the needed ports

    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.