SIP address changes inside organizations are usually challenging – for the IT team making the change and the end users experiencing the change. For those unfamiliar with the SIP address change, it involves a change to either:
- The format of the left-hand side (e.g. firstname.lastname@example.org changing to email@example.com)
- The domain name on the right-hand side of the @ sign (e.g. firstname.lastname@example.org changes to user@new_domain.com)
This blog entry contains key reminders to end users going through the SIP address change process.
The impact to end users will depend somewhat on the Lync or Skype for Business (SfB) deployment and the clients used.
In most environments however, end users need to take the following 5 actions to re-establish their Lync and SfB services:
- Change the sign-in address on all SfB clients; don’t forget any clients running on mobile and tablets. Sign-out, change the SIP address, and sign-in again. Older Lync clients will sign the user out after their SIP address is changed on the backend.
- Any scheduled Skype for Business meetings (e.g. scheduled through the Outlook “Skype for Business Online Meeting” option) need to be canceled and recreated.
- When searching the address book for the first 24 hours post SIP change, enter the contacts full new SIP address.
- Change the SIP sign-in address at the same time as the email address (if it’s changing at the same time). This will minimize problems with the SfB feature integration with Exchange such as free/busy integration.
- Notify external contacts of the new SIP address. An external contact is any contact that either federated (in another Lync/SfB organization) or a Public IM contact (e.g. email@example.com). This is by far one of the highest impact items for the end users since it can render communication with external contacts. Basically the user has two options in my experience:
- Notify external contacts that their SIP address has changed, and that they need to add it as a new contact in their address books.
- Re-add the external contacts after the SIP change. Re-adding the external contact generates a request to the external contact to have them add the user (and the new SIP address) to their contact list. If there are a lot of external contacts, fellow Office Servers and Services MVP Michael LaMontagne has developed a nifty PowerShell script that uses the Lync SDK to run on the Lync or SfB client that can export and import contacts. An advanced user, or IT administrator, can use this script to export the contacts, delete the external contacts in the client, and then re-import them after the SIP change.
- See Invoke-SFBContacts on the TechNet Gallery to get the script.
Lastly, if weird issues arise on older Lync clients (e.g. Lync 2010/2013) and/or older client operating systems such as Windows 7, try rebooting the computer is a good first step.