Enable/Disable Features on the Phone Side
The following sections provide the new enable/disable features on the IP phones in Release 1.3.1.
5.1.1 Enable/Disable Callers List & Missed Calls Indicator
New features have been added that allow an administrator to: - Enable/disable user access to the Callers List Enable/disable the Missed Calls Indicator. You can configure these features using the configuration files only (aastra.cfg and <mac>.cfg).
Configuring via the Configuration Files
The new configuration parameters for enabling/disabling Callers List and the Missed Calls Indicator are as follows.
Parameter Configuration Files: aastra.cfg, <mac>.cfg Enables or disables the callers list. If this parameter is set to 0, the Callers List can be accessed by all users. If this parameter is set to 1, the IP phone does not save any caller information to the Caller List. For 480i and 480i CT phones, the Caller List option on the IP phone is removed from the Services menu, and the Caller List key is ignored if pressed by the user. Boolean (false), 1 (true) callers list disabled: 1 Configuration Files: aastra.cfg, <mac>.cfg

callers list disabled

Description
Format Default Value Range Example Parameter -
missed calls indicator disabled
Description Enables or disables the missed calls indicator. If the missed calls indicator disabled parameter is set to 0, the indicator increments as unanswered calls come into the IP phone. If the missed calls indicator disabled parameter is set to 1, the indicator is disabled and will not increment as unanswered calls come into the IP phone. Boolean (false), 1 (true) missed calls indicator disabled: 1
Format Default Value Range Example

Page 5 of 44

Enable/Disable Redial, Conference (Conf), or Transfer (Xfer) Keys
New features have been added that allow an administrator to: - Enable/disable the Redial, Conference (Conf), or Transfer (Xfer) Keys You can configure these features using the configuration files only (aastra.cfg and <mac>.cfg).
The new configuration parameters for enabling/disabling Redial, Conf, or Xfer keys are as follows.
Parameter Configuration Files: aastra.cfg, <mac>.cfg Enables or disables the Redial key on the IP phone. If this parameter is set to 0, the key is active and can be pressed by the user. If this parameter is set to 1, pressing the Redial key is ignored, and the dialed number is not saved to the Redial List. Boolean (false), 1 (true) redial disabled: 1 Configuration Files: aastra.cfg, <mac>.cfg Enables or disables the conference key on the IP phone. If this parameter is set to 0, the key is active and can be pressed by the user. If this parameter is set to 1, pressing the Conf key is ignored. Boolean (false), 1 (true) conference disabled: 1 Configuration Files: aastra.cfg, <mac>.cfg Enables or disables the Xfer key on the IP phone. If this parameter is set to 0, the key is active and can be pressed by the user. If this parameter is set to 1, pressing the Xfer key is ignored. Boolean (false), 1 (true) call transfer disabled: 1

redial disabled

conference disabled

call transfer disabled

Page 6 of 44

Enable/Disable Directory

A new feature has been added that allows an administrator to: - Enable/disable the Directory You can configure these features using the configuration files only (aastra.cfg and <mac>.cfg).
The new configuration parameter for enabling/disabling the Directory is as follows.
Parameter Configuration Files: aastra.cfg, <mac>.cfg Enables or disables user access to the Directory on the IP phone. If this parameter is set to 0, users can access the Directory List via the IP phone UI. If this parameter is set to 1, the Directory List does not display on the IP phone and the Directory key is disabled. On the 480i and 480i CT the "Directory" option is also removed from the "Services" menu. Boolean (false), 1 (true) directory disabled: 1

directory disabled

Enable/Disable Call Forward
A feature has been added to the IP phones that allows an administrator to enable/disable the Call Forward feature. Disabling Call Forward removes the Call Forward information from the Aastra Web UI and the IP Phone UI. You can configure the enable/disable call forward feature using the configuration files only (aastra.cfg and <mac>.cfg).
The new configuration parameter for enabling/disabling Call Forward is as follows.
Parameter Configuration Files: aastra.cfg, <mac>.cfg Enables or disables the ability to configure Call Forwarding. If this parameter is set to 0, a user and administrator can configure Call Fowarding via the Aastra Web UI and the IP Phone UI using the "Call Foward" options. If this parameter is set to 1, all "Call Forward" options are removed from the Aastra Web UI and the IP Phone UI, preventing the ability to configure Call Fowarding. Boolean (false), 1 (true) call forward disabled: 1

call forward disabled

