Skip to main content

Unable to validate location information with provider.

Unable to validate location information with provider.
Recently I came across issue where customer was unable to validate location information with emergency (E911) service provider. To validate location information with Service provider is important step because without validation Location information cannot dispatch to by a Public Safety Answering Point (PSAP).

Customer has SIP trunk from well-known E911 service provider. However they run below command let using PowerShell (Open PowerShell as Administrator)

Get-CsLisCivicAddress | Test-CsLisCivicAddress –UpdateValidationStatus
It gives error message:
Test-CsLisCivicAddress : The request was aborted: Could not create SSL/TLS secure channel.
1.     Assuming that you have already added all network subnet to LIS database if not then use below command to add each subnet with location information (physical address):
Set-CSLisSubnet -Subnet -Description "PrivateSubnet" -Location "House" -CompanyName "" -MyHome "1235" -HouseNumberSuffix "" -PreDirectional "" -StreetName "Wildwood Ave" -StreetSuffix "" -PostDirectional "" -City Sunnyvale -State "CA" -PostalCode "94089"  -Country "USA"
After adding all subnet information publish the location information to LIS database using below command let.

2.     After completing first step check if Service provider name and validation URL correctly setup.

3.     Use below command to get service provider name and URL
Get-CsLisServiceProvider |fl

Result will show:
·        ServiceProviderName: E911Provider
·        ValidationServiceUrl:

4.     If validation URL and provider name is not correct then need to correct. In my case provider name validation URL was correct.

5.     Now run validation command to see validation status:
Get-CsLisCivicAddress | Test-CsLisCivicAddress -UpdateValidationStatus
I always received error like “Test-CsLisCivicAddress : The request was aborted: Could not create SSL/TLS secure channel.”
6.     Error explain that unable to create SSL/TLS secure channel for validation URL in order to validate location information. In my case authentication URL and service provider name shows correctly however this was setup by someone else using certificate and password but same is not available on Lync Front End server.  Hence need must have certificate to establish secure connection to Service provider URL.
7.     Get certificate and password from service provider and re-run the  below command to set the new configuration which will over write existing configuration and details.
$p= read-host -AsSecureString

Set-CsLisServiceProvider -ServiceProviderName -ValidationServiceUrl  

8.     Now command will you the setup validation URL correctly.
9.     Now you can run validation command to validation location information.
Get-CsLisCivicAddress | Test-CsLisCivicAddress –UpdateValidationStatus
This time you will see the result with validation status. So you will be able to validate LIS information with provider so it can dispatch to by a Public Safety Answering Point (PSAP).

Thank you


  1. For anyone seeing this error but isn't having any luck with Balu's resolution, we found that the command would run correctly on a different FE (we have 3). Not sure why one FE would work but the other wouldn't, but there it is.


Post a Comment

Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: ·User name: orgname\bilag ·Password: ************
Note: is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…