Users Devices
From Taridium
(→Device List) |
|||
| Line 18: | Line 18: | ||
: support for Auto-Provisioning | : support for Auto-Provisioning | ||
: support for boot | : support for boot | ||
| - | * '''Linksys''' | + | * '''Linksys (Cisco SPA Series)''' |
: support for Auto-Provisioning | : support for Auto-Provisioning | ||
: support for boot | : support for boot | ||
Latest revision as of 15:01, 16 February 2011
Contents |
Device List
In ipbx devices control how phones are provisioned. Phones can be connected to ipbx with or without a device definition. Devices need to have a MAC address associated and are usually created automatically when creating a new user. Devices are always based on a Channel Template which instructs ipbx how to create any provisioning files.
Some devices will feature centralized boot control and other management features. By selecting the 
symbol you can change the MAC address of the device transparently. This will automatically update the configuration file for the edited device. If you enter an existing MAC address ipbx will ask you whether you want to swap the two devices. This is particularly useful if you want to exchange two phones between users.
Be careful when deleting devices as this might cause your phone(s) to become unreachable. To re-create the device go to Users and select your device template and re-enter the MAC address.
The following device brands are supported:
- Aastra
- support for Auto-Provisioning
- support for XML push
- support for boot
- Polycom
- support for Auto-Provisioning
- support for boot
- Cisco
- support for Auto-Provisioning
- support for boot
- Linksys (Cisco SPA Series)
- support for Auto-Provisioning
- support for boot
- Grandstream (limited)
- support for Auto-Provisioning
- Generic Device Support
- support for Auto-Provisioning
Device Templates are automatically created by adding a SIP/IAX Channel Template. Your device type needs to be setup for auto-provisioning See Device Type Setup.
Generate Configurations
This interaction allows you to re-generate all existing configuration files if needed.
Reboot Devices
This interaction will attempt to reboot all supported devices. Please note that quite often it is not possible to reboot not properly registered or unreachable phones.
DHCP Leases
This interaction will list all local DHCP leases, or leases that haven been provided by ipbx remote lease client.
