Dialin Simple URL in Lync 2013 (Change of Default SIP Domain)

-
WARNING: Do NOT change the default SIP Domain in Lync!

As Microsoft wrote in the article Planning for Simple URLs, you will also see during your Topology setup, if you use multiple SIP domains, you only have one (1) active DIALIN URL.

This is by design and normal.

If you default SIP domain should be different from that you want to use in your simple URL.
Say your default SIP domain is CONTOSO.COM, you are able to Change your DIALIN and also MEET URL to say: CUSTOMER.COM.

If you need to do this, you have to add, as Best Practice, CUSTOMER.COM as additional SIP domain. Even if this domain will not be used for user SIP addressing.

If you want to make those changes after certain times, meens after you deployed Lync 2013.

Be Aware about the Impact.
You need to change your DNS and all related certificates.

1. NEVER DELETE nor CHANGE your Default SIP Domain
2. after you changed the simple URL, you MUST run Enable-CsComputer on all Frontend and Director Servers.


Comments

  1. Paul BloemJune 23, 2014 at 11:50 PM

    Hi Thomas,
    Thanks for the article. Can you please advise why the WARNING is stated in the beginning as I thought once you had catered for the DNS changes, meet and dialin URL's, sign-in cache cleared that it was ok to go ahead. I am aware that any other services like UM and RGS will need updated SIP addresses, is this the reason for the statement?

    Regards,
    Paul

    ReplyDelete
    Replies
    1. Thomas PoettJune 24, 2014 at 9:20 AM

      Hi Paul, you are welcome.
      as explained, during the initial Lync setup, Lync is activating several RTC-Applications. All those application start with RTCApplication_GUID@SIP.DOMAIN.
      This means:
      If you change the default SIP Domain and do NOT add it to the additional SIP Domains, you have Lync (RTC) application which cannot be proper addressed.
      This cause you issues at all sites of your deployment.

      Just give it in a Lab a try:
      Change the default SIP domain and start logging SIP Stack, e.g. SIP Stack on the Edge, you will see a number of errors related to the non existing SIP default domain.
      You can add e.g. a DNS entry again and solve some of the issues. But at the end you are running an unsupported Lync environment.

      I hope this helps you and other a bit, why you should NEVER do it
      Cheers
      Thomas

      Delete
  2. AnonymousFebruary 25, 2015 at 8:03 PM

    Great article. Enable-CsComputer, who can imagine. thanks a lot.

    ReplyDelete
  3. UnknownOctober 21, 2015 at 12:08 PM

    Hello, do you know any user impact after change the meet/dialin URLs?

    ReplyDelete
    Replies
    1. Thomas PoettOctober 21, 2015 at 1:06 PM

      Hi,
      well the are some impacts.
      First all meetings which are send out and or save with your mailbox have the SIMPLE URLs stored. a https:\\meet.sipdam.com\Thomas.poett\ajfur6hn and the https:\\dialin.sipdom.com
      if you now change those URL, the stored meeting information can't be accessed any long. Therefore you need to implement a URL redirect on the RevProxy and or in your location/ infrastructure.

      Another point important to consider is, if the URL changed, it also required internally and externally a new certificate with the new SAN names.

      Cheers

      Delete
  4. UnknownOctober 21, 2015 at 5:29 PM

    Hello,

    Thanks for the quick reply. I have found this error msg will pop up for the users: http://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-74-93/2014_5F00_01_5F00_06_5F00_01_2D00_09.png

    So probably they need to recreate all the meetings with the new URLs, right?

    Is the URL redirection works with meet and dialin? Do you know any detailed description about these activities?

    ReplyDelete
    Replies
    1. Thomas PoettOctober 22, 2015 at 8:33 AM

      Hi Mihály,
      this could also be another reason.
      1. test und check the normal process of creating a meeting with your new URL. if this work your are ok in general

      In your case here, the URL is working, since it accessed the MEET URL, else it wouldn't have found the Conferencing Service. Now you need to check if the meeting ID is still present.
      therefore you need follow the instruction provided in my Skype for Business Troubleshooting Guide:
      https://gallery.technet.microsoft.com/office/Skype-for-Business-and-7857597d

      if the ID still exists, we might talk about a 3rd level support case, where I could offer help
      Thomas

      Delete

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more