Page 7 of 44
Enable/Disable Suppression of DTMF Playback
A feature has been added to the IP phones that allows users and administrators to enable or disable suppression of DTMF playback when a number is dialed from the softkeys and programmable keys. DTMF playback suppression is disabled by default. Suppressing DTMF playback can be configured using the Aastra Web UI and the configuration files (aastra.cfg and <mac>.cfg).
Configuring via Aastra Web UI or Configuration Files
The new configuration parameter for enabling/disabling DTMF playback is as follows.

Parameter -

suppress dtmf playback Suppress DTMF Playback (in Web UI)
Aastra Web UI: Basic Settings->Preferences Configuration Files: aastra.cfg, <mac>.cfg
Enables and disables suppression of DTMF playback when a number is dialed from the softkeys or programmable keys. When you disable the suppression of DTMF playback and you press a softkey or programmable key, the IP phone dials the stored number and displays each digit as dialed in the LCD window. When you enable the suppression of DTMF playback, the IP phone dials the stored number and displays the entire number immediately in the LCD window, allowing the call to be dialed faster. Boolean (disabled), 1 (enabled) suppress dtmf playback: 1

Page 8 of 44

Global/Per-Line Ring Tones
A feature has been added to the IP phones that allows a user or administrator to enable/disable ring tones on a global basis or on a per-line basis. Ring tones can be set to five distinct rings. You can configure ring tones using the Aastra Web UI, IP Phone UI, or configuration files (aastra.cfg and <mac>.cfg). However, when using the IP phone UI, you can set global configuration only. Note: The 480i CT cordless handsets also come with four user-configurable ring tones, but they are not associated with the per-line ring tone feature.
Configuring via Aastra Web UI, IP PhoneUI, or Configuration Files
The new configuration parameter for setting ring tones on a global basis is as follows. Global Configuration
Parameter Aastra Web UI: Basic Settings->Preferences IP Phone UI: Options->Set Ring Tone Configuration Files: aastra.cfg, <mac>.cfg
ring tone Global Ring Tone (in Web UI)
Description Format Default Value
Globally sets the type of ring tone on the IP phone. Ring tone can be set to one of five distinct rings. Integer Aastra Web UI IP Phone UI Configuration Files Aastra Web UI & IP Phone UI Tone 1 Tone (Tone 1) Tone 1 Tone 2 Tone 3 Tone 4 Tone (Tone 1) 1 (Tone (Tone 3) 3 (Tone 4) 4 (Tone 5)

Configuration Files

Example

ring tone: 3

Page 9 of 44

Per-line Configuration

Parameter
lineN ring tone LineN (in Web UI)
Sets the type of ring tone on the IP phone on a per-line basis. Ring tone can be set to one of five distinct rings. Integer Aastra Web UI Configuration Files Global -1 (Global) Global Tone 1 Tone 2 Tone 3 Tone 4 Tone 5 -1 (global) 0 (Tone 1) 1 (Tone (Tone 3) 3 (Tone 4) 4 (Tone 5))

Aastra Web UI

line1 ring tone: 3

Page 10 of 44

Multiple SIP Outbound Proxy Servers on Per-Line Basis
For an administrator, a multiple SIP outbound proxy feature has been added to the IP phones that is configurable on a per-line basis. This feature allows all SIP messages originating from a line on the IP phone to be sent to an outbound proxy server. For example, if you have a Session Border Controller in your network, then you would enter the IP address for this controller as the SIP outbound proxy server. If you configure an outbound proxy and registrar for a specific line (for example, Advanced Settings->Line1), and you also configure a global outbound proxy and registrar (for example, Advanced Settings->Global SIP), the IP phone uses the global configuration for all lines except Line 1. Line 1 uses the outbound proxy and registrar that you configured for that line. You can configure this feature using the Aastra Web UI or the configuration files (aastra.cfg and <mac>.cfg).

The two new configuration parameters for SIP outbound proxies on a per-line basis are as follows. Per Line Configuration
Parameter Aastra Web UI: Advanced Settings->LineN Configuration Files: aastra.cfg, <mac>.cfg
sip lineN outbound proxy Outbound Proxy Server (in Web UI)
This parameter allows all SIP messages originating from a line on the IP phone to be sent to an outbound proxy server. For example, if you have a Session Border Controller in your network, then you would enter the IP address for this controller as the SIP outbound proxy server. Note: If you configure an outbound proxy and registrar for a specific line (for example, Advanced Settings->Line1), and you also configure a global outbound proxy and registrar (for example, Advanced Settings->Global SIP), the IP phone uses the global configuration for all lines except Line 1. Line 1 uses the outbound proxy and registrar that you configured for that line.
<IP address or fully qualifed domain name> 0.0.0.0 N/A sip line1 outbound proxy: ippbx.abc.com

Page 11 of 44

sip lineN outbound proxy port Outbound Proxy Port (in Web UI)
Description Format Default Value Range Example
Aastra Web UI: Advanced Settings->LineN Configuration Files: aastra.cfg, <mac>.cfg
The port on the IP phone that allows SIP messages to be sent to the outbound proxy server. Integer 0 N/A sip line1 outbound proxy port: 5060

SIP Transaction Timer

A new feature in Release 1.3.1 allows an administrator to configure the amount of time that the phone allows the callserver to respond to SIP messages that it sends. You configure this feature using the Aastra Web UI or the configuration files (aastra.cfg and <mac>.cfg).

sip transaction timer

Aastra Web UI: Advanced Settings->Global SIP ->Advanced SIP Settings Configuration Files: aastra.cfg, <mac>.cfg The amount of time, in milliseconds that the phone allows the callserver (registrar/ proxy) to respond to SIP messages that it sends. If the phone does not receive a response in the amount of time desginated for this parameter, the phone assumes the message has timed out. Valid values are 4000 to 64000. Default is 4000. Integer to 64000 sip transaction timer: 6000

Page 12 of 44

ToS, QoS, DiffServ/VLAN/DSCP
New features in Release 1.3.1 of the IP phones include enhancements to Type of Service (ToS), Quality of Service (QoS), and Differentiated Services (DiffServ), global configuration of VLAN, and the use of Differentiated Services Code Point (DSCP) in the Differentiated Service (DS) field. ToS is an octet as a field in the standard IP header. It is used to classify the traffic of the different Quality of Services (QoSs). QoS provides service differentiation between IP packets in the network. This service differentiation is noticeable during periods of network congestion (for example, in case of contention for resources) and results in different levels of network performance. DiffServ QoS is class-based where some classes of traffic receive preferential handling over other traffic classes. The DSCP value is stored in the first six bits of the ToS field. Each DSCP specifies a particular per-hop behavior that is applied to a packet. DSCP bits in the ToS field of the IP header are now set for RTP, RTCP, and SIP packets using either the default values or the values configured via the tos priority map parameter. When the VLAN global configuration parameter, tagging enabled, is set to 1, VLAN priority for IP packets is mapped to the DSCP value instead of a single priority for all packets. An administrator can also configure VLAN priority for non-IP packets. An administrator can configure ToS, QoS, and DiffServ QoS using the configuration files only (aastra.cfg and <mac>.cfg).

Page 16 of 44

BLF Key Dialout
A feature enhancement has been added to the original BLF and BLF/List functions on the 480i, 480i CT, and 9133i IP phones. On these model phones, you can now dial out on the configured BLF or BLF/List line. If a softkey on the 480i or 480i (CT), or a programmable key on the 9133i is defined as a BLF or BLF/List key, a user or administrator can press the softkey to automatically dial out using the configured extension.
Automatic Update of Firmware/Configuration Files
A feature has been added to the IP phone that allows an administrator to enable the phone to be updated automatically once a day at a specific time in a 24-hour period if the files on the server have changed. This feature works with TFTP, FTP, and HTTP servers. An administrator can enable this feature using the Aastra Web UI or using the configuration files (aastra.cfg and <mac>.cfg). Notes: 1. If a user is accessing the Aastra Web UI, they are not informed of an auto-reboot. 2. Any changes made using the Aastra Web UI or the IP phone UI are not overwritten by an auto-resync update. Auto-resync affects the configuration files only. However, the settings in the Aastra Web UI take precedence over the IP phone UI and the configuration files. 3. The resync time is based on the local time of the IP phone. 4. If the IP phone is in use (not idle) at the time of the resync check, the reboot occurs when the phone becomes idle. 5. The automatic update feature works with both encrypted and plain text configuration files. When configuring via the Aastra Web UI, the administrator can set the period of time in the Time (24-hour) field, for which the IP phone is automatically updated. In the Aastra Web UI, the time is in 30 minute increments. Valid values are 00:00 to 23:30. The value of 00:00 is 12:00 A.M. An administrator can also set the period of time for which the IP phone is automatically updated using the auto-resync time parameter in the configuration files. Valid values for the auto-resync time are 00:00 to 23:59 and can be entered using minute values from 00 to 59 (for example, the auto resync time can be entered as 02:56). The value of 00:00 is 12:00 A.M. Notes: 1. Auto-Resync adds up to 15 minutes random time to the configured time. For example, if the auto resync time parameter is set to 02:00, the event takes place any time between 02:00 and 02:15. This prevents several phones from accessing the server at the exact same time. 2. When the language on the phone is set to French or Spanish, you must enter the auto resync time in the format 00h00 in the configuration files.

Page 17 of 44

In the configuration files, the following new parameters have been added to enable the automatic update of the IP phones.
Parameter Aastra Web UI: Advanced Settings->Configuration Server Configuration Files: aastra.cfg, <mac>.cfg Enables and disables the phone to be updated automatically once a day at a specific time in a 24-hour period. This parameter works with TFTP, FTP, and HTTP servers. Valid values are: None (0) Disable auto-resync Configuration Files (1) - Updates the configuration files on the IP phone automatically at the specified time if the files on the server have changed. Firmware (2) - Updates the firmware on the IP phone automatically at the specified time if the files on the server have changed. Both (3) - Updates the configuration files and firmware automatically at the specified time if the files on the server have changed. Notes: 1. If a user is accessing the Aastra Web UI, they are not informed of an auto-reboot. 2. Any changes made using the Aastra Web UI or the IP phone UI are not overwritten by an auto-resync update. Auto-resync affects the configuration files only. However, the settings in the Aastra Web UI take precedence over the IP phone UI and the configuration files. 3. The resync time is based on the local time of the IP phone. 4. If the IP phone is in use (not idle) at the time of the resync check, the reboot occurs when the phone becomes idle. 5. The automatic update feature works with both encrypted and plain text configuration files. Integer Aastra Web UI None Configuration Files 0 Aastra Web UI None Configuration Files Firmware Both Configuration Files 0 (none) 1 (configuration files only) 2 (firmware only) 3 (configuration files and firmware) auto resync mode: 1

auto resync mode

Format Default Value

Page 18 of 44

auto resync time
Aastra Web UI: Advanced Settings->Configuration Server Configuration Files: aastra.cfg, <mac>.cfg Sets the time of day in a 24-hour period for the IP phone to be automatically updated. This parameter works with TFTP, FTP, and HTTP servers. Notes: 1. The resync time is based on the local time of the IP phone. 2. The value of 00:00 is 12:00 A.M. 3. When selecting a value for this parameter in the Aastra Web UI, the values are in 30-minute increments only. 4. When entering a value for this parameter using the configuration files the value can be entered using minute values from 00 to 59 (for example, the auto resync time can be entered as 02:56). 5. Auto-Resync adds up to 15 minutes random time to the configured time. For example, if the auto resync time parameter is set to 02:00, the event takes place any time between 02:00 and 02:15. 6. When the language on the phone is set to French or Spanish, you must enter the time in the format 00h00 (configuration files only).

hh:mm 00h00 (for French and Spanish configuration files) Aastra Web UI 00:00 Configuration Files 00:00 Aastra Web UI 00:00 to 23:30 (in 30 minute increments) Configuration Files hh = 00 to 23 mm = 00 to 59 auto resync time: 03:24

Page 19 of 44

Bridged Line Appearance (BLA) (not supported on 9112i)
A SIP bridge line appearance (BLA) feature has been added to the IP phones. BLA allows multiple devices to share a single directory address (DA). For example, people working at a technical support department could be located in different places. If their desktop phones are configured for BLA DA, when customer calls come in, all the phones with the BLA DA would ring but the call can only be answered by one of them. Once the call is answered, the rest of the phones reflect the status of the call. If the call was put on hold by the original recipient, any one from the group can pick up the call. Notes: 1. This feature is dependent on the IP telephony system to which the IP phone is registered and according to draft-anil-sipping-bla-02.txt. 2. Interactive Intelligence and Sylantro servers support the single BLA group with single line appearance feature only. You can apply BLA on the IP phones as follows: As a single BLA group - One BLA DA is shared among multiple phones. Only one phone at a time can pick up an incoming call or initiate an outgoing call on the BLA DA. All phones reflect the usage of the BLA DA. If the call is put on hold, any one from the group can pick up the held call. As a multiple BLA group - On one single phone, multiple BLA DA can be associated with different line appearances. Every BLA DA is independent from each other and follows the same rules as a single BLA group. As multiple instances of a BLA DA - A x-line-id parameter was defined in draft-anilsipping-bla-02.txt to present the incoming call to or place an outgoing call on the specified line appearance instance. The parameter is carried in Alert-Info header field over the request-URI (INVITE e.g.) or in the NOTIFY messages to report the status of a dialog.
BLA DA can be configured on a global basis or on a per-line basis on the IP phones using the Aastra Web UI or the configuration files (aastra.cfg and <mac>.cfg). The following table shows the number of lines that can be set to BLA for each model phone.
IP Phone Model 480i 480i CT 9133i Possible Number of BLA Lines 9

Page 20 of 44

To configure BLA using the configuration files (aastra.cfg or <mac>.cfg), you enter the following parameters: Global Configuration
sip mode Line Mode (in Web UI)
Aastra Web UI: Advanced Settings->Global SIP->Basic SIP Settings Configuration Files: aastra.cfg, <mac>.cfg

9112i and 9133i Using the configuration files, you can configure flash support using the following programmable key parameter: prgkeyN type: flash

Page 27 of 44

5.11 Password Protection for Options Key
A new feature has been added that allows an administrator to assign a password for using the Options key on the IP phone. If enabled, upon pressing the Options key, a user has to enter a password at the IP phone UI. If the password is entered correctly, the user is allowed to gain access to the Options Menu and no more password prompts display for other password protected screens. If the user fails to enter the correct password in three attempts, access to the Options Menu is denied and the IP phone returns to the idle screen. Note: The password to enter is the administrator password configured for that phone. This feature is configurable using the configuration files only (aastra.cfg, <mac>.cfg).
The following configuration file parameter allows an administrator to password protect the Options key.
Parameter Configuration Files: aastra.cfg, <mac>.cfg

options password enabled

Description Enables or disables password protection of the Options key on the IP phone. If enabled, upon pressing the Options key, a user has to enter a password at the IP phone UI. If the password is entered correctly, the user is allowed to gain access to the Options Menu and no more password prompts display for other password protected screens. If the user fails to enter the correct password in three attempts, access to the Options Menu is denied and the IP phone returns to the idle screen. Note: The password to enter is the administrator password configured for that phone. Boolean (false; not password protected) 1 (true; password protected) options password enabled: 1

Page 28 of 44

5.12 State-Based Softkey Configuration and Softkey Type Empty
(480i/480i CT only) A new feature on the 480i and 480i CT IP phones allows users and administrators to configure a specific state to display when a softkey is being used. Available states you can configure for each softkey include: idle connected incoming outgoing The phone is not being used. The line currently being displayed is in an active call (or the call is on hold) The phone is ringing. The user is dialing a number, or the far-end is ringing.

By default, the softkeys display in the states of idle, connected, incoming, and outgoing. You can configure the softkey states using the Aastra Web UI or the configuration files (aastra.cfg, <mac>.cfg).
The softkey states are enabled by default. You can disable all or specific states for a softkey at Operation->Softkeys and XML, by selecting a softkey and removing the checkmark from the state you want to disable (idle, connected, incoming, outgoing).
The following new parameter has been added to support the configuration of softkey states: softkeyN states: <value>
Valid values for this new parameter are idle, connected, incoming, and outgoing. You can enter multiple values for this parameter separated by white space. For example: softkey12 states: idle connected The softkey state parameter that you enter in the configuration files must be associated with a specific softkey. In the following example, the softkey states parameter is associated with softkey 12: softkey12 type: speeddial softkey12 label: voicemail softkey12 value: *89 softkey12 states: outgoing Note: The IP phone idle screen condenses the softkeys. So in the previous example, softkey 12 will appear in position 1 if no other softkeys are set. A softkey type of empty does not display on the idle screen at all. (For more information about the softkey type of empty see section 4.12.1).

Page 29 of 44

5.12.1 New Softkey Type called Empty (480i/480i CT only)
A new softkey type called empty has been added in release 1.3.1 for the 480i and 480i CT, which forces a blank entry on the IP phone display for a specific softkey. The soft keys are added in order (from softkey1 to softkey20) after any hard-coded keys have been added. If a particular soft key is not defined, it is ignored. You can configure this softkey type using the Aastra Web UI or the configuration files.
Using the Aastra Web UI, you can configure an empty softkey at Operation->Softkeys and XML, and in the Type field, select empty from the drop-down list. All other fields except the States fields for that softkey are disabled.
You use the softkeyN type parameter to assign a value of empty as follows: softkeyN type: empty

5.12.2 Example Usage

The following example shows how the new state parameter and empty softkey type are used. For clarity purposes, only the softkeyN type and softkeyNstates parameters are shown. softkey1 type: line softkey1 states: idle connected softkey3 type: dnd softkey3 states: idle softkey4 type: line softkey5 type: empty softkey5 states: connected softkey6 type: speeddial softkey6 states: connected The table below shows how the keys in the example above would display on the IP phone UI:
Softkey softkey1 softkey2 softkey3 softkey4 softkey5 softkey6 Idle Key 1 (not used) Key 2 Key 3 (not used) (not used) Connected Key 2 (not used) (not used) Key 3 Key 4 (blank) Key 5 Notes Key 1 in connected state is the Drop key. Line displays for softkey 1. Idle and connected display as applicable. Softkey is not displayed. DND displays for softkey 3. Idle displays as applicable. Line displays for softkey 4. Default state values (idle, connected, incoming, outgoing) display as applicable. A blank displays for softkey 5. Connected displays as applicable. Speeddial displays for softkey 6. Connected displays as applicable.
Note: The empty key type allows a soft key to be removed quickly by deleting the soft key information from the configuration file.

Page 30 of 44

5.13 Domain Name Support in the TFTP and Time Server Fields
Release 1.3.1 now supports an administrator entry of a domain name in the TFTP and Time Server parameters on the IP phones. These parameters are configurable using the Aastra Web UI and the configuration files. Note: The TFTP domain name resolves when the phone is restarted. The Time Server domain name resolves when it is saved and when the phone restarts.
Using the Aastra Web UI, you configure a primary TFTP Server at Advanced Settings->Configuration Server, and in the TFTP Server field, enter a domain name (for example, 123.ana.aastra.com). You can also enter a domain name for an alternate TFTP server in the Alternate TFTP Server field. You configure the Time Server at Advanced Settings->Network->Advanced Network Settings, and in the Timer Server 1, 2, or 3 fields, enter a domain name (for example, 123.ana.aastra.com).
You use the following parameters to configure the TFTP Server and the Time Server in the configuration files: tftp server: <domain name or IP address> alternative tftp server: <domain name or IP address> time server1: <domain name or IP address> time server2: <domain name or IP address> time server3: <domain name or IP address>
5.14 Language Localization (480i, 9112i, 9133i only)
In release 1.3.1, the Models 480i, 9133i, and 9112i IP phones now support German and Italian languages for the IP Phone UI. Please refer to your product-specific User Guide or Administrators Guide for instruction on changing your language preference.

Outgoing Intercom Configuration
sip intercom type Type (in Web UI)
Aastra Web UI: Basic Settings->Preferences ->Outgoing Intercom Settings Configuration Files: aastra.cfg, <mac>.cfg Determines whether the IP phone or the server is responsible for notifying the recipient that an Intercom call is being placed. Integer For Aastra Web UI: Off (480i, 480i CT and handsets) For Configuration Files: Off (480i, 480i CT and handsets) 2 (480i) 3 (480i CT and handsets)
For Aastra Web UI: Phone-Side Server-Side Off (480i and 480i CT handsets) For Configuration Files: 1 - Phone-Side 2 - Server-Side 3 Off
sip intercom type: 1 Aastra Web UI: Basic Settings->Preferences ->Outgoing Intercom Settings Configuration Files: aastra.cfg, <mac>.cfg
sip intercom prefix code Prefix Code (in Web UI)
The prefix to add to the phone number for server-side Intercom calls. This parameter is required for all server-side Intercom calls. Note: The example below shows *96 for the prefix code which is used for Sylantro servers. string N/A N/A sip intercom prefix code: *96

Page 33 of 44

sip intercom line Line (in Web UI)
Aastra Web UI: Basic Settings->Preferences ->Outgoing Intercom Settings Configuration Files: aastra.cfg, <mac>.cfg
Specifies the line for which the IP phone uses the configuration from, when making the Intercom call. The IP phone uses the first available line for physically making the call but uses the configuration from the line you set for this parameter. Note: The sip intercom type parameter must be set with the Server-Side option to enable the sip intercom line parameter. Integer 1 Line 1 through 9 sip intercom line: 1
Incoming Intercom Configuration
sip intercom mute mic Microphone Mute (in Web UI)
Aastra Web UI: Basic Settings->Preferences ->Incoming Intercom Settings Configuration Files: aastra.cfg, <mac>.cfg
Enables or disables the microphone on the IP phone for Intercom calls made by the originating caller. Integer (false microphone is not muted) 1 (true microphone is muted) sip intercom mute mic: 1

Page 34 of 44

sip allow auto answer Auto-Answer (in Web UI)
Enables or disables the IP phone to allow automatic answering for an Intercom call. If auto-answer is enabled on the IP phone, the phone plays a tone to alert the user before answering the intercom call. If auto-answer is disabled, the phone rejects the incoming intercom call and sends a busy signal to the caller. Boolean (false do not allow auto-answer) 1 (true allow auto-answer) sip allow auto-answer: 0

Feature Parameter Park Call Note: Enter to disable. Pickup Parked Call Note: Enter to disable. Asterisk Server 700 BroadWorks Server Value *68 Sylantro Server Value *98 ININ PBX Value callpark

pickup

Page 37 of 44
Using Park a Call/Pick up a Call Feature
The following tables provide a procedure for parking and picking up a call.

To park a call:

1. 2. While on a live call, press the Park softkey (located below the Drop softkey). Perform the following for your specific server: For Asterisk Server: Server announces the extension number where the call has been parked. Once the call is parked, press the y key to complete parking. For Broadworks Server: After you hear the greeting from the CallPark server, enter the extension where you want to park the call. For Sylantro Server: Enter the extension number where you want to park the call, followed by # key. For ININ Server: Enter the extension number where you want to park the call, followed by # key. Result: If the call is parked successfully, the response will either be a greeting voice confirming that the call was parked, or a hang up occurs. The parked call party will get music on hold.
If the call park fails, you can pick up the call (using the next procedure) and press the Park softkey again to retry step 2.

To pick up a call:

1. 2. Enter the extension number where the call was parked. Press the PickUp softkey (located as the 2

softkey on the phone).

Result: If the call pick up is successful, you are connected with the parked call.

Page 38 of 44

5.19 XML Features(480i/480i CT only)
5.19.1 XML Application Title
A new XML Application Title parameter in the Aastra Web UI and the configuration files allows a user or administrator to rename the XML application in the IP phone UI (Services->4. Custom Feature). By default, when you load an XML application to the IP phone, the XML application title is called "Custom Feature". The XML Application Title parameter allows you to change that title. For example, if you are loading a traffic report XML application, you could change this parameter title to "Traffic Reports", and that title will display in the IP phone UI as Services->4. Traffic Reports
Using the Aastra Web UI, you can assign an XML application title using Advanced Settings->Softkeys and XML->Services, and in the XML Application Title field, enter a title for the XML application you are loading to the IP phone (for example, Traffic Reports)

You use the following parameter to assign an XML application title in the configuration files: xml application title: <title>
For example: xml application title: Traffic Reports

xml application title

Aastra Web UI: Operation->Softkeys and XML->Services Configuration Files: aastra.cfg, <mac>.cfg This parameter allows you to rename the XML application in the IP phone UI (Services->4. Custom Feature). By default, when you load an XML application to the IP phone, the XML application title is called "Custom Feature". The "xml application title" parameter allows you to change that title. For example, if you are loading a traffic report XML application, you could change this parameter title to "Traffic Reports", and that title will display in the IP phone UI as Services->4. Traffic Reports. Alphanumeric characters Not Applicable Not Applicable xml application title: Traffic Reports

Page 39 of 44

5.19.2 Use of XML APIs on Custom Softkeys
Also, Release 1.3.1 now allows developers to customize softkeys on the 480i and 480i CT IP phones to use XML APIs to produce powerful XML applications. Developers can now link arbitrary URIs to keys in the XML screens and can invoke softkey behavior to each XML screen type. A new softkey XML element has been implemented that you can use in conjunction with all current XML objects (Text Menu, Text Screen, User Input, Directory) on the IP phones. This new element is as follows:
<SoftKey index = 1-6> <Label> Text (10 characters max will fit on the screen) </Label> <URI> http://someserver/somepage.pl OR SoftKey:someaction </URI> </Softkey>
You can define up to six softkeys before the closing tag of any object on the 480i and 480i CT. The following example illustrates the use of the new softkey XML element used with the Text Menu object, and the resulting screen output. Text Menu Object
<AastraIPPhoneTextMenu> <Title> New Directory </Title> <MenuItem> <Prompt> My 480i </Prompt> <URI>10.50.10.49 </URI> <MenuItem> <MenuItem> <Prompt> My 9112 </Prompt> <URI>10.50.10.75</URI> </MenuItem> <SoftKey index = 1 > <Label> Dial </Label> <URI>SoftKey:Dial</URI> </Softkey> <SoftKey index = 2> <Label> Back </Label> <URI>http://someserver/somepage.xml</URI> </Softkey> <SoftKey index = 5> <Label> More </Label> <URI>http://someserver/somepage.xml</URI> </Softkey> <SoftKey index = 6> <Label> Cancel </Label> <URI>SoftKey:Exit</URI> </Softkey> </AastraIPPhoneTextMenu>

Page 40 of 44

Aastra Telecom
Bringing VoIP endpoint solutions to the desktop

SIMPLICITY

FLEXIBILITY

AFFORDABILITY

MOBILITY
Aastra Telecom offers a portfolio of standards-based VoIP desktop endpoints designed to tightly integrate with todays most popular IP platforms. In addition to supporting a wide variety of IP PBX and Softswitch solutions, Aastras family of IP products have been tested and/or certified compatible with the following IP platforms.
Third-Party Interoperability Asterisk/Digium Platform Asterisk Open Source PBX Protocol SIP 480i CT 480i 9133i 9112i

BroadSoft

BroadWorks

Nortel Networks

MCS 5100 & MCS 5200

Sylantro Systems

Applications Feature Server

Sphere Communications

Sphericall

SIP/MGCP

SIP only
Visit www.aastra.com/EnterpriseIP Or call us at 1-800-574-1611

V O I P

T E L E P H O N E

F E A T U R E

M A T R I X

IP Phones

9 Y Y Modular connector 3 lines x 16 characters Y Y Y Y Y Y Y 100 Y Y Y N/A N/A Y Y Y Y Y Y Y Y 2 Y Y Y Y Y Y Y Y Y
9 Y Y Modular connector 8 lines x 20 characters Y Y Y Y Y Y Y 100 Y Y Y N/A N/A Y Y

480i CT

9 Y Y Modular connector 8 lines x 20 characters Y Y Y Y Y Y Y 100 Y Y Y WDCT 2.4 GHz FH-SS 4 Y Y Y Y Y Y Y Y 2 Y Y Y Y Y Y Y Y Y
Telephone Features Number of lines 1 Multi-line, multi-proxy registration support Programmable hard keys 2 Programmable soft keys Pre-programmed feature keys 11 Full-duplex speakerphone Y Dedicated headset jack Modular connector Backlit Visual display 3 lines x 16 characters Adjustable display contrast Y Visual message waiting indication Y Busy lamp field (BroadSoft and Asterisk) Do not disturb (DND) Y Call waiting display Y Call forward Y Missed call indicator Y Directory 200 Callers Log 200 Redial last numbers 100 Priority alert/distinctive ringing Y Y Call park/pickup Y Multilingual support - Eng., Fr., Spn., Germ., Ital. N/A Cordless mobility N/A Number of cordless handsets Power Options 1 Power over Ethernet Optional mid-span PoE injector Y AC wall adapter (Included) Configuration & Administration Y Telephone User Interface Y Web User Interface Y Encryption of configuration file Y Software & Config. download - TFTP, FTP, HTTP Y Automatic software update Network Support 1 10/100 Mbps Switched Ethernet ports Y 802.1p/q VLAN tagging & QOS Y NAT support - phone side Y Outbound proxy support Y IETF DHCP Y IETF SNTP Protocol Support Y IETF SIP (RFC3261) IETF MGCP Y XML browser Codecs Y G.711 -law/A-law Y G.729 (Annex B)
Y Y Y Y Y 2 Y Y Y Y Y Y Y Y Y Y
Compatible with IEEE 802.3af device
* The Aastra 480i CT, 480i, 9133i and 9112i IP Phones were verified as compatible with Nortel Networks Multimedia Communications Server 5100 and 5200 in a controlled laboratory environment.
All Service marks, trademarks and registered trademarks shown in this document are the property of their respective companies.
COPYRIGHT (C) 2006 AASTRA TELECOM. ALL RIGHTS RESERVED. INFORMATION IN THIS DOCUMENT IS SUBJECT TO CHANGE WITHOUT NOTICE. AASTRA TELECOM ASSUMES NO RESPONSIBILITY FOR ANY ERRORS THAT MAY APPEAR IN THIS DOCUMENT. PRODUCT CAPABILITIES DESCRIBED IN THIS DOCUMENT PERTAIN SOLELY TO AASTRA TELECOMS MARKETING ACTIVITIES IN THE U.S AND CANADA. AVAILABILITY IN OTHER MARKETS MAY VARY.