DinkyDonkey

Btw @Karl Stallknecht, @littleredtech is one of our staff and we're currently on 2600hz Hosted. I know different installs and configurations could modify this behavior so wanted to be clear.

One of our larger clients has begun using hotdesking. Currently the options are very limited: enable on a user, allow to hotdesk to multiple devices, and set a PIN. Looking at github.com I don't see much more information besides those options. Questions we have, Is there a way to set a timer so the user auto-logs out? Is there a way to see who is hotdesking where through the API? If a user hotdesks a phone it's hard to tell what state the phone is in (default, or hotdesked). Or is there a way for the user sitting at the phone to tell without calling an extension (default or hotdesk) from another phone? https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/users.md hotdesk.enabled Determines if the user has hotdesking enabled boolean() false false hotdesk.id The users hotdesk id string(0..15) false hotdesk.keep_logged_in_elsewhere Determines if user should be able to login to multiple phones simultaneously boolean() false false hotdesk.pin The users hotdesk pin number string(4..15) false hotdesk.require_pin Determines if user requires a pin to change the hotdesk state boolean() false false hotdesk The user hotdesk parameters object() {} false https://github.com/2600hz/kazoo/blob/003c6bb44a9e1e28fcb76afa08b0cb89741170cc/applications/callflow/doc/hotdesk.md action The action to take for hotdesking `string('logout' 'login' 'toggle' 'bridge')` id Hotdesk ID string() false interdigit_timeout How long, in seconds, to wait between keypresses integer() false

I don't think it's urgent as using standard 911 and multiple emergency TNs works well, however great to hear that it's in the pipeline.

@mc_ @Darren Schreiber looks like Bandwidth.com offers what they call "dynamic location routing" where you can send additional details, https://www.bandwidth.com/9-1-1/dynamic-location-routing/ and this is from their pdf "Sophisticated 9-1-1 routing that uses PIDF-LO (Presence Information Data Format-Location Object), a standard that’s used to represent an address/ location in XML format". I found details on PIDF-LO here: https://tools.ietf.org/html/rfc4119 and https://www.ietf.org/rfc/rfc5139.txt @safarov Kazoo currently uses standard 911 routing where the emergency caller ID on the device, user, or account has an address in a database which is sent to emergency dispatch. There is no additional information provided, however this thread is to talk about how more details could be provided.

When dialing in from an external number and either entering an extension or using the directory we'd like the call to go straight to voicemail. For internal calls we'd like the call to ring the user devices first. I believe I'm going to have to edit the callflow with the API and prefix a 0 (to send to voicemail) if the call is external. Has anyone done this or does anyone have any advice?

Thank you Bobby for the referral for Judy at Telecom Professionals, Inc.

Can you expand the TPI out for me or point me to their website? Thank you!

Thanks for update Izabell, glad to hear I didn't miss anything.

Is KazooCon 2017 online still happening tomorrow and Wednesday? I have noticed anything in the newsletters and am not sure where to get this information for access. When it happens I'd like to block off the time to participate as much as possible.

How is everyone handling taxes through the Hosted Kazoo? My plan is to use external billing and SureTax to calculate taxes. SureTax has recommended tax professionals to help file in each state of service. What is everyone else doing that is compliant? I've noticed many providers are not federal and state compliant on VoIP taxes and e911 and I'm looking for direction from those that are.

Thanks Darren, this was my thinking too, glad to see it confirmed on your end. I don't think what they want is available yet, so I'm going to pitch it as they can divide up the property as granular as they want, and pay for each e911 enabled DID, and then tie that to the location. It's nice knowing it's unlikely any other vendor will be able to deliver exactly what they want.

I'm answering an RFP with a request for advanced e911 location based on the port the phone is plugged into. I imagine this can be done crudely with a unique e911 number for each building, floor, room (depending on granularity) and then updating the devices using LLDP and the Kazoo API. Has anyone tackled granular e911 locations for larger buildings? I've noticed in Bandwidth newsletters that they are working on this, https://www.bandwidth.com/9-1-1/

We'd like to get started on some simple Monster-UI apps. Maybe a talk/training on creating an App start to finish with some advanced things such as storing app specific data in the database?