Registered Location. Sprint requires a valid United States Postal Service and Master Street Address Guide address for each End User’s primary work location addresses (“Registered Location”) to provide the Service. The primary mechanism for routing 911 calls to the correct PSAP is the Registered Location at the time a 911 call is placed. The routing of calls relies on the Registered Location information when communicating with emergency operators. If the Registered Location has not been updated, is not complete, or is not accurate, the 911 call may route incorrectly.
Registered Location. If you need to place an emergency call, you can dial the emergency 911 number through Xxxxxxxx’x VRS. To ensure your 911 call is routed to the proper emergency response center and to ensure that the emergency response personnel can send help to your physical location, Xxxxxxxx (as your default provider) needs to obtain the address from which you are placing the emergency call. You are responsible for providing Xxxxxxxx, as your default provider, or other VRS provider if you use their Video Relay Services to place a 911 call, an up- to-date Registered Location. If you fail to do so, the provider may not be able to obtain your location information and route your call to the appropriate emergency center or provide your physical location. If you change your Registered Location (e.g., move your residence or take your VRS calling device to another location) you must update your default provider with your new location information. After you update your VRS provider with your Registered Location, it will take some time (hours or more if there are issues reading or entering the address information provided) to activate 911 service at the provided address and, if a 911 emergency call is made prior to activation, then your call and the Registered Location information may not be automatically routed to the appropriate emergency personnel. If Xxxxxxxx is your default provider, you can inform Xxxxxxxx of your initial or new Registered Location by visiting xxx.xxxxxxxxxxx.xxx/xxxxxx, or calling 000-000-0000 from the Hardware or from the Operating Device with the Software. Some versions of the Software include an optional functionality called “Share Location.” If you elect to turn on the “Share Location” feature during a call, the Software will attempt to retrieve your current location via GPS (if you are using a GPS-enabled Operating Device) and you may elect to display your current address to you, the Xxxxxxxx interpreter, and/or to the person to whom you have placed the call. “Share Location” is an entirely optional feature, and it will not identify or otherwise track your location unless you elect to turn it on. Xxxxxxxx cannot guarantee that the “Share Location” feature will provide correct address information in every situation. Accordingly, you acknowledge and agree that “Share Location” is not a substitute for providing us with your Registered Location for purposes of 911 emergency calls.
Registered Location. YOUR SERVICE LOCATION WILL BE YOUR REGISTERED LOCATION. USE OF THE VOIP SERVICE FROM A LOCATION OTHER THAN YOUR REGISTERED LOCATION MAY CAUSE YOUR 911 CALL OR E911 INFORMATION TO BE ROUTED TO THE WRONG PSAP, MAY CAUSE EMERGENCY RESPONSE PERSONNEL TO BE DISPATCHED TO THE WRONG ADDRESS, AND MAY RESULT IN OTHER PROBLEMS WITH ACCESSING AND OBTAINING EMERGENCY SERVICES, INCLUDING BUT NOT LIMITED TO YOUR INABILITY TO RECEIVE EMERGENCY SERVICES. AS A RESULT, YOU MUST UPDATE YOUR REGISTERED LOCATION WITH PROVIDER BEFORE USING THE VOIP SERVICE AT A NEW LOCATION. EVEN IF YOU USE THE VOIP SERVICE FROM YOUR REGISTERED LOCATION, TRYING TO CALL 911 OR OBTAIN EMERGENCY SERVICES THROUGH A 911 CALL MAY FAIL FOR A NUMBER OF REASONS, INCLUDING:
Registered Location. Because a voice-over-IP call can be made anywhere a User has an Internet connection, the caller’s telephone number will not necessarily correspond with the caller’s physical location. All customers must therefore provide Cisco with a “Registered Location” for each User when Cisco Calling Offers service is set up. The “
Registered Location. Because a voice-over-IP (“VoIP”) call can be made anywhere a User has an Internet connection, the caller’s telephone number will not necessarily correspond with the caller’s physical location. All customers must therefore provide Cisco with a “Registered Location” for each User when Cisco Calling Offers service is set up. The “Registered Location” is the street address where the Users will be using the service. If You or Your Users move the equipment to a new location, You or Your Users must immediately update the Registered Location with the new physical location of the device in Your Control Hub. If the Registered Location is not updated, any emergency calls made from the device may be sent to the wrong emergency response center and will transmit incorrect location information to emergency responders, delaying emergency assistance to Your Users. Customers with multiple Users are responsible for ensuring that an accurate and up-to-date Registered Location is maintained for each User, and that their Users are aware of how the Registered Location can be changed. There may be a delay in making the updated Registered Location available for routing and to emergency call centers. You are responsible for notifying, and You agree to notify, any User or potential Users of Your VoIP services of the nature and limitations of emergency calls on the VoIP services described in this Policy.
Registered Location. Sprint requires a valid address for all End Users‟ primary work location addresses (“Registered Location”) to provide ISIP. The primary mechanism for routing emergency calls to the correct Emergency Service is the Registered Location at the time an emergency call is placed. The routing of calls relies on the Registered Location information when communicating with emergency operators. If the Registered Location has not been updated, is not complete, or is not accurate, the emergency call may route incorrectly.
Registered Location. Client is required to provide to ENA the physical location(s) at which the Service will be utilized (“Registered Location”). Client is required to notify ENA via phone (0-000-000-0000) or email (xxxxxxx@xxx.xxx) if Client needs to update one or more Registered Locations. Client may opt-in for self-management of 9-1-1 records via a supplied web portal. Client must designate individuals who will be granted access to the web portal and who will be responsible for maintaining 9-1-1 data.
Registered Location. UniVoIP will register your Main Business Telephone Number (MBTN) with Public Safety Answering Point (PSAP) for 911 service. Customer agrees to provide UniVoIP with complete and accurate Registration Location for every of Customer’s sites prior to service activation of each site. In case of any changes to the Registered Location, Customer must contact UniVoIP by calling 000-000-0000 during regular business hours to provide the updated Registered Location information.
Registered Location. Because a VoIP call can be made anywhere a User has an Internet connection, the caller’s telephone number will not necessarily correspond with the caller’s physical location. All customers must therefore provide Cisco with a “Registered Location” for each User when VoIP service is set up. The “
Registered Location. Use of the Telephony Service from a location other than Customer’s Registered Location may cause Customer’s 911 call or E911 information to be routed to the wrong PSAP, may cause emergency response personnel to be dispatched to the wrong address, and may result in other problems with accessing and obtaining emergency services, including, but not limited to, Customer’s inability to receive emergency services. As a result, Customer must update Customer’s Registered Location with Wisper before using the Telephony Service at a new location. To update Customer’s Registered Location, Customer should log into the Telephony Service web portal at xxxxx://xxxxx.Xxxxxx.xxx and choose “Manage E911 Info”, or contact Wisper Technical Support at 800-765-7772, or at the address set forth at xxxx://xxx.XxxxxxXXX.xxx.
