Topic Last Modified: 2010-07-14
Microsoft Office Communications Server 2007 R2 embedded links into meeting requests that were unreadable to most people, making it difficult to troubleshoot. Microsoft Communications Server 2010 addresses that issue by publishing meeting information in an easy to read format:
- Sample Office Communications Server 2007 R2 meeting
request:
meet:sip:cstest01@contoso.com;gruu;opaque=app:conf:focus:id:86dddd778f0443feaad144739eb6d285%3Fconf-key=A3O3Mrxm9
- Sample Communications Server 2010 meeting request (shared
Simple URL syntax):
https://cs.contoso.com/meet/cstest01/D7RDV4KG
- Sample Communications Server 2010 meeting request (dedicated
Simple URL syntax):
https://meet-us.contoso.com/cstest01/D7RDV4KG
When planning your simple URLs, you need to decide whether to use the shared or dedicated format. Selection criteria for each approach are listed in the following table.
Simple URL Format | When to use: |
---|---|
Shared |
For single pool deployments For multiple pool deployments where each pool shares global simple URLs For multiple pool deployments where each pool has dedicated simple URLs and public certificate cost is an issue, you can save one certificate per pool buy using shared simple URLs |
Dedicated |
For multiple pool deployments where each pool has dedicated simple URLs For deployments where you do not want to potentially expose internal server names externally |
Note: |
---|
Simple URLs are defined globally but in some cases, you may want to create a different set of simple URLs (for example, dialin, meet, and if internal, admin) per geography or pool. If so, you can use Windows PowerShell to assign them at the pool level. |