locked
After migrating infrastructure to SfB2019 - User can't join to the meeting with external partner RRS feed

  • Question

  • Errors: PS C:\Users\adm04830> Test-CsFederatedPartner -TargetFqdn sfbedgepoolemea.int.doamin.net -Domain push.lync.com -ProxyFqdn sipfed.online.lync.com
    Target Fqdn : sfbedgepoolemea.int.domain.net
    Result : Failure
    Latency : 00:00:00
    Error Message : 11001, No such host is known
    Inner Exception:No such host is known

    Customer reviewed Skype Setup:
    - federation route in Skype for business is configured to use new sfb2019-edge pool
    - next hop for sfb frontends is new sfb2019-edge pool
    - federation settings are correct
    - ports are not changed from default values

    Diagnosis :
    An exception 'Unable to establish a connection.' occurred during Workflow Microsoft.Rtc.SyntheticTransactions.Workflows.STFederatedPartnerWorkflow execution.
    Exception Call Stack: at Microsoft.Rtc.Signaling.SipAsyncResult2`1.ThrowIfFailed()

    Transaction failed: Unable to establish a connection..
    VERBOSE: Workflow Instance ID 'f0bce56a-ad8f-4444-8bd8-17e949c2a0e5' completed.
    VERBOSE: Workflow run-time (sec): 0.1230001


    Thursday, December 5, 2019 3:50 PM

Answers

  • Hi Tarique A!

    Your post mentioned your privacy, so I covered this information. Thanks for your understanding.

    Does this issue exist before migrating infrastructure to SfB2019?

    From your description, it seems that your external domain’s host file is not add ProxyFQDN. Make sure that the TargetFQDN parameter points to the internal Edge Server FQDN to which federated SIP traffic is directed.

    Moreover, we recommend you check your internal and external domain DNS configuration on Edge Server to see if it is correct.The following picture shows external DNS configuration


    Besides, you can refer to this article to check if your deployment about migration to Skype for Business 2019 is right.

    https://docs.microsoft.com/en-us/skypeforbusiness/migration/migration-to-skype-for-business-server-2019

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
    • Marked as answer by Tarique A Thursday, December 12, 2019 7:57 AM
    Friday, December 6, 2019 10:08 AM

All replies

  • Hi Tarique A!

    Your post mentioned your privacy, so I covered this information. Thanks for your understanding.

    Does this issue exist before migrating infrastructure to SfB2019?

    From your description, it seems that your external domain’s host file is not add ProxyFQDN. Make sure that the TargetFQDN parameter points to the internal Edge Server FQDN to which federated SIP traffic is directed.

    Moreover, we recommend you check your internal and external domain DNS configuration on Edge Server to see if it is correct.The following picture shows external DNS configuration


    Besides, you can refer to this article to check if your deployment about migration to Skype for Business 2019 is right.

    https://docs.microsoft.com/en-us/skypeforbusiness/migration/migration-to-skype-for-business-server-2019

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
    • Marked as answer by Tarique A Thursday, December 12, 2019 7:57 AM
    Friday, December 6, 2019 10:08 AM
  • Yes, this worked. it was an issue with DNS configuration.
    Thursday, December 12, 2019 7:55 AM