Phones #

This section of settings provides the tools to manage the configuration/keymaps of supported devices.

Phones can be added to the system individually or imported in bulk before they are then assigned to customers and users.

Keep reading this page for information on provisioning and supported hardware. Otherwise, follow the links below for information on how to add/edit phones or specific information on configuration and keymap options:

• Devices -> Adding/Editing devices
• Configuration -> Details on available configuration options
• Keymap -> Details on available softkey types

warning

When provisioning a phone which has been used on a previous system, ensure it has been completely removed from that system before adding it to ~.Dimensions.~. If it is not correctly removed, ~.Dimensions.~ will not be able to successfully provision the phone on the manufacturer's provisioning server.

Every device that is managed by ~.Dimensions.~ will be provided with configuration files and firmware. When a device makes a provisioning request, it is passed a combination of the default 'Configuration Options' and any configuration overridden at the individual device's level.

Each device will receive provisioning updates in the following ways:

• Phone Reboot - The phone is manually rebooted
• Daily Re-sync - By default, all devices are configured to re-provision on a daily basis
• Configuration Update - Devices are dynamically pushed configuration updates when there has been a change through the customer (or reseller) portal

~.Dimensions.~ supports configuration and keymap provisioning for a subset of SIP phones. Hardware from other manufacturers can be used on the system, but must be manually provisioned.

~.Dimensions.~ supports Yealink phones and automatic provisioning via the Yealink RPS. Once added to the ~.Dimensions.~ portal, a defaulted Yealink phone will automatically find the ~.Dimensions.~ service and will download the required configuration, keymaps and firmware.

Supported phones:

The following table lists all Yealink phones which are supported for automatic provisioning.

Series	Models	Directory Support	Comments
T1x	T19P1, T19P E21	1* Directories 1,000 contacts per directory
T2x	T21P1, T21P_E21 T23P1, T23G1 T26P1 T27G1, T27P1 T28P1 T29G1	3* Directories 1,000 contacts per directory
T3x	T30, T30P T31, T31P,T31G T32G1 T33P, T33G T34W	5* Directories 1,000 contacts per directory
T4x	T40G1, T40P1 T41U, T41G1, T41S, T41P1 T42U, T42G1, T42S T43U T44U, T44W T46U, T46G1, T46S T48U, T48G1, T48S T49G	5* Directories 1,000 contacts per directory
T5x	T53, T53W T54W, T57W, T58, T58W	5* Directories 1,000 contacts per directory
VPx	VP59	5* Directories 1,000 contacts per directory
Wx	W52P,W56P, W60B, W70B, W80B, W90B	5* Directories 1,000 contacts per directory		Line 2 onwards need to be configured manually
CP	CP920, CP930W, CP960 CP925, CP935W, CP965	5* Directories 1,000 contacts per directory>
AX	AX83H, AX86R	1* Directories 1,000 contacts per directory>

info

\* One of the directories on each phone is used for internal user contact records.

warning

Any phone labeled Beta is being verified for a future release and is not yet supported.

---

1. This phone does not support TLS 1.2. ↩︎

~.Dimensions.~ supports Poly phones and automatic provisioning. Once added to the ~.Dimensions.~ portal, a configured Poly phone will download the required configuration, keymaps and firmware.

Supported phones:

The following table lists all Poly phones which are supported for automatic provisioning.

Series	Models	Directory Support	Comments
VVX	VVX101, VVX150 VVX201, VVX250 VVX300, VVX301, VVX310, VVX311, VVX350 VVX400, VVX401, VVX410, VVX411, VVX450 VVX500, VVX501 VVX600, VVX601 VVX1500	2* Directories 500 contacts per directory
SoundPoint	IP321 (Beta), IP330 (Beta), IP331 (Beta), IP335 (Beta) IP450 (Beta) IP550 (Beta), IP560 (Beta) IP650 (Beta), IP670 (Beta)	2* Directories 500 contacts per directory
SoundStation	IP5000 (Beta), IP6000 (Beta), IP7000 (Beta)	2* Directories 500 contacts per directory
Edge	E100 (Beta) E220 (Beta) E300 (Beta), E320 (Beta), E350 (Beta) E400 (Beta), E450 (Beta) E500 (Beta), E550 (Beta)	2* Directories 500 contacts per directory
Trio	8500 (Beta), 8800 (Beta)	2* Directories 500 contacts per directory

info

• One of the directories on each phone is used for internal user contact records.

warning

Any phone labeled Beta is being verified for a future release and is not yet supported.

~.Dimensions.~ supports Mitel phones and automatic provisioning via the Mitel RCS. Once added to the ~.Dimensions.~ portal, a configured Mitel phone will download the required configuration, keymaps and firmware.

Supported phones:

The following table lists all Mitel phones which are supported for automatic provisioning.

Series	Models	Directory Support	Comments
68xx	6863i, 6865i,6867i 6869i, 6873i	2* Directories 2,000 contacts per directory
69xx	6905, 6910, 6915, 6920/6920w, 6930/6930w,6940/6940w 6970	2* Directories 2,000 contacts per directory
53xx	5312, 5320, 5324 53301, 53401, 5360 5320e, 5330e, 5340e	1* Directory 50 contacts	Phones need to be placed in SIP mode first.

info

\* One of the directories on each phone is used for internal user contact records.

---

1. This phone does not support TLS 1.2. ↩︎

~.Dimensions.~ supports Cisco phones and automatic provisioning via the Cloud Device Activation (CDA). Once added to the ~.Dimensions.~ portal, a configured Cisco phone will download the required configuration, keymaps and firmware.

info

Only the 8800/7800 series of Cisco phones are supported for automatic provisioning.

Supported phones:

The following table lists all Mitel phones which are supported for automatic provisioning.

Series	Models	Directory Support	Comments
68xx	6821, 6841,6851,6861, 6871	Not Supported	Automatic provisioning not supported
78xx	7811, 7821, 7841, 7861	Not Supported
88xx	8811, 8841, 8845, 8851, 8861, 8865	Not Supported
ATA	ATA1911, ATA1921	Not Supported

---

1. This phone does not support TLS 1.2. ↩︎

Any SIP phone which is not listed above can still be provisioned on ~.Dimensions.~, but it will need to be manually provisioned. This means manually configuring:

• SIP Credentials
• General Phone Config
• Keymaps for feature codes

Please refer to the Generic SIP Phones section for more information.