locked
E911 Location Policy's RRS feed

  • General discussion

  • I am attempting to move forward with E911 location policies in our S4B topology.  Our org needs to have unique PSTN records in place so we can "Mask" the caller ID so the "Branch" line is passed along rather than the "Call Center" # that is normally passed along.

    Our problem is simply that under "Location Policy" we are unable to add the Sites we built so we can select the needed PSTN usages with the masked caller ID. The list does not include the sites we built , we do however see 1 site that is a mystery to us.

    How does S4B on prem find Sites under the Location Policy?

    Wednesday, September 14, 2016 2:28 PM

All replies

  • Look at this link

    https://blog.unplugthepbx.com/2011/07/06/lync-e911-deployment/

    You have to create the sites on the control pannel and also subnet and assign the subnet to the correct site.

    On the Site, you can assign the location policy


    regards Holger Technical Specialist UC

    Wednesday, September 14, 2016 2:44 PM
  • Thanks for the reply. I have created a site and assigned a subnet to that site. I can create a "User" Location policy and assign the PSTN usage record for that site BUT the user account location policy set to automatic does not show the users current location. I just get the "Global" location policy. The User policy is skipped. I was told by our E911 vendor that we need site polices and not User policies.. are they wrong?

    Wednesday, September 14, 2016 3:57 PM
  • These are two different things. The E911 policy is only for Emergency calls. If the user dial 911 the Elin Information will be send from SFB to the SIP trunk or your PSAP server.

    The Location information has also to be setup through the LIS service.

    https://technet.microsoft.com/en-us/library/gg398390%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396


    regards Holger Technical Specialist UC

    Wednesday, September 14, 2016 5:03 PM
  • This has been done. our LIS database is setup for this site in question and validated against the E911 providers database.

    We are just stuck a the USER's properties to updating when they move from one subnet (site) to another. They keep getting the "Global" site and not the configured "User" site location policy with the needed  PSTN

    Wednesday, September 14, 2016 5:11 PM
  • Therefore you have to implement Location based routing.

    https://technet.microsoft.com/en-us/library/jj994068%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

    The E911 Policy should work without Location base routing.


    regards Holger Technical Specialist UC

    Wednesday, September 14, 2016 5:17 PM