locked
Skype 2015 Reverse Proxy with WAP and multiple Urls / subdomains RRS feed

  • Question

  • Hi Guy's

    we are migrating away from TMG to the Microst Web Application Proxy(2016)

    Now on the TMG i had a Listener with one IP and 4 Subdomains:

    lyncdiscover.domain.com
    dialin.domain.com
    meet.domain.com
    ocsproxy.domain.com

    als these Subdomains pointed to the same Skype Backend Url: skypefrontend.domain.internal:4443/*

    Now i have trouble rebuilding this with the WAP, becaue you can use a backend Urls only once
    e.g.
    If i publish dialin.domain.com -> skypefrontend.domain.internal:4443/*

    and the try to publish meet.domain.com -> skypefrontend.domain.internal:4443/*
    it says "skypefrontend.domain.internal:4443/*" is already used.

    Now my question is: Can i work arround this by selectively puslishing subdirectorys:
    like
    ocsproxy.domain.com -> goes to skypefrontend.domain.internal:4443/*
    but
    meet.domain.com -> goes to skypefrontend.domain.internal:4443/meet
    dialin.domain.com -> goes to skypefrontend.domain.internal:4443/dialin
    lyncdiscover.domain.com -> goes to skypefrontend.domain.internal:4443/autodiscove

    I've also seen that you could you subdirectorys for the simple urls:
    like skype.domain.com/meet and skype.domain.com/dialin
    But that would clearly be more work.

    Any help is realy appreciated,

    thanks guys

    regards

    Stefan

    Wednesday, October 9, 2019 8:19 AM

Answers

  • Hey Sharon,

    thanks for you reply.

    But i think i found the simple solution ... i just thought a little to much "inside the box"

    i didn't know that the skype hast multiple internal Urls.

    so i can just use different backend urls for each Public hostname on the WAP:

    meet.domain.com -> meet.domain.internal

    dialin.domain.com -> dialin.domain.internal

    and so on ...

    regards

    Stefan

    Thursday, October 10, 2019 7:32 AM

All replies

  • Hi steven_85,

    According to your description, you can refer to this document:

    https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Using-IIS-ARR-as-a-Reverse-Proxy-for-Lync-Server-2013/ba-p/620912


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Thursday, October 10, 2019 3:04 AM
  • Hey Sharon,

    thanks for you reply.

    But i think i found the simple solution ... i just thought a little to much "inside the box"

    i didn't know that the skype hast multiple internal Urls.

    so i can just use different backend urls for each Public hostname on the WAP:

    meet.domain.com -> meet.domain.internal

    dialin.domain.com -> dialin.domain.internal

    and so on ...

    regards

    Stefan

    Thursday, October 10, 2019 7:32 AM
  • Hi Stefan,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.

    Thanks for your understanding.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, October 15, 2019 2:22 AM
  • Here I will provide a brief summary of this post. This will make answer searching in the forum easier.

     

    <Request/Exception>:

    Migrate from TMG to the Microsoft Web Application Proxy (2016). User has one IP and 4 Subdomains on the TMG. How to set this Subdomains point to the Skype for Business Backend Server URLs?

     

    <Solution Summary>:

    Use different backend URLs for each Public hostname on the WAP.

     

    <Reference Link>:

    https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Using-IIS-ARR-as-a-Reverse-Proxy-for-Lync-Server-2013/ba-p/620912


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, October 31, 2019 8:36 AM