Plau
-
Posts
107 -
Joined
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Plau
-
-
It's on my to-do list, but I haven't had time to work on it since it's lower on my priority list. I have an HT802 for testing. I think all the HT8xx ATAs operate roughly the same, just different number of ports.
-
If you want Reseller settings applied to Accounts under Reseller2, then make changes to Reseller settings for Reseller2. Accounts will always inherit from the closest Reseller parent account. So, if you had something like
Master -> Reseller1 -> Reseller2 -> Account1 -> Account2
-> Reseller3 -> Account 3
-> Reseller4 -> Account4
-> Account5
All the Resellers inherit settings from Global/Cluster. Accounts 1 and 2 inherits settings from Reseller2. Account 3 inherits settings from Reseller3. Account 4 and 5 will inherit from Reseller4.
No one inherits from Reseller1 because there are no accounts that is a child of Reseller1 and not a child of another Reseller account. This is also true if you set the Master account as a Reseller.
I think a long time ago inheritance might have worked differently as our production cluster is setup with a MasterReseller account under the Master (superDuperAdmin) account. For organizational purposes, I can see the value of having a MasterReseller account, but as you can see, settings don't trickle down. It is confusing if you haven't been told about it. I did a talk about Inheritance in Provisioner at KazooCon 2 years ago, but never got around to writing a full documentation on how it works.
-
I'm a bit confused. Are you trying to update the provisioning URL the phone has set when you look through the phone's Web UI? Each time you update a device through the UI, it applies whatever is in the White-labeling setting to the provisioning URL in the phone's auto provisioning config file. When a phone fetches that file, it's updated without the need to factory reset. If you're changing it at the Reseller or Account level, just say yes to regenerating all the config files. Otherwise you would have to individually save a device for the settings to be applied.
-
It should work from Reseller down to Account and Device levels. If not then there's a bug, but it would also affect a lot of people.
There does exist a situation where Reseller settings won't be inherited. It's when you have accounts setup as: Reseller1 -> Reseller2 -> Account. Any Reseller level settings set for Reseller1 will not be applied to any accounts under Reseller2 nor would Reseller2. Inheritance is strictly from Global/Cluster -> Reseller -> Account -> Device.
-
Failover on the phones are just for media servers which if you have SRV records setup, those would handle them. The reason we use SRV records over setting primary and secondary proxies is because some phones, like Polycoms, alternate between the two instead of falling back to the secondary proxy if and only if the first one has failed. SRV records are also independent of the media servers, to my knowledge, so regardless of the state of each media server, the SRV records can be reach no matter what.
Maybe this guide can help answer some of your questions about setting up SRV records: https://docs.2600hz.com/user_guides/doc/provisioner/failover/failover/
As for GEO-DNS, I'm not sure what you're talking about. Can you elaborate?
-
Not sure if you got this working or not, but here's a guide I've written on how to provision Obihais: https://docs.2600hz.com/user_guides/doc/provisioner/obihai/obihai_provisioning_guide/
-
Try resaving the device through the UI, I think I figured out the issue with the "Update device settings" being stuck.
-
The new MAC range has been added to production and you can provision Yealinks with the new MAC range.
-
I didn't know that was a feature of Yealinks. I do know that Polycoms could update configurations without rebooting, but our policy has been enforcing rebooting when updating configs.
-
@esoare So it looks like there's something else I overlooked. The reason why there are multiple pages of keys set to Line 1 (and I think this is the issue you were actually talking about) is because all combo keys are defaulted to be Line Keys and with a recent update, the combo keys > number of accounts are now set to blank instead of the last account number. I'm working on solving that now.
-
@esoare That might fix the problem, but it's not the best solution. My intention with the work I did was that you could simply regenerate the config file, restart the phone and the issue would be fixed.
-
@esoare Can you resave your T46S/T46G on production and reboot to see if it's still an issue? I had to test the fix on production because I could not reproduce it in my dev environment. Currently, only those models have changes, but I have updated all the templates. I'll update this Friday evening if I don't find any issues.
-
I think I know what's going on. There's a bug where the combo keys are offset by 1 causing both combo key 1 and 2 to be set to Line Key for Line 1. I just worked on a fix yesterday which I tested and fixes that issue.
-
Inherit Account 1 only works on the first key. All subsequent keys are set to their corresponding key number (e.g. key 2 to account 2) and then it's set to the last account if there are more keys than lines. This was done a long time ago and we have kept this functionality while not updating the UI. I did try to fix it with adding an "Auto" setting, but it doesn't look like it took.
I don't work on the UI, but the fix would be to add logic to the front end when generating the UI. All Provisioner provides is a json of the settings for the UI to display.
It's best practice to always set the account. I was told not to remove the auto increment for account to key pairing because it was a feature request in the past.
-
17 hours ago, esoare said:
So a better name would be "IDLE LOGO" OR a better description to show it's kinda the screen saver?
I guess IF you get the Wallpaper setting done, it would be called Wall Paper.
? If the LOGO isn't supported, should that not even be an option on the models that don't support it?
esoare
Yeah, as I said, I didn't work on it, so at the time, that might have been the only "Logo" you could change. Or that might have been the "Logo" feature request. This has been around for at least 2 years and all the Yealink phones inherit this setting, so at the time there probably wasn't any phones that didn't support it. I'll remove it on the next update.
17 hours ago, extremerotary said:I think a good improvement upon the advanced provisioner would be to have a section where a user can put additional "custom code". These would be parameters otherwise unset by the template used in the provisioner. We have this in our provisioner and our customers love it. It allows them to customize or otherwise improve the default template and tailor it to their customers' needs.
For Polycoms and Yealinks using v81 firmware, there is a newly added feature through the UI where you can add links to your own custom config files. Both brands support loading multiple config files and has priority order, and I've made it such that any custom config files loaded is applied over our Provisioner's generated config file.
-
So, I wasn't very clear in my explanation earlier. My bad.
There are multiple "logo" settings in the config file. The one you see as "Logo" in Advanced Provisioner sets the image for the idle screen. That one specifically isn't supported by the models I listed in my previous post. This is the setting I'm talking about that is set through Advanced Provisioner: http://support.yealink.com/faq/faqInfo?id=219
The Wallpaper setting, which is what esoare has posted about, is not something that can be set through Advanced Provisioner at this time. I'm assuming that Jack set the Wallpaper for the T29G through the phone's web UI.
-
Thanks esoare for the work around while I was tracking down and fixing the bug. I've hot patched it so it's fixed on production.
-
Hi,
While I didn't work on that, the Logo setting are for displaying a Logo for the idle screen. It's not applicable to T48G/T48S/T46G/T46S/T29G IP phones. If you're looking to set wallpapers, it's currently not supported through the UI for any of the Yealink phones.
-
I just tested by changing a T23P to a T23G and I didn't run into any issues on sandbox.
What it sounds like is that the device is in another account. Saving a device in Smart PBX and Callflows uses the same operation to save to Provisioner. If you saved on either Smart PBX or Callflows, and it doesn't show up in Advanced Provisioner, that generally means the device is in another account.
-
22 minutes ago, esoare said:
Plau,
I wouldn't recommend that. I did the following, and the Phone was removed from Advanced Provisioner.
Built a Smart PBX using T42G template.
After provisioning (which didn't look quite right)
I changed the device type in Callflows/Devices to T42S.
That removed the phone from advanced provisioner.
But the phone was in SmartPBX
I Tried re-saving the Smart PBX device after making minor changes, but that did not work.
So, I would not recommend changing the Device type in CallFlows.
I'll hope for success this Friday.
Oh, I didn't think that would happen. It didn't before, so that's why I recommended that action.
-
11 minutes ago, esoare said:
I know I probably could accomplish through regular provisioning on the Yealink T42S's. But I don't want to do things twice...
You can provision it as a T42G, then later go into the Callflows App -> Devices and change the device type from T42G to T42S. Afaik, that's the only place to change a device type after it's been added.
-
It didn't happen last week because I ended up finding a couple more issues and didn't have time to make a full announcement for the upgrade. We will be posting an announcement either today or tomorrow about the upgrade scheduled for this Friday along with release notes of changes and fixes to Provisioner, so look out for that update.
-
It looks like the firmware file was missing so it didn't ever upgrade, just downgraded. Sorry about that. I just added the firmware file so the phones will now upgrade.
Thanks for noting that the w56 doesn't work with v73 firmware. I'll update the w5x series to use v80 by default since both models share the same y0000000000xx.cfg file which is how we setup default firmwares.
-
Hi,
The working url is provisioner.sandbox.2600hz.com.
Provisioner Logs
in Provisioner Service
Posted
Currently, no, there's no way of viewing the logs. I have built an API to pull it, but the server isn't setup to give the API access to view the logs. Also there's no UI component to display the logs. We have a UI refresh planned and I'll see about getting this into the UI.