-
Posts
54 -
Joined
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by DinkyDonkey
-
-
@Plau thanks for the prompt reply! Client is having issues however I believe it's DHCP option 66 related and not due to this, however as I was reviewing our related tickets I realized this was an unknown step. Thanks for clarifying this and getting it automated!
-
@Plau what's the status on Provisioning for Polycom phones? Do you still need to manually enable "Tag SN to UA" through the phone's GUI after a factory reset? If so that really hurts the deployment of Polycom phones.
-
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.
-
@esoare tool is done and working successfully. I'll update when we post it to our website, however if anyone needs it before then please PM me. So far it only works with Yealink, however we'd like to add Polycom and Cisco next.
-
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
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
-
This is happening to us too. @Plau does this require setting "Tag SN to UA" (found on the phone's GUI, Settings, Provisioning Server) after each factory reset? If so, we really need to figure out a solution for this as this is a manual step on each phone and we prefer zero touch using DHCP options.
BTW, looks like the customer that had this had reset around Sept 12th, as he opened a ticket with us on the 13th. I think my question summary is: did this only impact Polycom reset around this time, or will all Polycom's require this manual change going forward?
-
Are you on the open source or hosted? I had this issue on open source and could not figure it out! Posting here so if someone replies I'll know.
-
Some of the sales guys at Alloy CP moved to Vital Communications (vitalcomm.net). I haven't ordered from them yet but I really liked my reps so will be trying them in the future. I haven't used Jenne yet however they are looking good and their Yealink guy was also at the most recent KazooCon.
-
We have a client with 200 Yealink phones and a good reason to factory reset all of them. This can be a bit tedious so we decided to make this a bit easier with a Python tool.
Currently it will work by running the code against a csv file with ipv4 addresses, and credentials if different from defaults. It will try both http on 80 and https on 443 and then write out a new csv with the devices, their MAC, model, firmware, connection status (if http or https were non responsive) and then the result of the command (reboot or factory reset).
We thought about having the option to feed a sheet of MAC addresses and if you're on the same network it will discover the IP addresses, however for now we'll just provide a command that you can run to get IPs from MACs instead.
We'd like to share this with everyone so we're cleaning it up and wanted to ask for feedback in the case it changes any design decisions.
-
@Plau I'm having a problem where my custom config URLs are not being pulled. They were working August 2nd (just started testing them recently) however they are no longer being fetched at all if I look at my nginx logs.
I opened up a support ticket just now titled "Advanced Provosioner Custom Config File URL is not pulling config" however wanted to bring this to your attention here as it might be related.
-
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.
-
Thanks @SPC-Tim. What does "unlock" technically do to the phone? Is it only meant to prevent the provisioning URL from being changed?
-
On Yealinks this is what I'm seeing, "If you go change the provisioning URL under Advanced Provisioner, this will change it for any new devices or factory resets, however existing devices will continue to use the old provisioning URL."
Without doing a factory reset I don't see how to change the provisioning URL. Do I have to do an unlock on the phone first?
-
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?
-
Thanks @esoare
This is a Yealink T23G
Advanced Provisioner, Account Settings, Primary Address manually set to us-west, Secondary Address us-central.
Advanced Provisioner, Device config shows inheritance for these fields.
Looking good with a fresh device.
Seems like the issue I was having was when I originally created devices I had primary and secondary as ingheritance all the way up, and the devices within Advanced Provisioner manually set them instead of using inheritance all the way up. I'm going to test this more to verify that.
-
All of my Yealink's receive us-east as the outbound proxy and there's no options that I see in the Advanced Provisioner to change this. For now all of my clients are on the West coast so I'd like to ensure us-west is being used.
I set the SIP primary to us-west and secondary to us-central and am using DNS/NAPTR
This is with 2600hz's hosted domain, no white labeling applied.
-
prov-dhcp = option 43 or 66 URL
prov-ui = URL configured in Advanced Provisioner, Account Settings, White Labeling URLs
prov-2600hz = 2600Hz provisioning URLFor visibility I am proxying my provisioner URL to 2600hz and it's working well. Only issue is if I ever want to change that URL.
proxy: prov-dhcp/ui to prov-2600hz
prov-dhcp and prov-ui are likely the same however I'm separating them here to explain what happens.- Using DHCP option 43 or 66 you set provisioning URL (http://prov-dhcp),
- Phone connects and gets configs, this SETS the provisioning URL on the phone and option 43 or 66 will no longer apply.
- Now the phone's provisioning URL is set to (http://prov-ui)
- If you go change the provisioning URL under Advanced Provisioner, this will change it for any new devices or factory resets, however existing devices will continue to use the old provisioning URL.
Is it possible to reprovision the phone to set the new URL without a factory reset? Or to trigger a factory reset remotely through the Advanced Provisioner?
-
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.
SMS client for PC & Mobil
in PSTN, Software, and Services
Posted
@FASTDEVICE please post pricing or send me a DM for pricing. We'd be interested in exploring your capabilities to see if it could work for some of our customer requests. Please note we also built out an SMS system unrelated to Kazoo (before they supported SMS) and might be updating it to work with Kazoo, so if you have concerns about competitors or anything like that ignore this. We don't steal IP or anything like that but just wanted to be transparent.