Installation guide

Administrator Level Options
41-001561-00 REV00 – 10.2014 3-41
Softkeys, Programmable Keys, Expansion Module Keys
A user or administrator can assign specific functions to softkeys, programmable keys, or expansion module keys. The avail-
able keys for configuration depend on the IP phone model as shown in the following table.
*The M680i expansion module consists of 16 softkeys. You can have up to 3 expansion modules on an IP phone totalling 48
softkeys. Valid for 6865i, 6867i, and 6869i phones.
**The M685i expansion module consists of 3 pages of 28 softkeys (for a total of 84). You can have up to 3 expansion modules
on an IP phone totalling 252 softkeys. Valid for 6865i, 6867i, and 6869i phones.
The softkey, programmable key, or expansion module key can be set to use a specific function. Available functions depend
on the IP phone model.
Reference
For more information about key functions see Appendix A, the section, “Softkey/Programmable Key/Keypad Key/Expan-
sion Module Key/Hard Key Parameters” on page A-174.
For information about configuring softkeys, programmable keys, and expansion module keys, see Chapter 5, the section,
“Softkeys/Programmable Keys/Expansion Module Keys” on page5-104.
Action URI
The IP phones have a feature that allows an administrator to specify a uniform resource identifier (URI) that triggers a GET
when certain XML events occur. The Action URI feature prevents the phones from hanging if the Action URIs should fail.
The phones also support transparent, non-blocking, XML post execute item URIs.
The IP phone XML events that support this feature are defined in the following table.
IP Phone Model Softkeys Expansion Module Keys Programmable Keys
6863i - Not Applicable 3
6865i - 16 to 48***
(Model M680i)
84 to 252****
(Model (M685i)
8
6867i 10 16 to 48***
(Model M680i)
84 to 252****
(Model (M685i)
-
6869i 17 16 to 48***
(Model M680i)
84 to 252****
(Model (M685i)
-
Action URI Description
Startup Specifies the URI for which the phone executes a GET on when a startup event occurs.
Successful Registration Specifies the URI for which the phone executes a GET on when a successful registration event occurs.
Registration Event Specifies the URI for when registration events occur or when there are registration state changes.
Note:
This action URI is not called when the same event is repeated (for example, a timeout occurs again when registration is
already in a timeout state.)
Incoming Call Specifies the URI for which the phone executes a GET on when an incoming call event occurs.
Outgoing Call Specifies the URI for which the phone executes a GET on when an outgoing call event occurs.
Offhook Specifies the URI for which the phone executes a GET on when an offhook event occurs.
Onhook Specifies the URI for which the phone executes a GET on when an onhook event occurs.