Typically the meet URL resolves to the Reverse proxy in the your organization which is configured to receive the request for the meet URL. The reverse proxy will then proxy the request to one of the Frontend (FE) pools or director pool on port 4443. For
this to
So let me explain the difference between meet.domain.com and
External-pool.domain.com/meet/?origurl=xxxx
1. meet.domain.com
>> This type of request will be processed when the Meet URL (meet.domain.com) points to organizer’s home pool.
2. External-Pool.domain.com/meet/?origurl=xxx
>> This type of request processed when the Meet URL (meet.domain.com) points to a pool which is not the meeting organizer’s home pool or it is pointing to director pool.
In this type of scenario, the Lync /Skype for Business server validates the conference and returns the
200 OK response to the request. The
200 OK response contains the value for “var domainownerjoinlauncherurl” which contains the external Webservices URL for the organizer pool and it looks like
https://external-pool.domain.com/meet/?origurl=xxxx
Note : You shall trace this flow in fiddler logs.
Hope this helps !
**Mark as answered, if this helps, it might help others who have similar query**
Best Regards, Neeranjan
