Users Devices
From Taridium
(Difference between revisions)
(New page: 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 creat...) |
|||
| Line 1: | Line 1: | ||
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. | 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. | ||
The following device brands are supported: | The following device brands are supported: | ||
* Aastra | * Aastra | ||
| + | :: support for XML push | ||
* Polycom | * Polycom | ||
* Cisco | * Cisco | ||
Revision as of 18:47, 24 November 2008
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.
The following device brands are supported:
- Aastra
- support for XML push
- Polycom
- Cisco
- Linksys
- Grandstream (limited)
- Generic Device Support
Device Templates are automatically created by adding a SIP/IAX Channel Template.
