issues with Lync 2010 servers after adding new SIP domain

hi there,

we have our Lync servers running with abc.com as a SIP domain and everything was working fine.

recently we have added xyz.com as an additional SIP domain and assigned new SIP domain to some users.

user1@xyz.com (new user)

user2@xyz.com (new user)

user_old@abc.com (old user)

below are the issues we are facing at the moment, need you guys assistance to correct them.

1. user1 and user2 are unable to perform IM/audio call/sharing each other. (presence unknown too)

2. user1 and user2 can perform IM/calls/sharing etc with user_old, also from user_old to user1 and user2 works fine.

3. meeting invitee send out by user1 or user2 can't be logged in by user_old

4. meeting invitee send out by user_old can be logged in by both user1 and user2.

in short, I feel like the new SIP domain does not work properly, please assist me how can I take it further.


July 9th, 2015 6:19am

Check that you are properly configured your new domain on SIP check here all steps to reconnect or reconfigured them

http://blog.ucitsimple.com/2011/10/04/adding-new-sip-domains-to-lync/

Free Windows Admin Tool Kit Click here and download it now
July 9th, 2015 6:44am

hi bro, sorry for the late response.

There is some improvement in the resolution at the moment, as the IM seems to be working between new and old SIP domains, but the meeting URL for the new SIP domain not working internally as well as with externally.

Having said the above, meet.newSIPdomain.com is not working internally as well as externally, meanwhile the meet.oldSIPdomain.com works fine. any clue why do I have problem with meet URL of new SIP domain, where can I locate the issue related to this? if it is something to do with IIS on the FE server how to fix this?

I can confirm the necessary DNS records and certificates are in place, as identically as the old SIP domain, so I feel like this problem is related to something else (IIS or different).

July 14th, 2015 12:17am

hi bro, sorry for the late response.

There is some improvement in the resolution at the moment, as the IM seems to be working between new and old SIP domains, but the meeting URL for the new SIP domain is not working at the moment.

like I said above, while the URL of meet.newSIPdomain.com is not working internally as well as externally, the URL of meet.oldSIPdomain.com works fine. any clue why do I have problem with meet URL of new SIP domain, where can I locate the events related to this issue? If it is something to do with IIS on the FE server, what to be validated apart from the usual event logs?

I can confirm the necessary DNS records and certificates are in place, as identically as the old SIP domain, so I feel like this problem is related to something else (may be IIS or different component).


Free Windows Admin Tool Kit Click here and download it now
July 14th, 2015 4:17am

hi bro, sorry for the late response.

There is some improvement in the resolution at the moment, as the IM seems to be working between new and old SIP domains, but the meeting URL for the new SIP domain is not working at the moment.

like I said above, while the URL of meet.newSIPdomain.com is not working internally as well as externally, the URL of meet.oldSIPdomain.com works fine. any clue why do I have problem with meet URL of new SIP domain, where can I locate the events related to this issue? If it is something to do with IIS on the FE server, what to be validated apart from the usual event logs?

I can confirm the necessary DNS records and certificates are in place, as identically as the old SIP domain, so I feel like this problem is related to something else (may be IIS or different component).


July 14th, 2015 4:17am

If you go into your topology builder, and at the highest level where is says "Lync Server" review your simple URLs, did you add the meet.newsipdomain.com record?  https://technet.microsoft.com/en-us/library/gg398063%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

It's an easy step to miss.

Free Windows Admin Tool Kit Click here and download it now
July 15th, 2015 2:50pm

Hi everyone,

I'm glad to announce the resolution to this topic, as the resolution is implemented just a min back and all works fine.

Resolution: logon to front end server --> Open Lync deployment wizard --> click "Install or update the Lync server system" -> select step2 "setup or remove Lync server component"->Run ->Execute--> Finish --> Reboot the server.

after performing the above steps, I could see the IIS virtual directory has been updated with all the references related to the meet URL of new SIP domain, when I tested the new meeting URL(https://meet.newSIPdomain.com\username\meeting ID\) it was found accessible internally as well as Externally.

Now the meeting between new SIP domain <-> new SIP domain and also old SIP domain <-> new SIP domains works fine.

July 19th, 2015 3:14am

Hi everyone,

I'm glad to announce the resolution to this topic, as the resolution is implemented just a min back and all works fine.

Resolution: logon to front end server --> Open Lync deployment wizard --> click "Install or update the Lync server system" -> select step2 "setup or remove Lync server component"->Run ->Execute--> Finish --> Reboot the server.

after performing the above steps, I could see the IIS virtual directory has been updated with all the references related to the meet URL of new SIP domain, when I tested the new meeting URL(https://meet.newSIPdomain.com\username\meeting ID\) it was found accessible internally as well as Externally.

Now the meeting between new SIP domain <-> new SIP domain and also old SIP domain <-> new SIP domains works fine.

Free Windows Admin Tool Kit Click here and download it now
July 19th, 2015 7:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics