...
ID | Hostname | Type | TTL | Value | Gate | Weight | Priority | Note | Usage |
---|---|---|---|---|---|---|---|---|---|
1 | sipaccess | a | 3600 | 95.211.37.68 | add before migration | Route to edge server for voice, video and federation | |||
2 | sipaccess | a | 3600 | 95.211.37.71 | add before migration | Route to edge server for voice, video and federation | |||
3 | _sipfederationtls._tcp | SRV | 3600 | sip.contoso.com | 5061 | 1 | 100 | change on migration | Federation with external Skype for Business domains |
4 | _sip._tls | SRV | 3600 | sip.contoso.com | 443 | 1 | 100 | change on migration | SIP traffic for Skype for Business voice and video |
5 | lyncdiscover | a | 3600 | 95.211.37.66 | change on migration | Sign in to Skype for Business |
...
Info | ||
---|---|---|
| ||
If the hostname sip access is in use. Another hostname can be used (for example sipaccess or accesssip). For migration from office 365 or legacy lync or skype for business a different hostname can be used (for example accessthan the currently in use (default is sip.domain.com). |
How to migrate
- Point the sipaccess.domain.com records to the IP addresses in table-1 (value: ID 1 and 2).
- Notify support@softapp-distribution.com of the modification in DNS records.
- The certificate extension for sipaccess.domain.com will be requested and loaded to our edge servers.
- TVO365 will notify the customer of the change. Migration is possible now.
- All other records can be pointed towards TVO365 (ID 3, 4 and 5).
The certificate extension for lyncdiscover.domain.com will be requested during the migration.
...