FWIW YOu need to provide per room routing but a DID per room isnt required if you can make that happen other ways. For example, West now offers in their NG platform to send an XML body with the invite to provide details intra-building routing. You still need to provide descreet callback info, but for that suite of 100 hotel rooms, you could use a block of 5-10 numbers and assign them to each room that dials 911 for a temporary callback period, this will give you bi-directional reachability from a 911 perspective without managing and provisioning hundreds of sparsley used numbers. You could also leverage their enterprise 911 option where you send a distinct sip URI that is statically mapped to a location (address and room/floor etc) and they will masquerade to the PSAP with a unique phone number. Personally if i were designing a system today (and I am) i would take the first option and supply the info in the outbound invite for maximum flexibility. On 4/4/2019 11:22 PM, Matthew Yaklin wrote:
That is correct. A DID for every phone and listed by e911. For example in NH it is law schools have it now days to get their special erate funding. When they call 911 they see very detailed information about floor, room, etc.. and the phone can be called back directly. We do it for every customer that has that specific need.
Matthew Yaklin Network Engineer FirstLight 359 Corporate Drive ? Portsmouth, NH 03801 Mobile 603-845-5031 myaklin at firstlight.net | www.firstlight.net This email may contain FirstLight confidential and/or privileged information. If you are not the intended recipient, you are directed not to read, disclose or otherwise use this transmission and to immediately delete same. Delivery of this message is not intended to waive any applicable privileges.
------------------------------------------------------------------------ *From:* Colton Conor <colton.conor at gmail.com> *Sent:* Thursday, April 4, 2019 8:40:11 PM *To:* Matthew Yaklin *Cc:* Jason Kuylen; VoiceOps at voiceops.org *Subject:* Re: [VoiceOps] Hotel Phone So if you had e911 per room, that would be quite a bit of e911 charges. Most hotels I have seen have a 10 to 1 ratio for rooms to phone lines. So a 100 room hotel gets 10 phone lines from the LEC. Are you saying we would have to pay bandwidth.com <http://bandwidth.com> or whomever we got our e911 from a separate e911 charge per room? Isn't e911 tied to DID? In that case you would need a DID per hotel room? To actuately say room 302 is on floor 3, and room 302 for example.
On Thu, Apr 4, 2019 at 11:21 AM Matthew Yaklin <myaklin at firstlight.net <mailto:myaklin at firstlight.net>> wrote:
I imagine you want to make sure E911 information is super accurate with actual floors and room numbers. Physical address and call back number is correct. By making that accurate and having the customer sign that phones cannot move you cover a serious base. Perhaps even a sticker on the phone saying such would be great to.
*Matthew Yaklin* Network Engineer *FirstLight* 359 Corporate Drive ? Portsmouth, NH 03801 Mobile 603-845-5031 myaklin at firstlight.net <mailto:myaklin at firstlight.net> | www.firstlight.net <http://www.firstlight.net> /This email may contain FirstLight confidential and/or privileged information. If you are not the intended recipient, you are directed/ /not to read, disclose or otherwise use this transmission and to immediately delete same. Delivery of this message is not intended/ /to waive any applicable privileges./
------------------------------------------------------------------------ *From:* VoiceOps <voiceops-bounces at voiceops.org <mailto:voiceops-bounces at voiceops.org>> on behalf of Jason Kuylen <kuylenj at eastex.com <mailto:kuylenj at eastex.com>> *Sent:* Thursday, April 4, 2019 12:08:32 PM *To:* VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> *Subject:* Re: [VoiceOps] Hotel Phone
I?ve never heard of any other 911 requirement for hotel or business phones outside of not have to dial 9 to dial 911, ie 9911. Kari?s Law.
Can anyone provide a link with more information?
Thanks.
Important/Confidential: This communication and any files or documents attached to it are intended only for the use of the person(s) or entity to which it is addressed. It contains information that may be confidential and exempt from disclosure under applicable law. If you are not the intended recipient of this communication, you are hereby notified that the copying, disclosure, distribution, storage, retransmission or other use of this communication is strictly prohibited. If you have received this communication by mistake, please notify the sender immediately and destroy all forms of this communication (electronic or paper). _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops