Installation guide | Aastra Telecom 53I IP Phone User Manual

53i, 55i, 57i, 57i C
CT
SIP IP
SI
I PHONE
41-001160-00
Rev 04
Administrator Guide
Release 2.1
Aastra Telecom will not accept liability for any damages and/or long distance charges, which result from
unauthorized and/or unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom will
not be liable for technical or editorial errors or omissions contained within this documentation. The
information contained in this documentation is subject to change without notice.
Copyright 2007 Aastra Telecom. www.aastratelecom.com
All Rights Reserved.
Software License Agreement
Aastra Telecom Inc., hereinafter known as "Seller", grants to Customer a
personal, worldwide, non-transferable, non-sublicenseable and non-exclusive,
restricted use license to use Software in object form solely with the Equipment for
which the Software was intended. This Product may integrate programs, licensed
to Aastra by third party Suppliers, for distribution under the terms of this
agreement. These programs are confidential and proprietary, and are protected as
such by copyright law as unpublished works and by international treaties to the
fullest extent under the applicable law of the jurisdiction of the Customer. In
addition, these confidential and proprietary programs are works conforming to the
requirements of Section 401 of title 17 of the United States Code. Customer shall
not disclose to any third party such confidential and proprietary programs and
information and shall not export licensed Software to any country except in
accordance with United States Export laws and restrictions.
Customer agrees to not reverse engineer, decompile, disassemble or display
Software furnished in object code form. Customer shall not modify, copy,
reproduce, distribute, transcribe, translate or reduce to electronic medium or
machine readable form or language, derive source code without the express
written consent of the Seller and its Suppliers, or disseminate or otherwise
disclose the Software to third parties. All Software furnished hereunder (whether
or not part of firmware), including all copies thereof, are and shall remain the
property of Seller and its Suppliers and are subject to the terms and conditions of
this agreement. All rights reserved.
Customer's use of this software shall be deemed to reflect Customer's agreement
to abide by the terms and conditions contained herein. Removal or modification
of trademarks, copyright notices, logos, etc., or the use of Software on any
Equipment other than that for which it is intended, or any other material breach of
this Agreement, shall automatically terminate this license. If this Agreement is
terminated for breach, Customer shall immediately discontinue use and destroy or
return to Seller all licensed software and other confidential or proprietary
information of Seller. In no event shall Seller or its suppliers or licensors be liable
for any damages whatsoever (including without limitation, damages for loss of
business profits, business interruption, loss of business information, other
pecuniary loss, or consequential damages) arising out of the use of or inability to
use the software, even if Seller has been advised of the possibility of such
damages.
41-001160-00, Release 2.1, Rev 04
iii
Preface
About this guide ...............................................................................................................xiii
Introduction ...............................................................................................................xiii
Audience ...................................................................................................................xiii
.
.
.
Other Documentation ............................................................................................... xiv
.
Chapters and appendixes in this guide ..................................................................... xv
.
Chapter 1
Overview
.
About this chapter ...........................................................................................................1-1
.
IP Phone Models ............................................................................................................1-2
.
Description ...............................................................................................................1-2
.
Model 53i IP Phone ..................................................................................................1-5
.
Model 55i IP Phone ..................................................................................................1-8
.
Model 57i and 57i CT IP Phone .............................................................................1-12
.
Firmware Installation Information .................................................................................1-18
.
Description .............................................................................................................1-18
.
Installation Considerations .....................................................................................1-18
.
Installation Requirements .......................................................................................1-19
.
Configuration Server Requirement .........................................................................1-20
.
Firmware and Configuration Files .................................................................................1-21
.
Description .............................................................................................................1-21
.
Configuration File Precedence ...............................................................................1-22
.
Installing the Firmware/Configuration Files ............................................................1-23
.
41-001160-00, Release 2.1 Rev 04
v
Contents
Contents
Contents
Chapter 2
Configuration Interface Methods
.
About this chapter ...........................................................................................................2-1
.
Configuration Methods ...................................................................................................2-2
.
Description ...............................................................................................................2-2
.
IP Phone UI ..............................................................................................................2-2
.
Aastra Web UI ..........................................................................................................2-5
.
Configuration Files (Administrator Only) ................................................................2-15
.
Chapter 3
Administrator Options
.
About this chapter ...........................................................................................................3-1
.
Administrator Level Options ...........................................................................................3-3
.
Description ...............................................................................................................3-3
.
IP Phone UI Options ................................................................................................3-3
.
Aastra Web UI Options ............................................................................................3-7
.
Configuration File Options ........................................................................................3-9
.
Phone Status ..........................................................................................................3-10
.
Restarting Your Phone ...........................................................................................3-13
.
Set Phone to Factory Defaults/Erase Local Configuration .....................................3-15
.
Basic Settings ........................................................................................................3-19
.
Network Settings ....................................................................................................3-31
.
Line Settings ..........................................................................................................3-56
.
Softkeys, Programmable Keys, Expansion Module Keys ......................................3-57
.
Action URI ..............................................................................................................3-58
.
Configuration Server Settings ................................................................................3-59
.
Firmware Update Features ....................................................................................3-66
.
vi
41-001160-00, Release 2.1 Rev 04
Contents
Chapter 4
Configuring Network and
Session Initiation Protocol (SIP) Features
.
About this chapter ...........................................................................................................4-1
Overview .........................................................................................................................4-3
Network Settings ............................................................................................................4-4
.
.
.
Basic Network Settings ............................................................................................4-4
.
Advanced Network Settings ...................................................................................4-16
.
Global SIP Settings ......................................................................................................4-44
.
Description .............................................................................................................4-44
.
Basic SIP Settings ..................................................................................................4-45
.
Advanced SIP Settings (optional) ..........................................................................4-57
.
Real-time Transport Protocol (RTP) Settings .........................................................4-63
.
Autodial Settings ....................................................................................................4-73
.
Configuration Server Protocol ......................................................................................4-78
Configuring the Configuration Server Protocol .......................................................4-78
.
.
Chapter 5
Configuring Operational Features
.
About this chapter ...........................................................................................................5-1
.
Operational Features ......................................................................................................5-4
.
Description ...............................................................................................................5-4
.
User Passwords .......................................................................................................5-4
.
Administrator Passwords .........................................................................................5-8
.
Locking/Unlocking the Phone ...................................................................................5-9
.
Defining an Emergency Dial Plan ..........................................................................5-15
.
Time and Date ........................................................................................................5-17
.
Language ...............................................................................................................5-21
.
Locking IP Phone Keys ..........................................................................................5-28
.
Local Dial Plan .......................................................................................................5-30
.
Park Calls/Pick Up Parked Calls ............................................................................5-35
.
Suppressing DTMF Playback .................................................................................5-39
.
Display DTMF Digits ..............................................................................................5-41
.
Call Waiting/Call Waiting Tone ...............................................................................5-43
.
Stuttered Dial Tone .................................................................................................5-46
.
41-001160-00, Release 2.1 Rev 04
vii
XML Beep Support .................................................................................................5-48
Contents
.
Status Scroll Delay .................................................................................................5-50
.
Incoming Call Interrupts Dialing .............................................................................5-52
.
Goodbye Key Cancels Incoming Call .....................................................................5-54
UPnP Mapping Lines (for remote phones) .............................................................5-56
.
.
Message Waiting Indicator Line .............................................................................5-58
.
Incoming/Outgoing Intercom with Auto-Answer and Barge In ...............................5-60
.
Key Mapping ..........................................................................................................5-66
.
Ring Tones and Tone Sets .....................................................................................5-70
.
Priority Alerting .......................................................................................................5-75
.
Directed Call Pickup (BLF or XML Call Interception) .............................................5-81
.
Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys ..................5-93
.
Speeddial Prefixes ...............................................................................................5-113
.
Busy Lamp Field (BLF) ........................................................................................5-114
.
BLF Subscription Period ......................................................................................5-120
.
Automatic Call Distribution (ACD) (for Sylantro Servers) .....................................5-122
.
ACD Subscription Period .....................................................................................5-133
.
Directed Call Pickup/Group Call Pickup (for Sylantro Servers) ............................5-135
.
Do Not Disturb (DND) ..........................................................................................5-142
.
Bridged Line Appearance (BLA) (55i, 57i, 57i CT only) .......................................5-144
.
BLA Support for Third Party Registration .............................................................5-151
.
Park/Pick Up Key .................................................................................................5-153
.
Last Call Return (lcr) (For Sylantro Servers .........................................................5-164
.
Call Forwarding ....................................................................................................5-168
.
Callers List ...........................................................................................................5-174
.
Customizable Callers List and Services Keys ......................................................5-179
.
Missed Calls Indicator ..........................................................................................5-180
.
Directory List ........................................................................................................5-182
.
Voicemail (55i, 57i, and 57i CT only) ....................................................................5-193
XML Customized Services ...................................................................................5-196
.
.
Audio Transmit and Receive Gain Adjustments ...................................................5-218
.
Centralized Conferencing (for Sylantro and Broadsoft Servers) ..........................5-220
Customizing the Display Columns on the 560M Expansion Module ....................5-224
viii
.
.
41-001160-00, Release 2.1 Rev 04
Contents
Chapter 6
Configuring Advanced Operational Features
.
About this chapter ...........................................................................................................6-1
.
Advanced Operational Features .....................................................................................6-3
.
Description ...............................................................................................................6-3
.
MAC Address/Line Number in REGISTER Messages .............................................6-5
.
SIP Message Sequence for Blind Transfer ..............................................................6-7
.
Update Caller ID During a Call .................................................................................6-8
.
Boot Sequence Recovery Mode ..............................................................................6-9
.
Auto-discovery Using mDNS ..................................................................................6-10
.
Single Call Restriction (57i CT only) ......................................................................6-11
.
Missed Call Summary Subscription .......................................................................6-13
.
Blacklist Duration (Broadsoft Servers) ...................................................................6-17
.
Whitelist Proxy .......................................................................................................6-19
.
Transport Layer Security (TLS) ..............................................................................6-21
.
Symmetric UDP Signaling ......................................................................................6-27
.
Removing UserAgent and Server SIP Headers .....................................................6-28
Multi-Stage Digit Collection (Billing Codes) Support (for Sylantro Servers) ...........6-29
Chapter 7
Encrypted Files on the IP Phone
.
.
.
About this chapter ...........................................................................................................7-1
.
Encrypted Files on the IP Phone ....................................................................................7-2
.
Configuration File Encryption Method ......................................................................7-2
.
Procedure to Encrypt/Decrypt Configuration Files ...................................................7-3
Chapter 8
Upgrading the Firmware
.
.
About this chapter ...........................................................................................................8-1
.
Upgrading the Firmware .................................................................................................8-2
.
Manual Firmware Update (TFTP only) .....................................................................8-2
Manual Firmware and Configuration File Update .....................................................8-4
.
.
Automatic Update (auto-resync) ..............................................................................8-6
.
......................................................................................................................................8-10
41-001160-00, Release 2.1 Rev 04
.
ix
Contents
Chapter 9
Troubleshooting
.
About this chapter ...........................................................................................................9-1
Troubleshooting ..............................................................................................................9-2
Troubleshooting Solutions ..............................................................................................9-7
.
.
.
Description ...............................................................................................................9-7
.
Why does my phone display “Application missing”? ................................................9-7
.
Why does my phone display the “No Service” message? ........................................9-8
.
Why does my phone display "Bad Encrypted Config"? ............................................9-8
.
Why is my phone not receiving the TFTP IP address from the DHCP Server? .......9-9
.
How do I restart the IP phone? ..............................................................................9-10
.
How do I set the IP phone to factory default? ........................................................9-11
.
How do I erase the phone’s local configuration? ...................................................9-12
.
How to reset a user’s password? ...........................................................................9-13
.
How do I lock and unlock the phone? ....................................................................9-14
.
Appendix A
Configuration Parameters
.
About this appendix ....................................................................................................... A-1
.
Setting Parameters in Configuration Files ..................................................................... A-4
.
Operational, Basic, and Advanced Parameters ............................................................. A-5
.
Simplified IP Phone UI Options Menu ..................................................................... A-5
.
Network Settings ..................................................................................................... A-6
.
Password Settings .................................................................................................. A-9
.
Emergency Dial Plan Settings ............................................................................... A-11
.
Aastra Web UI Settings ......................................................................................... A-12
.
Configuration Server Settings ............................................................................... A-13
.
Network Address Translation (NAT) Settings ........................................................ A-20
.
HTTPS Client and Server Settings ........................................................................ A-23
.
UPnP Settings ....................................................................................................... A-25
.
Virtual Local Area Network (VLAN) Settings ......................................................... A-26
.
Type of Service (ToS)/DSCP Settings ................................................................... A-30
.
Time Server Settings ............................................................................................. A-31
.
Time and Date Settings ......................................................................................... A-33
.
SIP Local Dial Plan Settings ................................................................................. A-39
.
x
41-001160-00, Release 2.1 Rev 04
SIP Basic, Global Settings .................................................................................... A-41
Contents
.
SIP Basic, Per-Line Settings ................................................................................. A-50
.
Centralized Conferencing Settings ........................................................................ A-60
.
Advanced SIP Settings ......................................................................................... A-62
.
Missed Call Summary Subscription Settings ........................................................ A-70
.
Transport Layer Security (TLS) Settings ............................................................... A-72
RTP, Codec, DTMF Global Settings ...................................................................... A-77
.
.
Autodial Settings ................................................................................................... A-81
.
Voicemail Settings ................................................................................................. A-84
.
Directory Settings .................................................................................................. A-85
.
Callers List Settings .............................................................................................. A-86
.
Customize Callers List and Services Key ............................................................. A-86
.
Call Forward Settings ............................................................................................ A-87
.
Missed Calls Indicator Settings ............................................................................. A-88
.
XML Settings ......................................................................................................... A-89
.
Action URI Settings ............................................................................................... A-92
.
Ring Tone and Tone Set Global Settings .............................................................. A-94
.
Ring Tone Per-Line Settings ................................................................................. A-97
.
Incoming Call Interrupts Dialing Setting ................................................................ A-98
.
Goodbye Key Cancels Incoming Call .................................................................... A-99
.
Stuttered Dial Tone Setting ................................................................................. A-100
.
Call Waiting Settings ........................................................................................... A-101
.
Message Waiting Indicator Settings .................................................................... A-102
.
Priority Alert Settings ........................................................................................... A-103
.
Language Settings .............................................................................................. A-109
.
Language Pack Settings ..................................................................................... A-110
.
Suppress DTMF Playback Setting ...................................................................... A-119
.
Display DTMF Digits Setting ............................................................................... A-120
.
Intercom, Auto-Answer, and Barge In Settings ................................................... A-121
.
Audio Transmit and Receive Gain Adjustment Settings ..................................... A-125
Directed Call Pickup (BLF or XML Call Interception) Settings ............................ A-128
.
.
ACD Auto-Available Timer Settings ................................................................... A-131
.
Park and Pickup Global Settings (57i/57i CT only) ............................................. A-132
.
Mapping Key Parameters .................................................................................... A-133
.
41-001160-00, Release 2.1 Rev 04
xi
Contents
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters ......... A-136
.
Softkey Settings for 55i, 57i, 57i CT .................................................................... A-137
.
Programmable Key Settings for 53i and 55i ........................................................ A-145
.
Top Softkey Settings for 57i and 57i CT .............................................................. A-150
.
Handset Feature Key Settings for the 57i CT ..................................................... A-156
.
Expansion Module Key Settings for 536M (for all model phones)
and 560M (for 55i, 57i, 57i CT phones only) ....................................................... A-158
.
Locking Softkeys and Programmable Keys ........................................................ A-163
.
Customizing 560M Expansion Module Column Display ............................................ A-166
.
Expansion Module 1 ............................................................................................ A-166
.
Expansion Module 2 ............................................................................................ A-168
.
Expansion Module 3 ............................................................................................ A-170
.
Advanced Operational Parameters ........................................................................... A-172
.
Blind Transfer Setting .......................................................................................... A-172
.
Update Caller ID Setting. .................................................................................... A-173
.
Boot Sequence Recovery Mode. ........................................................................ A-173
.
Single Call Restriction ......................................................................................... A-174
.
Blacklist Duration ................................................................................................ A-175
.
Whitelist Proxy .................................................................................................... A-175
.
Symmetric UDP Signaling Setting ....................................................................... A-176
.
User-Agent Setting .............................................................................................. A-176
.
Troubleshooting Parameters ..................................................................................... A-177
.
Log Settings ........................................................................................................ A-177
.
Appendix B
Configuration Server Setup
.
About this appendix ....................................................................................................... B-1
.
Configuration Server Protocol Setup ............................................................................. B-2
.
TFTP Server Set-up ................................................................................................ B-2
.
Appendix C
Configuring the IP Phone at the Asterisk IP PBX
.
About this appendix ....................................................................................................... C-1
.
IP Phone at the Asterisk IP PBX ................................................................................... C-2
xii
.
41-001160-00, Release 2.1 Rev 04
Contents
Appendix D
Sample Configuration Files
.
About this appendix ....................................................................................................... D-1
.
Sample Configuration Files ........................................................................................... D-2
.
57i Sample Configuration File ................................................................................. D-2
.
57i CT Sample Configuration File ......................................................................... D-12
.
53i Sample Configuration File ............................................................................... D-29
.
Appendix E
Sample BLF Softkey Settings
.
About this appendix ....................................................................................................... E-1
.
Sample BLF Softkey Settings ........................................................................................ E-2
.
Asterisk BLF ............................................................................................................ E-2
.
BroadSoft BroadWorks BLF .................................................................................... E-3
.
Appendix F
Sample Multiple Proxy Server Configuration
.
About this appendix ....................................................................................................... F-1
.
Multiple Proxy Server Configuration .............................................................................. F-2
.
Appendix G
Creating an XML Application
.
About this appendix .......................................................................................................G-1
.
How to Create an XML Application ................................................................................G-3
.
Overview .................................................................................................................G-3
.
XML format ..............................................................................................................G-3
.
Support of Virtual Web Servers ...............................................................................G-3
.
Creating XML Objects .............................................................................................G-4
.
Creating Custom Softkeys ......................................................................................G-5
.
Text Menu Object (Menu Screens) ..........................................................................G-6
.
Text Screen Object (Text Screens) ........................................................................G-12
.
UserInput Object (User Input Screens) .................................................................G-21
.
Directory Object (Directory List Screen) (57i only) ................................................G-36
.
Status Message Object (Idle Screen) ....................................................................G-38
.
Execute Commands Object (for executing XML commands) ...............................G-40
Dynamic Configuration Object (to push a configuration to the phone) ..................G-44
41-001160-00, Release 2.1 Rev 04
.
.
xiii
Contents
XML Image Objects (55i, 57i/57i CT only) ............................................................G-48
.
Attributes/Options to Use with XML Objects .........................................................G-58
.
HTTP Post .............................................................................................................G-62
.
XML Schema File ..................................................................................................G-65
.
Limited Warranty
.
xiv
41-001160-00, Release 2.1 Rev 04
Preface
Preface
About this guide
Introduction
This SIP IP Phone Administrator Guide provides information on the basic
network setup, operation, and maintenance of the IP phones, Models 53i, 55i, 57i,
and 57i Cordless (57i CT). It also includes details on the functioning and
configuration of the IP phones.
Note: Features, characteristics, requirements, and configuration that are
specific to a particular IP phone model are indicated where required in
this guide.
Audience
This guide is for network administrators, system administrators, developers and
partners who need to understand how to operate and maintain the IP phone on a
SIP network. It also provides some user-specific information.
This guide contains information that is at a technical level, more suitable for
system or network administrators. Prior knowledge of IP Telephony concepts is
recommended.
41-001160-00, Release 2.1, Rev 04
xiii
IP Phone Administrator Guide
About this guide
Preface
Other Documentation
The IP phone documentation consists of:
•
<Model-specific> SIP IP Phone Installation Guide – contains installation
and set-up instructions, information on general features and functions, and
basic options list customization. Included with the phone.
•
Model 53i, 55i, 57i, 57i CT SIP IP Phone Administrator Guide – explains
how to set the phone up on the network, as well as advanced configuration
instructions for the SIP IP phone. This guide contains information that is at a
technical level more suitable for a system or network administrator.
•
<Model-specific> SIP IP Phone User Guides – explains the most commonly
used features and functions for an end user.
This Administrator Guide complements the Aastra product-specific Installation
Guide and the Aastra product-specific User Guide.
xiv
41-001160-00, Release 2.1, Rev 04
Chapters and appendixes in this guide
For
Go to
An overview of the IP Phone firmware installation information
Chapter 1
IP Phone interface methods
Chapter 2
Administrator option information
Chapter 3
Configuring the Network and Global SIP Features on the IP Phone
Chapter 4
Configuring operational information on the IP Phones
Chapter 5
Configuring advanced operational information on the IP Phones
Chapter 6
Encryption information
Chapter 7
Firmware upgrade information
Chapter 8
Troubleshooting solutions
Chapter 9
Configuration parameters
Appendix A
Configuration server setup
Appendix B
Configuring the IP Phones at the Asterisk PBX
Appendix C
Sample configuration files
Appendix D
Sample BLF softkey settings
Appendix E
Sample multiple proxy server configuration
Appendix F
Creating XML applications
Appendix G
41-001160-00, Release 2.1, Rev 04
Preface
This guide contains the following chapters and appendixes:
xv
About this chapter
Introduction
This chapter briefly describes the IP Phone Models, and provides information
about installing the IP phone firmware. It also describes the firmware and
configuration files that the IP phone models use for operation.
Topics
This chapter covers the following topics:
Topic
Page
IP Phone Models
page 1-2
Firmware Installation Information
page 1-18
Firmware and Configuration Files
page 1-21
41-001160-00, Release 2.1, Rev 04
1-1
Overview
Chapter 1
Overview
IP Phone Administrator Guide
IP Phone Models
Overview
IP Phone Models
Description
The IP Phone Models 53i, 55i, 57i, and 57i CT communicate over an IP network
allowing you to receive and place calls in the same manner as a regular business
telephone.
All phone models support the Session Initiation Protocol (SIP). The 57i CT offers
the base phone along with a cordless extension.
References
For more information about the features and installation requirements, see the
SIP IP Phone Installation Guide for your specific model.
The following illustration shows the types of IP Phone Models.
53i
57i
1-2
55i
57i CT
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
Optional Accessories
Overview
The following are optional accessories for the IP Phones.
Power over Ethernet (PoE)
Inline Power Injector
Additional Ethernet Cable
(category 5/5e straight through
cable)
A Power over Ethernet (PoE) inline power injector supplies 48V power to the IP
phone through the Ethernet cable on pins 4 & 5 and 7 & 8.
Warning: Do not use this inline PoE power injector to power other
devices. See your phone-specific Installation Guide for more information.
Reference
For more information about installing the PoE and additional Ethernet cable, see
your phone-specific Installation Guide.
41-001160-00, Release 2.1, Rev 04
1-3
Overview
IP Phone Administrator Guide
IP Phone Models
536M Expansion Module
for 53i, 55i, 57i, and 57i CT
560M Expansion Module
for 55i, 57i, and 57i CT
The 536M module adds 36 additional softkeys to the IP phone models 53i, 55i,
57i, and 57i CT. The 536M provides paper labels for each softkey. Up to 3
modules can be piggy-backed to provide up to 108 additional softkeys for the
phone.
The 560M module adds 60 additional softkeys to the IP phone models 55i, 57i,
and 57i CT (using the 3 function keys on the bottom right of the unit). The 560M
module provides an LCD display for display softkey labels. Up to 3 modules can
be piggy-backed to provide up to 180 additional softkeys for the phone.
Reference
For more information about installing and using the expansion modules, see your
phone-specific Installation Guide and phone-specific User Guide.
1-4
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
Model 53i IP Phone
53i Phone Features
•
•
•
•
•
•
•
•
•
•
3-line LCD screen
6 top keys: 4 keys are programmable
3 call appearance lines with LEDs
Supports up to 9 call lines
Full-duplex speakerphone for handsfree calls
Headset support (modular connector)
Built-in two-port, 10/100 Ethernet ports - lets you share a connection with
your computer
AC power adapter (included)
Enhanced busy lamp fields*
Set paging*
*Availability of feature dependant on your phone system or service provider.
41-001160-00, Release 2.1, Rev 04
1-5
Overview
This section provides brief information about the Model 53i IP Phone. It includes
a list of features, and describes the hard keys and default programmable keys on
the 53i.
IP Phone Administrator Guide
IP Phone Models
Overview
53i Key Descriptions*
Keys
Key Description
Goodbye key - Ends an active call. The Goodbye key also exits an open
list, such as the Options List, without saving changes.
Options key - Accesses options to customize your phone. Your System
Administrator may have already customized some of your settings. Check
with your System Administrator before changing the administrator-only
options.
Hold key - Places an active call on hold. To retrieve a held call, press the
call appearance button beside the light that is flashing.
Redial key - Redials up to 100 previously dialed numbers. Pressing the
Redial key twice simultaneously redials the last dialed number.
Volume control key - Adjusts the volume for the handset, headset, ringer,
and handsfree speaker.
Line/Call Appearance key - Connects you to a line or call. The Aastra 53i
IP phone supports up to 3 line keys.
Handsfree key - Activates Handsfree for making and receiving calls
without lifting the handset. When the audio mode option is set, this key is
used to switch between a headset and the handsfree speakerphone.
Mute key - Mutes the microphone so that your caller cannot hear you (the
light indicator flashes when the microphone is on mute).
1-6
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
Keys
Key Description
Pressing the LEFT and RIGHT arrow keys lets you view the different line/
call appearances. While in the Options List, these keys allow you to exit or
enter the current option. When you are editing entries on the display,
pressing the LEFT arrow key erases the character on the left; pressing the
RIGHT arrow key sets the option.
Programmable keys - 6 Top Keys: 4 keys are programmable.
Keys 1 and 2 are hardcoded as the SAVE and DELETE keys, respectively,
and cannot be altered.
The following are the default functions for the programmable keys on the
53i IP phone:
1 - SAVE
(hardcoded)
Allows you to save numbers and/or names to the
Directory. Using this key, you enter the number,
name, and line (or speeddial key) to record in the
Directory List.
2 - DELETE
Allows you to delete a single entry or all entries from
(hardcoded)
the Directory List and Callers List.
3 - DIRECTORY
Displays up to 200 names and phone numbers
(stored in alphabetical order).
4 - CALLERS LIST Accesses the last 200 calls received.
5 - TRANSFER
Transfers the active call to another number.
6 - CONFERENCE Begins a conference call with the active call.
Note: For more information about programming keys 3, 4, 5, and 6 to
perform specific functions, see Chapter 5, “Configuring Operational
Features” the section, “Softkeys/Programmable Keys/Feature Keys/
Expansion Module Keys” on page 5-93.
*See the Aastra 53i User Guide for more information about each of these keys.
41-001160-00, Release 2.1, Rev 04
1-7
Overview
Navigation keys - Pressing the UP and DOWN arrow keys lets you view
different status and text messages on the LCD display (if there is more
than 1 line of status/text messages). These buttons also let you scroll
through menu selections, such as the Options List.
IP Phone Administrator Guide
IP Phone Models
Overview
Model 55i IP Phone
This section provides brief information about the Model 55i IP Phone. It includes
a list of features, and describes the hard keys, default programmable keys, and
default softkeys on the 55i.
55i Phone Features
•
•
•
•
•
•
•
•
•
1-8
8 line graphical LCD screen (144 x 75 pixels) with white backlight
12 programmable keys
6 Top keys:Programmable hard keys
(up to 6 programmable functions)
6 Bottom keys:Programmable state-based softkeys
(up to 20 programmable functions)
4 call appearance lines with LEDs
Supports up to 9 call lines
Full-duplex speakerphone for handsfree calls
Headset support (modular connector)
Built-in-two-port, 10/100 Ethernet switch - lets you share a connection with
your computer.
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
•
Overview
•
•
•
Inline power support (based on 802.3af standard) which eliminates power
adapters.
AC power adapter (included)
Enhanced busy lamp fields*
Set paging*
*Availability of feature dependant on your phone system or service provider.
55i Key Descriptions*
Keys
Key Description
Goodbye key - Ends an active call. The Goodbye key also exits an open list, such
as the Options List, without saving changes.
Options key - Accesses options to customize your phone. Your System
Administrator may have already customized some of your settings. Check with your
System Administrator before changing the administrator-only options.
Hold key - Places an active call on hold. To retrieve a held call, press the call
appearance button beside the light that is flashing.
Redial key - Redials up to 100 previously dialed numbers. Pressing the Redial key
twice simultaneously redials the last dialed number.
Volume control key - Adjusts the volume for the handset, headset, ringer, and
handsfree speaker.
Line/Call Appearance key - Connects you to a line or call. The Aastra 55i IP phone
supports up to 4 line keys.
41-001160-00, Release 2.1, Rev 04
1-9
Keys
Key Description
Handsfree key - Activates Handsfree for making and receiving calls without lifting
the handset. When the audio mode option is set, this key is used to switch between
a headset and the handsfree speakerphone.
Mute key - Mutes the microphone so that your caller cannot hear you (the light
indicator flashes when the microphone is on mute).
Navigation keys - Pressing the UP and DOWN arrow keys lets you view different
status and text messages on the LCD display (if there is more than 1 line of status/
text messages). These buttons also let you scroll through menu selections, such as
the Options List.
Pressing the LEFT and RIGHT arrow keys lets you view the different line/call
appearances. While in the Options List, these keys allow you to exit or enter the
current option. When you are editing entries on the display, pressing the LEFT arrow
key erases the character on the left; pressing the RIGHT arrow key sets the option.
Programmable keys - 6 Top keys: programmable hard keys (up to 6 programmable
functions)
By default, the top keys 1 through 4 are assigned as Services, Directory, Callers List,
and Intercom, respectively. Keys 5 and 6 have no assigned functions. All 6 keys are
programmable and can be assigned to perform specific functions.
The following are the default functions for the programmable keys on the 55i IP
phone:
1 - SERVICES
Accesses enhanced features and services such as XML
applications and voicemail, provided by third parties.
2 - DIRECTORY
Displays up to 200 names and phone numbers (stored in
alphabetical order).
3 - CALLERS LIST Accesses the last 200 calls received.
4 - ICOM
Accesses another extension on the network.
5 - NONE
No assigned function.
6 - NONE
No assigned function.
Note: For more information about configuring the programmable keys 1 through 6 to
perform specific functions, see Chapter 5, “Configuring Operational Features” the
section, “Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys” on
page 5-93.
Overview
IP Phone Models
Keys
Key Description
By default, keys 1 through 6 have no assigned functions. You can configure all 6
bottom softkeys to perform specific functions on the 55i IP phone. However, after
you lift the handset, there are specific static softkeys that display that cannot be
changed. These are as follows:
1 - DIAL
2 - CONF
3 - XFER
Allows you to dial out on the phone.
Begins a conference call with the active phone.
Transfers the active call to another number.
Note: For more information about configuring softkeys 1 through 6 to perform
specific functions, see Chapter 5, “Configuring Operational Features” the section,
“Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys” on
page 5-93.
*See the Aastra 55i User Guide for more information about each of these keys.
41-001160-00, Release 2.1, Rev 04
1-11
Overview
Softkeys - 6 Bottom keys: programmable state-based softkeys (up to 20
programmable functions).
IP Phone Administrator Guide
IP Phone Models
Overview
Model 57i and 57i CT IP Phone
This section provides brief information about the Model 57i IP Phone. It includes
a list of features, and describes the hard keys and default softkeys on the 57i.
57i and 57i CT Phone Features
•
•
11 line graphical LCD screen (144 x 128 pixels) with white backlight
12 multi-functional softkeys
- 6 Top Keys: programmable static softkeys (up to 10 programmable
functions)
•
•
•
•
•
1-12
- 6 Bottom Keys: programmable state-based softkeys (up to 20 programmable
functions)
4 call appearance lines with LEDs
Supports up to 9 call lines
Full-duplex speakerphone for handsfree calls
Headset support (modular connector)
Built-in-two-port, 10/100 Ethernet switch - lets you share a connection with
your computer.
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
•
*Availability of feature dependant on your phone system or service provider.
57i and 57i CT Key Descriptions*
Keys
Key Description
Goodbye key - Ends an active call. The Goodbye key also exits an open list, such
as the Options List, without saving changes.
Options key - Accesses options to customize your phone. Your System
Administrator may have already customized some of your settings. Check with your
System Administrator before changing the administrator-only options.
Hold key - Places an active call on hold. To retrieve a held call, press the call
appearance button beside the light that is flashing.
Redial key - Redials up to 100 previously dialed numbers. Pressing the Redial key
twice simultaneously redials the last dialed number.
Volume control key - Adjusts the volume for the handset, headset, ringer, and
handsfree speaker.
Line/Call Appearance key - Connects you to a line or call. The Aastra 57i IP phone
supports up to 4 line keys.
41-001160-00, Release 2.1, Rev 04
1-13
Overview
•
•
•
Inline power support (based on 802.3af standard) which eliminates power
adapters.
AC power adapter (included)
Enhanced busy lamp fields*
Set paging*
IP Phone Administrator Guide
IP Phone Models
Overview
Keys
Key Description
Handsfree key - Activates Handsfree for making and receiving calls without lifting
the handset. When the audio mode option is set, this key is used to switch between
a headset and the handsfree speakerphone.
Mute key - Mutes the microphone so that your caller cannot hear you (the light
indicator flashes when the microphone is on mute).
Navigation keys - Pressing the UP and DOWN arrow keys lets you view different
status and text messages on the LCD display (if there is more than 1 line of status/
text messages). These buttons also let you scroll through menu selections, such as
the Options List.
Pressing the LEFT and RIGHT arrow keys lets you view the different line/call
appearances. While in the Options List, these keys allow you to exit or enter the
current option. When you are editing entries on the display, pressing the LEFT arrow
key erases the character on the left; pressing the RIGHT arrow key sets the option.
1-14
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
Keys
Key Description
By default, the top softkeys 1 through 4 are assigned as Services, Directory, Callers
List, and Intercom, respectively. Keys 5 and 6 have no assigned functions. All 6 keys
are programmable and can be assigned to perform specific functions.
The following are the default functions for the top softkeys on the 57i IP phone:
1 - SERVICES
Accesses enhanced features and services such as XML
applications and voicemail, provided by third parties.
2 - DIRECTORY
Displays up to 200 names and phone numbers (stored in
alphabetical order).
3 - CALLERS LIST Accesses the last 200 calls received.
4 - ICOM
Accesses another extension on the network.
5 - NONE
No assigned function.
6 - NONE
No assigned function.
By default, the bottom softkeys 7 through 12 have no assigned functions. You can
configure all 6 bottom softkeys to perform specific functions on the 57i IP phone.
However, after you lift the handset, there are specific static softkeys that display that
cannot be changed. These are as follows:
7- DIAL
8- CONF
9- XFER
Allows you to dial out on the phone.
Begins a conference call with the active phone.
Transfers the active call to another number.
Note: For more information about programming the softkeys to perform specific
functions, see Chapter 5, “Configuring Operational Features” the section, “Softkeys/
Programmable Keys/Feature Keys/Expansion Module Keys” on page 5-93.
*See the Aastra 57i or 57i CT User Guide for more information about each of these keys.
41-001160-00, Release 2.1, Rev 04
1-15
Overview
Softkeys - 12 softkeys on the 57i IP Phone.
- 6 Top Keys: programmable static softkeys (up to 10 programmable functions)
- 6 Bottom Keys: programmable state-based softkeys (up to 20 programmable
functions)
IP Phone Administrator Guide
IP Phone Models
Overview
57i CT Cordless Handset Features
•
•
•
•
•
•
5 line backlit display screen
2 multi-functional softkeys
Programmable function key supports up to 14 functions
Vibration Alerter
Headset Jack
Desk charging stand
57i CT Cordless Handset Key Descriptions
1-16
Function #
Function Description
1
Receiver
2
Volume key
During Ringing: Adjusts ringer volume
During a call: Adjusts receiver volume
During text mode (not in a call): Moves cursor right/left
3
Display
4
Features ƒ Key List
Access key to the programmed Feature Key List
Scrolls up when in the various lists
Adds a space during editing
41-001160-00, Release 2.1, Rev 04
Overview
IP Phone Models
Function Description
5
Softkeys
Activates feature or option shown on the display above
the keys
6
Call key
Used to obtain dial tone
Also used as a Hold key
7
Dial Pad
8
Mute Key
When used, prevents the caller from hearing you
9
Headset Jack
10
Status Light
11
Release key
To end calls and go on hook
Exits Menu and the various lists
12
Menu Key
Access key to the different Options
Scrolls down when in the various lists
Used as Backspace during editing
13
Redial Key
Displays the last 10 numbers dialed
14
Charging Jack
15
Charging Contacts
16
Microphone
41-001160-00, Release 2.1, Rev 04
Overview
Function #
1-17
IP Phone Administrator Guide
Firmware Installation Information
Overview
Firmware Installation Information
Description
The firmware setup and installation for the IP phone can be done using any of the
following:
•
Phone keypad menu (Phone UI)
•
Aastra Web-based user interface (Aastra Web UI)
When the IP phone is initialized for the first time, DHCP is enabled by default.
Depending on the type of configuration server setup you may have, the IP phone
may download a firmware version automatically, or you may need to download it
manually.
Installation Considerations
The following considerations must be made before connecting the IP phone to the
network:
•
If you are planning on using dynamic IP addresses, make sure a DHCP server
is enabled and running on your network.
•
If you are not planning on using dynamic IP addresses, see Chapter 4, the
section, “Configuring Network Settings Manually” on page 4-8 for manually
setting up an IP address.
To install the IP phone hardware and cabling, refer to the model-specific
SIP IP Phone Installation Guide.
1-18
41-001160-00, Release 2.1, Rev 04
Overview
Firmware Installation Information
Installation Requirements
•
SIP-based IP PBX system or network installed and running with a SIP
account created for the 53i IP phone.
•
Access to a Trivial File Transfer Protocol (TFTP), File Transfer Protocol
(FTP), Hypertext Transfer Protocol (HTTP) server, or HyperText Transfer
Protocol over Secure Sockets Layer (SSL) (HTTPS).
•
Ethernet/Fast Ethernet LAN (10/100 Mb)
•
Category 5/5e straight through cabling
•
Power source
— For Ethernet networks that supply in-line power to the phone (IEEE
802.3af):
— For power, use the Ethernet cable (supplied) to connect from the
phone directly to the network for power. (No 48v AC power adapter
required.)
— For Ethernet networks that DO NOT supply power to the phone:
— For power, use the 48V AC Power Adapter (included) to connect
from the DC power port on the phone to a power source.
or
— (optional) - For power, use a Power over Ethernet (PoE) power
injector or a PoE switch. A PoE power injector is available as an
optional accessory from Aastra Telecom. Contact your Administrator
for more information.
41-001160-00, Release 2.1, Rev 04
1-19
Overview
The following are general requirements for setting up and using your SIP IP
phone:
IP Phone Administrator Guide
Firmware Installation Information
Overview
Configuration Server Requirement
A basic requirement for setting up the IP phone is to have a configuration server.
The configuration server allows you to:
•
Store the firmware images that you need to download to your IP phone.
•
Stores configuration files for the IP phone
•
Stores the software when performing software upgrades to the IP phone
Note: If you use TFTP, the configuration server must be able to accept
connections anonymously.
Reference
To set the protocol for your configuration server, see Chapter 4, the section,
“Configuring the Configuration Server Protocol” on page 4-79.
For setting up your configuration server, see Appendix B, “Configuration Server
Setup.”
1-20
41-001160-00, Release 2.1, Rev 04
Overview
Firmware and Configuration Files
Firmware and Configuration Files
When the IP phone is initialized for the first time, DHCP is enabled by default.
Depending on the type of configuration server setup you may have, the IP phone
may download a firmware version and configuration files automatically, or you
may need to download it manually.
Note: Automatic download is dependant on your configuration server
setup.
The firmware consists of a single file called:
•
<phone model>.st
The configuration files consist of two files called:
•
aastra.cfg
•
<mac>.cfg
The following table provides the firmware for each Aastra IP phone model.
IP Phone
Model
Associated
Firmware
53i
53i.st
55i
55i.st
57i
57i.st
57i CT
57i Cordless.st
The IP Phone firmware file includes all the necessary files you need for your
phone, including the language files. Loading the language files to your phone(s) is
optional. For more information about loading languages files, see Chapter 5, the
section, “Customizing the Display Columns on the 560M Expansion Module” on
page 5-224.
41-001160-00, Release 2.1, Rev 04
1-21
Overview
Description
IP Phone Administrator Guide
Firmware and Configuration Files
Overview
Configuration File Precedence
Aastra IP phones can accept two sources of configuration data:
•
The server configuration most recently downloaded/cached from the
configuration server files, aastra.cfg/<mac>.cfg (or the aastra.tuz/<mac>.tuz
encrypted equivalents).
•
Local configuration changes stored on the phone that were entered using
either the IP phone UI or the Aastra Web UI
In the event of conflicting values set by the different methods, values are applied
in the following sequence:
1.
Default values hard-coded in the phone software
2.
Values downloaded from the configuration server
3.
Values stored locally on the phone
The last values to be applied to the phone configuration are the values that take
effect.
For example, if a parameter’s value is set in the local configuration (via Aastra
Web UI or IP phone UI) and the same value was also set differently in one of the
<mac>.cfg/aastra.cfg files on the configuration server, the local configuration
value is the value that takes effect because that is the last value applied to the
configuration.
1-22
41-001160-00, Release 2.1, Rev 04
Overview
Firmware and Configuration Files
Installing the Firmware/Configuration Files
Step
Action
1
If DHCP is disabled, manually enter the configuration server’s IP address. For details on manually
setting DHCP, see Chapter 4, the section “DHCP” on page 4-4.
2
Copy the firmware file <phone model>.st to the root directory of the configuration server. The IP
phone accepts the new firmware file only if it is different from the firmware currently loaded on the IP
phone.
Note: The <phone model> attribute is the IP phone model (i.e., 53i.st, 55i.st)
3
Copy the Aastra configuration files (aastra.cfg and <mac>.cfg) to the root directory of the
configuration server.
Note: The <mac> attribute represents the actual MAC address of your phone.
(i.e., 00085D030996.cfg).
4
Note: Restart the IP phone as described in Chapter 3, “Restarting Your Phone” on page 3-13.
41-001160-00, Release 2.1, Rev 04
1-23
Overview
The following procedure describes how to install the firmware and configuration
files.
About this chapter
Introduction
This chapter describes the methods you, as an Administrator, can use to configure
the IP phones.
Note: Features, characteristics, requirements, and configuration that are
specific to a particular IP phone models are indicated where required in
this guide.
Topics
This chapter covers the following topics:
Topic
Page
Configuration Methods
page 2-2
IP Phone UI
page 2-2
Aastra Web UI
page 2-5
Configuration Files (Administrator Only)
page 2-15
41-001160-00, Release 2.1, Rev 04
2-1
Configuration Interface Methods
Chapter 2
Configuration Interface Methods
IP Phone Administrator Guide
Configuration Methods
Configuration Interface Methods
Configuration Methods
Description
You can use the following to setup and configure the IP phone:
•
IP phone UI
•
Aastra Web UI
•
Configuration files
Note: There are specific parameters you can configure using only the IP
Phone UI, only and Aastra Web UI, only the configuration files, or a
combination of any of these methods. For more information about
configuring the phone, see Chapter 4, Chapter 5, and Chapter 6.
The following paragraphs describe each method of configuring the IP Phone.
IP Phone UI
The IP Phone User Interface (UI) provides an easy way to access features and
functions for using and configuring the IP phone. An Administrator can configure
all features and functions on the phone. A User can configure a subset of these
features and functions. Users of the IP phones should see their Model-specific
User’s Guide for available features and functions to configure.
You use the phone’s hard keys and keypad to configure specific features on the IP
phone. By default, specific softkeys/programmable keys on each phone model can
also access the Directory List and Callers List, and initiate transfers and
conference calls.
Reference
Refer to Chapter 1, the section “IP Phone Models” on page 1-2 for keys specific to
your phone model.
For more information about using the hard keys on each phone, see Chapter 5, the
section, “Locking IP Phone Keys” on page 5-28.
For more information about the softkeys/programmable keys, see Chapter 5, the
section, “Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys”
on page 5-93.
2-2
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Options Key
Note: An Administrator can apply a simplified options menu to the IP
phones. An Administrator can also enable and disable the use of an
Administrator password protection in the IP phone UI. These features are
configurable using the configuration files only.
For more information about these features, see Chapter 3, the section,
“Simplified IP Phone UI Options Menu” on page page 3-5, and Chapter
5, the section, “Administrator Passwords” on page 5-8.
This document describes the administrator options only. For a description of the
user options in the "Options List", see your model-specific SIP IP Phone User
Guide.
The following illustration indicates the location of the Options Key on each phone
model.
Options Key
53i
55i
Options Key
57i/57i CT
41-001160-00, Release 2.1, Rev 04
57i CT Handset
2-3
Configuration Interface Methods
The Options key allows you to access the "Options List" on the IP phone.
Accessible options in this list are for both user and Administrator use. An
Administrator must enter a password for administrator options.
IP Phone Administrator Guide
Configuration Methods
Configuration Interface Methods
Using the Options Key
From the 53i, 55i, or 57i/57i CT:
Step
Action
1
Press
2
Use the r and s to scroll through the list of options.
3
on the phone to enter the Options List.
On 53i:
To select an option, press the Enter softkey, or select the number on the keypad that corresponds to
the option in the Option List.
On the 55i, 57i, 57i CT:
To select an option, press the Select softkey, press 4, or select the number on the keypad that
corresponds to the option in the Option List.
4
On 53i:
Use the Set softkey after making a change to an option, to save the change.
On the 55i, 57i, 57i CT:
Use the Change softkey to change a selected option.
5
Press the Done softkey at any time to save the changes and exit the current option.
6
Press the Cancel softkey, press 3, or press
at any time to exit without saving changes.
From the 57i CT handset:
Step
Action
1
Press the  key to enter the Options List when the phone is not in use.
2
3
4
2-4
Use the scroll keys  and Ï to scroll the options.
To select and change an option, press the r keys.
Press y when done.
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Aastra Web UI
HTTP/HTTPS Support
The Aastra Web UI supports both Hypertext Transfer Protocol (HTTP) and
Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) client and server
protocols.
HTTP is the set of rules for transferring files (text, graphic images, sound,
video, and other multimedia files) over the Internet. When you open your
Web browser, you are indirectly making use of HTTP. HTTP is an
application protocol that runs on top of the TCP/IP suite of protocols (the
foundation protocols for the Internet).
HTTPS is a Web protocol that encrypts and decrypts user page requests as well as
the pages that are returned by the Web server. HTTPS uses Secure Socket Layer
(SSL) or Transport Layer Security (TLS) as a sublayer under its regular HTTP
application layering. SSL is a commonly-used protocol for managing the
security of a message transmission on the Internet. It uses a 40-bit key size
for the RC4 stream encryption algorithm, which is considered an adequate degree
of encryption for commercial exchange. TLS is a protocol that ensures privacy
between communicating applications and their users on the Internet. When a
server and client communicate, TLS ensures that no third party may eavesdrop or
tamper with any message. TLS is the successor to SSL.
Note: HTTPS uses port 443 instead of HTTP port 80 in its interactions
with the TCP/IP lower layer.
41-001160-00, Release 2.1, Rev 04
2-5
Configuration Interface Methods
An administrator can setup and configure the IP phone using the Aastra Web UI.
The Aastra Web UI supports Internet Explorer and Gecko engine-based browsers
like Firefox, Mozilla or Netscape.
IP Phone Administrator Guide
Configuration Methods
Configuration Interface Methods
HTTP/HTTPS Client and Server Support
2-6
The Aastra IP phones allow for HTTP request processing and associated data
transfers to perform over a secure connection (HTTPS). The IP phones support
the following:
•
Transfer of firmware images, configuration files, script files, and web page
content over a secure connection.
•
Web browser phone configuration over a secure connection.
•
TLS 1.0or SSL 3.0 methods for both client and server
HTTPS Client
When an HTTPS client opens and closes its TCP socket, the SSL software
respectively handshakes upon opening and disconnects upon closing from the
HTTPS server. The main HTTPS client functions are:
•
Downloading of configuration files and firmware images.
•
Downloading of script files based on an “HTTPS://” URL supplied by a
softkey definition.
HTTPS Server
The HTTPS server provides HTTP functionality over secure connections. It
coexists with the HTTP server but has its own set of tasks. The main HTTPS
server functions are:
•
Delivery of web page content to a browser client over a secure connection.
•
Execution of HTTP GET and POST requests received over a secure
connection.
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Using HTTPS via the Aastra Web UI
Notes:
1. The private key and certificate generate outside the phone and embed
in the phone firmware for use by the HTTPS server during the SSL
handshake.
2. Using the configuration files, the IP phone UI, or the Aastra Web UI,
you can configure the following regarding HTTPS:
- Specify HTTPS security client method to use (TLS 1.0 or SSL 3.0)
- Enable or disable HTTP to HTTPS server redirect function
- HTTPS server blocking of XML HTTP POSTS to the phone
Reference
For more information on configuring the HTTPS protocol, see Chapter 4,
“Configuring Network and Session Initiation Protocol (SIP) Features”, the
sections:
•
“Configuring the Configuration Server Protocol” on page 4-79
•
“HTTPS Client/Server Configuration” on page 4-23
41-001160-00, Release 2.1, Rev 04
2-7
Configuration Interface Methods
HTTPS is enabled by default on the IP phones. When you open a browser window
and enter an IP address or host name for a phone using HTTP, a server redirection
occurs which automatically converts an HTTP connection to an HTTPS
connection. After the redirection, a “Security Alert” certificate window displays
alerting the user that information exchanged with the phone cannot be viewed or
changed by others. Accepting the certificate then forwards you to the phone’s Web
UI.
IP Phone Administrator Guide
Configuration Methods
Configuration Interface Methods
Accessing the Aastra Web UI
Use the following procedure to access the Aastra Web UI.
Step
Action
1
Open your web browser and enter the phone’s IP address or host name into the address field.
The following Login screen displays.
2-8
IP address or
host name
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Action
2
Enter your username and password and click
.
Note: For an administrator, the default username is “admin” and the password is “22222”.
For a user, the default username is “user” and the password field is left blank.
The IP phones accept numeric passwords only.
The Network Status window displays for the IP phone you are accessing. The following illustration is
an example of a Network Status screen for the 55i IP phone.
55i Network
Status Window
Logout button
3
You can logout of the Aastra Web UI at any time by clicking LOGOFF.
41-001160-00, Release 2.1, Rev 04
2-9
Configuration Interface Methods
Step
The following categories display in the side menu of the Aastra Web UI: Status,
Operation, Basic Settings, Advanced Settings.
Status
The Status section displays the network status and the MAC address of the IP
phone. It also displays hardware and firmware information about the IP phone.
The information in the Network Status window is read-only.
Operation
The Operation section provides the following options:
Heading
Description
User Password
Allows you to change user password.
(Applicable to User and Administrator).
Phone Lock
Allows you to assign an emergency dial plan to the phone,
lock the phone to prevent any changes to the phone and to
prevent use of the phone, and reset the user password.
Note: You can also configure a softkey to use for locking/
unlocking the phone.
(Applicable to User and Administrator).
Programmable Keys
53i - 6 Top programmable keys (up to 4 programmable
functions)
55i - 6 Top programmable hard keys (up to 6 programmable
functions)
(Applicable to User and Administrator).
Softkeys and XML
55i - 6 Bottom programmable state-based softkeys (up to 20
programmable functions)
57i/57i CT - 6 Top programmable, static softkeys (up to 10
programmable functions; and 6 bottom programmable
state-based softkeys (up to 20 programmable functions)
(Applicable to User and Administrator).
Configuration Interface Methods
Configuration Methods
Description
Expansion Module <N>
The 536M has up to 36 configurable keys. The 560M has up
to 60 configurable keys. You can have up to 3 expansion
modules attached to a single phone allowing you to
configure keys for Expansion Module 1, Expansion Module
2, and Expansion Module 3.See your Model-specific User
Guide for applicable expansion modules for your model
phone.
(Applicable to User and Administrator).
Handset Keys
(57i CT only)
Allows you to configure up to 15 softkeys on the handset.
(Applicable to User and Administrator).
Directory
Allows you to copy the Callers List and Directory List from
your IP phone to your PC.
(Applicable to User and Administrator).
Reset
Allows you to restart the IP phone when required.
(Applicable to User and Administrator).
This setting also allows you to set the IP phone back to its
factory default settings or remove the local configuration.
(Applicable Administrator only).
41-001160-00, Release 2.1, Rev 04
2-11
Configuration Interface Methods
Heading
IP Phone Administrator Guide
Configuration Methods
Configuration Interface Methods
Basic Settings
The Basic Settings section provides the following options:
Heading
Description
Preferences
Allows you to set the following General specifications on the
IP phone.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
This section also allows you to set:
•
•
•
•
•
•
•
•
•
Call Forward
2-12
Local Dial Plan (Admin Only)
Send Dial Plan Terminator (Admin Only)
Digit Timeout (Admin Only)
Park Call (not available on 53i)
Pickup Parked Call (not available on 53i)
Suppress DTMF Playback
Display DTMF Digits
Call Waiting
Play Call Waiting Tone
Stuttered Dial Tone
XML Beep Support
Status Scroll Delay
Incoming Call Interrupts Dialing
Goodbye Key Cancels Incoming Call
UPnP Mapping Lines
Message Waiting Indicator Line
Incoming Intercom Settings
Outgoing Intercom Settings (Admin Only; Administrator
can enable these or a User if required)
Key Mapping (Admin Only)
Ring Tones
Priority Alert Settings (Admin Only)
Directed Call Pickup Settings (Admin Only)
Auto Call Distribution Settings (Admin Only)
Time and Date Settings
Language Settings (Admin only can specify the
language pack names to load to the phone).
Allows you to set a phone number destination for where you
want calls forwarded.
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Advanced Settings
Heading
Description
Network
Allows you to set Basic Network Settings, Advanced
Network Settings, Type of Service DSCP, and VLAN
settings.
(Applicable to Administrator Only)
Global SIP
Allows you to set global Basic SIP Authentication Settings,
Basic SIP Network Settings, Advanced SIP Settings,
Real-time Transport Protocol (RTP) settings, and Autodial
Settings that apply to all lines on the IP phone.
(Applicable to Administrator Only)
Lines 1 through 9
Allows you to set per-line Basic SIP Authentication Settings,
Basic SIP Network Settings, Advanced SIP Settings,
Real-time Transport Protocol (RTP) settings, and Autodial
Settings that apply to specific lines on the IP phone.
(Applicable to Administrator Only)
Action URI
Allows an administrator to specify a uniform resource
identifier (URI) that triggers a GET when certain events
occur.
(Applicable to Administrator Only)
Configuration Server
Allows you to set the protocol to use on the configuration
server (TFTP (default), FTP, HTTP, or HTTPS), configure
automatic firmware and configuration file updates, enable/
disable auto-resync, and assign an XML push server list.
(Applicable to Administrator Only)
Firmware Update
Allows you to manually perform a firmware update on the IP
phone from the configuration server.
(Applicable to Administrator Only)
41-001160-00, Release 2.1, Rev 04
2-13
Configuration Interface Methods
The Advanced Settings section provides the following options:
Configuration Interface Methods
IP Phone Administrator Guide
Configuration Methods
Heading
Description
TLS Support
Allows you to specify the SIP Root and Intermediate
Certificate files to use when the phone uses the TLS
transport protocol to setup a call.
(Applicable to Administrator Only)
Troubleshooting
Allows you to perform troubleshooting tasks whereby the
results can be forwarded to Aastra Technical Support for
analyzing and troubleshooting.
(Applicable to Administrator Only)
Enabling/Disabling the Aastra Web UI
The Aastra Web UI is enabled by default on the IP phones. A System
Administrator can disable the Aastra Web UI on a single phone or on all phones if
required using the configuration files. Use the following procedure to enable and
disable the Aastra Web UI.
To disable the Aastra Web UI:
Configuration Files
Step
Action
1
Using a text-based editing application, open the <mac>.cfg file if you want to disable the Web UI on a
single phone. Open the aastra.cfg file to disable the Web UI on all phones
2
Enter the following parameter:
web interface enabled: 0
Note: A value of zero (0) disables the Web UI on the phone. A value of 1 enables the Web UI.
3
Save the changes and close the <mac>.cfg or the aastra.cfg file.
4
Restart the phone to apply the changes. The Aastra Web UI is disabled for a single IP phone or for all
phones.
2-14
41-001160-00, Release 2.1, Rev 04
Configuration Interface Methods
Configuration Methods
Configuration Files (Administrator Only)
You can enter specific configuration parameters in either of the following
configuration files:
•
aastra.cfg
•
<mac>.cfg
References
For information about configuration file precedence, see Chapter 1, “Overview.”
For a description of each configuration file parameter, see Appendix A,
“Configuration Parameters.”
Using the Configuration Files
When you use the configuration files to configure the IP phones, you must use a
text-based editing application to open the configuration file (aastra.cfg or
<mac>.cfg).
Use the following procedure to add, delete, or change parameters and their
settings in the configuration files.
Note: Apply this procedure wherever this Administrator Guide refers to
configuring parameters using the configuration files.
41-001160-00, Release 2.1, Rev 04
2-15
Configuration Interface Methods
A system administrator can enter specific parameters in the configuration files to
configure the IP phones. All parameters in configuration files can only be set by
an administrator.
Configuration Interface Methods
IP Phone Administrator Guide
Configuration Methods
Configuration files
Step
Action
1
Using a text-based editing application, open the configuration file for the phone, for which you want to
configure the directory list (either aastra.cfg, <mac>.cfg or both).
2
Enter the required configuration parameters followed by the applicable value. For example,
directory 1: company_directory
directory 2: my_personal_directory
3
Save the changes and close the configuration file.
4
If the parameter requires the phone to be restarted in order for it to take affect, use the
IP Phone UI or the Aastra Web UI to restart the phone.
2-16
41-001160-00, Release 2.1, Rev 04
About this chapter
Introduction
The IP phones provide specific options on the IP Phone that only an Administrator
can access. These options are password protected and allow an Administrator to
change or set features and configuration information as required. For all models,
an Administrator can use the IP Phone UI, the Aastra Web UI, or the configuration
files to enter and change values.
Note: Specific options are configurable only via the IP Phone UI, and/or
Aastra Web UI, and/or configuration files.
This chapter provides information about the available Administrator options.
Topics
This chapter covers the following topics:
Topic
Page
Administrator Level Options
page 3-3
IP Phone UI Options
page 3-3
Aastra Web UI Options
page 3-7
Configuration File Options
page 3-9
Phone Status
page 3-10
Restarting Your Phone
page 3-13
Set Phone to Factory Defaults/Erase Local Configuration
page 3-15
Basic Settings
page 3-19
41-001160-00, Release 2.1, Rev 04
3-1
Administrator Options
Chapter 3
Administrator Options
IP Phone Administrator Guide
About this chapter
Administrator Options
Topic
3-2
Page
Network Settings
page 3-31
Line Settings
page 3-56
Softkeys, Programmable Keys, Expansion Module Keys
page 3-57
Action URI
page 3-58
Configuration Server Settings
page 3-59
Firmware Update Features
page 3-66
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Administrator Level Options
There are options on the IP phone that both a User and Administrator can access.
However, there are specific options that an Administrator can access only. These
options allow the Administrator to configure and manage local and/or remote IP
phones in a network.
An Administrator can access and manage these options using the IP Phone UI, the
Aastra Web UI, or the configuration files.
IP Phone UI Options
Using the IP Phone UI, you can access the Administrator options at
Options->Administrator Menu using the default password of "22222"
Options Menu
1. Call Forward
2. Preferences
3. Phone Status
4. User Password
5. Administrator Menu
6. Restart Phone
7. Phone Lock
8. Handset Pairing
Administrator Menu
Handset Pairing
displays for CT
Models only.
Select
Done
Note: An administrator has the option of enabling and disabling the use
of password protection in the IP phone UI. This is configurable using the
configuration files only. For more information about this feature, see
Appendix A, the section “Password Settings” on page A-9.
41-001160-00, Release 2.1, Rev 04
3-3
Administrator Options
Description
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
The following are administrator options in the "Options List" on the IP phone UI:
3-4
•
Administrator Menu
— Configuration Server
— Network Settings
— SIP Settings
— Factory Default
— Erase Local Config.
References
For information about all other user options in the “Options Menu”, see your
model-specific SIP IP Phone User Guide.
For procedures on configuring Administrator Options on the IP phone via the IP
phone UI, see:
Chapter 4, “Configuring Network and Session Initiation Protocol (SIP) Features”
Chapter 5, “Configuring Operational Features”
Chapter 6, “Configuring Advanced Operational Features”
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Simplified IP Phone UI Options Menu
When setting the “options simple menu” parameter, the menu changes in the
Phone UI only. The Aastra Web UI is not affected.
Full Options Menu
Simplified Options Menu
Call Forward
Call Forward
Preferences
Preferences
Phone Status
Phone Status
User Password
Removed
Administrator Menu
Removed
Restart Phone
Removed
Phone Lock
Phone Lock
Handset Pairing
(CT models only)
Handset Pairing
(CT models only)
Warning: When using the simplified menu, you cannot change the
Network settings from the IP Phone UI. If the network settings become
misconfigured, you must “factory default” the phone and use the full
menu to recover the network settings from the Phone UI OR use the
Aastra Web UI to configure the network settings.
41-001160-00, Release 2.1, Rev 04
3-5
Administrator Options
An Administrator can replace the existing options menu on the Phone UI with a
more simplified options menu. In the configuration files, the “options simple
menu” parameter allows you to display either the full menu (if set to 0), or the
simplified menu (if set to 1). The following table illustrates the differences
between the full menu and the simplified menu.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Configuring the Simplified IP Phone UI Options Menu
You can enable the simplified IP Phone UI Options menu using the configurations
files only.
Configuration Files
For the specific parameter you can set in the configuration files, see Appendix A, the section, “Simplified IP
Phone UI Options Menu” on page A-5.
3-6
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Aastra Web UI Options
Administrator Web UI Menu
41-001160-00, Release 2.1, Rev 04
User Web UI Menu
3-7
Administrator Options
An Administrator can configure specific options using the Aastra Web UI. These
options display after an Administrator logs into the Web UI using a Web browser
and entering the Admin username and password at the login prompt (The default
username is "admin" and the default password is "22222". The IP phones accept
numeric passwords only.) The column on the left side of the screen indicates the
configurable options. A User has limited configuration options as shown in the
following illustrations.
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
The following are options that an Administrator can configure in the Aastra Web
UI (and are not available for the User to configure):
•
•
•
•
Basic Settings->Preferences->Key Mapping
•
Basic Settings->Preferences->Priority Alerting Settings
•
Basic Settings->Preferences->Directed Call Pickup Settings
•
Basic Settings->Preferences->Auto Call Distribution Settings
•
Basic Settings->Preferences->Language Settings
— Language 1 (entering language pack filename)
— Language 2 (entering language pack filename)
— Language 3 (entering language pack filename)
— Language 4 (entering language pack filename)
Advanced Settings
— Network
— Global SIP
— Line 1 through 9 Settings
— Action URI
— Configuration Server
— Firmware Update
— TLS Support
— Troubleshooting
•
3-8
Operation->Reset
— Restore to Factory Defaults
— Remove Local Configuration Settings
Basic Settings->Preferences->General
— Local Dial Plan
— Send Dial Plan Terminator
— Digit Timeout (seconds)
Basic Settings->Preferences->Outgoing Intercom Settings (User can
configure this via the Aastra Web UI if enabled by an Administrator)
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
References
For procedures to Restart your phone or restore factory defaults, see “Restarting
Your Phone” on page 3-13, and “Set Phone to Factory Defaults/Erase Local
Configuration” on page 3-15.
For more information about Advanced Settings for the IP Phone, see Chapter 4,
“Configuring Network and Session Initiation Protocol (SIP) Features.”
For procedures on configuring the Basic Settings for the IP Phone, see Chapter 5,
“Configuring Operational Features.”
Configuration File Options
An Administrator can enter specific parameters in the configuration files to
configure the IP phones. All parameters in configuration files can only be set by
an administrator.
References
For a procedure on using the configuration files, see Chapter 2, the section,
“Configuration Files (Administrator Only)” on page 2-1.
For a description of each parameter you can enter in the configuration files, see
Appendix A, “Configuration Parameters.”
41-001160-00, Release 2.1, Rev 04
3-9
Administrator Options
For information about options available to a User AND Administrator in the
Aastra Web UI, see your Model-specific User Guide.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Phone Status
The Phone Status on the IP Phone displays the network status and firmware
version of the IP phone.
You can display phone status using the IP phone UI or the Aastra Web UI.
Phone Status via IP Phone UI
In the IP phone UI, the Phone Status options are available to the user and the
administrator and do not require a password entry.
The following options display for phone status on the IP phone UI:
Phone Status Screen for 53i Phone
Phone Status
1. IP&MAC Addresses
2. LAN Port
3. PC Port
4. Firmware Info
=Next
=Enter
Phone Status Screen for 55i, 57i, and 57i CT Phones
Phone Status
1. IP&MAC Addresses
2. LAN Port
3. PC Port
4. Firmware Info
Select
Done
3-10
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
IP&MAC Addresses
Displays the IP address and MAC address of the phone.
•
LAN Port
Displays the Link State, Negotiation Method, Speed, and Duplex Method that
the phone uses on its LAN port.
•
PC Port
Displays the Link State, Negotiation Method, Speed, and Duplex Method that
the phone uses on its PC Port.
•
Firmware Info
Displays information about the firmware that is currently installed on the IP
phone.
Phone Status via Aastra Web UI
In the Aastra Web UI, the "Network Attributes", "Hardware Information", and
"Firmware Information" options display on the Network Status screen.
41-001160-00, Release 2.1, Rev 04
3-11
Administrator Options
•
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
3-12
The following information displays for phone status in the Aastra Web UI at the
location Status->System Information. This information is available to the user
and the administrator as read-only.
•
Network Attributes
Displays the network status of the Ethernet ports at the back of the phone. You
can also view the phone’s IP and MAC addresses. Information in this field
includes Link State, Negotiation, Speed, and Duplex for Port 0 and Port 1.
•
Hardware Information
Displays the current IP phone platform and the revision number.
•
Firmware Information
Displays information about the firmware that is currently installed on the IP
phone. Information in this field includes Firmware Version, Firmware Release
Code, Boot Version, Release Date/Time.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Restarting Your Phone
•
There is a change in your network, OR
•
To re-load modified configuration files, OR
•
If the settings for the IP phone on the IP PBX system have been modified.
You can restart the phone using the IP Phone UI or the Aastra Web UI.
Restarting the Phone Using the IP Phone UI
IP Phone UI
Step
Action
1
Press
2
Select Restart Phone.
3
For 53i:
Press # to confirm.
on the phone to enter the Options List.
Note: To cancel the Restart, press the 3 key.
For 55i, 57i, 57i CT:
Press Restart.
Note: To cancel the Restart, press Cancel.
41-001160-00, Release 2.1, Rev 04
3-13
Administrator Options
As System Administrator, there may be times when you need to restart a phone.
The Restart option allows you reboot the phone when required. A reset may be
necessary when:
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Restarting the Phone Using the Aastra Web UI
Aastra Web UI
1
Click on Operation->Reset->Phone.
2
Click
3-14
to restart the phone.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Set Phone to Factory Defaults/Erase Local Configuration
Setting Factory Defaults on the Phone
Factory default settings are the settings that reside on the phone after it has left the
factory. The factory default settings on the phone sets the factory defaults for all
of the settings in the aastra.cfg, <mac>.cfg, and local configuration. Performing
this action results in losing all user-modified settings.You can reset a phone to
factory defaults using the IP Phone UI or the Aastra Web UI.
Setting Factory Defaults Using the IP Phone UI
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu and enter your Administrator Password (default is 22222).
3
Select Factory Default.
4
For 53i:
The “Restore Defaults?” prompt displays.
Press # to confirm.
on the phone to enter the Options List.
For 55i/57i/57i CT:
The “Reset phone to factory defaults?” prompt displays.
Press Default to confirm.
41-001160-00, Release 2.1, Rev 04
3-15
Administrator Options
You can set phones to their factory default setting or remove a local phone’s
configuration using the IP Phone UI or the Aastra Web UI.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Settings Factory Defaults Using the Aastra Web UI
Aastra Web UI
Step
Action
1
Click on Operation->Reset->Current Settings.
2
In the "Restore to Factory Defaults" field, click
3-16
.
This restores all factory defaults, and removes any saved configuration and directory list files.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Erasing the Phone’s Local Configuration
Erasing the Phone’s Local Configuration Using the IP Phone UI
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu and enter your Administrator Password (default is 22222).
3
Select Erase Local Config.
4
For 53i:
The “Erase local config?” prompt displays.
Press # to confirm.
on the phone to enter the Options List.
For 55i/57i/57i CT:
The “Erase local config?” prompt displays.
Press Erase to confirm.
41-001160-00, Release 2.1, Rev 04
3-17
Administrator Options
You can reset the IP Phone’s local configuration if required. The local
configuration is the last updated configuration you performed using the IP Phone
UI or the Aastra Web UI. Performing this action results in losing all recently
user-modified settings. For more information about local configuration, see
Chapter 1, the section, “Configuration File Precedence” on page 1-22.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Erasing the Phone’s Local Configuration Using the Aastra Web UII
Aastra Web UI
Step
Action
1
Click on Operation->Reset->Current Settings.
2
In the "Remove Local Configuration Settings" field, click
3-18
.
This removes the last customized configuration settings made on the phone.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Basic Settings
General Settings
Parameter in
Aastra Web UI
Local Dial Plan
Parameter in
Configuration Files
sip dial plan
Description
A dial plan that describes the number and pattern of
digits that a user dials to reach a particular telephone
number.
For more information on this feature, see “Local Dial
Plan” on page 5-30.
Send Dial Plan
Terminator
sip dial plan terminator
Allows you to enable or disable a dial plan terminator.
When you configure the dial plan on the phone to use
a dial plan terminator (such as the pound symbol (#)),
the phone waits 4 or 5 seconds after you pick up the
handset or after dialing the number on the keypad
before making the call.
For more information on this feature, see “SIP Dial
Plan Terminator” on page 5-32.
Digit Timeout
sip digit timeout
Represents the time, in seconds, to configure the
timeout between consecutive key presses.
For more information on this feature, see. “Digit
Timeout” on page 5-32.
41-001160-00, Release 2.1, Rev 04
3-19
Administrator Options
An Administrator has access to specific Basic Setting options to configure and
manage the IP Phone in the network. The following sections identify the options
available to an Administrator only, or where indicated, to a User and
Administrator. These tables also identify whether you can configure them using
the Aastra Web UI, IP Phone UI, or the configuration files.
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter in
Aastra Web UI
Park Call
Parameter in
Configuration Files
sprecode
Note: This option can
be set by both Users
and Administrators.
Description
The parking of a live call to a specific extension.
This feature on the Basic Preferences screen is
available on the 55i, 57i, and 57i CT only.
To configure the Park feature on a global basis, see
Chapter 5, the section, “Park Calls/Pick Up Parked
Calls” on page 35.
To configure the Park feature on a key, see Chapter 5,
the section, “Park/Pick Up Key” on page 5-153.
Pick Up Parked Call
pickupsprecode
Picking up a parked call at the specified extension.
This feature on the Basic Preferences screen is
available on the 55i, 57i, and 57i CT only.
Note: This option can
be set by both Users
and Administrators.
To configure the Pickup feature on a global basis, see
Chapter 5, the section, “Park Calls/Pick Up Parked
Calls” on page 35.
To configure the Pickup feature on a key, see Chapter
5, the section, “Park/Pick Up Key” on page 5-153.
Suppress DTMF
Playback
suppress dtmf playback
Note: This option can
be set by both Users
and Administrators.
Display DTMF Digits
For more information on this feature, see.
“Suppressing DTMF Playback” on page 5-39.
display dtmf digits
Note: This option can
be set by both Users
and Administrators.
Call Waiting
Note: This option can
be set by both Users
and Administrators.
3-20
Enables and disables suppression of DTMF playback
when a number is dialed from the softkeys or
programmable keys.
Enables and disables the display of DTMF digits on
the IP phone display during a connected state.
For more information on this feature, see. “Display
DTMF Digits” on page 5-41.
call waiting
Enable or disables Call Waiting on the IP Phone.
For more information on this feature, see. “Call
Waiting/Call Waiting Tone” on page 5-43.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Play Call Waiting Tone
Parameter in
Configuration Files
call waiting tone
Note: This option can
be set by both Users
and Administrators.
Stuttered Dial Tone
Enable or disables the playing of a call waiting tone
when a caller is on an active call and a new call comes
into the phone.
For more information on this feature, see. “Call
Waiting/Call Waiting Tone” on page 5-43.
stutter disabled
Note: This option can
be set by both Users
and Administrators.
XML Beep Support
Description
Enable or disables the playing of a stuttered dial tone
when there is a message waiting on the IP phone.
For more information on this feature, see. “Stuttered
Dial Tone” on page 5-46.
xml beep notification
Note: This option can
be set by both Users
and Administrators.
Enables or disables the playing of a beep to indicate a
status on the phone. When the phone receives a
status message, the BEEP notifies the user that the
message is displaying.
For more information on this feature, see “XML Beep
Support” on page 5-48.
Status Scroll Delay
(seconds)
xml status scroll delay
Allows you to set the time delay, in seconds, between
the scrolling of each status message on the phone.
Note: This option can
be set by both Users
and Administrators.
For more information on this feature, see “Status
Scroll Delay” on page 5-50.
Incoming Call Interrupts incoming call interrupts
Dialing
dialing
Enable or disables how the phone handles incoming
calls while the phone is dialing out. For more
information on this feature, see “Incoming Call
Interrupts Dialing” on page 5-52.
Note: This option can
be set by both Users
and Administrators.
Goodbye Key Cancels
Incoming Call
goodbye key cancels
incoming call
Note: This option can
be set by both Users
and Administrators.
41-001160-00, Release 2.1, Rev 04
Enable or disables the behavior of the Goodbye Key
on the IP phone.
For more information on this feature, see “Goodbye
Key Cancels Incoming Call” on page 5-54.
3-21
Administrator Options
Parameter in
Aastra Web UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter in
Aastra Web UI
UPnP Mapping Lines
Parameter in
Configuration Files
upnp mapping lines
Note: This option can
be set by both Users
and Administrators.
Message Waiting
Indicator Line
Description
Enables or disables the use of Universal Plug and
Play (UpnP) on a specific line on the IP phone.
For more information on this feature, see “UPnP
Mapping Lines (for remote phones)” on page 5-56.
mwi led line
Note: This option can
be set by both Users
and Administrators.
Allows you to enable the Message Waiting Indicator
(MWI) on a single line or on all lines on the phone. For
example, if you set this parameter to 3, the LED
illuminates if a voice mail is pending on line 3. If you
set this parameter to 0, the LED illuminates if a voice
mail is pending on any line on the phone (lines 1
through 9).
For more information on this feature, see “Message
Waiting Indicator Line” on page 5-58.
Incoming/Outgoing Intercom Calls
The Incoming/Outgoing Intercom Call settings on the IP Phone specify
whether the IP phone or the server is responsible for notifying the recipient that an
Intercom call is being placed. These settings also specify the prefix code for
server-side Intercom calls, and specifies the configuration to use when making the
Intercom call.
Parameter in
Aastra Web UI
Parameter in
Configuration Files
Description
Incoming Intercom Settings (all models)
Auto-Answer
Note: This option can
be set by both Users
and Administrators.
sip allow auto answer
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.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
3-22
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Microphone Mute
Parameter in
Configuration Files
sip intercom mute mic
Note: This option can
be set by both Users
and Administrators.
Play Warning Tone
Enables or disables the microphone on the IP phone
for Intercom calls made by the originating caller.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
sip play warning tone
Note: This option can
be set by both Users
and Administrators.
Allow Barge In
Description
Enables or disables a warning tone to play when the
phone receives an incoming intercom call on an active
line.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
sip intercom allow barge Enable or disables how the phone handles incoming
in
intercom calls while the phone is on an active call.
Note: This option can
be set by both Users
and Administrators.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
Outgoing Intercom Settings (55i, 57i, and 57i CT only))
Type
sip intercom type
Determines whether the IP phone or the server is
responsible for notifying the recipient that an Intercom
call is being placed. Applicable settings are
Phone-Side, Server-Side, OFF.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
41-001160-00, Release 2.1, Rev 04
3-23
Administrator Options
Parameter in
Aastra Web UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter in
Aastra Web UI
Prefix Code
Parameter in
Configuration Files
sip intercom prefix code
Description
The prefix to add to the phone number for server-side
outgoing Intercom calls. This parameter is required for
all server-side Intercom calls.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
Line
3-24
sip intercom line
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.
For more information on this feature, see “Incoming/
Outgoing Intercom with Auto-Answer and Barge In” on
page 5-60.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Key Mapping
Map Redial Key To
Parameter in
Configuration Files
map redial key to
Description
Sets the Redial key as a speeddial key if a value is
entered for this parameter. If you leave this parameter
blank, the Redial key returns to its original
functionality.
Note: If you configure the Redial key for speeddialing
on the 57i CT Base Station, the Redial key on the 57i
CT handset retains its original functionality. The
Redial key on the handset is not configured for
speeddial.
For more information on this feature, see “Key
Mapping” on page 5-66.
Map Conf Key To
map conf key to
Sets the Conf key as a speeddial key if a value is
entered for this parameter. If you leave this parameter
blank, the Conf key returns to its original functionality.
Note: If you configure the Conf key for speeddialing
on the 57i CT Base Station, the Conf key on the 57i
CT handset retains its original functionality. The Conf
key on the handset is not configured for speeddial.
For more information on this feature, see “Key
Mapping” on page 5-66.
41-001160-00, Release 2.1, Rev 04
3-25
Administrator Options
Parameter in
Aastra Web UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Ring Tones
Parameter in
IP Phone UI
Tone Set
Parameter in
Aastra Web UI
Tone Set
Parameter in
Configuration Files
tone set
Note: This option can
be set by both Users
and Administrators.
Ring Tone
Globally sets a tone set for a
specific country
For more information on this
feature, see “Ring Tones and
Tone Sets” on page 5-70.
Global Ring Tone
ring tone
Note: This option can
be set by both Users
and Administrators.
N/A
Description
Globally sets the type of ring tone
on the IP phone. Ring tone can
be set to one of six distinct rings.
For more information on this
feature, see “Ring Tones and
Tone Sets” on page 5-70.
LineN
lineN ring tone
Note: This option can
be set by both Users
and Administrators.
Sets the type of ring tone on the
IP phone on a per-line basis.
Ring tone can be set to one of six
distinct rings.
For more information on this
feature, see “Ring Tones and
Tone Sets” on page 5-70.
Priority Alerting Settings
Parameter in
Aastra Web UI
Enable Priority Alerting
Parameter in
Configuration Files
priority alerting enabled
Description
Enables and disables distinctive ringing on the IP
phone for incoming calls and call-waiting calls.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Group
alert group
When an "alert group" keyword appears in the header
of the INVITE request, the configured Bellcore ring
tone is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
3-26
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
External
Parameter in
Configuration Files
alert external
Description
When an "alert external" keyword appears in the
header of the INVITE request, the configured Bellcore
ring tone is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Internal
alert internal
When an "alert-internal" keyword appears in the
header of the INVITE request, the configured Bellcore
ring tone is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Emergency
alert emergency
When an "alert emergency" keyword appears in the
header of the INVITE request, the configured Bellcore
ring tone is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Priority
alert priority
When an "alert priority" keyword appears in the
header of the INVITE request, the configured Bellcore
ring tone is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Auto Call Distribution
alert auto call distribution When an "alert-acd" keyword appears in the header of
the INVITE request, the configured Bellcore ring tone
is applied to the IP phone.
For more information on this feature, see “Priority
Alerting” on page 5-75.
Community 1 thru
Community 4
alert community 1
alert community 2
alert community 3
alert community 4
When an "alert community-#” keyword appears in the
header of the INVITE request, the configured Bellcore
ring tone is applied to the IP phone. Available Bellcore
tones are:
0 Normal ringing (default)
1 Bellcore-dr2
2 Bellcore-dr3
3 Bellcore-dr4
4 Bellcore-dr5
5 Silent
For more information on this feature, see “Priority
Alerting” on page 5-75.
41-001160-00, Release 2.1, Rev 04
3-27
Administrator Options
Parameter in
Aastra Web UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Directed Call Pickup (DCP)
Parameter in
Aastra Web UI
Directed Call Pickup
Parameters in
Configuration Files
directed call pickup
Description
Enables or disables the use of "directed call pickup"
feature.
For more information on this feature, see “Directed
Call Pickup (BLF or XML Call Interception)” on
page 5-81.
Directed Call Pickup
Prefix
directed call pickup
prefix
Allows you to specify a prefix to use for "directed call
pickup" that you can use with a BLF or BLF List
softkey.
For more information on this feature, see “Directed
Call Pickup (BLF or XML Call Interception)” on
page 5-81.
Play a Ring Splash
3-28
play a ring splash
Enables or disables the playing of a short "ring splash
tone" when there is an incoming call on the BLF
monitored extension. If the host tone is idle, the tone
plays a "ring splash".
For more information on this feature, see “Directed
Call Pickup (BLF or XML Call Interception)” on
page 5-81.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Auto Call Distribution (ACD) Settings
Auto Available
Parameters in
Configuration Files
acd auto available
Description
Enables or disables the use of the ACD Auto-Available
Timer.
For more information on this feature, see “Automatic
Call Distribution (ACD) (for Sylantro Servers)” on
page 5-122.
Auto Available Timer
acd auto available timer
Specifies the length of time, in seconds, before the IP
phone status switches back to “available.”
For more information on this feature, see “Automatic
Call Distribution (ACD) (for Sylantro Servers)” on
page 5-122.
Time and Date
Parameter in
IP Phone UI
Time Format
Parameter in
Aastra Web UI
Time Format
Parameters in
Configuration Files
time format
Note: This option can
be set by both Users
and Administrators.
Description
This parameter changes the time
to 12 hour or 24 hour format. Use
“0” for the 12 hour format and “1”
for the 24 hour format.
For more information on this
feature, see “Time and Date” on
page 5-17.
Date Format
Date Format
Note: This option can
be set by both Users
and Administrators.
41-001160-00, Release 2.1, Rev 04
date format
This parameter allows the user to
change the date to various
formats
For more information on this
feature, see “Time and Date” on
page 5-17.
3-29
Administrator Options
Parameter in
Aastra Web UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Language
Parameter in
Aastra Web UI
WebPage Language
Parameter in
Configuration Files
language
Note: This option can
be set by both Users
and Administrators.
Description
The language you want to display in the IP Phone UI
and the Aastra Web UI.
Valid values for 53i, 55i, 57i are:
0 (English)
1 (French - Canadian)
2 (Spanish - Mexican)
3 (German)
4 (Italian)
Valid values for 57i CT are:
0 (English)
1 (French - Canadian)
2 (Spanish - Mexican)
Note: All languages may not be available for
selection. The available languages are dependant on
the language packs currently loaded to the IP phone.
For more information about loading language packs,
see “Loading Language Packs” on page 5-21.
For more information on this feature, see “Language”
on page 5-21.
Language 1 thru
Language
language N
The language pack you want to load to the IP phone.
Valid values are:
lang_fr-ca.txt
lang_es.txt
lang_de.txt
lang_it.txt
Notes:
1. The languages packs you load are dependant on
available language packs from the configuration
server.
2. You must reboot the phone to load a language
pack.
For more information about loading language packs,
see “Loading Language Packs” on page 5-21.
For more information on this feature, see “Language”
on page 5-21.
3-30
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Network Settings
•
Basic network settings
•
Advanced network settings
Note: Specific parameters are configurable using the Aastra Web UI only
and are indicated where applicable.
41-001160-00, Release 2.1, Rev 04
3-31
Administrator Options
The following paragraphs describe the network parameters you can configure on
the IP phone. Network settings are in two categories:
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Basic Network Settings
If Dynamic Host Configuration Protocol (DHCP) is enabled, the IP phone
automatically configures all of the Network settings. If the phone cannot populate
the Network settings, or if DHCP is disabled, you can set the Network options
manually.
Parameter In
IP Phone UI
DHCP
Parameter in
Aastra Web UI
DHCP
Parameters in
Configuration Files
dhcp
Description
Enables or disables DHCP.
Enabling DHCP populates the
required network information. The
DHCP server serves the network
information that the IP phone
requires. If the IP phone is unable to
get any required information, then
you must enter it manually. DHCP
populates the following network
information:
IP Address, Subnet Mask, Gateway,
Broadcast Address, Domain Name
Servers (DNS), TFTP, HTTP
HTTPS, and FTP servers, and
Timer Servers.
Note: For DHCP to automatically
populate the IP address or qualified
domain name for the TFTP server,
your DHCP server must support
Option 66.
For more information, see “DHCP”
on page 4-4.
IP Address
IP Address
ip
IP address of the IP phone. To
assign a static IP address, disable
DHCP.
For more information, see
“Configuring Network Settings
Manually” on page 4-8.
3-32
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Subnet Mask
Parameter in
Aastra Web UI
Subnet Mask
Parameters in
Configuration Files
subnet mask
Description
Subnet mask defines the IP address
range local to the IP phone. To
assign a static subnet mask, disable
DHCP.
For more information, see
“Configuring Network Settings
Manually” on page 4-8.
Gateway
Gateway
default gateway
The IP address of the network’s
gateway or default router IP
address. To assign a static Gateway
IP address, disable DHCP.
For more information, see
“Configuring Network Settings
Manually” on page 4-8.
Primary DNS
Primary DNS
dns1
Primary domain name server IP
address. For any of the IP address
settings on the IP phone a domain
name value can be entered instead
of an IP address. With the help of
the domain name servers the
domain names for such parameters
can then be resolved to their
corresponding IP addresses.
To assign static DNS addresses,
disable DHCP.
Note: If a host name is configured
on the IP phone, you must also set
a DNS.
For more information, see
“Configuring Network Settings
Manually” on page 4-8.
41-001160-00, Release 2.1, Rev 04
3-33
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
Secondary DNS
Parameter in
Aastra Web UI
Secondary DNS
Parameters in
Configuration Files
dns2
Description
A service that translates domain
names into IP addresses. To assign
static DNS addresses, disable
DHCP.
For more information, see
“Configuring Network Settings
Manually” on page 4-8.
LAN Port
LAN Port
ethernet port 0
The send (TX) and receive (RX)
method to use on Ethernet port 0
(LAN Port) to transmit and receive
data over the LAN.
For more information, see Chapter
4, “Configuring LAN and PC Port
Negotiation” on page 4-11.
PC Port
PC Port
ethernet port 1
The send (TX) and receive (RX)
method to use on Ethernet port 1
(PC Port) to transmit and receive
data to your PC.
For more information, see Chapter
4, “Configuring LAN and PC Port
Negotiation” on page 4-11.
3-34
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Advanced Network Settings
UPnP
Parameter in
Aastra Web UI
UPnP
Parameters in
Configuration Files
upnp manager
Description
Enables or disables Universal Plug
and Play (UpnP) on the IP phone. If
you set this parameter to “0”, you
can manually configure NAT on the
IP phone and the UPnP manager
will not start.
For more information, see Chapter
4, “Universal Plug and Play (UPnP)
(for remote phones)” on page 4-27.
N/A
N/A
upnp gateway
IP address or fully qualified Domain
Name of the Internet gateway or
router. This parameter stores the IP
address of the gateway or router in
the event that only non-default
UPnP gateways get discovered on
the network. The UPnP port
mappings are saved to this IP
address so even if the phone
reboots, it will still have the correct
port mappings.
For more information, see Chapter
4, “Universal Plug and Play (UPnP)
(for remote phones)” on page 4-27.
NAT IP
NAT IP
sip nat ip
IP address the network device that
enforces NAT.
For more information, see Chapter
4, “Configuring NAT Address and
Port (optional)” on page 4-21.
NAT SIP Port
NAT SIP Port
sip nat port
Port number of the network device
that enforces NAT.
For more information, see Chapter
4, “Configuring NAT Address and
Port (optional)” on page 4-21.
41-001160-00, Release 2.1, Rev 04
3-35
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
NAT RTP Port
Parameter in
Aastra Web UI
NAT RTP Port
Parameters in
Configuration Files
sip nat rtp port
Description
Indicates the port through which the
RTP packets are sent. This value
must specify the beginning of the
RTP port range on the gateway or
router.
The RTP port is used for sending
DTMF tones and for the audio
stream. Your network administrator
may close some ports for security
reasons. You may want to use this
parameter to send RTP data using a
different port.
For more information, see Chapter
4, “Configuring NAT Address and
Port (optional)” on page 4-21.
Nortel NAT
Nortel NAT Traversal sip nortel nat support
Enabled
Enables or disables the phone to
operate while connected to a
network device that enforces NAT.
For more information, see Chapter
4, “Configuring Nortel NAT
(optional)” on page 4-18.
N/A
Nortel NAT Timer
(seconds)
sip nortel nat timer
The interval, in seconds, that the
phone sends SIP ping requests to
the Nortel proxy.
For more information, see Chapter
4, “Configuring Nortel NAT
(optional)” on page 4-18.
3-36
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
N/A
Parameter in
Aastra Web UI
NTP Time Servers
Parameters in
Configuration Files
time server disabled
Description
Enables or disables the time server.
This parameter affects the time
server1, time server2, and time
server3 parameters. Setting this
parameter to 0 allows the use of the
configured Time Server(s). Setting
this parameter to 1 prevents the use
of the configured Time Server(s).
For more information, see Chapter
4, “Network Time Servers” on
page 4-42.
N/A
Time Servers 1, 2,
and 3
time server1
time server2
time server3
time server4
The 1st, 2nd, 3rd, and 4th time
server's IP address or qualified
domain name. If the time server is
enabled, the value for time server1
will be used to request the time
from.
For more information, see Chapter
4, “Network Time Servers” on
page 4-42.
Client Method
HTTPS Client
Method
https client method
Defines the security method that the
client advertises to the server during
the Secure Socket Layer (SSL)
handshake. Available options are:
TLS 1.0 - Transport Layer Security
version 1 (TLS 1.0) is a protocol that
ensures privacy between
communicating applications and
their users on the Internet. TLS is
the successor to SSL.
SSL 3.0 - Secure Socket Layer
version 3 (SSL 3.0) is a
commonly-used protocol for
managing the security of a message
transmission on the Internet.
For more information, see Chapter
4, “HTTPS Client/Server
Configuration” on page 4-23.
41-001160-00, Release 2.1, Rev 04
3-37
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
HTTPS
Parameter in
Aastra Web UI
HTTPS Server Redirect HTTP to
HTTPS
Parameters in
Configuration Files
https redirect http get
Description
Allows or disallows redirection from
the HTTP server to the HTTPS
server.
For more information, see Chapter
4, “HTTPS Client/Server
Configuration” on page 4-23.
XML HTTP POSTs HTTPS Server Block XML HTTP
POSTs
https block http post xml
Enables or disables the blocking of
XML scripts from HTTP POSTs.
Some client applications use HTTP
POSTs to transfer XML scripts. The
phones’s HTTP server accepts
these POSTs even if server
redirection is enabled, effectively
bypassing the secure connection.
When this parameter is enabled
(blocking is enabled), receipt of an
HTTP POST containing an XML
parameter header results in the
following response:
“403 Forbidden”. This forces the
client to direct the POSTs to the
HTTPS server through use of the
“https://” URL.
For more information, see Chapter
4, “HTTPS Client/Server
Configuration” on page 4-23.
3-38
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Type of Service (ToS), DSCP (53i)
Parameter In
IP Phone UI
Type of Service
SIPt
Parameter in
Aastra Web UI
SIP
Parameters in
Configuration Files
tos sip
Description
The Differentiated Services Code
Point (DSCP) for SIP packets.
For more information, see Chapter
4, “Type of Service (ToS), Quality of
Service (QoS), and DiffServ QoS”
on page 4-31.
Type of Service
RTP
RTP
tos rtp
The Differentiated Services Code
Point (DSCP) for RTP packets.
For more information, see Chapter
4, “Type of Service (ToS), Quality of
Service (QoS), and DiffServ QoS”
on page 4-31.
Type of Service
RTCP
RTCP
tos rtcp
The Differentiated Services Code
Point (DSCP) for RTCP packets.
For more information, see Chapter
4, “Type of Service (ToS), Quality of
Service (QoS), and DiffServ QoS”
on page 4-31.
41-001160-00, Release 2.1, Rev 04
3-39
Administrator Options
Networks settings include Type of Service (ToS) and Differentiated Services Code
Point (DSCP) for the 53i IP phone.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
VLAN
You can enable or disable VLAN and set specific VLAN IDs and priorities under
Network Settings.
Parameter In
IP Phone UI
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Description
Global Settings
VLAN Enable
VLAN Enable
tagging enabled
Enables or disables VLAN on the IP
phones.
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
Other Priority
Priority, Non-IP
Packet
priority non-ip
Specifies the priority value for
non-IP packets.
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
LAN Port Settings (Port 0)
Phone VLAN ID
VLAN ID
VLAN id
VLAN is a feature on the IP phone
that allows for multiple logical
Ethernet interfaces to send
outgoing RTP packets over a single
physical Ethernet as described in
IEEE Std 802.3. On the IP phone,
you configure a VLAN ID that
associates with the physical
Ethernet Port 0.
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
3-40
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
SIP Priority
RTP Priority
RTCP Priority
Parameter in
Aastra Web UI
SIP Priority
RTP Priority
RTCP Priority
Parameters in
Configuration Files
tos priority map
Description
This parameter is based on the
Type of Service (ToS), Differentiated
Services Code Point (DSCP) setting
for SIP (tos sip parameter), RTP
(tos rtp parameter) and RTCP (tos
rtcp parameter). It is the mapping
between the DSCP value and the
VLAN priority value for SIP, RTP,
and RTCP packets.
You enter the tos priority map value
as follows:
(DSCP_1,Priority_1)(DSCP_2,Priori
ty_2).....(DSCP_64,Priority_64)
where the DSCP value range is
0-63 and the priority range is 0-7.
Mappings not enclosed in
parentheses and separated with a
comma, or with values outside the
ranges, are ignored.
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
41-001160-00, Release 2.1, Rev 04
3-41
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Description
PC Port Settings (Port 1)
PC Port VLAN ID
VLAN ID
VLAN id port 1
Specifies the VLAN ID used to pass
packets through to a PC via Port 1.
Note: If you set the PC Port VLAN
ID (Port 1) to 4095, all untagged
packets are sent to this port. The
following is an example of
configuring the phone on a VLAN
where all untagged packets are sent
to the passthrough port.
Example
You enable tagging on the LAN Port
(VLAN id) as normal but set the PC
Port (VLAN id port 1) to 4095. The
following example sets the phone to
be on VLAN 3 on the LAN Port but
the PC Port is configured as
untagged.
tagging enabled: 1
VLAN id: 3
VLAN id port 1: 4095
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
PC Port Priority
Priority
QoS eth port 1 priority
Specifies the priority value used for
passing VLAN packets through to a
PC via Port 1.
For more information, see Chapter
4, “Virtual LAN (optional)” on
page 4-31.
3-42
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
SIP Settings
•
Basic SIP Authentication Settings
•
Basic SIP Network Settings
•
Advanced SIP settings
•
RTP Settings
Note: Specific parameters are configurable on a global and per-line basis.
You can also configure specific parameters using the IP Phone UI, the
Aastra Web UI, or the configuration files. If you have a proxy server or
have a SIP registrar present at a different location than the PBX server,
the SIP parameters may need to be changed.
Basic SIP Authentication Settings
Parameter In
IP Phone UI
Screen Name
Parameter in
Aastra Web UI
Screen Name
Parameters in
Configuration Files
sip screen name
(global)
sip lineN screen name
(per-line)
N/A
Screen Name 2
sip screen name 2
(global)
sip lineN screen name 2
(per-line)
41-001160-00, Release 2.1, Rev 04
Description
Name that displays on the idle
screen. Valid values are up to 20
alphanumeric characters.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Custom text message that displays
on the idle screen. Valid values are
up to 20 alphanumeric characters.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
3-43
Administrator Options
The following paragraphs describe the SIP parameters you can configure on the IP
phone. SIP configuration consists of configuring:
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
User Name
Parameter in
Aastra Web UI
Phone Number
Parameters in
Configuration Files
sip user name
(global)
sip lineN user name
(per-line)
Description
User name used in the name field of
the SIP URI for the IP phone and for
registering the phone at the
registrar. Valid values are up to 20
alphanumeric characters.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Display Name
Caller ID
sip display name
(global)
sip lineN display name
(per-line)
Name used in the display name
field of the "From SIP" header field.
Some IP PBX systems use this as
the caller’s ID, and some may
overwrite this with the string that is
set at the PBX system. Valid values
are up to 20 alphanumeric
characters.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Auth Name
Authentication Name sip auth name
(global)
sip lineN auth name
(per-line)
Authorization name used in the
username field of the Authorization
header field of the SIP REGISTER
request. Valid values are up to 20
alphanumeric characters.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Password
Password
sip password
(global)
sip lineN password
(per-line)
Password used to register the IP
phone with the SIP proxy. Valid
values are up to 20 numeric
characters. Passwords are
encrypted and display as asterisks
when entering.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
3-44
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
N/A
Parameter in
Aastra Web UI
BLA Number
Parameters in
Configuration Files
sip bla number
(global)
sip lineN bla number
(per-line)
Description
Phone number that you assign to
BLA lines that is shared across all
phones (global configuration) or
shared on a per-line basis (per-line
configuration).
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
For more information about BLA,
see Chapter 5, the section, “Bridged
Line Appearance (BLA) (55i, 57i,
57i CT only)” on page 5-144.
N/A
Line Mode
sip mode
(global)
sip lineN mode
(per-line)
The mode-type that you assign to
the IP phone. Valid values are
Generic (0), BroadSoft SCA (1),
Nortel (2), or BLA (3). Default is
Generic (0).
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
41-001160-00, Release 2.1, Rev 04
3-45
Administrator Options
Parameter In
IP Phone UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Basic SIP Network Settings
Parameter In
IP Phone UI
Proxy Server
Proxy Port
N/A
Parameter in
Aastra Web UI
Proxy Server
Proxy Port
Parameters in
Configuration Files
sip proxy ip
(global)
IP address of the SIP proxy server.
Up to 64 alphanumeric characters.
sip lineN proxy ip
(per-line)
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
sip proxy port
(global)
SIP proxy server’s port number.
Default is 0.
sip lineN proxy port
(per-line)
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Backup Proxy Server sip backup proxy server
(global)
sip lineN backup proxy
server
(per-line)
N/A
Backup Proxy Port
sip backup proxy port
(global)
sip lineN backup proxy
port
(per-line)
3-46
Description
The IP address of the backup SIP
proxy server for which the IP phone
uses when the primary SIP proxy is
unavailable.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
The port number of the backup SIP
proxy server for which the IP phone
uses when the primary SIP proxy
port is unavailable.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
N/A
Parameter in
Aastra Web UI
Outbound Proxy
Server
Parameters in
Configuration Files
Description
sip outbound proxy
server
(global)
Address of the outbound proxy
server. All SIP messages originating
from the phone are sent to this
server. For example, if you have a
sip lineN outbound proxy Session Border Controller in your
server
network, then you would normally
(per-line)
set its address here. Default is
0.0.0.0.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
N/A
Outbound Proxy Port sip outbound proxy port
(global)
The proxy port on the proxy server
to which the IP phone sends all SIP
messages. Default is 0.
sip lineN outbound proxy
port
For more information, see Chapter
(per-line)
4, “Basic Network Settings” on
page 4-4.
Registrar Server
Registrar Server
sip registrar ip
(global)
sip lineN registrar ip
(per-line)
IP address of the SIP registrar. Up
to 64 alphanumeric characters.
Enables or disables the phone to be
registered with the Registrar. When
Register is disabled globally, the
phone is still active and you can dial
using username and IP address of
the phone. A message "No Service"
displays on the idle screen and the
LED is steady ON. If Register is
disabled for a single line, no
messages display and LEDs are
OFF.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
Registrar Port
Registrar Port
41-001160-00, Release 2.1, Rev 04
sip registrar port
(global)
SIP registrar’s port number. Default
is 0.
sip lineN registrar port
(per-line)
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
3-47
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
N/A
Parameter in
Aastra Web UI
Backup Registrar
Server
Parameters in
Configuration Files
sip backup registrar ip
(global)
sip lineN backup
registrar ip
(per-line)
Description
The address of the backup registrar
(typically, the backup SIP proxy) for
which the IP phone uses to send
REGISTER requests if the primary
registrar is unavailable.
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
N/A
N/A
N/A
Backup Registrar
Port
Registration Period
Conference Server
URI
sip backup registrar port
(global)
The backup registrar's (typically the
backup SIP proxy) port number.
sip lineN backup
registrar port
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
sip registration period
(global)
The requested registration period,
in seconds, from the registrar.
sip lineN registration
period
(per-line)
For more information, see Chapter
4, “Basic Network Settings” on
page 4-4.
sip centralized conf
(global)
Globally enables or disables SIP
centralized conferencing for an IP
phone.
sip lineN centralized conf
(per-line)
For more information, see Chapter
4, “Centralized Conferencing (for
Sylantro and Broadsoft Servers)” on
page 5-220.
3-48
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Advanced SIP Settings
Parameter in
Aastra Web UI
Explicit MWI Subscription
Parameters in
Configuration Files
sip explicit mwi subscription
Description
If the IP phone has a message waiting
subscription with the Service Provider, a
Message Waiting Indicator (MWI) (LED or
display icon) tells the user there is a message
on the IP Phone. You can enable and disable
MWI by setting this parameter to 0 (disable) or
1 (enable) in the configuration files or by
checking the box for this field in the Aastra
Web UI. Default is disabled.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Explicit MWI Subscription
Period
sip explicit mwi subscription
period
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Missed Call Summary
Subscription
sip missed call summary
subscription
Enables or disables the Missed Call Summary
Subscription feature.
This feature allows missed calls that have
been redirected by the server, to be
incremented in the missed calls indicator on
the phone it was initially directed to. Default is
disabled.
For more information about this parameter,
see Chapter 6, the section, “Missed Call
Summary Subscription” on page 6-13.
41-001160-00, Release 2.1, Rev 04
3-49
Administrator Options
In addition to the basic SIP settings, you can also configure the following
advanced SIP parameters. These parameters are configurable via the Aastra Web
UI and the configuration files on a global basis only.
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Missed Call Summary
Subscription Period
sip missed call summary
subscription period
Description
Specifies the amount of time, in seconds, that
the phone uses the Missed Calls Summary
Subscription feature. This parameter is always
enabled with a default value of 86400
seconds. When the phone reaches the limit
set for this parameter, it sends the
subscription again.
For more information about this parameter,
see Chapter 6, the section, “Missed Call
Summary Subscription” on page 6-13.
Send MAC Address in
REGISTER Message
sip send mac
Adds an "Aastra-Mac:" header to the SIP
REGISTER messages sent from the phone to
the call server, where the value is the MAC
address of the phone.
For more information about this parameter,
see Chapter 6, the section, “MAC Address/
Line Number in REGISTER Messages” on
page 6-5.
Send Line Number in
REGISTER Message
sip send line
Adds an "Aastra-Line:" header to the SIP
REGISTER messages sent from the phone to
the call server, where the value is the line
number that is being registered.
For more information about this parameter,
see Chapter 6, the section, “MAC Address/
Line Number in REGISTER Messages” on
page 6-5.
Session Timer
sip session timer
The time, in seconds, that the IP phone uses
to send periodic re-INVITE requests to keep a
session alive. The proxy uses these re-INVITE
requests to maintain the status' of the
connected sessions. See RFC4028 for details.
Default is 0.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
3-50
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Timer 1 and Timer 2
Parameters in
Configuration Files
sip T1 timer
sip T2 timer
Description
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Transaction Timer
sip transaction timer
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Transport Protocol
sip transport protocol
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Registration Failed Retry
Timer
sip registration retry timer
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
Registration Timeout Retry sip registration timeout retry
Timer
timer
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
41-001160-00, Release 2.1, Rev 04
3-51
Administrator Options
Parameter in
Aastra Web UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter in
Aastra Web UI
Registration Renewal
Timer
Parameters in
Configuration Files
Description
sip registration renewal timer The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
BLF Subscription Period
sip blf subscription period
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
ACD Subscription Period
sip acd subscription period
The requested duration, in seconds, before
the MWI subscription times out. The phone
re-subscribes to MWI before the subscription
period ends.
For more information, see Chapter 4,
“Advanced SIP Settings (optional)” on
page 4-58.
3-52
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Blacklist Duration
Parameters in
Configuration Files
sip blacklist duration
Description
Specifies the length of time, in seconds, that a
failed server remains on the server blacklist.
The IP phone avoids sending a SIP message
to a failed server (if another server is
available) for this amount of time.
For more information about Blacklist Duration,
see Chapter 6, the section, “Blacklist Duration
(Broadsoft Servers)” on page 6-17.
Whitelist Proxy
sip whitelist
This parameter enables/disables the whitelist
proxy feature, as follows:
• Set to 0 to disable the feature.
• Set to 1 to enable the feature. When this
feature is enabled, an IP phone accepts
call requests from a trusted proxy server
only. The IP phone rejects any call
requests from an untrusted proxy server.
For more information about Whitelist Proxy
see Chapter 6, the section, “Whitelist Proxy”
on page 6-19.
41-001160-00, Release 2.1, Rev 04
3-53
Administrator Options
Parameter in
Aastra Web UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
RTP Settings
You can configure the following RTP settings.
Parameter In
IP Phone UI
RTP Port Base
Parameter in
Aastra Web UI
RTP Port
Parameters in
Configuration Files
sip rtp port
Description
The RTP port is used for sending
DTMF tones and for the audio
stream. Your network administrator
may close some ports for security
reasons. You may want to use this
parameter to send RTP data using a
different port. Default is 3000.
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
N/A
Basic Codecs
(G.711 u-Law,
G.711 a-Law, G.729)
sip use basic codecs
Enables or disables basic codecs.
Enabling this parameter allows the
IP phone to use the basic Codecs
when sending/receiving RTP
packets. Valid values are 0
(disabled) and 1 (enabled). Default
is 0 (disabled).
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
N/A
Force RFC2833 Out
of Band DTMF
sip out-of-band dtmf
Enables or disables out-of-band
DTMF. Enabling this parameter
forces the IP phone to use
out-of-band DTMF according to
RFC283. Valid values are 0
(disabled) and 1 (enabled). Default
is 1 (enabled).
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
3-54
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
N/A
Parameter in
Aastra Web UI
Customized Codec
Preference List
Parameters in
Configuration Files
sip customized codec
Description
Specifies a customized Codec
preference list which allows you to
use the preferred Codecs for this IP
phone.
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
N/A
DTMF Method
sip dtmf method
(global)
sip lineN dtmf method
(per-line)
Sets the dual-tone multifrequency
(DTMF) method to use on the IP
phone on a global or per-line basis.
Valid values are 0 (RTP), 1 (SIP
INFO), or 2 (BOTH). Default is 0
(RTP).
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
N/A
RTP Encryption
sip srtp mode
(global)
sip lineN srtp mode
(per-line)
This parameter determines if SRTP
is enabled on this IP phone, as
follows:
•
If set to 0, then disable SRTP.
•
If set to 1 then SRTP calls are
preferred.
•
If set to 2, then SRTP calls only
are generated/accepted.
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
N/A
Silence Suppression sip silence suppression
Silence suppression is enabled by
default on the IP phones. The
phone negotiates whether or not to
use silence suppression. Disabling
this feature forces the phone to
ignore any negotiated value.
For more information, see Chapter
4, “Real-time Transport Protocol
(RTP) Settings” on page 4-64.
41-001160-00, Release 2.1, Rev 04
3-55
Administrator Options
Parameter In
IP Phone UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Line Settings
An administrator can configure multiple lines on the IP phone with the same SIP
network configuration (global) or a different SIP network configuration (per-line).
The following table provides the number of lines available for each IP phone
model.
IP Phone
Model
Available
Lines
53i
9
55i
9
57i
9
57i CT
9
On the IP Phones, you can configure the following on a per-line basis using the
configuration files or the Aastra Web UI:
•
Basic SIP Authentication Settings
•
Basic SIP Network Settings
•
Advanced SIP Settings (Missed Call Summary Subscription only)
•
RTP Settings (DTMF Method and RTP Encryption only)
•
Autodial Settings (You can enable/disable “Use Global Settings” on a
per-line basis only)
References
For more information about configuring the features listed above on a per-line
basis, see Chapter 4, the sections:
3-56
•
“Basic SIP Settings” on page 4-46
•
“Advanced SIP Settings (optional)” on page 4-58
•
“Real-time Transport Protocol (RTP) Settings” on page 4-64
•
“Autodial Settings” on page 4-74
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Softkeys, Programmable Keys, Expansion Module Keys
IP Phone Model
Softkeys
Expansion Module
Keys
Programmable Keys
53i
-
36 to 108*
(Model 536M)
4
55i
6
36 to 108*
(Model 536M)
6
60 to 180**
(Model 560M)
57i
12
36 to 108*
(Model 536M)
-
60 to 180**
(Model 560M)
57i CT
12
36 to 108* on Base
Station
(Model 536M)
-
60 to 180** on Base
Station
(Model 560M)
*The 536M expansion module consists of 36 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 108 softkeys. Valid for 53i, 55i, 57i, and 57i CT phones.
**The 560M expansion module consists of 60 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 180 softkeys. Valid for 55i, 57i, and 57i CT 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/Feature Key/Expansion Module Key Parameters” on
page A-136.
For information about configuring softkeys, programmable keys, and expansion
module keys, see Chapter 5, the section, “Softkeys/Programmable Keys/Feature
Keys/Expansion Module Keys” on page 5-93.
41-001160-00, Release 2.1, Rev 04
3-57
Administrator Options
A user or administrator can assign specific functions to softkeys, programmable
keys, or expansion module keys. The available keys for configuration depend on
the IP phone model as shown in the following table.
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Action URI
3-58
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
IP phone XML events that support this feature are:
•
Startup
•
Successful registration
•
Incoming call
•
Outgoing call
•
Offhook
•
Onhook
You can set these parameters using the configuration files or the Aastra Web UI.
Reference
For more information about setting the Action URIs for XML applications, see
“XML Action URIs” on page 5-209.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Configuration Server Settings
Parameter In
IP Phone UI
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Description
Download Protocol Settings
Download Protocol Download Protocol
download protocol
Protocol to use for downloading
new versions of software to the IP
phone. Valid values are:
TFTP
FTP
HTTP
HTTPS
For DHCP to automatically populate
the IP address or domain name for
the download servers, your DHCP
server must support Option 66. For
more information, see Chapter 4,
the section, “DHCP” on page 4-4.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
Primary TFTP
TFTP Server
tftp server
The TFTP server’s IP address or
qualified domain name. If DHCP is
enabled and the DHCP server
provides the information, this field is
automatically populated. Use this
parameter to change the IP address
or domain name of the TFTP server.
This will become effective after this
configuration file has been
downloaded into the phone.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
41-001160-00, Release 2.1, Rev 04
3-59
Administrator Options
The configuration server stores the firmware images, configuration files, and
software when performing software upgrades to the IP phone. An administrator
can configure the following parameters for the configuration server:
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
Alternate TFTP
Parameter in
Aastra Web UI
Alternate TFTP
Parameters in
Configuration Files
alternate tftp server
Description
The alternate TFTP server’s IP
address or qualified domain name.
This will become effective after this
configuration file has been
downloaded into the phone.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
Select TFTP
Use Alternate TFTP
use alternate tftp
Enables or disables the alternate
TFTP server. Valid values are "0"
disabled and "1" enabled.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
FTP Server
FTP Server
ftp server
The FTP server’s IP address or
network host name. This will
become effective after this
configuration file has been
downloaded into the phone.
Optional: You can also assign a
username and password for access
to the FTP server. See the following
parameters for setting username
and password.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
FTP Username
FTP Username
ftp username
The username to enter for
accessing the FTP server. This will
become effective after this
configuration file has been
downloaded into the phone.
Note: The IP Phones support
usernames containing dots (“.”).
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
3-60
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
FTP Password
Parameter in
Aastra Web UI
FTP Password
Parameters in
Configuration Files
ftp password
Description
The password to enter for
accessing the FTP server. This will
become effective after this
configuration file has been
downloaded into the phone.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
HTTP Server
HTTP Server
http server
The HTTP server’s IP address. This
will become effective after this
configuration file has been
downloaded into the phone.
Optional: You can also assign an
HTTP relative path to the HTTP
server. See the next parameter
(http path).
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
HTTP Path
HTTP Path
http path
The HTTP path name to enter.
If the IP phone’s configuration and
firmware files are located in a
sub-directory beneath the server’s
HTTP root directory, the relative
path to that sub-directory should be
entered in this field.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
41-001160-00, Release 2.1, Rev 04
3-61
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
Download Server
Parameter in
Aastra Web UI
HTTPS Server
Parameters in
Configuration Files
https server
Description
The HTTPS server’s IP address.
This will become effective after this
configuration file has been
downloaded into the phone.
Optional: You can also assign an
HTTPS relative path to the HTTPS
server. See the next parameter
(https path).
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
Download Path
3-62
HTTPS Path
https path
The HTTPS path name to enter.
If the IP phone’s configuration and
firmware files are located in a
sub-directory beneath the server’s
HTTPS root directory, the relative
path to that sub-directory should be
entered in this field.
For more information, see Chapter
4, “Configuration Server Protocol”
on page 4-79.
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Description
Auto-Resync Settings
N/A
Mode
auto resync mode
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.
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.
For more information, see Chapter
8, the section, “Automatic Update
(auto-resync)” on page 8-6.
41-001160-00, Release 2.1, Rev 04
3-63
Administrator Options
Parameter In
IP Phone UI
Administrator Options
IP Phone Administrator Guide
Administrator Level Options
Parameter In
IP Phone UI
N/A
Parameter in
Aastra Web UI
Time (24-hour)
Parameters in
Configuration Files
auto resync time
Description
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).
For more information, see Chapter
8, the section, “Automatic Update
(auto-resync)” on page 8-6.
3-64
41-001160-00, Release 2.1, Rev 04
Administrator Options
Administrator Level Options
Parameter in
Aastra Web UI
Parameters in
Configuration Files
Description
XML Push Server List (Approved IP Addresses)
N/A
XML Push Server
List (Approved IP
Addresses)
xml application post list
The HTTP server that is pushing
XML applications to the IP phone.
For more information, see Chapter
5, the section, “XML Push
Requests” on page 5-203.
41-001160-00, Release 2.1, Rev 04
3-65
Administrator Options
Parameter In
IP Phone UI
IP Phone Administrator Guide
Administrator Level Options
Administrator Options
Firmware Update Features
3-66
The IP phone uses a TFTP, FTP, HTTP, or HTTPS server (depending on the
protocol configured on the IP phone) to download configuration files and
firmware.
You can download the firmware stored on the configuration server in one of three
ways:
•
Manual firmware update using the Aastra Web UI (TFTP only).
•
Manual update of firmware and configuration files (by restarting the phone
via the IP phone UI or the Aastra Web UI).
•
Automatic update of firmware, configuration files, or both at a specific time
in a 24-hour period (via the Aastra Web UI or configuration files)
Reference
For more information about firmware update, see Chapter 8, “Upgrading the
Firmware.”
41-001160-00, Release 2.1, Rev 04
About this chapter
Introduction
This chapter provides the information required to configure the Network and
Global SIP features on the IP Phone. These features are password protected on the
IP Phone UI and the Aastra Web UI. This chapter also includes procedures for
configuring the Network and Global SIP features via the configuration files, the
IP Phone UI, and the Aastra Web UI where applicable.
Note: The IP Phone User Interface (UI) procedures in the remainder of
this Guide use the keys on the 55i, 57i, and/or 57i CT when configuring
Administrator Options. For information on using the 53i keys to
configure the Administrator Options, see Chapter 2, the section, “Using
the Options Key” on page 2-4.
Topics
This chapter covers the following topics:
Topic
Page
Overview
page 4-3
Network Settings
page 4-4
Basic Network Settings
page 4-4
Advanced Network Settings
page 4-16
41-001160-00, Release 2.1, Rev 04
4-1
Configuring the IP Phones
Chapter 4
Configuring Network and
Session Initiation Protocol (SIP)
Features
Configuring the IP Phones
IP Phone Administrator Guide
About this chapter
4-2
Topic
Page
Global SIP Settings
page 4-45
Basic SIP Settings
page 4-46
Advanced SIP Settings (optional)
page 4-58
Real-time Transport Protocol (RTP) Settings
page 4-64
Autodial Settings
page 4-74
Configuration Server Protocol
Configuring the Configuration Server Protocol
page 4-79
page 4-79
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Overview
Overview
Note: An administrator has the option of enabling and disabling the use
of password protection in the IP phone UI. This is configurable using the
configuration files only. For more information about this feature, see
Appendix A, the section “Password Settings” on page A-9.
The procedures in this section include configuring from the IP phone UI and the
Aastra Web UI. To configure the IP phones using the configuration files, see
Appendix A, “Configuration Parameters.”
To configure the phone using the IP phone UI, you must enter an administrator
password. To configure the phone using the Aastra Web UI, you must enter an
administrator username and password.
Note: In the IP phone UI, the default password is "22222". In the
Aastra Web UI, the default admin username is "Admin" and the default
password is "22222".
References
For configuring the IP phone at the Asterisk IP PBX, see Appendix C,
“Configuring the IP Phone at the Asterisk IP PBX.”
For sample configuration files, see Appendix D, “Sample Configuration Files.”
These sample files include basic parameters required to register the IP phone at
the PBX.
41-001160-00, Release 2.1, Rev 04
4-3
Configuring the IP Phones
An administrator can configure the IP Phone Network and SIP options from the
phone UI, from the Aastra Web UI, or the configuration files. Administrator level
options are password protected in both the IP phone UI and the Aastra Web UI.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
Network Settings
This section describes the basic network settings on the IP phone which include
configuring for:
•
DHCP
•
IP Address (of phone)
•
Subnet Mask (of phone)
•
Gateway
•
Primary DNS
•
Secondary DNS
•
LAN Port
•
PC Port
Basic Network Settings
4-4
DHCP
The IP phone is capable of querying a DHCP server, allowing a network
administrator a centralized and automated method of configuring various network
parameters for the phone. If DHCP is enabled, the IP phone requests the following
network information:
•
Subnet Mask
•
Gateway (i.e. router)
•
Domain Name Server (DNS)
•
Broadcast Address
•
Network Time Protocol Server
•
IP Address
•
TFTP Server
•
FTP Server
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
HTTP Server
•
HTTPS Server
Note: The IP Phones support download protocols according to RFC2131
and RFC1541 (TFTP, FTP, HTTP,. HTTPS) to support DHCP option 66.
Option 66 is part of the DHCP Offer message that the DHCP server
generates to tell the phone which configuration server it should use to
download new firmware and configuration files.
For DHCP to automatically populate the IP address or domain name for
the servers, your DHCP server must support Option 66. Option 66 is
responsible for forwarding the server’s IP address or domain name to the
phone automatically. If your DHCP server does not support Option 66,
you must manually enter the IP address or domain name for the TFTP
server into your IP phone configuration.
The network administrator chooses which of these parameters (if any) are
supplied to the IP phone by the DHCP server. The administrator must configure
the phone manually to provide any required network parameters not supplied by
the DHCP server.
Your DHCP server configuration file, such as the dhcpd.conf file, may include one
of these lines to configure the configuration server protocol and the server details.
Protocol
Format
Examples
HTTP
http://<server>/<path>
option tftp-server-name “http://192.168.1.45”;
option tftp-server-name “http://192.168.1.45/path”;
option tftp-server-name “http://httpsvr.example.com/path”;
HTTPS
https://<server>/<path>
option tftp-server-name “https://192.168.1.45”;
option tftp-server-name “https://192.168.1.45/path”;
option tftp-server-name “https://httpssvr.example.com/
path”;
41-001160-00, Release 2.1, Rev 04
4-5
Configuring the IP Phones
•
Configuring the IP Phones
IP Phone Administrator Guide
Network Settings
Protocol
Format
Examples
FTP
ftp://user:password@ftpserver
option tftp-server-name “ftp://192.168.1.45”;
option tftp-server-name “ftp://ftpsvr.example.com”;
(for anonymous user)
option tftp-server-name “ftp://userID:password@
ftpsvr.example.com”;
TFTP
tftp://tftpserver
option tftp-server-name “192.168.1.45”;
option tftp-server-name “tftpsvr.example.com”;
option tftp-server-name “tftp://tftpsvr.example.com”;
DNS Caching
The IP phones have the ability to cache DNS requests according to RFC1035 and
RFC2181. The phone caches DNS lookups according to the TTL field, so that the
phone only performs another lookup for an address when the TTL expires.
Configuring DHCP
You can enable and disable DHCP using the configuration files, the IP phone UI,
or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Network
Settings” on page A-6.
4-6
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring the IP Phones
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select option DHCP.
6
Press Change to set "Use DHCP?" to "Yes" (enable) or "No" (disable).
7
Press Done to save the changes.
on the phone to enter the Options List.
41-001160-00, Release 2.1, Rev 04
4-7
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Basic Network Settings.
2
Enable the "DHCP" field by checking the check box. (Disable this field by unchecking the box).
3
Click
to save your settings.
Configuring Network Settings Manually
If you disable DHCP on your phone, you need to configure the following network
settings manually:
4-8
•
IP Address
•
Subnet Mask
•
Gateway
•
Primary DNS
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
•
Secondary DNS
You can configure the network settings using the configuration files, the IP phone
UI, or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Network
Settings” on page A-6.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select IP Address and enter the IP address of the phone.
6
Select Subnet Mask and enter the subnet mask.
7
Select Gateway and enter the gateway address.
8
Select DNS and enter a Primary and/or Secondary DNS server.
9
Press Done to save the changes.
on the phone to enter the Options List.
The IP phone is manually configured.
41-001160-00, Release 2.1, Rev 04
4-9
Configuring the IP Phones
Note: If you disable DHCP on the phone, the phone uses the TFTP
protocol as the default server protocol. If you want to specify a different
protocol to use, see “Configuration Server Protocol” on page 4-79.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Basic Network Settings.
2
Enter an IP address of the phone in the IP Address field.
3
Enter a subnet mask in the Subnet Mask field.
4
Enter a gateway address in the Gateway field.
5
Enter a Primary DNS in the Primary DNS field, and/or a secondary DNS in the Secondary DNS
field.
6
Click
to save your settings.
The IP phone is manually configured.
4-10
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring LAN and PC Port Negotiation
There are two Ethernet ports on the rear of the IP phones: LAN Port and PC Port.
Using the Aastra Web UI, you can select the type of transmission you want these
ports to use to communicate over the LAN. The IP phones support each of the
following methods of transmission:
•
Auto-negotiation
•
Half-duplex (10Mbps or 100 Mbps)
•
Full-duplex (10Mbps or 100Mbps)
Auto-negotiation
Auto-negotiation is when two connected devices choose common transmission
parameters. In the auto-negotiation process, the connected devices share their
speed and duplex capabilities and connect at the highest common denominator
(HCD). Auto-negotiation can be used by devices that are capable of different
transmission rates (such as 10Mbit/sec and 100Mbit/sec), different duplex modes
(half duplex and full duplex) and/or different standards at the same speed. You can
set the LAN and PC Ports on the IP phones to auto-negotiate during transmission.
Half-Duplex (10Mbps or 100Mbps)
Half-duplex data transmission means that data can be transmitted in both
directions on a signal carrier, but not at the same time. For example, on a LAN
using a technology that has half-duplex transmission, one device can send data on
the line and then immediately receive data on the line from the same direction in
which data was just transmitted. Half-duplex transmission implies a bidirectional
line (one that can carry data in both directions). On the IP phones, you can set the
half-duplex transmission to transmit in 10Mbps or in 100Mbps.
41-001160-00, Release 2.1, Rev 04
4-11
Configuring the IP Phones
Ethernet is the computer networking technology for local area networks (LANs).
You use the LAN Port to connect to a LAN using a twisted pair 10BASE-T cable
to transmit 10BASE-T Ethernet. You use the PC Port to connect to the
configuration server (your PC).
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
Full-Duplex (10Mbps or 100Mbps)
Full-duplex data transmission means that data can be transmitted in both
directions on a signal carrier at the same time. For example, on a LAN with a
technology that has full-duplex transmission, one device can be sending data on
the line while another device is receiving data. Full-duplex transmission implies a
bidirectional line (one that can move data in both directions). On the IP phones,
you can set the full-duplex transmission to transmit in 10Mbps or in 100Mbps.
Configuring the LAN Port and PC Port
You can configure the Ethernet port transmission method to use on the IP phones
using the configuration files, the IP Phone UI, or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Network
Settings” on page A-6.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select Ethernet.
6
Select LAN Port Link.
4-12
on the phone to enter the Options List.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
7
Select a negotiation method to use on port 0 and press Done. Valid values are:
• AutoNegotiation
• FullDuplex 10Mbps
• FullDuplex 100Mbps
• HalfDuplex 10Mbps
• HalfDuplex 100Mbps
Configuring the IP Phones
IP Phone UI
Default is AutoNegotiation.
8
Select PC Port Link.
9
Select a negotiation method to use on port 1and press Done. Valid values are:
• AutoNegotiation
• FullDuplex 10Mbps
• FullDuplex 100Mbps
• HalfDuplex 10Mbps
• HalfDuplex 100Mbps
Default is AutoNegotiation.
10
Press Done (3 times) to finish configuring the configuration server protocol for the IP phone.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
11
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-13
Configuring the IP Phones
IP Phone Administrator Guide
Network Settings
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Basic Network Settings.
2
In the “LAN Port” field, select a negotiation method to use on port 0. Valid values are:
• Auto Negotiation
• Full Duplex, 10Mbps
• Full Duplex, 100Mbps
• Half Duplex, 10Mbps
• Half Duplex, 100Mbps
Default is Auto Negotiation.
4-14
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
3
In the “PC Port” field, select a negotiation method to use on port 1. Valid values are:
• Auto Negotiation
• Full Duplex, 10Mbps
• Full Duplex, 100Mbps
• Half Duplex, 10Mbps
• Half Duplex, 100Mbps
Configuring the IP Phones
Aastra Web UI
Default is Auto Negotiation.
4
Click
to save your settings.
41-001160-00, Release 2.1, Rev 04
4-15
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
Advanced Network Settings
4-16
You can set advanced network settings on the IP phone such as, Network Address
Translation (NAT), Nortel NAT, Network Time Protocol (NTP) Time Servers,
Virtual LAN (VLAN), and Quality of Service (QoS), and Universal Plug and Play
(UPnP) using the Aastra Web UI or the configuration files.
Note: The available advanced network parameters via the IP phone UI
are NAT, Nortel NAT, UPnP, VLAN, and QoS only.
Network Address Translation (NAT)
The protocols used by all IP phones do not interoperate completely with Network
Address Translation (NAT). For the IP Phones, specific configuration parameters
allow the phone to operate while connected to a network device that enforces
NAT. The following is a sample network using a NAT proxy and relevant IP
phone configuration parameters.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Nortel Proxy/Registrar
Note: This IP phone uses RTP port 3000 (the default value) since an RTP
port was not explicitly configured.
SBC or ALG proxy/registrar
The phone at IP address 10.10.10.20 is configured to register with the proxy at
63.251.195.20. Because the proxy/registrar has session border control (SBC) or
application layer gateway (ALG) functionality, no additional IP phone
configuration is required.
Other proxy/registrars
The phone at IP address 10.10.10.30 is configured to register with the proxy at
63.251.195.30. Because this proxy/registrar is not a Nortel proxy and has no SBC
or ALG functionality, the configuration must additionally include the "sip nat ip"
and "sip nat port" settings that contain the public ip address of the NAT router and
the port used for call signaling messages. This information is embedded in
protocol messages to allow the proxy/registrar to reach the IP phone on the NAT
router private network.
NAT router configuration
You must configure the NAT router to allow signaling or media packets
containing the various UDP port values to flow between the private and public
networks that are separated by the NAT router. In the sample network, the NAT
router must not filter packets using ports 3000, 5060, 6060, 16420, and 16430.
41-001160-00, Release 2.1, Rev 04
4-17
Configuring the IP Phones
The phone at IP address 10.10.10.10 is configured to register with the proxy at
63.251.195.10. Because it is a Nortel proxy, the configuration must additionally
include the "sip nortel nat support" and "sip nortel nat timer" settings, telling the
firmware to enhance the protocols with Nortel specific content.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
Nortel Networks NAT
Nortel Networks provides a proprietary solution to support connectivity to their
proxies from phones placed behind devices (such as routers or firewalls) that use
NAT. Nortel uses the SIP ping request/reply between the Nortel proxy and the
phone in order to keep the connection through the router or firewall active. A SIP
Nortel NAT timer is the interval, in seconds (default is 60), that the phone sends
SIP ping requests to the Nortel proxy.
When you use NAT in your network, a network device (usually a router) provides
a “firewall” division between the public network (usually the Internet) and the
private network, to which the IP Phones are connected. The firewall protects the
network by translating port numbers within packets between the public and
private networks. When using NAT, and an RTP packet arrives at the public side
of the firewall, it is expected to have the NAT RTP port within the packet. If the
packet contains the proper port number, the firewall changes the NAT RTP port
number in the packet to the RTP port number that the phone recognizes, and then
forwards it onto the private network. Often the router/firewall automatically
discovers these various port numbers and other information concerning public and
private sides of the network with the use of the Universal Plug and Play (UPnP)
Protocol between the phone and the router/firewall.
Configuring Nortel NAT (optional)
You can configure Nortel NAT using the configuration files, the IP phone UI, or
the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Network
Address Translation (NAT) Settings” on page A-20.
4-18
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring the IP Phones
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select NAT Settings.
6
Select Nortel NAT.
7
Press Change to set either “Enabled” or “Disabled”.
8
Press Done (3 times) to finish.
on the phone to enter the Options List.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
9
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-19
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Advanced Network Settings.
2
Select Yes (enable) or No (disable) in the "Nortel NAT Traversal Enabled" field to enable or disable
NAT for a Nortel network.
3
Enter a time, in seconds, in the "Nortel NAT timer" field. Valid values are 0 to 2147483647.
Default is 60.
4
Click
4-20
to save your settings.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring NAT Address and Port (optional)
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Network
Address Translation (NAT) Settings” on page A-20.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select Static NAT.
6
Select NAT IP.
7
Enter a public IP address of your NAT device in dotted-decimal format.
8
Press Done to save the setting.
9
Select NAT SIP Port. Default is 51620.
10
Enter the public SIP signalling port number of your NAT device.
11
Press Done to save the setting.
12
Select NAT RTP Port.
13
Enter the RTP Port number of your NAT device. Default is 51720.
14
Press Done (4 times) to finish.
on the phone to enter the Options List.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
15
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-21
Configuring the IP Phones
You can also configure a specific NAT address and port on the IP phone using the
configuration files, IP Phone UI, or Aastra Web UI.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Advanced Network Settings.
2
Enter a NAT IP address in the "NAT IP" field. The value must be entered in dotted decimal format.
For example, 0.0.0.0. The “NAT IP” is the public IP address of your NAT device.
3
Enter a NAT port in the "NAT SIP Port" field. Default is 51620.
The “NAT SIP Port” is the public SIP signalling port number of your NAT device.
4
Enter a NAT port in the "NAT RTP Port" field. Default is 51720.
The “NAT RTP Port” is the RTP Port number of your NAT device.
5
Click
4-22
to save your settings.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
HTTPS Client/Server Configuration
Note: HTTPS uses port 443 instead of HTTP port 80 in its interactions
with the TCP/IP lower layer.
When an HTTPS client opens and closes its TCP socket, the SSL software
respectively handshakes upon opening and disconnects upon closing from the
HTTPS server. The main HTTPS client functions are:
•
Downloading of configuration files and firmware images.
•
Downloading of script files based on an “HTTPS://” URL supplied by a
softkey definition.
41-001160-00, Release 2.1, Rev 04
4-23
Configuring the IP Phones
HTTPS is a Web protocol that encrypts and decrypts user page requests as well as
the pages that are returned by the Web server. HTTPS uses Secure Socket Layer
(SSL) or Transport Layer Security (TLS) as a sublayer under its regular HTTP
application layering. SSL is a commonly-used protocol for managing the
security of a message transmission on the Internet. It uses a 40-bit key size
for the RC4 stream encryption algorithm, which is considered an adequate degree
of encryption for commercial exchange. TLS is a protocol that ensures privacy
between communicating applications and their users on the Internet. When a
server and client communicate, TLS ensures that no third party may eavesdrop or
tamper with any message. TLS is the successor to SSL.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
The HTTPS server provides HTTP functionality over secure connections. It
coexists with the HTTP server but has its own set of tasks. The main HTTPS
server functions are:
•
Delivery of web page content to a browser client over a secure connection.
•
Execution of HTTP GET and POST requests received over a secure
connection.
Using the configuration files, the IP phone UI, or the Aastra Web UI, you can
configure the following regarding HTTPS:
•
Specify HTTPS security client method to use (TSLv1 or SSLv3)
•
Enable or disable HTTP to HTTPS server redirect function
•
HTTPS server blocking of XML HTTP POSTS to the phone
Configuring HTTPS Client and Server Settings
Use the following procedures to configure the HTTPS client and server for
the IP phones.
Note: To enable or disable the IP phones to use the HTTPS protocol as
the configuration server, see the section, “Configuring the Configuration
Server Protocol” on page 4-79.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “HTTPS Client
and Server Settings” on page A-23.
4-24
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring the IP Phones
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Configuration Server.
5
Select HTTPS Settings.
on the phone to enter the Options List.
Configure HTTPS Client
6
Select HTTPS Client.
7
Select Client Method.
8
Press Change to select a client method to use for HTTPS. Valid values are:
•
•
9
SSL 3.0 (default)
TLS 1.0
Press Done to save the changes.
Configure HTTPS Server
10
Select HTTPS Server.
11
Select HTTP->HTTPS.
12
Press Change to select “Yes” or “No”. Default is “No”.
Enabling this feature redirects the HTTP protocol to HTTPS.
13
Press Done to save the changes.
14
Select XML HTTP POSTs.
15
Press Change to select “Yes” or “No”. Default is “No”.
Enabling this feature blocks XML HTTP POSTs from the IP Phone.
16
Press Done (4 times) to finish.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
17
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-25
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Advanced Network Settings.
2
Select an HTTPS client method to use from the HTTPS Client Method field. Valid values are:
SSL 3.0 (default)
TSL 1.0
3
Enable HTTP to HTTPS redirect by checking the HTTPS Server - Redirect HTTP to HTTPS field
check box. (Disable this field by unchecking the check box). Default is disabled.
4
Enable the blocking of XML HTTP POSTs by the HTTPS server by checking the HTTPS Server Block XML HTTP POSTs field check box. (Disable this field by unchecking the check box). Default is
disabled.
5
Click
4-26
to save your settings.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Universal Plug and Play (UPnP) (for remote phones)
This method of device discovery on a network is called “Universal Plug and Play”
or UPnP. If you enable UPnP, and the phone is discovered on the network, port
mappings are set up between the phone and the Internet Gateway Device (IGD).
The phone controls the opening, closing, and polling of ports on the IGD. HTTP
and SIP use a single port each. RTP/RTCP uses a range of ports.
The UPnP manager performs its functions when you set the phone to remote
mode. When you switch the phone back to local mode, the UPnP manager
removes any open port mappings and shuts itself down. If you boot the phone in
remote mode, the UPnP manager initializes after the phone obtains an IP address
and before a SIP registration is sent out. If you want to manually configure your
NAT, you must disable UPnP on the remote mode phone.
Note: Enabling UPnP allows the IP phones to access the Internet even if
a firewall has been set on the IGD. This allows the phone to send and
receive SIP calls and XML pushes without interruption. UPnP does not
work with multiple firewalls.
41-001160-00, Release 2.1, Rev 04
4-27
Configuring the IP Phones
UPnP is a standard that uses Internet protocols to enable devices to be plugged
into a network and automatically know about each other. With UPnP, when a user
plugs a device into the network, the device configures itself, acquires a TCP IP
address, and uses a discovery protocol based on the Internet's HTTP or HTTPS
URL to announce its presence on the network to other devices.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
You can enable UPnP on remote IP phones using the configuration files, the IP
Phone UI, or the Aastra Web UI. Using the configuration files, you can enable
UPnP using the following parameters:
•
upnp manager
•
upnp gateway
•
sip nat rtp port
The “upnp manager” parameter enables or disables UPnP. The “upnp gateway”
parameter is the IP address or qualified domain name of the Internet gateway or
router that stores the port mappings. In the event a phone using UPnP is rebooted,
it will still have the previously set port mappings on the gateway. The “sip nat rtp
port” parameter specifies the RTP port range on the gateway.
A User or Administrator can specify UPnP on specific lines using the
configuration files (using the “upnp mapping lines” parameter) or the Aastra
Web UI (at the path Basic Settings->Preferences->UPnP Mapping Lines).
Reference
For more information about enabling/disabling UPnP Mapping on specific lines,
see Chapter 5, the section, “UPnP Mapping Lines (for remote phones)” on
page 5-56.
Configuring UPnP (optional)
Use the following procedures to configure UPnP on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “UPnP Settings”
on page A-25.
4-28
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring the IP Phones
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select NAT Settings.
6
Select UPnP.
7
Press Change to select “Yes” or “No”. Default is “No”.
This field enables or disables the use of UPnP on the IP Phone.
8
Press Done (3 times) to save the changes.
on the phone to enter the Options List.
Note: The session prompts you to restart the IP phone to apply the configuration settings
9
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-29
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Advanced Network Settings.
2
The “UPnP” field is disabled by default. To enable UPnP, place a check in the “Enabled” box.
Uncheck the box to disable this field. This field enables and disable UPnP on the IP phone.
3
Click
4-30
to save your settings.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Virtual LAN (optional)
By configuring specific VLAN parameters, the IP phones have the capability of
adding and removing tags, and processing the ID and priority information
contained within the tag.
Note: All latest VLAN functionality is backwards compatible with IP
Phone Releases 1.3 and 1.3.1.
VLAN on the IP phones is disabled by default. When you enable VLAN, the IP
phone provides defaults for all VLAN parameters. If you choose to change these
parameters, you can configure them using the configuration files, the IP Phone UI,
or the Aastra Web UI.
The following sections describe the VLAN features you can configure on the IP
phones.
Type of Service (ToS), Quality of Service (QoS), and DiffServ QoS
ToS is an octet as a field in the standard IP header. It is used to classify the traffic
of the different 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.
Port 0 is the Ethernet LAN Port connected to the network. Port 1 is the Ethernet
PC Port used for passthrough to a PC.
Differentiated Service (DiffServ) QoS is class-based where some classes of traffic
receive preferential handling over other traffic classes.
The Differentiated Services Code Point (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.
41-001160-00, Release 2.1, Rev 04
4-31
Configuring the IP Phones
Virtual Local Area Network (VLAN) is a feature on the IP phone that allows for
multiple logical Ethernet interfaces to send outgoing RTP packets over a single
physical Ethernet as described in IEEE Std 802.3. On the IP phone, you configure
a VLAN ID that associates with the physical Ethernet port.
Configuring the IP Phones
IP Phone Administrator Guide
Network Settings
The following parameters allow an administrator to configure ToS, QoS, and
DiffServ QoS for VLAN:
Parameters in Configuration Files
Parameters in Aastra Web UI
Global
tagging enabled
VLAN enable
priority non-ip
Priority, Non-IP Packet
LAN Port
vlan id
VLAN ID
tos priority map
SIP Priority
tos priority map
RTP Priority
tos priority map
RTCP Priority
PC Port
vlan id port 1
VLAN ID
QoS eth port 1 priority
Priority
Notes:
1. In order for the software to successfully maintain connectivity with a
network using VLAN functionality, the IP phone reboots if you modify
the "tagging enabled" (VLAN Enable in the Web UI), "vlan id", or
"vlan id port 1" parameters.
2. When the LAN Port (vlan id) and the PC Port (vlan id port 1)
parameters have the same value, VLAN functionality is compatible with
earlier IP phone software releases.
If you set the PC Port (vlan id port 1) to 4095, all untagged packets are
sent to this port. For configuring this feature via the Phone UI and the
Aastra Web UI, see “Configuring VLAN (optional)” on page 4-37. For
configuring this feature using the configuration files, see Appendix A, the
section, “Virtual Local Area Network (VLAN) Settings” on page A-26.
4-32
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
DSCP Range/VLAN Priority Mapping
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 using the "priority non-ip" parameter.
Since the default DSCP settings for SIP, RTP, and RTCP are 24, 32, and 32
respectively, this results in corresponding default VLAN priorities of 3 for SIP, 4
for RTP, and 4 for RTCP (based on the settings in the table “DSCP Range/VLAN
Priority” on page 4-33).
You can change the default parameters by modifying just the DSCP values, just
the VLAN priority values, or by modifying all values.
The following table shows the DSCP range/VLAN priority mapping.
DSCP Range/VLAN Priority
41-001160-00, Release 2.1, Rev 04
DSCP
Range
VLAN Priority
0-7
0
8-15
1
16-23
2
24-31
3
32-39
4
40-47
5
48-55
6
56-63
7
4-33
Configuring the IP Phones
DSCP bits in the ToS field of the IP header are set for RTP, RTCP, and SIP packets
using either the default values or the values configured via the "tos sip", "tos rtp",
and "tos rtcp" parameters.
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
The following table identifies the default DSCP of protocols.
Protocol
Name
Default DSCP
Values in the
ToS Field
rtp
32
rtcp
32
sip
24
Configuring Type of Service (ToS)/DSCP (optional)
Use the following procedures to configure ToS/DSCP on the IP phone.
Note: ToS/DSCP is enabled by default. The SIP, RTP, and RTCP
parameters show defaults of 24, 32, and 32, respectively. Use the
following procedures to change these settings if required.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Type of Service
(ToS)/DSCP Settings” on page A-30.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select Type of Service DSCP.
4-34
on the phone to enter the Options List.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
6
Select Type of Service SIP.
or
Select Type of Service RTP.
or
Select Type of Service RTCP.
7
Enter a value for “Type of Service SIP”. Default is 26.
or
Enter a value for “Type of Service RTP”. Default is 46.
or
Enter a value for “Type of Service RTCP”. Default is 46.
Valid values are 0 to 63.
Note: If you change the ToS/DSCP setting for a Protocol, and VLAN is enabled, you will need to map
the applicable priority to the Protocol setting as shown in the table “DSCP Range/VLAN Priority” on
page 4-33 For more information, see the section “Configuring VLAN (optional)” on page 4-37.
8
Press Done (3 times) to save the changes.
Note: The session prompts you to restart the IP phone to apply the configuration settings
9
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-35
Configuring the IP Phones
IP Phone UI
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Type of Service,DSCP.
2
Select a Protocol field:
• “SIP”
or
• “RTP”
or
• “RTCP”
3
Enter a value from 0 to 63. Default values are as follows:
SIP = 26
RTP = 46
RTCP = 46
Note: If you change the ToS/DSCP setting for a Protocol, and VLAN is enabled, you will need to map
the applicable priority to the Protocol setting as shown in the table “DSCP Range/VLAN Priority” on
page 4-37 For more information, see the section “Configuring VLAN (optional)” on page 4-37.
4
4-36
Click
to save your settings.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Configuring VLAN (optional)
Note: VLAN is disabled by default. When you enable VLAN, the IP
phones use the default settings for each VLAN parameter. You can
change the default settings if required using the following procedure.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Virtual Local
Area Network (VLAN) Settings” on page A-26.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Network Settings.
5
Select VLAN Settings.
on the phone to enter the Options List.
To globally enable/disable VLAN and set priority for non-IP packets:
6
Select VLAN Enable.
7
Press Change to set VLAN Enable to “Yes” to enable or “No” to disable. Default is “No”.
8
Press Done to save the changes.
9
Select Phone VLAN.
10
Select VLAN Priority.
11
Select Other and enter a non-IP priority value from 0 to 7 for non-IP packets.
Default for this field is 5.
12
Press Done (3 times) to return to the VLAN Settings menu.
41-001160-00, Release 2.1, Rev 04
4-37
Configuring the IP Phones
Use the following procedures to configure VLAN on the IP phone.
Configuring the IP Phones
IP Phone Administrator Guide
Network Settings
IP Phone UI
Step
Action
To set VLAN ID and priority for LAN Port (Port 0):
13
Select Phone VLAN.
14
Select Phone VLAN ID and enter a value from 1 to 4094 to specify the VLAN ID for the LAN Port.
Default is 1.
15
Press Done to save the change.
16
Select VLAN Priority.
17
Select one of the following VLAN Protocols:
•
•
•
18
SIP Priority
RTP Priority
RTCP Priority
Enter a VLAN priority value from 0 to 7 for the associated Protocol. Default values for each Protocol
are:
SIP Priority = 3
RTP Priority = 5
RTCP Priority = 5
19
Press Done (3 times) to return to the VLAN Settings menu.
To set VLAN ID and priority for PC Port (Port 1):
20
Select PC Port VLAN.
21
Select PC Port VLAN ID.
22
Enter a value from 1 to 4095 to specify the VLAN ID for the PC Port.
Default is 1.
Note: If you set the PC Port VLAN ID (Port 1) to 4095, all untagged packets are sent to this port. The
following is an example of configuring the phone on a VLAN where all untagged packets are sent to
the PC Port (passthrough port).
Example
You enable tagging on the phone port as normal but set the passthrough port (PC Port) to
4095. The following example sets the phone to be on VLAN 3 but the passthrough port is
configured as untagged.
VLAN Settings->VLAN Enable: Yes
VLAN Settings->Phone VLAN->Phone VLAN ID: 3
VLAN Settings->PC Port VLAN->PC Port VLAN ID: 4095
4-38
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
23
Press Done to save the change.
24
Select PC Port Priority.
25
Select a PC Port VLAN priority value from 0 to 7 for the PC Port.
Default is 0..
26
Press Done (4 times) to save the changes.
Configuring the IP Phones
IP Phone UI
Note: The session prompts you to restart the IP phone to apply the configuration settings
27
Select Restart.
41-001160-00, Release 2.1, Rev 04
4-39
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->VLAN.
To globally enable/disable VLAN and set priority for non-IP packets:
2
Enable VLAN by checking the VLAN Enable field check box. (Disable this field by unchecking the
check box).
3
With VLAN enabled, select the priority (0 to 7) for non-IP packets in the Priority, Non-IP Packet field.
To set VLAN ID and priority for the LAN Port (Port 0):
4
Enter a VLAN ID value from 1 to 4094 in the VLAN ID field. Default is 1.
5
Choose a VLAN Protocol (SIP Priority, RTP Priority, and/or RTCP Priority), and select a priority for
the associated Protocol. Valid values are 0 to 7, Defaults are as follows:
SIP Priority = 3
RTP Priority = 5
RTCP Priority = 5
4-40
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
To set VLAN ID and priority for the PC Port (Port 1):
6
Enter a VLAN ID value from 1 to 4095 in the VLAN ID field. Default is 0.
Note: If you set the PC Port VLAN ID (Port 1) to 4095, all untagged packets are sent to this PC Port.
The following is an example of configuring the phone on a VLAN where all untagged packets are sent
to the passthrough port.
Example
You enable tagging as normal, enter a value for the LAN Port VLAN ID, and then set the PC
Port VLAN ID to 4095. The following example sets the phone to be on VLAN 3 but the PC Port
VLAN ID is configured as untagged..
7
Select a VLAN priority value from 0 to 7 for the PC Port in the Priority field. Default is 0.
8
Click
to save your settings.
41-001160-00, Release 2.1, Rev 04
4-41
Configuring the IP Phones
Aastra Web UI
IP Phone Administrator Guide
Network Settings
Configuring the IP Phones
Network Time Servers
Network Time Protocol (NTP) is a protocol that the IP phone uses to synchronize
the phone clock time with a computer (configuration server) in the network.
To use NTP, you must enable it using the configuration files or the Aastra Web UI.
You can specify up to three time servers in your network.
Note: The IP phones support NTP version 1.
Configuring NTP Servers (optional)
Use the following procedure to enable/disable and configure the NTP servers
using the configuration files.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Time Server
Settings” on page A-31.
Use the following procedure to enable/disable the NTP server using the IP Phone
UI.
IP Phone UI
Step
Action
1
Press
2
Select Preferences.
3
Select Time and Date.
4
Select Time Server.
5
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
6
Select Timer Server 1, Timer Server 2, or Time Server 3.
on the phone to enter the Options List.
Note: The Time Servers are disabled by default.
7
4-42
To set a Time Server, press Enable. (Press Disable to disable a Time Server.)
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Network Settings
Step
Action
8
Enter the IP Address (in dotted decimal) or qualified domain name for the Time Server.
9
Press Done to save the change.
Configuring the IP Phones
IP Phone UI
Use the following procedure to enable/disable and configure the NTP Servers
using the Aastra Web UI.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Network->Advanced Network Settings.
2
Enable the "NTP Time Servers" field by checking the check box.
(Disable this field by unchecking the box). Default is disabled.
41-001160-00, Release 2.1, Rev 04
4-43
Configuring the IP Phones
IP Phone Administrator Guide
Network Settings
Aastra Web UI
Step
Action
3
Enter an IP address or qualified domain name in the "Time Server 1", "Time Server 2", and/or
"Time Server 3" field(s) to specify the location of the NTP time server.
4
Click
4-44
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Global SIP Settings
The IP phone uses the information in the Global Session Initiation Protocol (SIP)
settings to register at the IP PBX.
The IP phone configuration defines network and user account parameters that
apply globally to all SIP lines. Since not all SIP lines are necessarily hosted using
the same IP-PBX/server or user account, additional sets of per-line parameters
can also be defined for network and user account.
You configure and modify these parameters and associated values using the
configuration files, the IP phone UI, or the Aastra Web UI. The Aastra Web UI
and configuration file methods configure global and per-line SIP settings on the IP
phone. The IP phone UI configures global SIP settings only.
On the IP Phones, you can configure Basic and Advanced SIP Settings. The Basic
SIP Settings include authentication and network settings. The Advanced SIP
Settings include other features you can configure on the IP Phone.
Reference
For more information about Basic SIP Settings (for authentication and network),
see “Basic SIP Settings” on page 4-46.
For more information bout Advanced SIP Settings, see “Advanced SIP Settings
(optional)” on page 4-58.
41-001160-00, Release 2.1, Rev 04
4-45
Configuring the IP Phones
Description
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Basic SIP Settings
The following tables identify the SIP global and per-line, authentication and
network parameters on the IP phones.
SIP Global Parameters
IP Phone UI Parameters
Aastra Web UI Parameters
Configuration File Parameters
SIP Global Authentication Parameters
•
•
•
•
•
•
•
•
Screen Name
N/A
User Name
Display Name
Auth Name
Password
N/A
N/A
•
•
•
•
•
•
•
•
Screen Name
Screen Name 2
Phone Number
Caller ID
Authentication Name
Password
BLA Number
Line Mode
•
•
•
•
•
•
•
•
•
sip screen name
sip screen name 2
sip user name
sip display name
sip auth name
sip password
sip bla number
sip mode
sip vmail
Proxy Server
Proxy Port
Backup Proxy Server
Backup Proxy Port
Outbound Proxy Server
Outbound Proxy Port
Registrar Server
Registrar Port
Backup Registrar Server
Backup Registrar Port
Registration Period
Conference Server URI
(see Chapter 5)
•
•
•
•
•
•
•
•
•
•
•
•
•
sip proxy ip
sip proxy port
sip backup proxy ip
sip backup proxy port
sip outbound proxy
sip outbound proxy port
sip registrar ip
sip registrar port
sip backup registrar ip
sip backup registrar port
sip registration period
sip centralized conf
(see Chapter 5)
SIP Global Network Parameters
•
•
•
•
•
•
•
•
•
•
•
•
Proxy Server
Proxy Port
N/A
N/A
N/A
N/A
Registrar Server
Registrar Port
N/A
N/A
N/A
N/A
•
•
•
•
•
•
•
•
•
•
•
•
Reference
For more information about centralized conferencing, see Chapter 5, the section,
“Centralized Conferencing (for Sylantro and Broadsoft Servers)” on page 5-220.
4-46
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
SIP Per-Line Parameters
Aastra Web UI Parameters
Configuration File Parameters
SIP Per-Line Authentication Parameters
•
•
•
•
•
•
•
•
Screen Name
N/A
User Name
Display Name
Auth Name
Password
N/A
N/A
•
•
•
•
•
•
•
•
Screen Name
Screen Name 2
Phone Number
Caller ID
Authentication Name
Password
BLA Number
Line Mode
•
•
•
•
•
•
•
•
•
sip lineN screen name
sip lineN screen name 2
sip lineN user name
sip lineN display name
sip lineN auth name
sip lineN password
sip lineN bla number
sip lineN mode
sip lineN vmail
Proxy Server
Proxy Port
Backup Proxy Server
Backup Proxy Port
Outbound Proxy Server
Outbound Proxy Port
Registrar Server
Registrar Port
Backup Registrar Server
Backup Registrar Port
Registration Period
Conference Server URI
(see Chapter 5)
•
•
•
•
•
•
•
•
•
•
•
•
•
sip lineN proxy ip
sip lineN proxy port
sip lineN backup proxy ip
sip lineN backup proxy port
sip lineN outbound proxy
sip lineN outbound proxy port
sip lineN registrar ip
sip lineN registrar port
sip lineN backup registrar ip
sip lineN backup registrar port
sip lineN registration period
sip lineN centralized conf
(see Chapter 5)
SIP Per-Line Network Parameters
•
•
•
•
•
•
•
•
•
•
•
•
Proxy Server
Proxy Port
N/A
N/A
N/A
N/A
Registrar Server
Registrar Port
N/A
N/A
N/A
N/A
•
•
•
•
•
•
•
•
•
•
•
•
•
Reference
For more information about centralized conferencing, see Chapter 5, the section,
“Centralized Conferencing (for Sylantro and Broadsoft Servers)” on page 5-220.
Note: The "sip vmail" and "sip lineN vmail" parameters are configurable
using the configuration files only. To configure voicemail see Chapter 5,
the section, “Voicemail (55i, 57i, and 57i CT only)” on page 5-193.
Specific sets of SIP parameters are inter-dependent with each other. To prevent
conflicting parameter values from being applied, per-line values always take
precedence over the corresponding set of global values.
41-001160-00, Release 2.1, Rev 04
4-47
Configuring the IP Phones
IP Phone UI Parameters
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
For example, if a parameter value is configured for one of the per-line sets, all
parameters from that set are applied and all parameters from the corresponding
global section are ignored, even if some of the parameters within the global set are
not defined in the per-line set.
SIP Precedence Example
The following example shows the SIP proxy feature and example schema for
storage and parsing of the SIP configuration parameters.
The following SIP configuration is assumed:
# SIP network block
sip proxy ip: 10.30.11.154
sip proxy port: 5060
sip registrar ip: 10.44.122.37
sip registrar port: 4020
sip line3 proxy ip: siparator.vonage.com
sip line3 proxy port: 0
Line3 specifies per-line values for proxy IP address and proxy port, so the phone
uses those parameter values for SIP calls made on that line. However, because
those parameters are part of the SIP network block, the phone does not apply any
of the global SIP network block parameters. So even though the global parameters
configure a SIP registrar, Line3 on the phone ignores all global network block
parameters. Since line3 does not contain a per-line SIP registrar entry, the phone
does not use a registrar for that line.
Note: Global SIP parameters apply to all lines unless overridden by a
per-line configuration.
Per-line settings are configurable for lines 1 through 7.
4-48
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Backup Proxy/Registrar Support
How it Works
All SIP registration messages are sent to the primary registrar first. If the server is
unavailable, then a new registration request is sent to the backup registrar. This
also applies to registration renewal messages, which try the primary server before
the backup.
Similarly, any outgoing calls attempt to use the primary proxy first, then the
backup if necessary. In addition, subscriptions for BLF, BLA, and explicit MWI
can also use the backup proxy when the primary fails. Outgoing calls and the
previously mentioned subscriptions behave the same as registrations, where the
primary proxy is tried before the backup.
You can configure the backup SIP proxy on a global or per-line basis via the
configuration files or the Aastra Web UI.
SIP Server (SRV) Lookup
The SIP SRV Lookup feature allows you to configure the IP phone to perform a
DNS server lookup on a SIP proxy, a SIP registrar, or a SIP outbound proxy.
The IP phone performs an SRV lookup when the IP address of the server is FQDN
and the corresponding port is 0.
For example, if the phone is configured with sip proxy ip of "ana.aastra.com",
and sip proxy port of "0", the SRV lookup may return multiple servers, based on
the priorities if one is selected as primary and others are selected as secondary.
However, if the IP address is an FQDN and the corresponding server port is
non-zero, then the phone performs a DNS "A" Name Query to resolve the FQDN
into dot notation form.
If the IP address is a valid dot notation and the port is zero, then a default port
5060 is used.
41-001160-00, Release 2.1, Rev 04
4-49
Configuring the IP Phones
The IP phones support a backup SIP proxy and backup SIP registrar feature. If
the primary server is unavailable, the phone automatically switches to the backup
server allowing the user's phone to remain in service.
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
You can configure SRV lookup using the configuration files (aastra.cfg and
<mac>.cfg) only. The parameters to use are:
•
sip proxy ip
•
sip proxy port
Configuring Basic SIP Network Settings (optional)
You can configure SIP settings using the configuration files, the IP Phone UI, or
the Aastra Web UI.
Note: To configure the SIP settings per-line, use the configuration files or
the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “SIP Basic,
Global Settings” on page A-41 or “SIP Basic, Per-Line Settings” on page A-50
4-50
Note: You can set global configuration only using the IP Phone UI.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select SIP Settings.
on the phone to enter the Options List.
Configuring Proxy IP and Proxy Port
5
Select Proxy IP/Port.
6
Enter an IP address or fully qualified host name in the Proxy Server field. Default is 0.0.0.0.
7
Enter a Proxy Port number in the Proxy Port field for accessing the SIP proxy server.
Default is 0.
8
Press Done to save the changes.
Configuring Registrar IP and Registrar Port
9
Select Registrar IP/Port.
10
Enter an IP address or fully qualified host name in the Registrar Server field. Default is 0.0.0.0.
A global value of 0.0.0.0 disables registration. However, the phone is still active and you can dial
using username@ip address of the phone.
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1, line 2, etc.), then the
register request is not sent, the "No Service" message does not display, and the message waiting
indicator (MWI) does not come on.
11
Enter a Registrar Port number in the Registrar Port field for accessing the SIP registrar server.
Default is 0.
12
Press Done to save the changes.
Enabling/Disabling the Use of the Registrar Server
13
Select SIP Register.
14
Press Change to set Register to "Yes" (enable) or "No" (disable). Default is “Yes”.
This parameter enables/disables the IP phone to register on the network.
15
Press Done to save the changes.
41-001160-00, Release 2.1, Rev 04
4-51
Configuring the IP Phones
IP Phone UI
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
IP Phone UI
Step
Action
16
Select User Name to enter the username in the name field of the SIP URI for the IP phone, and for
registering the phone at the registrar.
Note: The IP phones allow usernames containing dots (“.”).
17
Press Done to save the changes.
18
Select Display Name to enter the name used in the display name field of the "From SIP" header
field.
19
Press Done to save the changes.
20
Select Screen Name and enter the name to display on the idle screen.
21
Press Done to save the changes.
22
Select Authentication Name to enter the authorization name used in the username field of the
Authorization header field of the SIP REGISTER request.
23
Press Done to save the changes.
24
Select Password to enter the password used to register the IP phone with the SIP proxy.
Note: The IP phones accept numeric passwords only.
25
Press Done (3 times) to save the changes.
Note: The session prompts you to restart the IP phone to apply the configuration settings
26
4-52
Select Restart.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
.
Configuring the IP Phones
Aastra Web UI
Step
Action
1
For global configuration, click on Advanced Settings->Global SIP->Basic SIP Settings.
41-001160-00, Release 2.1, Rev 04
4-53
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
Aastra Web UI
Step
Action
Or, for per-line configuration, click on Advanced Settings->Line N (1-9).
To configure SIP authentication settings:
2
4-54
In the "Screen Name" field, enter the screen name that displays on the idle screen.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
3
In the "Screen Name 2" field, enter the text you want to display on the phone under the “Screen
Name” on the idle screen.
Configuring the IP Phones
Aastra Web UI
Notes:
1. If other status messages display on the phone, such as “Network Disconnected”, the Screen
Name 2 value does not display.
2. Symbol characters are allowed (such as “#”).
3. If the text is longer than the display width, than the display truncates the text to fit the display.
Figure 1
57i
Services
Dir
Callers
L1
Icom
Screen Name
Screen Name 2
John Smith
Lab Phone
Sat Jan 1 12:18am
Figure 2
53i
4
1
John Burns
Lab Phone
Sat Jun 8 2:55pm
Screen Name
Screen Name 2
In the "Phone Number" field, enter the phone number of the IP phone.
5
In the "Caller ID" field, enter the phone number of the IP phone.
6
In the "Authentication Name" field, enter the name used in the username field of the Authorization
header of the SIP REGISTER request.
7
In the "Password" field, enter the password used to register the IP phone with the SIP proxy.
Note: The IP phones accept numeric passwords only.
8
In the "BLA Number" field, enter the Bridge Line Appearance (BLA) number to be shared across all
IP phones.
41-001160-00, Release 2.1, Rev 04
4-55
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
Aastra Web UI
Step
Action
9
In the "Line Mode" field, select "Generic" for normal mode, "BroadSoft SCA" for a BroadWorks
network, or "Nortel" for a Nortel network.
To configure SIP network settings:
10
In the "Proxy Server" field, enter an IP address or fully qualified host name of the SIP proxy server.
11
In the "Proxy Port" field, enter a port number for accessing the SIP proxy server.
12
In the "Backup Proxy Server" field, enter an IP address or fully qualified host name for the backup
proxy server.
13
In the "Backup Proxy Port" field, enter a port number for accessing the backup proxy server.
14
In the "Outbound Proxy Server" field, enter the SIP outbound proxy server IP address or fully
qualified domain name. This parameter allows all SIP messages originating from a line on the IP
phone, to be sent to an outbound proxy server.
Note: If you configure an outbound proxy and registrar for a specific line, and you also configure a
global outbound proxy and registrar, 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.
15
In the "Outbound Proxy Port" field, enter the port on the IP phone that allows SIP messages to be
sent to the outbound proxy server.
16
In the "Registrar Server" field, enter an IP address or fully qualified host name for the SIP registrar
server. A global value of 0.0.0.0 disables registration. However, the phone is still active and you can
dial using username@ip address of the phone.
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1, line 2, etc.), then the
register request is not sent, the "No Service" message does not display, and the message waiting
indicator (MWI) does not come on.
17
In the "Registrar Port" field, enter the port number associated with the Registrar.
18
In the "Backup Registrar Server" field, enter an IP address or fully qualified host name for the
backup registrar server. A global value of 0.0.0.0 disables registration. However, the phone is still
active and you can dial using username@ip address of the phone.
If the Backup Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1, line 2, etc.), then
the register request is not sent, the "No Service" message does not display, and the message waiting
indicator (MWI) does not come on.
19
In the "Backup Registrar Port" field, enter the port number associated with the backup registrar.
20
In the "Registration Period" field, enter the requested registration period, in seconds, from the
registrar.
4-56
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
21
To enter a value in the “Conference Server URI” field, see Chapter 5, the section, “Centralized
Conferencing (for Sylantro and Broadsoft Servers)” on page 5-220.
22
Click
Configuring the IP Phones
Aastra Web UI
to save your changes.
41-001160-00, Release 2.1, Rev 04
4-57
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Advanced SIP Settings (optional)
Advanced SIP Settings on the IP Phone allow you to configure specific features
on the phone. The following table provides a list of Advanced SIP Settings that
you can configure using the Aastra Web UI or the configuration files.
Aastra Web UI Parameters
Configuration File Parameters
Explicit MWI Subscription
Explicit MWI Subscription Period
sip explicit mwi subscription
sip explicit mwi subscription period
Missed Call Summary Subscription (see Chapter 6)
(global and per-line settings)
missed call summary subscription (see Chapter 6)
(global and per-line settings)
Missed Call Summary Subscription Period
(see Chapter 6)
Send MAC Address in REGISTER Message
(see Chapter 6)
Send Line Number in REGISTER Message
(see Chapter 6)
Session Timer
T1 Timer
T2 Timer
Transaction Timer
Transport Protocol
Registration Failed Retry Timer
Registration Timeout Retry Timer
Registration Renewal Timer
BLF Subscription Period (see Chapter 5)
ACD Subscription Period (see Chapter 5)
Blacklist Duration (see Chapter 6)
Whitelist Proxy (see Chapter 6)
missed call summary subscription period
(see Chapter 6)
sip send mac (see Chapter 6)
sip send line (see Chapter 6)
sip session timer
sip T1 timer
sip T2 timer
sip transaction timer
sip transport protocol
sip registration retry timer
sip registration timeout retry timer
sip registration renewal timer
sip blf subscription period (see Chapter 5)
sip acd subscription period (see Chapter 5)
sip blacklist duration (see Chapter 6)
sip whitelist (see Chapter 6)
Note: You configure Advanced SIP settings on a global basis only.
4-58
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Reference
For more information about Blacklist Duration and Whitelist Proxy, see
Chapter 6, “Configuring Advanced Operational Features.”
Configuring Advanced SIP Settings
Use the following procedures to configure the advanced SIP settings on the IP
phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Advanced SIP
Settings” on page A-62.
41-001160-00, Release 2.1, Rev 04
4-59
Configuring the IP Phones
Refer to Appendix A,“Advanced SIP Settings” on page A-62 for a description of
each of the above parameters.
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
.
Aastra Web UI
Step
Action
For Global configuration, click on Advanced Settings->Global SIP->Advanced SIP Settings.
1
4-60
Or for per-line configuration, click on Advanced Settings->Line N (1-9).
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
2
Enable the "Explicit MWI Subscription" field by checking the check box.
(Disable this field by unchecking the check box. Default is disabled).
If the IP phone has a message waiting subscription with the Service Provider, a Message Waiting
Indicator (MWI) (LED or display icon) tells the user there is a message on the IP Phone.
3
If you enable the “Explicit MWI Subscription” field, then in the “Explicit MWI Subscription Period”
field, enter the requested duration, in seconds, before the MWI subscription times out. The phone
re-subscribes to MWI before the subscription period ends. Default is 86400.
4
Enable the “Missed Call Summary Subscription” field by checking the check box.
(Disable this field by unchecking the check box. Default is disabled).
This feature allows missed calls that have been redirected by the server, to be incremented in the
missed calls indicator on the phone it was initially directed to. For more information about this feature,
see Chapter 6, “Configuring Advanced Operational Features.”.
Note: The “Missed Call Summary Subscription” feature is configurable on a global or per-line basis.
5
If you enable the “Missed Call Summary Subscription” field, then in the “Missed Call Summary
Subscription Period” field, enter the amount of time, in seconds, that the phone uses the Missed
Calls Summary Subscription feature. Default is 86400.
For more information about this feature, see Chapter 6, “Configuring Advanced Operational
Features.”
Note: The “Missed Call Summary Subscription Period” is configurable on a global basis only.
6
Enable the “Send MAC Address in REGISTER Message” and the “Send Line Number in
REGISTER Message” fields by checking the check boxes.
(Disable these fields by unchecking the check boxes. Default is disabled for both fields).
For more information about these message features, see Chapter 6, “Configuring Advanced
Operational Features.”.
7
In the "Session Timer" field, enter the time, in seconds, that the IP phone uses to send periodic
re-INVITE requests to keep a session alive. The proxy uses these re-INVITE requests to maintain the
status' of the connected sessions. See RFC4028 for details.
8
In the "Timer 1 and Timer 2" fields, enter a time, in milliseconds, that will apply to an IP phone
session. These timers are SIP transaction layer timers defined in RFC 3261.
Timer 1 is an estimate of the round-trip time (RTT). Default is 500 msec.
Timer 2 represents the amount of time a non-INVITE server transaction takes to respond to a
request. Default is 4 seconds.
41-001160-00, Release 2.1, Rev 04
4-61
Configuring the IP Phones
Aastra Web UI
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
Aastra Web UI
Step
Action
9
In the "Transaction Timer" field, enter the amount of time, in milliseconds, that the phone allows the
call server (registrar/proxy) to respond to SIP messages that it sends.
Valid values are 4000 to 64000. Default is 4000.
Note: If the phone does not receive a response in the amount of time designated for this parameter,
the phone assumes the message has timed out.
10
In the "Transport Protocol" field, select a transport protocol to use when sending SIP Real-time
Transport Protocol (RTP) packets. Valid values are User Datagram Protocol (UDP) and Transmission
Control Protocol (TCP), UDP, TCP, Transport Layer Security (TLS) or Persistent TLS. The value
“UDP” is the default. For more information about TLS, see “RTP Encryption” on page 4-68 and
Chapter 5, the section, “Transport Layer Security (TLS)” on page 6-21.
11
In the " Registration Failed Retry Timer" field, enter the amount of time, in seconds, that the phone
waits between registration attempts when a registration is rejected by the registrar.
Valid values are 30 to 1800. Default is 1800.
12
In the " Registration Timeout Retry Timer" field, enter the amount of time, in seconds, that the
phone waits until it re-attempts to register after a REGISTER message times out.
Valid values are 30 to 214748364. Default is 120.
13
In the " Registration Renewal Timer" field, enter the length of time, in seconds, prior to expiration,
that the phone renews registrations.
For example, if the value is set to 20, then 20 seconds before the registration is due to expire, a new
REGISTER message is sent to the registrar to renew the registration.
Valid values are 0 to 214748364. Default is 15.
14
The “BLF Subscription Period” field is enabled by default with a value of 3600 seconds.
This feature sets the time period, in seconds, that the IP phone resubscribes the BLF subscription
service after a software/firmware upgrade or after a reboot of the IP phone.
For information about setting the “BLF Subscription Period”, see Chapter 5, the section,
“BLF Subscription Period” on page 5-120.
15
(For Sylantro Servers) The “ACD Subscription Period” field is enabled by default with a value of
3600 seconds.
This feature sets the time period, in seconds, that the IP phone resubscribes the BLF subscription
service after a software/firmware upgrade or after a reboot of the IP phone.
For information about setting the “ACD Subscription Period”, see Chapter 5, the section,
“ACD Subscription Period” on page 5-133.
4-62
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
16
(For Broadsoft Servers) The “Blacklist Duration” field is enabled by default with a value of 300
seconds (5 minutes). Valid values are 0 to 9999999.
This feature sets the time period, in seconds, that the IP phone resubscribes the BLF subscription
service after a software/firmware upgrade or after a reboot of the IP phone.
Note: The value of “0” disables the blacklist feature.
For information about setting the “Blacklist Duration”, see Chapter 6, the section, “Blacklist Duration
(Broadsoft Servers)” on page 6-17.
17
Enable the "Whitelist Proxy" field by checking the check box.
(Disable this field by unchecking the check box. Default is disabled).
When this feature is enabled, an IP phone accepts call requests from a trusted proxy server only. The
IP phone rejects any call requests from an untrusted proxy server.
For information about setting the “Whitelist Proxy”, see Chapter 6, the section, “Whitelist Proxy” on
page 6-19.
18
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
4-63
Configuring the IP Phones
Aastra Web UI
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Real-time Transport Protocol (RTP) Settings
Real-time Transport Protocol (RTP) is used as the bearer path for voice packets
sent over the IP network. Information in the RTP header tells the receiver how to
reconstruct the data and describes how the bit streams are packetized (i.e. which
codec is in use). Real-time Transport Control Protocol (RTCP) allows endpoints
to monitor packet delivery, detect and compensate for any packet loss in the
network. Session Initiation Protocol (SIP) and H.323 both use RTP and RTCP for
the media stream, with User Datagram Protocol (UDP) as the transport layer
encapsulation protocol.
Note: If RFC2833 relay of DTMF tones is configured, it is sent on the
same port as the RTP voice packets.
You can set the following parameters for RTP on the IP Phones:
Aastra Web UI Parameters
Configuration File Parameters
RTP Port
sip rtp port
Basic Codecs (G.711 u-Law, G.711 a-Law, G.729)
sip use basic codecs
Force RFC2833 Out-of-Band DTMF
sip out-of-band dtmf
Customized Codec Preference List
sip customized codec
DTMF Method (global and per-line settings)
sip dtmf method (global and per-line settings)
RTP Encryption (global and per-line settings)
sip srtp mode (global and per-line settings)
Silence Suppression
sip silence suppression
4-64
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
RTP Port
The RTP port is assigned to the first line on the phone, and is then incremented for
each subsequent line available within the phone to provided each line a unique
RTP port for its own use.
On the IP phone, the initial port used as the starting point for RTP/RTCP port
allocation can be configured using "RTP Port Base". The default RTP base port
on the IP phones is 3000.
For example, if the RTP base port value is 5000, the first voice patch sends RTP
on port 5000 and RTCP on port 5001. Additional calls would then use ports 5002,
5003, etc.
You can configure the RTP port on a global-basis only, using the configuration
files, the IP Phone UI, or the Aastra Web UI.
Basic Codecs (G.711 u-Law, G.711 a-Law, G.729)
CODEC is an acronym for COmpress-DECompress. It consists of a set of
instructions that together implement one or more algorithms. In the case of IP
telephony, these algorithms are used to compress the sampled speech data, to
decrease the content's file size and bit-rate (the amount of network bandwidth in
kilobits per second) required to transfer the audio. With smaller file sizes and
lower bit rates, the network equipment can store and stream digital media content
over a network more easily.
Aastra IP phones support the International Telecommunications Union (ITU)
transmission standards for the following CODECs:
•
Waveform CODECs: G.711 pulse code modulation (PCM) with a-Law or
u-Law companding
•
Parametric CODEC: G.729a conjugate structure - algebraic code excited
linear prediction (CS_ACELP).
41-001160-00, Release 2.1, Rev 04
4-65
Configuring the IP Phones
RTP is described in RFC1889. The UDP port used for RTP streams is traditionally
an even-numbered port, and the RTCP control is on the next port up. A phone call
therefore uses one pair of ports for each media stream.
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
All Codecs have a sampling rate of 8,000 samples per second, and operate and
operate in the 300 Hz to 3,700 Hz audio range. The following table lists the
default settings for bit rate, algorithm, packetization time, and silence suppression
for each Codec, based on a minimum packet size.
Default Codec Settings.
Bit Rate
Algorithm
Packetizatio
n Time
Silence
Suppression
G.711 a-law
64 Kb/s
PCM
30 ms
enabled
G.711 u-law
64 Kb/s
PCM
30 ms
enabled
G.729a
8
Kb/s
CS-ACELP
30 ms
enabled
CODEC
You can enable the IP phones to use a default "basic codec" set, which consists of
the set of codecs and packet sizes shown above.
Or you can instead configure a custom set of codecs and attributes instead of using
the defaults.
Note: The basic and custom codec parameters apply to all calls, and are
configured on a global-basis only using the configuration files or the
Aastra Web UI.
Customized Codec Preference List
You can also configure the IP phones to use preferred Codecs. To do this, you
must enter the payload value (payload), the packetization time in milliseconds
(ptime), and enable or disable silence suppression (silsupp).
Payload is the codec type to be used. This represents the data format carried
within the RTP packets to the end user at the destination. You can enter payload
values for G.711 a-law, G.711 u-law, and G.729a.
Ptime (packetization time) is a measurement of the duration of PCM data within
each RTP packet sent to the destination, and hence defines how much network
bandwidth is used for transfer of the RTP stream. You enter the ptime values for
the customized Codec list in milliseconds. (See table below).
4-66
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
You must enter the values for this feature in list form as shown in the following
example:
payload=8;ptime=10;silsupp=on; payload=0;ptime=10;silsupp=off
The valid values for creating a Codec preference list are as follows.
Customized Codec Settings
Attribute
Value
payload
0 for G.711 u-Law
8 for G.711 a-Law
18 for G.729a
ptime (in milliseconds)
5, 10, 15, 20.......90
silsupp
on
off
You can specify a customized Codec preference list on a global-basis using the
configuration files or the Aastra Web UI.
Out-of-Band DTMF
The IP phones support out-of-band Dual-Tone Multifrequency (DTMF) mode
according to RFC2833. In the Aastra Web UI, you can enable or disable this
feature as required. The "out-of-band DTMF" is enabled by default.
In out-of-band mode, the DTMF audio is automatically clamped (muted) and
DTMF digits are not sent in the RTP packets.
You can configure out-of-band DTMF on a global-basis using the configuration
files or the Aastra Web UI.
41-001160-00, Release 2.1, Rev 04
4-67
Configuring the IP Phones
Silsupp is used to enable or disable silence suppression. Voice Activity Detection
(VAD) on the IP phones is used to determine whether each individual packet
contains useful speech data. Enabling silsupp results in decreased network
bandwidth, by avoiding sending RTP packets for any frame where no voice
energy was detected by the VAD.
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
DTMF Method
A feature on the IP phone allows you to select the DTMF method that the phone
uses to send DTMF digits from the IP phone via INFO messages. You can set the
DTMF method as Real-Time Transport Protocol (RTP), SIP info, or both.
You can configure the DTMF method on a global or per-line basis using the
configuration files or the Aastra Web UI.
RTP Encryption
The IP Phones include support for Secure Real-time Transfer Protocol (SRTP),
using Session Description Protocol Security (SDES) key negotiation, for
encryption and authentication of RTP/RTCP messages sent and received by the
Aastra IP phones on your network.
As administrator, you specify the global SRTP setting for all lines on the IP
phone. You can choose among three levels of SRTP encryption, as follows:
•
SRTP Disabled (default): IP phone generates and receives nonsecured RTP
calls. If the IP phone gets called from SRTP enabled phone, it ignores SRTP
tries to answer the call using RTP. If the receiving phone has SRTP only
enabled, the call fails; however, if it has SRTP preferred enabled, it will accept
RTP call.
•
SRTP Preferred: IP phone generates RTP secured calls, and accepts both
secured and non-secured RTP calls. If the receiving phone is not SRTP
enabled, it sends non-secured RTP calls instead.
•
SRTP Only: IP phone generates and accepts RTP secured calls only; all other
calls are rejected (fail).
You can override the global setting as necessary, configuring SRTP support on a
per-line basis. This allows IP phone users to have both secured and unsecured
lines operating on the same phone.
4-68
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Note: If you enable SRTP, then you should also enable Transport Layer
Security (TLS). This prevents capture of the key used for SRTP
encryption. To enable TLC, set the Transport Protocol parameter
(located on the Global SIP Settings menu) to TLS.
You can configure SRTP on a global or per-line basis using the configuration files
or the Aastra Web UI.
Silence Suppression
In IP telephony, silence on a line (lack of voice) uses up bandwidth when sending
voice over a packet-switched system. Silence suppression is encoding that starts
and stops the times of silence in order to eliminate that wasted bandwidth.
Silence suppression is enabled by default on the IP phones. The phone negotiates
whether or not to use silence suppression. Disabling this feature forces the phone
to ignore any negotiated value.
You can configure silence suppression on a global-basis using the configuration
files or the Aastra Web UI.
41-001160-00, Release 2.1, Rev 04
4-69
Configuring the IP Phones
If an SRTP enabled IP phone initiates a call, and the receiving phone is also SRTP
enabled, the IP Phone UI displays a “lock” icon, indicating that the call is secure.
If the receiving phone does not support SRTP, the IP phone will send unsecured
RTP messages instead of SRTP encrypted messages. However in this case, the IP
Phone UI does not display the lock icon - indicating a non-secure call.
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Configuring RTP Features
Use the following procedures to configure the RTP features on the IP phone.
Configuration Files
For specific parameters you can set for RTP features in the configuration files, see Appendix A, the section,
“RTP, Codec, DTMF Global Settings” on page A-77.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select SIP Settings.
5
Select RTP Port Base to change the RTP port base setting. Default is 3000.
6
Press Done (2 times) to save the change.
on the phone to enter the Options List.
Note: The session prompts you to restart the IP phone to apply the configuration settings
7
4-70
Select Restart.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
.
Configuring the IP Phones
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Global SIP->RTP Settings.
Global Settings.
41-001160-00, Release 2.1, Rev 04
4-71
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
Aastra Web UI
Step
Action
Click on Advanced Settings->Line <N>->RTP Settings.
Per-Line Settings.
2
Enter an RTP Port Base in the RTP Port field. Default is 3000.
The RTP Port indicates the port through which the RTP packets are sent. This value must specify the
beginning of the RTP port range on the gateway or router. The RTP port is used for sending DTMF
tones and for the audio stream. Your network administrator may close some ports for security
reasons. You may want to use this parameter to send RTP data using a different port.
3
Enable the "Basic Codecs (G.711 u-Law, G.711 a-Law, G.729)" field by checking the check box.
(Disable this field by unchecking the box. Default is disabled).
Enabling this parameter allows the IP phone to use the basic Codecs when sending/receiving RTP
packets.
4
The "Force RFC2833 Out-of-Band DTMF" field is enabled by default. Disable this field by
unchecking the box.
Enabling this parameter forces the IP phone to use out-of-band DTMF according to RFC2833.
4-72
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Step
Action
5
Enter a "Customized Codec Preference List". For example,
payload=8;ptime=10;
silsupp=on;
payload=0;ptime=10;
silsupp=off
Valid values are:
Attribute
Value
payload
0 for G.711 u-Law
8 for G.711 a-Law
18 for G.729a
ptime (in milliseconds)
5, 10, 15, 20.....90
silsupp
on
off
For this parameter, you specify a customized codec list which allows you to use the preferred Codecs
for this IP phone. Default for the “Customized Codec Preference List” is blank.
6
Select a method to use from the “DTMF Method” list box. Valid values are RTP, SIP Info, Both.
Default is RTP.
Note: You can configure the DTMF Method on a global or per-line basis.
7
Select the type of RTP encryption to use from the “RTP Encryption” list box. Valid values are SRTP
Disabled, SRTP Preferred, or SRTP Only. Default is SRTP Disabled.
Note: You can configure RTP Encryption on a global or per-line basis.
8
The “Silence Suppression” field is enabled by default. Disable this field by unchecking the check
box.
When enabled, the phone negotiates whether or not to use silence suppression. Disabling this
feature forces the phone to ignore any negotiated value.
9
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
4-73
Configuring the IP Phones
Aastra Web UI
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Autodial Settings
4-74
The IP phones include a feature called “Autodial”. When you configure Autodial
on an IP phone, the phone automatically dials a preconfigured number whenever
it is off-hook. Depending on the configuration you specify, the Autodial functions
as either a “hotline”, or as a “warmline,” as follows:
•
Hotline (default): The IP phone immediately dials a preconfigured number
when you lift the handset.
•
Warmline: The IP phone waits for a specified amount of time after you lift
the handset before dialing a preconfigured number. If you do not dial a
number within the time allotted, then the IP phone begins to dial the number.
By default, the Autodial feature functions as a hotline. If you want Autodial to
function as a warmline, you can use the Autodial “time-out” parameter to specify
the length of time (in seconds) the IP phone waits before dialing a preconfigured
number.
As administrator, you configure Autodial globally, or on a per-line basis, for an IP
phone. The line setting overrides the global setting. For example, you can disable
Autodial on a specific line simply by setting the line’s autodial number parameter
to empty (blank).
Note: IMPORTANT INFORMATION before configuring Autodial on
your IP phone:
•
Any speeddial numbers that you configure on an IP phone are not
affected by autodial settings.
•
If you configure autodial on your IP phone, any lines that function as
hotlines do not accept conference calls, transferred calls, and/or
intercom calls.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
Configuring AutoDial Using the Configuration Files
Global Configuration
•
sip autodial number
•
sip autodial timeout
Per-Line Configuration
•
sip lineN autodial number
•
sip lineN autodial timeout
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Autodial
Settings” on page A-81.
41-001160-00, Release 2.1, Rev 04
4-75
Configuring the IP Phones
You use the following parameters to configure Autodial using the configuration
files:
IP Phone Administrator Guide
Global SIP Settings
Configuring the IP Phones
Configuring Autodial Using the Aastra Web UI
Use the following procedure to configure Autodial using the Aastra Web UI.
By default, your IP phone uses the global settings you specify for Autodial for all
lines on your IP phone. However, you can also configure Autodial on a per-line
basis.
Aastra Web UI
Global Configuration
1
Click on Advanced Settings->Global SIP->Autodial Settings.
2
In the “Autodial Number” field, specify the SIP number that the IP phone dials whenever the IP
phone is off-hook. An empty (blank) value disables autodial on the phone.
For example: 8500
4-76
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Global SIP Settings
3
In the “Autodial Timeout” field, specify a value, in seconds, for the timer as follows:
•
If you want the IP phone to autodial the number immediately (hotline) whenever the IP phone is
off-hook, accept the default value of 0.
•
If you want to specify a length of time for the IP phone to wait before dialing the number, enter
the length of time (in seconds). For example: 30
Valid values are 0 to 120.
4
Click
to save your changes.
Per-Line Configuration
1
Click on Advanced Settings->Line <1 - 9>->Autodial Settings.
41-001160-00, Release 2.1, Rev 04
4-77
Configuring the IP Phones
Aastra Web UI
Configuring the IP Phones
IP Phone Administrator Guide
Global SIP Settings
Aastra Web UI
2
3
4
Do one of the following actions:
•
To allow this line to use the global autodial settings, click on the Use Global Settings parameter
to enable it, then click
to save your changes.
•
To specify a different autodial configuration for this specific line, disable the Use Global
Settings parameter. Then proceed to step 3.
In the “Autodial Number” field, specify the SIP number for this line that the IP phone dials
whenever the IP phone is off-hook as follows:
•
If set to -1, then the global autodial settings for this IP phone to this line.
•
If set to empty (blank), then disable Autodial on this line.
•
If set to a valid SIP number, dial the SIP number specified for this line. For example: 8500
In the “Autodial Timeout” field, specify a value, in seconds, for the timer for this line as follows:
•
If you want the IP phone to autodial the number immediately (hotline) whenever the IP phone is
off-hook, accept the default value of 0.
•
If you want to specify a length of time for the IP phone to wait before dialing the number, enter
the length of time (in seconds). For example: 30
Valid values are 0 to 120.
5
4-78
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Configuration Server Protocol
Configuration Server Protocol
Note: For DHCP to automatically populate the IP address or domain
name for the TFTP, FTP, HTTP, or HTTPS server, your DHCP server
must support download protocol according to RFC2131 and RFC1541 for
Option 66. For more information, see this chapter, the section, “DHCP”
on page 4-4.
Configuring the Configuration Server Protocol
Use the following procedure to configure the configuration server protocol.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Configuration
Server Settings” on page A-13.
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu.
3
Enter your Administrator password.
Note: The IP Phones accept numeric passwords only.
4
Select Configuration Server.
5
Select Download Protocol.
on the phone to enter the Options List.
41-001160-00, Release 2.1, Rev 04
4-79
Configuring the IP Phones
You can download new versions of firmware and configuration files from the
configuration server to the IP phone using any of the following types of protocols:
TFTP, FTP, HTTP, and HTTPS. The TFTP setting is the default download
protocol. You can configure the type of protocol that the IP phone uses by setting
it in the configuration files, the IP phone UI, or the Aastra Web UI.
Configuring the IP Phones
IP Phone Administrator Guide
Configuration Server Protocol
IP Phone UI
Step
Action
6
Select from the following:
• Use TFTP
• Use FTP
• Use HTTP
• Use HTTPS
Default is “Use TFTP”.
The IP phone uses the protocol you select to download new firmware and configuration files from
the configuration server.
7
Press Done to save the changes.
8
From the Configuration Server menu, select from the following. This selection is dependent on the
Download Protocol you selected in step 6.
4-80
TFTP Settings
FTP Settings
HTTP Settings
HTTPS Settings
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Configuration Server Protocol
Step
Action
9
Enter the IP address of the protocol server (in dotted decimal format).
Use the following table to configure the applicable server.
TFTP Settings
- Select Primary TFTP
- Enter the IP address or qualified domain name of the primary TFTP server.
- Press Done to save the change.
Optional: You can also configure an Alternate TFTP server if required by selecting the
“Alternate TFTP” selection and configuring an IP address or qualified domain name for the
alternate TFTP server.
- From the TFTP Settings menu, select “Select TFTP”.
- Press Change to select the “Primary” or “Alternate” TFTP server to use for the phone.
- Press Done to save the change.
FTP Settings
- Select FTP Server.
- Enter the IP address of the FTP server.
- Press Done.
Optional: You can enter a username and password for accessing the FTP server if required:
-
Select FTP Username.
Enter a username for accessing the FTP server.
Press Done.
Select FTP Password.
Enter a password for accessing the FTP server.
Press Done.
HTTP Settings
-
Select HTTP Server
Enter the IP address of the HTTP server.
Press Done.
Select HTTP Path.
Enter the HTTP sub-directory path name. If the IP phone’s files are located in a sub-directory
beneath the server’s HTTP root directory, the relative path to that sub-directory should be
entered in this field.
- Press Done.
41-001160-00, Release 2.1, Rev 04
4-81
Configuring the IP Phones
IP Phone UI
Configuring the IP Phones
IP Phone Administrator Guide
Configuration Server Protocol
IP Phone UI
Step
Action
9
(Cont’d)
HTTPS Settings
-
Select HTTP Client.
Select Download Server.
Enter the IP address of the HTTPS server.
Press Done.
Select Download Path.
Enter the HTTPS path name. If the IP phone’s configuration files and firmware files are
located in a sub-directory beneath the server’s HTTPS root directory, the relative path to that
sub-directory should be entered in this field.
- Press Done.
- Select HTTPS Server.
- Select HTTP->HTTPS.
- Press Change to select “Yes” or “No”. Default is “No”.
Enabling this feature redirects the HTTP protocol to HTTPS.
- Press Done.
- Select XML HTTP POSTs.
- Press Change to select “Yes” or “No”. Default is “No”.
Enabling this feature blocks XML HTTP POSTs from the IP Phone.
Reference: For more information on configuring the HTTPS security method, HTTP to HTTPS
redirect, and HTTPS server blocking for HTTP XML POSTs, see the section, “HTTPS Client/
Server Configuration” on page 4-23.
10
Press Done (4 times) to save the changes.
Note: The session prompts you to restart the IP phone to apply the configuration settings
11
4-82
Select Restart.
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Configuration Server Protocol
Configuring the IP Phones
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Configuration Server.
41-001160-00, Release 2.1, Rev 04
4-83
Configuring the IP Phones
IP Phone Administrator Guide
Configuration Server Protocol
Aastra Web UI
Step
Action
2
Select the protocol from the "Download Protocol" list box. Valid values are TFTP, FTP, HTTP, and
HTTPS. Default is TFTP.
The IP phone uses the protocol you select to download new firmware and configuration files from the
configuration server. Use the following table to configure the applicable server.
TFTP
- Enter an IP address or qualified domain name in the "TFTP Server" field.
Optional: You can also configure an alternate TFTP server if required. If "Use Alternate
TFTP" is enabled, you must also enter an IP address or qualified domain name for the
alternate server in the "Alternate TFTP" field.
FTP
- Enter an IP address in the "FTP Server" field.
Optional: You can enter a username and password for accessing the FTP server if
required.
- Enter a username for a user that will access the FTP server in the "FTP User Name" field.
- Enter a password for a user that allows access to the FTP server in the "FTP Password"
field.
HTTP
- Enter an IP address in the "HTTP Server" field.
- Enter a root sub-directory path for the HTTP server in the "HTTP Path" field.
Optional: You can enter a list of users to be authenticated when they access the HTTP
server in the "XML Push Server List (Approved IP Addresses)" field.
HTTPS
- Enter an IP address in the "HTTPS Server" field.
- Enter a root directory path for the HTTPS server in the "HTTP Path" field.
Optional: You can enter a list of users to be authenticated when they access the HTTP
server in the "XML Push Server List (Approved IP Addresses)" field.
Reference: For more information on configuring the HTTPS security method, HTTP to HTTPS
redirect, and HTTPS server blocking for HTTP XML POSTs, see the section, “HTTPS Client/Server
Configuration” on page 4-23.
4-84
41-001160-00, Release 2.1, Rev 04
Configuring Network and Session Initiation Protocol (SIP) Features
Configuration Server Protocol
Step
Action
3
Click
Configuring the IP Phones
Aastra Web UI
to save your settings.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
4
Select Operation->Reset and click
41-001160-00, Release 2.1, Rev 04
.
4-85
Configuring the IP Phones
IP Phone Administrator Guide
Configuration Server Protocol
4-86
41-001160-00, Release 2.1, Rev 04
About this chapter
Introduction
The IP phones have specific operational features you can configure to customize
your IP phone. This chapter describes each feature and provides procedures for
configuring your phone to use these features.
Topics
This chapter covers the following topics:
Topic
Page
Operational Features
page 5-4
User Passwords
page 5-4
Administrator Passwords
page 5-8
Locking/Unlocking the Phone
page 5-9
Defining an Emergency Dial Plan
page 5-15
Time and Date
page 5-17
Language
page 5-21
Locking IP Phone Keys
page 5-28
Local Dial Plan
page 5-30
Park Calls/Pick Up Parked Calls
page 5-35
Suppressing DTMF Playback
page 5-39
Display DTMF Digits
page 5-41
41-001160-00, Release 2.1, Rev 04
5-1
Operational IP Phone Features
Chapter 5
Configuring Operational Features
IP Phone Administrator Guide
About this chapter
Operational IP Phone Features
Topic
5-2
Page
Call Waiting/Call Waiting Tone
page 5-43
Stuttered Dial Tone
page 5-46
XML Beep Support
page 5-48
Status Scroll Delay
page 5-50
Incoming Call Interrupts Dialing
page 5-52
Goodbye Key Cancels Incoming Call
page 5-54
UPnP Mapping Lines (for remote phones)
page 5-56
Message Waiting Indicator Line
page 5-58
Incoming/Outgoing Intercom with Auto-Answer and Barge In
page 5-60
Key Mapping
page 5-66
Ring Tones and Tone Sets
page 5-70
Priority Alerting
page 5-75
Directed Call Pickup (BLF or XML Call Interception)
page 5-81
Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys
page 5-93
Speeddial Prefixes
page 5-113
Busy Lamp Field (BLF)
page 5-114
BLF Subscription Period
page 5-120
Automatic Call Distribution (ACD) (for Sylantro Servers)
page 5-122
ACD Subscription Period
page 5-133
Directed Call Pickup/Group Call Pickup (for Sylantro Servers)
page 5-135
Do Not Disturb (DND)
page 5-142
Bridged Line Appearance (BLA) (55i, 57i, 57i CT only)
page 5-144
BLA Support for Third Party Registration
page 5-151
Park/Pick Up Key
page 5-153
Last Call Return (lcr) (For Sylantro Servers
page 5-164
Call Forwarding
page 5-168
Callers List
page 5-174
Customizable Callers List and Services Keys
page 5-179
Missed Calls Indicator
page 5-180
Directory List
page 5-182
Voicemail (55i, 57i, and 57i CT only)
page 5-193
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
About this chapter
Topic
Page
page 5-196
Audio Transmit and Receive Gain Adjustments
page 5-218
Centralized Conferencing (for Sylantro and Broadsoft Servers)
page 5-220
Customizing the Display Columns on the 560M Expansion Module
page 5-224
41-001160-00, Release 2.1, Rev 04
5-3
Operational IP Phone Features
XML Customized Services
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Operational Features
Description
This section describes the operational features managed and configured by a
System Administrator.
User Passwords
A user or an administrator can change the user passwords on the phone using the
configuration files, the IP phone UI, or the Aastra Web UI.
Use the following procedures to change the user password.
Note: The IP phones support numeric characters only in passwords. If
you enter a password with alpha characters, the phone uses the default
password instead.
Configuring a User Password
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Password
Settings” on page A-9.
IP Phone UI
1
Press
2
Select User Password.
3
Enter the current user password.
4
Press Enter.
5-4
on the phone to enter the Options List.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
5
Operational IP Phone Features
IP Phone UI
Enter the new user password.
Note: The IP phones support numeric characters only in passwords. If you enter a password with
alpha characters, the phone uses the default password instead.
6
Press Enter.
7
Re-enter the new user password.
8
Press Enter.
A message, "Password Changed" displays on the screen.
Aastra Web UI
1
Click on Operation->User Password.
2
In the "Current Password" field, enter the current user password.
3
In the "New Password" field, enter the new user password.
Note: The IP phones support numeric characters only in passwords. If you enter a password with
alpha characters, the phone uses the default password instead.
4
In the "Password Confirm" field, enter the new user password again.
5
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-5
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Resetting a User Password
If a user forgets his password, either the user or an administrator can reset it so a
new password can be entered. The reset user password feature resets the password
to the factory default which is blank (no password).
You can reset a user password using the Aastra Web UI only at the path
Operation->Phone Lock. Use the following procedure to reset a user password.
Aastra Web UI
1
5-6
Click on Operation->Phone Lock.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
2
In the “Reset User Password” field, click
Operational IP Phone Features
Aastra Web UI
.
The following screen displays:
3
In the “Current Password” field, leave this blank.
4
In the “New Password” field, enter a new password for the user.
Note: The IP phones support numeric characters only in passwords. If you enter a password with
alpha characters, the phone uses the default password instead.
5
In the “Password Confirm” field, re-enter the new user password.
6
Click
to save the new user password and perform the next procedure.
41-001160-00, Release 2.1, Rev 04
5-7
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Administrator Passwords
An administrator can change the administrator passwords on the phone using the
configuration files only.
An administrator can also assign a password for using the Options key on the IP
phone. You turn this feature on and off by entering the "options password
enabled" parameter followed by a valid value in the configuration files. Valid
values are 0 (false; Options key not password protected), or 1 (true; Options key
password protected). If this parameter is set to 1, 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.
Procedure
Use the following procedure to change the administrator password.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Password
Settings” on page A-9.
5-8
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Locking/Unlocking the Phone
You can lock/unlock a phone using the configuration files, the IP Phone UI, or the
Aastra Web UI.
You can use any of the following methods to lock/unlock a phone:
•
Using the IP Phone UI via the “Phone Lock” option in the Options Menu.
•
Using the Aastra Web UI via the path Operation->Phone Lock.
•
Using the configuration files to configure a key as “phonelock”, and then
pressing the key to lock/unlock the phone.
•
Using the Aastra Web UI to configure a key as “Phone Lock”, and then
pressing the key to lock/unlock the phone.
Note: All of the methods above configure locking/unlocking of the
phone dynamically. Once configured, the feature takes affect
immediately. To unlock the phone, a user or administrator must enter their
password.
41-001160-00, Release 2.1, Rev 04
5-9
Operational IP Phone Features
A user or administrator can lock a phone to prevent it from being used or
configured. Once the phone is locked, the user or administrator can enter their
password to unlock the phone.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Locking/Unlocking the Phone Using the IP Phone UI
Use the following IP Phone UI procedure to lock/unlock an IP phone and prevent
it from being used or configured.
IP Phone UI
Step
Action
Lock the phone:
1
Press
on the phone to enter the Options List.
2
Select Phone Lock.
The prompt, “Lock the phone?” displays.
3
Press Lock to lock the phone.
Unlock the phone:
1
Press
on the phone to enter the Options List.
The prompt, “To unlock the phone...Password:”
2
5-10
Enter the user or administrator password and press Enter.
The phone unlocks.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Locking/Unlocking the Phone Using the Aastra Web UI
Operational IP Phone Features
Use the following Aastra Web UI procedure to lock/unlock an IP phone and
prevent it from being used or configured.
Aastra Web UI
1
Click on Operation->Phone Lock.
Lock the phone:
2
In the “Lock the Phone?” field, click
.
The phone locks dynamically and displays the following message:
“Phone is locked”.
Unlock the phone:
3
Click on Operation->Phone Lock.
4
In the “Unlock the Phone?” field, click
.
The phone unlocks dynamically and displays the following message:
“Phone is unlocked”.
41-001160-00, Release 2.1, Rev 04
5-11
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuring a Lock/Unlock Key Using the Configuration Files
Using the configuration files, you can configure a key on the phone (softkey,
programmable key, or expansion module key) to use as a lock/unlock key. In the
configuration files, you assign the function of the key as “phonelock”.
Use the following procedure to configure a key as a lock/unlock key using
the configuration files.
Configuration Files
To configure a softkey/programmable key as a lock/unlock key using the configuration files, see Appendix A,
the section, “Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
5-12
Reference
To use the lock/unlock softkey or programmable key, see “Using the Configured
Lock/Unlock Key on the IP Phone” on page 5-14.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring a Lock/Unlock Key using the Aastra Web UI
Use the following procedure to configure a key as a lock/unlock key using the
Aastra Web UI.
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Note: Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
Select a key you want to configure for locking/unlocking the phone.
41-001160-00, Release 2.1, Rev 04
5-13
Operational IP Phone Features
Using the Aastra Web UI, you can configure a key on the phone (softkey,
programmable key, expansion module key) to use as a lock/unlock key. In the
Aastra Web UI, you assign the function of the as “Phone Lock”.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
3
In the “Type” field, select Phone Lock from the list of options.
4
Click
to save your changes.
Using the Configured Lock/Unlock Key on the IP Phone
After configuring a key as a lock/unlock key, refer to the following procedure to
use the key on the IP phone.
IP Phone UI
Step
Action
Lock the phone:
1
Press the LOCK softkey.
The phone locks.
The LED for the softkey AND the Message Waiting Lamp illuminate steady ON.
An “Unlock” label appears next to the softkey you just pressed.
Unlock the phone:
1
Press the UNLOCK softkey.
A password prompt displays.
2
5-14
Enter the user or administrator password and press ENTER.
The phone unlocks.
The LED for the softkey AND the Message Waiting Lamp go OFF.
The “Lock” label appears next to the softkey you just pressed.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Defining an Emergency Dial Plan
You can specify the digits to dial on the IP phone for contacting emergency
services. Once you specify the emergency number(s) on the phone, you can dial
those numbers directly on the dial pad when required and the phone automatically
dials to those emergency services.
Note: Contact your local phone service provider for available emergency
numbers in your area.
The following table describes the default emergency numbers on the IP phones.
Emergency Number
Description
911
A United States emergency number
999
A United Kingdom emergency number
112
An international emergency telephone
number for GSM mobile phone networks.
In all European Union countries it is also the
emergency telephone number for both
mobile and fixed-line telephones.
110
A police and/or fire emergency number in
Asia, Europe, Middle East, and South
America.
You can set the emergency dial plan via the configuration files or the Aastra Web
UI.
41-001160-00, Release 2.1, Rev 04
5-15
Operational IP Phone Features
Public telephone networks in countries around the world have a single emergency
telephone number (emergency services number), that allows a caller to contact
local emergency services for assistance when required. The emergency telephone
number may differ from country to country. It is typically a three-digit number so
that it can be easily remembered and dialed quickly. Some countries have a
different emergency number for each of the different emergency services.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuring an Emergency Dial Plan
Use the following procedures to specify the numbers to use on your phone for
dialing emergency services in your area.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Emergency Dial
Plan Settings” on page A-11.
Aastra Web UI
1
Click on Operation->Phone Lock.
2
In the “Emergency Dial Plan” field, enter the 3-digit number used in your local area to contact emergency services. For multiple numbers, enter a “|” between each emergency number.
For example:
911|110.
Default for this field is 911|999|112|110.
3
5-16
Click
to save the emergency dial plan to your phone.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Time and Date
Feature
Method of configuration
Set Time
IP Phone UI
Set Time Format
Configuration Files
IP Phone UI
Aastra Web UI
Set Date
IP Phone UI
Set Date Format
Configuration Files
IP Phone UI
Aastra Web UI
Set Time Zone
IP Phone UI
Configuration Files
Set Daylight Savings Time
IP Phone UI
Configuration Files
Daylight Savings Time (DST) Information
The Aastra IP Phones incorporate the federally mandated DST observance
change. This change became affective starting in 2007.
The US has made a change to its daylight savings time observance starting in
2007. The Energy Policy Act of 2005 mandates that DST will now begin at 2:00
A.M. on the second Sunday in March and revert to Standard time on the first
Sunday in November.
Note: In previous years, the DST began on the first Sunday of April and
ended on the first Sunday of October.
The changes to daylight savings time applies to the U.S. and Canada, but may
impact other countries outside North America.
41-001160-00, Release 2.1, Rev 04
5-17
Operational IP Phone Features
In addition to enabling/disabling the time server, you can also set the time and
date, set the time and date format, set the time zone, and set daylight savings time
on the IP phones. You configure these features using the configuration files, the IP
Phone UI, or the Aastra Web UI. The following table identifies which method of
configuration applies to each feature.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Use the following procedures to set a time and date, time and date format, time
zone, and daylight savings time on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Time and Date
Settings” on page A-33.
IP Phone UI
Step
Action
1
Press
on the phone to enter the Options List.
Set Time and Time Format:
2
Select Time and Date.
3
Select Set Time.
4
Using the keys on the keypad, enter a time to set on the IP phone.
5
Press Done to save the time you entered.
6
Select Time Format.
Valid values are 12hr and 24hr.
Note: The default Time Format is 12hr.
7
Press Change to toggle between 24hr and 12hr format.
8
Press Done to save the Time Format you selected.
Set Date and Date Format:
9
Select Set Date.
10
Using the keys on the keypad, enter a date to set on the IP phone.
11
Press Done to save the date you entered.
12
Select Date Format.
5-18
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
13
Select a date format from the list of options.
Valid values are:
• WWW MMM DD (default)
• DD-MMM-YY
• YYYY-MM-DD
• DD/MM/YYYY
• DD/MM/YY
• DD-MM-YY
• MM/DD/YY
• MMM DD
Operational IP Phone Features
IP Phone UI
Note: The default Date Format is WWW MMM DD (Day of Week, Month, Day).
14
Press Done to save the Date Format.
Set Time Zone:
15
Select Time Zone.
16
For 53i:
Press * to display a list of Time Zone options.
17
Select a Time Zone from the list of options.
For valid values, see Appendix A, the section, “Time and Date Settings” on page A-33.
Note: The default Time Zone is US-Eastern.
18
Press Done to save the Time Zone you selected.
Set Daylight Savings Time:
19
Select Daylight Savings.
20
Select a Daylight Savings time from the list of options.
Valid values are:
• OFF
• 30 min summertime
• 1 hr summertime
• automatic
Note: The default for Daylight Savings is Automatic.
21
Press Done to save the Daylight Savings value you selected.
41-001160-00, Release 2.1, Rev 04
5-19
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences->Time and Date Setting.
2
In the “Time Format” field, select the time format you want to use on your phone. Valid values are:
• 12h (12 hour format) (default)
• 24h (24 hour format).
Note: The time displays on the phone’s idle screen in the format you select for this field.
3
In the “Date Format” field, select the date format you want to use on your phone. Valid values are:
• WWW MMM DD (default)
• DD-MMM-YY
• YYYY-MM-DD
• DD/MM/YYYY
• DD/MM/YY
• DD-MM-YY
• MM/DD/YY
• MMM DD
Note: The date displays on the phone’s idle screen in the format you select for this field.
4
5-20
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Language
•
English (default)
•
French
•
Spanish
•
German (not applicable to 57i CT cordless handset)
•
Italian (not applicable to 57i CT cordless handset)
Loading Language Packs
You make languages available to use on the phone by loading language packs
from the configuration server to the local <mac>.cfg configuration file. You can
use the configuration files or the Aastra Web UI to perform the download. Each
language pack consists of the IP Phone UI and Aastra Web UI translated in a
specific language.
Loading Language Packs via the Configuration File (<mac>.cfg)
Using the configuration files, you specify a language pack to load in the following
format:
lang_<ISO 639>-<ISO 3166>.txt
or
lang_<ISO 639>.txt
where <ISO 639> is the language code specified in Standard ISO 639
(see Appendix A, the section, Language Codes (from Standard ISO 639) on
page A-111) and <ISO 3166> is the country code specified in Standard ISO 3166
(see Country Codes (from Standard ISO 3166) on page A-111).
The <ISO 3166> attribute is optional.
Note: Adding/changing language packs can only be done at bootup of the
IP phone. The default language (English) cannot be changed or removed.
41-001160-00, Release 2.1, Rev 04
5-21
Operational IP Phone Features
The IP phones support several different languages. You can have the IP phone UI
and the Aastra Web UI display in a specific language as required. When you set
the language to use, all of the display screens (menus, services, options,
configuration parameters, etc.) display in that language. The IP phones support
the following languages:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Example
5-22
The following is an example of the parameters you would enter in the
<mac>.cfg file to load a French, Italian, German, and Spanish language
pack to the IP phone.
language
language
language
language
1:
2:
3:
4:
lang_fr_ca.txt
lang_it.txt
lang_de.txt
lang_es_mx.txt
The above entries in the <mac>.cfg file tells the phone which language
packs to load. When the language pack(s) have loaded, you must then use
the configuration files IP Phone UI to specify which language to display on
the IP phone. You must use the Aastra Web UI to specify the language to
use in the Web UI.
For more information about specifying the language to use, see the section,
“Specifying the Language to Use” on page 5-24.
For more information about language codes and country codes, see
Appendix A, the section, “Language Pack Settings” on page A-110.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Loading Language Packs via the Aastra Web UI
You use the following fields in the Aastra Web UI to specify which language
packs to load:
Once the language pack is loaded to the phone, it is available for selection from
either the configuration files, the IP Phone UI or the Aastra Web UI.
41-001160-00, Release 2.1, Rev 04
5-23
Operational IP Phone Features
Using the Aastra Web UI, you can specify a language pack to load using the
parameters at Basic Settings->Preferences->Language Settings.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Specifying the Language to Use
Once the language pack(s) have loaded, you must then specify which language to
use on the phone. After the phone has booted up, you can specify which
language(s) to use. You can use the configuration files and the IP Phone UI to
specify the language for the IP Phone UI. You can use the Aastra Web UI to
specify the files for the Aastra Web UI.
Use the following procedures to specify the language to use on the IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Language
Settings” on page A-109 and “Language Pack Settings” on page A-110.
5-24
Notes:
1.
If you specify the language to use on the phone via the
configuration files, you must reboot the phone for the changes to take
affect.
2.
All languages may not be available for selection. The available
languages are dependant on the language packs currently loaded to the IP
phone.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
1
Press
2
Select Language.
3
Select English (English), Français (French), Español (Spanish), Deutsch (German), Italiano
(Italian).
on the phone to enter the Options List.
Notes:
1. Valid values for the 57i CT are English, French, and Spanish only.
2. All languages may not be available for selection. The available languages are dependant on the
language packs currently loaded to the IP phone. English is the default language and cannot be
changed or removed. For more information about loading language packs, see “Loading Language
Packs” on page 5-21.
4
Press Done to save the changes.
The change is dynamic. The IP phone UI displays all menu items in the language you chose.
41-001160-00, Release 2.1, Rev 04
5-25
Operational IP Phone Features
IP Phone UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences->Language Settings.
Loading the Language Pack
2
In the “Language N” fields, enter the file name of the language pack you want to use to display a
specific language in the Aastra Web UI. For example, you could enter the following in the
“Language 1”, “Language 2”, “Language 3”, and “Language 4” fields to display the Aastra Web UI in
French, Spanish, German, and Italian:
lang_fr-ca.txt
lang_es.txt
lang_de.txt
lang_it.txt
Note: You must have the language pack(s) already loaded to your phone in order to use them. For
more information about loading language packs, see “Loading Language Packs” on page 5-21.
For more information about language codes and country codes, see Appendix A, the section,
“Language Pack Settings” on page A-110.
3
Click
to save your changes.
Specifying the Language to Use in the Aastra Web UI
4
After restarting your phone, log back in using the Aastra Web UI.
5
Click on Basic Settings->Preferences->Language Settings.
5-26
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
6
In the “Webpage Language” field, select a language to apply to the Aastra Web UI. The IP phone
supports the following languages:
•
•
•
•
•
English (default)
French (Canadian)
Spanish (Mexican)
German
Italian
Notes:
1. Valid values for the 57i CT are English, French, and Spanish only.
2. All languages may not be available for selection. The available languages are dependant on the
language packs currently loaded to the IP phone. English is the default language and cannot be
changed or removed.
7
Click
to save your changes.
The Aastra Web UI displays all screens in the language you chose.
41-001160-00, Release 2.1, Rev 04
5-27
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Locking IP Phone Keys
The IP phones allow you to lock or unlock programmable keys, softkeys, hard
keys, cordless handset keys, and expansion keys (for expansion modules). When
key locking is enabled, the phone uses the server settings and ignores any
previous local configuration. A user cannot override the configuration of a locked
key.
You can lock and unlock keys using the configuration files, the IP Phone UI, or
the Aastra Web UI. When viewing the locked key via the Aastra Web UI, the key
is grayed out (disabled) and cannot be changed. Locking is dynamic for XML
pushes.
You use the following “locking” parameters in the configuration files to lock the
softkeys and programmable keys on the 53i, 55i, 57i, and 57i CT. The locking
parameters impact existing softkey and programmable key parameters as shown
in the table below.
Locking Parameter
Impacted Parameters
Phone Model Affected
softkeyN locked
softkeyN type
softkeyN label
softkeyN value
softkeyN line
softkeyN states
55i
57i
57i CT
topsoftkeyN locked
topsoftkeyN type
topsoftkeyN label
topsoftkeyN value
topsoftkeyN line
57i
57i CT
prgkeyN locked
prgkeyN type
prgkeyN value
prgkeyN line
53i
55i
featurekeyN locked
featurekeyN type
featurekeyN label
57i CT
expmodX keyN locked
expmodX keyN type
expmodX keyN value
expmodX keyN line
5-series expansion modules
5-28
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Locking the IP Phone Keys
Use the following procedures to lock the softkeys and programmable keys on the
IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Locking Softkeys and Programmable Keys” on page A-163.
Reference
For more information about locking/unlocking the phones using the Phone UI and
Aastra Web UI, see your applicable phone-specific User Guide.
41-001160-00, Release 2.1, Rev 04
5-29
Operational IP Phone Features
Note: The 53i IP phone prevents users from setting a speed dial key via
the Phone UI on a key that has been locked.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Local Dial Plan
5-30
A dial plan describes the number and pattern of digits that a user dials to reach a
particular telephone number. Access codes, area codes, specialized codes, and
combinations of the number of digits dialed are all part of a dial plan. For
instance, the North American Public Switched Telephone Network (PSTN) uses a
10-digit dial plan that includes a 3-digit area code and a 7-digit telephone number.
Most PBXs support variable length dial plans that use 3 to 11 digits. Dial plans
must comply with the telephone networks to which they connect. Only totally
private voice networks that are not linked to the PSTN or to other PBXs can use
any dial plan.
The IP phones have local dial plan capacity. You configure the SIP Local Dial
Plan using the Aastra Web UI or the configuration files.
The IP phone SIP local dial plan available symbols are as follows:
Symbol
Description
0, 1, 2, 3, 4, 5, 6, 7, 8, 9
Digit symbol
X
Match any digit symbol (wildcard)
*, #, .
Other keypad symbol
|
Expression inclusive OR
+
0 or more of the preceding digit symbol or [] expression
[]
Symbol inclusive OR
-
Used only with [], represent a range of acceptable symbols;
For example, [2-8]
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Dial Plan Example
[01]XXX|[2-8]XXXX|91XXXXXX
XXXX|X+.|*XX
The dial plan in the above example can accept any 4-digit dial strings that begin
with a '0' or '1', any 5-digit dial strings that begin with a '2' up to '8', any 12-digit
dial strings that begin with '91', any non-empty digit string that ends with a '.' or
any 2-digit code that begins with a '*'.
Prefix Dialing
The IP phones support a prefix dialing feature for outgoing calls.
You can manually dial a number or dial a number from a list. The phone
automatically maps the pre-configured prepended digit in the configuration, to the
outgoing number. When a match is found, the prepended digits are added to the
beginning of the dial string and the call is dialed.
Note: The prepend digits are also added if the dialing times-out on a
partial match.
You can enable this feature by adding a prepend digit(s) to the end of the Local
Dial Plan parameter string in the configuration files or the Aastra Web UI at
Basic Settings->Preferences->General.
For example, if you add a prepend map of “[2-9]XXXXXXXXX,91”, the IP
phone adds the digits “91” to any 10-digit number beginning with any digit from 2
to 9 that is dialed out. Other examples of prepend mappings are:
•
1X+#,9 (Prepends 9 to any digit string beginning with “1” and terminated
with “#”.)
•
6XXX,579 (Prepends “579” to any 4-digit string starting with “6”.)
•
[4-6]XXXXXX,78 (Prepends “78” to any 7-digit string starting with “4”, “5”, or “6”.)
Note: You can configure a local dial plan via the configuration files or
the Aastra Web UI.
41-001160-00, Release 2.1, Rev 04
5-31
Operational IP Phone Features
An example of a SIP Local Dial Plan is:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Example
5-32
If you enter the following dial string for a local dial plan:
sip dial plan: 1+#,9
where “9” is the prepended digit, and you dial the following number:
15551212
the IP phone automatically adds the “9” digit to the beginning of the dialed
number before the number is forwarded as 915551212.
Note: You can configure a local dial plan via the configuration files or
the Aastra Web UI.
SIP Dial Plan Terminator
The IP phone allows you to enable or disable the use of the “dial plan terminator”.
When you configure the phone’s dial plan to use a dial plan terminator or timeout
(such as the pound symbol (#)) the phone waits 4 or 5 seconds after you pick up
the handset or after you finish dialing the numbers on the keypad before making
the call.
You can enable or disable the dial plan terminator using Aastra Web UI or the
configuration files.
Digit Timeout
The IP phone allows you to configure a “Digit Timeout” feature on the IP phone.
The Digit Timeout is the time, in seconds, between consecutive key presses on the
IP phone’s keypad. The default for this parameter is 4 seconds. If you press a key
on the phone and wait 4 seconds before pressing the next key, the key times out
and cancels the digit selection. You must press consecutive keys before the
timeout occurs.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedures to configure the SIP Local Dial Plan using the
configuration files or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “SIP Local Dial
Plan Settings” on page A-39.
Aastra Web UI
1
Click on Basic Settings->Preferences.
2
In the "Local Dial Plan" field, enter a valid local dial plan (up to 127 alphanumeric characters) for the
IP phone. Default is X+#|XX+*. Enter prepended digits as required.
3
Enable the "Send Dial Plan Terminator" field by checking the check box. (Disable this field by
unchecking the box). Default is disabled.
41-001160-00, Release 2.1, Rev 04
5-33
Operational IP Phone Features
Configuring the SIP Local Dial Plan, Dial Plan Terminator, and Digit
Timeout
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
4
In the "Digit Timeout (in seconds)" field, enter a timeout value. This is the length of time, in
seconds, he phone waits before dialing. Default is 4 seconds.
5
Click
5-34
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Park Calls/Pick Up Parked Calls
•
Using a static configuration (globally configures park and pickup)
•
Using a programmable configuration
Note: The IP phones accept both methods of configuration. However, to
avoid redundancy, Aastra Telecom recommends you configure either a
static configuration or a programmable configuration.
The IP phones support the Park/Pickup feature on the Asterisk, BroadWorks,
Sylantro, and ININ PBX servers.
The following paragraph describes the park and pickup static configuration on the
IP phones.
Reference
For information on configuring the park and pickup programmable configuration
(using a key), see “Park/Pick Up Key” on page 5-153.
Park/Pickup Static Configuration (55i, 57i, 57i CT only)
Using the static method of configuring park and pickup configures these features
on a global basis for all IP phones connected in the network. You can use the
configuration files or the Aastra Web UI to configure a park/pickup static
configuration.
In the configuration files, you use the following parameters to statically configure
park/pickup:
•
sprecode:
•
pickupsprecode:
41-001160-00, Release 2.1, Rev 04
5-35
Operational IP Phone Features
The IP phones (including the 57i CT handset) have a park and pickup call feature
that allows you to park a call and pickup a call when required. There are two ways
a user or administrator can configure this feature:
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
In the Aastra Web UI, you use the following fields at Basic Settings->
Preferences to configure park/pickup statically:
•
Park Call
•
Pickup Call
How It displays on the Phone
On the IP phone UI, the static configuration method displays the following:
•
When a call comes in, and you pickup the handset, the default label of "Park"
displays on the first screen of the Phone UI.
•
After pressing the "Park" softkey to park the call, the default label of
"Pickup" displays on the first screen of the phone UI.
Note: On the 57i CT handset, pressing Ï displays the "Park" and
"Pickup" labels.
The values you enter for the Park/Pickup feature are dependant on your type of
server. The following table provides the values you enter for the “sprecode” and
“pickupsprecode” parameters (configuration files), or "Park Call" and "Pickup
Parked Call" fields (Aastra Web UI).
Park/Pickup Call Server Configuration Values
Server
Park Values*
Pickup Values*
Aasterisk
70
70
Sylantro
*98
*99
BroadWorks
*68
*88
callpark
pickup
ININ PBX
*Leave "value" fields blank to disable the park and pickup feature.
5-36
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedures to configure the Park/Pickup call feature using the
static configuration method.
Note: Aastra recommends you configure either the static or the
programmable configuration, but not both.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Park and Pickup Global Settings (57i/57i CT only)” on page A-132.
41-001160-00, Release 2.1, Rev 04
5-37
Operational IP Phone Features
Configuring Park /Pickup using Static Configuration
(55i, 57i, 57i CT only)
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
Enter a server value in the Park Call field to which incoming live calls will be parked.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-36.
3
Enter a server value in the "Pickup Parked Call" field.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-36.
4
5-38
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Suppressing DTMF Playback
When suppression of DTMF playback is disabled, 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 the suppression of DTMF playback is enabled, the IP phone dials the stored
number and displays the entire number immediately in the LCD window, allowing
the call to be dialed much faster.
DTMF playback suppression is disabled by default. Suppressing DTMF playback
can be configured using the Aastra Web UI and the configuration files.
Configuring Suppression of DTMF Playback
Use the following procedures to configure the suppression of DTMF playback on
the IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Suppress DTMF
Playback Setting” on page A-119.
41-001160-00, Release 2.1, Rev 04
5-39
Operational IP Phone Features
A feature on the IP phones allows users and administrators to enable or disable the
suppression of DTMF playback when a number is dialed from the softkeys and
programmable keys.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
Enable the "Suppress DTMF Playback" field by checking the check box.
(Disable this field by unchecking the box). Default is disabled.
3
Click
to save your settings.
You must restart your IP phone for the changes to take affect.
4
Click on Operation->Reset.
5
In the "Restart Phone" field click
5-40
to restart the IP phone and apply the changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Display DTMF Digits
DTMF is the signal sent from the phone to the network that you generate when
you press the phone’s touch keys. This is also known as “touchtone” dialing. Each
key you press on your phone generates two tones of specific frequencies. One
tone is generated from a high-frequency group of tones and the other from a low
frequency group.
If you enable the Display DTMF Digits parameter, the digits you are dialing from
the keypad or from a softkey or programmable key display to the IP phone’s LCD
display. This parameter is disabled by default (no digits display when dialing).
You can enable the “Display DTMF Digits” parameter using the configuration
files or the Aastra Web UI.
Configuring Display DTMF Digits
Use the following procedures to configure the suppression of DTMF playback on
the IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Display DTMF
Digits Setting” on page A-120.
41-001160-00, Release 2.1, Rev 04
5-41
Operational IP Phone Features
A feature on the IP phones allows users and administrators to enable or disable
DTMF (dual-tone multi-frequency) digits to display to the IP phone when using
the keypad to dial, or when dialing from a softkey or programmable key.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
Enable the "Display DTMF Digits" field by checking the check box.
(Disable this field by unchecking the box). Default is disabled.
3
Click
to save your settings.
You must restart your IP phone for the changes to take affect.
4
Click on Operation->Reset.
5
In the "Restart Phone" field click
5-42
to restart the IP phone and apply the changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Call Waiting/Call Waiting Tone
If you disable call waiting on the phone, and the user is on a call, any further
incoming calls will receive busy unless “Call Forward Busy” or “Call Forward No
Answer and Busy” is configured on the phone. It will then forward the call
according to the rule configured. The phone can only:
•
transfer the currently active call
or
•
accept transferred calls if there is no active calls.
If call waiting is disabled:
•
on the 57i CT bases, and the handset is currently on a call, all additional
incoming calls are rejected on the handset.
•
intercom calls are treated as regular incoming calls and are rejected.
•
pre-dialing with live dial pad disabled still accepts incoming calls.
•
the “Incoming Call Cancels Dialing” parameter is ignored because the
incoming call is automatically rejected.
•
the Missed Calls List does not get updated with details of calls.
•
the Blind Transfer feature on the phone may not work if two calls are made to
the phone at one time.
You can enable/disable call waiting using the configuration files or the Aastra
Web UI.
41-001160-00, Release 2.1, Rev 04
5-43
Operational IP Phone Features
A call waiting feature notifies the user currently on the phone, of a new incoming
call. You can disable this call waiting feature, so that the new incoming call is
automatically rejected by the phone with a busy message. A User or
Administrator can configure this feature.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Call Waiting Tone
You can also enable or disable the playing of a short “Call Waiting Tone" when
there is an incoming call on your phone. This feature is enabled by default. If you
have Call Waiting enabled, and a call comes into the line for which you are on an
active call, a tone is audible to notify you of that incoming call. The tone is also
audible to the caller to indicate to that caller you are currently on another call.
Note: The Call Waiting Tone feature works only if Call Waiting is
enabled.
A User or Administrator can configure this feature. An Administrator can
configure this feature using the configuration files or the Aastra Web UI.
Configuring Call Waiting/Call Waiting Tone
Use the following procedures to configure the Call Waiting/Call Waiting Tone
features on the IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Call Waiting
Settings” on page A-101.
5-44
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
.
1
Click on Basic Settings-> Preferences->General.
2
The "Call Waiting" field is enabled by default. To disable this field, uncheck the box. This feature
allows you to enable or disable the call waiting feature on the IP phone.
3
The "Play Call Waiting Tone" field is enabled by default. To disable this field, uncheck the box. This
feature allows you to enable or disable the call waiting tone on the IP phone.
Note: The Call Waiting Tone feature works only if the “Call Waiting” tone field is enabled.
4
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-45
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Stuttered Dial Tone
You can enable or disable the playing of a stuttered dial tone when there is a
message waiting on the IP phone.
You can configure this feature using the configuration files and the Aastra Web
UI.
Configuring Stuttered Dial Tone
Use the following procedures to configure stuttered dial tone on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling stuttered dial tone, see
Appendix A, the section, “Stuttered Dial Tone Setting” on page A-100.
5-46
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
The "Stuttered Dial Tone" field is enabled by default. To disable this field, uncheck the box.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-47
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
XML Beep Support
The IP phones have a feature that allows you to enable or disable a beep on the
phone with it receives a status message from an XML application. This beep can
be turned ON or OFF using the Aastra Web UI, the configuration files, or in an
XML script.
Reference
For more information about enabling/disabling the XML Beep Support in an
XML script, see “XML Customized Services” on page 5-196.
Configuring XML Beep Support
Use the following procedures to enable/disable XML Beep Support.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “XML Settings”
on page A-89.
5-48
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
The “XML Beep Support” field is enabled by default. To disable this field, uncheck the box.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-49
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Status Scroll Delay
The IP phones have a feature that allows you to specify the time delay, in seconds,
between the scrolling of each status message (including XML status messages) on
the phone. The default time is 5 seconds for each message to display before
scrolling to the next message. You can configure this option via the configuration
files or the Aastra Web UI.
Reference
For more information about configuring the status scroll delay for XML status
messages, see “XML Customized Services” on page 5-196.
Configuring Status Scroll Delay
Use the following procedures to configure Status Scroll Delay.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “XML Settings”
on page A-89.
5-50
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
In the “Status Scroll Delay (seconds)” field, enter a value, in seconds, that each XML status
message displays on the phone. Default is 5 seconds. Valid values are 1 to 25.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-51
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Incoming Call Interrupts Dialing
You can configure whether or not an incoming call interrupts an outgoing call that
is dialing. The incoming call interrupts dialing parameter controls this feature.
How it Works
When you enable this parameter (1 = enable), an incoming call interrupts the
outgoing call during dialing and allows the phone to ring for the user to answer the
incoming call.
When you disable the “incoming call interrupts dialing” parameter
(0 = disable), which is the default, the phone does not interrupt the outgoing call
during dialing and instead rings the incoming call on another free line (or sends
busy signal if all remaining lines are busy). You have a choice to ignore the
incoming call, or answer the incoming call on another line, via the Ignore and
Answer softkeys that display. If you choose to answer the incoming call, you can
answer the call, finish the call, and then hang up. You can still go back to the
original outgoing call and finish dialing out.
Notes:
1.
On a 53i, you must use the down arrow key to ignore the call. To
answer the call you must press the line key where the call is coming in.
2.
For all models, if you disable this parameter (0=disable), and the
phone receives an incoming call while you are dialing an outgoing call,
you can pick up the call and perform transfer or conference as required.
Configuring Incoming Call Interrupts Dialing
Use the following procedures to configure how the IP phone handles incoming
calls that interrupt outgoing dialing.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling how the IP phones
handle incoming calls that interrupt outgoing dialing, see Appendix A, the section, “Incoming Call Interrupts
Dialing Setting” on page A-98.
5-52
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
Incoming Call Interrupts Dialing is disabled by default.
If required, enable the "Incoming Call Interrupts Dialing" field by checking the check box.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-53
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Goodbye Key Cancels Incoming Call
You can configure the Goodbye key to drop active calls or ignore incoming calls
using the “goodbye cancels incoming call” parameter. This parameter controls
the behavior of the goodbye key when the phone is on an active call and a second
call is presented to the phone.
How it Works
When you enable this parameter (1 = enable in the configuration files), which is
the default, the Goodbye key rejects the incoming call. When you disable this
parameter (0 = disable in the configuration files), the Goodbye key hangs up the
active call.
For the 55i, 57i, and 57i CT:
If you enable this parameter, and the phone receives another call when an active
call is already present, the phone displays softkey 1 as “answer” and softkey 2 as
“ignore”. You can press the required softkey as applicable.
For the 53i:
If you enable this parameter, and the phone receives another call when an active
call is already present, the “ignore” option only displays in the LCD window. The
phone ignores the incoming call. If you press the DOWN arrow key, the phone
answers the incoming call.
You can set this parameter using the configuration files or the Aastra Web UI.
Configuring the Goodbye Key to Cancel Incoming Calls
Use the following procedures to configure the behavior of the Goodbye Key on
the IP phone.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling the behavior of the
Goodbye Key, see Appendix A, the section, “Incoming Call Interrupts Dialing Setting” on page A-98.
5-54
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Basic Settings->Preferences->General.
2
Incoming Call Interrupts Dialing is disabled by default.
If required, enable the "Incoming Call Interrupts Dialing" field by checking the check box.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-55
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
UPnP Mapping Lines (for remote phones)
Universal Plug and Play (UPnP) is a standard that uses Internet protocols to
enable devices to be plugged into a network and automatically know about each
other. With UPnP, when a user plugs a device into the network, the device
configures itself, acquires a TCP IP address, and uses a discovery protocol based
on the Internet's HTTP or HTTPS URL to announce its presence on the network
to other devices.
This method of device discovery on a network is called “Universal Plug and Play”
or UPnP. If you enable UPnP, and the phone is discovered on the network, port
mappings are set up between the phone and the Internet Gateway Device (IGD) in
your network. The phone controls the opening, closing, and polling of ports on the
IGD. HTTP and SIP use a single port each. RTP/RTCP uses a range of ports.
You can enable the UPnP mappings to specific lines on your phone. You set this
configuration using the Aastra Web UI at Basic Settings->Preferences->UPnP
Mapping Lines.
Note: UPnP must be enabled on your remote phone before you can
configure the UPnP mapping lines. For information on enabling/disabling
UPnP see Chapter 4, the section, “Universal Plug and Play (UPnP) (for
remote phones)” on page 4-27.
Configuring UPnP Mapping Lines
Use the following procedures to configure UPnP mapping on specific lines on the
IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “UPnP Settings”
on page A-25.
5-56
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
1
Click on Basic Settings->Preferences->General.
2
The "UPnP Mapping Lines" field is set to 0 by default. If required, change the setting to a specific
line by selecting a line from the list. Valid values are 0 through 10. The line you select is the line that
your remote phone uses to perform Universal Plug and Play on the network you are connecting to.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-57
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Message Waiting Indicator Line
A User or Administrator can configure the Message Waiting Indicator (MWI) to
illuminate for a specific line or for all lines. For example, if you configure the
MWI LED on line 3 only, the LED illuminates if a voice mail is pending on line 3.
If you configure the MWI LED for all lines, the LED illuminates if a voice mail is
pending on any line on the phone (lines 1 through 9).
A User can configure the MWI using the Aastra Web UI only. An Administrator
can configure the MWI on single or all lines using the configuration files or the
Aastra Web UI.
Configuring Message Waiting Indicator (MWI)
Use the following procedures to configure MWI on the IP phone.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Message
Waiting Indicator Settings” on page A-102.
5-58
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
1
Click on Basic Settings-> Preferences->General.
2
In the “Message Waiting Indicator Line” field, select a single line from 1 to 9, or select “All” for all
lines. If you select a single line, the MWI illuminates when a voice mail message is pending on that
line. If you select all lines, the MWI illuminates when a voice mail message is pending on any line
from 1 to 9.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-59
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Incoming/Outgoing Intercom with Auto-Answer and Barge In
The Intercom feature allows you to press the configured Intercom button on the IP
phone and then enter the number you want to call to initiate an intercom call.
Intercom calls can be controlled either locally (phone-side) or by the SIP server
(server-side).
You can configure incoming and outgoing intercom calls on all phone models. A
User can configure incoming intercom calls only.
Outgoing Intercom Calls
On outgoing intercom calls, an available unused line is found when the Icom
button is pressed. Since this line has no configuration, the phone applies an
existing configuration ("Outgoing Intercom Settings", Line, default is Line 1) to
this line in preparation for placing the intercom call. For example, an outgoing
intercom call can use the configuration of line 1 but places the actual intercom call
using line 9. Only an Administrator can configure outgoing intercom calls.
A phone-side Intercom call indicates the phone is responsible for telling the
recipient that an intercom call is being placed, while a server-side intercom call
means the SIP server is responsible for informing the recipient. Server-side calls
require additional configuration of a prefix code. After pressing the Icom button
and entering the number to call, the phone automatically adds the prefix to the
called number and sends the outgoing call via the server.
For outgoing intercom calls, an administrator can configure the following
parameters:
Configuration File Parameters
Web UI Parameters
•
sip intercom type
•
Type)
•
sip intercom prefix code
•
Prefix Code
•
sip intercom line
•
Line
Note: To configure outgoing intercom calls using these parameters, see
“Configuring Intercom Calls Settings” on page 5-62.
5-60
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Incoming Intercom Calls
Microphone Mute
You can mute or unmute the microphone on the IP phone for intercom calls made
by the originating caller. If you want to mute the intercom call, you enable this
feature. If you want to unmute (or hear the intercom call), you disable this feature.
Auto-Answer/Play Warning Tone
The auto-answer feature on the IP phone allows you to enable or disable
automatic answering for an Intercom call. If “Auto-Answer” is enabled, the phone
automatically answers an incoming intercom call. If “Play Warning Tone” is also
enabled, 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.
“Delay” before Auto-Answer
The IP Phones include support for the "delay" parameter (in the Alert-Info header,
used in conjunction with info=alert-autoanswer) in order to facilitate auto-answer
functionality. When present, the value of the "delay" parameter specifies the
length of time in seconds an IP phone rings before a call is auto-answered. If this
value of the "delay" parameter set to 0 (delay=0), then an incoming call is
immediately auto-answered. The absence of the parameter is considered as ring
forever.
In order for the delay functionality to operate, you must first enable Auto-Answer
on the IP Phone.
41-001160-00, Release 2.1, Rev 04
5-61
Operational IP Phone Features
You can configure how the phone handles incoming intercom calls. You can
receive incoming intercom calls whether or not there are active calls on the phone.
The way the phone handles the call depends on the incoming intercom call
configuration. The following paragraphs describe the configuration parameters for
incoming intercom calls.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Allow Barge In
You can configure whether or not the IP phone allows an incoming intercom call
to interrupt an active call. The “sip intercom allow barge in” parameter controls
this feature. When you enable the sip intercom allow barge in parameter
(1 = enable in the configuration files), which is the default value, an incoming
intercom call takes precedence over any active call, by placing the active call on
hold and automatically answering the intercom call. When you disable this
parameter (0 = disable in the configuration files), and there is an active call, the
phone treats an incoming intercom call like a normal call and plays the call
warning tone. You can set this parameter using the configuration files or the
Aastra Web UI.
For incoming intercom calls, an administrator or user can configure the following
parameters:
Configuration File Parameters
Web UI Parameters
•
sip allow auto answer
•
Auto-Answer
•
sip intercom mute mic
•
Microphone Mute
•
sip play warning tone
•
Play Warning Tone
•
sip intercom allow barge in
•
Barge In
Note: To configure incoming intercom calls using these parameters, see
“Configuring Intercom Calls Settings” on page 5-62.
Configuring Intercom Calls Settings
You can configure the Intercom feature using the configuration files or the Aastra
Web UI.
Note: An administrator can configure the incoming and outgoing
Intercom feature. A user can configure the incoming Intercom feature
only.
5-62
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedures to configure Intercom calls on the IP phone.
For specific parameters you can set in the configuration files for outgoing Intercom, see Appendix A, the
section, “Outgoing Intercom Settings” on page A-121.
For specific parameters you can set in the configuration files for incoming Intercom, see Appendix A, the
section, “Incoming Intercom Settings” on page A-123.
Aastra Web UI
Outgoing intercom settings (55i, 57i, and 57i CT only):
1
Click on Basic Settings->Preferences->Outgoing Intercom Settings.
2
Select an Intercom type for outgoing Intercom calls from the Type list box.
Valid values are Phone-Side, Server-Side, Off. Default is Off.
3
If Server-Side is selected, enter a prefix to add to the phone number in the "Prefix Code" field.
Note: For Sylantro servers, enter *96.
41-001160-00, Release 2.1, Rev 04
5-63
Operational IP Phone Features
Configuration Files
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
4
If Phone-Side or Server-Side is selected, select a line from the Line list box for which you want the IP
phone to use as its configuration on the Intercom call.
Note: The IP phone uses the configuration from the line you select from this list box. The call itself is
made using the first available line at the time of the call.
5
Click
to save your changes.
Incoming intercom settings:
1
Click on Basic Settings->Preferences->Incoming Intercom Settings.
2
The "Auto-Answer" field is enabled by default. The automatic answering feature is turned on for the
IP phone for answering Intercom calls. To disable this field, uncheck the box.\
Note: If the Auto-Answer field is not checked (disabled), the phone rejects the incoming intercom call
and sends a busy signal to the caller.
5-64
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
3
The "Microphone Mute" field is enabled by default. The microphone is muted on the IP phone for
Intercom calls made by the originating caller. To disable this field, uncheck the box.
4
The "Play Warning Tone" field is enabled by default. If “Auto-Answer” is enabled, the phone plays a
warning tone when it receives in incoming intercom call. To disable this field, uncheck the box.
5
The "Allow Barge In" field is enabled by default. If an active line on the phone receives an incoming
intercom call, the active call is put on hold and the phone automatically answers the incoming
intercom call. To disable this field, uncheck the box.
6
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-65
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Key Mapping
There are hard keys on your phone, such as Hold, Redial, Xfer, and Conf that are
configured by default for specific call-handling features. (See the product-specific
User Guide for more information about these key functions.
Notes:
1.
On the 55i and 57i, the Xfer and Conf keys are hard-coded by
default on keys 5 and 6 to the left of the LCD display
and cannot be reassigned. The Xfer and Conf labels display
when you lift the handset. To disable these keys, see the next
paragraph.
2.
On the 53i, the Xfer and Conf keys are assigned by default to keys
5 and 6, respectively. These keys are programmable keys and can
be reassigned if applicable. To disable these keys, see the
next paragraph.
Enabling/Disabling Redial, Xfer, and Conf Keys
You can enable or disable the Redial, Xfer, and Conf keys as required using the
following parameters in the configuration files:
•
redial disabled
•
conference disabled
•
call transfer disabled
Valid values for this parameter are 0 (enabled) and 1 (disabled).
If this parameter is set to 1, the key is not active and is ignored if pressed by the
user. For "redial disabled" the value of 1 does not save the dialed number to the
"Redial List".
If this parameter is set to 0, the key is active and can be pressed by the user.
This feature is configurable via the configuration files only.
5-66
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedure to enable/disable the Redial, Xfer, and Conf keys.
For specific parameters you can set in the configuration files, see Appendix A, the section, “Mapping Key
Parameters” on page A-133.
Mapping Redial and Conf Keys as Speeddials
You can map the Redial and Conference keys on the IP phone to use as speeddial
keys. When the Redial or Conference key is pressed, the number configured for
the key automatically speed dials. If no number is configured, the Redial and
Conference keys return to their original functionality.
You can configure this feature using the configuration files or the Aastra Web UI.
Note: If you configure the Redial and Conference keys for speeddialing
on the 57i CT Base Station, the Redial and Conference keys on the
57i CT handset retain their original functionality. The Redial and
Conference keys on the handset are not configured for speeddial.
Use the following procedures to set the Redial and Conf keys as speeddial keys.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Mapping Key
Parameters” on page A-133.
41-001160-00, Release 2.1, Rev 04
5-67
Operational IP Phone Features
Configuration Files
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences.
2
In the Key Mapping section, enter a number in the "Map Redial Key To" field, that the IP phone will
use to speeddial when the Redial key is pressed.
3
Enter a number in the "Map Conf Key To" field, that the IP phone will use to speeddial when the
Conf Key is pressed.
4
Click
5-68
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Using Redial Key for “Last Number Redial”
Operational IP Phone Features
The IP phones have an enhanced redial user interface that allows a user to
quickly redial the last number that was dialed out from the phone. You can:
•
Press the REDIAL key twice to redial the last number dialed.
•
Press the REDIAL key once, scroll the list of numbers, then press the
REDIAL button again to dial the number that displays on the screen.
The “last number redial” feature for the Redial key is static and is not
configurable.
Note: You can use the Redial key during active calls.
41-001160-00, Release 2.1, Rev 04
5-69
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Ring Tones and Tone Sets
You can configure ring tones and ring tone sets on the IP phones.
Ring Tones
There are several distinct ring tones a user or administrator can select from to set
on the IP phones. You can enable/disable these ring tones on a global basis or on a
per-line basis.
The following table identifies the valid settings and default values for each type of
configuration method.
Ring Tone Settings Table
Configuration Method
Configuration Files
IP Phone UI
5-70
Valid Values
Default Value
Global:
0 (Tone1)
1 (Tone 2)
2 (Tone 3)
3 (Tone 4)
4 (Tone 5)
5 (Silent)
Global:
0 (tone 1)
Per-Line:
-1 (global)
0 (Tone1)
1 (Tone 2)
2 (Tone 3)
3 (Tone 4)
4 (Tone 5)
5 (Silent)
Per-Line:
-1 (global)
Global:
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Global:
Tone 1
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuration Method
Default Value
Global:
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Silent
Global:
Tone 1
Per-Line:
Global
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Silent
Per-Line:
Global
41-001160-00, Release 2.1, Rev 04
Operational IP Phone Features
Aastra Web UI
Valid Values
5-71
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Ring Tone Sets
5-72
In addition to ring tones, you can configure ring tone sets on a global-basis on the
IP phones. Ring tone sets consist of tones customized for a specific country. The
ring tone sets you can configure on the IP phones are:
•
US (Default - also used in Canada)
•
Australia
•
Europe (generic tones)
•
France
•
Germany
•
Italy
•
Mexico
•
United Kingdom (UK)
When you configure the country's tone set, the country-specific tone is heard on
the phone for the following:
- dial tone
- secondary dial tone
- ring tone
- busy tone
- congestion tones
- call waiting tone
- ring cadence pattern
You configure ring tones and tone sets using the Aastra Web UI, IP Phone UI, or
configuration files. However, when using the IP phone UI, you can set global
configuration only.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Ring Tones and Tone Sets
Configuration Files
For specific parameters you can set in the configuration files for ring tones, see Appendix A, the section,
“Ring Tone and Tone Set Global Settings” on page A-94 or “Ring Tone Per-Line Settings” on page A-97.
IP Phone UI
Step
Action
For global configuration only:
1
Press
on the phone to enter the Options List.
2
Select Preferences.
3
Select Tones.
4
Select Set Ring Tone.
5
Select the type of ring tone (Tone 1 through Tone 5, or Silent).
6
Press Done to save the change.
7
Select Tone Set.
8
Select the country for which you want to apply the tone set.
Valid values are Australia, Europe, France, Germany, Italy, Mexico, UK, and US. Default is US.
9
Press Done to save the change.
The ring tone and tone set you select is immediately applied to the IP phone.
41-001160-00, Release 2.1, Rev 04
5-73
Operational IP Phone Features
Use the following procedures to configure ring tones and tone sets on the IP
phones.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Preferences.
For global configuration:
2
In the "Ring Tones" section, select a country from the "Tone Set" field.
Valid values are Australia, Europe, France, Germany, Italy, Mexico, UK, and US. Default is US.
3
Select a value from the "Global Ring Tone" field.
Note: See the “Ring Tone Settings Table” on page 5-70 for valid values.
For per-line configuration:
4
In the "Ring Tone" section, select a line for which you want to set ring tone.
5
Select a value from the "LineN" field.
Note: See the “Ring Tone Settings Table” on page 5-70 for valid values.
6
5-74
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Priority Alerting
You can enable or disable priority alerting on the IP phone for the Asterisk,
Broadworks, and Sylantro servers using the configuration files and the Aastra
Web UI. Configuration of priority alerting is on a global-basis only.
How Priority Alerting Works
When the IP phone detects an incoming call, the phone firmware inspects the
INVITE request in the IP packet for an "Alert-Info" header.
If it contains an "Alert-Info" header, the firmware strips out the URL and keyword
parameter and maps it to the appropriate Bellcore tone.
If there is no keyword parameter in the "Alert-Info" header, or the INVITE
message contains no "Alert-Info" header, then the IP phone firmware uses the
Bellcore standard ring tone.
Asterisk/Broadworks Servers
The ring tone keywords that can display in the "Alert-Info" header for an Asterisk
and Broadworks server are:
Asterisk/Broadworks Server
Ring Tone Keywords
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
When the ring tone keywords appear in an "Alert-Info" header from an Asterisk or
Broadworks server, the IP phone maps the keywords to the default ring tone
patterns.
41-001160-00, Release 2.1, Rev 04
5-75
Operational IP Phone Features
Priority alerting on the IP phones is a feature that allows incoming calls to trigger
pre-defined ringing or call waiting alert tones.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Sylantro Servers
5-76
The ring tone keywords that can display in the "Alert-Info" header for a Sylantro
server are:
Sylantro Server
Ring Tone Keywords
alert-acd (auto call distribution)
alert-community-1
alert-community-2
alert-community-3
alert-community-4
alert-emergency
alert-external
alert-group
alert-internal
alert-priority
When the ring tone keywords appear in an "Alert-Info" header from a Sylantro
server, the keyword is mapped to the ring tone pattern based on the configuration
you set in the Aastra Web UI or the configuration files.
Ring Tone Patterns
In IP Telephony, different ringing patterns have different frequencies and
cadences. Ring cadence is the ringing pattern heard by the called party, before
they pick up the call.
On the IP phones, if you enable priority alerting when using an Asterisk or
Broadworks server, the IP phone uses the following Bellcore-specified tones by
default:
Ring Tone Pattern (Asterisk/Broadworks Servers)
Call Criteria
Bellcore Tones
internal calls
Bellcore-dr2
external calls
Bellcore-dr3
calls with contact list
Bellcore-dr4
calls with specific time frames
Bellcore-dr5
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Ring Tone Pattern (Sylantro Servers)
Call criteria
Bellcore tones for each call criteria
alert-acd (auto call distribution)
alert-community-1
alert-community-2
alert-community-3
alert-community-4
alert-emergency
alert-external
alert-group
alert-internal
alert-priority
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
The following table identifies the different Bellcore ring tone patterns and
cadences.
Cadence
Minimum
Duration
(ms)
Nominal
Duration
(ms)
Maximum
Duration
(ms)
Ringing
Silent
2s On
4s Off
1800
3600
2000
4000
2200
4400
Ringing
Silent
Long
630
315
800
400
1025
525
Ringing
Silent
Long
Long
630
3475
800
4000
1025
4400
Ringing
Silent
Short
315
145
400
200
525
525
Ringing
Silent
Short
315
145
400
200
525
525
Ringing
Silent
Long
630
2975
800
4000
1025
4400
Ringing
Silent
Short
200
145
300
200
525
525
Ringing
Silent
Long
800
145
1000
200
1100
525
Ringing
Silent
Short
200
2975
300
4000
525
4400
450
500
550
Pattern
ID
Pattern
(Standard)
1
Bellcore-dr2
2
Bellcore Tone
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
3
4
5
41-001160-00, Release 2.1, Rev 04
Ringing
5-77
Operational IP Phone Features
If you enable priority alerting when using a Sylantro server, you can specify the
Bellcore tone to be used for the following configurable criteria:
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Note: If the "Do Not Disturb" (DND) or the "Call Forward" (CFWD)
feature is enabled on the server-side, and the user is still waiting for a call,
the "Bellcore-dr5" is a ring splash tone that reminds the user that these are
enabled.
Call Waiting Tones
Call Waiting is a feature that tells you if a new caller is trying to contact you when
you are already on the phone.
A discreet tone alerts you to the new caller, so you can answer your second
incoming call by putting your first caller on hold.
The IP phones use the following Bellcore-specified call waiting tones.
Bellcore
Call-Waiting Tone
Pattern
ID
Pattern
Minimum
Duration
(ms)
Nominal
Duration
(ms)
Maximum
Duration
(ms)
CallWaitingTone 1
1
Tone On
270
300
330
Bellcore-dr2
CallWaitingTone2
2
Tone On
Tone Off
90
90
100
100
110
110
Bellcore-dr3
CallWaitingTone3
3
Tone On
Tone Off
90
90
100
100
110
110
Tone On
Tone Off
Tone On
Tone Off
90
90
90
90
100
100
100
100
110
110
110
110
Tone On
Tone Off
270
90
300
100
330
110
Bellcore-dr4
CallWaitingTone4
4
For Asterisk and Broadworks servers, call waiting tones are specified by the
default Bellcore tones indicated in the table Ring Tone Pattern (Asterisk/
Broadworks Servers) on page 76.
For Sylantro servers, call waiting tones are specified by the Bellcore tones you
configure in the Aastra Web UI or the configuration files. See the table Ring Tone
Pattern (Sylantro Servers) on page 77.
5-78
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Priority Alerting
Operational IP Phone Features
Use the following procedures to configure priority alerting on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files for priority alerting, see Appendix A, the
section, “Priority Alert Settings” on page A-103.
Aastra Web UI
1
Click on Basic Settings->Preferences.
2
In the "Priority Alerting Settings" section, enable the "Enable Priority Alerting" field by checking the
check box. (Disable this field by unchecking the box).
41-001160-00, Release 2.1, Rev 04
5-79
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For Sylantro Servers:
3
Select a ring tone pattern for each of the following fields:
•
•
•
•
•
•
•
•
•
•
4
5-80
Group
Internal
External
Emergency
Priority
auto call distribution
community-1
community-2
community-3
community-4
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Directed Call Pickup (BLF or XML Call Interception)
•
With the existing BLF feature on Asterisk, a user can dial “*76” followed by
the extension to pick up a ringing call on another phone. (For more
information about BLF, see “Busy Lamp Field (BLF)” on page 114
•
Using XML, a user can intercept a call by selecting an extension from a list
and then pressing a “Pickup” softkey/programmable key. To use the Directed
call pickup feature from an XML application, you must list all ringing
extensions using the AastraIPPhoneTextMenu XML object in an XML
script. This allows the user to select the ringing extension from a text menu
without having to dial. The following illustration shows an example of how
this feature displays to the LCD from an XML application.:
Ringing Extensions
201
212
225
234
Pickup
Done
(For more information about using the AastraIPPhoneTextMenu object, see
Appendix G, the section, “Text Menu Object (Menu Screens)” on page G-6.
41-001160-00, Release 2.1, Rev 04
5-81
Operational IP Phone Features
Directed call pickup is a feature on the phones that allows a user to intercept a call
on a ringing phone which is part of the same interception group. You can use the
Directed call pickup feature on the phone in two ways:
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
BLF and XML softkeys/programmable keys monitor the states of an extension.
The extension states can be one of three states: "busy", "ringing" and "idle". If the
monitored extension is in the "ringing" state with an incoming call, and "Directed
call pickup" is enabled, pressing the BLF or XML key can pick up the incoming
call on the monitored extension.
Note: The Asterisk and Epygi Quadro 4x/16x IP PBX servers support
this feature. For details about Asterisk support, contact Aastra Technical
Support.
Directed Call Pickup Prefix (optional)
The optional “directed call pickup prefix” allows you to enter a specific prefix
string (depending on what is available on your server), that the phone
automatically dials when dialing the Directed Call Pickup number. For example,
for Broadsoft servers, you can enter a value of *98 for the “directed call pickup
prefix”. When the phone performs the Directed Call Pickup after pressing a BLF
or BLF/List softkey, the phone prepends the *98 value to the designated extension
of the BLF or BLF/List softkey when dialing out.
How this feature works when Directed Call Pickup is enabled with BLF or
BLF/List
1.
Phone A monitors Phone B via BLF/List.
2.
Phone C calls Phone B; Phone B rings.
3.
If you press the BLF/List softkey on Phone A, it picks up the ringing line on
Phone B.
4.
Phone C connects to Phone A.
How this feature works when Directed Call Pickup is disabled with BLF or
BLF/List
5-82
1.
Phone A monitors Phone B via BLF/List.
2.
Phone C calls Phone B; Phone B rings.
3.
If you press the BLF/List softkey on Phone A, it performs a speeddial to
Phone B.
4.
Phone C and Phone A are ringing Phone B on separate lines (if available).
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
2.
You can define only one prefix at a time for the entire BLF/List.
3. The phone that picks up displays the prefix code + the extension
number (for example, *981234 where prefix key = *98, extension =
1234).
You can enable/disable “Directed Call Pickup” using the configuration files or the
Aastra Web UI.
Note: The “Directed Call Pickup” feature is disabled by default.
41-001160-00, Release 2.1, Rev 04
5-83
Operational IP Phone Features
Notes:
1. The default method for the phone to use is Directed Call Pickup over
BLF if the server provides applicable information. If the Directed Call
Pickup over BLF information is missing in the messages to the server, the
Directed Call Pickup by Prefix method is used if a value for the prefix
code exists in the configuration.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Enabling/Disabling Directed Call Pickup
Use the following procedure to enable or disable the Directed Call Pickup feature
on the IP phone.
Configuration Files
To enable/disable Directed Call Pickup on the IP phone using the configuration files, see Appendix A, the
section, “Directed Call Pickup (BLF or XML Call Interception) Settings” on page A-128.
Aastra Web UI
1
Click on Basic Settings->Preferences->Directed Call Pickup Settings.
2
Enable the "Directed Call Pickup" field by checking the check box.
(Disable this field by unchecking the box). Default is disabled.)
3
(optional) Enter a prefix in the "Directed Call Pickup Prefix" field. For example, *98.
This prefix is appended to the beginning of the Directed Call Pickup number when dialed from the
BLF or BLF/List softkey.
5-84
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
4
Enable the "Play a Ring Splash" field by checking the check box.
(Disable this field by unchecking the box). Default is disabled.)
The IP phone plays a short "ring splash" when there is an incoming call on the BLF monitored
extension. If the "Play a Ring Splash" parameter is enabled, and the host tone is idle, the tone plays
a "ring splash".
5
Click
to save your changes.
Configuring BLF/BLF List for Directed Call Pickup
Use the following procedure to configure BLF/BLF List for Directed Call Pickup
in the configuration files.
Note: You must enable Directed Call Pickup before performing these
procedures. See “Enabling/Disabling Directed Call Pickup” on
page 5-84.
Configuration Files
To set BLF or BLF\List in the configuration files for Directed Call Pickup, see Appendix A, the section,
“Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
41-001160-00, Release 2.1, Rev 04
5-85
Operational IP Phone Features
Aastra Web UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Use the following procedure to configure BLF or BLF/List for Directed Call
Pickup in the Aastra Web UI.
Aastra Web UI
1
Click on Basic Settings->Preferences->Directed Call Pickup Settings.
2
Enable the "Directed Call Pickup" field by checking the check box.
3
(optional) Enter a prefix in the "Directed Call Pickup Prefix" field. For example, *98.
This prefix is appended to the beginning of the Directed Call Pickup number when dialed from the
BLF or BLF/List softkey.
4
Enable the "Play a Ring Splash" field by checking the check box.
5-86
The IP phone plays a short "ring splash" when there is an incoming call on the BLF monitored
extension. If the "Play a Ring Splash" parameter is enabled, and the host tone is idle, the tone plays
a "ring splash".
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
5
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Note: Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
6
Select a softkey or programmable key to configure.
7
In the "Type" field, select "BLF" (Asterisk), "BLF\List" (BroadSoft BroadWorks).
8
For the 55i, 57i, and 57i CT softkeys:
In the "Label" field, enter the name of the person who’s extension you are monitoring (if “Type” is
BLF).
Note: If BLF\List type is selected, no label value is required. The BroadWorks BLF List name is
configured in the "BLF List URI" field instead.
41-001160-00, Release 2.1, Rev 04
5-87
Operational IP Phone Features
Aastra Web UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
9
In the "Value" field, enter a value to associate with the softkey or programmable key.
For example, for BLF, the value is the extension you want to monitor.
For BLF\List, the value is an identifier for the list of numbers you are monitoring.
10
Click
11
In the "Line" field, select a line number that is actively registered to the appropriate SIP proxy you are
using.
12
In the "BLF List URI" field, enter the name of the BLF list defined on the BroadSoft BroadWorks
Busy Lamp field page for your particular user.
For example, my57i-blf-list@as.broadworks.com.
to save your changes.
Note: The value of the BLF\List URI parameter must match the list name configured. Otherwise, no
values display on the 57i screen and the feature is disabled.
13
Select the line state (idle, connected, incoming, outgoing, busy) that you want to apply to the BLF
softkey or programmable key.
14
Click
5-88
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring XML for Directed Call Pickup
Notes:
1.
Before implementing this procedure, you must create an XML
application that the phone uses when the XML softkey or programmable
key is pressed. This XML application must be entered as a URI in the
“Value” field of the XML key. For information about creating an XML
script, see Appendix G, the section “Text Menu Object (Menu Screens)”
on page G-6.
2.
You must enable Directed Call Pickup before performing these
procedures. See “Enabling/Disabling Directed Call Pickup” on
page 5-84.
Configuration Files
To set XML in the configuration files for Directed Call Pickup, see Appendix A, the section, “Softkey/
Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
41-001160-00, Release 2.1, Rev 04
5-89
Operational IP Phone Features
Use the following procedure to configure XML for Directed Call Pickup in the
configuration files.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Use the following procedure to configure XML for Directed Call Pickup in the
Aastra Web UI.
Aastra Web UI
1
Click on Basic Settings->Preferences->Directed Call Pickup Settings.
2
Enable the "Directed Call Pickup" field by checking the check box.
3
(optional) Enter a prefix in the "Directed Call Pickup Prefix" field. For example, *98.
This prefix is appended to the beginning of the Directed Call Pickup number when dialed from the
BLF or BLF/List softkey.
4
Enable the "Play a Ring Splash" field by checking the check box.
5-90
The IP phone plays a short "call waiting tone" when there is an incoming call on the BLF monitored
extension. If the "Play a Ring Splash" parameter is enabled, and the host tone is idle, the tone plays
a "ring splash".
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
5
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Note: Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
6
Select a softkey or programmable key to configure.
7
In the "Type" field, select "XML”.
8
For the 55i, 57i, and 57i CT softkeys:
In the "Label" field, enter the name of the person who’s extension you are monitoring.
41-001160-00, Release 2.1, Rev 04
5-91
Operational IP Phone Features
Aastra Web UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
9
In the "Value" field, enter the URI that the phone uses to display the XML application to the LCD.
For example, http://65.205.71.13/xml/startup/key.php?user=$$SIPREMOTENUMBER$$.
Note: For more information about creating an XML script to use with Directed Call Pickup, see
Appendix G, the section “Text Menu Object (Menu Screens)” on page G-6.
10
Select the line state (idle, connected, incoming, outgoing, busy) that you want to apply to the XML
softkey or programmable key.
11
Click
5-92
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Softkeys/Programmable Keys/Feature Keys/Expansion Module Keys
Note: When entering definitions for softkeys in the configuration files,
the “#” sign must be enclosed in quotes.
Softkeys (55i, 57i, 57i CT)
The 55i IP phone has 6 softkeys you can configure to perform specific functions,
The 57i and 57i CT IP phones have 12 softkeys you can configure. With up to 3
Expansion Modules attached to the phone, you can get an additional 72 softkeys
to configure (not all functions apply to Expansion Module softkeys). The
following table provides the number of softkeys you can configure, and the
number of lines available for each type of phone.
IP Phone
Model
55i
Softkeys
Expansion Module
Keys
Programmable
Keys
Lines
Available
Handset
Keys
Available
6
36 to 108*
(Model 536M)
6
9
-
-
9
-
-
9
15
60 to 180**
(Model 560M)
57i
12
36 to 108*
(Model 536M)
60 to 180**
(Model 560M)
57i CT
12
36 to 108* on Base
Station
(Model 536M)
60 to 180** on Base
Station
(Model 560M)
*The 536M expansion module consists of 36 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 108 softkeys. Valid for 55i, 57i, and 57i CT phones.
**The 560M expansion module consists of 60 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 180 softkeys. Valid for 57i and 57i CT phones only.
41-001160-00, Release 2.1, Rev 04
5-93
Operational IP Phone Features
You can configure the softkeys, programmable keys (53i has programmable keys
only), feature keys, and expansion module keys to perform specific functions on
the IP phones.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
State-Based Softkeys (55i, 57i, 57i CT only)
5-94
Users and administrators can configure a specific state to display when a softkey
is being used. Available states you can configure for each softkey include:
•
idle - The phone is not being used.
•
connected - The current line is in an active call (or the call is on hold)
•
incoming - The phone is ringing.
•
outgoing - The user is dialing a number, or the far-end is ringing.
•
busy - The current line is busy because the line is in use or the line is set as
“Do Not Disturb”.
The following table identifies the applicable default states for each type of
softkey you can configure on the IP phone.
Softkey Type
Default States
None
All states disabled.
Line
idle, connected, incoming, outgoing, busy
Do Not Disturb
(DND)
idle, connected, incoming, outgoing, busy
Speeddial
idle, connected, incoming, outgoing, busy
Busy Lamp Field
(BLF)
idle, connected, incoming, outgoing, busy
BLF List
idle, connected, incoming, outgoing, busy
Auto Call
Distribution (ACD)
idle
Directed Call
Pickup (DCP)/
Group Call Pickup
(GCP)
idle, connected, incoming, outgoing, busy
XML
idle, connected, incoming, outgoing, busy
Flash
All states disabled.
Sprecode
connected
Park
connected
Pickup
idle, outgoing
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Default States
Last Call Return
(lcr)
idle, connected, incoming, outgoing, busy
Directory
idle, connected, incoming, outgoing, busy
Callers List
idle, connected, incoming, outgoing, busy
Intercom
idle, connected, incoming, outgoing, busy
Services
idle, connected, incoming, outgoing, busy
Empty
idle, connected, incoming, outgoing, busy
You can enable or disable the softkey states using the configuration files or the
Aastra Web UI. In the Aastra Web UI, you disable a state by unchecking the box
for that operational state.
In the configuration files, you use the following parameters to enable and disable
operational states:
•
softkeyN states
You can enter multiple values (idle, connected, incoming, outgoing, busy) for
the "softkeyN state" parameter. For example:
softkeyN states: idle connected
You must associate the softkeyN state parameter with a specific softkey. In the
following example, the softkeyN states parameter is associated with softkey 12:
softkey12
softkey12
softkey12
softkey12
type: speeddial
label: voicemail
value *89
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
Appendix A, the section, “Softkey Settings for 55i, 57i, 57i CT” on
page A-137.
41-001160-00, Release 2.1, Rev 04
5-95
Operational IP Phone Features
Softkey Type
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuration Example
The following example illustrates the use of the "softkeyN states" parameter, and
the "softkeyN type" parameter with a value of empty. For clarity purposes, only
the "softkeyN type" and "softkeyNstates" parameters are shown.
softkey1
softkey1
softkey3
softkey3
softkey4
softkey5
softkey5
softkey6
softkey6
type: line
states: idle connected
type: dnd
states: idle
type: line
type: empty
states: connected
type: speeddial
states: connected
The following table shows how the keys in the example above would display on
the IP Phone UI.
Note: The "empty" key type allows a softkey to be removed quickly by
deleting the softkey information from the configuration file.
Softkey
Idle
Connected
Notes
softkey1
Key 1
Key 2
Line displays for softkey1.
Key 1 in connected state is the Drop key. Idle
and connected display as applicable.
softkey2
(not used)
(not used)
Softkey2 is not displayed.
softkey3
Key 2
(not used)
DND displays for softkey3. Idle displays as
applicable.
softkey4
Key 3
Key 3
Line displays for softkey4. Default state
values (idle, connected, incoming, outgoing)
display as applicable.
softkey5
(not used)
Key 4 (blank)
A blank displays for softkey5. Connected
displays as applicable.
softkey6
(not used)
Key 5
Speeddial displays for softkey6. Connected
displays as applicable.
Softkeys and programmable keys are configurable using the Aastra Web UI or the
configuration files.
5-96
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Programmable Keys (53i, 55i)
Softkeys
Expansion Module
Keys
Programmable
Keys
Lines
Available
Handset
Keys
Available
53i
-
36 to 108*
(Model 536M)
4
9
-
55i
6
36 to 108*
(Model 536M)
6
9
-
IP Phone
Model
60 to 180**
(Model 560M)
*The 536M expansion module consists of 36 softkeys. You can have up to 3 expansion modules on an IP phone totaling
108 softkeys.
Softkey/Programmable Key/Expansion Module Key Functions
You can configure the softkeys, programmable keys, and any attached expansion
module keys on the 53i, 55i, 57i, and 57i CT to perform specific functions using
the configuration files or the Aastra Web UI. The following table identifies the
available functions of the softkeys, programmable keys, and expansion module
keys on the IP phones. Available functions may vary on each model phone.
The following Key Functions Table lists the available functions for the keys on
the IP Phones and Expansion Modules.
Note: These functions apply to the 53i, 55i, 57i, 57i CT and Expansion
Modules unless specifically stated otherwise.
41-001160-00, Release 2.1, Rev 04
5-97
Operational IP Phone Features
The following table provides the number of softkeys and programmable keys you
can configure, and the number of lines available for each type of phone.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Key Functions Table
Softkey/
Programmable
Key Function
Configuration
File Parameter
Aastra Web UI
Parameter
Description
None
none
None
Indicates not setting for the key.
Line
line
Line
Indicates the key is configured for line use.
Speeddial
speeddial
Speeddial
Indicates the key is configured for speeddial
use.
You can configure a softkey to speeddial a
specific number by pressing that softkey.
Optionally, you can also configure a speeddial
key to dial prefix numbers. With this option, the
prefix numbers automatically dial when you
press the softkey, and the phone waits for you
to enter the remaining numbers to dial out.
For more information about speeddial prefixes,
see “Speeddial Prefixes” on page 5-113.
You can also create speeddial keys using the
IP Phone keypad. For more information about
speeddial keys, see your Model-specific User
Guide for more information.
Busy Lamp Field
(BLF)
blf
BLF
Indicates the key is configured for Busy Lamp
Field (BLF) use. A user can dial out on a BLF
configured key. You can also set a BLF
subscription period.
For more information about BLF, see the
section “Busy Lamp Field (BLF)” on
page 5-114.
For more information about BLF Subscription
Period, see “BLF Subscription Period” on
page 5-120.
Busy Lamp Field
List
list
BLF/List
Indicates the key is configured for BLF list use.
A user can dial out on a BLF\List configured
key.
For more information on BLF, see the section
“Busy Lamp Field (BLF)” on page 5-114.
5-98
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuration
File Parameter
Auto Call
acd
Distribution (ACD)
Aastra Web UI
Parameter
Auto Call
Distribution
Description
(For Sylantro Servers) Indicates the key is
configured for automatic call distribution
(ACD). ACD allows the Sylantro Server to
distribute calls from a queue to registered IP
Phones (agents). You can also set an ACD
subscription period.
For more information about ACD, see the
section “Automatic Call Distribution (ACD) (for
Sylantro Servers)” on page 5-122.
For more information about ACD subscription
period, see “ACD Subscription Period” on
page 5-133.
Directed Call
dcp
Pickup (DCP)/
Group Call Pickup
(GCP)
Directed Call
Pickup
(For Sylantro Servers) Indicates the key is
configured for either Directed Call Pickup or
Group Call Pickup. The DCP/GCP feature
allows you to intercept - or pickup - a call on a
monitored extension(s).
For more information about DCP/GCP, see the
section “Directed Call Pickup/Group Call
Pickup (for Sylantro Servers)” on page 5-135.
Do Not Disturb
(DND)
dnd
Do Not Disturb
Indicates key is configured for "do not disturb"
use.
For more information on DND, see the section
“Do Not Disturb (DND)” on page 5-142.
Extensible Markup xml
Language) (XML)
XML
Indicates the key is configured to accept an
XML application for accessing customized
XML services. You can also specify a URL for
an XML key.
For more information on XML, see the section
“XML Customized Services” on page 5-196.
41-001160-00, Release 2.1, Rev 04
5-99
Operational IP Phone Features
Softkey/
Programmable
Key Function
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Softkey/
Programmable
Key Function
Flash
Configuration
File Parameter
flash
Aastra Web UI
Parameter
Flash
(Not applicable on
Expansion
Modules)
Description
Indicates the key is set to generate a flash
event when it is pressed, or when a feature
key is pressed on the 57i CT handset. The IP
phone generates flash events only when a call
is connected and there is an active RTP
stream (for example, when the call is not on
hold).
For more information about the Flash key, see
your Model-specific User Guide.
Sprecode
sprecode
Sprecode
(Not applicable on
Expansion
Modules)
Indicates the key is set to automatically
activate specific services offered by the server.
For example, if the sprecode value of *82 is
configured, then by pressing the key, *82
automatically activates a service provided by
the server. The value you enter for this field is
dependent on the services provided by the
server.
For more information about the Flash key, see
your Model-specific User Guide.
Park
park
Park
(Not applicable on
Expansion
Modules)
Pickup
For more information on park, see the section
“Park/Pick Up Key” on page 5-153.
pickup
Pickup
(Not applicable on
Expansion
Modules)
Last Call Return
(LCR)
Indicates the key is set to be used as a park
key to park an incoming call.
Indicates the key is set to be used as a pickup
key to pick up a parked call.
For more information on pickup, see the
section “Park/Pick Up Key” on page 5-153.
lcr
Last Call Return
(For Sylantro Servers) Indicates the key is set
to be used to dial the last call that came in on
that line.
For more information on lcr, see the section
“Last Call Return (lcr) (For Sylantro Servers”
on page 5-164.
5-100
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Callers List
Configuration
File Parameter
callers list
Aastra Web UI
Parameter
Callers List
Description
Indicates the key is set for accessing the
Callers List.
For more information on the Callers List, see
the section “Callers List” on page 174.
Directory
directory
Directory
Indicates the key is set for accessing the
Directory List.
For more information about the Directory List,
see the section “Directory List” on page 182.
Icom
icom
Intercom
Indicates the key is set to be used as the
Intercom key. For more information about
using the Intercom key, see your
model-specific Aastra IP Phone User’s Guide.
For information about other Intercom features,
see “Incoming/Outgoing Intercom with
Auto-Answer and Barge In” on page 5-60.
Conference
conf
Conference
(Not applicable on
Expansion
Modules)
Indicates the key is configured as a
conference key (for local conferencing).
(For Sylantro and Broadsoft Servers) An
Administrator can also enable centralized
conferencing on the IP Phones.
For more information about using the
Conference key, see your Model-specific
User’s Guide.
For information about enabling centralizing
conferencing, see “Centralized Conferencing
(for Sylantro and Broadsoft Servers)” on
page 5-220.
Transfer
xfer
(Not applicable on
Expansion
Modules)
41-001160-00, Release 2.1, Rev 04
Transfer
Indicates the key is configured as a transfer
key for transferring calls.
For more information about using the Xfer key,
see your Model-specific User’s Guide.
5-101
Operational IP Phone Features
Softkey/
Programmable
Key Function
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Softkey/
Programmable
Key Function
Services
Configuration
File Parameter
services
Aastra Web UI
Parameter
Services
(Not applicable to
the 53i)
Description
Indicates the key is set to access Services,
such as, Directory List, Callers List, Voicemail,
and any other XML applications configured on
the phone.
For more information about using the Services
key, see your Model-specific User’s Guide.
Phone Lock
phone lock
Phone Lock
(Not applicable to
the 57i CT cordless
handset)
Empty
For more information about the lock/unlock
key, see “Locking IP Phone Keys” on
page 5-28.
empty
(Not applicable to
the 53i)
5-102
Indicates the key is configured as a phone lock
key, allowing you to press this key to lock/
unlock the phone.
Empty
Indicates the key is configured to force a blank
entry on the IP phone display for a specific
key. If a particular key is not defined, it is
ignored.
For more information about empty keys, see
your Model-specific User’s Guide.
Reference
For more information about key functions for your model phone, see your
Model-specific User’s Guide.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Softkeys and Programmable Keys
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the sections,
“Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
41-001160-00, Release 2.1, Rev 04
5-103
Operational IP Phone Features
Use the following procedures to configure the softkeys and programmable keys
on the IP phone.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
Select a key to configure.
For Softkeys and Expansion Module Keys:
3
In the "Type" field, select the type of softkey you want to configure.
Reference: For available type values on each IP phone model, see Appendix A, the section,
“Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
4
5-104
If applicable, enter a label in the “Label” field.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
5
If applicable, in the "Value" field, enter a value to associate with the softkey. For example, for a
speeddial value, you can enter a number you want to use for the speeddial key, or 12345+ as a
speeddial prefix.
6
If applicable, in the "Line" field, select the line for which you want to associate the softkey.
7
Some softkey types allow you to configure specific operational states.
Operational states display to the IP phone when a softkey is used.
To enable/disable an operational state, click the "Idle", "Connected", "Incoming", or "Outgoing"
fields to check or uncheck the box.
Note: Operational states are not applicable to expansion modules.
8
Click
to save your changes.
For programmable keys:
9
In the “Hard Key” field, select the programmable key type you want to configure.
Reference: For available type values on each IP phone model, see Appendix A, the section,
“Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
10
In the "Value" field, enter a value to associate with the programmable key. For example, for a
speeddial value, you can enter a number you want to use for the speeddial key, or 12345+ as a
speeddial prefix.
11
In the "Line" field, select the line for which you want to associate the programmable key.
12
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-105
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
57i Cordless (CT) Feature Keys
In addition to the softkeys on the 57i CT, this phone also has handset keys you can
configure with specific features. You can use the Aastra Web UI to configure the
handset keys.
Note: You configure the handset keys using the Aastra Web UI
(Operation->Handset Keys) or by pressing the "F" button on the
handset.
You can program up to 15 feature keys on the 57i CT handset with specific
functions using the Aastra Web UI.
The following table identifies the functions available for all 15 handset keys and
the default functions for each key.
Handset Key
1
2
3
4
5
6
7
8
9
10
11
Key Function
Line 1
Line 2
Line 3
Line 4
Icom
Dir
Callers
Xfer
Conf
Public
None
12
None
13
None
14
None
15
None
5-106
Description
Line 1 key - Selects line one
Line 2 key - Selects line two
Line 3 key - Selects line three
Line 4 key - Selects line four
Icom key – Enter handset list to select handset to call
Directory key – Activate directory feature
Callers key – Activate callers feature
Transfer key - Activate transfer feature
Conference key - Activate conference feature
Public key – Toggle between public & private call mode
No function selected. Line 5 key (if available) - Selects line
five.
No function selected. Line 6 key (if available) - Selects line
six.
No function selected. Line 7 key (if available) - Selects line
seven.
No function selected. Line 8 key (if available) - Selects line
eight.
No function selected. Line 9 key (if available) - Selects line
nine.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Feature Key Programming Guidelines
•
All handsets paired with the same Base Station have the same programmed
functions since the web interface applies the functions to all the handsets
paired with that base.
•
A newly registered handset or handset that was out-of-range during the
programming needs to perform an "off-hook and on-hook" sequence in order
for the newly programmed function to be broadcasted to the affected
handsets. Simply press the v key from the idle state to go off-hook. Then,
press the y key to go back on-hook.
•
Duplicate functions can exist in the feature key as there is no filtering or
duplicate checking done on the handset or the base.
•
If no line keys are programmed for the feature key, the handset is restricted to
intercom calls only.
•
If all 12 programmable functions have been programmed to "None", the user
is presented with a List empty message when the feature key is pressed.
List empty
Use web page to
configure
•
For security reasons, the user has 180 seconds (3 minutes) to complete the
programming. Otherwise, the phone displays the following error:
** Error **: Session expired, Please reload page.
•
For security reasons, the user must submit the page from the same browser
that was used to load the page. If the user tries to submit the page from any
other IP address, the following error displays:
** Error ** Session invalid. Different Client IP Addresses. —
Please reload page
41-001160-00, Release 2.1, Rev 04
5-107
Operational IP Phone Features
The following are guidelines to use when programming the feature keys on the
handset:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Handset Feature Key Functions
You can configure the features keys on the 57i CT handset to perform specific
functions using the configuration files or the Aastra Web UI.The following table
identifies the available functions for the feature keys on the 57i CT handset.
The following Handset Key Functions Table lists the available functions for the
keys on the 57i CT IP Phone.
Handset Key Functions Table
Feature Key
Function
None
Configuration
File Parameter
none
Aastra Web UI
Parameter
None
Description
Indicates the key is disabled.
This option is available from Web UI only.
Line
line
Line
Indicates the key is configured for line use.
icom
Icom
Indicates the key is set to be used as the
Intercom key.
(Lines 1 through 9
are available for
selection)
Icom
For more information about the Icom key, see
your Aastra IP Phone 57i CT User’s Guide.
For information about other Intercom features,
see “Incoming/Outgoing Intercom with
Auto-Answer and Barge In” on page 5-60.
Directory
dir
Dir
Indicates the key is set for accessing the
Directory List.
For more information about the Directory List,
see the section “Directory List” on page 182.
Callers List
callers
Callers
Indicates the key is set for accessing the
Callers List.
For more information on the Callers List, see
the section “Callers List” on page 174.
5-108
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Transfer
Configuration
File Parameter
xfer
Aastra Web UI
Parameter
Xfer
Description
Indicates the key is configured as a transfer
key for transferring calls.
For more information about the Xfer key, see
your Aastra IP Phone 57i CT User’s Guide.
Park
park
Park
Indicates the key is set to be used as a park
key to park an incoming call.
For more information on park, see the section
“Park/Pick Up Key” on page 5-153.
Pickup
pickup
PickUp
Indicates the key is set to be used as a pickup
key to pick up a parked call.
For more information on pickup, see the
section “Park/Pick Up Key” on page 5-153.
Conference
conf
Conf
Indicates the key is configured as a
conference key (for local conferencing).
(For Sylantro and Broadsoft Servers) An
Administrator can also enable centralized
conferencing on the IP Phones.
For more information about using the
Conference key, see your Aastra IP Phone 57i
CT User’s Guide.
For information about enabling centralizing
conferencing, see “Centralized Conferencing
(for Sylantro and Broadsoft Servers)” on
page 5-220.
41-001160-00, Release 2.1, Rev 04
5-109
Operational IP Phone Features
Feature Key
Function
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Feature Key
Function
Public
Configuration
File Parameter
public
Aastra Web UI
Parameter
Public
Description
Indicates the key is configured to toggle from
public to private mode. A public and private
key can be used when at a line item in the
Directory List. The Private key toggles a
number in the Directory List to private. The
Public key allows a number in the Directory
List to be sent to the handsets. A 57i CT
accepts a maximum of 50 entries with the
public attribute.
For more information about the public/private
keys, see your Aastra IP Phone 57i CT User’s
Guide.
Flash
5-110
flash
Flash
Indicates the key is set to generate a flash
event when it is pressed, or when a feature
key is pressed on the 57i CT cordless handset.
The IP phone generates flash events only
when a call is connected and there is an active
RTP stream (for example, when the call is not
on hold).
For more information about the Flash key, see
your Aastra IP Phone 57i CT User’s Guide.
Reference
For more information about features key functions for your 57i CT, see your
Aastra IP Phone 57i CT User’s Guide.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Handset Feature Keys
Use the following procedures to configure the IP phone handset feature keys.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Handset Feature Key Settings for the 57i CT” on page A-156.
41-001160-00, Release 2.1, Rev 04
5-111
Operational IP Phone Features
You can program up to 15 feature keys on the 57i CT IP phone using the
configuration files or the Aastra Web UI. Use the following procedure to program
the feature keys on your 57i CT Base Station and all paired handsets.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Operation->Handset Keys.
2
Select the handset key you want to program.
3
Select the function for that handset key from the "Key Function" field.
4
Click
to save the function you selected to the handset key.
The key programming information is sent to the 57i Base Station and to all the cordless handsets
associated with that Base Station. Any key programmed to "None" does not appear in the handset’s
list.
5-112
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Speeddial Prefixes
softkey1
softkey1
softkey1
softkey1
type: speeddial
label: Office
value: 5552345
line: 1
after you press softkey1 on the phone, it dials the Office number at 555-2345 on
line 1.
A new feature for the speeddial option allows you to configure a preset string of
numbers followed by a “+”. This feature allows the phone to speeddial a prefix
number and then pause to let you enter the remaining phone number. You can use
this feature for numbers that contain long prefixes. For example, if you had the
following speeddial configuration in the configuration files:
softkey2
softkey2
softkey2
softkey2
type: speeddial
label: Europe Office
value: 1234567+
line: 2
after you press softkey2 on the phone, it dials the prefix number automatically and
pauses for you to enter the remaining number using the keypad on the phone.
You can configure the speeddial prefix using the configuration files or the Aastra
Web UI.
41-001160-00, Release 2.1, Rev 04
5-113
Operational IP Phone Features
The normal function of the speeddial option allows you to configure a specific
key on the phone to dial a number quickly by pressing the configured key. For
example, if you had the following speeddial configuration in the configuration
files:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Busy Lamp Field (BLF)
The BLF feature on the IP phones allows a specific extension to be monitored for
state changes. BLF monitors the status (busy or idle) of extensions on the IP
phone.
Note: The BLF setting is applicable to the Asterisk server only.
Example
A Supervisor configures BLFs on his phone for monitoring the status of a
worker’s phone use (busy or idle). When the worker picks up his phone to make a
call, a busy indicator on the Supervisor’s phone shows that the worker’s phone is
in use and busy.
BLF Setting (For use with Asterisk)
On the 55i, 57i, and 57i CT, the busy and idle indicators show on the IP phone
screen display next to the softkey or programmable key configured for BLF
functionality. When the monitored user is idle, an icon with the handset on-hook
shows next to the BLF softkey or programmable key. When the monitored user is
on an active call, a small telephone icon is shown with the handset off-hook.
On the 53i, the LED lights next to each BLF programmable key illuminate steady
to indicate the monitored line is off-hook or unregistered. The LED goes off when
the line is idle.
Note: You can configure a maximum of 50 BLFs on the 536M and 560M
Expansion Modules.
5-114
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
BLF\List Setting
The BLF\List feature on the IP phones is specifically designed to support the
BroadSoft Broadworks Rel 13 Busy Lamp Field feature. This feature allows the
IP phone to subscribe to a list of monitored users defined through the BroadWorks
web portal.
In addition to monitoring the idle and busy state, the BLF\List feature also
supports the ringing state. When the monitored user is idle, there is a small
telephone icon shown with the handset on-hook. When the monitored user is in
ringing state, there is a small bell icon shown. When the monitored user is on an
active call then a small telephone icon is shown with the handset off-hook.
On the 53i phone, the LED lights next to each BLF programmable key illuminate
steady to indicate the monitored line is off-hook or unregistered. The LED goes
off when the is idle. When the monitored extension is ringing, the LED flashes.
The Broadworks BLF feature is not the same as the Broadworks Shared Call
Appearance (SCA) feature and does not permit call control over the monitored
extension.
Example
A receptionist has a 57i running Broadsoft firmware that subscribes to a list of
extensions from the BroadWorks Application Server. Each monitored extension
in the list shows up individually on the 57i screen next to a softkey button. The
softkey icons on the screen change depending on the state of the extensions.
On the 53i running Broadsoft firmware, the programmable key LEDs illuminate
either flashing, solid, or turn off depending on the state of those extensions.
41-001160-00, Release 2.1, Rev 04
5-115
Operational IP Phone Features
(For use with the BroadSoft Broadworks Rel 13 or higher platform only)
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Asterisk BLF Configuration
You can enable the BLF feature on Asterisk to enable monitoring for specific
extensions. BLF on Asterisk is possible through the “hint” extension parameter.
Add the following in the Asterisk extensions.conf file for each target extension
being monitored.
For example:
exten -> 9995551212,hint,SIP/9995551212
Add the following in the Asterisk sip.conf file for each subscriber if it is not
defined already.
For example:
[9995551212]
Subscribecontext=sip
BroadSoft BLF Configuration
You can enable the BLF feature on BroadSoft BroadWorks Rel 13 or higher
through the BroadWorks Web Portal. Each user must have the Busy Lamp Field
service enabled for their user. The user must add each desired extension to the
“Monitored Users List” on the Busy Lamp Field service page and also enter in a
list name for the monitored users BLF list on the same page.
Changes to the “Monitored Users List” are dynamic and the Aastra IP phones are
automatically updated without requiring a restart.
Reference
For sample BLF configurations, see Appendix E, “Sample BLF Softkey Settings.”
5-116
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring BLFs
Configuration Files
To set BLF or BLF\List in the configuration files, see Appendix A, the section, “Softkey/Programmable Key/
Feature Key/Expansion Module Key Parameters” on page A-136.
41-001160-00, Release 2.1, Rev 04
5-117
Operational IP Phone Features
Use the following procedures to configure BLF and BLF\List on the IP phone.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
Select a softkey, programmable, or expansion module key to configure.
3
In the "Type" field, select "BLF" (Asterisk), "BLF\List" (BroadSoft BroadWorks).
5-118
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
4
For the 55i, 57i, and 57i CT softkeys:
In the "Label" field, enter the name of the person who’s extension you are monitoring (if “Type” is
BLF).
Note: If BLF\List type is selected, no label value is required. The BroadWorks BLF List name is
configured in the "BLF List URI" field instead.
5
In the "Value" field, enter a value to associate with the softkey or programmable key.
For example, for BLF, the value is the extension you want to monitor.
For BLF\List, the value is an identifier for the list of numbers you are monitoring.
6
Click
7
In the "Line" field, select a line number that is actively registered to the appropriate SIP proxy you are
using.
8
In the "BLF List URI" field, enter the name of the BLF list defined on the BroadSoft BroadWorks
Busy Lamp field page for your particular user.
For example, my57i-blf-list@as.broadworks.com.
to save your changes.
Note: The value of the BLF\List URI parameter must match the list name configured. Otherwise, no
values display on the 57i screen and the feature is disabled.
9
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-119
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
BLF Subscription Period
On the IP phones, you can set the time period, in seconds, that the IP phone
resubscribes the BLF subscription service after a software/firmware upgrade or
after a reboot of the IP phone.
In the configuration files, you enter the following parameter with a valid value to
set the BLF subscription period:
sip blf subscription period: <value in seconds>
The minimum value for this 120 seconds (2 minutes). The default is 3600 (1
hour).
Setting this parameter to a value lower than 3600 allows the configured BLF
feature to become active more quickly after a software/firmware upgrade or after
a reboot of the IP phone. If you enter a value lower than 120 for this parameter,
the default value (3600) will be used by the IP phone.
You can configure this feature using the configuration files or the Aastra Web UI.
Configuring BLF Subscription Period
Use the following procedures to configure the BLF subscription period on the IP
phone.
Configuration Files
To configure the BLF subscription period on the IP phones using the configuration files, see Appendix A, the
section, “Advanced SIP Settings” on page A-62.
5-120
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings.
2
Enter a value, in seconds, from 120 (2 min) to 3600 (1 hour) in the "BLF Subscription Period" field.
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-121
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Automatic Call Distribution (ACD) (for Sylantro Servers)
The IP phones support an Automatic Call Distribution (ACD) feature for Sylantro
servers. The ACD feature allows the Sylantro server to distribute calls from a
queue to registered IP phone users (agents).
To use the ACD feature on an IP phone, the administrator must first configure an
an ACD softkey or programmable key. When an IP phone user wants to subscribe
to a queue (in order to receive incoming calls), the user presses the ACD key. The
IP phone UI prompts the user to specify the following information:
•
User ID: the phone number(s) used to login into the queue.
•
Password: the password used to login to the queue.
•
Available/unavailable: Shows the current status of the IP phone. Specifies if
the IP phone user is available/unavailable to receive a call from the queue.
This parameter is set to “unavailable” by default.
When the IP phone user is ready to receive calls from the server, the user logs into
a queue. Depending on the server configuration, the IP phone is either in an
“unavailable” or “available” state. If the phone is set to “available” then the server
begins to distribute calls to this phone immediately. If the phone is set to
unavailable, then server waits until the IP phone user manually changes the phone
status to “available” (using the IP phone UI) before distributing calls.
Whenever the IP phone user answers a call, or misses a call, the server
automatically changes the phone’s status to unavailable. The server updates it
database with this new information and no longer distributes calls to this phone.
The IP phone will remain in this state until:
— the IP phone user makes himself “available” again.
— the ACD auto-availability timer expires. This occurs only if the
administrator has configured an ACD auto-availability timer as described
in “ACD Auto-Available Timer” on page 5-123.
The IP phone user can also choose to manually change the phone status to
unavailable, using the IP Phone UI.
Note: It is recommended you configure no more than a single ACD
softkey or programmable key per IP phone.
5-122
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
ACD Auto-Available Timer
You use the following parameters to configure an ACD Auto-Available Tmer in
the configuration files:
•
acd auto available
•
acd auto available timer
Configuring an Automatic Call Distribution (ACD) Key
You can configure an ACD key on softkeys, programmable keys, and extension
module keys. The following table illustrates examples of configuring an ACD key
on the phone.
Softkey Examples
softkey1 type: acd
softkey1 label: sales
softkey1 line: 1
softkey1 states: idle
Top Softkey Examples
Programmable Key
Examples
prgkey1 type: acd
topsoftkey1 type: acd
topsoftkey1 label: sales prgkey1 line: 1:
topsoftkey1 line: 1
topsoftkey1 states: idle
Extension Module
Examples
expmod1 key1 type: acd
expmod1 key1 label: sales
expmod1 key 1 line: 1
Use the following procedures to configure an ACD key n the IP phone.
Configuration Files
To configure an ACD key using the configuration files, see Appendix A, the section, “Softkey/Programmable
Key/Feature Key/Expansion Module Key Parameters” on page A-136.
41-001160-00, Release 2.1, Rev 04
5-123
Operational IP Phone Features
Whenever the IP phone user answers a call, or misses a call, the server
automatically changes the phone’s status to unavailable. The administrator can
control how long the IP phone remains in the unavailable state by configuring an
auto-available timer. When the timer expires, the IP phone status is automatically
changed to available. The default setting for the timer is 60 seconds.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuring the ACD Auto-Available Timer.
Configuration Files
To configure the ACD Auto-Available Timer using the configuration files, see Appendix A, the section, “ACD
Auto-Available Timer Settings” on page A-131.
5-124
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring an ACD Key Using the Aastra Web UI
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
In the “Type” field, select Auto Call Distribution.
3
In the “Label” field, specify a name for this ACD softkey. The Label helps identify which queue you
are subscribing to when you login. (This field does not apply to the 53i.)
For example: Sales
41-001160-00, Release 2.1, Rev 04
5-125
Operational IP Phone Features
Use the following procedure to configure an ACD softkey, programmable key, or
expansion module key using the Aastra Web UI. This procedure uses the 55i IP
phone as an example.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
4
In the “Line” field, select the line which the IP phone uses to subscribe to the queue.
For example: Line 1
5
Click
to save your changes.
Configuring the ACD Auto-Available Timer Using the Aastra Web UI
Use the following procedure to configure an ACD auto-available timer using the
Aastra Web UI.
Aastra Web UI
1
Click on Basic Settings->Preferences->Auto Call Distribution Settings.
2
In the “Auto Available” check-box, click Enabled.
5-126
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
3
In the “Auto Available Timer” field, specify the length of time (in seconds) before the IP phone
state is automatically reset to “available.” Valid values are 0 to 120 seconds. Default is 60.
For example: 60
4
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-127
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Using the ACD Feature on your IP Phone
The ACD feature allows you to login to a phone queue in order to receive
distributed calls on your IP phone. To login to a phone queue, your system
administrator must preconfigure an ACD softkey or programmable key on your
Aastra IP phone.
For models 55i, 57i, 57i CT, the ACD softkey is labeled according to your
network requirements. Check with your administrator to verify the label assigned
to the ACD softkey on your IP phone. The label usually describes which phone
queue you are accessing when you press the ACD softkey.
For example, suppose the administrator wants to configure an ACD softkey to
allow an IP phone user to log into the Customer Support phone queue. The
administrator assigns the label “Support” to the softkey, so it is easily
recognizable to the IP phone user. When the IP phone user wants to subscribe to
the Customer Support queue, the user presses the Support key and can log in.
Once logged in to the queue, you can make himself “available” or “unavailable”
to take calls by pressing the Available/Unavailable key on the phone UI. The
server monitors your IP phone status. When you set the IP phone to “available,”
the server begins distributing calls to your phone. When you set the IP phone to
“unavailable,” the server temporarily stops distributing calls to your phone.
The icon that appears next to the ACD softkey or programmable key on the IP
Phone UI reflects your current status. In the example shown below, the
icon
shows the current status of this IP phone user as “logged off.”
Services
Dir
Callers
Icom
L1
Mon Jan 2 10:37am
ACD softkey
for this example
5-128
o Support
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Phone Model
Status: Logged In
and Available
Status: Unavailable Logged Out
53i
Solid Red LED
Blinking red LED
No LED
55i, 57i, 57i CT
Solid Red LED
icon
Blinking Red LED
Blinking
icon
No LED
icon
41-001160-00, Release 2.1, Rev 04
5-129
Operational IP Phone Features
This icon changes when you log on to the phone queue and are available to take
calls. The icon changes again when you are busy with an active call. The table
below describes the meaning of the LED, and each icon, as they may appear on
your IP phone:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Logging In to a Phone Queue (55i, 57i, 57i CT)
Use the following procedure to log into a phone queue from your Aastra IP phone.
Aastra IP Phone UI
Step
Action
1
Press the ACD softkey on your IP phone.
Note: Check with your administrator to verify the label assigned to the ACD softkey on your IP
phone.
The login screen (see below) appears. In this example, the ACD softkey accesses the Customer
Support phone queue and is labelled “Support.”
Services
Dir
Callers
Icom
ACD: Support
User ID:
Password:
Backspace
Log In
Cancel
2
To log into the phone queue, use your IP phone keypad to enter the following information:
User ID: The phone number you use to access the queue.
Password: The password you use to access this queue.
5-130
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
3
Press the Log In softkey.
You are logged into the phone queue. Once you log in, examine the IP Phone UI, and note the
following information:
•
If your IP phone status is set to “available” then the server will begin to distribute phone calls from
this queue to your IP phone.
•
If your IP phone status remains “unavailable” after you log in, then you must manually change the
state to “available” in order to start receiving calls.
•
To temporarily stop receiving calls, you can switch the IP phone status to “unavailable.”
While you are on a call (or miss a call that has been distributed to your IP phone), your IP phone
status automatically switches to “unavailable.” Your IP phone remains in the unavailable state until
one of the following things occur:
4
•
You use the IP Phone UI to manually switch the IP phone state back to available, or
•
The availability “timer” for your IP phone expires. This only occurs if your administrator has
configured an auto-availability timer on your IP phone.
To Log out of the queue, press the Log Out softkey. The server no longer distributes phone calls to
your IP phone.
41-001160-00, Release 2.1, Rev 04
5-131
Operational IP Phone Features
Aastra IP Phone UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Logging In To a Phone Queue (53i)
Use the following procedure to log into a phone queue from your Aastra IP phone.
Aastra IP Phone UI
Step
Action
1
Press the ACD programmable key on your IP phone.
2
To login to the phone queue, use your IP phone keypad to enter the following information:
User ID: The phone number you use to access the queue.
Password: The password you use to access this queue.
3
Select Login.
You are logged into the phone queue. Once you log in, examine the IP Phone UI, and note the
following information:
•
If your IP phone status is set to “available” then the server will begin to distribute phone calls from
this queue to your IP phone.
•
If your IP phone status remains “unavailable” after you log in, then you must manually change the
state to “available” in order to start receiving calls.
•
To temporarily stop receiving calls, you can switch the IP phone status to “unavailable.”
While you are on a call (or miss a call that has been distributed to your IP phone), your IP phone
status automatically switches to “unavailable.” Your IP phone remains in the unavailable state until
one of the following things occur:
4
•
You use the IP Phone UI to manually switch the IP phone state back to available, or
•
The availability “timer” for your IP phone expires. This only occurs if your administrator has
configured an auto-availability timer on your IP phone.
To Log out of the queue, select Logout.
The server no longer distributes phone calls to your IP phone.
5-132
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
ACD Subscription Period
In the configuration files, you enter the following parameter with a valid value to
set the ACD subscription period:
sip acd subscription period: <value in seconds>
The minimum value for this 120 seconds (2 minutes).
The default is 3600 (1 hour).
Setting this parameter to a value lower than 3600 allows the configured ACD
feature to become active more quickly after a software/firmware upgrade or after
a reboot of the IP phone. If you enter a value lower than 120 for this parameter,
the default value (3600) will be used by the IP phone.
You can configure this feature using the configuration files or the Aastra Web UI.
Configuring ACD Subscription Period
Use the following procedures to configure the ACD subscription period on the IP
phone.
Configuration Files
To configure the ACD subscription period on the IP phones using the configuration files, see Appendix A, the
section, “Advanced SIP Settings” on page A-62.
41-001160-00, Release 2.1, Rev 04
5-133
Operational IP Phone Features
On the IP phones, you can set the time period, in seconds, that the IP phone
resubscribes the ACD subscription service after a software/firmware upgrade or
after a reboot of the IP phone.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings.
2
Enter a value, in seconds, from 120 (2 min) to 3600 (1 hour) in the "ACD Subscription Period" field.
3
Click
5-134
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Directed Call Pickup/Group Call Pickup (for Sylantro Servers)
The Directed Call Pickup/Group Call Pickup feature allows you to intercept - or
pickup - a call on a monitored extension. An Administrator or User can configure
this feature using the Aastra Web UI to create a DCP or GCP softkey on the IP
phone. When you configure a DCP softkey, you specify the extension that you
want to monitor. Then, when the monitored extension receives a call, you press
the DCP softkey to “pickup” (intercept) it. If the monitored extension receives
multiple incoming calls simultaneously, the IP Phone UI displays a list of
incoming calls. You select a call from this list, and are connected to the call.
When you configure a GCP softkey, you specify the ring group that you want to
monitor for incoming calls. For example, suppose an Operator configures a GCP
softkey to monitor incoming calls for a specific ring group (extensions
2200-2210). When an incoming call is received on any of these extensions, the
Operator presses the GCP softkey and is connected to the call. If multiple
incoming calls are received simultaneously, the Operator does the following
actions:
•
Presses the GCP softkey. The Operator Phone UI displays the current list of
incoming calls (see below).
•
Selects an extension to “pickup” first.
•
Presses the Pickup softkey. The Operator is connected to the incoming call.
Select an extension
Press the Pickup
softkey to intercept
the call
41-001160-00, Release 2.1, Rev 04
DCP on line:
1. 2201
= Pickup = Cancel
5-135
Operational IP Phone Features
Aastra IP phones and any attached Expansion Modules support the Directed Call
Pickup (DCP) and Group Call Pickup (GCP) features.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Configuring DCP/GCP Using the Configuration Files
(for Sylantro Servers)
Use the following procedures to configure DCP/GCP using the configuration
files.
Configuration Files
To set DCP/GCP in the configuration files, see Appendix A, the section, “Softkey/Programmable Key/
Feature Key/Expansion Module Key Parameters” on page A-136.
5-136
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedure to configure Directed Call Pickup using the Aastra
Web UI. This procedure uses the 57i IP Phone as an example.
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
Select a key for which to configure Directed Call Pickup.
3
In the “Type” field, select Directed Call Pickup.
4
In the “Label” field, specify a name for this Directed Call Pickup softkey.
For example: DCP2200
41-001160-00, Release 2.1, Rev 04
5-137
Operational IP Phone Features
Configuring Directed Call Pickup (DCP) Using the Aastra Web UI
(for Sylantro Servers)
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
5
In the “Value” field, specify the extension you want to intercept when you press this softkey.
For example: 2200
6
5-138
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Use the following procedure to configure Group Call Pickup using the Aastra
Web UI.
Note: A ring group must be configured on the Sylantro Server in order
for a GCP softkey to function.
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example.
2
Select a key for which to configure Group Call Pickup.
3
In the “Type” field, select Directed Call Pickup.
41-001160-00, Release 2.1, Rev 04
5-139
Operational IP Phone Features
Configuring Group Call Pickup (GCP) Using the Aastra Web UI
(for Sylantro Servers)
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
4
In the “Label” field, specify a name for this Directed Call Pickup softkey.
For example: GCP_A
5
In the “Value” field, enter groupcallpickup.
6
Click
to save your changes.
Using Directed Call Pickup/Group Call Pickup
Use the following procedure for the DCP/GCP on your phone.
Note: Before using the DCP/GCP feature on your phone, you must first
configure the DCP or GCP key. You must identify the extension(s) or
phone number(s) you want to monitor when configuring the key.
IP Phone UI
Step
Action
Using Directed Call Pickup (DCP)
1
When the monitored extension receives a call, press the DCP softkey to pick up the call.
2
If the monitored extension receives multiple incoming calls simultaneously, the phone displays a list
of incoming calls.
3
Select a call from this list using the UP and DOWN arrow keys.
The call is answered.
Using Group Call Pickup (GCP)
1
5-140
When any of the monitored group of extensions receives a call, press the GCP softkey to pick up the
call.
The call is answered.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
2
If the monitored extension receives multiple incoming calls simultaneously, the phone displays a list
of incoming calls.
3
Select a call from this list using the UP and DOWN arrow keys.
Press the "Pickup" softkey to answer the call you selected.
Select an extension
Press the Pickup
softkey to answer
the call
41-001160-00, Release 2.1, Rev 04
DCP on line:
1. 2201
= Pickup = Cancel
5-141
Operational IP Phone Features
IP Phone UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Do Not Disturb (DND)
The IP phones have a feature you can enable called "Do not Disturb (DND). You
can configure DND on softkeys and programmable keys using the Aastra Web UI
or the configuration files.
If DND is configured on the phone, the softkey or programmable key switches
DND ON and OFF. If the phone shares a line with other phones, only the phone
that has DND configured is affected.
The second line on the screen of the IP phone shows when DND is configured.
When a call comes in on the line, the caller hears a busy signal or recorded
message, depending on the server configuration.
Configuring DND
Use the following procedures to configure DND on the IP phone.
Configuration Files
For specific softkey and programmable key parameters you can set in the configuration files, see
Appendix A, the section, “Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on
page A-136.
5-142
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
1
Click on Operation->Softkeys and XML
or
Click on Operation->Programmable Keys
or
Click on Operation->Expansion Module <N>.
Depending on your phone-model, the key configuration screen displays. The 57i Key Screen is
shown as an example
2
Select a hard key to configure.
3
In the "Type" field, select "do not disturb".
Note: You do not need to set the "Value" for DND. DND is applied to the hard key only.
4
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-143
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Bridged Line Appearance (BLA) (55i, 57i, 57i CT only)
A SIP bridge line appearance (BLA) on the IP phones 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-anil-sipping-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.
5-144
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
IP Phone Model
Possible # of BLA
Lines
57i
9
57i CT
9
53i
9
Configuring BLA
You can configure BLA on a global or per-line basis using the configuration files
or the Aastra Web UI.
Global BLA
You configure BLA on a global basis in the configuration files using the following
parameters:
sip mode
sip user name
sip bla number
You configure BLA on a global basis in the Aastra Web UI using the following
fields at Advanced Settings->Global SIP->Basic SIP Settings:
•
Line Mode
•
Phone Number
•
BLA Number
41-001160-00, Release 2.1, Rev 04
5-145
Operational IP Phone Features
The following table shows the number of lines that can be set to BLA for each
model phone.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Per-Line BLA
5-146
You configure BLA on a per-line basis in the configuration files using the
following parameters:
sip lineN mode
sip lineN username
sip lineN bla number
You configure BLA on a per-line basis in the Aastra Web UI using the following
fields at Advanced Settings->Line 1 thru Line 9:
•
Line Mode
•
Phone Number
•
BLA Number
Sylantro servers and ININ servers require specific configuration methods for
per-line configurations.
For Sylantro Server
When configuring the BLA feature on a per-line basis for a Sylantro server, the
value set for the "sip lineN bla number" parameter shall be the same value set for
the "sip lineN user name" parameter for all the phones in the group. For example,
if sip lineN user name is 1010, you would configure BLA on a per-line basis for
the Sylantro server as follows:
sip line 1 mode: 3
sip line1 user name: 1010 (# for all the phones)
sip line1 bla number: 1010
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
For ININ Server
(# for phone 1 with appearance of phone 3)
sip line1 mode: 3
sip line1 user name: 10101 sip line1 bla number: 1010
(# for phone 2 with appearance of phone 3)
sip line1 mode: 3
sip line1 user name: 10102
sip line1 bla number: 1010
(# for phone 3)
sip line1 mode: 3
sip line1 user name: 1010
sip line1 bla number: 1010
Note: The original phone number which has the bridged line appearance
on other phones, will have the "sip lineN user name" parameter the same
as the "sip lineN bla number" (1010 in the above example on Phone 3).
Use the following procedures to configure BLA on the IP phone.
Configuring Global BLA
Configuration Files
For specific global parameters you can set in the configuration files, see Appendix A, the section,
“SIP Basic, Global Settings” on page A-41.
Configuring Per-Line BLA
Configuration Files
For specific per-line parameters you can set in the configuration files, see Appendix A, the section,
“SIP Basic, Per-Line Settings” on page A-50.
41-001160-00, Release 2.1, Rev 04
5-147
Operational IP Phone Features
When configuring the BLA feature on an ININ server, the value set for the sip
lineN bla number parameter shall be the same value set for the sip lineN user
name parameter without the incremented digit added to the phone #. For example,
if the sip lineN user name for the first phone is 10101, and the sip lineN user name
for the second phone is 10102, etc., you would configure BLA on a per-line basis
for the ININ server as follows:
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
5-148
For global configuration of BLA:
Click on Advanced Settings->Global SIP->Basic SIP Authentication Settings.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
For per-line configuration of BLA:
Click on Advanced Settings->Line N (1-9).
In the "Line Mode" field, select the BLA option.
2
In the "Phone Number" field, enter the phone number of the IP phone.
3
For global configuration of BLA:
In the "BLA Number" field, enter the Bridge Line Appearance (BLA) number to be shared across all
IP phones.
For per-line configuration of BLA:
In the "BLA Number" field, enter the Bridge Line Appearance (BLA) number to be shared on a
specific line.
4
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-149
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Using a BLA Line on the IP Phone
5-150
If you have either a global or per-line BLA configuration, and you want to share a
call on the line with a BLA group, you need to press the Hold button before
sharing the call with the group.
For example, if line 1 is configured for BLA, and you pick up a call on line 1, you
must press the Hold button to share the call with the BLA group.
If you pick up a call on line 1 configured for BLA, and another call comes in on
line 2, you can pick up line 2 without putting line 1 on hold. The line 1 call will
be on hold automatically; however it is on hold locally only. The line 1 call
cannot be shared with the BLA group.
Note: The Hold button must be pressed for a call on a BLA line to be
shared with the BLA group.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
BLA Support for Third Party Registration
When configuring the BLA feature on a per-line basis for third party registration
and subscription, the third party name must be configured using the “sip lineN bla
number” parameter. For third party registration to work effectively, one of the
lines should register as generic with its own username.
For example, Bob has Alice’s appearance on his phone. Bob’s configuration is as
follows:
#line 1 Bob
sip
sip
sip
sip
sip
sip
line1
line1
line1
line1
line1
line1
auth name:4082272203
password:
mode: 0
user name:4082272203
display name:Bob
screen name:Bob
#line 2 Alice
sip line2 auth name:4082272203
sip line2 password:
#BLA mode 3
sip line2 mode: 3
sip line2 user name:4082272203
41-001160-00, Release 2.1, Rev 04
5-151
Operational IP Phone Features
BLA allows an Address Of Record (AOR) to be assigned onto different line
appearances for a group of SIP user agents (IP phones). When a call is made to
this BLA number, the call is offered to all user agents that have mapping to this
BLA. To support this, the IP phones need to support third party registration for the
BLA along with the registration for its own primary appearance number. If the IP
phone has the primary appearance as a BLA, then there is no need for third party
registration.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
#Alice phone number
5-152
sip line2 bla number:4085582868
sip line2 display name:Alice
sip line2 screen name:Alice
Alice’s configuration is as follows:
#line 1
sip
sip
sip
sip
sip
sip
line1
line1
line1
line1
line1
line1
auth name:4085582868
password:
mode: 3
user name:4085582868
display name: Alice
screen name: Alice
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Park/Pick Up Key
•
Using a static configuration (globally configures park and pickup)
•
Using a programmable configuration (using a key)
Note: The IP phones accept both methods of configuration. However, to
avoid redundancy, Aastra Telecom recommends you configure either a
static configuration or a programmable configuration.
The IP phones support the Park/Pickup feature on the Asterisk, BroadWorks,
Sylantro, and ININ PBX servers.
The following paragraph describes the configuration of a park and pickup key on
the IP phone. For information about configuring the park and pickup static
configuration method see “Park Calls/Pick Up Parked Calls” on page 5-35.
Park/Pickup Programmable Configuration (using a key)
The programmable method of configuration creates park and pickup keys
(softkeys, programmable keys, extension module keys) that you can configure on
the IP phones.
For the 55i, 57i, and 57i CT you can set a key as "Park" or "Pickup" and then:
•
specify a customized label to display on the Phone UI
•
specify a value
•
specify which line to use
•
specify the state of the park and/or pickup keys
For the 53i, you can set a programmable key as "Park" or "Pickup" and then:
•
specify a value
•
specify a line to use
41-001160-00, Release 2.1, Rev 04
5-153
Operational IP Phone Features
The IP phones (including the 57i CT handset) have a park and pickup call feature
that allows you to park a call and pickup a call when required. There are two ways
a user or administrator can configure this feature:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
On 57i/57i CT
On the IP phone UI, the Park/Pickup feature displays the following:
•
When a call comes in, and you pickup the handset, the custom label that you
configured for the Park softkey displays on the Phone UI.
•
After the call is parked, the label that you configured for the Pickup softkey
displays on other phones in the network. You can then press the "Pickup"
softkey, followed by the applicable value to pickup the call on another phone
in your network.
•
On the 57i CT, the customized labels apply to the base unit only. On the 57i
CT handset, pressing Ï displays the default labels of "Park" and "Pickup".
Notes:
1. On the 57i CT, the customized labels apply to the base unit only. On
the 57i CT handset, pressing Ï displays the default labels of "Park" and
"Pickup".
2. On the 57i/57i CT, the old softkey labeled "Pickup" has been
renamed to "Answer". This softkey uses the old functionality - when you
pickup the handset, you see a softkey labeled "Answer". You can then
press this key to pick up an incoming call. Do no confuse this feature
with the new Park/Pickup configuration feature.
On 53i
•
When a call comes in, and you pickup the handset, you can press the
applicable "Park" programmable key to park the call.
•
After the call is parked, you can press the "Pickup" programmable key,
followed by the applicable value to pickup the call.
You can configure a Park and Pickup key configuration using the configuration
files or the Aastra Web UI.
5-154
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Park/Pickup Key Using Configuration Files
Model 57i/57i CT Examples
Server
Park Configuration
Pickup Configuration
Asterisk
softkeyN type: park
softkeyN label: parkCall
softkeyN value: asterisk;70
softkeyN line: 1
softkeyN states: connected*
softkeyN type: pickup
softkeyN label: pickupCall
softkeyN value: asterisk;70
softkeyN line: 1
softkeyN states: idle, outgoing**
Sylantro
softkeyN type: park
softkeyN label: parkCall
softkeyN value: sylantro;*98
softkeyN line: 1
softkeyN states: connected*
softkeyN type: pickup
softkeyN label: pickupCall
softkeyN value: sylantro;*99
softkeyN line: 1
softkeyN states: idle, outgoing**
BroadWorks
softkeyN type: park
softkeyN label: parkCall
softkeyN value: broadworks;*68
softkeyN line: 1
softkeyN states: connected*
softkeyN type: pickup
softkeyN label: pickupCall
softkeyN value: broadworks;*88
softkeyN line: 1
softkeyN states: idle, outgoing**
ININ PBX
softkeyN type: park
softkeyN label: parkCall
softkeyN value: inin;callpark
softkeyN line: 1
softkeyN states: connected*
softkeyN type: pickup
softkeyN label: pickupCall
softkeyN value: inin;pickup
softkeyN line: 1
softkeyN states: idle, outgoing**
*When you configure a softkey as "Park", you must configure the state of the softkey as
"connected".
**When you configure a softkey as "Pickup", you can configure the state of the softkey as "idle,
outgoing", or just "idle", or just "outgoing".
41-001160-00, Release 2.1, Rev 04
5-155
Operational IP Phone Features
In the configuration files, you configure Park/Pickup using the key parameters.
You must specify the "softkeyN value", "prgkeyN value", “topsoftkeyN value“, or
“expmodX keyN value”. The following examples show Park/Pickup
configurations using specific servers.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Model 53i Examples
Server
Park Configuration
Pickup Configuration
Asterisk
prgkeyN type: park
prgkeyN value: asterisk;70
prgkeyN line: 1
prgkeyN type: pickup
prgkeyN value: asterisk;70
prgkeyN line: 1
Sylantro
prgkeyN type: park
prgkeyN value: sylantro;*98
prgkeyN line: 1
prgkeyN type: pickup
prgkeyN value: sylantro;*99
prgkeyN line: 1
BroadWorks
prgkeyN type: park
prgkeyN value: broadworks;*68
prgkeyN line: 1
prgkeyN type: pickup
prgkeyN value: broadworks;*88
prgkeyN line: 1
ININ PBX
prgkeyN type: park
prgkeyN value: inin;callpark
prgkeyN line: 1
prgkeyN type: pickup
prgkeyN value: inin;pickup
prgkeyN line: 1
Note: The 53i does not allow for the configuration of labels and states.
Use the following procedure to configure a Park/Pickup key using the
configuration files.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Softkey Settings for 55i, 57i, 57i CT” on page A-137 and “Programmable Key Settings for 53i and 55i” on
page A-145.
5-156
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring a Park/Pickup Key Using Aastra Web UI
The 57i CT handsets use the park/pickup configuration enabled at
Operation->Handset Keys in the Aastra Web UI. If Park or Pickup are enabled
on more than one line on the base unit, the 57i handset uses the first
programmable configuration.
For example, if line 1 and line 6 are configured for park, the 57i CT handset uses
the configuration set for line 1 to park a call.
On the 53i, you configure a Park and/or Pickup key at
Operation->Programmable Keys, and then enter the appropriate value and line.
Note: Applicable values depend on the server in your network (Asterisk,
BroadWorks, Sylantro, ININ PBX. See the table below for applicable
values.
Park/Pickup Call Server Configuration Values
Server
Park Values*
Pickup Values*
Aasterisk
70
70
Sylantro
*98
*99
BroadWorks
*68
*88
callpark
pickup
ININ PBX
*Leave "value" fields blank to disable the park and pickup feature.
Use the following procedure to configure the Park/Pickup call feature using the
programmable configuration method and the Aastra Web UI.
41-001160-00, Release 2.1, Rev 04
5-157
Operational IP Phone Features
On the 57i/57i CT, you configure a Park and/or Pickup key at
Operation->Softkeys and XML. You enter a key label, and value for a specific
line on the phone. The default state of the Park configuration is "connected". The
default state of the Pickup configuration is "idle, outgoing".
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For the 57i/57i CT:
1
Click on Operation->Softkeys and XML.
2
Pick a softkey to configure for Parking a call.
3
In the "Type" field, select Park.
4
In the "Label" field, enter a label for the Park softkey.
5
In the "Value" field, enter the appropriate value based on the server in your network.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-157.
6
In the "Line" field, select a line for which to apply the Park configuration.
7
The park softkey has a default state of “Connected”.
Leave this state enabled or to disable, uncheck the check box.
8
Pick a softkey to configure for Picking up a call.
9
In the "Type" field, select Pickup.
10
In the "Label" field, enter a label for the Pickup softkey.
5-158
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
11
In the "Value" field, enter the appropriate value based on the server in your network.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-157.
12
In the "Line" field, select a line for which to apply the Pickup configuration.
13
The pickup softkey has a default state of “Idle” and “Outgoing”.
Leave these states enabled or to disable, uncheck the check boxes.
14
Click
to save your changes.
For the 57i CT Handset:
1
Click on Operation->Handset Keys.
2
Pick a handset key to configure for parking a call.
3
In the "Key Function" field, select Park.
4
Pick another handset key to configure for picking up a call.
5
In the "Key Function" field, select Pickup.
6
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-159
Operational IP Phone Features
Aastra Web UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For the 53i:
1
Click on Operation->Programmable Keys.
53i Screen
2
Pick a hard key (from keys 3 through 6) to configure for Parking a call.
3
In the "Hard Key" field, select Park.
4
In the "Value" field, enter the appropriate value based on the server in your network.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-157.
5
For the 53i:
In the "Line" field, select a line for which to apply the Park configuration.
6
Pick a hard key to configure for Picking up a call.
7
In the "Hard Key" field, select Pickup.
8
In the "Value" field, enter the appropriate value based on the server in your network.
Note: For values to enter in this field, see the table “Park/Pickup Call Server Configuration Values”
on page 5-157.
9
For the 53i:
In the "Line" field, select a line for which to apply the Pickup configuration.
5-160
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
10
Click
Operational IP Phone Features
Aastra Web UI
to save your changes.
You must restart your IP phone for the changes to take affect.
11
Click on Operation->Reset.
12
In the "Restart Phone" field click
41-001160-00, Release 2.1, Rev 04
to restart the IP phone and apply the changes.
5-161
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Using the Park Call/Pickup Parked Call Feature
Use the following procedures on the IP phones to park a call and pick up a parked
call.
IP Phone UI
Step
Action
Parking a Call
1
While on a live call, press the "Park" softkey.
2
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.
If the call is parked successfully, the response is either a greeting voice confirming that the call was
parked, or a hang up occurs. The parked call party will get music on hold.
3
If the call fails, you can pick up the call (using the next procedure) and press the "Park" softkey again
to retry step 2.
Picking up a Parked Call
4
5-162
Pick up the handset on the phone.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
5
Enter the extension number where the call was parked.
6
Press the "Pickup" softkey.
Operational IP Phone Features
IP Phone UI
If the call pick up is successful, you are connected with the parked call.
41-001160-00, Release 2.1, Rev 04
5-163
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Last Call Return (lcr) (For Sylantro Servers
Last call return (lcr) allows an administrator or user to configure a "last call
return" function on a softkey or programmable key. This feature is for
Sylantro servers only.
You can configure the “lcr” softkey feature via the configuration files or the
Aastra Web UI.
How it works
If you configure "lcr" on a softkey or programmable key, and a call comes
into your phone, after you are finished with the call and hangup, you can
press the key configured for “lcr” and the phone dials the last call you received.
When you configure an “lcr” softkey, the label “LCR” displays next to that
softkey on the IP phone. When the Sylantro server detects an “lcr” request, it
translates this request and routes the call to the last caller.
Configuring Last Call Return
Use the following procedures to configure LCR on the IP phones.
Configuration Files
For specific last call return (lcr) parameters you can set in the configuration files, see Appendix A, the
section, “Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
5-164
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
For the 57i/57i CT:
1
Click on Operation->Softkeys and XML.
2
Pick a softkey to configure for Last Call Return.
3
In the "Type" field, select lcr.
4
In the "Line" field, select a line for which to apply the last call return configuration.
5
The lcr softkey has a default state of “Idle”, “Connected”, “Incoming”, “Outgoing”.
Leave these states enabled or to disable, uncheck the check boxes as required.
6
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-165
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For the 57i CT Handset:
1
Click on Operation->Handset Keys.
2
Pick a handset key to configure for Last Call Return.
3
In the "Key Function" field, select lcr.
4
Click
5-166
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Operational IP Phone Features
Aastra Web UI
For the 53i
1
Click on Operation->Programmable Keys.
53i Screen
2
Pick a hard key (from keys 3 through 6) to configure for Last Call Return.
3
In the "Type" field, select lcr.
4
For the 53i:
In the "Line" field, select a line for which to apply the lcr configuration.
5
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-167
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Call Forwarding
5-168
The call forwarding feature on the IP phone allows incoming calls to be forwarded
to another destination. The phone sends the SIP message to the SIP proxy, which
then forwards the call to the assigned destination.
Call forwarding is disabled by default. You can configure call forwarding on a
phone-wide basis or on multi-line phones on a per-line basis. If you have
configured call forwarding on an individual line, then the settings for this line are
used; otherwise, the phone-wide call forward settings are used.
You can configure call forwarding on all phones (global settings) or on specific
lines (local settings) of a single phone.
For call forwarding you can set the following:
•
Call forward mode
•
Destination number
•
Number of rings before forwarding the call (from 1 to 9 rings)
The following are the call forward modes you can set:
Call Forward Mode
Description
Off
Disables call forward
All
Phone forwards all incoming calls
immediately to the specified destination.
Busy
Phone forwards incoming calls if the line is
already in use.
No Answer
Phone forwards the call if it is not
answered in the specified number of rings
Busy No Answer
Phone forwards the call if either the line is
already in use or the call is not answered
in the specified number of rings.
Global
(per-line only)
Phone uses the phone-wide call forward
setting. This is only valid when setting the
mode of individual lines.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
IP Phone Model
Available Lines for
Call Forwarding
53i
9
55i
9
57i
9
57i CT
9
Enabling/Disabling the Ability to Configure Call Forwarding
Using the configuration files, you can enable or disable the ability to configure
Call Forwarding in the Aastra Web UI and the IP Phone UI. You use the following
parameter to enable/disable this feature:
•
call forward disabled
Valid values for this parameter are 0 (disabled) and 1 (enabled). If this parameter
is set to 0, a user and administrator can configure Call Forwarding via the Aastra
Web UI and the IP Phone UI using the "Call Forward" 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 Forwarding.
Use the following procedures to enable/disable Call Forwarding on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling Call Forwarding, see
Appendix A, the section, “Call Forward Settings” on page A-87.
41-001160-00, Release 2.1, Rev 04
5-169
Operational IP Phone Features
The following table shows the IP phone model and the number of lines for which
you can configure call forwarding.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuration Method for Call Forwarding
The method you use to configure call forwarding depends on the model phone you
are configuring.
You can set the phone-wide call forward settings using the IP phone UI or the
Aastra Web UI. However, you must use the Aastra Web UI to set the per-line call
forward settings. The per-line settings override the settings for global call
forwarding.
You can set global and per-line settings on the 55i, 57i, and 57i CT.
Configuring Call Forwarding
Use the following procedure to configure phone-wide call forwarding.
IP Phone UI
Step
Action
For global configuration of call forwarding:
1
Press
on the phone to enter the Options List.
2
Select Call Forward.
3
For 53i:
In the “Cfwd Number” field, enter the destination number for which you want your incoming calls to
be forwarded.
For 55i/57i/57i CT:
In the “Number” field, enter the destination number for which you want your incoming calls to be
forwarded.
Note: Leaving the number field blank disables call forwarding.
5-170
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
4
For 53i:
In the “Cfwd Mode” field, enter the mode that you want to set on your phones.
Operational IP Phone Features
IP Phone UI
For 55i/57i/57i CT:
In the “Mode” field, enter the mode that you want to set on your phones.
Valid modes are:
•
•
•
•
•
5
Off
All
Busy
No Answer
Busy No Answer
In the “No. Rings” field, enter the number of rings you want the phone to ring before the call is
forwarded.
Valid values are 1 to 9.
Note: "No. Rings" field applies to No Answer and Busy No Answer modes only.
6
For 53i:
Press Set to save the changes.
For 55i/57i/57i CT:
Press Done to save the changes.
41-001160-00, Release 2.1, Rev 04
5-171
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Basic Settings->Call Forward.
For global configuration of call forwarding:
2
In the "Mode" field, select the mode you want to set on your phone.
Valid modes are:
•
•
•
•
•
Off
All
Busy
No Answer
Busy No Answer
Note: To disable call forwarding in the Aastra Web UI, set the mode to OFF and remove the phone
number in the "Number" field.
3
5-172
In the "Number" field, enter the destination number for which you want your calls to be call
forwarded.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
4
In the "Number of Rings" field, enter the number of rings you want your phone to ring before the call
is forwarded.
Valid values are 1 to 9.
Note: "Number of Rings" field applies to No Answer and Busy No Answer modes only.
5
Click
to save your changes.
For per-line configuration of call forwarding
6
Select a line to configure Call Forwarding on.
7
In the "Mode" field, select the mode you want to set on your phone.
Valid modes are:
•
•
•
•
•
•
Off
All
Busy
No Answer
Busy No Answer
Global
Notes:
1. To disable call forwarding in the Aastra Web UI, set the mode to OFF and remove the phone
number in the "Number" field.
2. To force a line to use the global settings, set the "Mode" field to Global.
8
In the "Forward Number" field, enter the destination number for which you want your calls on this
line to be call forwarded.
9
In the "Number of Rings" field, select the number of rings you want this line to ring before the call is
forwarded.
Valid values are 1 to 9.
Note: "Number of Rings" field applies to No Answer and Busy No Answer modes only.
10
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-173
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Callers List
The IP phones have a "Callers List" feature that store the name, phone number,
and incremental calls, for each call received by the phone.
The following illustrating shows the default location of the Callers List Key on
each type of phone model.
Callers List Key
53i
55i
57i/57i CT
You can enable and disable the Callers List feature using the configuration files.
When disabled, the Callers List does not display on the IP phone UI and the Caller
List key is ignored when pressed.
When enabled, you can view, scroll, and delete line items in the Callers List from
the IP phone UI. You can also directly dial from a displayed line item in the
Callers List. You can download the Callers List to your PC for viewing using the
Aastra Web UI.
5-174
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
You can use any spreadsheet application to open the file for viewing. The
following is an example of a Callers List in a spreadsheet application.
The file displays the name, phone number, and the line that the call came in on.
41-001160-00, Release 2.1, Rev 04
5-175
Operational IP Phone Features
When you download the Callers List, the phone stores the callerlist.csv file to
your computer in comma-separated value (CSV) format.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Enabling/Disabling Callers List
You can enable and disable user access to the Callers List on the IP phones using
the following parameter in the configuration files:
•
callers list disabled
Valid values for this parameter are 0 (enabled) and 1 (disabled). 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 57i and
57i 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.
Use the following procedures to enable/disable the Callers List on the IP phones.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling the Callers List, see
Appendix A, the section, “Callers List Settings” on page A-86.
Using the Callers List
Use the following procedure to access and use the Callers List.
IP Phone UI
Step
Action
1
Press the “Callers List” key on the phone to enter the Callers List.
2
Use the r and s to scroll through the line items in the Callers List.
To the left of a line item, a b icon displays with the handset ON or OFF the receiver. The ON
receiver indicates the call came in as a missed call. The OFF receiver indicates the call came in and
was answered.
3
To delete all entries in the Callers list, press the 3 Delete key at the "Callers List" header.
To delete a line item from the Callers List, select the line item you want to delete and press the 3
Delete key.
4
5-176
To cancel a delete function, press the r or the s Scroll keys.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
5
To save a line item to a programmable key for speeddialing, press the 3 Save key and enter the line
number at the "Save to?" prompt that is already configured for speeddialing at a programmable key.
6
To dial a displayed entry from the Callers List, pick up the handset, press the d/f handsfree key, or
press a line key.
7
To exit the Callers List, press the “Callers List” key again or the “Goodbye” key.
41-001160-00, Release 2.1, Rev 04
5-177
Operational IP Phone Features
IP Phone UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Downloading the Callers List
Use the following procedure to download the Callers List using the Aastra Web
UI.
Aastra Web UI
1
Click on Operation->Directory.
2
In the Callers List field, click on
.
A “File Download” message displays.
3
Click
.
4
Enter the location on your computer where you want to download the Callers List and click
.
The callerslist.csv file downloads to your computer.
5
5-178
Use a spreadsheet application to open and view the Callers List.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Customizable Callers List and Services Keys
• services script
• callers list script
Specifying URIs for these parameters cause the creation of an XML custom
application instead of the standard function of the Callers List and Services keys.
An Administrator can configure these parameters using the configuration files
only.
Creating Customizable Callers List and Services Keys
Use the following procedure to create customized Callers List and Services keys
on the IP Phone using the configuration files.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Customize
Callers List and Services Key” on page A-86.
41-001160-00, Release 2.1, Rev 04
5-179
Operational IP Phone Features
The IP phones currently have a Callers List key (all 5i Series phones) and a
Services key (55i, 57i, and 57i CT). An Administrator can specify URI overrides
for these keys using the following parameters in the configuration files:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Missed Calls Indicator
The IP phone has a "missed calls" indicator that increments the number of missed
calls to the phone. This feature is accessible from the IP phone UI only.
You can enable and disable the Missed Calls Indicator feature using the
configuration files. When disabled, the Missed Calls Indicator does not increment
as calls come into the IP phone.
When enabled, the number of calls that have not been answered increment on the
phone’s idle screen as "<number> New Calls". As the number of unanswered
calls increment, the phone numbers associated with the calls are stored in the
Callers List. The user can access the Callers List and clear the call from the list.
Once the user accesses the Callers List, the "<number> New Calls" on the idle
screen is cleared.
Enabling/Disabling Missed Calls Indicator
You can enable (turn on) and disable (turn off) the Missed Calls Indicator on the
IP phones using the following parameter in the configuration files:
•
missed calls indicator disabled
Valid values for this parameter are 0 (enabled) and 1 (disabled). If this parameter
is set to 0, the indicator increments as unanswered calls come into the IP phone. If
set to 1, the indicator does not increment the unanswered calls.
Use the following procedures to enable/disable the Missed Calls Indicator on the
IP phones.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling the Missed Calls
Indicator, see Appendix A, the section, “Missed Calls Indicator Settings” on page A-88.
5-180
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Accessing and Clearing Missed Calls
IP Phone UI
Step
Action
1
Press the “Callers List” key on the phone to enter the Callers List.
2
3
Use the r and s to scroll through the line items in the Callers List to find the line items that have
the b icon with the receiver ON. These are the missed calls to the phone.
To clear the line item from the Callers List, select the line item you want to clear and press the 3,
Clear, or Delete key (depending on your phone model).
Note: To cancel a delete function, press the r or the s Scroll keys.
The line item deletes from the Callers List.
41-001160-00, Release 2.1, Rev 04
5-181
Operational IP Phone Features
Use the following procedure to access and clear missed calls from the Callers List.
Once you display the Callers List, the "<number> New Calls" indicator clears.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Directory List
The IP phones have a "Directory List" feature that allows you to store frequently
used names and numbers on the phone. You can also dial directly from the
directory entry.
The following illustrating shows the default location of the Directory Key on each
type of phone model.
Directory key
Directory Key
53i
55i
57i/57i CT
Directory List Capabilities
In the Directory List a user or administrator can store a maximum of 7 numbers
associated with a unique name. You can apply pre-defined labels to the entry
which include, Office, Home, Cell, and Pager, or create your own labels. Labels
can be up to 14 characters in length.
5-182
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Reference
For more detailed information about the Directory Key on your IP phone, and the
Directory List, see your model-specific User Guide.
Administrator/User Functions for Directory List
You can perform the following pertaining to the Directory List:
•
You can enable and disable access to the Directory List using the
configuration files. When disabled, the Directory List does not display on the
IP phone UI and the Directory List softkey is ignored when pressed. This is an
administrator function only.
•
If the Directory List is enabled, you can view, add, change, and delete entries
to/from the Directory List using the IP phone UI. You can also directly dial a
number from the Directory List. This is an administrator and user function.
•
A public and private softkey can be used when at a line item in the Directory
List. The Private key toggles a number in the Directory List to private. The
Public key allows a number in the Directory List to be sent to the handsets. A
57i CT accepts a maximum of 50 entries with the public attribute. This is an
administrator and user function.
•
You can download the Directory List to your PC via the Aastra Web UI. The
phone stores the directorylist.csv file to your PC in comma-separated value
(CSV) format. This is an administrator and user function.
41-001160-00, Release 2.1, Rev 04
5-183
Operational IP Phone Features
You can also sort multiple numbers according to preference and perform a
quick-search feature that allows you to enter the first letter that corresponds to a
name in the Directory to find specific line items. The phone displays the first
name with this letter.The quick-search feature in the Directory List works only
when the Directory is first accessed.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
•
5-184
You can use any spreadsheet application to open the file for viewing. The
following is an example of a Directory List in a spreadsheet application. This
is an administrator and user function.
The file displays the name, phone number(s), and line number(s) for each
Directory entry.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Enabling/Disabling Directory List
•
directory disabled
Valid values for this parameter are 0 (enabled) and 1 (disabled). If this parameter
is set to 0, the Directory List can be accessed by all users. 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 53i, the "Directory" option is also removed from the "Services"
menu.
Use the following procedures to enable/disable the Directory List on the IP
phones.
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling the Directory List, see
Appendix A, the section, “Directory Settings” on page A-85.
41-001160-00, Release 2.1, Rev 04
5-185
Operational IP Phone Features
You can enable and disable user access to the Directory List on the IP phones
using the following parameter in the configuration files:
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Server to IP Phone Download
You can populate your IP phone Directory List with server directory files. To
activate this feature, you need to add the following parameters to the
configuration files:
•
directory 1: company_directory
•
directory 2: my_personal_directory’
The IP phone recognizes the following characters in a Directory List:
Character
Description
’#’
Pound character; any characters appearing after
the # on a line are treated as a comment
’,’
Comma character; used to separate the name,
URI number, line, and mode fields within each
directory entry.
’"’
Quotation mark; when pound and comma
characters are found between quotes in a name
field or URI number field, they are treated as
regular characters.
A valid directory entry has a name, a URI number, and optional line number, and
an optional mode attribute, all separated by commas. If a line number is not
present, the entry is assigned to line 1. If a mode attribute (public or private) is not
present, the entry is assigned to "Private".
The following directory entries are considered valid:
# our company's directory
# updated 1 jan 2012
# mode = private, by default
#
joe foo bar, 123456789, 6
# line = 1, by default
# mode = private, by default
#
snidley whiplash, 000111222
# the parser ignores the COMMA # in the name
# mode = private, by default
#
"manny, jr", 093666888, 9
# the parser ignores the POUND # chars in the URI number
# mode = private, by default
#
hello dolly, "12#34#7", 2
5-186
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Server to IP Phone Download Behavior
During the boot process both directory files are read, combined into a single list,
and any duplicate entries are deleted from the list. Any entries in this list that are
not already in the phone's NVRAM are added to the NVRAM and flagged as
being owned by the server.
Likewise, any entries in the NVRAM that are owned by the server, but are no
longer in one of the server's directory files, are removed from the NVRAM.
Entries made from the IP phone UI are never touched.
Directory List Limitations
The following table indicates the maximum characters for each line and field in
the Directory List.
Directory List Limitations
Maximum length of a line
255 characters
Maximum length of a name
15 characters
Maximum length of a URI
45 characters
Maximum number directory entries in the NVRAM
200 entries
Maximum number directory entries in the NVRAM
with the "public" attribute
(57i CT only)
50 entries
41-001160-00, Release 2.1, Rev 04
5-187
Operational IP Phone Features
The software that reads directory files from the server, loads the file’s contents
into the phone's NVRAM when the phone is booting. Directory entries in the
NVRAM that originate from a server directory file are 'owned' by the server.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Using the Directory List
Use the following procedures to access and use the Directory List.
Note: In the following procedure, the location of keys (hard keys,
softkeys, and programmable keys) on the phone are dependant on your
specific phone model. See Chapter 1, Overview, for the keys that are
specific to your phone model.
IP Phone UI
Step
Action
1
Press the DIRECTORY key to enter the Directory List.
Note: After entering the Directory List, if no key is pressed within 3 seconds, the phone prompts you
to press the first letter in the name of the required directory entry. The phone finds and displays the
first name with this letter.
2
Use the r and s to scroll through the line items in the Directory List.
To dial from an entry in the Directory List:
3
At a line item in the Directory List, pick up the handset, press the d/f key, or press a line key.
The phone automatically dials the Directory List number for you.
To add a new entry to the Directory List:
4
a
or
Press the SAVE key or ADD NEW softkey at a line item and press the DIRECTORY key again.
b
5-188
Press the SAVE key or ADD NEW softkey (depending on your model phone) at the Directory List
header screen and perform step 4.
Enter a phone number, name, and line number and press the SAVE key after each field entry.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
To edit an entry in the Directory List:
5
a
At a line item in the Directory List, press the 3 key.
Note: Use the SAVE key to scroll between the number, name and line entries.
b
Edit the phone number if required and press SAVE.
c
Edit the name if required and press SAVE.
d
Edit the line if required and press SAVE.
e
Press SAVE to save the changes and exit the editing function.
To delete an entry from the Directory List:
6
a
At a line item in the Directory List, press DELETE. The following prompt displays:
“DELETE again to erase this item”.
b
Press DELETE again to delete the entry from the Directory List.
Note: To cancel a delete function, press the r or the s scroll keys.
To delete all entries from the Directory List:
7
a
At the Directory List header, press DELETE or DELETE LIST (depending on your phone model).
The following prompt displays:
“DELETE again to erase all items”.
b
Press DELETE again to delete all entries from the Directory List.
Note: To cancel a delete function, press the r or the s scroll keys.
To copy an entry from the Directory List to a programmable speeddial key:
8
At a line item in the Directory List, press the COPY key and enter the line number at the "Save to?"
prompt that is already configured for speeddialing at a programmable key.
Note: You must have a speeddial key previously configured on your phone to use this feature. To
configure a speeddial key, see your Model-specific User’s Guide.
41-001160-00, Release 2.1, Rev 04
5-189
Operational IP Phone Features
IP Phone UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
IP Phone UI
Step
Action
9
To exit the Directory List, press the DIRECTORY key again, the GOODBYE key, or the QUIT key
(depending on your specific phone model).
From the 57i CT handset:
10
5-190
a
Press the Public/Private softkeys to toggle between making the new entry public or private.
Note: The entry is set to Private by default. If the entry is made Public, the entry is sent to the
handsets. A 57i CT accepts a maximum of 50 entries with the public attribute.
b
c
To edit an entry, use the Change softkey.
A screen displays allowing you to edit the name, phone number, and line number, as well as the
public/private setting.
To dial a displayed entry from the Directory List, pick up the handset, press the d/f handsfree
key, or press the Dial softkey.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Downloading from the Server to the IP Phone
Note: You must use TFTP to download the Directory List.
Use the following procedure to configure the download.
Configuration Files
For specific parameters you can set in the configuration files for downloading the Directory List, see
Appendix A, the section, “Directory Settings” on page A-85.
Downloading from the IP Phone to the Server
You can use the Aastra Web UI to download the Directory List from the IP phone
to the configuration server.
Note: You must use TFTP to download the Directory List.
41-001160-00, Release 2.1, Rev 04
5-191
Operational IP Phone Features
You can use the configuration files to download the Directory List from the
configuration server to the IP phone..
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Use the following procedure to configure the download.
Aastra Web UI
1
Click on Operation->Directory.
2
In the Directory List field, click on
.
A “File Download” message displays.
3
Click
.
4
Enter the location on your computer where you want to download the Directory List and click
.
The directorylist.csv file downloads to your computer.
5
5-192
Use a spreadsheet application to open and view the Directory List.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Voicemail (55i, 57i, and 57i CT only)
For each assigned Voicemail number, there can be a minimum of 0 or a maximum
of 1 Voicemail access phone number.
The Voicemail list displays a list of phone numbers assigned to the 55i, 57i, and
57i CT that have registered voicemail accounts associated with them.
Note: The Voicemail list does not display the voicemail access number.
The phone displays up to 99 voicemails for an account even if the number of
voicemails exceeds the limit.
Registered account numbers/URIs that exceed the length of the screen, either with
or without the voicemail icon and the message count, are truncated with an ellipse
character at the end of the number/URI string.
The end of the Voicemail list displays the number of new voicemail messages (if
any exist).
Configuring Voicemail (55i, 57i, and 57i CT only)
You configure Voicemail in the configuration files to dial a specific number to
access an existing voicemail account. The user then follows the voicemail
instructions for listening to voicemails.
Note: The phone must have a registered voicemail account from a server
for this feature to be enabled. When no registered voicemail accounts are
registered to the phone, the display shows "List Empty".
To configure the Voicemail feature on the 57i/57i CT, you must enter the
following parameter in the configuration files:
•
sip lineN vmail:
41-001160-00, Release 2.1, Rev 04
5-193
Operational IP Phone Features
The Voicemail feature on the 55i, 57i and 57i CT IP phones allow you to
configure lines with phone numbers so the phone can dial out to connect to a
voicemail server. You associate the Voicemail numbers with the phone numbers
configured on each line (1 - 9 lines).
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
You can enter up to 9 Voicemail numbers associated with each of the 9 lines on the
phone.
For example:
sip line1 vmail: *97
sip line2 vmail: *95
Note: In the above example, the user would dial *97 to access the
voicemail account for line 1, and *95 to access the voicemail account for
line 2.
Use the following procedure to configure voicemail using the configuration files.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Voicemail
Settings” on page A-84.
5-194
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Using Voicemail (57i57i CT only)
IP Phone UI
Step
Action
For the 57i/57i CT:
1
Press Services on the phone to display the Services menu.
2
From the Services menu, select "Voicemail".
3
Use the r and s to scroll through the line items in the Voicemail List.
4
When you have selected a line item, press the d/f handsfree key, 4 Scroll Right key, or press a
line softkey to make an outgoing call using the voicemail access phone number associated with the
line for which the voicemail account is registered.
From a selected item in the Voicemail list, you can also lift the handset (go offhook) to make an
outgoing call using the voicemail access phone number.
41-001160-00, Release 2.1, Rev 04
5-195
Operational IP Phone Features
Use the following procedure to access and use voicemail.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
XML Customized Services
Extensible Markup Language (XML) is a markup language much like HTML.
HTML was designed to display data and to focus on how data looks. XML was
designed to describe data and to focus on what data is.
The following are characteristics of XML:
•
XML tags are not predefined. You must define your own tags.
•
XML uses a Document Type Definition (DTD) or an XML Schema to
describe the data.
•
XML with a DTD or XML Schema is designed to be self-descriptive
•
XML is a W3C Standard Recommendation
Creating Customized XML Services on the IP Phones
The XML application for the IP phones allows users to create custom services
they can use via the phone’s keyboard and display. These services include things
like weather and traffic reports, contact information, company info, stock quotes,
or custom call scripts.
The IP phone XML application supports the following proprietary objects that
allow for the customization of the IP phone’s display.
XML Object
Description
AastraIPPhoneTextMenu
(for Menu screens)
Creates a numerical list of menu items on
the IP phones.
AastraIPPhoneTextScreen
(for Text screens)
Creates a screen of text that wraps
appropriately.
AastraIPPhoneFormattedTextScreen
(for Text screens)
AastraIPPhoneInputScreen
(for User Input screens)
AastraIPPhoneInputScreen Time
and Date Attributes
(for User Input screens)
5-196
Creates a formatted screen of text
(specifies text alignment, text size, text
static or scrolling)
Creates screens for which the user can
input text where applicable.
Allows you to specify US (HH:MM:SS am/
pm and MM/DD/YYYY) or International
(HH:MM:SS and DD/MM/YYYY) time/date
formats for an XML user input screen.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Description
AastraIPPhoneDirectory
(for Directory List screen)
Creates an online Directory List that a user
can browse in real-time.
AastraIPPhoneStatus
(for Idle screen)
Creates a screen that displays status
messages when applicable.
AastraIPPhoneExecute
(for executing XML commands)
Allows the phone to execute commands
(i.e., “reset”, “NoOp”, etc.) using XML .
AastraIPPhoneConfiguration
(for pushing a configuration to the phone)
Allows the server to push a configuration to
the phone.(See page 201 for more
information).
AastraIPPhoneImageScreen
(Standard Bitmap Image)
Creates a display with a single bitmap
image according to alignment, height, and
width specifications.
AastraIPPhoneImageMenu
(Menu Image)
Creates a display with a bitmap image as a
menu. Menu selections are linked to keypad
keys (0-9, *, #).
AastraIPPhoneTextMenu (Icon Menu)
(Icon Menu Image)
Creates a display that has a small icon
before each item in the menu.
For more information about creating customized XML applications, see
Appendix G, “Creating an XML Application.”
41-001160-00, Release 2.1, Rev 04
5-197
Operational IP Phone Features
XML Object
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
You can also use the following attributes/options with the XML objects to further
customize your XML applications:
Attribute/Option
Description/Usage
Valid Values
Beep
Enables or disables a BEEP option to
indicate a status on the phone.
yes | no
Default = no
Use with:
XML object (See Appendix G)
Configuration files (See page 200)
Aastra Web UI (See page 200)
Note: This value is
case sensitive.
xml status scroll delay (config files)
Status Scroll Delay (seconds) (Web UI)
1 to 25
Allows you to set the time delay, in
seconds, between the scrolling of each Default = 5
status message on the phone.
Use with:
Configuration files (See page 201)
Aastra Web UI (See page 201)
Timeout
Specifies a timeout value for the LCD
screen display.
0, 30, 45, 60
Default =45
Use with:
XML object (See Appendix G)
XML Get Timeout
5-198
Specifies a timeout value, in seconds,
that the phone waits for the far side to
return a response after accepting the
HTTP GET connection.
0 to 214748364
seconds
Default =0 (never
timeout)
Use with:
Configuration Files (See page 202)
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Description/Usage
Valid Values
LockIn
Specifies whether or not the
information on the LCD screen stays
displayed when other events occur
(such as pressing buttons on the
keypad).
yes | no
Default = no
Use with:
XML object (See Appendix G)
CancelAction
Specifies a URI that the phone
executes a GET on when the user
presses the default CANCEL key.
Use with:
XML object (See Appendix G)
41-001160-00, Release 2.1, Rev 04
Fully qualified URI
For example:
cancelAction=
http://
10.50.10.117/
ft.xml
5-199
Operational IP Phone Features
Attribute/Option
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Enabling/Disabling a Beep for Status Message Displays
You can enable or disable a BEEP option using the Status Message object
(AastraIPPhoneStatus), the configuration files, or the Aastra Web UI.
Note: For enabling/disabling a status message beep using the Status
Message object, see Appendix G, “Creating an XML Application.”
When the phone receives a status message, the BEEP notifies the user that the
message is displaying.
You can use the following to enable/disable a status message beep:
•
AastraIPPhoneStatus object (via XML object; see Appendix G)
•
xml beep notification (via configuration files)
•
XML Beep Support (via the Aastra Web UI)
Enabling the beep is an indication to the phone to sound a beep when it receives
an AastraIPPhoneStatus object. If you disable the beep, or no
AastraIPPhoneStatus object appears in the status message, then the default
behavior is no beep is heard when the object arrives to the phone.
The value set in the configuration files and Aastra Web UI override the attribute
you specify for the AastraIPPhoneStatus object.
For example, if the AastraIPPhoneStatus object has the attribute of Beep=”yes”,
and you uncheck (disable) the “XML Beep Support” in the Aastra Web UI, the
phone does not beep when it receives an AastraIPPhoneStatus object.
Setting the BEEP option in the configuration files and the Aastra Web UI applies
to the phone immediately.
Reference
For information about enabling/disabling the XML beep in the Aastra Web UI, see
“XML Beep Support” on page 5-48.
5-200
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Scroll Delay Option for Status Messages
You can use the following to set the scroll delay for status messages:
•
xml status scroll delay (via the configuration files)
•
Status Scroll Delay (seconds) (via the Aastra Web UI)
Changes apply to the phone immediately.
Reference
For more information about configuring status scroll delay, see “Status Scroll
Delay” on page 5-50.
XML Configuration Push from the Server
The IP phones provide an XML feature that allows you to make configuration
changes to the phone that take affect immediately, without having to reboot the
phone. This feature involves creating XML scripts that push the changed
configuration parameter(s) from the server to the IP phones.
You can use the AastraIPPhoneConfiguration object in the XML scripts to
change configuration parameters or configure new parameters. However, since the
IP phone does not save new parameters created in XML scripts to the local.cfg
file, when the phone reboots, it does not save the new parameters on the phone. In
order for the phone to apply new configuration parameters, you have to enter the
parameters via the user interfaces (Telephone User Interface, Web User Interface,
or configuration files), or reapply the new parameters using the XML scripts after
every boot.
Specific configuration parameters are dynamic on the phone when pushed from
XML scripts on the server. See Appendix G, “Creating an XML Application” for
more information about XML configuration scripts and dynamic configuration
parameters.
41-001160-00, Release 2.1, Rev 04
5-201
Operational IP Phone Features
The IP phones support a scroll delay option that allows you to set the time delay,
in seconds, between the scrolling of each status message on the phone. The default
time is 5 seconds for each message to display before scrolling to the next message.
You can configure this option via the configuration files or the Aastra Web UI.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
For more information about creating XML configuration scripts and for XML
script examples, see Appendix G, “Creating an XML Application”.
Configuring the Phone to use XML
You can configure the phone to request the XML objects you create by
configuring specific parameters via the configuration files or the Aastra Web UI.
Users can access XML applications via softkeys configured on the IP phones.
The phone performs an HTTP GET on the URI configured in the Aastra Web UI
or configuration files.
You configure the following parameters for object requests:
•
xml application URI
•
xml application title
The xml application URI is the application you are loading into the IP phone.
The xml application title is the name of the XML application that displays on the
Services menu in the IP Phone UI (as option #4).
XML Get Timeout
The IP phone has a parameter called, “xml get timeout” that allows you to
specify a timeout value, in seconds, that the phone waits for the far side to return a
response after accepting the HTTP GET connection. If the far side accepts the
GET connection but never returns a response, it blocks the phone until it is
rebooted. If you enter a value greater than 0 for this parameter, the phone times
out and will not be blocked.
For more information about configuring this parameter, see Appendix A, the
section, “XML Settings” on page A-89.
5-202
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
XML Push Requests
Note: The HTTP Post must contain HTTP packets that have an "xml"
line in the message body. For more information about adding "xml" lines
in HTTP packets, see Appendix G, “Creating an XML Application.”.
Example Configuration of XML application
The following example shows the parameters you enter in the configuration files
to configure an XML application:
xml application URI: http://172.16.96.63/aastra/internet.php
xml application title: Aastra Telecom
xml application post list: 10.50.10.53, dhcp10-53.ana.aastra.com
Configuring for XML on the IP Phone
After creating an XML application, an administrator can configure the IP phone to
use the application using the configuration files or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “XML Settings”
on page A-89.
41-001160-00, Release 2.1, Rev 04
5-203
Operational IP Phone Features
In addition to initiating a request to an XML application from a softkey, an HTTP
server can push an XML object to the phone via HTTP Post. When the phone sees
a PUSH request containing an XML object, it tries to authenticate the request. It
does so by checking the IP address or host name of the requesting host against a
list of trusted hosts (or domain names) configured via the Aastra Web UI
(parameter called XML Push Server List) or the configuration files (parameter
called xml application post list). If the request is authenticated, the XML object
is handled by the IP phone accordingly, and displays the information to the screen.
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For the 57i/57i CT:
1
Click on Operation->Softkeys and XML.
2
Select a key from keys 1 through 20.
3
In the "Type" field, select XML from the list box.
4
In the "Label" field, enter a label that displays on the IP phone for the softkey. For example, "XML".
5
In the "Value" field, enter the IP address or qualified domain name of the XML application.
6
In the "XML Application URI" field, enter the HTTP server path or qualified domain name of the XML
application you want to load to the IP phone. For example, you could enter an XML application called
"http://172.16.96.63/aastra/internet.php" in the applicable field.
7
In the "XML Application Title" field, enter the name of the XML application that you want to display
on the IP phone Services Menu. In the illustration above, the XML Application Title is "Aastra
Telecom".
5-204
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
8
Click
to save your changes.
The XML application is applied to the IP phone immediately.
When the XML application is pushed to the phone via an HTTP POST, a host IP address or domain
name server is required.
9
Click on Advanced Settings->Configuration Server.
10
In the "XML Push Server List (Approved IP Addresses)" field, enter the host IP address and/or
domain name server. You can enter multiple IP address and/or domain name servers (separated by
commas). In the example in Step 8, the illustration shows a host IP address of "10.50.10.53,
10.50.10.54" in the applicable field.
11
Click
to save your changes.
Note: No posting is performed if a session times out.
41-001160-00, Release 2.1, Rev 04
5-205
Operational IP Phone Features
Aastra Web UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
For the 53i
1
Click on Operation->Programmable Keys.
53i Screen
2
For the 53i, select a key from keys 3 through 6.
3
In the "Hard Key" field, select XML from the list box.
4
In the "Value" field, enter the IP address or qualified domain name of the XML application.
5
Click
5-206
to save your changes.
The XML application is applied to the IP phone immediately.
When the XML application is pushed to the phone via an HTTP POST, a host IP address or domain
name server is required.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
6
Click on Advanced Settings->Configuration Server.
7
In the "XML Push Server List (Approved IP Addresses)" field, enter the host IP address and/or
domain name server. You can enter multiple IP address and/or domain name servers (separated by
commas). In the example in Step 6, the illustration shows a host IP address of "10.50.10.53,
10.50.10.54" in the applicable field.
8
Click
to save your changes.
Note: No posting is performed if a session times out.
41-001160-00, Release 2.1, Rev 04
5-207
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Using the XML Customized Service
After you create, save, and configure the IP phone with an XML application, the
customized service is ready for you to use.
Use the following procedure to use the XML feature on the IP phone.
IP Phone UI
Step
Action
For the 55i/57i/57i CT:
1
Press the Services key on the phone to display the Services menu.
2
Select "Custom Features".
3
Use the r and s to scroll through the line items in a menu-driven and directory "Custom
Features" screen.
Message services display to the screen after selecting the "Custom Features" option.
For user input services, follow the prompts as appropriate.
4
5-208
To exit from the "Custom Features" screen, press Exit.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Step
Action
For the 53i:
1
Press the programmable key configured on the phone for XML services.
A "Custom Features" screen displays.
2
Use the r and s to scroll through the customized features.
3
Select a service to display the information for that customized service.
Message services display to the screen after pressing the programmable key.
For user input services, follow the prompts as appropriate.
4
To exit from the "Custom Features" screen, press the XML programmable key again.
XML Action URIs
The IP phones have a feature that allows an administrator to specify a uniform
resource identifier (URI) that triggers a GET when certain events occur. The IP
phone events that support this feature are:
•
Startup
•
Successful registration
•
Incoming call
•
Outgoing call
•
Offhook
•
Onhook
41-001160-00, Release 2.1, Rev 04
5-209
Operational IP Phone Features
IP Phone UI
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
The following table identifies the configurable action URI parameters in the
configuration files and the Aastra Web UI. This table also identifies the variables
that apply to specific parameters.
Configuration File
Parameters
Aastra Web UI Parameters at
Advanced Settings->Action URI
Applicable Variables
action uri startup
Startup
-
action uri registered
Successful Registration
$$SIPUSERNAME$$
$$SIPAUTHNAME$$
$$PROXYURL$$
action uri incoming
Incoming Call
$$REMOTENUMBER$$
$$DISPLAYNAME$$
$$SIPUSERNAME$$
$$INCOMINGNAME$$
action uri outgoing
Outgoing Call
$$REMOTENUMBER$$
$$SIPUSERNAME$$
action uri offhook
Offhook
-
action uri onhook
Onhook
-
How it works
When a startup, successful registration, incoming call, outgoing call,
offhook, or onhook call event occurs on the phone, the phone checks to see if
the event has an action URI configured. If the phones finds a URI configured, any
variables configured (in the form $$VARIABLENAME$$) are replaced with the
value of the appropriate variable. After all of the variables are bound, the phone
executes a GET on the URI. The Action URI binds all variables and is not
dependant on the state of the phone.
For example, if you enter the following string for the action uri outgoing
parameter:
action uri outgoing: http://10.50.10.140/
outgoing.pl?number=$$REMOTENUMBER$$
and you dial out the number 5551212, the phone executes a GET on:
5-210
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
http://10.50.10.140/outgoing.pl?number=5551212
http://10.50.10.140/outgoing.pl?number=
You can configure this feature via the configuration files or the Aastra Web UI.
Configuring XML Action URIs
Use the following procedures to configure XML Action URIs using the
configuration files or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Action URI
Settings” on page A-92.
41-001160-00, Release 2.1, Rev 04
5-211
Operational IP Phone Features
Note: If the phone can’t find the Action URI you specify, it returns a
“NULL” response. For example,
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
1
Click on Advanced Settings->Action URI.
2
Enter an XML URI for a startup event in the “Startup” field. For example:
http://10.50.10.140/startup
This parameter specifies the URI for which the phone executes a GET on when a startup event
occurs.
3
Enter an XML URI for a successful registration in the “Successful Registration” field. For example:
http://10.50.10.14/registered.php?auth name=$$SIPAUTHNAME$$
This parameter specifies the URI for which the phone executes a GET on when a successful
registration event occurs.
Note: For a successful registration event, you can use the following variables in the URI:
• $$SIPUSERNAME$$
• $$SIPAUTHNAME$$
• $$PROXYURL$$
The “Successful Registration” parameter executes on the first successful registration of each
unique line configured on the phone.
5-212
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
4
Enter an XML URI for an incoming call event in the “Incoming Call” field. For example:
http://10.50.10.140/incoming.php?number=$$REMOTENUMBER$$
This parameter specifies the URI for which the phone executes a GET on when an incoming call
event occurs.
Note: For an incoming call event, you can use the following variables in the URI:
• $$REMOTENUMBER$$
• $$DISPLAYNAME$$
• $$SIPUSERNAME$$
• $$INCOMINGNAME$$
5
Enter an XML URI for an outgoing call event in the “Outgoing Call” field. For example:
http://10.50.10.140/outgoing.php?number=$$REMOTENUMBER$$
This parameter specifies the URI for which the phone executes a GET on when an outgoing call
event occurs.
Note: For an outgoing call event, you can use the following variables in the URI:
• $$REMOTENUMBER$$
• $$SIPUSERNAME$$
6
Enter an XML URI for an offhook event in the “Offhook” field. For example:
http://10.50.10.140/offhook
This parameter specifies the URI for which the phone executes a GET on when an offhook event
occurs.
7
Enter an XML URI for an onhook event in the “Onhook” field. For example:
http://10.50.10.140/onhook
This parameter specifies the URI for which the phone executes a GET on when an onhook event
occurs.
8
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-213
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
XML Softkey URI
In addition to specifying variables for the Action URIs, you can also specify
variables in the XML softkey URIs that are bound when the key is pressed. These
variables are the same as those used in the Action URIs.
When an administrator enters an XML softkey URI either via the Aastra Web UI
or the configuration files, they can specify the following variables:
•
$$SIPUSERNAME$$
•
$$SIPAUTHNAME$$
•
$$PROXYURL$$
•
$$REMOTENUMBER$$
•
$$DISPLAYNAME$$
•
$$INCOMINGNAME$$
When the softkey is pressed, if the phone finds a URI configured with variables
(in the form $$VARIABLENAME$$), they are replaced with the value of the
appropriate variable. After all of the variables are bound, the softkey executes a
GET on the URI.
Example
For example, if the administrator specifies an XML softkey with the value:
http://10.50.10.140/script.pl?name=$$SIPUSERNAME$$
This softkey executes a GET on:
http://10.50.10.140/script.pl?name=42512
assuming that the sip username of the specific line is 42512.
You can configure the XML softkey URI variables via the configuration files or
the Aastra Web UI.
5-214
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring XML Softkey URIs
Operational IP Phone Features
Use the following procedures to configure XML Softkey URIs using the
configuration files or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters” on page A-136.
Aastra Web UI
For the 57i/57i CT:
1
Click on Operation->Softkeys and XML.
2
Select a key from keys 1 through 20.
41-001160-00, Release 2.1, Rev 04
5-215
Operational IP Phone Features
IP Phone Administrator Guide
Operational Features
Aastra Web UI
3
In the "Type" field, select XML from the list box.
4
In the "Label" field, enter a label that displays on the IP phone for the XML softkey. For example,
"aastra".
5
In the "Value" field, enter the URI that the phone performs a GET on when the key is pressed. For
example:
http://10.50.10.140/script.pl?name=$$SIPUSERNAME$$
Note: You can use the following variables in the URI:
• $$SIPUSERNAME$$
• $$SIPAUTHNAME$$
• $$PROXYURL$$
• $$REMOTENUMBER$$
• $$DISPLAYNAME$$
• $$INCOMINGNAME$$
6
5-216
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
For the 53i:
1
Click on Operation->Programmable Keys.
53i Screen
2
On the 53i, select a key from keys 1 through 6.
3
In the "Type" field, select XML from the list box.
4
On the 53i, in the "Label" field, enter a label that displays on the IP phone for the XML softkey. For
example, "aastra".
5
In the "Value" field, enter the URI that the phone performs a GET on when the key is pressed. For
example:
http://10.50.10.140/script.pl?name=$$SIPUSERNAME$$
Note: You can use the following variables in the URI:
• $$SIPUSERNAME$$
• $$SIPAUTHNAME$$
• $$PROXYURL$$
• $$REMOTENUMBER$$
• $$DISPLAYNAME$$
• $$INCOMINGNAME$$
6
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-217
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Audio Transmit and Receive Gain Adjustments
The audio gain properties for the IP phone handset, headset, and speakerphone is
adjusted to reduce side-tone and echo on the local and far-end equipment. You can
adjust these settings from -10 db to +10 db to best suit your comfort level and
deployment environment by using the following parameters in the configuration
files:
•
headset tx gain
•
headset sidetone gain
•
handset tx gain
•
handset sidetone gain
•
handsfree tx gain
•
audio mode
The default setting for these parameters is 0 (zero).
Note: Aastra Telecom recommends you leave the default of 0 (zero) as
the settings for these parameters.
The following table describes each parameter.
Parameter
Description
Headset tx gain
The increased (+db) or decreased (-db) amount of signal transmitted from
the headset microphone to t he far-end party.
Headset sidetone gain
The increased (+db) or decreased (-db) amount of sidetone signal from the
headset microphone to the headset speaker.
Handset tx gain
The increased (+db) or decreased (-db) amount of signal transmitted from
the handset microphone to the far-end party.
Handset sidetone gain
The increased (+db) or decreased (-db) amount of sidetone signal from the
handset microphone to the handset speaker.
(continued)
5-218
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Description
Handsfree tx gain
The increased (+db) or decreased (-db) amount of signal transmitted from
the base microphone to the far-end party.
Audio mode
Allows you to configure how the d/f key (handsfree key) works. Audio
mode has 4 options:
0 (Speaker) - Calls can be made or received using the handset or
handsfree speakerphone and can be switched between the two modes by
pressing the d /fkey. When on speaker, you can return to using the
handset by placing the handset on the cradle and picking it up again.
1 (Headset) - Calls can be made or received using the headset. Calls can
be switched between the headset and handset by pressing the d /fkey.
2 (Speaker/Headset) - Incoming calls are sent to the speakerphone. By
pressing the d /fkey, you can switch between the handsfree
speakerphone, the headset, and the handset.
3 (Headset/Speaker) - Incoming calls are sent to the headset. By pressing
the d /fkey, you can switch between the headset, the handsfree
speakerphone, and the handset.
Configuring Audio Transmit and Receive Gain Adjustments
You can configure the audio transmit and gain adjustments using the configuration
files only.
Use the following procedure to configure this feature.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Audio Transmit
and Receive Gain Adjustment Settings” on page A-125.
41-001160-00, Release 2.1, Rev 04
5-219
Operational IP Phone Features
Parameter
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Centralized Conferencing (for Sylantro and Broadsoft Servers)
The IP phones include support for centralized conferencing (Ad-Hoc
conferencing) for Sylantro and Broadsoft servers. This feature provides
centralized conferencing on the SIP server (versus localized, on the phone) and
allows IP phone users to do these tasks:
•
Conference two active calls together into a conference call.
•
When on an active conference call, invite another party into the call.
•
Create simultaneous conference calls on the same IP phone (Sylantro servers
only). For example, the IP phone user at extension 2005 could create these
two conferences, and put one conference on hold while conversing with the
other party:
— Line 1: conference together extensions 2005, 2010, and 2020.
— Line 2: conference together extensions 2005, 2011 and 2021.
When an IP phone user is connected to multiple conference calls, some
outbound proxies have maximum call “hold” time set from 30-90 seconds.
After this time, the call that is on hold is disconnected.
•
Disconnect from an active conference call while allowing the other callers to
remain connected.
•
Ability to create N-way conference.
•
Join two active calls together into a conference call.
•
Incoming or outgoing active call can join any of the existing conferences.
If the administrator does not configure centralized conferencing, then the IP
phone uses localized conferencing by default.
Note: When you configure centralized conferencing globally for an IP
Phone, the global settings apply to all lines. Although, for the global
setting to work on soft lines, the user must configure the lines with the
applicable phone number.
An Administrator can configure centralized conferencing on a global or per-line
basis using the configuration files or the Aastra Web UI.
5-220
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Configuring Centralized Conferencing Using the Configuration Files
You use the following parameters to configure centralized conferencing in the
configuration files:
Global Parameter
•
sip centralized conf
Per-Line Parameter
sip lineN centralized conf
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Centralized
Conferencing Settings” on page A-60.
41-001160-00, Release 2.1, Rev 04
5-221
Operational IP Phone Features
To use the centralized conferencing after it is enabled, see your Model-specific IP
Phone User Guide.
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Configuring Centralized Conferencing Using the Aastra Web UI
Use the following procedure to configure centralized conferencing using the
Aastra Web UI.
Aastra Web UI
Global Configuration
1
Click on Advanced Settings->Global SIP Settings->Basic SIP Network Settings.
2
In the “Conference Server URI” field, do one of the following actions:
•
To disable centralized conferencing on the IP phone, leave this field empty (blank).
•
To enable SIP centralized conferencing on the IP phone, do one of the following actions:
—
If you have specified a proxy server/registrar server, then to reach the media server via the
proxy server, set this field to one of the following:
conf (Sylantro server), or
Conference (Broadsoft server)
By setting this field to conf or Conference, you specify conf@<proxy_server _address>:
<proxy_port>. For example, if the proxy server address is 206.229.26.60 and the port used
is 10060, then by setting this parameter to conf, you are specifying the following:
conf@206.229.26.60:10060.
— To reach the media server using a different address/port than that specified by the proxy,
set this field to the following:
conf@<media_server _address>: <media_port>
5-222
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
3
Click
to save your changes.
Per-Line Configuration
1
Click on Advanced Settings->Line <#>->Basic SIP Network Settings
2
In the “Conference Server URI” field, do one of the following actions:
•
To disable centralized conferencing on this line, leave this field empty (blank).
•
To enable SIP centralized conferencing on this line, do one of the following actions:
— If you have specified a proxy server/registrar server, then to reach the media server via the
proxy server, set this field to one of the following:
conf (Sylantro server), or
Conference (Broadsoft server)
By setting this field to conf or Conference, you specify conf@<proxy_server _address>:
<proxy_port>.
—
To reach the media server using a different address/port than that specified by the proxy,
set this field to the following:
conf@<media_server _address>: <media_port>
3
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
5-223
Operational IP Phone Features
Aastra Web UI
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Customizing the Display Columns on the 560M Expansion Module
The 560M Expansion Module screen displays softkeys in column format. The
function keys on the bottom left of the Module allow you to display 3 full screens
of softkeys. Each screen consists of 2 columns with the following default
headings on each page:
Page 1
"List 1" and "List 2"
Page 2
"List 3" and "List 4"
Page 3
"List 5" and "List 6"
Softkeys
List 1
List 2
Lock/Unlock
BLF 200
Home (speeddial)
(Press for page 1)
(Press for page 2)
Function Keys
(Press for page 3)
Page 1 Screen
5-224
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
List 4
Page 2 Screen
List 5
List 6
Page 3 Screen
To use the 560M, press the function key for the page you want to display to the
LCD (page 1, page2, or page 3), and press the applicable softkey.
You can customize the headings on each 560M Expansion Module screen using
the configuration files. You use the following parameters to customize the column
headings:
Expansion Module 1 (3 pages)
•
expmod1page1left
•
expmod1page1right
•
expmod1page2left
•
expmod1page2right
•
expmod1page3left
•
expmod1page3right
Expansion Module 2 (3 pages)
•
expmod2page1left
•
expmod2page1right
•
expmod2page2left
•
expmod2page2right
•
expmod2page3left
•
expmod2page3right
41-001160-00, Release 2.1, Rev 04
5-225
Operational IP Phone Features
List 3
IP Phone Administrator Guide
Operational Features
Operational IP Phone Features
Expansion Module 3 (3 pages)
5-226
•
expmod3page1left
•
expmod3page1right
•
expmod3page2left
•
expmod3page2right
•
expmod3page3left
•
expmod3page3right
Example
The following is an example of configuring Expansion Module 1 column
headings.
expmod1page1left: Personnel Ext
expmod1page1right: Operations Ext
expmod1page2left: Marketing Ext
expmod1page2right: Logistics Ext
expmod1page3left: Engineering Ext
expmod1page3right: Shipping Ext
41-001160-00, Release 2.1, Rev 04
Configuring Operational Features
Operational Features
Personnel Ext
Marketing Ext
Operations Ext
Page 1 Screen
Operational IP Phone Features
These settings display to the Expansion Module as shown in the following
illustrations.
Logistics Ext
Page 2 Screen
Engineering Ext Shipping Ext
Page 3 Screen
Cuztomizing the 560M Expansion Module Column Display.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Customizing 560M Expansion Module Column Display” on page A-166.
41-001160-00, Release 2.1, Rev 04
5-227
About this chapter
Introduction
The IP phones have advanced operational features you can configure using the
configuration files and/or the Aastra Web UI.
This chapter describes each of these features and provides procedures for
configuring each feature.
Topics
This chapter covers the following topics:
Topic
Page
Advanced Operational Features
page 6-3
MAC Address/Line Number in REGISTER Messages
page 6-5
SIP Message Sequence for Blind Transfer
page 6-7
Update Caller ID During a Call
page 6-8
Boot Sequence Recovery Mode
page 6-9
Auto-discovery Using mDNS
page 6-10
Single Call Restriction (57i CT only)
page 6-11
Missed Call Summary Subscription
page 6-13
Blacklist Duration (Broadsoft Servers)
page 6-17
41-001160-00, Release 2.1, Rev 04
6-1
Advanced Operational Features
Chapter 6
Configuring Advanced
Operational Features
IP Phone Administrator Guide
About this chapter
Advanced Operational Features
Topic
6-2
Page
Whitelist Proxy
page 6-19
Transport Layer Security (TLS)
page 6-21
Symmetric UDP Signaling
page 6-27
Removing UserAgent and Server SIP Headers
page 6-28
Multi-Stage Digit Collection (Billing Codes) Support (for Sylantro
Servers)
page 6-29
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Advanced Operational Features
This section provides the following information about advanced features of the IP
phones:
Feature
Description
MAC Address/Line Number in REGISTER
Messages
Allows you to enable or disable the sending of the MAC
address and line number from the IP phone to the call
server, in a REGISTER message.
SIP Message Sequence for Blind Transfer
Allows you to enable or disable the phone to use the Blind
Transfer method available in software prior to release 1.4.
Update Caller ID During a Call
Allows you to enable or disable the updating of the Caller ID
information during a call.
Boot Sequence Recovery Mode
Allows you to enable or disable Web recovery mode and set
the maximum boot count on the IP phone.
Auto-discovery Using mDNS
The IP phones automatically perform an auto-discovery of all
servers on a network using mDNS. When the IP phone
discovers a TFTP server, it is automatically configured by
that TFTP server.
Single Call Restriction (57i CT only)
Allows you to enable or disable a single call restriction
between the 57i CT base unit and a call server.
Missed Call Summary Subscription
Allows missed calls that have been redirected by the server,
to be incremented in the missed calls indicator on the phone
it was initially directed to.
Blacklist Duration (Broadsoft Servers)
Allows you to specifies the length of time, in seconds, that a
failed server remains on the server blacklist. The IP phone
avoids sending a SIP message to a failed server (if another
server is available) for this amount of time.
Whitelist Proxy
Allows you to configure the phone to either accept or reject
call requests from a trusted proxy server.
41-001160-00, Release 2.1, Rev 04
6-3
Advanced Operational Features
Description
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
Feature
Description
Transport Layer Security (TLS)
Allows you to enable or disable the use of Persistent
Transport Layer Security (TLS).
Persistent TLS sets up the connection to the server once
and re-uses that connection for all calls from the phone. The
setup connection for Persistent TLS is established during the
registration of the phone. If the phones are set to use
Persistent TLS, and a call is made from the phone, this call
and all subsequent calls use the same authenticated
connection. This significantly reduces the delay time when
placing a call.
Symmetric UDP Signaling
Allows you to enable or disable the phone to use port 5060
to send SIP UDP messages.
Removing UserAgent and Server SIP
Headers
Allows you to enable or disable the addition of the
User-Agent and Server SIP headers in the SIP stack.
Multi-Stage Digit Collection (Billing Codes)
Support (for Sylantro Servers)
IP Phones support Sylantro Server features, like mandatory
and optional billing codes that require the application server
to notify the phone to collect more digits before completing
the call. The IP phone is able to collect digits in two stages to
support the billing code feature.
6-4
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
MAC Address/Line Number in REGISTER Messages
Aastra-Mac: <mac address>
Aastra-Line: <line number>
The MAC address is sent in uppercase hex numbers, for example,
00085D03C792. The line number is a number between 1 and 9.
The following parameters allow you to enable/disable the sending of MAC
address and line number to the call server:
•
sip send mac
•
sip send line
These parameters are disabled by default. The parameters are configurable via the
configuration files or the Aastra Web UI.
Configuring the MAC address/Line Number in REGISTER Message
Configuration Files
For specific parameters you can set in the configuration files for enabling/disabling MAC address and line
number, see Appendix A, the section, “Advanced Operational Parameters” on page A-172.
41-001160-00, Release 2.1, Rev 04
6-5
Advanced Operational Features
The IP phones can send the MAC address and line number in the REGISTER
packets making it easier for the call server when a user configures the phones via
the Aastra Web UI or the IP Phone UI. The following two configurable headers
send this information to the call server:
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
.
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Global SIP->Advanced SIP Setting.
2
Enable the "Send MAC Address in REGISTER Message" field by checking the check box.
(Disable this field by unchecking the box).
3
Enable the "Send Line Number in REGISTER Message" field by checking the check box.
(Disable this field by unchecking the box).
4
Click
to save your settings.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
5
6-6
Select Operation->Reset and click
.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
SIP Message Sequence for Blind Transfer
The following parameter allows the system administrator to force the phone to use
the Blind Transfer method available in software versions prior to 1.4:
sip cancel after blind transfer
This parameter is configurable via the configuration files only.
Configuring SIP Message Sequence for Blind Transfer
Configuration Files
For the specific parameter you can set in the configuration files for enabling/disabling the blind transfer
method, see Appendix A, the section, “Blind Transfer Setting” on page A-172.
41-001160-00, Release 2.1, Rev 04
6-7
Advanced Operational Features
The SIP message sequence for Blind Transfer avoids the transfer target having
two simultaneous calls. Prior to release 1.4, a CANCEL message was sent to the
transfer target (if it was in a ringing state) after sending a REFER to the transferee
to complete the transfer. In the 1.4 and later releases, the CANCEL is now sent
before the REFER message.
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Update Caller ID During a Call
It is possible for a proxy or call server to update the Caller ID information that
displays on the phone during a call, by modifying the SIP Contact header in the
200 OK message and/or in a re-INVITE message. The phone displays the
updated name and number information contained within the Contact header.
The following parameter allows the system administrator to enable or disable this
feature:
sip update callerid:
This parameter is configurable via the configuration files only.
Configuring Update Caller ID During a Call
Configuration Files
For the specific parameter you can set in the configuration files for enabling/disabling the update of caller ID
during a call, see Appendix A, the section, “Update Caller ID Setting.” on page A-173.
6-8
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Boot Sequence Recovery Mode
You can disable this feature using the following parameter in the configuration
files:
•
force web recovery mode disabled
Valid values for this parameter are 0 (false) and 1 (true). Default is 0 (false).
A boot counter increments after each faulty boot. When the counter reaches a
predetermined value, it forces Web recovery mode. The counter is reset to zero
upon a successful boot.
The predetermined value is set using the following parameter in the configuration
files:
•
max boot count
A zero (0) value disables this feature. The default value is 10.
You can configure the boot sequence recovery mode parameters using the
configuration files only.
Configuring Boot Sequence Recovery Mode
Configuration Files
For the specific parameters you can set in the configuration files for boot sequence recovery mode, see
Appendix A, the section, “Boot Sequence Recovery Mode.” on page A-173.
41-001160-00, Release 2.1, Rev 04
6-9
Advanced Operational Features
You can force the IP phone into recovery mode by pressing the 1 and # keys
during boot up when the logo displays. This feature is enabled by default on the IP
phone.
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Auto-discovery Using mDNS
6-10
The IP phones can perform an auto-discovery of all servers on a network using
mDNS. When the IP phone discovers a TFTP server, it is automatically
configured by that TFTP server.
An unconfigured phone (phone right out of the box) added to a network, attempts
to auto-discover a configuration server on the network without any end-user
intervention. When it receives DHCP option 66 (TFTP server), it automatically
gets configured by the TFTP server.
An already configured phone (either previously configured by auto-discovery or
manually configured) added to a network, uses its predefined configuration to
boot up.
Notes:
1. Configuration parameters received via DHCP do not constitute
configuration information, with the exception of a TFTP server.
Therefore, you can plug a phone into a DHCP environment, still use the
auto-discovery process, and still allow the use of the TFTP server
parameter to set the configuration server.
2. DHCP option 66 (TFTP server details) overrides the mDNS phase of
the auto-discovery. Therefore, the DHCP option takes priority and the
remaining process of auto-discovery continues.
3. As the phone performs auto-discovery, all servers in the network
(including the TFTP server), display in the phone window. However, only
the server configured for TFTP automatically configures the phone.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Single Call Restriction (57i CT only)
When this feature is enabled (set to 1), you can make separate active calls from
the 57i CT base unit and from the cordless handset. If this feature is disabled (set
to 0), only one call can be active at a time either from the base unit or from the
handset. When this feature is disabled, and you make an active call on either the
base unit or the handset, any other attempt to make an active call is put on hold.
Also, when this feature is disabled, more than one call can negotiate complex
audio codecs since only a single call is decoding audio at a time.
You can configure this feature via the configuration files or the Aastra Web UI.
Configuring Single Call Restriction.
Configuration Files
For the specific parameters you can set in the configuration files for single call restriction on the 57i CT, see
Appendix A, the section, “Single Call Restriction” on page A-174.
41-001160-00, Release 2.1, Rev 04
6-11
Advanced Operational Features
On the 57i CT, an administrator can enable or disable a single call restriction
between the 57i CT base unit and a call server.
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Global SIP->RTP Settings.
2
Enable the "Two Call Support" field by checking the check box.
(Disable this field by unchecking the box).
3
Click
to save your settings.
Note: The session prompts you to restart the IP phone to apply the configuration settings.
4
6-12
Select Operation->Reset and click
.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Missed Call Summary Subscription
For example, phones A, B, and C are connected to the server. You configure the
server to direct calls coming into phone B (which has voicemail configured) to be
forwarded to phone C. When phone A calls phone B, the server forwards the call
to phone C. With the new feature in 2.1, phone B receives notification from the
server that the call was forwarded and the missed calls indicator is incremented on
phone B.
3KRQH$
$FDOOV%
3KRQH&
3KRQH%
%IRZDUGVFDOOWR&
0LVVHGFDOOVLQGLFDWRULQFUHPHQWVRQSKRQH%
9RLFHPDLOPXVWEHFRQILJXUHGRQSKRQH%
1RWH
An Administrator can configure this feature on a global or per-line basis, using the
configuration files or the Aastra Web UI
41-001160-00, Release 2.1, Rev 04
6-13
Advanced Operational Features
The “Missed Call Summary Subscription” feature allows missed calls that have
been redirected by the server, to be incremented in the missed calls indicator on
the phone it was initially directed to. This feature is called the Missed Call
Summary Subscription and can be set with a timer that allows the phone to use the
feature for a period of time before the timer expires. For this feature to work, you
must configure voicemail on the phone that the call was initially directed to.
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
Configuring Missed Call Summary Subscription using the
Configuration Files
In addition to enabling/disabling the Misses Call Summary Subscription, You can
also configure the amount of time, in seconds, that the phone uses this feature.
The timer is configurable on a global basis only.
You use the following parameters to configure Missed Call Summary
Subscription feature on a global basis:
Global Parameters
•
sip missed call summary subscription
•
sip missed call summary subscription period
Use the following parameters to configure Missed Call Summary Subscription
feature on a per-line basis:
Per-Line Parameter
•
sip lineN missed call summary subscription
Configuration Files
For the specific parameters you can set in the configuration files for Missed Call Summary Subscription, see
Appendix A, the section, “Missed Call Summary Subscription Settings” on page A-70.
6-14
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Use the following procedure to configure the Missed Call Summary Subscription
feature using the Aastra Web UI.
Aastra Web UI
Global Configuration
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings.
41-001160-00, Release 2.1, Rev 04
6-15
Advanced Operational Features
Configuring Missed Call Summary Subscription using the
Aastra Web UI
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
Aastra Web UI
2
The "Missed Call Summary Subscription" field is disabled by default. To enable this field, check
the box.
This feature allows missed calls that have been redirected by the server, to be incremented in the
missed calls indicator on the phone it was initially directed to. For example, phones A, B, and C are
connected to the server. You configure the server to direct calls coming into phone B (which has
voicemail configured) to be forwarded to phone C. When phone A calls sip missed call summary
subscription parameter, phone B receives notification from the server that the call was forwarded
and the missed calls indicator is incremented on phone B.
Note: You must configure voicemail on the phone that the call was initially directed to (phone B in the
above example).
3
The "Missed Call Summary Subscription Period" field is enabled with a default value of 86400. To
disable this field, enter zero (0), or leave the field blank.
4
Click
to save your changes.
Per-Line Configuration
1
Click on Advanced Settings->Line <N>->Advanced SIP Settings.
2
Click
6-16
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Blacklist Duration (Broadsoft Servers)
You can specify how long failed servers remain on the blacklist in the IP phone’s
configuration file or in the Aastra Web UI. The default setting is 300 seconds. If
you set the duration to 0 seconds, then you disable the blacklist feature.
Configuring Blacklist Duration Using the Configuration Files
Use the following parameter to configure the Blacklist Duration in the
configuration files:
•
sip blacklist duration
Configuration Files
For the specific parameters you can set in the configuration files for setting Blacklist Duration, see Appendix
A, the section, “Transport Layer Security (TLS) Settings” on page A-72.
41-001160-00, Release 2.1, Rev 04
6-17
Advanced Operational Features
The Blacklist Duration feature on Broadsoft Servers helps to reduce unnecessary
delays during proxy/registrar server failures, caused by the IP phone repeatedly
sending SIP messages to a failed server. If you enable this feature, then whenever
the IP phone sends a SIP message to a server, and does not get a response, the
phone automatically adds the server to the blacklist. The IP phone avoids sending
messages to any servers on the blacklist. If all servers are on the blacklist, then the
IP phone attempts to send the message to the first server on the list.
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Configuring a Server Blacklist Using the Aastra Web UI
You use the following procedure to configure Blacklist Duration using the Aastra
Web UI.
Aastra Web UI
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings
2
In the “Blacklist Duration” field, specify the length of time, in seconds, that a failed server remains
on the server blacklist. The IP phone avoids sending a SIP message to a failed server (if another
server is available) for this amount of time. Valid values are 0 to 9999999. Default is 300 seconds (5
minutes).
For example: 600
Note: The value of “0” disables the blacklist feature.
3
6-18
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Whitelist Proxy
Configuring Whitelist Proxy Using the Configuration Files
You use the following parameter to configure the whitelist proxy feature using the
configuration files:
•
sip whitelist
Configuration Files
For the specific parameters you can set in the configuration files for setting Whitelist Proxy, see Appendix A,
the section, “Whitelist Proxy” on page A-175.
41-001160-00, Release 2.1, Rev 04
6-19
Advanced Operational Features
To protect your IP phone network, you can configure a “Whitelist Proxy” feature
that screens incoming call requests received by the IP phones. When this feature is
enabled, an IP phone accepts call requests from a trusted proxy server only. The IP
phone rejects any call requests from an untrusted proxy server
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Configuring Whitelist Proxy Using the Aastra Web UI
Use the following procedure to configure the Whitelist Proxy feature using the
Aastra Web UI.
Aastra Web UI
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings
2
The "Whitelist Proxy" field is disabled by default. To enable this field, check the box.
When this feature is enabled, an IP phone accepts call requests from a trusted proxy server only. The
IP phone rejects any call requests from an untrusted proxy server.
3
6-20
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Transport Layer Security (TLS)
TLS is composed of two layers: the TLS Record Protocol and the TLS handshake
protocol. The TLS Record Protocol provides connection security with some
encryption method such as the Data Encryption Standard (DES). The TLS
Handshake Protocol allows the server and client to authenticate each other and to
negotiate an encryption algorithm and cryptographic keys before data is
exchanged. TLS requires the use of specific security certificate files to perform
TLS handshake:
•
Root and Intermediate Certificates
•
Local Certificate
•
Private Key
•
Trusted Certificate
When the phones use TLS to authenticate with the server, each individual call
must setup a new TLS connection. This can take more time when placing each
call. Thus, the IP phones also have a feature that allows you to setup the
connection to the server once and re-use that one connection for all calls from the
phone. It is called Persistent TLS. The setup connection for Persistent TLS is
established during the registration of the phone. If the phones are set to use
Persistent TLS, and a call is made from the phone, this call and all subsequent
calls use the same authenticated connection. This significantly reduces the delay
time when placing a call.
41-001160-00, Release 2.1, Rev 04
6-21
Advanced Operational Features
The IP Phones support a transport protocol called Transport Layer Security
(TLS) and Persistent TLS. TLS is a protocol that ensures communication
privacy between the SIP phones and the Internet. TLS ensures that no third party
may eavesdrop or tamper with any message.
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
6-22
Notes:
1.
Persistent TLS requires the outbound proxy server and outbound
proxy port parameters be configured in either the configuration files or
the Aastra Web UI (Advanced Settings->Global SIP->Basic SIP Network
Settings). There can be only one persistent TLS connection created per
phone. The phone establishes the TLS connection to the configured
outbound proxy.
2.
If you configure the phone to use Persistent TLS, you must also
specify the Trusted Certificate file to use. The Root and Intermediate
Certificates, Local Certificate, and Private Key files are optional.
On the IP phones, an Administrator can configure TLS and Persistent TLS on a
global-basis only, using the configuration files or the Aastra Web UI.
SIP Asserted Identity (for Sylantro Servers)
The IP Phones support a private extension to the SIP, Asserted Identity (SAI)
within Trusted Networks (as defined in RFC 3325), inside the User Agent Server
(UA) in the Aastra IP phones.
This feature allows a network of trusted SIP servers to assert the identity of
authenticated users, and verify that phone messages originate from a Trusted
Identity. Upon receiving a message from a caller in the Trust Network, the IP
phone reads the contents of the P-Asserted-Identity (PAI) header field and
displays it on the phone UI. This field contains a more accurate description of the
caller identity (extension/phone number) than is contained in the SIP message.
When an IP phone receives an incoming call, the IP phone does the following
actions:
•
Checks to see if the incoming call is from a registered proxy server.
•
If the call is forwarded via a registered proxy server, then the message has
already been verified and authenticated by the server. The caller is part of the
Trust Network. The IP phone UI displays the caller information contained in
the PAI header.
•
If the call is not forwarded via a registered proxy server - and therefore is not
a “Trusted Entity” - the IP phone UI does not display any trust information
contained in the PAI header.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Configuring TLS Using the Configuration Files
Advanced Operational Features
You use the following parameters to configure TLS in the configuration files:
•
sip transport protocol
•
sips persistent tls
•
sips root and intermediate certificates
•
sips local certificate
•
sips private key
•
sips trusted certificates
Configuration Files
For the specific parameters you can set in the configuration files for setting TLS, see Appendix A, the
section, “Transport Layer Security (TLS) Settings” on page A-72.
41-001160-00, Release 2.1, Rev 04
6-23
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Configuring TLS Using the Aastra Web UI
To configure TLS using the Aastra Web UI, you must enable TLS or Persistent
TLS first. Then you must define the TLS certificate file names that you want the
phone to use. Use the following procedure to configure TLS using the Aastra Web
UI.
Aastra Web UI
1
Click on Advanced Settings->Global SIP->Advanced SIP Settings.
2
In the "Transport Protocol" field, select TLS or Persistent TLS.
Note: If configuring Persistent TLS, you must go to Advanced Settings->Global SIP->Basic Network
Settings and configure the “Outbound Proxy Server” and “Outbound Proxy Port” parameters.
3
6-24
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
4
Advanced Operational Features
Aastra Web UI
Click on Advanced Settings->TLS Support.
41-001160-00, Release 2.1, Rev 04
6-25
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
Aastra Web UI
5
Enter the certificate file names and the private key file name in the appropriate fields.
The Root and Intermediate Certificate files contain one root certificate and zero or more intermediate
certificates which must be placed in order of certificate signing with root certificate being the first in
the file. If the local certificate is signed by some well known certificate authority, then that authority
provides the user with the Root and Intermediate Certificate files (most likely just CA root certificate).
The Trusted Certificate files define a list of trusted certificates. The phone’s trusted list must contain
the CA root certificates for all the servers it is connecting to. For example, if the phone is connecting
to server A which has a certificate signed by CA1, and server B which has a certificate signed by
CA2, the phone must have CA1 root certificate and CS2 root certificate in its Trusted Certificate file.
Notes:
1. If configuring TLS, you must specify the files for Root and Intermediate Certificates, the Local
Certificate, the Private Key, and the Trusted Certificates in order for the phone to receive calls.
2. If configuring Persistent TLS, you must specify the Trusted Certificates (which contains the trusted
certificate list). All other certificates and the Private Key are optional.
3. The certificate files and Private Key file names must use the format “.pem”.
4. To create custom certificate files and private key files to use on your IP phone, contact Aastra
Technical Support.
6
6-26
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Symmetric UDP Signaling
You can manually disable symmetric UDP signaling using the IP phone’s
configuration file. When you disable symmetric UDP signaling, then the IP phone
chooses a random source port for UDP messages.
The IP phone also chooses a random source port for UDP messages if you
configure a backup proxy server, registrar server, or outbound proxy server.
An Administrator can configure symmetric UDP signaling using the configuration
files only.
Configuring Symmetric UDP Signaling Using the Configuration Files
You use the following parameter to enable or disable Symmetric UDP Signaling
in the configuration files:
•
sip symmetric udp signaling
Configuration Files
For the specific parameter you can set in the configuration files, see Appendix A, the section, “RTP, Codec,
DTMF Global Settings” on page A-77.
41-001160-00, Release 2.1, Rev 04
6-27
Advanced Operational Features
By default, the IP phones use symmetric UDP signaling for outgoing UDP SIP
messages. When symmetric UDP is enabled, the IP phone generates and listens
for UDP messages using port 5060.
IP Phone Administrator Guide
Advanced Operational Features
Advanced Operational Features
Removing UserAgent and Server SIP Headers
Currently, the phone always configures the SIP UserAgent/Server headers to
contain:
Aastra <PhoneModel>/<FirmwareVersion>
You can suppress the addition of these headers by using the following parameter
in the configuration files:
•
sip user-agent
Setting this parameter allows you to enable or disable the addition of the
User-Agent and Server SIP headers from the SIP stack.
You can configure this feature using the configuration files only.
Configuring UserAgent/Server SIP Headers
You use the following parameter to specify whether the UserAgent and Server SIP
header is added to the SIP stack.
•
sip user-agent
Configuration Files
For the specific parameter you can set in the configuration files, see Appendix A, the section, “User-Agent
Setting” on page A-176.
6-28
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
The IP Phones support Multi-Stage Digit Collection (billing codes) for Sylantro
Servers. Sylantro Server features, like mandatory and optional billing codes,
requires that the application server notify the phone to collect more digits before
completing the call. The IP phone is able to collect digits in two stages to support
the billing code feature.
Aastra IP Phone users are prompted to enter the correct billing code when they
dial these numbers:
•
External numbers.
•
Eternal numbers dialed using a Speeddial key.
Billing Codes Implementation Notes
Note the following implementation information:
•
IP phone users may enter a 2-9 digit billing code. Billing codes may not start
with either 0 (Operator) or 9 (external calls).
•
When using Sylantro Click-to-Call, IP phone users select a billing code from
a pull-down menu.
•
When placing a call, a secondary dial tone alerts IP phone users to enter the
billing code. The IP phone UI also displays a “Enter Billing Code” message.
•
If an IP phone user redials a number, they do not have to re-enter the billing
code. The billing code information is maintained and processed accordingly.
•
If an IP phone user enters an invalid billing code, the call fails.
Mandatory versus Optional Billing Codes
This release of the Aastra IP phones supports two types of billing codes:
Mandatory and Optional. The Sylantro server configuration determines which
type of billing code is used on the IP phones.
•
Mandatory billing codes: Calls are not connected until the user enters a valid
billing code. The user dials the phone number. When prompted for billing
codes, user dials the billing code.
41-001160-00, Release 2.1, Rev 04
6-29
Advanced Operational Features
Multi-Stage Digit Collection (Billing Codes) Support (for Sylantro
Servers)
Advanced Operational Features
IP Phone Administrator Guide
Advanced Operational Features
For example, suppose the IP phone user is using billing code 300, and dialing
the external number 617-238-5500. The IP user then enters the number using
the following format:
6172385000#300
Using mandatory billing codes, if the user is configuring a Speeddial number,
then they enter the number using the following format:
<phonenumber>%23<billingcode>
To use this format with the default dial plan terminator (#), the # sign required
by Sylantro as a delimiter should be represented as an escaped character by
using the sequence %23. The speed dial format for an external number that
includes a mandatory billing code becomes:
<phonenumber>%23<billing code>
•
Optional billing codes: The user dials an optional billing code by dialing
*50, followed by the billing code digits. When prompted for additional digits,
user enters the phone number.
For example, suppose the IP phone user is using billing code 500, and dialing
the external number 617-238-5000. The IP user then enters the number using
the following format:
*50500#6172385000
If the user is dialing configuring a Speeddial number, then they enter the
number using the following format:
*50<billingcode>#<phonenumber>
To use this format with the default dial plan terminator (#), the # sign
required by Sylantro as a delimiter should be represented as an escaped
character by using the sequence %23. The speed dial format for an
external number that includes an optional billing code becomes:
*50<billing code>%23<phone number>
6-30
41-001160-00, Release 2.1, Rev 04
Configuring Advanced Operational Features
Advanced Operational Features
Numbers Not Requiring Billing Codes
Advanced Operational Features
Billing codes are not required for the following two types of calls:
•
Emergency calls (E911)
•
Calls between extensions
41-001160-00, Release 2.1, Rev 04
6-31
About this chapter
Introduction
This chapter provides information about encryption on the IP phones and provides
methods an administrator can use to store encrypted files to a server.
Topics
This chapter covers the following topics:
Topic
Page
Encrypted Files on the IP Phone
page 7-2
Configuration File Encryption Method
page 7-2
Procedure to Encrypt/Decrypt Configuration Files
page 7-3
41-001160-00, Release 2.1, Rev 04
7-1
Encryption and the IP Phone
Chapter 7
Encrypted Files on the IP Phone
IP Phone Administrator Guide
Encrypted Files on the IP Phone
Encryption and the IP Phone
Encrypted Files on the IP Phone
An encryption feature for the IP phone allows Service Providers the capability of
storing encrypted files on their server to protect against unauthorized access and
tampering of sensitive information (i.e., user accounts, login passwords,
registration information). Service Providers also have the capability of locking a
phone to use a specific server-provided configuration only.
Configuration File Encryption Method
Only a System Administrator can encrypt/decrypt the configurations files for an
IP Phone.
System Administrators use a password distribution scheme to manually
pre-configure or automatically configure the phones to use the encrypted
configuration with a unique key.
From a Microsoft Windows command line, the System Administrator uses an
Aastra-supplied encryption tool called "anacrypt.exe".
Note: Aastra also supplies encryption tools to support Linux platforms
(anacrypt.linux) and Solaris platforms (anacrypt.sunos) if required.
This tool processes the plain text <mac>.cfg and aastra.cfg files and creates
triple-DES encrypted versions called <mac>.tuz and aastra.tuz. Encryption is
performed using a secret password that is chosen by the administrator.
The encryption tool is also used to create an additional encrypted tag file called
security.tuz, which controls the decryption process on the IP phones. If
security.tuz is present on the TFTP/FTP/HTTP server, the IP phones download it
and use it locally to decrypt the configuration information from the aastra.tuz and
<mac>.tuz files. Because only the encrypted versions of the configuration files
need to be stored on the server, no plain-text configuration or passwords are sent
across the network, thereby ensuring security of the configuration data.
7-2
41-001160-00, Release 2.1, Rev 04
Encrypted Files on the IP Phone
Encrypted Files on the IP Phone
Note: If the use of encrypted configuration files is enabled (via
security.tuz or pre-provisioned on the IP phone) the aastra.cfg and
<mac>.cfg files are ignored, and only the encrypted equivalent files
aastra.tuz and <mac>.tuz are read.
Procedure to Encrypt/Decrypt Configuration Files
To encrypt the IP phone configuration files:
1.
Open a command line window application (i.e., DOS window).
2.
At the prompt, enter anacrypt.exe and press <Return>.
C:\> anacrypt.exe -h
Provides encryption and decryption of the configuration files used for the family
of Aastra IP phones, using 56bit triple-DES and site-specific keys.
Copyright (c) 2005, Aastra Technologies, Ltd.
Copyright (c) 1999, Philip J. Erdelsky
Usage:
anacrypt infile.{cfg|tuz} [-o outfile] [-p password] [-h]
[-v] Display version number
[-h] Display program help text
[-o [device:][path]] Writes output file on specific device or path
[-p password] Password used to generate the cryptographic key
Restrictions:
Infile extension determines operation, .cfg=plaintext to be encrypted,
.tuz=ciphertext to be decrypted. Outfile extension is opposite of input.
Filenames may optionally include any non-wildcard subset of [device:][\path\].
If -p is omitted, user is prompted to interactively enter the password.
Note: 3DES does not validate decryption, incorrect password produces garbage. For
site-specific keyfile security.cfg the plaintext must match password.
41-001160-00, Release 2.1, Rev 04
7-3
Encryption and the IP Phone
To make changes to the configuration files, the System Administrator must
decrypt the files, make the changes, and re-encrypt the files. The encrypted files
must then be downloaded to the IP phones again.
IP Phone Administrator Guide
Encrypted Files on the IP Phone
Encryption and the IP Phone
Examples
The following examples illustrate the use of the anacrypt.exe file.
Example 1
Encrypt aastra.cfg into aastra.tuz using password 1234abcd:
C:\> anacrypt aastra.cfg -p 1234abcd
Example 2
Decrypt aastra.tuz into aastra.cfg prompting user for password:
C:\> anacrypt aastra.tuz
Example 3
Decrypt mac.tuz using password 1234abcd, display plaintext on console:
C:\> anacrypt aastra.tuz -o CON: -p 1234abcd
Example 4
Encrypt a site-specific keyfile prompting user for password and write the
encrypted file directly into the TFTP server root directory:
C:\> anacrypt security.cfg -o d:\tftp\root
Example 5
Encrypt all config files in C:\data using password 1234abcd and write the
encrypted files directly into the TFTP server root directory:
C:\> FOR %a IN (C:\data\*.cfg) DO "anacrypt %a -o
d:\tftp\root -p 1234abcd"
Example 6
Decrypt all config files in the TFTP root directory using password 1234abcd and
write the resulting plaintext into the Windows temporary directory:
C:\> FOR %a IN (d:\tftp\root\*.tuz) DO "anacrypt %a -o
%TEMP% -p 1234abcd"
7-4
41-001160-00, Release 2.1, Rev 04
Encrypted Files on the IP Phone
Encrypted Files on the IP Phone
Example 7
Encryption and the IP Phone
Use the "-v" variable to display version number.
C:\> anacrypt -v
The encryption tag format supported by this anacrypt is: Tuzo v1.3 rev1
The corresponding IP phone firmware build is: 20051017
41-001160-00, Release 2.1, Rev 04
7-5
About this chapter
Introduction
This chapter provides information about upgrading the IP phone firmware.
Topics
This chapter covers the following topics:
Topic
Page
Upgrading the Firmware
page 8-2
Manual Firmware Update (TFTP only)
page 8-2
Manual Firmware and Configuration File Update
page 8-4
Automatic Update (auto-resync)
page 8-6
41-001160-00, Release 2.1, Rev 04
8-1
Firmware Upgrade
Chapter 8
Upgrading the Firmware
IP Phone Administrator Guide
Upgrading the Firmware
Firmware Upgrade
Upgrading the Firmware
The IP phone uses a TFTP, FTP, or HTTP server (depending on the protocol
configured on the IP phone) to download configuration files and firmware.
The configuration server should be ready and be able to accept connections. For
information on setting up the configuration server, see Chapter 1, the section,
“Configuration Server Requirement” on page 1-20.
You can download the firmware stored on the configuration server in one of three
ways:
•
Manual firmware update using the Aastra Web UI (TFTP only).
•
Manual update of firmware and configuration files (by restarting the phone
via the IP phone UI or the Aastra Web UI).
•
Automatic update of firmware, configuration files, or both at a specific time
in a 24-hour period (via the configuration files or the Aastra Web UI).
Manual Firmware Update (TFTP only)
Use the following procedure to activate a firmware download using TFTP.
Warning: Do not reset or turn off the phone until the download is
complete.
Note: This procedure allows you to download the <phone model.st> file
from a TFTP server even if your phone is configured to use HTTP or FTP.
8-2
41-001160-00, Release 2.1, Rev 04
Upgrading the Firmware
Upgrading the Firmware
Firmware Upgrade
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Firmware Update.
2
Enter the TFTP server IP address or qualified domain name in the "TFTP Server IP" field.
3
Enter the firmware file name (<phone model>.st) that you want to download to your IP phone in the
"File Name" field. For example, 53i.st.
This file name must match the actual name of the firmware file residing on your configuration server.
4
Click
.
This starts the upgrade process. If the upgrade is successful the following message displays on the
screen: "Firmware Upgrade Successful".
41-001160-00, Release 2.1, Rev 04
8-3
IP Phone Administrator Guide
Upgrading the Firmware
Firmware Upgrade
Manual Firmware and Configuration File Update
Restarting the phone forces the phone to check for both firmware and
configuration files stored on the configuration server.
Warning: Do not reset or turn off the phone until the download is
complete.
Restarting the Phone Using the IP Phone UI
IP Phone UI
Step
Action
1
Press
2
Select Restart Phone.
3
For 53i:
Press # to confirm.
on the phone to enter the Options List.
Note: To cancel the Restart, press the 3 key.
For 55i, 57i, 57i CT:
Press Restart.
Note: To cancel the Restart, press Cancel.
8-4
41-001160-00, Release 2.1, Rev 04
Upgrading the Firmware
Upgrading the Firmware
Restarting the Phone Using the Aastra Web UI
Firmware Upgrade
Aastra Web UI
1
Click on Operation->Reset->Phone.
2
Click
to restart the phone.
41-001160-00, Release 2.1, Rev 04
8-5
IP Phone Administrator Guide
Upgrading the Firmware
Firmware Upgrade
Automatic Update (auto-resync)
The auto-resync feature on the IP phones 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).
Note: The automatic update feature works with both encrypted and plain
text configuration files.
When configuring via the Aastra Web UI, the administrator sets the following
parameters:
Mode Time
The Mode parameter determines the type of update that the IP phone performs:
configuration file only, firmware only, or both.
The Time parameter sets the period of time for which the IP phone is
automatically updated.
When configuring via the configuration files, the following parameters must be
set:
8-6
•
auto-resync mode
•
auto-resync time
41-001160-00, Release 2.1, Rev 04
Upgrading the Firmware
Upgrading the Firmware
Configuring Automatic Update
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. If the IP phone is in use (not idle) at the time of the resync check, the
reboot occurs when the phone becomes idle.
4.
The resync time is based on the local time of the IP phone.
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. This prevents
several phones from accessing the server at the exact same time.
Configuration Files
For specific parameters you can set in the configuration files for automatic update, see Appendix A, the
section, “Configuration Server Settings” on page A-13.
41-001160-00, Release 2.1, Rev 04
8-7
Firmware Upgrade
Use the following procedures to configure automatic update of the IP phone
firmware, configuration files, or both.
Firmware Upgrade
IP Phone Administrator Guide
Upgrading the Firmware
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Configuration Server->Auto-Resync.
2
Select the auto-resync mode from the Mode field.
Valid values are None, Configuration Files, Firmware, Both. Default is None.
3
Select the time from the Time (24-hour) field that you want the update to take place.
Valid values are 00:00 to 23:30 (in 30 minute increments).
4
Click
to save your settings.
These changes are not dynamic.
You must restart your IP phone for the changes to take affect.
5
Click on Operation->Reset.
6
In the "Restart Phone" field click
to restart the IP phone and apply the update.
The update performs automatically at the time you designated.
8-8
41-001160-00, Release 2.1, Rev 04
Upgrading the Firmware
Upgrading the Firmware
Reference
Firmware Upgrade
For more information about setting automatic update on the IP phone, see the
"auto resync mode" and "auto resync time" parameters, see Appendix A, the
section, “Configuration Server Settings” on page A-13.
41-001160-00, Release 2.1, Rev 04
8-9
Troubleshooting
About this chapter
About this chapter
Introduction
This chapter describes tasks that a system administrator can perform on the IP
phones for troubleshooting purposes. It also includes answers to questions you
may have while using the IP phones.
Topics
This chapter covers the following topics:
Topic
Page
Troubleshooting
page 9-2
Troubleshooting Solutions
page 9-7
Why does my phone display “Application missing”?
page 9-7
Why does my phone display the “No Service” message?
page 9-8
Why does my phone display "Bad Encrypted Config"?
page 9-8
Why is my phone not receiving the TFTP IP address from the DHCP
Server?
page 9-9
How do I restart the IP phone?
page 9-10
How do I set the IP phone to factory default?
page 9-11
How do I erase the phone’s local configuration?
page 9-12
How to reset a user’s password?
page 9-13
How do I lock and unlock the phone?
page 9-14
41-001160-00, Release 2.1, Rev 04
9-1
Troubleshooting
Chapter 9
Troubleshooting
IP Phone Administrator Guide
Troubleshooting
Troubleshooting
Troubleshooting
This section describes tasks that a system administrator can perform on the IP
phones for troubleshooting purposes. Using the Aastra Web UI, a system
administrator can:
•
Assign an IP address and IP port in which to save log files
•
Filter the logs according to severity that get reported to log files
•
Save the current local configuration file to a specified location
•
Save the current server configuration file to a specified location
•
Show task and stack status
Aastra Technical Support can then use the information gathered to perform
troubleshooting tasks.
Log Settings
Using the configuration files or the Aastra Web UI, you can specify the location
for which to save files for troubleshooting purposes.
In the configuration files, you use the following parameters to configure log
settings:
•
log server ip - The IP address for which to save log files for troubleshooting
purposes.
•
log server port - The IP port to use to save log files for troubleshooting
purposes.
•
log level - The severity level of the logs to be reported to a log file. Log Level
default is Error (3). (Changes to this parameter via the Aastra Web UI require
a reboot).
Reference
For more information about the log setting configuration parameters, see
Appendix A, the section, “Troubleshooting Parameters” on page A-177.
9-2
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting
•
Log IP - The IP address for which to save log files for troubleshooting
purposes.
•
Log Port - The IP port to use to save log files for troubleshooting purposes.
Module/Debug Level Settings
The Aastra IP phones provide blog module support that allows enhanced severity
filtering of log calls sent as blog output.
The blog, as used on the IP phones, is a an online debugging tool that can be
frequently updated and intended for technical support analyzation. Blogs are
defined by their format: a series of entries posted to a single page in
reverse-chronological order. The IP Phone blogs are separated into modules
which allow you to log specific information for analyzing.
You can set the Module/Debug Levels using the configuration files or the Aastra
Web UI. The following table identifies the blog modules you can set.
Aastra Web UI Parameters
Configuration File Parameters
LINMGR (Line Manager information)
log module linemgr
UI (User Interface (UI) related)
log module user interface
MISC (Miscellaneous)
log module misc
SIP (Call control SIP stack)
log module sip
DIS (Display drivers)
log module dis
DSTORE (Delayed storage)
log module dstore
EPT (Endpoint module)
log module ept
IND (Indicator module)
log module ind
KBD (Keyboard module
log module kbd
NET (Network module
log module net
PROVIS (Provisioning module
log module provis
RTPT (Realtime Transport module
log module rtpt
SND (Sound module
log module snd
41-001160-00, Release 2.1, Rev 04
9-3
Troubleshooting
In the Aastra Web UI, you use the following parameters to configure log
settings:
Troubleshooting
IP Phone Administrator Guide
Troubleshooting
Aastra Web UI Parameters
Configuration File Parameters
PROF (Profiler module)
log module prof
XML (Extension Markup Lanaguage)
log module xml
In the configuration files and the Aastra Web UI, you can enable or disable each
module by setting the values of 1 (enable) or 0 (disable).
Support Information
You can save the local and/or server configuration files of the IP phone to the
location specified in the "Log Settings" section.
Performing this task allows Aastra Technical Support to view the current
configuration of the IP phone and troubleshoot as necessary.
In the “Support Information” section, you can:
•
Get local.cfg
•
Get server.cfg
•
Show task and Stack Status
Aastra Technical Support uses this support information for troubleshooting the IP
phone when required.
Performing Troubleshooting Tasks
Use the following procedures to perform troubleshooting on the IP phone via the
configuration files or the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Troubleshooting
Parameters” on page A-177.
9-4
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting
Troubleshooting
Aastra Web UI
Step
Action
1
Click on Advanced Settings->Troubleshooting.
To set log settings:
2
In the "Log IP" field, enter the IP address of where you want log files to be stored.
3
In the "Log Port" field, enter the port number associated with the IP address specified in the "Log IP"
field. This port passes the information from the IP phone to the IP address location.
41-001160-00, Release 2.1, Rev 04
9-5
Troubleshooting
IP Phone Administrator Guide
Troubleshooting
Aastra Web UI
Step
Action
4
Click
5
Click on Operation->Reset.
6
In the "Restart Phone" field click
to save your settings.
to restart the IP phone.
To set blog modules:
7
Select a module for which you want to have log files created and sent to a blog.
8
Enter a value (in decimal format) in the “Debug Level” field. The value of “1” enables the logging of
the module. The value of “0” disables the logging of the module. The default value is “1”.
9
Click
10
Click on Operation->Reset.
11
In the "Restart Phone" field click
to save your settings.
to restart the IP phone.
To perform support tasks:
12
To store the local configuration file to the specified location, click on
local.cfg" field.
13
To store the server configuration file to the specified location, click on
"Get server.cfg" field.
14
To display task and stack status information to the screen, click on
and Stack Status" field.
in the "Get
in the
in the "Show Task
Note: The local and server configuration file information and the task and stack status information is
for use by Aastra Technical Support for troubleshooting purposes.
Reference
For information that describes solutions to most common problems using the IP
phones, see the next section, “Troubleshooting Solutions” on page 9-7.
9-6
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting Solutions
Troubleshooting Solutions
This section describes solutions to some most common problems that can occur
while using the IP phones.
Why does my phone display “Application missing”?
If you have experienced networking issues while the phone was downloading the
application from the TFTP server, it is possible that the phone can no longer
retrieve the required firmware file. In the event that the phone is no longer able to
communicate with the TFTP server in its attempt to re-download the firmware and
the phone cannot locate the application locally, the message "Application
missing" displays.
The phone also displays the following: “Recovery web-client at: <IP Address>”.
The IP Address displayed is the IP address of the phone. If the phone is unable to
receive an IP from the DHCP server or has lost its record of its static IP, the phone
auto-assigns itself the default IP 192.168.0.50.
To recover the firmware for your phone in this circumstance, please perform the
following:
1.
Launch your web browser on your computer.
Note: Your computer needs to be on the same network as your IP Phone.
2.
In the URL, type: “http://<IP Address>” (where IP Address is the IP Address
displayed on the phone). Your browser launches the Aastra IP Phone
Firmware Recovery page.
3.
Call Customer Support and request a <phone model>.st file.
4.
Copy the file to your TFTP server.
5.
Enter the <phone model>.st file that is ready for download.
6.
Enter the IP address or qualified domain name of the TFTP server.
7.
Press the Download Firmware button.
41-001160-00, Release 2.1, Rev 04
9-7
Troubleshooting
Description
Troubleshooting
IP Phone Administrator Guide
Troubleshooting Solutions
Please ensure that the TFTP server is running and accessible on the network. If the
firmware file is correctly located on the running TFTP server, the phone will
locate the file and reload the application onto the phone.
Why does my phone display the “No Service” message?
The phone displays the “No Service” message if the SIP settings have not been set
up correctly.
The Registrar server could be set to 0.0.0.0. A global value of 0.0.0.0 disables
registration. However, the phone is still active and you can dial using
username@ip address of the phone. The phone displays "No Service".
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1, line 2,
etc.), then the register request is not sent, the "No Service" message does not
display, and the message waiting indicator (MWI) does not come on.
Check that the "Registrar Server" IP address in the Aastra Web UI at Advanced
Settings->Global SIP is correct. Check the "sip registrar ip" parameter in the
configuration files is correct.
Why does my phone display "Bad Encrypted Config"?
The IP phone displays "Bad Encrypted Config" because encrypted configuration
files are enabled but the decryption process has failed. Specific cases where
decryption fails are:
Reason:
The site-specific password in security.tuz does not match the password used to
encrypt the <mac>.tuz or aastra.tuz files.
Fix:
Encrypt the .cfg files to .tuz using the correct password, or replace the security.tuz
with the correct encrypted file.
9-8
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting Solutions
Reason:
Fix:
Create the encrypted files using anacrypt.exe and copy them to the configuration
server.
Reason:
The encrypted <mac>.tuz or aastra.tuz file is encrypted using a different version
of anacrypt.exe than the phone firmware.
Fix:
Run "anacrypt.exe -v" and confirm that the correct version is reported, compared
to the phone firmware version.
Why is my phone not receiving the TFTP IP address from the DHCP
Server?
For DHCP to automatically populate the IP address or qualified domain name for
the TFTP server, your DHCP server must support Option 66. Option 66 is
responsible for forwarding the TFTP server IP address or domain name to the
phone automatically. If your DHCP server does not support Option 66, you must
manually enter the IP address or qualified domain name for the TFTP server into
your IP phone configuration.
For procedures on configuring the TFTP server using the IP phone UI and the
Aastra Web UI, see Chapter 4, the section, “Configuring the Configuration Server
Protocol” on page 4-79.
For specific protocol parameters you can set in the configuration files, see
Appendix A, the section, “Configuration Server Settings” on page A-13.
41-001160-00, Release 2.1, Rev 04
9-9
Troubleshooting
Neither of the <mac>.tuz and aastra.tuz files are present on the configuration
server (TFTP/FTP/HTTP).
IP Phone Administrator Guide
Troubleshooting Solutions
Troubleshooting
How do I restart the IP phone?
IP Phone UI
Step
Action
1
Press
2
Select Restart Phone.
3
For 53i:
Press # to confirm.
on the phone to enter the Options List.
Note: To cancel the Restart, press the 3 key.
For 55i, 57i, 57i CT:
Press Restart.
Note: To cancel the Restart, press Cancel.
Aastra Web UI
1
Click on Operation->Reset->Phone.
2
Click
9-10
to restart the phone.
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting Solutions
How do I set the IP phone to factory default?
Troubleshooting
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu and enter your Administrator Password (default is 22222).
3
Select Factory Default.
4
For 53i:
The “Restore Defaults?” prompt displays.
Press # to confirm.
on the phone to enter the Options List.
For 55i/57i/57i CT:
The “Reset phone to factory defaults?” prompt displays.
Press Default to confirm.
Aastra Web UI
Step
Action
1
Click on Operation->Reset->Current Settings.
2
In the "Restore to Factory Defaults" field, click
.
This restores all factory defaults, and removes any saved configuration and directory list files.
41-001160-00, Release 2.1, Rev 04
9-11
IP Phone Administrator Guide
Troubleshooting Solutions
Troubleshooting
How do I erase the phone’s local configuration?
IP Phone UI
Step
Action
1
Press
2
Select Administrator Menu and enter your Administrator Password (default is 22222).
3
Select Erase Local Config.
4
For 53i:
The “Erase local config?” prompt displays.
Press # to confirm.
on the phone to enter the Options List.
For 55i/57i/57i CT:
The “Erase local config?” prompt displays.
Press Erase to confirm.
Aastra Web UI
Step
Action
1
Click on Operation->Reset->Current Settings.
2
In the "Remove Local Configuration Settings" field, click
.
This removes the last customized configuration settings made on the phone.
9-12
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting Solutions
How to reset a user’s password?
1
Press
on the phone to enter the Options List.
2
Select User Password.
3
Enter the current user password.
4
Press Enter.
5
Enter the new user password.
Note: The IP phones support numeric characters only in passwords. If you enter a password with
alpha characters, the phone uses the default password instead.
6
Press Enter.
7
Re-enter the new user password.
8
Press Enter.
A message, "Password Changed" displays on the screen.
Aastra Web UI
Step
Action
1
Click on Operation->User Password.
2
In the "Current Password" field, enter the current user password.
3
In the "New Password" field, enter the new user password.
4
In the "Confirm Password" field, enter the new user password again.
5
Click
to save your changes.
41-001160-00, Release 2.1, Rev 04
9-13
Troubleshooting
IP Phone UI
IP Phone Administrator Guide
Troubleshooting Solutions
Troubleshooting
How do I lock and unlock the phone?
IP Phone UI
Step
Action
Lock the phone:
1
Press
on the phone to enter the Options List.
2
Select Phone Lock.
The prompt, “Lock the phone?” displays.
3
Press Lock to lock the phone.
Unlock the phone:
1
Press
on the phone to enter the Options List.
The prompt, “To unlock the phone...Password:”
2
Enter the user or administrator password and press Enter.
The phone unlocks.
9-14
41-001160-00, Release 2.1, Rev 04
Troubleshooting
Troubleshooting Solutions
Troubleshooting
Aastra Web UI
1
Click on Operation->Phone Lock.
Lock the phone:
2
In the “Lock the Phone?” field, click
.
The phone locks dyanamically and displays the following message:
“Phone is locked”.
Unlock the phone:
3
Click on Operation->Phone Lock.
4
In the “Unlock the Phone?” field, click
.
The phone unlocks dynamically and displays the following message:
“Phone is unlocked”.
41-001160-00, Release 2.1, Rev 04
9-15
Configuration Parameters
About this appendix
About this appendix
Introduction
This appendix describes the parameters you can set in the configuration files for
the IP phones. The configuration files include <mac.cfg> and config.cfg.
Topics
This appendix covers the following topics:
Topic
Page
Setting Parameters in Configuration Files
page A-4
Operational, Basic, and Advanced Parameters
page A-5
Network Settings
page A-6
Password Settings
page A-9
Emergency Dial Plan Settings
page A-11
Aastra Web UI Settings
page A-12
Configuration Server Settings
page A-13
Network Address Translation (NAT) Settings
page A-20
HTTPS Client and Server Settings
page A-23
UPnP Settings
page A-25
Virtual Local Area Network (VLAN) Settings
page A-26
Type of Service (ToS)/DSCP Settings
page A-30
41-001160-00, Release 2.1, Rev 04
A-1
Appendix A
Appendix A
Configuration Parameters
IP Phone Administrator Guide
About this appendix
Appendix A
Topic
A-2
Page
Time Server Settings
page A-31
Time and Date Settings
page A-33
SIP Local Dial Plan Settings
page A-39
SIP Basic, Global Settings
page A-41
SIP Basic, Per-Line Settings
page A-50
Centralized Conferencing Settings
page A-60
Advanced SIP Settings
page A-62
Missed Call Summary Subscription Settings
page A-70
Transport Layer Security (TLS) Settings
page A-72
RTP, Codec, DTMF Global Settings
page A-77
Autodial Settings
page A-81
Voicemail Settings
page A-84
Directory Settings
page A-85
Callers List Settings
page A-86
Customize Callers List and Services Key
page A-86
Call Forward Settings
page A-87
Missed Calls Indicator Settings
page A-88
XML Settings
page A-89
Action URI Settings
page A-92
Ring Tone and Tone Set Global Settings
page A-94
Ring Tone Per-Line Settings
page A-97
Incoming Call Interrupts Dialing Setting
page A-98
Goodbye Key Cancels Incoming Call
page A-99
Stuttered Dial Tone Setting
page A-100
Call Waiting Settings
page A-101
Message Waiting Indicator Settings
page A-102
Priority Alert Settings
page A-103
Language Settings
page A-109
Language Pack Settings
page A-110
Suppress DTMF Playback Setting
page A-119
Display DTMF Digits Setting
page A-120
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
About this appendix
Topic
Page
page A-121
Audio Transmit and Receive Gain Adjustment Settings
page A-125
Directed Call Pickup (BLF or XML Call Interception) Settings
page A-128
ACD Auto-Available Timer Settings
page A-131
Park and Pickup Global Settings (57i/57i CT only)
page A-132
Mapping Key Parameters
page A-133
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
page A-136
Softkey Settings for 55i, 57i, 57i CT
page A-137
Programmable Key Settings for 53i and 55i
page A-145
Top Softkey Settings for 57i and 57i CT
page A-150
Handset Feature Key Settings for the 57i CT
page A-156
Expansion Module Key Settings for 536M (for all model phones) and 560M (for 55i,
57i, 57i CT phones only)
page A-158
Locking Softkeys and Programmable Keys
page A-163
Customizing 560M Expansion Module Column Display
page A-166
Expansion Module 1
page A-166
Expansion Module 2
page A-168
Expansion Module 3
page A-170
Advanced Operational Parameters
page A-172
Blind Transfer Setting
page A-172
Update Caller ID Setting.
page A-173
Boot Sequence Recovery Mode.
page A-173
Single Call Restriction
page A-174
Missed Call Summary Subscription Settings
page A-70
Transport Layer Security (TLS) Settings
page A-175
Whitelist Proxy
page A-175
Transport Layer Security (TLS) Settings
page A-72
RTP, Codec, DTMF Global Settings
page A-176
User-Agent Setting
page A-176
Troubleshooting Parameters
page A-177
Log Settings
41-001160-00, Release 2.1, Rev 04
Appendix A
Intercom, Auto-Answer, and Barge In Settings
page A-177
A-3
IP Phone Administrator Guide
Setting Parameters in Configuration Files
Appendix A
Setting Parameters in Configuration Files
You can set specific configuration parameters in the configuration files for
configuring you IP phone. The aastra.cfg and <mac>.cfg files are stored on the
server. The aastra.cfg file stores global IP phone configuration settings. The
<mac>.cfg file stores configuration settings specific to the IP phone with that
MAC address. When you restart the IP phone, these files are downloaded to the
phone.
If you make changes to the phone configuration, the changes are stored in a local
configuration on the phone (not on the server).
Configuration changes made to the <mac>.cfg file override the configuration
settings in the aastra.cfg file.
Note: Configuration parameters that you enter in the configuration files
are NOT case sensitive.
Reference
For information about configuration file precedence, see Chapter 1, the section,
“Configuration File Precedence” on page 1-22.
This section includes the following types of configurable parameters:
A-4
•
Operational, Basic, and Advanced Parameters on page A-5
•
Mapping Key Parameters on page A-133
•
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
on page A-136
•
Advanced Operational Parameters on page A-172
•
Troubleshooting Parameters on page A-177
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Operational, Basic, and Advanced Parameters
Simplified IP Phone UI Options Menu
Parameter –
options simple menu
Configuration Files
aastra.cfg, <mac>.cfg
Description
Allows you to enable a simplified options menu or enable the full menu on
the IP Phone UI.
Full Options Menu
Simplified Options Menu
Call Forward
Call Forward
Preferences
Preferences
Phone Status
Phone Status
User Password
Removed
Administrator Menu
Removed
Restart Phone
Removed
Phone Lock
Phone Lock
Handset Pairing
(CT models only)
Handset Pairing
(CT models only)
Warning: When using the simplified menu, you cannot change the
Network settings from the IP Phone UI. If the network settings become
misconfigured, you must “factory default” the phone and use the full menu
to recover the network settings from the Phone UI OR use the Aastra
Web UI to configure the network settings.
Format
Boolean
Default Value
0 (full options menu)
Range
0 (full options menu)
1 (simplified options menu)
Example
options simple menu: 1
41-001160-00, Release 2.1, Rev 04
A-5
Appendix A
The following sections provide the configuration parameters you can configure on
the IP phone. Each parameter table includes the name of the parameter, a
description, the format, default value, range, and example. The table also provides
the method for which the parameters can be configured (IP phone UI, Aastra Web
UI, or configuration files).
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Network Settings
Parameter –
dhcp
IP phone UI
Aastra Web UI
DHCP
(in Web UI)
Description
Configuration Files
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Enables or disables DHCP. Enabling DHCP populates the required
network information. The DHCP server serves the network information
that the IP phone requires. If the IP phone is unable to get any required
information, then you must enter it manually. DHCP populates the
following network information:
IP Address, Subnet Mask, Gateway, Broadcast Address, Domain Name
Servers (DNS), TFTP, HTTP HTTPS, and FTP servers, and Timer
Servers.
For DHCP to automatically populate the IP address or qualified domain
name for the TFTP server, your DHCP server must support Option 66.
Format
Integer
Default Value
1 (enabled)
Range
0 (disabled)
1 (enabled)
Example
dhcp: 1
Parameter –
ip
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Ip Address
(in Web UI)
Configuration Files
Description
This parameter assigns a static IP address to the IP phone device.
Format
IP address
Default Value
0.0.0.0
Range
Not Applicable
Example
ip: 192.168.0.25
A-6
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Subnet Mask
(in Web UI)
Configuration Files
Description
Subnet mask defines the IP address range local to the IP phone.
Format
IP address
Default Value
255.255.255.0
Range
Not Applicable
Example
subnet mask: 255.255.255.224
Parameter –
default gateway
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Gateway
(in Web UI)
Configuration Files
Description
The IP address of the network’s gateway or default router IP address.
Format
IP address
Default Value
1.0.0.1
Range
Not Applicable
Example
default gateway: 192.168.0.1
Parameter –
dns1
IP phone UI
Aastra Web UI
Primary DNS
(in Web UI)
Configuration Files
Appendix A
Parameter –
subnet mask
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Description
Primary domain name server IP address. For any of the IP address
settings on the IP phone a domain name value can be entered instead of
an IP address. With the help of the domain name servers the domain
names for such parameters can then be resolved to their corresponding
IP addresses.
Format
IP address
Default Value
0.0.0.0
Range
Not Applicable
Example
dns1: 192.168.0.5
41-001160-00, Release 2.1, Rev 04
A-7
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
dns2
IP phone UI
Aastra Web UI
Secondary DNS
(in Web UI)
Configuration Files
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Description
A service that translates domain names into IP addresses. To assign
static DNS addresses, disable DHCP.
Format
IP address
Default Value
0.0.0.0
Range
Not Applicable
Example
dns2: 192.168.0.6
Parameter –
ethernet port 0
IP phone UI
Aastra Web UI
LAN Port
(in Web UI)
Configuration Files
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Description
The send (TX) and receive (RX) method to use on Ethernet port 0 to
transmit and receive data over the LAN.
Format
Integer
Default Value
0
Range
0 - auto-negotiate
1 - full-duplex, 10Mbps
2 - full-duplex, 100Mbps
3 - half-duplex, 10Mbps
4 - half-duplex, 100Mbps
Example
lan port: 1
A-8
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP phone UI
Aastra Web UI
PC Port
(in Web UI)
Configuration Files
Options->Administrator Menu->
Network Settings
Advanced Settings->Network->
Basic Network Settings
aastra.cfg, <mac>.cfg
Description
The send (TX) and receive (RX) method to use on Ethernet port 1 to
transmit and receive data over the LAN.
Format
Integer
Default Value
0
Range
0 - auto-negotiate
1 - full-duplex, 10Mbps
2 - full-duplex, 100Mbps
3 - half-duplex, 10Mbps
4 - half-duplex, 100Mbps
Example
ethernet port 1: 2
Appendix A
Parameter –
ethernet port 1
Password Settings
Parameter –
admin password
Configuration Files
aastra.cfg, <mac>.cfg
Description
Allows you to set a new administrator password for the IP phone.
Note: The IP phones support numeric characters only in passwords. If you
enter a password with alpha characters, the phone uses the default
password instead.
Format
Integer
Default Value
22222
Range
0 to 4294967295
Example
admin password: 1234567890
41-001160-00, Release 2.1, Rev 04
A-9
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
user password
IP phone UI
Aastra Web UI
Configuration Files
Options->User Password
Operation->User Password
aastra.cfg, <mac>.cfg
Current Password
(in Web UI)
Description
Allows you to set a new user password for the IP phone.
Note: The IP phones support numeric characters only in passwords. If you
enter a password with alpha characters, the phone uses the default
password instead.
Format
Integer
Default Value
Default value is an empty string ““ (left blank)
Range
0 to 4294967295
Example
user password: 123
A-10
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Emergency Dial Plan Settings
Configuration Files
Aastra Web UI
aastra.cfg, <mac>.cfg
Operation->Phone Lock
Description
Allows you to specify an emergency number to use on your IP phone so a
caller can contact emergency services in the local area when required.
The default emergency numbers on the IP phones is 911, 999, 112, and
110.
911 - A United States emergency number.
999 - A United Kingdom emergency number.
112 - An international emergency telephone number for GSM mobile
phone networks. In all European Union countries it is also the
emergency telephone number for both mobile and fixed-line
telephones.
110 - A police and/or fire emergency number in Asia, Europe, Middle
East, and South America.
Note: Contact your local phone service provider for available emergency
numbers in your area.
Format
Integer
Default Value
911|999|112|110
Range
Up to 128 characters
Example
emergency dial plan: 911|999
41-001160-00, Release 2.1, Rev 04
A-11
Appendix A
Parameter –
emergency dial plan
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
options password enabled
Configuration Files
aastra.cfg, <mac>.cfg
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.
Format
Boolean
Default Value
0
Range
0 (false; not password protected)
1 (true; password protected)
Example
options password enabled: 1
Aastra Web UI Settings
Parameter –
web interface enabled
Configuration Files
aastra.cfg, <mac>.cfg
Description
Enables or disables the Aastra Web UI for a single IP phone when placed
in the <mac>.cfg file.
Enables or disables the Aastra Web UI for all phones when placed in the
aastra.cfg file.
Format
Boolean
Default Value
Not Applicable
Range
0 = Disable
1 = Enable
Example
web interface enabled: 1
A-12
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Configuration Server Settings
Download Protocol
(in Web UI)
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
Protocol to use for downloading new versions of software to the IP phone.
Format
Text
Default Value
TFTP
Range
TFTP
FTP
HTTP
HTTPS
Example
download protocol: HTTPS
Parameter –
tftp server
IP phone UI
TFTP Server
(in Web UI)
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->TFTP Server->Primary TFTP
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
The TFTP server’s IP address or qualified domain name. If DHCP is
enabled and the DHCP server provides the information, this field is
automatically populated. Use this parameter to change the IP address or
domain name of the TFTP server. This will become effective after this
configuration file has been downloaded into the phone.
Format
IP address or qualified domain name
Default Value
0.0.0.0
Range
Not Applicable
Example
tftp server: 192.168.0.130
41-001160-00, Release 2.1, Rev 04
A-13
Appendix A
Parameter –
download protocol
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
alternate tftp server
IP phone UI
Alternate TFTP
(in Web UI)
Aastra Web UI
Configuration Files
Description
The alternate TFTP server’s IP address or qualified domain name. This
will become effective after this configuration file has been downloaded into
the phone.
Format
IP address or qualified domain name
Default Value
0.0.0.0
Range
Not Applicable
Example
alternate tftp server: 192.168.0.132
Parameter –
use alternate tftp
IP phone UI
Use Alternate TFTP
(in Web UI)
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->TFTP Server->
Alternate TFTP
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Options->Administrator Menu->
Network Settings->TFTP Server->Select TFTP
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
Enables or disables the alternate TFTP server. Valid values are "0"
disabled and "1" enabled.
Format
Not Applicable
Default Value
0
Range
0 or 1
Example
use alternate tftp: 1
A-14
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
FTP Server
(in Web UI)
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->FTP Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
The FTP server’s IP address or network host name. This will become
effective after this configuration file has been downloaded into the phone.
Optional: You can also assign a username and password for access to the
FTP server. See the following parameters for setting username and
password.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
ftp server: 192.168.0.131
Parameter –
ftp username
IP phone UI
FTP User Name
(in Web UI)
Description
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->FTP Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
The username to enter for accessing the FTP server. This will become
effective after this configuration file has been downloaded into the phone.
Note: The IP Phones support usernames containing dots (“.”).
Format
Text
Default Value
Not Applicable
Range
Up to 63 alphanumeric characters
Example
ftp username: 57iaastra
41-001160-00, Release 2.1, Rev 04
A-15
Appendix A
Parameter –
ftp server
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
ftp password
FTP Password
(in Web UI)
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->FTP Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
The password to enter for accessing the FTP server. This will become
effective after this configuration file has been downloaded into the phone.
Format
Text
Default Value
Not Applicable
Range
Up to 63 alphanumeric characters
Example
ftp password: 1234
Parameter –
http server
IP phone UI
HTTP Server
(in Web UI)
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->HTTP Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
Description
The HTTP server’s IP address. This will become effective after this
configuration file has been downloaded into the phone.
Optional: You can also assign an HTTP relative path to the HTTP server.
See the next parameter (http path).
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
http server: 192.168.0.132
Parameter –
http path
IP phone UI
HTTP Path
(in Web UI)
Description
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->HTTP Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
The HTTP path name to enter.
If the IP phone’s configuration and firmware files are located in a
sub-directory beneath the server’s HTTP root directory, the relative path
to that sub-directory should be entered in this field.
Format
dir/dir/dir
Default Value
Not Applicable
Range
Up to 63 alphanumeric characters
Example
http path: ipphones/57i
A-16
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP phone UI
Options->Administrator Menu->
Network Settings->HTTPS->
HTTPS Client->Download Server
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
HTTPS Server
(in Web UI)
Aastra Web UI
Configuration Files
Description
The HTTPS server’s IP address. This will become effective after this
configuration file has been downloaded into the phone.
Optional: You can also assign an HTTPS relative path to the HTTPS
server. See the next parameter (https path)
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
https server: 192.168.0.143
Parameter –
https path
IP phone UI
HTTPS Path
(in Web UI)
Aastra Web UI
Configuration Files
Description
The HTTPS path name to enter.
Appendix A
Parameter –
https server
Options->Administrator Menu->
Network Settings->HTTPS->
HTTPS Client->Download Path
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
If the IP phone’s configuration and firmware files are located in a
sub-directory beneath the server’s HTTPS root directory, the relative path
to that sub-directory should be entered in this field.
Format
dir/dir/dir
Default Value
Not Applicable
Range
Up to 63 alphanumeric characters
Example
https path: ipphones/55i
41-001160-00, Release 2.1, Rev 04
A-17
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
auto resync mode
Mode
(in Web UI)
Aastra Web UI
Configuration Files
Advanced Settings->Configuration Server->
Auto-Resync
aastra.cfg, <mac>.cfg
Description
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.
Format
Integer
Default Value
Aastra Web UI
None
Configuration Files
0
Range
Aastra Web UI
None
Configuration Files
Firmware
Both
Configuration Files
0 (none)
1 (configuration files only)
2 (firmware only)
3 (configuration files and firmware)
Example
A-18
auto resync mode: 1
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Configuration Server->
Auto-Resync
aastra.cfg, <mac>.cfg
Time (24-hour)
(in Web UI)
Description
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).
Format
hh:mm
00h00 (for French and Spanish configuration files)
Default Value
Aastra Web UI
00:00
Configuration Files
00:00
Range
Aastra Web UI
00:00 to 23:30 (in 30 minute increments)
Configuration Files
hh = 00 to 23
mm = 00 to 59
Example
auto resync time: 03:24
41-001160-00, Release 2.1, Rev 04
A-19
Appendix A
Parameter –
auto resync time
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Network Address Translation (NAT) Settings
Parameter –
sip nat ip
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->SIP Settings
Advanced Settings->Network
aastra.cfg, <mac>.cfg
NAT IP
(in Web UI)
Description
IP address the network device that enforces NAT.
Format
IP Address
Default Value
0.0.0.0
Range
Not Applicable
Example
sip nat ip: 192.245.2.1
Parameter –
sip nat port
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->SIP Settings
Advanced Settings->Network
aastra.cfg, <mac>.cfg
NAT SIP Port
(in Web UI)
Description
Port number of the network device that enforces NAT.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip nat port: 51620
A-20
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP Phone UI
Aastra Web UI
NAT RTP Port
(in Phone UI and Web UI)
Description
Configuration Files
Options->Administrator Menu->
SIP Settings->RTP Port Base
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Indicates the port through which the RTP packets are sent. This value
must specify the beginning of the RTP port range on the gateway or
router.
The RTP port is used for sending DTMF tones and for the audio stream.
Your network administrator may close some ports for security reasons.
You may want to use this parameter to send RTP data using a different
port.
Format
Integer
Default Value
51720
Range
Not Applicable
Example
sip nat rtp port: 51730
Parameter –
sip nortel nat support
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->SIP Settings
Advanced Settings->Network
aastra.cfg, <mac>.cfg
Nortel NAT Traversal
Enabled
(in Web UI)
Description
Enables or disables the phone to operate while connected to a network
device that enforces NAT.
Format
Integer
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip nortel nat support: 1
41-001160-00, Release 2.1, Rev 04
A-21
Appendix A
Parameter –
sip nat rtp port
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip nortel nat timer
Aastra Web UI
Configuration Files
Advanced Settings->Network
aastra.cfg, <mac>.cfg
Nortel NAT Timer
(in Web UI)
Description
The interval, in seconds, that the phone sends SIP ping requests to the
Nortel proxy.
Format
Integer
Default Value
30
Range
0 to 2147483647
Example
sip nortel nat timer: 60
A-22
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
HTTPS Client and Server Settings
IP Phone UI
Aastra Web UI
HTTPS Client Method
(in Web UI)
Description
Configuration Files
Options->Administrator Menu->
Network Settings->HTTPS->HTTPS Client
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Defines the security method that the client advertises to the server during
the Secure Socket Layer (SSL) handshake. Available options are:
TLS 1.0 - Transport Layer Security version 1 (TLS 1.0) is a protocol that
ensures privacy between communicating applications and their users on
the Internet. TLS is the successor to SSL.
SSL 3.0 - Secure Socket Layer version 3 (SSL 3.0) is a commonly-used
protocol for managing the security of a message transmission on the
Internet.
Format
Alphanumeric characters
Default Value
SSL 3.0
Range
TLS 1.0
SSL 3.0 (default)
Example
https client method: TLS 1.0
Parameter –
https redirect http get
IP Phone UI
HTTPS Server - Redirect
HTTP to HTTPS
(in Web UI)
Aastra Web UI
Description
Allows or disallows redirection from the HTTP server to the HTTPS
server.
Format
Boolean
Default Value
1 (enables redirection)
Range
0 (disables redirection)
1 (enables redirection)
Example
https redirect http get: 0
Configuration Files
41-001160-00, Release 2.1, Rev 04
Options->Administrator Menu->
Network Settings->HTTPS->
HTTPS Server->Redirect
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
A-23
Appendix A
Parameter –
https client method
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
https block http post xml
IP Phone UI
HTTPS Server - Block XML
HTTP POSTs
(in Web UI)
Aastra Web UI
Description
Enables or disables the blocking of XML scripts from HTTP POSTs.
Configuration Files
Options->Administrator Menu->
Network Settings->HTTPS->
HTTPS Server->XML
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Some client applications use HTTP POSTs to transfer XML scripts. The
phones’s HTTP server accepts these POSTs even if server redirection is
enabled, effectively bypassing the secure connection. When this
parameter is enabled (blocking is enabled), receipt of an HTTP POST
containing an XML parameter header results in the following response:
“403 Forbidden”. This forces the client to direct the POSTs to the HTTPS
server through use of the “https://” URL.
Format
Boolean
Default Value
0 (disables blocking of XML HTTP POSTs)
Range
0 (disables blocking of XML HTTP POSTs)
1 (enables blocking of XML HTTP POSTs)
Example
https block http post xml: 1
A-24
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
UPnP Settings
IP phone UI
Aastra Web UI
UPnP
(in Web UI)
Configuration Files
Options->Administrator Menu->
Network Settings->UPnP
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Description
Enables or disables Universal Plug and Play (UpnP) on the IP phone. If
you set this parameter to “0”, you can manually configure NAT on the IP
phone and the UPnP manager will not start.
Format
Boolean
Default Value
0 (false)
Range
0 (false)
1 (true)
Example
upnp manager: 1
Parameter –
upnp gateway
Configuration Files
Description
IP address or fully qualified Domain Name of the Internet gateway or
router. This parameter stores the IP address of the gateway or router in
the event that only non-default UPnP gateways get discovered on the
network. The UPnP port mappings are saved to this IP address so even if
the phone reboots, it will still have the correct port mappings.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
upnp gateway: 120.400.003.2
41-001160-00, Release 2.1, Rev 04
aastra.cfg, <mac>.cfg
A-25
Appendix A
Parameter –
upnp manager
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
upnp mapping lines
Aastra Web UI
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
UPnP Mapping Lines
(in Web UI)
Description
Enables or disables the use of Universal Plug and Play (UpnP) on a
specific line on the IP phone.
Note: For this feature to work, UPnP must be enabled on the phone
(upnp manager and upnp gateway must be set).
Format
Integer
Default Value
0 (UPnP is not mapped to a specific line)
Range
0 to 10
Example
upnp mapping lines: 5
This example indicates that line 5 allows UPnP mapping.
Virtual Local Area Network (VLAN) Settings
Global Parameters
Parameter –
tagging enabled
VLAN Enable
(in Web UI)
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->VLAN->VLAN Enable
Advanced Settings->Network->VLAN->Global
aastra.cfg, <mac>.cfg
Description
Enables or disables VLAN on the IP phones. This is a global setting.
Format
Boolean
Default Value
0 (false)
Range
0 (false)
1 (true)
Example
tagging enabled: 1
A-26
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP phone UI
Options->Administrator Menu->
Network Settings->VLAN->Phone->Priority
->Other
Advanced Settings->Network->VLAN->Global
aastra.cfg, <mac>.cfg
Priority, Non-IP Packet
(in Web UI)
Aastra Web UI
Configuration Files
Description
Specifies the priority value for non-IP packets. This is a global setting.
Format
Integer
Default Value
5
Range
0 to 7
Example
priority non-ip: 7
LAN Port (Ethernet Port 0) Parameters
Parameter –
vlan id
VLAN ID
(for LAN Port in
Web UI)
IP phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
Network Settings->VLAN->Phone->VLAN ID
Advanced Settings->Network->VLAN->Port 0
aastra.cfg, <mac>.cfg
Description
VLAN is a feature on the IP phone that allows for multiple logical Ethernet
interfaces to send outgoing RTP packets over a single physical Ethernet
as described in IEEE Std 802.3. On the IP phone, you configure a VLAN
ID that associates with the physical Ethernet Port 0.
Format
Integer
Default Value
1
Range
1 to 4094
Example
VLAN id: 300
41-001160-00, Release 2.1, Rev 04
A-27
Appendix A
Parameter –
priority non-ip
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
tos priority map
IP phone UI
Options->Administrator Menu->
Network Settings->VLAN->Phone->
Priority->SIP
SIP Priority
RTP Priority
RTCP Priority
Options->Administrator Menu->
Network Settings->VLAN->Phone->
Priority->RTP
(for LAN Port in
Web UI)
Options->Administrator Menu->
Network Settings->VLAN->Phone->
Priority->RTCP
Aastra Web UI
Configuration Files
Description
Advanced Settings->Network->VLAN->Port 0
aastra.cfg, <mac>.cfg
This parameter is based on the Type of Service (ToS), Differentiated
Services Code Point (DSCP) setting for SIP (tos sip parameter), RTP (tos
rtp parameter) and RTCP (tos rtcp parameter). It is the mapping between
the DSCP value and the VLAN priority value for SIP, RTP, and RTCP
packets.
You enter the tos priority map value as follows:
(DSCP_1,Priority_1)(DSCP_2,Priority_2).....(DSCP_64,Priority_64)
where the DSCP value range is 0-63 and the priority range is 0-7.
Mappings not enclosed in parentheses and separated with a comma, or
with values outside the ranges, are ignored.
Format
Integer
Default Value
3 (based on the default ToS DSCP SIP setting of 26)
5 (based on the default ToS DSCP RTP setting of 46)
5 (based on the default ToS DSCP RTCP setting of 46)
Range
0 to 63 (for DSCP)
0 to 7 (for SIP, RTP, and RTCP priorities)
Example
tos priority map: (26,7)
The following table identifies the default DSCP-to-priority mapping structure.
DSCP
Range
A-28
DSCP Priority
0-7
0
8-15
1
16-23
2
24-31
3
32-39
4
40-47
5
48-55
6
56-63
7
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
PC Port (Ethernet Port 1) Parameters
IP phone UI
VLAN ID
(for PC Port in
Web UI)
Aastra Web UI
Configuration Files
Description
Specifies the VLAN ID used to pass packets through to a PC via Port 1.
Options->Administrator Menu->
Network Settings->VLAN->
Passthrough->VLAN ID
Advanced Settings->Network->VLAN->Port 1
aastra.cfg, <mac>.cfg
Note: If you set the VLAN id port 1 (passthrough port) to 4095, all
untagged packets are sent to this port. The following is an example of
configuring the phone on a VLAN where all untagged packets are sent to
the passthrough port.
Example
You enable tagging on the phone port as normal but set the
passthrough port (VLAN id port 1) to 4095. The following example
sets the phone to be on VLAN 3 but the passthrough port is
configured as untagged.
tagging enabled: 1
VLAN id: 3
VLAN id port 1: 4095
Format
Integer
Default Value
1
Range
1 to 4095
Example
VLAN id port 1: 3
Parameter –
QoS eth port 1 priority
IP phone UI
Priority
(for PC Port in
Web UI)
Aastra Web UI
Configuration Files
Description
Specifies the priority value used for passing VLAN packets through to a
PC via Port 1.
Format
Integer
Default Value
0
Range
0 to 7
Example
QoS eth port 1 priority: 3
41-001160-00, Release 2.1, Rev 04
Options->Administrator Menu->
Network Settings->VLAN->Passthrough
->Priority
Advanced Settings->Network->VLAN->Port 1
aastra.cfg, <mac>.cfg
A-29
Appendix A
Parameter –
vlan id port 1
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Type of Service (ToS)/DSCP Settings
Parameter –
tos sip
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings->Type of Service->SIP
Advanced Settings->Network->
Type of Service,DSCP
aastra.cfg, <mac>.cfg
SIP
(in Web UI)
Configuration Files
Description
The Differentiated Services Code Point (DSCP) for SIP packets.
Format
Integer
Default Value
26
Range
0 to 63
Example
tos sip: 3
Parameter –
tos rtp
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings->Type of Service->RTP
Advanced Settings->Network->
Type of Service,DSCP
aastra.cfg, <mac>.cfg
RTP
(in Web UI)
Configuration Files
Description
The Differentiated Services Code Point (DSCP) for RTP packets.
Format
Integer
Default Value
46
Range
0 to 63
Example
tos rtp: 2
Parameter –
tos rtcp
IP phone UI
Aastra Web UI
Options->Administrator Menu->
Network Settings->Type of Service->RTCP
Advanced Settings->Network->
Type of Service,DSCP
aastra.cfg, <mac>.cfg
RTCP
(in Web UI)
Configuration Files
Description
The Differentiated Services Code Point (DSCP) for RTCP packets.
Format
Integer
Default Value
46
Range
0 to 63
Example
tos rtcp: 3
A-30
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Time Server Settings
Aastra Web UI
Configuration Files
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
NTP Time Servers
(in Web UI)
Description
Enables or disables the time server. This parameter affects the time
server1, time server2, and time server3 parameters. Setting this
parameter to 0 allows the use of the configured Time Server(s). Setting
this parameter to 1 prevents the use of the configured Time Server(s).
Format
Integer
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
time server disabled: 0
Parameter –
time server1
Aastra Web UI
Configuration Files
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Time Server 1
(in Web UI)
Description
The primary time server's IP address or qualified domain name. If the
time server is enabled, the value for time server1 will be used to request
the time from.
Format
IP address or qualified domain name
Default Value
0.0.0.0
Range
Not Applicable
Example
time server1: 192.168.0.5
41-001160-00, Release 2.1, Rev 04
A-31
Appendix A
Parameter –
time server disabled
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
time server2
Aastra Web UI
Configuration Files
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Time Server 2
(in Web UI)
Description
The secondary time server's IP address or qualified domain name. If the
time server is enabled, and the primary time server is not configured or
cannot be accessed the value for time server2 will be used to request
the time from.
Format
IP address or qualified domain name
Default Value
0.0.0.0
Range
Not Applicable
Example
time server2: 192.168.0.5
Parameter –
time server3
Aastra Web UI
Configuration Files
Advanced Settings->Network->
Advanced Network Settings
aastra.cfg, <mac>.cfg
Time Server 3
(in Web UI)
Description
The tertiary time server's IP address or qualified domain name. If the
time server is enabled, and the primary and secondary time servers are
not configured or cannot be accessed the value for time server3 will be
used to request the time from.
Format
IP address or qualified domain name
Default Value
0.0.0.0
Range
Not Applicable
Example
time server3: 192.168.0.5
A-32
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Time and Date Settings
IP phone UI
Configuration Files
Options->Time and Date->Time Format
aastra.cfg, <mac>.cfg
Time Format
(in Phone UI)
Description
This parameter changes the time to 12 hour or 24 hour format. Use “0”
for the 12 hour format and “1” for the 24 hour format.
Format
Integer
Default Value
0
Range
0 (12 hr format))
1 (24 hr format)
Example
time format: 0
Parameter –
date format
IP phone UI
Configuration Files
Options->Time and Date->Date Format
aastra.cfg, <mac>.cfg
Date Format
(in Phone UI)
Description
This parameter allows the user to change the date to various formats.
Format
Integer
Default Value
0
Range
0 (WWW MMM DD) (default)
1 (DD-MMM-YY)
2 (YYYY-MM-DD)
3 (DD/MM/YYYY)
4 (DD/MM/YY)
5 (DD-MM-YY)
6 (MM/DD/YY)
7 (MMM DD)
Example
date format: 7
41-001160-00, Release 2.1, Rev 04
A-33
Appendix A
Parameter –
time format
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
dst config
IP phone UI
Configuration Files
Options->Time and Date->Daylight Savings
aastra.cfg, <mac>.cfg
Daylight Savings
(in Phone UI)
Description
Enables/disables the use of daylight savings time.
Format
Integer
Default Value
3
Range
0 - OFF
1 - 30 min summertime
2 - 1 hr summertime
3 - automatic
Example
dst config: 0
Parameter –
time zone name
IP phone UI
Configuration Files
Options->Time and Date->Time Zone
aastra.cfg, <mac>.cfg
Time Zone
(in Phone UI)
Description
Assigns a time zone name to the time server.
Format
Text
Default Value
US-Eastern
Range
See “Time Zone Name/Time Zone Code Table” below.
Example
time zone name: US-Central
A-34
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Time Zone Name/Time Zone Code Table
Time Zone Code
AD-Andorra
AG-Antigua
AI-Anguilla
AL-Tirane
AN-Curacao
AR-Buenos Aires
AS-Pago Pago
AT-Vienna
AU-Lord Howe
AU-Tasmania
AU-Melbourne
AU-Sydney
AU-Broken Hill
AU-Brisbane
AU-Lindeman
AU-Adelaide
AU-Darwin
AU-Perth
AW-Aruba
CET
AST
AST
CET
AST
ART
BST
CET
LHS
EST
EST
EST
CST
EST
EST
CST
CST
WST
AST
BA-Sarajevo
BB-Barbados
BE-Brussels
BG-Sofia
BM-Bermuda
BO-La Paz
BR-Noronha
BR-Belem
BR-Fortaleza
BR-Recife
BR-Araguaina
BR-Maceio
BR-Sao Paulo
BR-Cuiaba
BR-Porto Velho
BR-Boa Vista
BR-Manaus
BR-Eirunepe
BR-Rio Branco
BS-Nassau
BY-Minsk
BZ-Belize
EET
AST
CET
EET
AST
BOT
FNT
BRT
BRT
BRT
BRS
BRT
BRS
AMS
AMT
AMT
AMT
ACT
ACT
EST
EET
CST
41-001160-00, Release 2.1, Rev 04
Appendix A
Time Zone Name
A-35
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
A-36
Time Zone Name
Time Zone Code
CA-Newfoundland
CA-Atlantic
CA-Eastern
CA-Saskatchewan
CA-Central
CA-Mountain
CA-Pacific
CA-Yukon
CH-Zurich
CK-Rarotonga
CL-Santiago
CL-Easter
CN-China
CO-Bogota
CR-Costa Rica
CU-Havana
CY-Nicosia
CZ-Prague
NST
AST
EST
EST
CST
MST
PST
PST
CET
CKS
CLS
EAS
CST
COS
CST
CST
EES
CET
DE-Berlin
DK-Copenhagen
DM-Dominica
DO-Santo Domingo
CET
CET
AST
AST
EE-Tallinn
ES-Madrid
ES-Canary
EET
CET
WET
FI-Helsinki
FJ-Fiji
FK-Stanley
FO-Faeroe
FR-Paris
EET
NZT
FKS
WET
CET
GB-London
GB-Belfast
GD-Grenada
GF-Cayenne
GI-Gibraltar
GP-Guadeloupe
GR-Athens
GS-South Georgia
GT-Guatemala
GU-Guam
GY-Guyana
GMT
GMT
AST
GFT
CET
AST
EET
GST
CST
CST
GYT
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Time Zone Code
HK-Hong Kong
HN-Tegucigalpa
HR-Zagreb
HT-Port-au-Prince
HU-Budapest
HKS
CST
CET
EST
CET
IE-Dublin
IS-Reykjavik
IT-Rome
GMT
GMT
CET
JM-Jamaica
JP-Tokyo
EST
JST
KY-Cayman
EST
LC-St Lucia
LI-Vaduz
LT-Vilnius
LU-Luxembourg
LV-Riga
AST
CET
EET
CET
EET
MC-Monaco
MD-Chisinau
MK-Skopje
MQ-Martinique
MS-Montserrat
MT-Malta
MX-Mexico City
MX-Cancun
MX-Merida
MX-Monterrey
MX-Mazatlan
MX-Chihuahua
MX-Hermosillo
MX-Tijuana
CET
EET
CET
AST
AST
CET
CST
CST
CST
CST
MST
MST
MST
PST
NI-Managua
NL-Amsterdam
NO-Oslo
NR-Nauru
NU-Niue
NZ-Auckland
NZ-Chatham
CST
CET
CET
NRT
NUT
NZS
CHA
41-001160-00, Release 2.1, Rev 04
Appendix A
Time Zone Name
A-37
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
A-38
Time Zone Name
Time Zone Code
PA-Panama
PE-Lima
PL-Warsaw
PR-Puerto Rico
PT-Lisbon
PT-Madeira
PT-Azores
PY-Asuncion
EST
PES
CET
AST
WET
WET
AZO
PYS
RO-Bucharest
RU-Kaliningrad
RU-Moscow
RU-Samara
RU-Yekaterinburg
RU-Omsk
RU-Novosibirsk
RU-Krasnoyarsk
RU-Irkutsk
RU-Yakutsk
RU-Vladivostok
RU-Sakhalin
RU-Magadan
RU-Kamchatka
RU-Anadyr
EET
EET
MSK
SAM
YEK
OMS
NOV
KRA
IRK
YAK
VLA
SAK
MAG
PET
ANA
SE-Stockholm
SG-Singapore
SI-Ljubljana
SK-Bratislava
SM-San Marino
SR-Paramaribo
SV-El Salvador
CET
SGT
CET
CET
CET
SRT
CST
TR-Istanbul
TT-Port of Spain
TW-Taipei
EET
AST
CST
UA-Kiev
US-Eastern
US-Central
US-Mountain
US-Pacific
US-Alaska
US-Aleutian
US-Hawaii
UY-Montevideo
EET
EST
CST
MST
PST
AKS
HAS
HST
UYS
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Time Zone Code
VA-Vatican
CET
YU-Belgrade
CET
Appendix A
Time Zone Name
SIP Local Dial Plan Settings
)
Parameter –
sip dial plan
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Local Dial Plan
(in Web UI)
Description
A dial plan describes the number and pattern of digits that a user dials to
reach a particular telephone number. The SIP local dial plan is as follows:
Symbol
Description
0, 1, 2, 3, 4, 5, 6, 7, 8, 9
Digit symbol
X
Match any digit symbol (wildcard)
*, #, .
Other keypad symbol; # can terminate
a dial string
|
Expression inclusive OR
+
0 or more of the preceding digit symbol
or [] expression
[]
Symbol inclusive OR
Used only with [], represent a range of
acceptable symbols; For example, [2-8]
“,” (open/close quotes)
In the configuration files, enter the sip dial
plan value using quotes.
Note: You can configure prefix dialing by adding a prepend digit to the
dial string. For example, if you add a prepend map of
“[2-9]XXXXXXXXX,91”, the IP phone adds the digits “91” to any 10-digit
number beginning with any digit from 2 to 9 that is dialed out. Other
examples of prepend mappings are:
•
•
•
1X+#,9 (Prepends 9 to any digit string beginning with “1” and
terminating with “#”.)
6XXX,579 (Prepends “579” to any 4-digit string starting with “6”.)
[4-6]XXXXXX,78 (Prepends “78” to any 7-digit string starting with “4”,
“5”, or “6”.
Format
Alphanumeric characters
Default Value
X+#|XX+*
Range
Up to 127 alphanumeric characters
Example
sip dial plan: "X+#|XXX+*"
41-001160-00, Release 2.1, Rev 04
A-39
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip dial plan terminator
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Send Dial Plan Terminator
(in Web UI)
Description
Allows you to enable or disable a dial plan terminator. If you enable the
use of this parameter, when you configure the IP phone’s dial plan with a
dial plan terminator or timeout (such as the pound symbol (#)), the phone
waits 4 or 5 seconds after you pick up the handset or after to finish
dialing the number on the keypad before making the call.
Format
Boolean
Default Value
0
Range
0 (Disable)
1 (Enable)
Example
sip dial plan terminator: 1
Parameter –
sip digit timeout
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Digit Timeout
(in Web UI)
Description
Represents the time, in seconds, between consecutive key presses on
the IP phone. The default for this parameter is 4 seconds. If you press a
key on the phone and wait 4 seconds before pressing the next key, the
key times out and cancels the digit selection. You must press consecutive
keys before the timeout occurs.
Format
Integer
Default Value
4
Range
Not Applicable
Example
sip digit timeout: 6
A-40
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
SIP Basic, Global Settings
Appendix A
SIP Global Authentication Settings
Parameter –
sip screen name
IP Phone UI
Aastra Web UI
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Screen Name
(in Web UI)
Configuration Files
Description
Used to display text on the screen of the phone. You may want to set
this parameter to display the user’s name of the phone.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip screen name: Joe Smith
Parameter –
sip screen name 2
IP Phone UI
Aastra Web UI
Screen Name 2
(in Web UI)
Configuration Files
Description
Used to display text on a second line on the screen of the phone.
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Notes:
1. If other status messages display on the phone, such as “Network
Disconnected”, the Screen Name 2 value does not display.
2. Symbol characters are allowed (such as “#”).
3. If the text is longer than the display width, than the display truncates
the text to fit the display.
Format
Alphanumeric characters.
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters.
Example
sip screen name 2: Lab Phone
41-001160-00, Release 2.1, Rev 04
A-41
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip user name
IP Phone UI
Aastra Web UI
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Phone Number
(in Web UI)
Configuration Files
Description
Used in the name field of the SIP URI for the IP phone and for registering
the IP phone at the registrar.
Note: The IP Phones support Usernames containing dots (“.”).
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip user name: 1010
Parameter –
sip display name
IP Phone UI
Aastra Web UI
Caller ID
(in Web UI)
Configuration Files
Description
Used in the display name field of the From SIP header field. Some IP
PBX systems use this as the caller’s ID and some may overwrite this
with the string that is set at the PBX system.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip display name: Joe Smith
A-42
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
IP Phone UI
Aastra Web UI
Authentication Name
(in Web UI)
Configuration Files
Description
Used in the username field of the Authorization header field of the SIP
REGISTER request.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip auth name: 5553456
Parameter –
sip password
IP Phone UI
Aastra Web UI
Password
(in Web UI)
Configuration Files
Description
The password that will be used to register at the registrar.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip password: 12345
41-001160-00, Release 2.1, Rev 04
Options->Administrator Menu->>SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
A-43
Appendix A
Parameter –
sip auth name
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip bla number
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
BLA Number
(in Web UI)
Description
Allows you to assign a phone number that is shared across all IP
phones.
Format
Integer
Default Value
Not Applicable
Range
Not Applicable
Example
sip bla number: 1010
Parameter –
sip mode
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Line mode
(in Web UI)
Description
Allows you to configure the mode of the line. Applicable values are:
• Generic - Normal line
• BroadSoft SCA - Shared Call/Line Appearances (SCA) line for
BroadWorks network (call activity can go to more than one phone)
• Nortel - Conference line for Nortel Networks (private - all call activity
goes to one phone)
• BLA - Bridged Line Appearance (BLA) line.
Format
Integer
Default Value
0
Range
Valid values are:
0 - Generic
1 - BroadSoft SCA
2 - Nortel
3 - BLA
Example
sip mode: 2
A-44
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
SIP Global Network Settings.
IP Phone UI
Aastra Web UI
Proxy Server
(in Web UI)
Configuration Files
Description
The IP address of the SIP proxy server for which the IP phone uses to
send all SIP requests.
A SIP proxy is a server that initiates and forwards requests generated by
the IP phone to the targeted user.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not applicable
Example
sip proxy ip: 192.168.0.101
Parameter –
sip proxy port
IP Phone UI
Aastra Web UI
Proxy Port
(in Web UI)
Configuration Files
Description
The proxy server's port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip proxy port: 5060
41-001160-00, Release 2.1, Rev 04
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
A-45
Appendix A
Parameter –
sip proxy ip
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip backup proxy ip
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Backup Proxy Server
(in Web UI)
Description
The IP address of the backup SIP proxy server for which the IP phone
uses when the primary SIP proxy is unavailable.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip backup proxy ip: 192.168.0.102
Parameter –
sip backup proxy port
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Backup Proxy Port
(in Web UI)
Description
The backup proxy’s port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip backup proxy port: 5060
Parameter –
sip outbound proxy
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
outbound proxy server
(in Web UI)
Description
This is the address of the outbound proxy server. All SIP messages
originating from the phone are sent to this server. For example, if you
have a Session Border Controller in your network, then you would
normally set its address here.
Format
IP Address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip outbound proxy: 10.42.23.13
A-46
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
outbound proxy port
(in Web UI)
Description
The proxy port on the proxy server to which the IP phone sends all SIP
messages.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip outbound proxy port: 5060
Parameter –
sip registrar ip
IP Phone UI
Aastra Web UI
Registrar Server
(in Web UI)
Configuration Files
Description
The address of the registrar for which the IP phone uses to send
REGISTER requests.
A SIP registrar is a server that maintains the location information of the
IP phone.
A global value of 0.0.0.0 disables registration. However, the phone is still
active and you can dial using username@ip address of the phone.
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1,
line 2, etc.), then the register request is not sent, the "No Service"
message does not display, and the message waiting indicator (MWI)
does not come on.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip registrar ip: 192.168.0.101
41-001160-00, Release 2.1, Rev 04
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
A-47
Appendix A
Parameter –
sip outbound proxy port
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip registrar port
IP Phone UI
Aastra Web UI
Registrar Port
(in Web UI)
Configuration Files
Description
The registrar's port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip registrar port: 5060
Parameter –
sip backup registrar ip
Aastra Web UI
Configuration Files
Options->Administrator Menu->SIP Settings
Advanced Settings->Global SIP->
Basic SIP Settings
aastra.cfg, <mac>.cfg
Advanced Settings->Global SIP->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Backup Registrar Server
(in Web UI)
Description
The address of the backup registrar (typically, the backup SIP proxy) for
which the IP phone uses to send REGISTER requests if the primary
registrar is unavailable.
A global value of 0.0.0.0 disables backup registration. However, the
phone is still active and you can dial using username@ip address of the
phone.
If the backup registrar IP address is set to 0.0.0.0 for a per-line basis (i.e,
line 1, line 2, etc.), then the backup register request is not sent, the "No
Service" message does not display, and the message waiting indicator
(MWI) does not come on.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip backup registrar ip: 192.168.0.102
A-48
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Appendix A
Parameter –
sip backup registrar port
Backup Registrar Port
(in Web UI)
Description
The backup registrar's (typically the backup SIP proxy) port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip backup registrar port: 5060
Parameter –
sip registration period
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Registration Period
(in Web UI)
Description
The requested registration period, in seconds, from the registrar.
Format
Integer
Default Value
0
Range
0 to 2147483647
Example
sip registration period: 3600
41-001160-00, Release 2.1, Rev 04
A-49
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
SIP Basic, Per-Line Settings
The following parameters are SIP per-line settings. The value of "N" is 1 - 9 for
53i, 55i, 57i, and 57i CT.
SIP Per-Line Authentication Settings
Parameter –
sip lineN screen name
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Screen Name
(in Web UI)
Description
Used to display text on the screen of the phone. You may want to set
this parameter to display the phone user's name.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 screen name: Joe Smith
Parameter –
sip lineN screen name 2
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Screen Name 2
(in Web UI)
Description
Used to display text on a second line on the screen of the phone.
Notes:
1. If other status messages display on the phone, such as “Network
Disconnected”, the Screen Name 2 value does not display.
2. Characters are allowed (such as “#”).
3. If the text is longer than the display width, than the display truncates
the text to fit the display.
Format
Alphanumeric characters
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 screen name 2: Lab Phone
A-50
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Phone Number
(in Web UI)
Description
Used in the name field of the SIP URI for the IP phone and for registering
the IP phone at the registrar.
When configuring per-line BLA on an ININ server, the username must be
incremented as shown in the example for the "sip lineN bla number"
parameter on page A-53.
Note: The IP Phones support Usernames containing dots (“.”).
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 user name: 1010
Parameter –
sip lineN display name
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Caller ID
(in Web UI)
Description
Used in the display name field of the From SIP header field. Some IP
PBX systems use this as the caller’s ID and some may overwrite this
with the string that is set at the PBX system.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 display name: Joe Smith
41-001160-00, Release 2.1, Rev 04
A-51
Appendix A
Parameter –
sip lineN user name
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip lineN auth name
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Authentication Name
(in Web UI)
Description
Used in the username field of the Authorization header field of the SIP
REGISTER request.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 auth name: 5553456
Parameter –
sip lineN password
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Password
(in Web UI)
Description
The password that will be used to register at the registrar.
Format
Text
Default Value
Not Applicable
Range
Up to 20 alphanumeric characters
Example
sip line1 password: 12345
A-52
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
BLA Number
(in Web UI)
Description
Allows you to assign a phone number that is shared on specific lines on
the IP phone.
For Sylantro Server:
When configuring the BLA feature on a Sylantro server, the value set for
the sip lineN bla number parameter shall be the same value set for the
sip lineN user name parameter for all the phones in the group. For
example, if sip lineN user name is 1010, you would configure BLA on a
per-line basis for the Sylantro server as follows:
sip line1 user name: 1010(# for all the phones)
sip line1 bla number: 1010
For ININ Server:
When configuring the BLA feature on an ININ server, the value set for the
sip lineN bla number parameter shall be the same value set for the sip
lineN user name parameter without the incremented digit added to the
phone #. For example, if the sip lineN user name for the first phone is
10101, and the sip lineN user name for the second phone is 10102, etc.
you would configure BLA on a per-line basis for the ININ server as
follows:
sip line1 user name: 10101(# for phone 1 with)
sip line1 bla number: 1010appearance of phone 3)
sip line1 user name: 10102(# for phone 2 with)
sip line1 bla number: 1010appearance of phone 3)
sip line1 user name: 1010(# for phone 3)
sip line1 bla number: 1010
Note: The original phone number which has the bridged line appearance
on other phones, will have the "sip lineN user name" parameter the same
as the "sip lineN bla number" (1010 in the above example on Phone 3).
Format
Integer
Default Value
Not Applicable
Range
Not Applicable
Example
Sylantro Server:
sip line1 bla number: 1010
ININ Server:
sip line 1 bla number: 1010
41-001160-00, Release 2.1, Rev 04
A-53
Appendix A
Parameter –
sip lineN bla number
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip lineN mode
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Line Mode
(in Web UI)
Description
Allows you to configure the mode of the line. Applicable values are:
• Generic - Normal line
• BroadSoft SCA - Shared Call/Line Appearances (SCA) line for
BroadWorks network (call activity can go to more than one phone)
• Nortel - Conference line for Nortel Networks (private - all call activity
goes to one phone)
• BLA - Bridged Line Appearance (BLA) line.
• If the softkeys on the 57i/57i CT or the programmable keys on the 53i
are set as line keys, and you configure that line key for BLA, the key
is configured to use BLA.
Format
Integer
Default Value
0
Range
Valid values are:
0 - Generic
1 - BroadSoft SCA
2 - Nortel
3 - BLA
Example
sip line1 mode: 2
A-54
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
SIP Per-Line Network Settings.
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Proxy Server
(in Web UI)
Description
The IP address of the SIP proxy server for which the IP phone uses to
send all SIP requests.
A SIP proxy is a server that initiates and forwards requests generated by
the IP phone to the targeted user.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not applicable
Example
sip line1 proxy ip: 192.168.0.101
Parameter –
sip lineN proxy port
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Proxy Port
(in Web UI)
Description
The proxy server's port number
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip line1 proxy port: 5060
41-001160-00, Release 2.1, Rev 04
A-55
Appendix A
Parameter –
sip lineN proxy ip
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip linex backup proxy ip
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Backup Proxy Server
(in Web UI)
Description
The IP address of the backup SIP proxy server for which the IP phone
uses when the primary SIP proxy is unavailable.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip line1 backup proxy ip: 192.168.0.102
Parameter –
sip linex backup proxy port
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Backup Proxy Port
(in Web UI)
Description
The backup proxy’s port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip line1 backup proxy port: 5060
Parameter –
sip lineN outbound proxy
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Outbound Proxy Server
(in Web UI)
Description
This is the address of the outbound proxy server. All SIP messages
originating from the phone are sent to this server. For example, if you
have a Session Border Controller in your network, then you would
normally set its address here.
Format
IP Address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip outbound proxy: 10.42.23.13
A-56
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Outbound Proxy Port
(in Web UI)
Description
The proxy port on the proxy server to which the IP phone sends all SIP
messages.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip outbound proxy port: 5060
Parameter –
sip lineN registrar ip
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Registrar Server
(in Web UI)
Description
The address of the registrar for which the IP phone uses to send
REGISTER requests.
A SIP registrar is a server that maintains the location information of the
IP phone.
A global value of 0.0.0.0 disables registration. However, the phone is still
active and you can dial using username@ip address of the phone.
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1,
line 2, etc.), then the register request is not sent, the "No Service"
message does not display, and the message waiting indicator (MWI)
does not come on.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip line1 registrar ip: 192.168.0.101
41-001160-00, Release 2.1, Rev 04
A-57
Appendix A
Parameter –
sip lineN outbound proxy port
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip lineN registrar port
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Registrar Port
(in Web UI)
Description
The registrar's port number
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip line1 registrar port: 5060
Parameter –
sip linex backup registrar ip
Aastra Web UI
Configuration Files
Advanced Settings->LineN->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Backup Registrar Server
(in Web UI)
Description
The address of the backup registrar (typically, the backup SIP proxy) for
which the IP phone uses to send REGISTER requests if the primary
registrar is unavailable.
A global value of 0.0.0.0 disables backup registration. However, the
phone is still active and you can dial using username@ip address of the
phone.
If the backup registrar IP address is set to 0.0.0.0 for a per-line basis (i.e,
line 1, line 2, etc.), then the backup register request is not sent, the "No
Service" message does not display, and the message waiting indicator
(MWI) does not come on.
Format
IP address or fully qualified Domain Name
Default Value
0.0.0.0
Range
Not Applicable
Example
sip line1 backup registrar ip: 192.168.0.102
A-58
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Appendix A
Parameter –
sip linex backup registrar port
Advanced Settings->LineN->
Basic SIP Network Settings
aastra.cfg, <mac>.cfg
Backup Registrar Port
(in Web UI)
Description
The backup registrar's (typically the backup SIP proxy) port number.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip line1 backup registrar port: 5060
Parameter –
sip lineN registration period
Aastra Web UI
Configuration Files
Advanced Settings->Line 1 thru 9
aastra.cfg, <mac>.cfg
Registration Period
(in Web UI)
Description
The requested registration period, in seconds, from the registrar.
Format
Integer
Default Value
0
Range
0 to 2147483647
Example
sip line1 registration period: 3600
41-001160-00, Release 2.1, Rev 04
A-59
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Centralized Conferencing Settings
Global Settings
Parameter –
sip centralized conf
Aastra Web UI
Advanced->Global SIP Settings->
Basic SIP Network Settings
Configuration Files aastra.cfg, <mac>.cfg
Conference Server URI
(in Web UI)
Description
Globally enables or disables SIP centralized conferencing for an IP
phone as follows:
•
To disable centralized conferencing, leave this field empty (blank).
•
To enable SIP centralized conferencing, then do one of the following
actions:
— If you have specified a proxy server/registrar server, then to
reach the media server via the proxy server, set this field to
one of the following:
conf (Sylantro server), or
Conference (Broadsoft server)
By setting this field to conf, you specify conf@<proxy_server
_address>: <proxy_port>. For example, if the proxy server address
is 206.229.26.60 and the proxy port used is 10060, then by setting
this parameter to conf, you are specifying the following:
conf@206.229.26.60:10060
—
To reach the media server using a different address/port than
that specified by the proxy, set this field to the following:
conf@<media_server _address>: <media_port>
Format
String
Default Value
Blank
Example
sip centralized conf: conf
A-60
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Per-Line Settings
Aastra Web UI
Advanced->Line <1 thru 9>->
Basic SIP Network Settings
Configuration Files aastra.cfg, <mac>.cfg
Conference Server URI
(in Web UI)
Description
Enable or disable per-line SIP centralized conferencing for an IP phone
as follows:
•
To disable centralized conferencing, leave this field empty (blank).
•
To enable SIP centralized conferencing on a specific line, do one of
the following actions:
—
If you have specified a proxy server/registrar server, then to
reach the media server via the proxy server, set this field to
one of the following:
conf (Sylantro server), or
Conference (Broadsoft server)
By setting this field to conf, you specify conf@<proxy_server
_address>: <proxy_port>. For example, if the proxy server address
is 206.229.26.60 and the proxy port used is 10060, then by setting
this parameter to conf, you are specifying the following:
conf@206.229.26.60:10060.
—
To reach the media server using a different address/port than
that specified by the proxy, set this field to the following:
conf@<media_server _address>: <media_port>
Format
String
Default Value
Blank
Examples
sip line3 centralized conf: conf
41-001160-00, Release 2.1, Rev 04
A-61
Appendix A
Parameter –
sip lineN centralized conf
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Advanced SIP Settings
Parameter –
sip explicit mwi subscription
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Explicit MWI Subscription
(in Web UI)
Description
If the IP phone has a message waiting subscription with the Service
Provider, a Message Waiting Indicator (MWI) (LED or display icon) tells
the user there is a message on the IP Phone. You can enable and
disable MWI by setting this parameter to the following:
"0" to disable
"1" to enable
Format
Boolean
Default Value
0
Range
0 (disable)
1 (enable)
Example
sip explicit mwi subscription: 1
Parameter –
Aastra Web UI
sip explicit mwi subscription
period
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Explicit MWI Timeout
(in Web UI)
Description
The requested duration, in seconds, before the MWI subscription times
out. The phone re-subscribes to MWI before the subscription period
ends.
Format
Integer
Default Value
86400
Range
30 - 214748364
Example
sip explicit mwi timeout: 30
A-62
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
.
Aastra Web UI:
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
Send MAC Address in
REGISTER Message
(in Web UI)
Description
Adds an "Aastra-Mac:" header to the SIP REGISTER messages sent
from the phone to the call server, where the value is the MAC address of
the phone.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip send mac: 1
Parameter –
sip send line
Aastra Web UI:
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
Send Line Number in
REGISTER Message
(in Web UI)
Description
Adds an "Aastra-Line:" header to the SIP REGISTER messages sent
from the phone to the call server, where the value is the MAC address of
the phone.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip send line: 1
41-001160-00, Release 2.1, Rev 04
A-63
Appendix A
Parameter –
sip send mac
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip session timer
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Session Timer
(in Web UI)
Description
The time, in seconds, that the IP phone uses to send periodic
re-INVITE requests to keep a session alive. The proxy uses these
re-INVITE requests to maintain the status' of the connected sessions.
See RFC4028 for details.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip session timer: 30
Parameter –
sip T1 timer
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
T1 Timer
(in Web UI)
Description
This timer is a SIP transaction layer timer defined in RFC 3261.
Timer 1 is an estimate, in milliseconds, of the round-trip time (RTT).
Format
Integer
Default Value
500
Range
Not Applicable
Example
sip T1 timer: 600
A-64
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
T2 Timer
(in Web UI)
Description
This timer is a SIP transaction layer timer defined in RFC 3261.
Timer 2 represents the amount of time, in milliseconds, a non-INVITE
server transaction takes to respond to a request.
Format
Integer
Default Value
0
Range
Not Applicable
Example
sip T2 timer: 8
Parameter –
sip transaction timer
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Transaction Timer
(in Web UI)
Description
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 designated for this
parameter, the phone assumes the message has timed out.
Format
Integer
Default Value
4000
Range
4000 to 64000
Example
sip transaction timer: 6000
41-001160-00, Release 2.1, Rev 04
A-65
Appendix A
Parameter –
sip T2 timer
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip transport protocol
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Transport Protocol
(in Web UI)
Description
The protocol that the Real-Time Transport Protocol (RTP) port on the IP
phone uses to send out SIP signaling packets.
Notes:
1. If you set the value of this parameter to 4 (TLS), the phone checks
to see if the “sips persistent tls” is enabled. If it is enabled, the phone
uses Persistent TLS on the connection. If “sips persistent tls” is
disabled, then the phone uses TLS on the connection. If TLS is used,
you must specify the Root and Intermediate Certificates, the Local
Certificate, the Private Key, and the Trusted Certificates.
2. If the phone uses Persistent TLS, you MUST specify the Trusted
Certificates; the Root and Intermediate Certificates, the Local
Certificate, and the Private Key are optional.
For more information about Persistent TLS, see “Transport Layer
Security (TLS) Settings” on page A-72.
Format
Integer
Default Value
1 - UDP
Range
Valid values are:
0 - User Datagram Protocol (UDP) and
Transmission Control Protocol (TCP)
1 - UDP
2 - TCP
4 - Transport Layer Security (TLS)
Example
sip transport protocol: 4
A-66
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Registration Failed Retry
Timer
(in Web UI)
Description
Specifies the time, in seconds, that the phone waits between registration
attempts when a registration is rejected by the registrar.
Format
Integer
Default Value
1800 (30 minutes)
Range
30 to 1800
Example
sip registration retry timer: 30
Parameter –
sip registration timeout retry
timer
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Registration Timeout Retry
Timer
(in Web UI)
Description
Specifies the length of time, in seconds, that the phone waits until it
re-attempts to register after a REGISTER message times out.
If this parameter is set lower than 30 seconds, the phone uses a
minimum timer of 30 seconds.
Format
Integer
Default Value
120
Range
30 to 214748364
Example
sip registration timeout retry timer: 150
41-001160-00, Release 2.1, Rev 04
A-67
Appendix A
Parameter –
sip registration retry timer
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip registration renewal timer
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Registration Renewal Timer
(in Web UI)
Description
The length of time, in seconds, prior to expiration, that the phone renews
registrations.
For example, if the value is set to 20, then 20 seconds before the
registration is due to expire, a new REGISTER message is sent to the
registrar to renew the registration.
Format
Integer
Default Value
15
Range
0 to 214748364
The value set for this parameter should be between 0 and the value set
for the registration period.
Example
Parameter –
sip blf subscription period
sip registration renewal timer: 10
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP
->Advanced SIP Settings
aastra.cfg, <mac>.cfg
BLF Subscription Period
(in Web UI)
Description
Specifies the time period, in seconds, that the IP phone resubscribes the
BLF subscription service after a software/firmware upgrade or after a
reboot of the IP phone.
Format
Integer
Default Value
3600
Range
120 (2 minutes is the minimum value)
Example
sip blf subscription period: 2000
A-68
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP
->Advanced SIP Settings
aastra.cfg, <mac>.cfg
ACD Subscription Period
(in Web UI)
Description
Specifies the time period, in seconds, that the IP phone resubscribes the
Automatic Call Distribution (ACD) subscription service after a software/
firmware upgrade or after a reboot of the IP phone.
Format
Integer
Default Value
3600
Range
120 (2 minutes is the minimum value)
Example
sip acd subscription period: 2000
41-001160-00, Release 2.1, Rev 04
A-69
Appendix A
Parameter –
sip acd subscription period
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Missed Call Summary Subscription Settings
Global Parameters
Parameter –
sip missed call summary
subscription
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
Missed Call Summary
Subscription
(in Web UI)
Description
Enables or disables the Missed Call Summary Subscription feature.
This feature allows missed calls that have been redirected by the server,
to be incremented in the missed calls indicator on the phone it was initially
directed to.
For example, phones A, B, and C are connected to the server. You
configure the server to direct calls coming into phone B (which has
voicemail configured) to be forwarded to phone C. When phone A calls
sip missed call summary subscription parameter, phone B receives
notification from the server that the call was forwarded and the missed
calls indicator is incremented on phone B.
Note: You must configure voicemail on the phone that the call was initially
directed to (phone B in the above example).
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip missed call summary subscription: 1
A-70
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
Missed Call Summary
Subscription Period
(in Web UI)
Description
Specifies the amount of time, in seconds, that the phone uses the Missed
Calls Summary Subscription feature. This parameter is always enabled
with a default value of 86400 seconds. When the phone reaches the limit
set for this parameter, it sends the subscription again.
To disable this parameter, leave the field blank or set the field to zero (0).
Format
Integer
Default Value
86400
Range
0 to 99999999
Example
sip missed call summary subscription period: 70000
Per-Line Parameter
Parameter –
sip lineN missed call
summary subscription
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->
Advanced SIP Settings
aastra.cfg, <mac>.cfg
Missed Call Summary
Subscription
(in Web UI)
Description
Enables or disables the Missed Call Summary Subscription feature.
This feature allows missed calls that have been redirected by the server,
to be incremented in the missed calls indicator on the phone it was initially
directed to.
For example, phones A, B, and C are connected to the server. You
configure the server to direct calls coming into phone B (which has
voicemail configured) to be forwarded to phone C. When phone A calls
phone B, the server forwards the call to phone C. If you enable the sip
missed call summary subscription parameter, phone B receives
notification from the server that the call was forwarded and the missed
calls indicator is incremented on phone B.
Note: You must configure voicemail on the phone that the call was initially
directed to (phone B in the above example).
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip line1 missed call summary subscription: 1
41-001160-00, Release 2.1, Rev 04
A-71
Appendix A
Parameter –
sip missed call summary
subscription period
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Transport Layer Security (TLS) Settings
Parameter –
sip transport protocol
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Transport Protocol
(in Web UI)
Description
Specifies the protocol that the RTP port on the IP phone uses to send
out SIP signaling packets.
Notes:
1. If you set the value of this parameter to 4 (TLS), the phone checks
to see if the “sips persistent tls” is enabled. If it is enabled, the phone
uses Persistent TLS on the connection. If “sips persistent tls” is
disabled, then the phone uses TLS on the connection. If TLS is used,
you must specify the Root and Intermediate Certificates, the Local
Certificate, the Private Key, and the Trusted Certificates.
2. If the phone uses Persistent TLS, you MUST specify the Trusted
Certificates; the Root and Intermediate Certificates, the Local
Certificate, and the Private Key are optional.
Format
Integer
Default Value
1 - UDP
Range
Valid values are:
0 - User Datagram Protocol (UDP) and
Transmission Control Protocol (TCP)
1 - UDP
2 - TCP
4 - Transport Layer Security (TLS)
Example
sip transport protocol: 4
A-72
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Configuration Files
aastra.cfg, <mac>.cfg
Description
Enables or disables the use of Persistent Transport Layer Security (TLS).
Persistent TLS sets up the connection to the server once and re-uses that
connection for all calls from the phone. The setup connection for
Persistent TLS is established during the registration of the phone. If the
phones are set to use Persistent TLS, and a call is made from the phone,
this call and all subsequent calls use the same authenticated connection.
This significantly reduces the delay time when placing a call.
Notes:
1. Persistent TLS requires the outbound proxy server and outbound
proxy port parameters be configured in either the configuration files or the
Aastra Web UI (Advanced Settings->Global SIP->Basic SIP Network
Settings). There can be only one persistent TLS connection created per
phone. The phone establishes the TLS connection to the configured
outbound proxy.
2. If you configure the phone to use Persistent TLS, you must also
specify the Trusted Certificate file to use. The Root and Intermediate
Certificates, Local Certificate, and Private Key files are optional.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sips persistent tls: 1
41-001160-00, Release 2.1, Rev 04
A-73
Appendix A
Parameter –
sips persistent tls
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sips root and intermediate
certificates
Aastra Web UI
Configuration Files
Advanced Settings->TLS Support
aastra.cfg, <mac>.cfg
Root and Intermediate
Certificates
(in Web UI)
Description
Allows you to specify the SIP Root and Intermediate Certificate files to use
when the phone uses the TLS transport protocol to setup a call.
The Root and Intermediate Certificate files contain one root certificate and
zero or more intermediate certificates which must be placed in order of
certificate signing with root certificate being the first in the file. If the local
certificate is signed by some well known certificate authority, then that
authority provides the user with the Root and Intermediate Certificate files
(most likely just CA root certificate).
This parameter is required when configuring TLS (optional for Persistent
TLS.)
Note: The certificate files must use the format “.pem”. To create custom
certificate files to use on your IP phone, contact Aastra Technical Support.
Format
<file name>.pem
Default Value
N/A
Range
N/A
Example
sips root and intermediate certificates: cacert_openser.pem
A-74
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->TLS Support
aastra.cfg, <mac>.cfg
Local Certificate
(in Web UI)
Description
Allows you to specify the Local Certificate file to use when the phone uses
the TLS transport protocol to setup a call.
This parameter is required when configuring TLS (optional for Persistent
TLS.)
Note: The certificate file must use the format “.pem”. To create specific
certificate files to use on your IP phone, contact Aastra Technical Support.
Format
<file name>.pem
Default Value
N/A
Range
N/A
Example
sips local certificate: phonesLocalCert.pem
Parameter –
sips private key
Aastra Web UI
Configuration Files
Advanced Settings->TLS Support
aastra.cfg, <mac>.cfg
Private Key
(in Web UI)
Description
Allows you to specify a Private Key file to use when the phone uses the
TLS transport protocol to setup a call.
This parameter is required when configuring TLS (optional for Persistent
TLS.)
Note: The key file must use the format “.pem”. To create specific private
key files to use on your IP phone, contact Aastra Technical Support.
Format
<file name>.pem
Default Value
N/A
Range
N/A
Example
sips private key: phone-privkey.pem
41-001160-00, Release 2.1, Rev 04
A-75
Appendix A
Parameter –
sips local certificate
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sips trusted certificates
Aastra Web UI
Configuration Files
Advanced Settings->TLS Support
aastra.cfg, <mac>.cfg
Trusted Certificates
(in Web UI)
Description
Allows you to specify the Trusted Certificate files to use when the phone
uses the TLS transport protocol to setup a call.
The Trusted Certificate files define a list of trusted certificates. The phone’s
trusted list must contain the CA root certificates for all the servers it is
connecting to. For example, if the phone is connecting to server A which
has a certificate signed by CA1, and server B which has a certificate
signed by CA2, the phone must have CA1 root certificate and CA2 root
certificate in its Trusted Certificate file.
This parameter is required when configuring TLS or Persistent TLS.
Note: The certificate files must use the format “.pem”. To create custom
certificate files to use on your IP phone, contact Aastra Technical Support.
Format
<file name>.pem
Default Value
N/A
Range
N/A
Example
sips trusted certificates: trustedCert.pem
A-76
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
RTP, Codec, DTMF Global Settings
Parameter –
sip rtp port
RTP Port Base
(in IP Phone UI)
IP Phone UI
Aastra Web UI
Configuration Files
Options->Administrator Menu->
SIP Settings->RTP Port Base
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
RTP Port
(in Web UI)
Description
Indicates the port through which the RTP packets are sent. This value
must specify the beginning of the RTP port range on the gateway or
router.
The RTP port is used for sending DTMF tones and for the audio stream.
Your network administrator may close some ports for security reasons.
You may want to use this parameter to send RTP data using a different
port.
Format
Integer
Default Value
3000
Range
Not Applicable
Example
sip rtp port: 3000
Parameter –
sip use basic codecs
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
Basic Codecs
(in Web UI)
Description
Enables or disables basic codecs. Enabling this parameter allows the IP
phone to use the basic Codecs when sending/receiving RTP packets.
Format
Boolean
Default Value
0
Range
0 - Disable
1 - Enable
Example
sip use basic codecs: 1
41-001160-00, Release 2.1, Rev 04
A-77
Appendix A
Global Settings
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip out-of-band dtmf
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
Force RFC2833 Out-of-Band
DTMF
(in Web UI)
Description
Enables or disables out-of-band DTMF. Enabling this parameter forces
the IP phone to use out-of-band DTMF according to RFC2833.
Format
Boolean
Default Value
1
Range
0 - Disable
1 - Enable
Example
sip out-of-band dtmf: 0
Parameter –
sip customized codec
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
Customized Codec Preference
List
(in Web UI)
Description
Specifies a customized Codec preference list which allows you to use
the preferred Codecs for this IP phone.
Format
Comma-separated list of semicolon-separated values
Default Value
Not Applicable
Range
Valid values for the syntax are:
payload
0 for G.711 m-Law
8 for G.711 a-Law
18 for G.729a
Example
A-78
ptime (in milliseconds)
5, 10, 15, 20........90
silsupp
on, off
sip customized codec:
payload=8;ptime=10;silsupp=on,payload=0;ptime=10;
silsupp=off
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
DTMF Method
(in Web UI)
Description
Sets the Dual-tone multifrequency (DTMF) method to use on the IP
phone.
Format
Boolean
Default Value
0 (RTP)
Range
0 (RTP)
1 (SIP INFO)
2 (BOTH)
Example
sip dtmf method: 1
Parameter –
sip srtp mode
Aastra Web UI
Advanced Settings->Global SIP->
RTP Settings
Configuration Files aastra.cfg, <mac>.cfg
RTP Encryption
(in Web UI)
Description
This parameter determines if SRTP is enabled on this IP phone, as
follows:
•
If set to 0, then disable SRTP.
•
If set to 1 then SRTP calls are preferred.
•
If set to 2, then SRTP calls only are generated/accepted.
Format
Integer
Default Value
0 (SRTP Disabled)
Range
0 (SRTP Disabled)
1 (SRTP Preferred)
2 (SRTP Only)
Example
sip srtp mode: 1
41-001160-00, Release 2.1, Rev 04
A-79
Appendix A
Parameter –
sip dtmf method
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip silence suppression
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
Silence Suppression
(in Web UI)
Description
Silence suppression is enabled by default on the IP phones. The phone
negotiates whether or not to use silence suppression. Disabling this
feature forces the phone to ignore any negotiated value.
Format
Boolean
Default Value
1 (enabled)
Range
0 (disabled)
1 (enabled)
Example
sip silence suppression: 0
Per-Line Settings
Parameter –
sip lineN dtmf method
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
DTMF Method
(in Web UI)
Description
Sets the Dual-tone multifrequency (DTMF) method to use on the IP
phone for a specific line.
Format
Integer
Default Value
0 (RTP)
Range
0 (RTP)
1 (SIP INFO)
2 (BOTH)
Example
sip line1 dtmf method: 1
A-80
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Advanced Settings->Line <1-9>->RTP Settings
Configuration Files aastra.cfg, <mac>.cfg
Description
This parameter determines if SRTP is enabled on this line, as follows:
•
If set to -1, then use the global setting for this line. (This is the
default setting.)
•
If set to 0, then disable SRTP.
•
If set to 1 then SRTP calls are preferred.
•
If set to 2, then SRTP calls only are generated/accepted.
Format
Integer
Default Value
0 (disabled)
Range
-1
0
1
2
Example
sip line1 mode: 1
Autodial Settings
Global Settings
Parameter –
sip autodial number
Aastra Web UI
Advanced Settings>Global SIP>
Autodial Settings
Configuration Files aastra.cfg, <mac>.cfg
Autodial Number
(in Web UI)
Description
Globally specifies the SIP phone number that the IP phone autodials
when the handset is lifted from the phone cradle. An empty (blank)
value disables autodial on the phone.
Format
Integer
Default Value
Blank
Range
Any valid SIP number
Examples
sip autodial number: 8500
41-001160-00, Release 2.1, Rev 04
A-81
Appendix A
Parameter –
sip lineN srtp mode
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip autodial timeout
Aastra Web UI
Advanced Settings>Global SIP>
Autodial Settings
Configuration Files aastra.cfg, <mac>.cfg
Autodial Timeout
(in Web UI)
Description
Globally specifies the time, in seconds, that the phone waits to dial a
preconfigured number after the handset is lifted from the IP phone
cradle.
If this parameter is set to 0 (hotline), the phone immediately dials a
preconfigured number when you lift the handset. If this parameter is set
to a value greater than 0, the phone waits the specified number of
seconds before dialing the preconfigured number (warmline) when you
lift the handset.
Default is 0 (hotline).
Format
Integer
Default Value
0
Range
0 to 120
Examples
sip autodial timeout: 30
A-82
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Per-Line Settings
Aastra Web UI
Advanced Settings>LineN>Autodial Settings
Configuration Files aastra.cfg, <mac>.cfg
Autodial Number
(in Web UI)
Description
On a per-line basis, this parameter specifies the SIP phone number that
the IP phone autodials when the handset is lifted from the phone cradle.
Valid values can be:
-1
Blank
Valid SIP Number
(Default) The phone uses the global
autodial setting for this line.
(Empty field) Disables autodial on this line.
Dials the SIP number specified for this line.
Format
Integer
Default Value
-1
Range
Any valid SIP number.
Examples
sip line1 autodial number: 8500
Parameter –
sip lineN autodial timeout
Aastra Web UI
Advanced Settings>LineN>Autodial Settings
Configuration Files aastra.cfg, <mac>.cfg
AutoDial Timeout
(in Web UI)
Description
On a per-line basis, this parameter specifies the time, in seconds, that
the phone waits to dial a preconfigured number after the handset is
lifted from the IP phone cradle.
If this parameter is set to 0 (hotline), the phone immediately dials a
preconfigured number when you lift the handset. If this parameter is set
to a value greater than 0, the phone waits the specified number of
seconds before dialing the preconfigured number (warmline) when you
lift the handset.
Default is 0 (hotline).
Format
Integer
Default Value
0
Range
0 to 120
Examples
sip line1 autodial timeout: 30
41-001160-00, Release 2.1, Rev 04
A-83
Appendix A
Parameter –
sip lineN autodial number
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Voicemail Settings
Parameter –
sip lineN vmail
Configuration Files
aastra.cfg, <mac>.cfg
Note: The value of "N" is 1 - 9
for 53i, 55i, 57i, 57i CT.
Description
Use this parameter in the <mac>.cfg file to configure the phone to dial a
specific number to access an existing voicemail account on a Service
Provider’s server. The user then follows the voicemail instructions for
listening to voicemails.
Note: The phone must have a registered voicemail account from a
server for this feature to be enabled.
When no registered voicemail accounts are registered to the phone, the
display shows "List Empty".
The phone displays up to 99 voicemails for an account even if the
number of voicemails exceeds the limit.
Registered account numbers/URIs that exceed the length of the screen,
either with or without the voicemail icon and the message count, are
truncated with an ellipse character at the end of the number/URI string.
Format
Integer
Default Value
Not Applicable
Range
0 to 99
Example
sip line1 vmail: *97
Note: In the above example, the user would dial *97 to access the
voicemail account.
A-84
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Directory Settings
Aastra Web UI
Configuration Files
Operation->Directory
aastra.cfg, <mac>.cfg
Directory List
(in Web UI)
Description
The name of a directory list that you can download from the configuration
server.
Format
Alphanumeric characters
Default Value
Not Applicable
Range
Not Applicable
Example
directory 1: companylist.csv
Parameter –
directory 2
Aastra Web UI
Configuration Files
Operation->Directory
aastra.cfg, <mac>.cfg
Directory List
(in Web UI)
Description
The name of a directory list that you can download from the configuration
server.
Format
Alphanumeric characters
Default Value
Not Applicable
Range
Not Applicable
Example
directory 2: personallist.csv
Parameter –
directory disabled
Configuration Files
Description
Enables or disables 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 57i and 57i CT
the "Directory" option is also removed from the "Services" menu.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
directory disabled: 1
41-001160-00, Release 2.1, Rev 04
aastra.cfg, <mac>.cfg
A-85
Appendix A
Parameter –
directory 1
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Callers List Settings
Parameter –
callers list disabled
Configuration Files
aastra.cfg, <mac>.cfg
Description
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 57i and 57i 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.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
callers list disabled: 1
Customize Callers List and Services Key
Parameter –
services script
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a specific URI for accessing services after
pressing the Services key. When this parameter is set, it overrides the
standard function of the Services key.
Format
Alphanumeric characters
Default Value
N/A
Range
N/A
Example
services script: http://10.50.100.234/test.xml
Parameter –
callers list script
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a specific URI for accessing the Callers List after
pressing the Callers List key. When this parameter is set, it overrides
the standard function of the Callers List key.
Format
Alphanumeric characters
Default Value
N/A
Range
N/A
Example
callers list script: http://10.50.100.234/test.xml
A-86
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Call Forward Settings
Configuration Files
Description
Enables or disables the ability to configure Call Forwarding. If this
parameter is set to 0, a user and administrator can configure Call
Forwarding via the Aastra Web UI and the IP Phone UI using the "Call
Forward" 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 Forwarding.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
call forward disabled: 1
41-001160-00, Release 2.1, Rev 04
aastra.cfg, <mac>.cfg
A-87
Appendix A
Parameter –
call forward disabled
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Missed Calls Indicator Settings
Parameter –
missed calls indicator
disabled
Configuration Files
Description
Enables or disables the Missed Calls Indicator. If the "missed calls
indicator disabled" parame.ter 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.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
missed calls indicator disabled: 1
A-88
aastra.cfg, <mac>.cfg
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
XML Settings
Configuration Files
Description
Allows you to specify a timeout value, in seconds, that the phone waits
for the far side to return a response after accepting the HTTP GET
connection. If the far side accepts the GET connection but never returns
a response, it blocks the phone until it is rebooted. If you enter a value
greater than 0 for this parameter, the phone times out and will not be
blocked.
Format
Integer
Default Value
0 (never timeout)
Range
0 to 214748364 seconds
Example
xml get timeout: 20
Parameter –
xml application URI
Aastra Web UI
Configuration Files
aastra.cfg, <mac>.cfg
Operation->Softkeys and XML->Services
aastra.cfg, <mac>.cfg
XML Application URI
(in Web UI)
Description
This is the XML application you are loading into the IP phone configuration.
Format
HTTP server path or fully qualified Domain Name
Default Value
Not Applicable
Range
Not Applicable
Example
xml application URI: http://172.16.96.63/aastra/internet.php
41-001160-00, Release 2.1, Rev 04
A-89
Appendix A
Parameter –
xml get timeout
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
xml application title
Aastra Web UI
Configuration Files
Operation->Softkeys and XML->Services
aastra.cfg, <mac>.cfg
XML Application Title
(in Web UI)
Description
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.
Format
Alphanumeric characters
Default Value
Not Applicable
Range
Not Applicable
Example
xml application title: Traffic Reports
Parameter –
xml application post list
Aastra Web UI
Configuration Files
Advanced Settings->Configuration Server
aastra.cfg, <mac>.cfg
XML Push Server List
(Approved IP Addresses)
(in Web UI)
Description
The HTTP server that is pushing XML applications to the IP phone.
Format
IP address in dotted decimal format and/or Domain name address
Default Value
Not Applicable
Range
Not Applicable
Example
xml application post list: 10.50.10.53,
dhcp10-53.ana.aastra.com
A-90
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Basic Settings->Preferences
Configuration Files aastra.cfg, <mac>.cfg
XML Beep Support
(in Web UI)
Description
Enables or disables a BEEP notification on the phone when a status
message object (AastraIPPhoneStatus) containing a “beep” attribute
arrives to the phone.
Changes to this parameter are applied immediately.
Format
Boolean
Default Value
1 (ON)
Range
0 (OFF)No beep is audible even if the beep attribute is present in
the XML object.
1 (ON)The phone beeps when an XML object with the “beep”
attribute arrives to the phone.
Example
xml beep notification: 0
Parameter –
xml status scroll delay
Aastra Web UI
Basic Settings->Preferences
Configuration Files aastra.cfg, <mac>.cfg
Status Scroll Delay (seconds)
(in Web UI)
Description
Specifies the length of time, in seconds, that each XML status
message displays on the phone.
Note: Changes to this parameter are applied immediately.
Format
Integer
Default Value
5
Range
1 to 25
Example
xml status scroll delay: 3
41-001160-00, Release 2.1, Rev 04
A-91
Appendix A
Parameter –
xml beep notification
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Action URI Settings
Parameter –
action uri startup
Aastra Web UI
Configuration Files
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Startup
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when a startup
event occurs.
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri startup: http://10.50.10.140/startup
Parameter –
action uri registered
Aastra Web UI
Configuration Files
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Successful Registration
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when a
successful registration event occurs. This parameter can use the
following variables:
$$SIPUSERNAME$$
$$SIPAUTHNAME$$
$$PROXYURL$$
Note: The “action uri registered” parameter executes on the first
successful registration of each unique line configured on the phone.
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri registered: http://10.50.10.14/registered.php?auth
name=$$SIPAUTHNAME$$
A-92
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Appendix A
Parameter –
action uri incoming
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Incoming Call
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when an
incoming call event occurs. This parameter can use the following
variables:
$$REMOTENUMBER$$
$$DISPLAYNAME$$
$$SIPUSERNAME$$
$$INCOMINGNAME$$
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri incoming: http://10.50.10.140/
incoming.php?number=$$REMOTENUMBER$$
Parameter –
action uri outgoing
Aastra Web UI
Configuration Files
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Outgoing Call
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when an
outgoing call event occurs. This parameter can use the following
variables:
$$REMOTENUMBER$$
$$SIPUSERNAME$$
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri outgoing: http://10.50.10.140/
outgoing.php?number=$$REMOTENUMBER$$
41-001160-00, Release 2.1, Rev 04
A-93
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
action uri offhook
Aastra Web UI
Configuration Files
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Offhook
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when an
offhook event occurs.
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri offhook: http://10.50.10.140/offhook
Parameter –
action uri onhook
Aastra Web UI
Configuration Files
Advanced Settings->Action URI
aastra.cfg, <mac>.cfg
Onhook
(in Web UI)
Description
Specifies the URI for which the phone executes a GET on when an
onhook event occurs.
Format
Fully qualified URI
Default Value
Not Applicable
Range
Up to 128 ASCII characters
Example
action uri onhook: http://10.50.10.140/onhook
Ring Tone and Tone Set Global Settings
Parameter –
ring tone
Global Ring Tone
(in Web UI)
IP Phone UI
Aastra Web UI:
Configuration Files
Options->Tones->Set Ring Tone
Basic Settings->Preferences->Ring Tones
aastra.cfg, <mac>.cfg
Description
Globally sets the type of ring tone on the IP phone. Ring tone can be set
to one of six distinct rings.
Format
Integer
Default Value
Aastra Web UI:
Tone 1
IP Phone UI:
Tone 1
Configuration Files: 0 (Tone 1)
A-94
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Range
Appendix A
Aastra Web UI & IP Phone UI
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Silent
Configuration Files
0 (Tone 1)
1 (Tone 2)
2 (Tone 3)
3 (Tone 4)
4 (Tone 5)
5 (Silent)
Example
ring tone: 3
41-001160-00, Release 2.1, Rev 04
A-95
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
tone set
Tone Set
(in Web UI)
IP Phone UI
Aastra Web UI:
Configuration Files
Options->Tones->Tone Set
Basic Settings->Preferences->Ring Tones
aastra.cfg, <mac>.cfg
Description
Globally sets a tone set for a specific country.
Format
Text
Default Value
US
Range
Australia
Europe (generic tones)
France
Germany
Italy
Mexico
United Kingdom (UK)
US (also used in Canada)
Example
tone set: Germany
A-96
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Ring Tone Per-Line Settings
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->Ring Tones
aastra.cfg, <mac>.cfg
Line N
(in Web UI)
Description
Sets the type of ring tone on the IP phone on a per-line basis. Ring tone
can be set to one of six distinct rings.
Format
Integer
Default Value
Aastra Web UI:
Configuration Files:
Range
Aastra Web UI
Global
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Silent
Global
-1 (Global)
Configuration Files
-1 (Global)
0 (Tone 1)
1 (Tone 2)
2 (Tone 3)
3 (Tone 4)
4 (Tone 5)
5 (Silent)
Example
line1 ring tone 3
41-001160-00, Release 2.1, Rev 04
A-97
Appendix A
Parameter –
lineN ring tone
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Incoming Call Interrupts Dialing Setting
Parameter –
incoming call interrupts
dialing
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Incoming Call Interrupts
Dialing
(in Web UI)
Description
Enable or disables how the phone handles incoming calls while the phone
is dialing out.
When you enable this parameter (1 = true), an incoming call interrupts the
outgoing call during dialing and allows the phone to ring for the user to
answer the incoming call.
When you disable this parameter (0 = false), which is the default, the
phone does not interrupt the outgoing call during dialing and instead rings
the incoming call on another free line (or sends busy signal if all
remaining lines are busy). You have a choice to ignore the incoming call,
or answer the incoming call on another line, via the Ignore and Answer
softkeys that display. If you choose to answer the incoming call, you can
answer the call, finish the call, and then hang up. You can still go back to
the original outgoing call and finish dialing out.
Notes:
1. On a 53i, you must use the up and down arrow keys to ignore or
answer the call.
2. On all phone models, if you disable this parameter (0=disable), and the
phone receives an incoming call while you are dialing an outgoing call,
you can pick up the call and perform transfer or conference as required.
After enabling or disabling this feature, it takes affect on the phone
immediately.
Format
Boolean
Default Value
0 (false)
Range
0 (false)
1 (true)
Example
incoming call interrupts dialing: 1
A-98
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Goodbye Key Cancels Incoming Call
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Goodbye Key Cancels
Incoming Call
(in Web UI)
Description
Enable or disables the behavior of the Goodbye Key on the IP phone.
When you enable this parameter (1 = enable), the Goodbye key rejects
the incoming call. When you disable this parameter (0 = disable), the
Goodbye key hangs up the active call.
For the 55i, 57i, and 57i CT:
If you enable this parameter, and the phone receives another call when
an active call is already present, the phone displays softkey 1 as
“answer” and softkey 2 as “ignore”. You can press the required softkey
as applicable.
For the 53i:
If you enable this parameter, and the phone receives another call when
an active call is already present, the “ignore” option only displays in the
LCD window. The phone ignores the incoming call. If you press the
DOWN arrow key, the phone answers the incoming call.
Note: After enabling or disabling this feature, it takes affect on the phone
immediately.
Format
Boolean
Default Value
1 (true)
Range
0 (false)
1 (true)
Example
goodbye cancels incoming call: 0
41-001160-00, Release 2.1, Rev 04
A-99
Appendix A
Parameter –
goodbye cancels incoming
call
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Stuttered Dial Tone Setting
Parameter –
stutter disabled
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Stuttered Dial Tone
(in Web UI)
Description
Enable or disables the playing of a stuttered dial tone when there is a
message waiting on the IP phone.
Format
Boolean
Default Value
0 (false)
Range
0 (false)
1 (true)
Example
stuttered disabled: 1
A-100
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Call Waiting Settings
Aastra Web UI
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Call Waiting
(in Web UI)
Description
Allows you to enable or disable Call Waiting on the IP phone.
If you enable call waiting (default), the user has the option of accepting a
second call while currently on the first call. If you disable call waiting, and
a user is currently on a call, a second incoming call is automatically
rejected by the phone with a busy message.
If you disable call waiting on the phone, and the user is on a call, any
further incoming calls will receive busy unless “Call Forward Busy” or “Call
Forward No Answer and Busy” is configured on the phone. It will then
forward the call according to the rule configured. The phone can only:
• -transfer the currently active call
or
• accept transferred calls if there is no active calls.
If call waiting is disabled:
• on the 57i CT base, and the handset is currently on a call, all additional
incoming calls are rejected on the handset.
• intercom calls are treated as regular incoming calls and are rejected.
• pre-dialing with live dial pad disabled still accepts incoming calls.
• the “Incoming Call Cancels Dialing” parameter is ignored because the
incoming call is automatically rejected.
• the Missed Calls List does not get updated with details of calls.
• the Blind Transfer feature on the phone may not work if two calls are
made to the phone at one time.
Format
Boolean
Default Value
1 (enabled)
Range
0 (disabled)
1 (enabled)
Example
call waiting: 0
41-001160-00, Release 2.1, Rev 04
A-101
Appendix A
Parameter –
call waiting
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
call waiting tone
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Play Call Waiting Tone
(in Web UI)
Description
Enable or disables the playing of a call waiting tone when a caller is on an
active call and a new call comes into the phone.
Note: The Call Waiting Tone feature works only if the Call Waiting
parameter is enabled.
Format
Boolean
Default Value
1 (enabled)
Range
0 (disable)
1 (enabled)
Example
call waiting tone: 0
Message Waiting Indicator Settings
Parameter –
mwi led line
Aastra Web UI
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Message Waiting Indicator
Line
(in Web UI)
Description
Allows you to enable the Message Waiting Indicator (MWI) on a single
line or on all lines on the phone. For example, if you set this parameter to
3, the LED illuminates if a voice mail is pending on line 3. If you set this
parameter to 0, the LED illuminates if a voice mail is pending on any line
on the phone (lines 1 through 9).
Note: To enable MWI for all lines in the configuration files, set this
parameter to zero (0). The enable MWI for all lines in the Aastra Web UI,
select “All” in the “Message Waiting Indicator Line” field.
Format
Integer
Default Value
0 (all lines)
Range
0 to 9
Example
mwi led line: 3
A-102
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Priority Alert Settings
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Enable Priority Alerting
(in Web UI)
Description
Enables and disables distinctive ringing on the IP phone for incoming
calls and call-waiting calls.
Format
Boolean
Default Value
1 (true)
Range
0 (false)
1 (true)
Example
priority alerting enabled: 0
For Sylantro Server only
Parameter –
alert auto call distribution
auto call distribution
(in Web UI)
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert-acd" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert auto call distribution: 2
41-001160-00, Release 2.1, Rev 04
A-103
Appendix A
Parameter –
priority alerting enabled
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
alert community 1
community-1
(in Web UI)
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert community-1” keyword appears in the header of the
INVITE request, the configured Bellcore ring tone is applied to the IP
phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert community 1: 3
Parameter –
alert community 2
Aastra Web UI:
community-2
(in Web UI)
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert community-2” keyword appears in the header of the
INVITE request, the configured Bellcore ring tone is applied to the IP
phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert community 2: 4
A-104
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
community-3
(in Web UI)
Description
When an "alert community-3” keyword appears in the header of the
INVITE request, the configured Bellcore ring tone is applied to the IP
phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert community 3: 1
Parameter –
alert community 4
Aastra Web UI:
community-4
(in Web UI)
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert community-4” keyword appears in the header of the
INVITE request, the configured Bellcore ring tone is applied to the IP
phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert community 4: 2
41-001160-00, Release 2.1, Rev 04
A-105
Appendix A
Parameter –
alert community 3
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
alert external
alert external
(in Web UI)
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert external" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert external: 4
Parameter –
alert emergency
Aastra Web UI:
alert emergency
(in Web UI)
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert emergency" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert emergency: 4
A-106
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Group
(in Web UI)
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert group" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert group: 4
Parameter –
alert internal
Aastra Web UI:
alert internal
(in Web UI)
Configuration Files
Appendix A
Parameter –
alert group
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert-internal" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert internal: 4
41-001160-00, Release 2.1, Rev 04
A-107
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
alert priority
alert priority
(in Web UI)
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Priority Alerting Settings
aastra.cfg, <mac>.cfg
Description
When an "alert priority" keyword appears in the header of the INVITE
request, the configured Bellcore ring tone is applied to the IP phone.
Format
Integer
Default Value
0
Normal ringing
Range
0
1
2
3
4
5
Normal ringing (default)
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Silent
Example
alert priority: 4
A-108
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Language Settings
IP Phone UI
Aastra Web UI
Webpage Language
(in Web UI)
Configuration File
Description
The language you want to display in the IP Phone UI and the Aastra Web
UI.
Options->Language
Basic Settings->Preferences->
Language Settings->Webpage Language
aastra.cfg, <mac>.cfg
Valid values for 53i, 55i, 57i are:
0 (English)
1 (French)
2 (Spanish)
3 (German)
4 (Italian)
Valid values for 57i CT are:
0 (English)
1 (French)
2 (Spanish)
Note: All languages may not be available for selection. The available
languages are dependant on the language packs currently loaded to the
IP phone. For more information about loading language packs, see
“Loading Language Packs” on page 5-21.
Format
Integer
Default Value
0
Range
0 to 4 (for 53i, 55i, 57i)
0 to 2 (for 57i CT)
Example
language: 2
language: 3
language: 4
41-001160-00, Release 2.1, Rev 04
A-109
Appendix A
Parameter –
language
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Language Pack Settings
Parameter –
language N
Aastra Web UI
Configuration File
Basic Settings->Preferences->
Language Settings
<mac>.cfg
Language N
(in Web UI)
Where “N” can be 1, 2, 3, or
4
Description
The language pack you want to load to the IP phone.
Valid values are:
lang_fr_ca.txt
lang_es_mx.txt
lang_de.txt
lang_it.txt
Notes:
1. The languages packs you load are dependant on available language
packs from the configuration server. For more information about loading
language packs, see “Loading Language Packs” on page 5-21.
2. You must reboot the phone to load a language pack.
Format
lang_<ISO 639>-<ISO 3166>.txt
or
lang_<ISO 639>.txt
Note: For valid values for <ISO 639> and <ISO 3166>, see “Language
Codes (from Standard ISO 639)” on page A-111 and “Country Codes
(from Standard ISO 3166)” on page A-111.
Default Value
N/A
Range
N/A
Example
language 1: lang_fr_ca.txt
language 2: lang_es_mx.txt
language 3: lang_de.txt
language 4: lang_it.txt
A-110
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Language Codes (from Standard ISO 639)
Language
Language Code
English
en
French
fr-ca
Spanish
es
German
de
Italian
it
The following table identifies the country codes to use for the IP phone language
packs.
Country Codes (from Standard ISO 3166)
Country
Country Code
AFGHANISTAN
ÅLAND ISLANDS
ALBANIA
ALGERIA
AMERICAN SAMOA
ANDORRA
ANGOLA
ANGUILLA
ANTARCTICA
ANTIGUA AND BARBUDA
ARGENTINA
ARMENIA
ARUBA
AUSTRALIA
AUSTRIA
AZERBAIJAN
AF
AX
AL
DZ
AS
AD
AO
AI
AQ
AG
AR
AM
AW
AU
AT
AZ
41-001160-00, Release 2.1, Rev 04
A-111
Appendix A
The following table identifies the language code to use for the IP phone language
packs.
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Country
Country Code
BAHAMAS
BAHRAIN
BANGLADESH
BARBADOS
BELARUS
BELGIUM
BELIZE
BENIN
BERMUDA
BHUTAN
BOLIVIA
BOSNIA AND HERZEGOVINA
BOTSWANA
BOUVET ISLAND
BRAZIL
BRITISH INDIAN OCEAN TERRITORY
BRUNEI DARUSSALAM
BULGARIA
BURKINA FASO
BURUNDI
BS
BH
BD
BB
BY
BE
BZ
BJ
BM
BT
BO
BA
BW
BV
BR
IO
BN
BG
BF
BI
CAMBODIA
CAMEROON
CANADA
CAPE VERDE
CAYMAN ISLANDS
CENTRAL AFRICAN REPUBLIC
CHAD
CHILE
CHINA
CHRISTMAS ISLAND
COCOS (KEELING) ISLANDS
COLOMBIA
COMOROS
CONGO
CONGO, THE DEMOCRATIC REPUBLIC OF THE
COOK ISLANDS
COSTA RICA
CÔTE D'IVOIRE
CROATIA
CUBA
CYPRUS
CZECH REPUBLIC
KH
CM
CA
CV
KY
CF
TD
CL
CN
CX
CC
CO
KM
CG
CD
CK
CR
CI
HR
CU
CY
CZ
A-112
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Country Code
DENMARK
DJIBOUTI
DOMINICA
DOMINICAN REPUBLIC
DK
DJ
DM
DO
ECUADOR
EGYPT
EL SALVADOR
EQUATORIAL GUINEA
ERITREA
ESTONIA
ETHIOPIA
EC
EG
SV
GQ
ER
EE
ET
FALKLAND ISLANDS (MALVINAS)
FAROE ISLANDS
FIJI
FINLAND
FRANCE
FRENCH GUIANA
FRENCH POLYNESIA
FRENCH SOUTHERN TERRITORIES
FK
FO
FJ
FI
FR
GF
PF
TF
GABON
GAMBIA
GEORGIA
GERMANY
GHANA
GIBRALTAR
GREECE
GREENLAND
GRENADA
GUADELOUPE
GUAM
GUATEMALA
GUERNSEY
GUINEA
GUINEA-BISSAU
GUYANA
GA
GM
GE
DE
GH
GI
GR
GL
GD
GP
GU
GT
GG
GN
GW
GY
HAITI
HEARD ISLAND AND MCDONALD ISLANDS
HOLY SEE (VATICAN CITY STATE)
HONDURAS
HONG KONG
HUNGARY
HT
HM
VA
HN
HK
HU
41-001160-00, Release 2.1, Rev 04
Appendix A
Country
A-113
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Country
Country Code
ICELAND
INDIA
INDONESIA
IRAN, ISLAMIC REPUBLIC OF
IRAQ
IRELAND
ISLE OF MAN
ISRAEL
ITALY
IS
IN
ID
IR
IQ
IE
IM
IL
IT
JAMAICA
JAPAN
JERSEY
JORDAN
JM
JP
JE
JO
KAZAKHSTAN
KENYA
KIRIBATI
KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF
KOREA, REPUBLIC OF
KUWAIT
KYRGYZSTAN
KZ
KE
KI
KP
KR
KW
KG
LAO PEOPLE'S DEMOCRATIC REPUBLIC
LATVIA
LEBANON
LESOTHO
LIBERIA
LIBYAN ARAB JAMAHIRIYA
LIECHTENSTEIN
LITHUANIA
LUXEMBOURG
LA
LV
LB
LS
LR
LY
LI
LT
LU
A-114
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Country Code
MACAO
MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF
MADAGASCAR
MALAWI
MALAYSIA
MALDIVES
MALI
MALTA
MARSHALL ISLANDS
MARTINIQUE
MAURITANIA
MAURITIUS
MAYOTTE
MEXICO
MICRONESIA, FEDERATED STATES OF
MOLDOVA, REPUBLIC OF
MONACO
MONGOLIA
MONTENEGRO
MONTSERRAT
MOROCCO
MOZAMBIQUE
MYANMAR
MO
MK
MG
MW
MY
MV
ML
MT
MH
MQ
MR
MU
YT
MX
FM
MD
MC
MN
ME
MS
MA
MZ
MM
NAMIBIA
NAURU
NEPAL
NETHERLANDS
NETHERLANDS ANTILLES
NEW CALEDONIA
NEW ZEALAND
NICARAGUA
NIGER
NIGERIA
NIUE
NORFOLK ISLAND
NORTHERN MARIANA ISLANDS
NORWAY
NA
NR
NP
NL
AN
NC
NZ
NI
NE
NG
NU
NF
MP
NO
OMAN
OM
41-001160-00, Release 2.1, Rev 04
Appendix A
Country
A-115
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Country
Country Code
PAKISTAN
PALAU
PALESTINIAN TERRITORY, OCCUPIED
PANAMA
PAPUA NEW GUINEA
PARAGUAY
PERU
PHILIPPINES
PITCAIRN
POLAND
PORTUGAL
PUERTO RICO
PK
PW
PS
PA
PG
PY
PE
PH
PN
PL
PT
PR
QATAR
QA
RÉUNION
ROMANIA
RUSSIAN FEDERATION
RWANDA
RE
RO
RU
RW
A-116
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Country Code
SAINT HELENA
SAINT KITTS AND NEVIS
SAINT LUCIA
SAINT PIERRE AND MIQUELON
SAINT VINCENT AND THE GRENADINES
SAMOA
SAN MARINO
SAO TOME AND PRINCIPE
SAUDI ARABIA
SENEGAL
SERBIA
SEYCHELLES
SIERRA LEONE
SINGAPORE
SLOVAKIA
SLOVENIA
SOLOMON ISLANDS
SOMALIA
SOUTH AFRICA
SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS
SPAIN
SRI LANKA
SUDAN
SURINAME
SVALBARD AND JAN MAYEN
SWAZILAND
SWEDEN
SWITZERLAND
SYRIAN ARAB REPUBLIC
SH
KN
LC
PM
VC
WS
SM
ST
SA
SN
RS
SC
SL
SG
SK
SI
SB
SO
ZA
GS
ES
LK
SD
SR
SJ
SZ
SE
CH
SY
TAIWAN, PROVINCE OF CHINA
TAJIKISTAN
TANZANIA, UNITED REPUBLIC OF
THAILAND
TIMOR-LESTE
TOGO
TOKELAU
TONGA
TRINIDAD AND TOBAGO
TUNISIA
TURKEY
TURKMENISTAN
TURKS AND CAICOS ISLANDS
TUVALU
TW
TJ
TZ
TH
TL
TG
TK
TO
TT
TN
TR
TM
TC
TV
41-001160-00, Release 2.1, Rev 04
Appendix A
Country
A-117
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Country
Country Code
UGANDA
UKRAINE
UNITED ARAB EMIRATES
UNITED KINGDOM
UNITED STATES
UNITED STATES MINOR OUTLYING ISLANDS
URUGUAY
UZBEKISTAN
UG
TA
AE
GB
US
TM
UY
UZ
VANUATU
Vatican City State
VENEZUELA
VIET NAM
VIRGIN ISLANDS, BRITISH
VIRGIN ISLANDS, U.S.
VU
see HOLY SEE
VE
VN
VG
VI
WALLIS AND FUTUNA
WESTERN SAHARA
WF
EH
YEMEN
YE
Zaire
see CONGO, THE DEMOCRATIC
REPUBLIC OF THE
ZM
ZW
ZAMBIA
ZIMBABWE
A-118
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Suppress DTMF Playback Setting
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Suppress DTMF Playback
(in Web UI)
Description
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.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
suppress dtmf playback: 1
41-001160-00, Release 2.1, Rev 04
A-119
Appendix A
Parameter –
suppress dtmf playback
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Display DTMF Digits Setting
Parameter –
display dtmf digits
Aastra Web UI
Configuration Files
Basic Settings->Preferences->General
aastra.cfg, <mac>.cfg
Display DTMF Digits
(in Web UI)
Description
Enables and disables the display of DTMF digits when dialing on the IP
phone.
DTMF is the signal sent from the phone to the network that you generate
when you press the phone’s touch keys. This is also known as “touchtone”
dialing. Each key you press on your phone generates two tones of specific
frequencies. One tone is generated from a high-frequency group of tones
and the other from a low frequency group.
If enabled, this parameter displays the digits on the IP phone display if you
are dialing from the keypad, or from a softkey or programmable key. This
parameter is disabled by default (no digits display when dialing).
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
display dtmf digits: 1
A-120
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Intercom, Auto-Answer, and Barge In Settings
Parameter –
sip intercom type
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Outgoing Intercom Settings
aastra.cfg, <mac>.cfg
Type
(in Web UI)
Description
Determines whether the IP phone or the server is responsible for notifying
the recipient that an Intercom call is being placed.
Format
Integer
Default Value
For Aastra Web UI:
Off
For Configuration Files:
3 - Off
Range
For Aastra Web UI:
Phone-Side
Server-Side
Off
For Configuration Files:
1 - Phone-Side
2 - Server-Side
3 - Off
Example
sip intercom type: 1
41-001160-00, Release 2.1, Rev 04
A-121
Appendix A
Outgoing Intercom Settings
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip intercom prefix code
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Outgoing Intercom Settings
aastra.cfg, <mac>.cfg
Prefix Code
(in Web UI)
Description
The prefix to add to the phone number for server-side outgoing 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.
Format
String
Default Value
N/A
Range
N/A
Example
sip intercom prefix code: *96
Parameter –
sip intercom line
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Outgoing Intercom Settings
aastra.cfg, <mac>.cfg
Line
(in Web UI)
Description
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.
Format
Integer
Default Value
1
Range
Line 1 through 9
Example
sip intercom line: 1
A-122
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Incoming Intercom Settings
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Incoming Intercom Settings
aastra.cfg, <mac>.cfg
Auto-Answer
(in Web UI)
Description
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.
Format
Boolean
Default Value
1 (true)
Range
0 (false - do not allow auto-answer)
1 (true - allow auto-answer)
Example
sip allow auto answer: 0
Parameter –
sip intercom mute mic
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Incoming Intercom Settings
aastra.cfg, <mac>.cfg
Microphone Mute
(in Web UI)
Description
Enables or disables the microphone on the IP phone for Intercom calls
made by the originating caller.
Format
Integer
Default Value
1 (true)
Range
0 (false - microphone is not muted)
1 (true - microphone is muted)
Example
sip intercom mute mic: 1
41-001160-00, Release 2.1, Rev 04
A-123
Appendix A
Parameter –
sip allow auto answer
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
sip play warning tone
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Incoming Intercom Settings
aastra.cfg, <mac>.cfg
Play Warning Tone
(in Web UI)
Description
Enables or disables a warning tone to play when the phone receives an
incoming intercom call on an active line.
Format
Integer
Default Value
1 (true)
Range
0 (false - warning tone will not play)
1 (true - warning tone will play)
Example
sip play warning tone: 0
Parameter –
sip intercom allow barge in
Aastra Web UI:
Configuration Files
Basic Settings->Preferences->
Incoming Intercom Settings
aastra.cfg, <mac>.cfg
Allow Barge In
(in Web UI)
Description
Enable or disables how the phone handles incoming intercom calls while
the phone is on an active call.
When you enable this parameter (1 = enable), which is the default value,
an incoming intercom call takes precedence over any active call, by
placing the active call on hold and automatically answering the intercom
call.
When you disable this parameter (0 = disable), and there is an active call,
the phone treats an incoming intercom call like a normal call and plays the
call warning tone.
Note: After enabling or disabling this feature, it takes affect on the phone
immediately.
Format
Boolean
Default Value
1 (true)
Range
0 (false)
1 (true)
Example
sip intercom allow barge in: 0
A-124
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Audio Transmit and Receive Gain Adjustment Settings
Configuration Files
Description
This is the increased (+db) or decreased (-db) amount of signal
transmitted from the headset microphone to t he far-end party. The amount
of Tx gain in the IP phone firmware has been reduced to avoid side-tone
and echo on the local and far-end equipment. This parameter allows you
to adjust the Tx gain settings to best suit your comfort level and
deployment environment.
Format
Integer
Default Value
0
Range
-10 db to +10 db
Example
headset tx gain: -5
Parameter –
headset sidetone gain
Configuration Files
Description
This is the is the increased (+db) or decreased (-db) amount of sidetone
signal from the headset microphone to the headset speaker. The amount
of sidetone gain in the IP phone firmware has been reduced to avoid
side-tone and echo on the local and far-end equipment. This parameter
allows you to adjust the sidetone gain settings to best suit your comfort
level and deployment environment.
Format
Integer
Default Value
0
Range
-10 db to +10 db
Example
headset sidetone gain: -1
41-001160-00, Release 2.1, Rev 04
aastra.cfg, <mac>.cfg
aastra.cfg, <mac>.cfg
A-125
Appendix A
Parameter –
headset tx gain
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
handset tx gain
Configuration Files
Description
This is the increased (+db) or decreased (-db) amount of signal
transmitted from the handset microphone to the far-end party. The amount
of Tx gain in the IP phone firmware has been reduced to avoid side-tone
and echo on the local and far-end equipment. This parameter allows you
to adjust the Tx gain settings to best suit your comfort level and
deployment environment.
Format
Integer
Default Value
0
Range
-10 db to +10 db
Example
handset tx gain: -5
Parameter –
handset sidetone gain
Configuration Files
Description
This is the increased (+db) or decreased (-db) amount of sidetone signal
from the handset microphone to the handset speaker. The amount of
sidetone gain in the IP phone firmware has been reduced to avoid
side-tone and echo on the local and far-end equipment. This parameter
allows you to adjust the sidetone gain settings to best suit your comfort
level and deployment environment.
Format
Integer
Default Value
0
Range
-10 db to +10 db
Example
handset sidetone gain: -1
A-126
aastra.cfg, <mac>.cfg
aastra.cfg, <mac>.cfg
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Configuration Files
aastra.cfg, <mac>.cfg
Description
This is the increased (+db) or decreased (-db) amount of signal
transmitted from the base microphone to the far-end party. The amount of
Tx gain in the IP phone firmware has been reduced to avoid side-tone and
echo on the local and far-end equipment. This parameter allows you to
adjust the Tx gain settings to best suit your comfort level and deployment
environment.
Note: The example below increases the speakerphone mic transmit gain
by 10 db.
Format
Integer
Default Value
0
Range
-10 db to +10 db
Example
handsfree tx gain: 10
Parameter –
audio mode
IP Phone UI
Configuration Files
Description
Allows you to configure how the "handsfree" key on the IP phone operates.
Format
Integer
Default Value
0
Range
0
Speaker - Calls can be made or received using the handset or
handsfree speakerphone and can be switched between the two
modes by pressing the d /fkey. When on speaker, you can return to
using the handset by placing the handset on the cradle and
picking it up again.
1
Headset - Calls can be made or received using the headset. Calls
can be switched between the headset and handset by pressing the d
/fkey.
2
Speaker/headset - Incoming calls are sent to the speakerphone . By
pressing the d /f key, you can switch between the handsfree
speakerphone, the headset, and the handset.
3
Headset/speaker - Incoming calls are sent to the headset. By
pressing the d /fkey, you can switch between the headset, the
handsfree speakerphone, and the handset.
Example
Options->Set Audio
aastra.cfg, <mac>.cfg
audio mode: 2
41-001160-00, Release 2.1, Rev 04
A-127
Appendix A
Parameter –
handsfree tx gain
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Directed Call Pickup (BLF or XML Call Interception) Settings
Parameter –
directed call pickup
Aastra Web UI
Configuration Files
Basic Settings->Preferences
->Directed Call Pickup Settings
aastra.cfg, <mac>.cfg
Directed Call Pickup
(in Web UI)
Description
Enables or disables the use of "directed call pickup" feature.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
directed call pickup: 1
A-128
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Basic Settings->Preferences->
Directed Call Pickup Settings
aastra.cfg, <mac>.cfg
Directed Call Pickup by Prefix
(in Web UI)
Description
Allows you to enter a specific prefix string (depending on what is
available on your server), that the phone automatically dials when
dialing the Directed Call Pickup number.
For example, for Broadsoft servers, you can enter a value of *98 for the
“directed call pickup prefix”. When the phone performs the Directed
Call Pickup after pressing a BLF or BLF/List softkey, the phone
prepends the *98 value to the designated extension of the BLF or BLF/
List softkey when dialing out.
Notes:
1. The default method for the phone to use is Directed Call Pickup over
BLF if the server provides applicable information. If the Directed Call
Pickup over BLF information is missing in the messages to the server,
the Directed Call Pickup by Prefix method is used if a value for the prefix
code exists in the configuration.
2. You can define only one prefix at a time for the entire BLF/List.
3. The phone that picks up displays the prefix code + the extension
number (for example, *981234 where prefix key = *98, extension =
1234).
4. Symbol characters are allowed (for example “*”).
Format
Integer
Default Value
Not Applicable
Range
Not Applicable
Example
directed call pickup prefix: *98
41-001160-00, Release 2.1, Rev 04
A-129
Appendix A
Parameter –
directed call pickup prefix
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
play a ring splash
Aastra Web UI
Configuration Files
Basic Settings->Preferences
->Directed Call Pickup Settings
aastra.cfg, <mac>.cfg
Play a Ring Splash
(in Web UI)
Description
Enables or disables the playing of a short "call waiting tone" when there is
an incoming call on the BLF monitored extension. If the host tone is idle,
the tone plays a "ring splash".
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
play a ring splash: 1
A-130
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
ACD Auto-Available Timer Settings
Aastra Web UI
Configuration Files
Appendix A
Parameter –
acd auto available
Basic Settings->Preferences
->Auto Call Distribution Settings
aastra.cfg, <mac>.cfg
Auto Available
(in Web UI)
Description
Enables or disables the use of the ACD Auto-Available Timer.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
acd auto available: 1
Parameter –
acd auto available timer
Aastra Web UI
Configuration Files
Basic Settings->Preferences
->Auto Call Distribution Settings
aastra.cfg, <mac>.cfg
Auto Available Timer
(in Web UI)
Description
Specifies the length of time, in seconds, before the IP phone status
switches back to “available.”
Format
Integer
Default Value
60 (seconds)
Range
0 to 120 (seconds)
Example
acd auto available timer: 60
41-001160-00, Release 2.1, Rev 04
A-131
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Appendix A
Park and Pickup Global Settings (57i/57i CT only)
Parameter –
sprecode
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Park Call
(in Web UI)
Description
Specifies the code to enter before entering the extension for where you
want to park an incoming call. The applicable value is dependant on the
type of server in the network:
Server
Asterisk
Sylantro
BroadWorks
ININ PBX
Park Values*
70
*98
*68
callpark
*Leave "value" fields blank to disable the park and pickup feature.
Format
Alphanumeric characters
Default Value
<Blank>
Range
See applicable values in the table above.
Example
sprecode: *68
Parameter –
pickupsprecode
Aastra Web UI
Configuration Files
Basic Settings->Preferences
aastra.cfg, <mac>.cfg
Pick Up Parked Call
(in Web UI)
Description
Specifies the code to enter before entering the extension for where you
want to pickup a parked call. The applicable value is dependant on the
type of server in the network:
Server
Pickup Values*
Asterisk
Sylantro
BroadWorks
ININ PBX
70
*99
*88
pickup
*Leave "value" fields blank to disable the park and pickup feature.
Format
Alphanumeric characters
Default Value
<Blank>
Range
See applicable values in the table above.
Example
pickupsprecode: *88
A-132
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Mapping Key Parameters
Parameter –
redial disabled
Configuration Files
Description
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".
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
redial disabled: 1
Parameter –
conference disabled
Configuration Files
Description
Enables or disables the Conf 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.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
conference disabled: 1
41-001160-00, Release 2.1, Rev 04
aastra.cfg, <mac>.cfg
aastra.cfg, <mac>.cfg
A-133
Appendix A
This section provides the hard key settings you can use to enable and disable the
Redial, Conf, and Xfer keys on the IP phone.
Appendix A
IP Phone Administrator Guide
Operational, Basic, and Advanced Parameters
Parameter –
call transfer disabled
Configuration Files
aastra.cfg, <mac>.cfg
Description
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.
Format
Boolean
Default Value
0 (false)
Range
0 (false), 1 (true)
Example
call transfer disabled: 1
Parameter –
map redial key to
Aastra Web UI
Configuration Files
Basic Settings->Preferences->Key Mapping
aastra.cfg, <mac>.cfg
Map Redial Key To
(in Web UI)
Description
Sets the Redial key as a speeddial key if a value is entered for this
parameter. If you leave this parameter blank, the Redial key returns to its
original functionality.
Note: If you configure the Redial key for speeddialing on the 57i CT Base
Station, the Redial key on the 57i CT handset retains its original
functionality. The Redial key on the handset is not configured for
speeddial.
Format
Integer
Default Value
N/A
Range
N/A
Example
map redial key to: 5551234
A-134
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Operational, Basic, and Advanced Parameters
Aastra Web UI
Configuration Files
Basic Settings->Preferences->Key Mapping
aastra.cfg, <mac>.cfg
Map Conf Key To
(in Web UI)
Description
Sets the Conf key as a speeddial key if a value is entered for this
parameter. If you leave this parameter blank, the Conf key returns to its
original functionality.
Note: If you configure the Conf key for speeddialing on the 57i CT Base
Station, the Conf key on the 57i CT handset retains its original
functionality. The Conf key on the handset is not configured for speeddial.
Format
Integer
Default Value
N/A
Range
N/A
Example
map conf key to: 5551267
41-001160-00, Release 2.1, Rev 04
A-135
Appendix A
Parameter –
map conf key to
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
Softkey/Programmable Key/Feature Key/
Expansion Module Key Parameters
This section provides the softkey, programmable key, feature key, and expansion
module key parameters you can configure on the IP phones. The following table
provides the number of keys you can configure for each model phone and
expansion module, and the number of lines available for each type of phone.
IP
Phone
Model
Softkeys
Expansion Module
Keys
Programmable
Keys
Lines
Available
Handset
Keys
Available
53i
-
36 to 108*
(Model 536M)
6
(Up to 4
functions)
9
-
55i
6 Bottom Keys
(Up to 20
functions)
36 to 108*
(Model 536M)
6 Top Keys
(Up to 6
functions)
9
-
12 Top and
Bottom Softkeys
36 to 108*
(Model 536M)
-
9
-
(Up to 10
functions on top
keys; Up to 20
functions on
bottom keys)
60 to 180**
(Model 560M)
12 Top and
Bottom Softkeys
36 to 108* on Base
Station
-
9
15
(Up to 10
functions on top
keys; Up to 20
functions on
bottom keys)
60 to 180** on Base
Station
(Model 560M)
57i
57i CT
60 to 180**
(Model 560M)
*The 536M expansion module consists of 36 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 108 softkeys. Valid for 53i, 55i, 57i, and 57i CT phones.
**The 560M expansion module consists of 60 softkeys. You can have up to 3 expansion modules on an IP
phone totaling 180 softkeys. Valid for 55i, 57i, and 57i CT phones.
Note: When entering definitions for softkeys, the “#” sign must be
enclosed in quotes.
A-136
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Softkey Settings for 55i, 57i, 57i CT
Parameter –
softkeyN type
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Type
(in Web UI)
Description
The type of softkey to configure. Valid types are:
• none - Indicates softkey and/or programmable key is disabled.
• line - Indicates softkey and/or programmable key is configured for
line use.
• speeddial - Indicates softkey and/or programmable key is configured
for speeddial use. Speeddial is applicable to the 536M and 560M
also. You can configure a softkey to speeddial a specific number by
pressing that softkey. Optionally, you can also configure a speeddial
key to dial prefix numbers. With this option, the prefix numbers
automatically dial when you press the softkey, and the phone waits
for you to enter the remaining numbers to dial out.
Note: When there is an active call, the speeddial keys send DTMF
digits through the active voice path. To dial out, you have to first put
the active call on hold and then press the speeddial key.
• dnd - Indicates softkey and/or programmable key is configured for do
not disturb on the phone. This option is "Do Not Disturb" in the
Aastra Web UI).
• blf - Indicates softkey and/or programmable key is configured for
Busy Lamp Field (BLF) use. User can dial out on a BLF configured
key. Maximum of 50 BLFs are applicable to the 536M and 560M also.
• list - Indicates softkey and/or programmable key is configured for
BLF list use. (This option is BLF/List in the Aastra Web UI). User can
dial out on a BLF List configured key.
• acd - (for Sylantro Servers only) Indicates the programmable key is
configured for auto call distribution (called “Auto call distribution” in
the Aastra Web UI). The ACD feature allows the Sylantro server to
distribute calls from a queue to registered IP phone users (agents).
• dcp - (for Sylantro Servers only) Indicates the programmable key is
configured for either directed call pickup or group call pickup (called
“Directed Call Pickup” in the Aastra Web UI). The Directed Call
Pickup/Group Call Pickup feature allows you to intercept or pickup a
call on a monitored extension or a group of monitored extensions.
• xml - Indicates the softkey and/or programmable key is configured to
accept an XML application for accessing customized XML services.
You can also specify an XML softkey URL for this option.
•
41-001160-00, Release 2.1, Rev 04
A-137
Appendix A
The value of "N" for the following parameters is dependent on the number of
softkeys available on the55i, 57i, and 57i CT models. See the table above for
applicable values.
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
•
•
•
•
•
•
•
•
•
•
•
flash - Indicates the softkey and/or programmable key is set to
generate a flash event when it is pressed on the 57i and 57i CT, or a
feature key is pressed on the 57i CT handset. The IP phone
generates flash events only when a call is connected and there is an
active RTP stream (for example, when the call is not on hold).
sprecode - Indicates the softkey and/or programmable key is
configured to automatically activate specific services offered by the
server. For example, if the sprecode value of *82 is configured, then
by pressing the softkey, *82 automatically activates a service
provided by the server.
park - Indicates the softkey and/or programmable key is configured to
park incoming calls when pressed.
pickup - Indicates the softkey and/or programmable key is configured
to pick up parked calls when pressed.
lcr - Indicates the softkey and/or programmable key is configured for
“last call return” when pressed.
directory - Indicates the softkey and/or programmable key is set for
accessing the Directory List.
callers list - Indicates the softkey and/or programmable key is set for
accessing the Callers List.
icom - Indicates the softkey and/or programmable key is set to be
used as the Intercom key.
services - Indicates the softkey and/or programmable key is set to be
used as the Services key.
phonelock - Indicates the softkey and/or programmable key is set to
be used to lock/unlock the phone.
empty - Indicates the softkey and/or programmable key is configured
to force a blank entry on the IP phone display for a specific softkey.
The softkeys 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.
Format
Text
Default Value
none
A-138
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
none
line
speeddial
dnd ("do not disturb" in the Aastra Web UI)
blf
list ("BLF\List" in the Aastra Web UI)
acd (“Auto call distribution” in the Aastra Web UI)
dcp (“Directed Call Pickup” in the Aastra Web UI)
xml
flash
sprecode
park
pickup
lcr
callers list
directory
icom
services
phonelock
empty
Example
softkey1 type: line
softkey2 type: speeddial
softkey3 type: lcr
softkey4 type: xml
Appendix A
Range
Directed Call Pickup on Extension 2200
softkey2 type: dcp
softkey2 label: dcp2200
softkey2 value: 2200
softkey2 states: incoming outgoing idle connected
Group Call Pickup on group_A
softkey3 type: dcp
softkey3 label: gcp_A
softkey3 value: groupcallpickup
softkey3 states: incoming outgoing idle connected
41-001160-00, Release 2.1, Rev 04
A-139
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
softkeyN label
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Label
(in Web UI)
Description
The text label that displays on the IP phone for the softkey.
The “softkeyN label” parameter can be set for the following softkey types
only:
• speeddial
• BLF
• acd
• dcp
• XML
• Flash
• sprecode
• Park
• Pickup
• Directory
• Callers List
• Icom
• Services
Notes:
1. For the 57i and 57i CT phones, an icon appears beside the soft key
label that indicates the status of the line.
2. If the softkeyN type parameter is set to "flash", and no label value is
entered for the softkeyN label parameter, the label of "Flash" is used.
Format
Text
Default Value
Not Applicable
Range
For line, blf types - Up to 9 characters.
For speeddial type - Up to 11 characters.
Example
softkey1 label: “Line 9”
softkey2 label: “info”
softkey3 label: flash
softkey4 label: “johnsmith”
A-140
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Value
(In WEb UI)
Description
This is the value you assign to the softkey.
The “softkeyN value” parameter can be set for the following softkey types
only:
• speeddial (you can enter a speeddial number for this field;
optionally, you can also enter a prefix for the
speeddial value to allow the phone to dial the prefix
after you press the speeddial softkey; you then
enter the rest of the number from the keypad on the
phone.)
• BLF
• sprecode
• Park
• Pickup
• dcp
• XML
Notes:
1. For speeddial - Value is the phone number, extension, or prefix
number to enter for the softkey.
2. For blf - Value is the extension you want to monitor.
3. For sprecode - Value is dependent on services offered by server.
4. For Park, Pickup - For valid values, see Chapter 5, the section,
“Park/Pickup Call Server Configuration Values” on page 5-157. For
Park/Pickup examples, see Chapter 5, the section, “Model 57i/57i CT
Examples” on page 5-155.
5. For xml - You can specify a URI to use for this XML softkey. The
variables you can use with the XML softkey URI are:
•
$$SIPUSERNAME$$
•
$$SIPAUTHNAME$$
•
$$PROXYURL$$
•
$$REMOTENUMBER$$
•
$$DISPLAYNAME$$
•
$$INCOMINGNAME$$
Format
Integer
Default Value
Not Applicable
Range
N/A
Example
softkey1 value: 9
softkey2 value: 411
softkey4 value: http://10.50.10.140 script.pl?name=$$SIPUSERNAME$$
softkey5 value: 123456+ (example of a speeddial prefix)
41-001160-00, Release 2.1, Rev 04
A-141
Appendix A
Parameter –
softkeyN value
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
softkeyN line
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Line
(in Web UI)
Description
This is the line associated with the softkey you are configuring. The
number of applicable lines available is dependent on the specific IP
phone model.
The “softkeyN line” parameter can be set for the following softkey types
only:
• speeddial
• BLF
• BLF/List
• acd
• dcp
• Park
• Pickup
• lcr
Format
Integer
Default Value
1
Range
1 through 9
Example
softkey1 line: 1
softkey2 line: 5
A-142
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Idle, Connected, Incoming,
Outgoing, Busy
(in Web UI)
Description
Displays the status of the phone when a softkey is pressed. You can
enter multiple values (idle, connected, incoming, outgoing, busy) for
the "softkeyN state" parameter.
You must associate the softkeyN state parameter with a specific softkey.
In the following example, the softkeyN 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.
Format
Text
Default Value
For softkey type - None:
All states disabled
For softkey types - Line, DND, speeddial, BLF, BLF List, dcp, XML,
lcr, Directory, Callers List, Icom, Services, empty:
idle, connected, incoming, outgoing
For softkey type - Flash:
All states disabled
For softkey type - Sprecode, Park:
connected
For softkey type - Pickup:
idle, outgoing
For softkey type - acd:
idle
41-001160-00, Release 2.1, Rev 04
A-143
Appendix A
Parameter –
softkeyN states
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Range
Valid values are:
idle
The phone is not being used.
connected
The line currently being displayed is
in an active call (or the call is on hold)
incoming
The phone is ringing.
outgoing
The user is dialing a number, or the
far-end is ringing.
busy
The current line is busy because the line is in use or
the line is set as “Do Not Disturb”
Note: For softkey type, Pickup, values can be: just idle, just outgoing, or
idle outgoing.
Example
softkey1 states: idle incoming outgoing
softkey2 states: connected
A-144
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Programmable Key Settings for 53i and 55i
The value of "N" for the following parameters is dependent on the number of
programmable keys available on the 53i models. See the table on page 136 for
the applicable values.
Parameter –
prgkeyN type
Aastra Web UI
Operation->Programmable Keys
Configuration Files aastra.cfg, <mac>.cfg
Type
(in Web UI)
Description
41-001160-00, Release 2.1, Rev 04
The type of programmable key to configure. Valid types are:
• none - Indicates no setting for programmable key.
• line - Indicates programmable key is configured for line use.
• speeddial - Indicates programmable key is configured for speeddial
use. You can configure a programmable key to speeddial a specific
number by pressing that key. Optionally, you can also configure a
speeddial key to dial prefix numbers. With this option, the prefix
numbers automatically dial when you press the programmable key,
and the phone waits for you to enter the remaining numbers to dial.
Note: When there is an active call, the speeddial keys send DTMF
digits through the active voice path. To dial out, you have to first put
the active call on hold and then press the speeddial key.
• dnd - Indicates programmable key is configured for do not disturb
on the phone. This option is "Do Not Disturb" in the Aastra Web
UI).
• blf - Indicates programmable key is configured for Busy Lamp Field
(BLF) use. User can dial out on a BLF configured key.
• list - Indicates programmable key is configured for BLF list use.
User can dial out on a BLF List configured key.
• acd - (for Sylantro Servers only) Indicates the programmable key is
configured for auto call distribution (called “Auto Call Distribution”
in the Aastra Web UI). The ACD feature allows the Sylantro server
to distribute calls from a queue to registered IP phone users
(agents).
• dcp - (for Sylantro Servers only) Indicates the programmable key is
configured for either directed call pickup or group call pickup (called
“Directed Call Pickup” in the Aastra Web UI). The Directed Call
Pickup/Group Call Pickup feature allows you to intercept or pickup a
call on a monitored extension or a group of monitored extensions.
• xml - Indicates programmable key is configured to accept an XML
application for accessing customized XML services. You can also
specify an XML softkey URL for this option.
• flash - Indicates programmable key is set to generate a flash event
when it is pressed on the 53i. The IP phone generates flash events
only when a call is connected and there is an active RTP stream (for
example, when the call is not on hold).
A-145
Appendix A
•
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
•
•
•
•
•
•
•
•
•
•
sprecode - Indicates programmable key is configured to
automatically activate specific services offered by the server. For
example, if the sprecode value of *82 is configured, then by
pressing the softkey, *82 automatically activates a service provided
by the server.
park - Indicates programmable key is configured to park incoming
calls when pressed.
pickup - Indicates programmable key is configured to pick up
parked calls when pressed.
lcr - Indicates programmable key is configured for “last call return”
when pressed.
directory - Indicates programmable key is configured to access the
Directory List.
callers list - Indicates programmable key is configured to access
the Callers List.
conference - Indicates programmable key is configured as a
conference key. Enter as “conf” in configuration files.
transfer - Indicates programmable key is configured as a Transfer
key for transferring calls. Enter as “xfer” in configuration files.
phonelock - Indicates the programmable key is set to be used to
lock/unlock the phone.
empty - Indicates programmable key is configured to force a blank
entry on the IP phone display for a specific programmable key.
Note: Keys 1 and 2 on the 53i are hardcoded as the Save and Delete
keys, respectively, and are not configurable.
Format
Text
Default Value
Not Applicable
A-146
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
none
line
speeddial
dnd ("do not disturb" in the Aastra Web UI)
blf
list (“BLF/List” in the Aastra Web UI)
acd (“Auto call distribution” in the Aastra Web UI)
dcp (“Directed Call Pickup” in the Aastra Web UI)
xml
flash
sprecode
park
pickup
lcr
directory
callers list
conf
xfer
phonelock
empty
Example
prgkey3 type: speeddial
41-001160-00, Release 2.1, Rev 04
Appendix A
Range
A-147
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
prgkeyN value
Aastra Web UI
Operation->Programmable Keys
Configuration Files aastra.cfg, <mac>.cfg
Value
(in Web UI)
Description
This is the value you assign to the programmable key.
The “prgkeyN value” parameter can be set for the following softkey types
only:
• speeddial (you can enter a speeddial number for this field;
optionally, you can also enter a prefix for the
speeddial value to allow the phone to dial the prefix
after you press the speeddial programmable key;
you then enter the rest of the number from the
keypad on the phone.)
• line
• BLF
• sprecode
• dcp
• XML
• Park
• Pickup
Notes:
1.
For speeddial - Value is the phone number, extension, or prefix
number to enter for the programmable key.
2.
For line - Value is optional; for example L4.
3.
For blf - Value is the extension you want to monitor.
4.
For sprecode - Value is dependent on services offered by server.
5.
For xml - Value is IP address of the XML application.
6.
For Park, Pickup - For valid values, see Chapter 5, the section,
“Park/Pickup Call Server Configuration Values” on page 5-157. For
Park/Pickup examples, see Chapter 5, the section “Model 53i
Examples” on page 5-156.
Format
Integer
Default Value
N/A
Range
N/A
Example
prgkey3 value: 411
prgkey4 value: 123456+ (example of a speeddial prefix)
A-148
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Operation->Programmable Keys
Configuration Files aastra.cfg, <mac>.cfg
Line
(in Web UI)
Description
This is the line associated with the programmable key you are
configuring.
The “prgkeyN line” parameter can be set for the following softkey types
only:
• speeddial
• BLF
• BLF/List
• acd
• dcp
• Park
• Pickup
• lcr
Format
Integer
Default Value
1
Range
1 through 9
Example
prgkey3 line: 1
prgkey4 line: 5
41-001160-00, Release 2.1, Rev 04
A-149
Appendix A
Parameter–
prgkeyN line
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
Top Softkey Settings for 57i and 57i CT
Parameter –
topsoftkeyN type
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Top Softkeys->Type
(in Web UI)
Description
A-150
The type of softkey to configure. Valid types are:
• none - Indicates softkey is disabled.
• line - Indicates softkey is configured for line use.
• speeddial - Indicates softkey is configured for speeddial use.
You can configure a softkey to speeddial a specific number by
pressing that softkey. Optionally, you can also configure a speeddial
key to dial prefix numbers. With this option, the prefix numbers
automatically dial when you press the softkey, and the phone waits
for you to enter the remaining numbers to dial out.
Note: When there is an active call, the speeddial keys send DTMF
digits through the active voice path. To dial out, you have to first put
the active call on hold and then press the speeddial key.
• dnd - Indicates softkey is configured for do not disturb on the phone.
This option is "Do Not Disturb" in the Aastra Web UI).
• blf - Indicates softkey is configured for Busy Lamp Field (BLF) use.
User can dial out on a BLF configured key.
• list - Indicates softkey is configured for BLF list use. (This option is
BLF/List in the Aastra Web UI). User can dial out on a BLF List
configured key.
• acd - (for Sylantro Servers only) Indicates the programmable key is
configured for auto call distribution (called “Auto call distribution” in
the Aastra Web UI). The ACD feature allows the Sylantro server to
distribute calls from a queue to registered IP phone users (agents).
• dcp - (for Sylantro Servers only) Indicates the programmable key is
configured for either directed call pickup or group call pickup (called
“Directed Call Pickup” in the Aastra Web UI). The Directed Call
Pickup/Group Call Pickup feature allows you to intercept or pickup a
call on a monitored extension or a group of monitored extensions.
• xml - Indicates the softkey is configured to accept an XML application
for accessing customized XML services. You can also specify an XML
softkey URL for this option.
• flash - Indicates the softkey is set to generate a flash event when it is
pressed on the 57i and 57i CT, or a feature key is pressed on the 57i
CT handset. The IP phone generates flash events only when a call is
connected and there is an active RTP stream (for example, when the
call is not on hold).
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
•
•
•
•
•
•
•
•
•
Format
Text
Default Value
none
Range
none
line
speeddial
dnd
blf
list ("BLF\List" in the Aastra Web UI)
acd (“Auto call distribution” in the Aastra Web UI)
dcp (“Directed Call Pickup” in the Aastra Web UI)
xml
flash
sprecode
park
pickup
lcr
callers list
directory
icom
services
phonelock
empty
41-001160-00, Release 2.1, Rev 04
A-151
Appendix A
•
sprecode - Indicates the softkey is configured to automatically
activate specific services offered by the server. For example, if the
sprecode value of *82 is configured, then by pressing the softkey, *82
automatically activates a service provided by the server.
park - Indicates the softkey is configured to park incoming calls when
pressed.
pickup - Indicates the softkey is configured to pick up parked calls
when pressed.
lcr - Indicates the softkey is configured for “last call return” when
pressed.
callers list - Indicates the softkey is set for accessing the Callers List.
directory - Indicates the softkey is set for accessing the Directory
List.
icom - Indicates the softkey is set to be used as the Intercom key.
services - Indicates the softkey is set to be used as the Services key.
phonelock - Indicates the softkey is set to be used to lock/unlock the
phone.
empty - Indicates the softkey is configured to force 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.
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
Example
A-152
topsoftkey1 type: line
topsoftkey2 type: speeddial
topsoftkey3 type: lcr
topsoftkey4 type: xml
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Top Softkeys->Label
(in Web UI)
Description
The text label that displays on the IP phone for the softkey.
The “topsoftkeyN label” parameter can be set for the following softkey
types only:
• speeddial
• BLF
• acd
• dcp
• XML
• Flash
• sprecode
• Park
• Pickup
• Directory
• Callers List
• Icom
• Services
Notes:
1. For the 57i and 57i CT phones, an icon appears beside the soft key
label that indicates the status of the line.
2. If the topsoftkeyN type parameter is set to "flash", and no label value
is entered for the topsoftkeyN label parameter, the label of "Flash" is
used.
Format
Text
Default Value
Not Applicable
Range
For line, blf types - Up to 9 characters.
For speeddial type - Up to 11 characters.
Example
topsoftkey1 label: “Line 9”
topsoftkey2 label: “info”
topsoftkey4 label: “johnsmith”
41-001160-00, Release 2.1, Rev 04
A-153
Appendix A
Parameter –
topsoftkeyN label
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
topsoftkeyN value
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Top Softkeys->Value
(In WEb UI)
Description
This is the value you assign to the softkey.
The “topsoftkeyN value” parameter can be set for the following softkey
types only:
• speeddial (you can enter a speeddial number for this field;
optionally, you can also enter a prefix for the
speeddial value to allow the phone to dial the prefix
after you press the speeddial programmable key;
you then enter the rest of the number from the
keypad on the phone.)
• BLF
• sprecode
• Park
• Pickup
• dcp
• XML
Notes:
1. For speeddial - Value is the phone number, extension, or prefix
number to enter for the softkey.
2. For blf - Value is the extension you want to monitor.
3. For sprecode - Value is dependent on services offered by server.
4. For Park, Pickup - For valid values, see Chapter 5, the section,
“Park/Pickup Call Server Configuration Values” on page 5-157. For
Park/Pickup examples, see Chapter 5, the section, “Model 57i/57i CT
Examples” on page 5-155.
5. For xml - You can specify a URI to use for this XML softkey. The
variables you can use with the XML softkey URI are:
•
$$SIPUSERNAME$$
•
$$SIPAUTHNAME$$
•
$$PROXYURL$$
•
$$REMOTENUMBER$$
•
$$DISPLAYNAME$$
•
$$INCOMINGNAME$$
Format
Integer
Default Value
Not Applicable
Range
N/A
Example
topsoftkey1 value: 9
topsoftkey2 value: 411
topsoftkey4 value: http://10.50.10.140 script.pl?name=$$SIPUSERNAME$$
topsoftkey5 value: 12345+ (example of a speeddial prefix)
A-154
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Configuration Files
Operation->Softkeys and XML
aastra.cfg, <mac>.cfg
Top Softkeys->Line
(in Web UI)
Description
This is the line associated with the softkey you are configuring. The
number of applicable lines available is dependent on the specific IP
phone model.
The “topsoftkeyN line” parameter can be set for the following softkey
types only:
• speeddial
• BLF
• BLF/List
• acd
• dcp
• Park
• Pickup
• lcr
Format
Integer
Default Value
1
Range
1 through 9
Example
topsoftkey1 line: 1
topsoftkey2 line: 5
41-001160-00, Release 2.1, Rev 04
A-155
Appendix A
Parameter –
topsoftkeyN line
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
Handset Feature Key Settings for the 57i CT
Parameter –
featurekeyN type
Aastra Web UI
Configuration Files
Operation->Handset Keys
aastra.cfg, <mac>.cfg
Type
(in Web UI)
Description
The type of feature key to configure. Valid types are:
• none - Indicates feature key is disabled.
• line - Indicates the feature key is configured for line use.
• transfer- Indicates feature key is configured for transferring a call.
• conference - Indicates feature key is configured for conference
calling.
• public - Indicates feature key is configured to toggle from public to
private mode. A public and private softkey can be used when at a line
item in the Directory List. The Private key toggles a number in the
Directory List to private. The Public key allows a number in the
Directory List to be sent to the handsets. A 57i CT accepts a
maximum of 50 entries with the public attribute.
• icom - Indicates the feature key is set to be used to make an
intercom call.
• directory - Indicates the feature key is set for accessing the Directory
List.
• callers list - Indicates the feature key is set for accessing the Callers
List.
• park- Indicates the feature key is configured to park incoming calls
when pressed.
• pickup- Indicates the feature key is configured to pick up parked calls
when pressed.
• flash - Indicates the feature key is set to generate a flash event when
it is pressed on the 57i CT handset. The IP phone generates flash
events only when a call is connected and there is an active RTP
stream (for example, when the call is not on hold).
Format
Text
Default Value
None
A-156
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
none
line
transfer
conference
public
icom
directory
callers list
park
pickup
flash
Example
featurekey1 type: line
featurekey2 type: public
featurekey3 type: park
featurekey4 type: pickup
Parameter –
featurekeyN label
Aastra Web UI
Configuration Files
Appendix A
Range
Operation->Handset Keys
aastra.cfg, <mac>.cfg
Label
(in Web UI)
Description
The text label that displays on the IP phone for the feature key.
Notes:
1. For the 57i CT phones, an icon appears beside the feature key label
that indicates the status of the line.
2. If a feature key is configured but no label is set, the IP phone sets the
label to the English, French, or Spanish translation of the chosen
action. The language used is based on the current language of the
cordless handset.
Format
Text
Default Value
Not Applicable
Range
Not Applicable
Example
featurekey1 label: Line 9
featurekey2 label: Public
featurekey4 label: John Smith
41-001160-00, Release 2.1, Rev 04
A-157
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Appendix A
Expansion Module Key Settings for 536M (for all model phones)
and 560M (for 55i, 57i, 57i CT phones only)
Parameter –
expmodX keyN type
Aastra Web UI
Configuration Files
Operation->Expansion Module N
aastra.cfg, <mac>.cfg
Type
(in Web UI)
Description
A-158
The type of softkey to configure. Valid types are:
• none - Indicates softkey is disabled.
• line - Indicates softkey is configured for line use.
• speeddial - Indicates softkey is configured for speeddial use.
You can configure a softkey to speeddial a specific number by
pressing that softkey. Optionally, you can also configure a speeddial
key to dial prefix numbers. With this option, the prefix numbers
automatically dial when you press the softkey, and the phone waits
for you to enter the remaining numbers to dial out.
Note: When there is an active call, the speeddial keys send DTMF
digits through the active voice path. To dial out, you have to first put
the active call on hold and then press the speeddial key.
• dnd - Indicates softkey is configured for do not disturb on the phone.
This option is "Do Not Disturb" in the Aastra Web UI).
• blf - Indicates softkey is configured for Busy Lamp Field (BLF) use.
User can dial out on a BLF configured key.
• list - Indicates softkey is configured for BLF list use. (This option is
BLF/List in the Aastra Web UI). User can dial out on a BLF List
configured key.
• acd - (for Sylantro Servers only) Indicates the programmable key is
configured for auto call distribution (called “Auto call distribution” in
the Aastra Web UI). The ACD feature allows the Sylantro server to
distribute calls from a queue to registered IP phone users (agents).
• dcp - (for Sylantro Servers only) Indicates the programmable key is
configured for either directed call pickup or group call pickup (called
“Directed Call Pickup” in the Aastra Web UI). The Directed Call
Pickup/Group Call Pickup feature allows you to intercept or pickup a
call on a monitored extension or a group of monitored extensions.
• xml - Indicates the softkey is configured to accept an XML application
for accessing customized XML services. You can also specify an XML
softkey URL for this option.
• lcr - Indicates the softkey is configured for “last call return” when
pressed.
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Format
•
•
•
•
callers list - Indicates the softkey is set for accessing the Callers List.
directory - Indicates the softkey is set for accessing the Directory
List.
icom - Indicates the softkey is set to be used as the Intercom key.
services - (not available on the 53i) Indicates the softkey is set to be
used as the Services key.
phonelock - Indicates the softkey is set to be used to lock/unlock the
phone.
empty - Indicates the softkey is configured to force 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.
Default Value
none
Range
none
line
speeddial
dnd
blf
list ("BLF\List" in the Aastra Web UI)
acd (“Auto call distribution” in the Aastra Web UI)
dcp (“Directed Call Pickup” in the Aastra Web UI)
xml
lcr
callers list
directory
icom
services (not available on the 53i)
phonelock
empty
Example
expmod1 key1 type: line
expmod1 key2 type: speeddial
expmod1 key3 type: blf
expmod1 key4 type: list
41-001160-00, Release 2.1, Rev 04
A-159
Appendix A
•
•
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
expmodX keyN label
Aastra Web UI
Configuration Files
Operation->Expansion Module N
aastra.cfg, <mac>.cfg
Label
(in Web UI)
Description
The text label that displays on the softkey for the Expansion Module.
The “expmodX keyN label” parameter can be set for the following
softkey types only:
• speeddial
• BLF
• acd
• dcp
• XML
• Directory
• Callers List
• Icom
• Services
Note: For the 57i and 57i CT phones, an icon appears beside the soft key
label that indicates the status of the line.
Format
Text
Default Value
Not Applicable
Range
For line, blf types - Up to 9 characters.
For speeddial type - Up to 11 characters.
Example
expmod1 key 1 label: “Line 9”
expmod2 key 1 label: “info”
expmod3 key 1 label: “johnsmith”
A-160
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Aastra Web UI
Configuration Files
Operation->Expansion Module N
aastra.cfg, <mac>.cfg
Appendix A
Parameter –
expmodX keyN value
Value
(In WEb UI)
Description
The text label that displays on the IP phone for the softkey on the
Expansion Module.
The “expmodX keyN value” parameter can be set for the following
softkey types only:
•
•
•
•
•
•
•
•
speeddial
blf
dcp
XML
directory
callers list
Icom
Services (not available on 53i)
Notes:
1. For the 57i and 57i CT phones, an icon appears beside the soft key
label that indicates the status of the line.
2. For blf - Value is the extension you want to monitor.
Format
Integer
Default Value
Not Applicable
Range
N/A
Example
expmod1 key1 value: 9
expmod1 key2 value: 411
expmod1 key3 value: 123456+ (example of a speeddial prefix)
41-001160-00, Release 2.1, Rev 04
A-161
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter –
expmodX keyN line
Aastra Web UI
Configuration Files
Operation->Expansion Module N
aastra.cfg, <mac>.cfg
Line
(in Web UI)
Description
This is the line associated with the softkey you are configuring on the
Expansion Module. The number of applicable lines available is
dependent on the specific IP phone model.
The “expmodX keyN line” parameter can be set for the following softkey
types only:
• speeddial
• BLF
• BLF/List
• acd
• dcp
• lcr
Format
Integer
Default Value
1
Range
1 through 9
Example
expmod1 key1 line: 1
expmod1 key2 line: 5
A-162
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Locking Softkeys and Programmable Keys
Configuration Files aastra.cfg, <mac>.cfg
Description
Locks the specified softkey on the 55i, 57i, or 57i CT IP phone. Locking
the key prevents a user from changing or configuring the softkey. When a
key is locked, the phone uses the server settings and ignores any
previous local configuration.
Affects the following parameters:
• softkeyN type
• softkeyN label
• softkeyN value
• softkeyN line
• softkeyN states
Format
Boolean
Default Value
0 (disable)
Range
0 (disable)
1 (enable)
Example
softkey1 locked: 1
Parameter–
topsoftkeyN locked
Configuration Files aastra.cfg, <mac>.cfg
Description
Locks the specified top softkey on the 57i or 57i CT IP phone. Locking the
key prevents a user from changing or configuring the softkey. When a key
is locked, the phone uses the server settings and ignores any previous
local configuration.
Affects the following parameters:
• topsoftkeyN type
• topsoftkeyN label
• topsoftkeyN value
• topsoftkeyN line
Format
Boolean
Default Value
0 (disable)
Range
0 (disable)
1 (enable)
Example
topsoftkey1 locked: 1
41-001160-00, Release 2.1, Rev 04
A-163
Appendix A
Parameter–
softkeyN locked
Appendix A
IP Phone Administrator Guide
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Parameter–
prgkeyN locked
Configuration Files aastra.cfg, <mac>.cfg
Description
Locks the specified top softkey on the 53i or 55i IP phone. Locking the key
prevents a user from changing or configuring the programmable key.
When a key is locked, the phone uses the server settings and ignores any
previous local configuration.
Affects the following parameters:
• prgkeyN type
• prgkeyN value
• prgkeyN line
Format
Boolean
Default Value
0 (disable)
Range
0 (disable)
1 (enable)
Example
prgkey1 locked: 1
Parameter–
featurekeyN locked
Configuration Files aastra.cfg, <mac>.cfg
Description
Locks the specified top softkey on the 57i CT IP phone. Locking the key
prevents a user from changing or configuring the feature key. When a key
is locked, the phone uses the server settings and ignores any previous
local configuration.
Affects the following parameters:
• featurekeyN type
• featurekeyN label
Format
Boolean
Default Value
0 (disable)
Range
0 (disable)
1 (enable)
Example
featurekey1 locked: 1
A-164
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Softkey/Programmable Key/Feature Key/Expansion Module Key Parameters
Configuration Files aastra.cfg, <mac>.cfg
Description
Locks the specified top softkey on the 5-Series Expansion Module
attached to the IP phone. Locking the key prevents a user from changing
or configuring the softkey on the expansion module. When a key is
locked, the phone uses the server settings and ignores any previous local
configuration.
Affects the following parameters:
• expmodX keyN type
• expmodX keyN value
• expmodX keyN line
Format
Boolean
Default Value
0 (disable)
Range
0 (disable)
1 (enable)
Example
expmod1 key4: 1
41-001160-00, Release 2.1, Rev 04
A-165
Appendix A
Parameter–
expmodX key N locked
IP Phone Administrator Guide
Customizing 560M Expansion Module Column Display
Appendix A
Customizing 560M Expansion Module Column
Display
Expansion Module 1
Parameter–
expanmod1page1left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, first page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page1left: Personnel Ext
Parameter–
expanmod1page1right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, first page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page1right: Operations Ext
Parameter–
expanmod1page2left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, second page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page2left: Marketing Ext
A-166
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Customizing 560M Expansion Module Column Display
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, second page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page2right: Logistics Ext
Parameter–
expanmod1page3left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, third page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page3left: Engineering Ext
Parameter–
expanmod1page3right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the first 560M expansion
module, third page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod1page3right: Shipping Ext
41-001160-00, Release 2.1, Rev 04
A-167
Appendix A
Parameter–
expanmod1page2right
IP Phone Administrator Guide
Customizing 560M Expansion Module Column Display
Appendix A
Expansion Module 2
Parameter–
expanmod2page1left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, first page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page1left: Personnel Ext
Parameter–
expanmod2page1right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, first page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page1right: Operations Ext
Parameter–
expanmod2page2left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, second page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page2left: Marketing Ext
A-168
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Customizing 560M Expansion Module Column Display
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, second page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page2right: Logistics Ext
Parameter–
expanmod2page3left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, third page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page3left: Engineering Ext
Parameter–
expanmod2page3right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the second 560M
expansion module, third page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod2page3right: Shipping Ext
41-001160-00, Release 2.1, Rev 04
Appendix A
Parameter–
expanmod2page2right
A-169
IP Phone Administrator Guide
Customizing 560M Expansion Module Column Display
Appendix A
Expansion Module 3
Parameter–
expanmod3page1left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, first page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page1left: Personnel Ext
Parameter–
expanmod3page1right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, first page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page1right: Operations Ext
Parameter–
expanmod3page2left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, second page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page2left: Marketing Ext
A-170
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Customizing 560M Expansion Module Column Display
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, second page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page2right: Logistics Ext
Parameter–
expanmod3page3left
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, third page, left column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page3left: Engineering Ext
Parameter–
expanmod3page3right
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to specify a customized heading for the third 560M expansion
module, third page, right column.
Format
Text String
Default Value
N/A
Range
N/A
Example
expanmod3page3right: Shipping Ext
41-001160-00, Release 2.1, Rev 04
A-171
Appendix A
Parameter–
expanmod3page2right
IP Phone Administrator Guide
Advanced Operational Parameters
Appendix A
Advanced Operational Parameters
The following parameters in this section allow the system administrator to set
advanced operational features on the IP phones.
Blind Transfer Setting
Parameter –
sip cancel after blind transfer
Configuration Files
Description
Forces the phone to use the Blind Transfer method available in software
prior to release 1.4. This method sends the CANCEL message after the
REFER message when blind transferring a call.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip cancel after blind transfer: 1
A-172
aastra.cfg, <mac>.cfg
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Advanced Operational Parameters
Update Caller ID Setting.
Configuration Files
aastra.cfg, <mac>.cfg
Description
Enables or disables the updating of the Caller ID information during a
call.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip update callerid: 1
Boot Sequence Recovery Mode.
Parameter –
force web recovery mode
disabled
Configuration Files
aastra.cfg, <mac>.cfg
Description
Enables or disables the forcing web recovery mode feature. If this
parameter is set to "1", you cannot force web recovery. If this parameter
is set to "0", press 1 and # keys during boot up when the logo displays to
force the web recovery mode.
Format
Boolean
Default Value
0 (false)
Range
0 (false)
1 (true)
Example
force web recovery mode disabled: 1
Parameter –
max boot count
Configuration Files
Description
Specifies the number of faulty boots that occur before the phone is forced
into Web recovery mode.
Format
Integer
Default Value
10
Range
0 to 32767
aastra.cfg, <mac>.cfg
Zero (0) disables the max boot count feature.
Example
max boot count: 0
41-001160-00, Release 2.1, Rev 04
A-173
Appendix A
Parameter –
sip update callerid
IP Phone Administrator Guide
Advanced Operational Parameters
Appendix A
Single Call Restriction
Parameter –
two call support
Aastra Web UI
Configuration Files
Advanced Settings->Global SIP->RTP Settings
aastra.cfg, <mac>.cfg
Two Call Support
(in Web UI)
Description
Enables or disables the single media path restriction between the
57i CT base unit and the handset.
When this feature is enabled (set to 1), you can make separate active
calls from the 57i CT base unit and from the cordless handset. If this
feature is disabled (set to 0), only one call can be active at a time either
from the base unit or from the handset.
When this feature is disabled, and you make an active call on either the
base unit or the handset, any other attempt to make an active call is put
on hold. Also, when this feature is disabled, more than one call can
negotiate complex audio codecs since only a single call is decoding
audio at a time.
Format
Boolean
Default Value
1
Range
0 - Disable
1 - Enable
Example
two call support: 0
A-174
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Advanced Operational Parameters
Blacklist Duration
Aastra Web UI
Advanced Settings->Global SIP Settings->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Blacklist Duration
(Aastra Web UI)
Description
Specifies the length of time, in seconds, that a failed server remains on
the server blacklist. The IP phone avoids sending a SIP message to a
failed server (if another server is available) for this amount of time.
Note: The value of “0” disables the blacklist feature.
Format
Integer
Default Value
300 (5 minutes)
Range
0 to 9999999
Example
sip blacklist duration: 600
Whitelist Proxy
Parameter –
sip whitelist
Aastra Web UI
Advanced Settings->Global SIP->
Advanced SIP Settings
Configuration Files aastra.cfg, <mac>.cfg
Whitelist Proxy
(Aastra Web UI)
Description
This parameter enables/disables the whitelist proxy feature, as follows:
•
•
Set to 0 to disable the feature.
Set to 1 to enable the feature. When this feature is enabled, an IP
phone accepts call requests from a trusted proxy server only. The IP
phone rejects any call requests from an untrusted proxy server.
Format
Boolean
Default Value
0 (disabled)
Range
0 (disabled)
1 (enabled)
Example
sip whitelist: 1
41-001160-00, Release 2.1, Rev 04
A-175
Appendix A
Parameter –
sip blacklist duration
IP Phone Administrator Guide
Advanced Operational Parameters
Appendix A
Symmetric UDP Signaling Setting
Parameter –
sip symmetric udp signaling
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to enable or disable the phone to use port 5060 to send SIP
UDP messages. The value “1” (which is the default) enables the phone
to use port 5060. The value “0” (zero) disables the phone from using
port 5060 and allows the phone to choose a random port to send SIP
UDP messages.
Format
Boolean
Default Value
1 (enabled)
Range
0 (disabled)
1 (enabled)
Example
sip symmetric udp signaling: 0
User-Agent Setting
Parameter –
sip user-agent
Configuration Files aastra.cfg, <mac>.cfg
Description
Allows you to enable or disable the addition of the User-Agent and
Server SIP headers in the SIP stack.
The value of “0” prevents the UserAgent and Server SIP header from
being added to the SIP stack. The value of “1” allows these headers to
be added.
Format
Boolean
Default Value
1 (true)
Range
0 (false)
1 (true)
Example
sip user-agent: 0
A-176
41-001160-00, Release 2.1, Rev 04
Configuration Parameters
Troubleshooting Parameters
Troubleshooting Parameters
Log Settings
Parameter –
log server ip
Aastra Web UI
Configuration Files
Advanced Settings->Troubleshooting->
Log Settings
aastra.cfg, <mac>.cfg
Log IP
(in Web UI)
Description
Specifies the IP address for which to save log files for troubleshooting
purposes.
Format
IP address
Default Value
0.0.0.0
Range
Not Applicable
Example
log server ip: 192.168.3.2
Parameter –
log server port
Aastra Web UI
Configuration Files
Advanced Settings->Troubleshooting->
Log Settings
aastra.cfg, <mac>.cfg
Log Port
(in Web UI)
Description
Specifies the IP port to use to save log files for troubleshooting purposes.
This is the IP port that transmits information from the IP phone to the IP
address location.
Format
Integer
Default Value
0
Range
Any valid IP port
Example
log server port: 2
41-001160-00, Release 2.1, Rev 04
A-177
Appendix A
The following parameters in this section allow the system administrator to set
logging and support settings for troubleshooting purposes.
Appendix A
IP Phone Administrator Guide
Troubleshooting Parameters
Parameters –
log module <module name>
Aastra Web UI
Configuration Files
Advanced Settings->Troubleshooting->
Module/Debug Level
aastra.cfg, <mac>.cfg
Module/Debug Level
(in Web UI)
Description
Allows enhanced severity filtering of log calls sent as blog output.
The blog, as used on the IP phones, is a an online debugging tool that
can be frequently updated and intended for technical support analyzation.
Blogs are defined by their format: a series of entries posted to a single
page in reverse-chronological order. The IP Phone blogs are separated
into modules which allow you to log specific information for analyzing:
Module Name (configuration files)
•
•
•
•
•
•
•
•
•
•
•
•
linemgr
user interface
misc
sip
dis (display driver)
ept (endpoint)
ind (indicator)
kbd (keyboard)
net (network)
provis (provisioning)
rtpt
snd (sound)
Format
Boolean
Default Value
1 (enable)
Range
0 - Disable
1 - Enable
Examples
log module sip: 0
log module kbd: 1
A-178
41-001160-00, Release 2.1, Rev 04
About this appendix
Introduction
This appendix describes how to setup the TFTP protocol configuration server in
your network.
Topics
This appendix covers the following topics:
Topic
Page
Configuration Server Protocol Setup
page B-2
TFTP Server Set-up
41-001160-00, Release 2.1, Rev 04
page B-2
B-1
Appendix B
Appendix B
Configuration Server Setup
IP Phone Administrator Guide
Configuration Server Protocol Setup
Appendix B
Configuration Server Protocol Setup
TFTP Server Set-up
There are a number of TFTP servers available. PumpKIN is one of such
TFTP servers. Use the keywords “pumpkin TFTP server” on Google and
you should get the web site where you can download the software
from. Installing PumpKIN is straightforward. To configure the directory
from where you would be serving the files, click on the Options button
on PumpKIN’s main window as shown in the following figure.
It is important to select the “Give all files” radio button under the “Read Request
Behavior” category. This makes the files to be served without any manual
intervention when requested.
B-2
41-001160-00, Release 2.1, Rev 04
Configuration Server Setup
Configuration Server Protocol Setup
41-001160-00, Release 2.1, Rev 04
Appendix B
If you want to prevent users from writing files to the directory select
the “Deny all requests” in the “Write Request Behavior” category. Click
the OK button after you have entered all the required information. All the
firmware files should be in the file system root directory. Currently we
do not support downloads from files present in sub-directories. Consult
PumpKIN’s documentation if you need more information on how to set-up the
TFTP server.
B-3
About this appendix
Introduction
This appendix describes how to setup a user’s phone with an extension to make
and receive calls using the Asterisk as the PBX.
Topics
This appendix covers the following topics:
Topic
Page
IP Phone at the Asterisk IP PBX
page C-2
41-001160-00, Release 2.1, Rev 04
C-1
Appendix C
Appendix C
Configuring the IP Phone
at the Asterisk IP PBX
IP Phone Administrator Guide
IP Phone at the Asterisk IP PBX
Appendix C
IP Phone at the Asterisk IP PBX
The following configuration illustrates how to create a user with an extension to
make and receive calls using the Asterisk as the PBX. This configuration is
defined in the sip.conf file present along with the other configuration files that are
created when Asterisk is installed. Usually, the configuration files can be found at
the /etc/asterisk directory.
;This is used in the “extensions.conf” file to identify this
;physical phone when issuing Dial commands.
[phone1]
;The type to use for the 57i is “friend”.
;”Peer” is used when the Asterisk is contacting a proxy,
;”user” is used for phones that can only make calls
;and “friend” acts as both a peer and a user.
type=friend
;If your host has an entry in your DNS then you just enter the
;machines name in the host= field.
host=dynamic
defaultip=192.168.1.1 ;default IP address that the phone is
;configured to
;The password that phone1 will use to register with this PBX
secret=1234
dtmfmode=rfc2833;Choices are inband, rfc2833, or info
mailbox=1000 ;Mailbox for message waiting indicator
;If a phone is not in a valid context you will not be
C-2
41-001160-00, Release 2.1, Rev 04
Configuring the IP Phone at the Asterisk IP PBX
IP Phone at the Asterisk IP PBX
;able to use it. In this example' sip' is used. You can use
;need to make an entry in your extensions.conf file (which we
;will get to later)
context=sip
callerid="Phone 1" <1234>
After this is defined in the “sip.conf” file, some information has to be entered in
the “extensions.conf” file present in the same directory as the “sip.conf” file. The
following definition in the file under the [sip]section/context completes defining
the extension for the 57i phone.
exten -> 1234,1,Dial(SIP/phone1,20)
This definition completes configuring the 57i phone at the IP PBX system.
To verify whether the extension has been successfully registered at the IP PBX
system, enter the Asterisk console and reload Asterisk. Use the command “sip
show peers” at the console. This will display the extensions that are registered at
the IP PBX system.
Name/username Host
Mask
Port
phone1/phone1192.168.1.1(D) 255.255.255.255 5060
Unmonitored
Status
This completes the basic set-up for the 57i phone with 1234 extension at
the Asterisk IP PBX system. Refer to Asterisk documentation for set-up on
extended or advanced features such as voice mail and call forwarding, etc.
41-001160-00, Release 2.1, Rev 04
C-3
Appendix C
;whatever you like, but make sure they are the same, you will
About this appendix
Introduction
This appendix provides sample configuration files for the 57i, 57i CT, and 53i.
Topics
This appendix covers the following topics:
Topic
Page
Sample Configuration Files
page D-2
57i Sample Configuration File
page D-2
57i CT Sample Configuration File
page D-12
53i Sample Configuration File
page D-29
41-001160-00, Release 2.1, Rev 04
D-1
Appendix D
Appendix D
Sample Configuration Files
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
Sample Configuration Files
This section consists of the sample configuration files necessary to configure the
IP phones. The general format is similar to configuration files used by several
Unix-based programs. Any text following a number sign (#) on a line is
considered to be a comment, unless the # is contained within
double-quotes. Currently, Boolean fields use 0 for false and 1 for true.
57i Sample Configuration File
# Sample Configuration File
# ===========================
# Date: October 20th, 2005
# Phone Model: 57i
# Notes:
#
# The general format used here is similar to configuration files
# used by several UNIX-based programs. Any text following a number
# sign (#) is considered to be a comment, unless the number sign is
# contained within double-quotes ("#") where it is considered to be
# a pound. For Boolean fields, 0 = false, 1 = true.
# Comments:
#
# This file contains sample configurations for the "aastra.cfg" or
# "<mac>.cfg" file. The settings included here are examples only.
# You should change/comment the values to suit your requirements.
#
# Not all possible paramters are shown, refer to the admin guide for
# the full list of supported parameters, their defaults and valid
# ranges.
#
D-2
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# The Aastra 57i, 57iCT, and 53i phones will download 2
Appendix D
# configuration files from the TFTP server while restarting, the
# "aastra.cfg" file and the "<mac>.cfg" file. These two configuration
# files can be used to configure all of the settings of the phone with
# the exception of assigning a static IP address to a phone and line
# settings, which should only be set in the "<mac>.cfg" file.
#
# The "aastra.cfg" file configures the settings server wide, while
# the "<mac>.cfg" file configures only the phone with the MAC address
# for which the file is named (for example, "00085d0304f4.cfg"). The
# settings in the "aastra.cfg" file will be overridden by settings
# which also appear in the "<mac>.cfg" file.
#------------------------------------------------------------------
# DHCP Setting
# ==============
#dhcp: 1 # DHCP enabled.
# DHCP:
# 0 = false, means DHCP is disabled.
# 1 = true, means DHCP is enabled.
#
# Notes:
#
# DHCP is normally set from the Options list on the phone or
# the web interface
#
# If DHCP is disabled, the following network settings will
# have to be configured manually either through the configuration
# files, the Options List in the phone, or the Web Client: IP
# Address (of the phone), Subnet Mask, Gateway, DNS, and TFTP
# Server.
#-------------------------------------------------------------------
41-001160-00, Release 2.1, Rev 04
D-3
IP Phone Administrator Guide
Sample Configuration Files
# Network Settings
Appendix D
## = = = = = = = =
# Notes: If DHCP is enabled, you do not need to set these network
# settings. Although depending on you DHCP server configuration you
# may still have to set the dns address.
#ip:
# This value is unique to each phone on a server
# and should be set in the "<mac>.cfg" file if
# setting this manually.
#subnet mask:
#default gateway:
#dns1:
#dns2:
# Time Server Settings
## =====================
#time server disabled: 1 # Time server disabled.
#time server1:
# Enable time server and enter at
#time server2:
# least one time server IP address or
#time server3:
# qualified domain name
# Time Server Disabled:
#
0 = false, means the time server is not disabled.
#
1 = true, means the time server is disabled.
# NAT Settings
# ===============
# Option 1:
#
# If you are connecting to a Nortel MCS call server and there is a
D-4
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# NAT device between the server and the phone, then you must set the
#sip nortel nat support: 1
# 1 = enabled
#sip nortel nat timer: 60
# seconds between keep alive messages
Appendix D
# following two parameters for the phone to function correctly.
# Option 2:
#
# If you are using a session border controller, you should set the
# outbound proxy to the session border controller address
#sip outbound proxy: sbc.aastra.com
#sip outbound proxy port: 0
# a value of 0 enables SRV
# lookups for the address of
# the proxy.
# Option 3:
#
# If you know the public IP address of your NAT device and and have
# opened up a port for the SIP messages then you can statically
# assign this information.
#sip nat ip: 67.123.122.90
#sip nat port: 5890
# Additional Network Settings
# =============================
#sip rtp port: 3000
# Eg. RTP packets are sent to port 3000.
#-------------------------------------------------------------------
# Configuration Server Settings
41-001160-00, Release 2.1, Rev 04
D-5
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
## = = = = = = = = = = = = = = =
# Notes: This section defines which server the phone retrieves new
# firmware images and configuration files from. Three protocols are
# supported TFTP, FTP and HTTP
download protocol: TFTP
# valid values are TFTP, FTP and HTTP
## TFTP server settings
tftp server: 192.168.0.130
#alternate tftp server:
#use alternate tftp server: 1
# If your DHCP server assigns
# a TFTP server address which
# you do not use, you can use
# the alternate tftp server.
## FTP server settings
#ftp server: 192.168.0.131
# can be IP or FQDN
#ftp username: aastra
#ftp password: 57iaastra
## HTTP server settings (for http://bogus.aastra.com/firmware/)
#http server: bogus.aastra.com
# can be IP or FQDN
#http path: firmware
#-------------------------------------------------------------------
# Dial Plan Settings
# =====================
#
# Notes:
#
# As you dial a number on the phone, the phone will initiate a call
# when one of the following conditions are meet:
D-6
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
#
(1) The entered number is an exact match in the dial plan
#
(2) The "#" symbol has been pressed
#
(3) A timeout occurs
Appendix D
#
#
# The dial plan is a regular expression that supports the following
# syntax:
#
#
0,1,2,3,4,5,6,7,8,9,*,# : matches the keypad symbols
#
x
: matches any digit (0...9)
#
+
: matches 0 or more repetitions of the
#
#
: previous expression
[]
#
: matches any number inside the brackets
: can be used with a "-" to represent a
#
: range
#
()
: expression grouping
#
|
: either or
#
#
# If the dialled number doesn't match the dial plan then the call
# is rejected.
sip digit timeout: 3
# set the inter-digit timeout in seconds
# Example dial plans
sip dial plan: "x+#|xx+*"
# this is the default dial string, note
# that is must be quoted since it contains
# a '#' character
#sip dial plan: [01]xxx|[2-8]xxxx|91xxxxxxxxxx
# accecpt any 4 digit number beginning
# with a 0 or 1, any 5 digit number
# beginning with a number between 2 and 8
# (inclusive) or a 12 digit number
# beginning with 91
41-001160-00, Release 2.1, Rev 04
D-7
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
#sip dial plan terminator: 1
# enable sending of the "#" symbol to
# to the proxy in the dial string
#------------------------------------------------------------------
# General SIP Settings
#===========
#sip session timer: 30
# enable support of RFC4028, the default
# value of 0 disables this functionality
#sip transport protocol: 0 # use UDP (1), TCP (2) or both (0) for sip
# messaging
#sip use basic codecs: 1
# limit codecs to G711 and G729
#sip out-of-band dtmf: 0
# turn off support for RFC2833 (on by
# default)
# Global SIP User Settings
# ==========================
#
# Notes:
#
These settings are used as the default configuration for the hard
#
key lines on the phone. That is:
#
#
L1 to L4 on the 57i and 57iCT
#
L1 to L3 on the 53i
#
#
These can be over-ridden on a per-line basis using the per-line
#
settings.
#
#
D-8
See the Admin Guide for a detailed explaination of how this works
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# the name display on the phone's screen
sip user name: 4256
# the phone number
Appendix D
sip screen name: Joe Smith
sip display name: Joseph Smith # the caller name sent out when making
# a call.
sip vmail: *78
# the number to reach voicemail on
sip auth name: jsmith
# account used to authenticate user
sip password: 12345
# password for authentication account
sip mode: 0
# line type:
#
0 - generic,
#
1 - BroadSoft SCA line
#
2 - Nortel line
sip proxy ip: proxy.aastra.com # IP address or FQDN of proxy
sip proxy port: 5060
# port used for SIP messages on the
# proxy. Set to 0 to enable SRV
# lookups
sip registrar ip: aastra.com
# IP address or FQDN of registrar
sip registrar port: 0
# as proxy port, but for the registrar
sip registration period: 3600 # registration period in seconds
# Per-line SIP Settings
# ======================
# configure line 3 as the support Broadsoft SCA line
#
#
- the proxy and registrar settings are taken from the global
settings above
sip line3 screen name: Support
sip line3 user name: 4000
sip line3 display name: Aastra Support
sip line3 auth name: support
sip line3 password: 54321
sip line3 mode: 1
41-001160-00, Release 2.1, Rev 04
D-9
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
sip line3 vmail: *78
# configure line 5 (a soft key line) as an ordinary line
# of a test server
sip line5 screen name: Test 1
sip line5 user name: 5551001
sip line5 display name: Test 1
sip line5 auth name: 5551001
sip line5 password: 5551001
sip line5 mode: 0
sip line5 proxy ip: 10.50.10.102
sip line5 proxy port: 5060
sip line5 registrar ip: 10.50.10.102
sip line5 registrar port: 5060
sip line5 registration period: 60
#------------------------------------------------------------------# Softkey Settings
#
# Softkeys can be set either server wide or unique to each phone.
# Setting softkeys as line/call appearances should be done in the
# "<mac>.cfg" file, since these are unique to each phone.
# Notes:
#
# There are a maximum of 18 softkeys that can be configured on the
# 57i or 57iCT phone. These can be set up through either of the 2
# configuration files, depending on whether this is to be server wide
# ("aastra.cfg") or phone specific ("<mac>.cfg"). Each softkey needs
# to be numbered from 1 - 18, for example "softkey12 type:
# speeddial". Softkeys can be set up as speeddials or as additional
# call/line appearances and have a type, label and value associated
D-10
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# with it as seen here in the default softkey settings.
Appendix D
# SOFTKEY TYPES: "line", "speeddial", "blf", "list", "dnd"
# SOFTKEY LABEL: Alpha numeric name for the softkey. The maximum
#
number of characters for this value is 10 for
#
speeddials and dnd, 9 chars for lines, blf
# SOFTKEY VALUE: If softkey type is a speeddial, any DTMFs (from
#
0 - 9, *, "#") or a comma (,) for 500ms pause and
#
'E' for On-hook can be set for the value.
#
If softkey type is blf it is the extension you want
#
to monitor.
# SOFTKEY LINE: This is line associated with the softkey. For line
#
softkeys the value must be between 5 and 9 (1 - 4
#
are already hardcoded as the L1, L2, L3 and L4 hard
#
key line/call appearances)
# Speed Dials
softkey1 type: speeddial
softkey1 label: "Ext Pickup"
softkey1 value: *8
softkey2 type: speeddial
softkey2 label: "Call Return"
softkey2 value: *69
# DND Key
softkey4 type: dnd
softkey4 label: DND
# Line appearance
softkey6 type: line
softkey6 label: Test 1
softkey6 line: 5
# blf
softkey8 type: blf
softkey8 label: Jane Doe
softkey8 value: 4559
41-001160-00, Release 2.1, Rev 04
D-11
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
softkey8 line: 1
# list
softkey11 type: list
softkey12 type: list
57i CT Sample Configuration File
# Sample Configuration File
# =========================
# Date: October 26th, 2005
# Phone Model: 57iCT
# Notes:
#
# The general format used here is similar to configuration files
# used by several UNIX-based programs. Any text following a number
# sign (#) is considered to be a comment, unless the number sign is
# contained within double-quotes ("#") where it is considered to be
# a pound. For Boolean fields, 0 = false, 1 = true.
# Comments:
#
# This file contains sample configurations for the "aastra.cfg" or
# "<mac>.cfg" file. The settings included here are examples only.
# You should change/comment the values to suit your requirements.
#
# Not all possible paramters are shown, refer to the admin guide for
# the full list of supported parameters, their defaults and valid
# ranges.
#
# The Aastra 57i, 57iCT, and 53i phones will download 2
# configuration files from the TFTP server while restarting, the
D-12
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# "aastra.cfg" file and the "<mac>.cfg" file. These two configuration
Appendix D
# files can be used to configure all of the settings of the phone with
# the exception of assigning a static IP address to a phone and line
# settings, which should only be set in the "<mac>.cfg" file.
#
# The "aastra.cfg" file configures the settings server wide, while the
# "<mac>.cfg" file configures only the phone with the MAC address for
# which the file is named (for example, "00085d0304f4.cfg"). The
# settings in the "aastra.cfg" file will be overridden by settings
# which also appear in the "<mac>.cfg" file.
#-------------------------------------------------------------------
# DHCP Setting
# ============
#dhcp: 1 # DHCP enabled.
# DHCP:
# 0 = false, means DHCP is disabled.
# 1 = true, means DHCP is enabled.
#
# Notes:
#
# DHCP is normally set from the Options list on the phone or
# the web interface
#
# If DHCP is disabled, the following network settings will
# have to be configured manually either through the configuration
# files, the Options List in the phone, or the Web Client: IP
# Address (of the phone), Subnet Mask, Gateway, DNS, and TFTP
# Server.
#-------------------------------------------------------------------
41-001160-00, Release 2.1, Rev 04
D-13
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
# Network Settings
# ================
# Notes: If DHCP is enabled, you do not need to set these network
# settings. Although depending on you DHCP server configuration you
# may still have to set the dns address.
D-14
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
#ip:
# This value is unique to each phone on a server
Appendix D
# and should be set in the "<mac>.cfg" file if
# setting this manually.
#subnet mask:
#default gateway:
#dns1:
#dns2:
# Time Server Settings
# ====================
#time server disabled: 1 # Time server disabled.
#time server1:
# Enable time server and enter at
#time server2:
# least one time server IP address or
#time server3:
# qualified domain name
# Time Server Disabled:
#
0 = false, means the time server is not disabled.
#
1 = true, means the time server is disabled.
# NAT Settings
#=============
# Option 1:
#
# If you are connecting to a Nortel MCS call server and there is a
# NAT device between the server and the phone, then you must set the
# following two parameters for the phone to function correctly.
#sip nortel nat support: 1
41-001160-00, Release 2.1, Rev 04
# 1 = enabled
D-15
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
#sip nortel nat timer: 60
# seconds between keep alive messages
# Option 2:
#
# If you are using a session border controller, you should set the
# outbound proxy to the session border controller address
#sip outbound proxy: sbc.aastra.com
#sip outbound proxy port: 0
# a value of 0 enables SRV
# lookups for the address of
# the proxy.
# Option 3:
#
# If you know the public IP address of your NAT device and and have
# opened up a port for the SIP messages then you can statically
# assign this information.
#sip nat ip: 67.123.122.90
#sip nat port: 5890
# Additional Network Settings
#============================
#sip rtp port: 3000
# Eg. RTP packets are sent to port 3000.
#------------------------------------------------------------------
# Configuration Server Settings
# =============================
D-16
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
Appendix D
# Notes: This section defines which server the phone retrieves new
# firmware images and configuration files from. Three protocols are
# supported TFTP, FTP and HTTP
download protocol: TFTP
# valid values are TFTP, FTP and HTTP
## TFTP server settings
tftp server: 192.168.0.130
#alternate tftp server:
#use alternate tftp server: 1
# If your DHCP server assigns
# a TFTP server address which
# you do not use, you can use
# the alternate tftp server.
## FTP server settings
#ftp server: 192.168.0.131
# can be IP or FQDN
#ftp username: aastra
#ftp password: 57iaastra
## HTTP server settings (for http://bogus.aastra.com/firmware/)
#http server: bogus.aastra.com
# can be IP or FQDN
#http path: firmware
#------------------------------------------------------------------
# Dial Plan Settings
# ==================
#
# Notes:
#
41-001160-00, Release 2.1, Rev 04
D-17
IP Phone Administrator Guide
Sample Configuration Files
# As you dial a number on the phone, the phone will initiate a call
Appendix D
# when one of the following conditions are meet:
#
#
(1) The entered number is an exact match in the dial plan
#
(2) The "#" symbol has been pressed
#
(3) A timeout occurs
#
# The dial plan is a regular expression that supports the following
# syntax:
#
#
0,1,2,3,4,5,6,7,8,9,*,# : matches the keypad symbols
#
x
: matches any digit (0...9)
#
+
: matches 0 or more repetitions of the
#
#
: previous expression
[]
: matches any number inside the brackets
#
: can be used with a "-" to represent a
#
: range
#
()
: expression grouping
#
|
: either or
#
#
# If the dialled number doesn't match the dial plan then the call
# is rejected.
sip digit timeout: 3
# set the inter-digit timeout in seconds
# Example dial plans
sip dial plan: "x+#|xx+*"
# this is the default dial string, note
# that is must be quoted since it contains
# a '#' character
#sip dial plan: [01]xxx|[2-8]xxxx|91xxxxxxxxxx
# accecpt any 4 digit number beginning
D-18
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# with a 0 or 1, any 5 digit number
Appendix D
# beginning with a number between 2 and 8
# (inclusive) or a 12 digit number
# beginning with 91
#sip dial plan terminator: 1
# enable sending of the "#" symbol to
# to the proxy in the dial string
#-------------------------------------------------------------------
# General SIP Settings
# ====================
#sip session timer: 30
# enable support of RFC4028, the default
# value of 0 disables this functionality
#sip transport protocol: 0 # use UDP (1), TCP (2) or both (0) for sip
# messaging
#sip use basic codecs: 1
# limit codecs to G711 and G729
#sip out-of-band dtmf: 0
# turn off support for RFC2833 (on by
# default)
# Global SIP User Settings
# ========================
#
# Notes:
#
These settings are used as the default configuration for the hard
#
key lines on the phone. That is:
#
41-001160-00, Release 2.1, Rev 04
D-19
IP Phone Administrator Guide
Sample Configuration Files
L1 to L4 on the 57i and 57iCT
#
L1 to L3 on the 53i
Appendix D
#
#
#
These can be over-ridden on a per-line basis using the per-line
#
settings.
#
#
See the Admin Guide for a detailed explaination of how this works
sip screen name: Joe Smith
# the name display on the phone's screen
sip user name: 4256
# the phone number
sip display name: Joseph Smith # the caller name sent out when making
# a call.
sip vmail: *78
# the number to reach voicemail on
sip auth name: jsmith
# account used to authenticate user
sip password: 12345
# password for authentication account
sip mode: 0
# line type:
#
0 - generic,
#
1 - BroadSoft SCA line
#
2 - Nortel line
sip proxy ip: proxy.aastra.com # IP address or FQDN of proxy
sip proxy port: 5060
# port used for SIP messages on the
# proxy. Set to 0 to enable SRV
# lookups
sip registrar ip: aastra.com
# IP address or FQDN of registrar
sip registrar port: 0
# as proxy port, but for the registrar
sip registration period: 3600 # registration period in seconds
# Per-line SIP Settings
# =====================
D-20
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
#
#
Appendix D
# configure line 3 as the support Broadsoft SCA line
- the proxy and registrar settings are taken from the global
settings above
sip line3 screen name: Support
sip line3 user name: 4000
sip line3 display name: Aastra Support
sip line3 auth name: support
sip line3 password: 54321
sip line3 mode: 1
sip line3 vmail: *78
# configure line 5 (a soft key line) as an ordinary line
# of a test server
sip line5 screen name: Test 1
sip line5 user name: 5551001
sip line5 display name: Test 1
sip line5 auth name: 5551001
sip line5 password: 5551001
sip line5 mode: 0
sip line5 proxy ip: 10.50.10.102
sip line5 proxy port: 5060
sip line5 registrar ip: 10.50.10.102
sip line5 registrar port: 5060
sip line5 registration period: 60
#------------------------------------------------------------------# Softkey Settings
# ================
41-001160-00, Release 2.1, Rev 04
D-21
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
# Softkeys can be set either server wide or unique to each phone.
# Setting softkeys as line/call appearances should be done in the
# "<mac>.cfg" file, since these are unique to each phone.
# Notes:
#
# There are a maximum of 18 softkeys that can be configured on the
# 57i or 57iCT phone. These can be set up through either of the 2
# configuration files, depending on whether this is to be server wide
# ("aastra.cfg") or phone specific ("<mac>.cfg"). Each softkey needs
# to be numbered from 1 - 18, for example "softkey12 type:
# speeddial". Softkeys can be set up as speeddials or as additional
# call/line appearances and have a type, label and value associated
# with it as seen here in the default softkey settings.
# SOFTKEY TYPES: "line", "speeddial", "blf", "list", "dnd"
# SOFTKEY LABEL: Alpha numeric name for the softkey. The maximum
#
number of characters for this value is 10 for
#
speeddials and dnd, 9 chars for lines, blf
# SOFTKEY VALUE: If softkey type is a speeddial, any DTMFs (from
#
0 - 9, *, "#") or a comma (,) for 500ms pause and
#
'E' for On-hook can be set for the value.
#
If softkey type is blf it is the extension you want
#
to monitor.
# SOFTKEY LINE: This is line associated with the softkey. For line
#
softkeys the value must be between 5 and 9 (1 - 4
#
are already hardcoded as the L1, L2, L3 and L4 hard
#
key line/call appearances)
# Speed Dials
softkey1 type: speeddial
softkey1 label: "Ext Pickup"
softkey1 value: *8
D-22
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
softkey2 type: speeddial
Appendix D
softkey2 label: "Call Return"
softkey2 value: *69
# DND Key
softkey4 type: dnd
softkey4 label: DND
# Line appearance
softkey6 type: line
softkey6 label: Test 1
softkey6 line: 5
# blf
softkey8 type: blf
softkey8 label: Jane Doe
softkey8 value: 4559
softkey8 line: 1
# list
softkey11 type: list
softkey12 type: list
#------------------------------------------------------------------# Cordless Handset Feature Keys
# =============================
# Notes:
#
# In addition to the configuration parameters that exist on the 57i
# phone, following are the parameters specific to the 57i Cordless
# phones' handset. These parameters can be defined either int the
41-001160-00, Release 2.1, Rev 04
D-23
IP Phone Administrator Guide
Sample Configuration Files
# aastra.cfg or the <mac>.cfg files.
Appendix D
#
# The feature keys are displayed when the user presses the F button
# on the cordless phone's hand set. If any changes to the features
# keys are made using these parameters the feature keys that exist on
# the hand set have to be refreshed. To refresh the feature keys
# simply open a new line or press one of the feature keys that are
# available from the hand set. After a couple of seconds the cordless
# should get the new list from the base set. There are 15 feature
# keys that can be configured for the cordless hand set. Each feature
# key has the following settings. N corresponds to the feature key
# that is being configured for and ranges from 0-14. Feature key N
# En label: "String" Feature key N Fr label: "Fr-String" Feature key
# N Sp label: "Sp-String" Feature key N control: 1
# integer value Feature key N hs event: 1
#Takes an
#Takes an integer value
# Feature key N base event: 1 #Takes an integer value
#key list version: 1
# The parameter value has to be incremented by one whenever the
# parameters that carry the feature keys change. The range is from
# 1-254. After reaching 254 start over from 1.
#Feature key 0 En label: "Line 1"
# English label for the key. Displayed when the phone's language is
# set to use English
#Feature key 0 Fr label: "Fr-Line 1"
# French label for the key. Displayed when the phone's language
# is set to use French
#Feature key 0 Sp label: "Sp-Line 1"
# Spanish label for the key. Displayed when the phone's language
# is set to use Spanish
D-24
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
Appendix D
Feature key 0 Gr label: "Gr-Line 1"
# German label for the key. Displayed when the phone's language
# is set to use German
Feature key 0 It label: "It-Line 1"
# Italian label for the key. Displayed when the phone's language
# is set to use Italian
#Feature key 0 control: 1
# 1 - Make the key configurable by the user through the phone and
#
the phone's web client
# 2 - Locks the key from user modifications. User cannot modify
#
this key from the handset or the phone's web client.
# 4 - Hide this key. Do not show it in the Feature keys list in the
#
cordless handset
# 6 - Lock and hide this key. Do not show it in the Feature keys
#
list in the cordless handset and do not let the user modify
#
this key using the phone or the web client.
#Feature key 0 hs event: 7
# These events are for handset specific events. Events can be local
# to the handset like directory/caller's list, intercom etc. or may
# be an event that is sent to the base set for fruther processing.
# When this key is configured as a base event then the base set
# will process the value of this key in conjunction with the value
# configured for the "Feature key N base event". Where N is the
# feature key is being configured for.
# In addition to the values listed below the valid values are
# [7-23]. The values [7-23] indicate generic handset events. If
# you are using values within this range make sure to use the value
# only once.
# The events local to the handset are as follows:
#
41-001160-00, Release 2.1, Rev 04
D-25
IP Phone Administrator Guide
Sample Configuration Files
58 - Menu (Options)
#
59 - Feature Key
#
60 - Redial
#
61 - Directory
#
62 - Callers' list
#
63 - Services
#
86 - Icom
Appendix D
#
#Feature key 0 base event: 1
# Indicates a corresponding action to perform on the base set when
# the "Feature key N hs event" is set to any value between 7-23.
#
#
1 - Seize base set's line1
#
2 - Seize base set's line2
#
3 - Seize base set's line3
#
4 - Seize base set's line4
#
5 - Seize base set's line5
#
6 - Seize base set's line6
#
7 - Seize base set's line7
#
8 - Seize base set's line8
#
9 - Seize base set's line9
#
10 - Seize base set's line0
#
11 - Send the base set's transfer event
#
12 - Send the base set's conference event
#
13 - Make feature list public
# Example configuration
key list version: 1
Feature key 0 En label: "Line 1"
Feature key 0 Fr label: "Fr-Line 1"
Feature key 0 Sp label: "Sp-Line 1"
Feature key 0 control: 0
D-26
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
Feature key 0 hs event: 7
Appendix D
Feature key 0 base event: 1
Feature key 1 En label: "Conf."
Feature key 1 Fr label: "Fr-Conf."
Feature key 1 Sp label: "Sp-Conf."
Feature key 1 control: 1
Feature key 1 hs event: 8
Feature key 1 base event: 12
Feature key 2 En label: "Xfer"
Feature key 2 Fr label: "Fr-Xfer."
Feature key 2 Sp label: "Sp-Xfer."
Feature key 2 control: 2
Feature key 2 hs event: 9
Feature key 2 base event: 11
Feature key 3 En label: "Icom"
Feature key 3 Fr label: "Fr-Icom"
Feature key 3 Sp label: "Sp-Icom"
Feature key 3 control: 1
Feature key 3 hs event: 86
Feature key 3 base event: 13
Feature key 4 En label: "Opt"
Feature key 4 Fr label: "Fr-Opt"
Feature key 4 Sp label: "Sp-Opt"
Feature key 4 hs event: 58
Feature key 4 control: 1
Feature key 4 base event: 13
Feature key 5 En label: "Callers"
Feature key 5 Fr label: "Fr-Callers"
Feature key 5 Sp label: "Sp-Callers"
41-001160-00, Release 2.1, Rev 04
D-27
IP Phone Administrator Guide
Sample Configuration Files
Feature key 5 hs event: 62
Appendix D
Feature key 5 control: 1
Feature key 5 base event: 13
Feature key 6 En label: "Top"
Feature key 6 Fr label: "Fr-Top"
Feature key 6 Sp label: "Sp-Top"
Feature key 6 hs event: 17
Feature key 6 control: 1
Feature key 6 base event: 13
Feature key 7 En label: "Redial"
Feature key 7 Fr label: "Fr-Redial"
Feature key 7 Sp label: "Sp-Redial"
Feature key 7 hs event: 60
Feature key 7 control: 4
Feature key 7 base event: 13
Feature key 8 En label: "Dir."
Feature key 8 Fr label: "Fr-Dir."
Feature key 8 Sp label: "Sp-Dir."
Feature key 8 hs event: 61
Feature key 8 control: 2
Feature key 8 base event: 13
Feature key 9 En label: "Services"
Feature key 9 Fr label: "Fr-Services"
Feature key 9 Sp label: "Sp-Services"
Feature key 9 hs event: 63
Feature key 9 control: 1
Feature key 9 base event: 13
D-28
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
53i Sample Configuration File
Appendix D
# Sample Configuration File
#= = = = = = = = = = = = = = = = = = = = =
# Date: October 26th, 2005
# Phone Model: 53i
# Notes:
#
# The general format used here is similar to configuration files
# used by several UNIX-based programs. Any text following a number
# sign (#) is considered to be a comment, unless the number sign is
# contained within double-quotes ("#") where it is considered to be
# a pound. For Boolean fields, 0 = false, 1 = true.
# Comments:
#
# This file contains sample configurations for the "aastra.cfg" or
# "<mac>.cfg" file. The settings included here are examples only.
# You should change/comment the values to suit your requirements.
#
# Not all possible paramters are shown, refer to the admin guide
# for the full list of supported parameters, their defaults and
# valid ranges.
#
# The Aastra 57i, 57iCT, and 53i phones will download 2
# configuration files from the TFTP server while restarting, the
# "aastra.cfg" file and the "<mac>.cfg" file. These two
# configuration files can be used to configure all of the settings
# of the phone with the exception of assigning a static IP address
# to a phone and line settings, which should only be set in the "<mac>.cfg" file.
#
41-001160-00, Release 2.1, Rev 04
D-29
IP Phone Administrator Guide
Sample Configuration Files
# The "aastra.cfg" file configures the settings server wide, while
Appendix D
# the "<mac>.cfg" file configures only the phone with the MAC
# address for which the file is named (for example,
# "00085d0304f4.cfg"). The settings in the "aastra.cfg" file will
# be overridden by settings which also appear in the "<mac>.cfg" file.
#-----------------------------------------------------------------
# DHCP Setting
# =============
#dhcp: 1 # DHCP enabled.
# DHCP:
# 0 = false, means DHCP is disabled.
# 1 = true, means DHCP is enabled.
#
# Notes:
#
# DHCP is normally set from the Options list on the phone or
# the web interface
#
# If DHCP is disabled, the following network settings will
# have to be configured manually either through the configuration
# files, the Options List in the phone, or the Web Client: IP
# Address (of the phone), Subnet Mask, Gateway, DNS, and TFTP
# Server.
#-----------------------------------------------------------------
# Network Settings
# = = = = = = = = =
# Notes: If DHCP is enabled, you do not need to set these network
# settings. Although depending on you DHCP server configuration
# you may still have to set the dns address.
D-30
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
Appendix D
#ip:
# This value is unique to each phone on a server
# and should be set in the "<mac>.cfg" file if
# setting this manually.
#subnet mask:
#default gateway:
#dns1:
#dns2:
# Time Server Settings
# =====================
#time server disabled: 1 # Time server disabled.
#time server1:
#time server2:
#time server3:
# Enable time server and enter at
# least one time server IP address or
# qualified domain name.
# Time Server Disabled:
#
0 = false, means the time server is not disabled.
#
1 = true, means the time server is disabled.
# NAT Settings
# = = = = = = =
# Option 1:
#
# If you are connecting to a Nortel MCS call server and there is a
# NAT device between the server and the phone, then you must set
# the following two parameters for the phone to function
# correctly.
#sip nortel nat support: 1
41-001160-00, Release 2.1, Rev 04
# 1 = enabled
D-31
IP Phone Administrator Guide
Sample Configuration Files
# seconds between keep alive messages
Appendix D
#sip nortel nat timer: 60
D-32
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# Option 2:
Appendix D
#
# If you are using a session border controller, you should set the
# outbound proxy to the session border controller address
#sip outbound proxy: sbc.aastra.com
#sip outbound proxy port: 0
# a value of 0 enables SRV
# lookups for the address of
# the proxy.
# Option 3:
#
# If you know the public IP address of your NAT device and and have
# opened up a port for the SIP messages then you can statically
# assign this information.
#sip nat ip: 67.123.122.90
#sip nat port: 5890
# Additional Network Settings
# ============================
#sip rtp port: 3000
# Eg. RTP packets are sent to port 3000.
#-----------------------------------------------------------------
# Configuration Server Settings
# = = = = = = = = = = = = = =
# Notes: This section defines which server the phone retrieves new
# firmware images and configuration files from. Three protocols
# are supported TFTP, FTP and HTTP
download protocol: TFTP
# valid values are TFTP, FTP and HTTP
41-001160-00, Release 2.1, Rev 04
D-33
Appendix D
IP Phone Administrator Guide
Sample Configuration Files
D-34
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
## TFTP server settings
Appendix D
tftp server: 192.168.0.130
#alternate tftp server:
#use alternate tftp server: 1
# If your DHCP server assigns
# a TFTP server address which
# you do not use, you can use
# the alternate tftp server.
## FTP server settings
#ftp server: 192.168.0.131
# can be IP or FQDN
#ftp username: aastra
#ftp password: 57iaastra
## HTTP server settings (for http://bogus.aastra.com/firmware/)
#http server: bogus.aastra.com
# can be IP or FQDN
#http path: firmware
#----------------------------------------------------------------
# Dial Plan Settings
# ====================
#
# Notes:
#
# As you dial a number on the phone, the phone will initiate a call
# when one of the following conditions are meet:
#
#
(1) The entered number is an exact match in the dial plan
#
(2) The "#" symbol has been pressed
#
(3) A timeout occurs
#
# The dial plan is a regular expression that supports the
# following:
# syntax:
41-001160-00, Release 2.1, Rev 04
D-35
IP Phone Administrator Guide
Sample Configuration Files
Appendix D
#
D-36
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
0,1,2,3,4,5,6,7,8,9,*,# : matches the keypad symbols
#
x
: matches any digit (0...9)
#
+
: matches 0 or more repetitions of the
#
#
Appendix D
#
: previous expression
[]
: matches any number inside the brackets
#
: can be used with a "-" to represent a
#
: range
#
()
: expression grouping
#
|
: either or
#
#
# If the dialled number doesn't match the dial plan then the call
# is rejected.
sip digit timeout: 3
# set the inter-digit timeout in seconds
# Example dial plans
sip dial plan: "x+#|xx+*"
# this is the default dial string, note
# that is must be quoted since it contains
# a '#' character
#sip dial plan: [01]xxx|[2-8]xxxx|91xxxxxxxxxx
# accecpt any 4 digit number beginning
# with a 0 or 1, any 5 digit number
# beginning with a number between 2 and 8
# (inclusive) or a 12 digit number
# beginning with 91
#sip dial plan terminator: 1
# enable sending of the "#" symbol to
# to the proxy in the dial string
#-----------------------------------------------------------------
41-001160-00, Release 2.1, Rev 04
D-37
IP Phone Administrator Guide
Sample Configuration Files
# General SIP Settings
Appendix D
# ======================
#sip session timer: 30
# enable support of RFC4028, the default
# value of 0 disables this functionality
#sip transport protocol: 0 # use UDP (1), TCP (2) or both (0) for
# sip messaging
#sip use basic codecs: 1
# limit codecs to G711 and G729
#sip out-of-band dtmf: 0
# turn off support for RFC2833 (on by
# default)
# Global SIP User Settings
# ==========================
#
# Notes:
#
These settings are used as the default configuration for the
#
hard key lines on the phone. That is:
#
#
L1 to L4 on the 57i and 57iCT
#
L1 to L3 on the 53i
#
#
These can be over-ridden on a per-line basis using the per-line
#
settings.
#
#
#
See the Admin Guide for a detailed explaination of how this
works
sip screen name: Joe Smith # the name display on the phone's screen
sip user name: 4256
# the phone number
sip display name: Joseph Smith # the caller name sent out when making
# a call.
sip vmail: *78
D-38
# the number to reach voicemail on
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
sip auth name: jsmith
# account used to authenticate user
# password for authentication account
sip mode: 0
# line type:
#
0 - generic,
#
1 - BroadSoft SCA line
#
2 - Nortel line
Appendix D
sip password: 12345
sip proxy ip: proxy.aastra.com # IP address or FQDN of proxy
sip proxy port: 5060
# port used for SIP messages on the
# proxy. Set to 0 to enable SRV
# lookups
sip registrar ip: aastra.com
# IP address or FQDN of registrar
sip registrar port: 0
# as proxy port, but for the registrar
sip registration period: 3600 # registration period in seconds
# Per-line SIP Settings
# =======================
# configure line 3 as the support Broadsoft SCA line
#
#
- the proxy and registrar settings are taken from the global
settings above
sip line3 screen name: Support
sip line3 user name: 4000
sip line3 display name: Aastra Support
sip line3 auth name: support
sip line3 password: 54321
sip line3 mode: 1
sip line3 vmail: *78
# configure line 5 (a soft key line) as an ordinary line
# of a test server
41-001160-00, Release 2.1, Rev 04
D-39
IP Phone Administrator Guide
Sample Configuration Files
sip line5 screen name: Test 1
Appendix D
sip line5 user name: 5551001
sip line5 display name: Test 1
sip line5 auth name: 5551001
sip line5 password: 5551001
sip line5 mode: 0
sip line5 proxy ip: 10.50.10.102
sip line5 proxy port: 5060
sip line5 registrar ip: 10.50.10.102
sip line5 registrar port: 5060
sip line5 registration period: 60
#----------------------------------------------------------------# Programmable Key Settings
# ===========================
# Programmable keys can be set either server wide or unique to each
# phone.
# Setting programmable keys as line/call appearances should be done
# in the "<mac>.cfg" file, since these are unique to each phone.
# Notes:
#
# There are a maximum of 7 programmable keys that can be configured
# on the 53i phone, and only 2 on the phone. These can be
# set up through either of the 2 configuration files, depending on
# whether this is to be server wide ("aastra.cfg") or phone
# specific ("<mac>.cfg"). Each prgkey needs to be numbered from
# 1 - 7, for example "prgkey2 type:
# speeddial". Programmable keys can be set up as speeddials or as
# additional call/line appearances or as feature keys and have a
# type, value and line associated with it as seen here in the
# default programmable settings.
# PRGKEY TYPES: "line", "speeddial", "blf", "list", "dnd"
D-40
41-001160-00, Release 2.1, Rev 04
Sample Configuration Files
Sample Configuration Files
# PRGKEY VALUE: If prgkey type is a speeddial, any DTMFs (from
0 - 9, *, "#") or a comma (,) for 500ms pause and
#
'E' for On-hook can be set for the value.
#
If prgkey type is blf it is the extension you want
#
to monitor.
# PRGKEY LINE:
This is line associated with the prgkey. For line
#
prgkeys the value must be between 4 and 9 (1 - 3
#
are already hardcoded as the L1, L2 and L3 hard
#
key line/call appearances).
Appendix D
#
# Speed Dials
prgkey1 type: speeddial
prgkey1 value: *8
prgkey2 type: speeddial
prgkey2 value: *69
# DND Key
prgkey3 type: dnd
# Line appearance
prgkey4 type: line
prgkey4 line: 5
# blf
prgkey5 type: blf
prgkey5 value: 4559
prgkey5 line: 1
# list
prgkey6 type: list
prgkey7 type: list
41-001160-00, Release 2.1, Rev 04
D-41
About this appendix
Introduction
This appendix provides sample BLF softkey settings for both the Asterisk server
and the BroadSoft BroadWorks server.
Topics
This appendix covers the following topics:
Topic
Page
Sample BLF Softkey Settings
page E-2
Asterisk BLF
page E-2
BroadSoft BroadWorks BLF
page E-3
41-001160-00, Release 2.1, Rev 04
E-1
Appendix E
Appendix E
Sample BLF Softkey Settings
IP Phone Administrator Guide
Sample BLF Softkey Settings
Appendix E
Sample BLF Softkey Settings
Asterisk BLF
The following are sample softkey and programmable key configurations to enable
Asterisk BLF support on Aastra IP phones.
57i and 57i CT Configuration Parameters for Asterisk BLF
softkey1
softkey1
softkey1
softkey1
type: blf
value: 9995551212
label: John
line: 1
53i Configuration Parameters for Asterisk BLF
E-2
prgkey1
prgkey1
prgkey1
prgkey1
type: blf
value: 9995551212
label: John
line: 1
prgkey7
prgkey7
prgkey7
prgkey7
type: blf
value: 9995551313
label: Jane
line: 1
41-001160-00, Release 2.1, Rev 04
Sample BLF Softkey Settings
Sample BLF Softkey Settings
BroadSoft BroadWorks BLF
57i and 57i CT Configuration Parameters for Broadsoft BroadWorks BLF
Note: One softkey must be defined of type “list” for EACH monitored
user. So if there are 2 users being monitored, 2 softkeys must be defined
of type list.
softkey1 type: list
softkey1 label:
softkey1 value:
softkey1 line: 1
softkey2 type: list
softkey2 label:
softkey2 value:
softkey2 line: 1
list uri: sip:my57i-blf-list@as.broadsoft.com
53i Configuration Parameters for Broadsoft BroadWorks BLF
Note: One prgkey must be defined of type “list” for each monitored user.
So if there are 2 users being monitored, 2 prgkeys must be defined of type
list.
prgkey6 type: list
prgkey6 label:
prgkey6 value: 1
prgkey7 type: list
prgkey7 label:
prgkey7 value: 1
list uri: sip:my53i-blf-list@as.broadsoft.com
41-001160-00, Release 2.1, Rev 04
E-3
Appendix E
The following are sample softkey and programmable key configurations to enable
Broadsoft BroadWorks Busy Lamp Field support on Aastra IP phones.
About this appendix
Introduction
This appendix provides a sample multiple proxy server configuration.
Topics
This appendix covers the following topics:
Topic
Page
Multiple Proxy Server Configuration
page F-2
41-001160-00, Release 2.1, Rev 04
F-1
Appendix F
Appendix F
Sample Multiple Proxy Server
Configuration
IP Phone Administrator Guide
Multiple Proxy Server Configuration
Appendix F
Multiple Proxy Server Configuration
Multiple proxy servers can be configured in the aastra.cfg file or the <mac>.cfg
file. In the example below, the default proxy setting is used if no specific setting is
specified in the line configuration. Line2 and line3 are used for the global proxy
configurations, while line1 and line4 use their own specific settings.
#sip settings
sip proxy ip: #.#.#.#
sip proxy port: 5060
sip registrar ip: #.#.#.#
sip registrar port: 5060
sip registration period:3600
sip nortel nat support:0
sip nortel nat timer:0
sip broadsoft talk:0
sip broadsoft hold:0
sip broadsoft conference:0
sip dial plan: "x+#""
#line info
# Fill in all necessary information below carefully. Populate all
lines even if there is only
# one account
#line 1
sip line1 auth name:
sip line1 password:
sip line1 mode: 0
sip line1 user name:
sip line1 display name:
sip line1 screen name:
sip line1 proxy ip: &.&.&.&
sip line1 proxy port: 5060
sip line1 registrar ip: #.#.#.#
sip line1 registrar port: 5060
sip registration period:600
sip nortel nat support:1
sip nortel nat timer:120
sip broadsoft talk:0
sip broadsoft hold:0
sip broadsoft conference:0
F-2
41-001160-00, Release 2.1, Rev 04
Sample Multiple Proxy Server Configuration
Multiple Proxy Server Configuration
#line 2
sip line2
sip line2
sip line2
sip line2
sip line2
sip line2
auth name:
password:
mode: 0
user name:
display name:
screen name:
#line 3
sip line3
sip line3
sip line3
sip line3
sip line3
sip line3
auth name:
password:
mode: 0
user name:
display name:
screen name:
Appendix F
Continued.....
#line 4
sip line4 auth name:
sip line4 password:
sip line4 mode: 0
sip line4 user name:
sip line4 display name:
sip line4 screen name:
sip line4 proxy ip: %.%.%.%
sip line4 proxy port: 5060
sip line4 registrar ip: %.%.%.%
sip line4 registrar port: 5060
sip registration period:500
sip nortel nat support:0
sip nortel nat timer:0
sip broadsoft talk:1
sip broadsoft hold:1
sip broadsoft conference:1
41-001160-00, Release 2.1, Rev 04
F-3
About this appendix
Introduction
This appendix provides information required to create an XML application for use
on the IP phones.
Topics
This appendix covers the following topics:
Topic
Page
How to Create an XML Application
page G-3
XML format
page G-3
Support of Virtual Web Servers
page G-3
Creating XML Objects
page G-4
Creating Custom Softkeys
page G-5
Text Menu Object (Menu Screens)
page G-6
Text Screen Object (Text Screens)
page G-12
UserInput Object (User Input Screens)
page G-21
Directory Object (Directory List Screen) (57i only)
page G-36
Status Message Object (Idle Screen)
page G-38
Execute Commands Object (for executing XML commands)
page G-40
Dynamic Configuration Object (to push a configuration to the phone)
page G-44
XML Image Objects (55i, 57i/57i CT only)
page G-48
41-001160-00, Release 2.1, Rev 04
G-1
Appendix G
Appendix G
Creating an XML Application
IP Phone Administrator Guide
About this appendix
Appendix G
Topic
G-2
Page
Attributes/Options to Use with XML Objects
page G-40
HTTP Post
page G-62
XML Schema File
page G-65
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
How to Create an XML Application
This Appendix describes how to create an XML application for your IP phones.
Sections in this appendix include:
•
XML format
•
Creating XML Objects
•
Creating Custom Softkeys
•
HTTP Post
•
XML Schema File
XML format
The text in the Aastra XML objects must be compliant with XML
recommendations and special characters must be escape encoded. The default
character set for the XML API is ISO-8859-1.
Character
Description
Escape Sequence
&
Ampersand
&amp;
"
Quote
&quot;
’
Apostrophe
&apos;
<
Left angle bracket
&lt;
>
Right angle bracket
&gt;
Support of Virtual Web Servers
The IP phones support the configuration of a web sever to host multiple websites
with different content. With this feature, the webserver looks at the Host header in
the incoming HTTP request sent by the browser to determine which website the
phone is trying to access.
41-001160-00, Release 2.1, Rev 04
G-3
Appendix G
Overview
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Creating XML Objects
This section describes how to create XML objects.
The IP phone XML API supports the following proprietary objects that allow for
the customization of the IP phone’s display.
•
Text Menu Object (Menu Screens)
— Turning Off Automatic Numbering of Menu Items
— Using Bullets in Menu Items
•
Text Screen Object (Text Screens)
— Text Screen Format Object (for Text Screens)
•
UserInput Object (User Input Screens)
— Time and Date Formats (User Input Screens)
— Multiple Input Fields (User Input Screens)
•
Directory Object (Directory List Screen) (57i only)
•
Status Message Object (Idle Screen)
•
Execute Commands Object (for executing XML commands)
— Using the Reset Command
— Using the NoOp Command
— Using the FastReboot Command
— XML Softkey or Programmable Key LED Behavior Command
•
Dynamic Configuration Object (to push a configuration to the phone)
•
XML Image Objects (55i, 57i/57i CT only)
You can also use the following attributes/options with the XML objects:
G-4
•
Beep Attribute (configurable via XML objects, config files, or Aastra Web
UI)
•
Scroll Delay Option (configurable via config files and Aastra Web UI only)
•
Timeout Attribute (configurable via XML objects only)
•
LockIn Attribute (configurable via XML objects only)
•
CancelAction Attribute (configurable via XML objects only)
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Creating Custom Softkeys
The following softkey functionality is available to the developer for the purpose
of reordering or preserving the default functionality of the XML screens. The
"Dial" function is available to screens that allow input. The dial string for the
"Dial" function is taken from the menu items URI on the Menu Screen, and from
the editor field input on the Input Screen.
Existing Action
Keys
Text
Screen
Menu
Screen
Input
Screen
Select
X
Done
X
X
Cancel
X
X
X
X
X
X
Exit
Dial
X
Submit
X
Backspace
X
Nextspace
X
Dot
X
ChangeCase
X
Numeric/Alpha
X
41-001160-00, Release 2.1, Rev 04
G-5
Appendix G
Developers can link arbitrary URIs to softkeys in the XML screens and can
invoke softkey behavior to each XML screen type (Text Menu, Text Screen, User
Input, Directory). A developer can define up to six softkeys before the closing tag
of any object on the 57i/57i CT.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Text Menu Object (Menu Screens)
The Text Menu object allows application developers to create a numerical list of
menu items on the IP phones. The go-to line support, arrow indicator, and scroll
key support are built into these objects, along with the "Select" and "Done" soft
keys. You can also turn off automatic numbering of menu items using the
style=”none" attribute or use bullets for lists instead of numbers using the
style=”bullet”.
TheText Menu object allows users to navigate the application, by linking HTTP
requests to menu items.
Implementation
The following is how you would implement the Text Menu object.
Note: For all available parameters you can use for the Text Menu object,
and for an explanation of each parameter, see Aastra Telecom’s
"XML Developer’s Guide".
Softkeys:
•
1=Select
•
6=Done
XML Description:
<AastraIPPhoneTextMenu
defaultIndex = "some integer"
destroyOnExit = "yes/no">
<Title>Menu Title</Title>
<MenuItem base ="http://base/">
<Prompt>First Choice</Prompt>
<URI>http://somepage.xml</URI>
<Selection></Selection>
</MenuItem>
<!-Additional Menu Items may be added -->
<!-Additional Softkey Items may be added -->
</AastraIPPhoneTextMenu>
G-6
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML example:
Appendix G
<AastraIPPhoneTextMenu>
<Title>Phone Services</Title>
<MenuItem base = "http://10.50.10.53/">
<Prompt>Traffic Reports</Prompt>
<URI> rss_to_xml.pl</URI>
</MenuItem>
<MenuItem>
<Prompt>Employee List</Prompt>
<URI>employees.xml</URI>
</MenuItem>
<MenuItem base ="">
<Prompt>Weather</Prompt>
<URI>http://10.50.10.52/weather.pl</URI>
</MenuItem>
</AastraIPPhoneTextMenu>
XML Screen Example:
Phone Services
1.Traffic Reports
2.Employee List
3.Weather
Select
Done
Note: The maximum number of items to be included in a Text Menu
object is 15.
41-001160-00, Release 2.1, Rev 04
G-7
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Turning Off Automatic Numbering of Menu Items
When implementing the AastraIPPhoneTextMenu object, you can turn off
automatic numbering of the items in a list using the style=”none" attribute.
XML Description:
You use this attribute as follows.
<AastraIPPhoneTextMenu style=”none”>
<Title>Example</Title>
<MenuItem>
<Prompt>Item 1</Prompt>
<URI>http://somepage.xml</URI>
</MenuItem>
</AastraIPPhoneTextMenu>
XML example:
The following is an example of using the "style=none" attribute with the
AastraIPPhoneText Menu object.
<AastraIPPhoneTextMenu style=”none”>
<Title>Phone Services</Title>
<MenuItem base = "http://10.50.10.53/">
<Prompt>Traffic Reports</Prompt>
<URI> rss_to_xml.pl</URI>
</MenuItem>
<MenuItem>
<Prompt>Employee List</Prompt>
<URI>employees.xml</URI>
</MenuItem>
<MenuItem base ="">
<Prompt>Weather</Prompt>
<URI>http://10.50.10.52/weather.pl</URI>
</MenuItem>
</AastraIPPhoneTextMenu>
G-8
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Screen Example:
Appendix G
The following example shows the items in the Text Menu without the item
numbering.
Phone Services
Traffic Reports
Employee List
Weather
Select
Done
41-001160-00, Release 2.1, Rev 04
G-9
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Using Bullets in Menu Items
When implementing the AastraIPPhoneTextMenu object, you can use bullets to
list items using the style=”bullet" attribute.
XML Description:
You use this attribute as follows.
<AastraIPPhoneTextMenu style=”bullet”>
<Title>Example</Title>
<MenuItem>
<Prompt>Item 1</Prompt>
<URI>http://somepage.xml</URI>
</MenuItem>
</AastraIPPhoneTextMenu>
XML example:
The following is an example of using the "style=bullet" attribute with the
AastraIPPhoneText Menu object.
<AastraIPPhoneTextMenu style=”bullet”>
<Title>Phone Services</Title>
<MenuItem base = "http://10.50.10.53/">
<Prompt>Traffic Reports</Prompt>
<URI> rss_to_xml.pl</URI>
</MenuItem>
<MenuItem>
<Prompt>Employee List</Prompt>
<URI>employees.xml</URI>
</MenuItem>
<MenuItem base ="">
<Prompt>Weather</Prompt>
<URI>http://10.50.10.52/weather.pl</URI>
</MenuItem>
</AastraIPPhoneTextMenu>
G-10
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Screen Example:
Appendix G
The following example shows the items in the Text Menu without the item
numbering.
Phone Services
Traffic Reports
Employee List
Weather
Select
Done
41-001160-00, Release 2.1, Rev 04
G-11
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Text Screen Object (Text Screens)
You use the AastraIPPhoneTextScreen object to display text to the LCD screen
on the IP Phone. The screen text wraps appropriately and can scroll to display a
message longer then four lines.
After implementing this object, text displays to the LCD on the IP phone.
A user can scroll through the screens as required. If you use the
“destroyOnExit” attribute in the XML script, when the user exits the
XML screeens, the screens are destroyed. You can also allow specific text
screens to redisplay for redirection to a new page by using the
“doneAction” attribute and specifying the new page to go to in the XML
script.
Notes:
1. You can use the “destroyOnExit” attribute with any XML object as
required.
2. You can use the “doneAction” attribute with the
AastraIPPhoneTextScreen and AastraIPPhoneFormattedTextScreen
objects only.
3. For all available parameters you can use for the Text Screen object, and
for an explanation of each parameter, see Aastra Telecom’s
"XML Developer’s Guide".
Implementation
The following is how you would implement the Text Screen object.
Softkey:
•
6=Done
XML Description:
<AastraIPPhoneTextScreen destroyOnExit = "yes/no">
<Title>Screen Title</Title>
<Text>The screen text goes here</Text>
</AastraIPPhoneTextScreen>
or
<AastraIPPhoneTextScreen doneAction=”HTTP address”>
<Title>Screen Title</Title>
<Text> The screen text goes here</Text>
</AastraIPPhoneTextScreen>
G-12
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Example 1:
Note: This example displays text that you can scroll through on the LCD
screen. As you scroll the screen, the previous text is destroyed.
XML Screen Example 1:
Screen Object
The screen object can
be implemented
similar to the
Done
41-001160-00, Release 2.1, Rev 04
G-13
Appendix G
<AastraIPPhoneTextScreen destroyOnExit = "yes">
<Title>Screen Object</Title>
<Text>The screen object can be implemented similar to the
firmware info screen. Note that white space is preserved in XML so
the display should word-wrap appropriately. Only three lines can
display at a time.</Text>
</AastraIPPhoneTextScreen>
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Example 2:
<AastraIPPhoneTextScreen doneAction=”http://10.50.10.117/
test.xml”>
<Title>Screen Object</Title>
<Text>For more information about this test, press Done.</Text>
</AastraIPPhoneTextScreen>
Note: This example displays text that you can scroll through on the LCD
screen. As you scroll the screen, and then press DONE (55i, 57i, 57i CT)
or the RIGHT ARROW key (53i), the screen redirects you to the
location specified in the script. After pressing DONE or the RIGHT
ARROW key, the phone checks if a “doneAction” exists in the XML
script. If it does, the screen gets redirected to the location specified. If it
does not exist, then the scrolled screens use the “destroyOnExit”
attribute and destroy the screens.
XML Screen Example 2:
Screen Object
For more information about
this test, press DONE.
Done
TEST
This screen displays the HTTP
screen that you have been
redirected to.
Done
G-14
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Support for Answer and Ignore Softkeys
For a 55i, 57i, and 57i CT, an Administrator can use the “Answer” and “Ignore”
attributes in an XML script to implement this feature. For a 53i, an Administrator
can use the “allowAnswer” attribute with the AastraIPPhoneTextScreen XML
object. Valid values for the “allowAnswer” attribute are “yes” or “no” (default).
For 55i, 57i, and 57i CT:
•
The Answer and Ignore softkeys display on the LCD when the phone has an
incoming call at the same time it receives an XML application.
•
XML applications are destroyed if the phone receives a call after the XML
has been rendered.
When the Answer softkey displays, you can press it to answer the incoming call
without disturbing the current XML application. When you answer the call, the
softkey disappears from the LCD. Pressing the Ignore softkey ignores the
incoming call without disturbing the current XML application.
Implementation (55i, 57i, 57i CT)
Softkeys:
•
•
1=Answer
2=Ignore
41-001160-00, Release 2.1, Rev 04
G-15
Appendix G
When the IP phone receives an XML application (either via a post or an incoming
action URI) while a call is coming into the phone, the user can either answer or
ignore the call with new softkeys that display (55i, 57i, and 57i CT), or press the
left and right arrow keys (53i), without canceling the XML application.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Example:
<SoftKey index="1">
<Label>Answer</Label>
<URI>SoftKey:Answer</URI>
</SoftKey>
<SoftKey index="2">
<Label>Answer</Label>
<URI>SoftKey:Ignore</URI>
</SoftKey>
XML Screen Example:
,
*OHN3MITH
!N8-,APPLICATIONCAN
DISPLAYHEREWHILEACALL
ISCOMINGIN
!NSWER
)GNORE
For 53i:
•
An <Ignore Answer> line displays on the LCD when the phone receives an
incoming call at the same time it receives an XML application.
•
XML applications are destroyed if the phone receives a call after the XML
has been rendered.
When the <Ignore Answer> line displays, you can press the Right Arrow key
(Answer) to answer the incoming call without disturbing the current XML
application. When you answer the call, the <Ignore Answer> line disappears from
the LCD. Pressing the Left Arrow key ignores the incoming call without
disturbing the current XML application.
G-16
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Implementation (53i)
<AastraIPPhoneTextScreen allowAnswer = "yes">
<Title>Screen Object</Title>
<Text>The screen object can be implemented similar to the
firmware info screen. Note that white space is preserved in XML so
the display should word-wrap appropriately. Only three lines can
display at a time.</Text>
</AastraIPPhoneTextScreen>
XML Screen Example:
!N8-,APPLICATIONCANDISPLAY
HEREWHILEACALLISCOMINGIN
,JQRUH
$QVZHU
Text Screen Format Object (for Text Screens)
The AastraIPPhoneFormattedTextScreen object allows you to specify a format
for the text that displays in the LCD window on the phone. Using this object, you
can specify the following for the text that displays:
•
alignment (using the “Align” attribute and specifying right, left, or center )*
•
text size (using the “Line Size” attribute and specifying normal or double
height)*
•
display type (using the “Line” or “Scroll” attributes to specify static or
scrolling)*
*See the AastraIPPhoneFormattedTextScreen structure example on page G-18.
The phone’s LCD screen allows up to a total of 5 lines for displaying text. The
formatted text displays in three distinct blocks in the order it is written in the XML
object:
•
The first block displays text at the top of the LCD window. By default, this
text block is static. This block can contain as many lines as the XML object
specifies and can range from zero (0) up to the LCD screen size.
41-001160-00, Release 2.1, Rev 04
G-17
Appendix G
XML Example:
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
•
The second block displays below the first block. By default, the second text
block displays as scrolling text. This block takes up as many lines as the XML
developer specifies, up to the LCD screen size.
•
The third block displays below the second block. By default, the third block
displays static text, and takes up whatever lines remain blank on the LCD
screen.
Note: Any of the three blocks can be set as static text or scrolling text but
the text displays on a total of 5 lines only. Any lines that display after line
5 are lost.
Using the AastraIPPhoneFormattedTextScreen object, the display truncates a line
after the last word in that line and continues to wrap the text to the next line.The
phone ignores any lines that display after the 5th line on the LCD screen.
AastraIPPhoneFormattedTextScreen Structure
The AastraIPPhoneFormattedTextScreen object describes the structure of the
XML document that you can use to format the text that displays on the phone’s
LCD screen. The default structure of the AastraIPPhoneFormattedTextScreen
object is:
<AastraIPPhoneFormattedTextScreen>
<Line Size="<normal/double>" Align="<right/left/center>">A line
of static text</Line>
<Scroll Height=n>
<Line Size="<normal/double>" Align="<right/left/center>">
Scrolling text</Line>
<Line>Another line of Scrolling Text</Line>
<Line>Yet another scrolling line</Line>
</Scroll>
<Line>Some static footer text</Line>
</AastraIPPhoneFormattedTextScreen>
Note: The text in bold in the above structure indicate the options you can
use for text size (normal, double), alignment (right, left, center), and
scrolling height (from 1 to 5 lines). Setting a scrolling height less than “1”
automatically sets the scroller height to “1”.
G-18
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Example:
<AastraIPPhoneFormattedTextScreen>
<Line Size="double" Align="left">A line of static text</Line>
<Scroll Height=2>
<Line Size="normal" Align="right"> Scrolling text</Line>
<Line>Another line of Scrolling Text</Line>
<Line>Yet another scrolling line</Line>
</Scroll>
<Line>Some static footer text</Line>
</AastraIPPhoneFormattedTextScreen>
XML Screen Examples:
IP Phones 55i, 57i, and 57i CT
A line of static text
This block can scroll
using the down arrow
on the navigation keys.
A line of static text
Done
41-001160-00, Release 2.1, Rev 04
G-19
Appendix G
The following is an example of using the AastraIPPhoneFormattedTextScreen
object with a static line at the top and bottom blocks and 2 scrolling lines in the
middle block.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
IP Phone 53i
G-20
A line of static text
This block can scroll
Note: You can view all 5 lines at once on the 55i, 57i and 57i CT IP
phones. You can view only 2 lines at a time (up to 5 lines) on the 53i IP
phone.
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
UserInput Object (User Input Screens)
For User input screens, you can also create the following:
•
Time and Date Format User input screens. For more information, see “Time
and Date Formats (User Input Screens)” on page G-28.
•
Multiple input fields per AastraIPPhoneInputScreen object. For more
information, see “Multiple Input Fields (User Input Screens)” on page G-31.
Implementation (IP Addresss)
The following is how you would implement the AastraIPPhoneInputScreen
object using an IP Address.
Note: For all available parameters you can use for the
AastraIPPhoneInputScreen object, and for an explanation of each
parameter, see Aastra Telecom’s "XML Developer’s Guide".
Softkeys:
•
•
•
•
•
•
1=Backspace
2=Dot
3=ChangeCase
4=Numeric/Alpha
5=Cancel
6=Done
41-001160-00, Release 2.1, Rev 04
G-21
Appendix G
The AastraIPPhoneInputScreen object allows application developers to create
screens for which the user can input text where applicable. (Line 1 is a title, Line 4
is an input prompt, and Line 5 is an input field). The IP phones support three
parameter types: IP Addresses, Numbers (integers), and Strings. Each parameter
has a URL tag that is used to send information back to the HTTP server. The label
in the parameter tag is appended to the address in the URL tag and sent via HTTP
GET.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Description:
G-22
<AastraIPPhoneInputScreen type = "IP/string/number" password =
"yes/no" destroyOnExit = "yes/no">
<!-password attribute is optional and set to "no" by defaultà
<!-destroyOnExit is optional and "no" by default à
<Title>Title string, usually same as menu title</Title>
<Prompt>Enter IP address or host name</Prompt>
<URL>Target receiving the input</URL>
<Parameter>parameter added to URL</Parameter>
<Default />
<SoftKey index = "1">
<Label> Backspace </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "2">
<Label> Dot </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "3">
<Label> ChangeCase </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "4">
<Label> Numeric/Alpha </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "5">
<Label> Cancel </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "6">
<Label> Done </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
</AastraIPPhoneInputScreen>
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Example:
Appendix G
<AastraIPPhoneInputScreen type = "IP">
<Title>Proxy Server</Title>
<Prompt>Server IP:</Prompt>
<URL>http://10.50.10.53/script.pl</URL>
<Parameter>proxy</Parameter>
<Default></Default>
<AastraIPPhoneInputScreen>
XML Screen Example:
Proxy Server
Server IP:
Backspace
Dot
41-001160-00, Release 2.1, Rev 04
Cancel
Done
G-23
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Implementation (Number)
The following is how you would implement the UserInput object using Numbers.
Softkeys:
•
1=Backspace,
•
5=Cancel,
•
6=Done
XML Example:
<AastraIPPhoneInputScreen type = "number">
<Title>Proxy Port</Title>
<Prompt>Port:</Prompt>
<URL>http://10.50.10.53/script.pl</URL>
<Parameter>port</Parameter>
<Default>5060</Default>
<AastraIPPhoneInputScreen>
XML Screen Example:
Proxy Port
Port: 5060
Backspace
G-24
Cancel
Done
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Implementation (String)
Softkeys:
•
1=Backspace,
•
2=Dot,
•
3=Tri-Mode key,
•
4=Nextspace,
•
5=Cancel,
•
6=Done
XML Example:
<AastraIPPhoneInputScreen type = "string" password = "yes">
<Title>SIP Settings</Title>
<Prompt>Enter something</Prompt>
<URL>http://10.50.10.53/script.pl</URL>
<Parameter>passwd</Parameter>
<Default></Default>
<AastraIPPhoneInputScreen>
XML Screen Example::
SIP Settings
Enter Password:
******
Backspace
Dot
ABC
Nextspace
Cancel
Done
Note: In the above example, if the user entered 12345, then the URL sent
back to the server is http://10.50.10.53/script.pl?passwd=12345.
41-001160-00, Release 2.1, Rev 04
G-25
Appendix G
The following is how you would implement the UserInput object using Strings in
XML.
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
XML Softkey for Special Characters
(User Input Screens for 55i, 57i, and 57i CT only)
In Release 2.1, the IP Phone can dynamically receive a Symbol List when it
receives the AastraIPPhoneInputScreen XML object. You can have a single
symbol specified for the softkey, or you can have a list of symbols. When there is
only one symbol in the list, the symbol displays with no delay. When there is a list
of symbols, you can keep pressing the symbol softkey to cycle through the list of
symbols to select the one you want to use.
To display a list of customized symbols to the phone’s softkey, the server must
include the list of characters in the URI field of the XML softkey script. The URI
must be in the format:
SymbolList=”<Symbol List content>”
The content of the Symbol List must be encapsulated by quotes. You can specify
multiple symbols in one URI. For example, the SymbolList="@#” specifies the
@ and # symbols.
Note: You can have multiple Symbol List softkeys with different lists of
symbols. The maximum length of the data in a Symbol List is 230
characters.
There are some special characters that needed to be encoded due to XML
limitations. The following table specifies these characters.
Symbol
XML Encoding
single quote (‘)
&apos;
double quote (“)
&quot;
greater-than sign (>)
&gt;
less-than sign (<)
&lt;
ampersand (&)
&amp;
The following is an example XML URI using the characters in the table above:
SymbolList="@#&amp;&gt;&lt"
The Symbol List content for this URI is @, #, &, >, <.
G-26
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Implementation
Appendix G
Softkeys:
•
1 = <Single Symbol or Symbol List>
XML Softkey Example:
<SoftKey index="1">
<Label>Symbols</Label>
<URI>SoftKey:SymbolList="@#=&amp;"</URI>
</SoftKey>
XML Object and Softkey Example:
<AastraIPPhoneInputScreen type = "IP">
<Title>Email</Title>
<SoftKey index="1">
<Label>Symbols</Label>
<URI>SoftKey:SymbolList="@"</URI>
</SoftKey>
<SoftKey index = "2">
<Label> Backspace </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<SoftKey index = "3">
<Label> Dot </Label>
<URI>SoftKey:Exit</URI>
</Softkey>
<Prompt>Email Address:</Prompt>
<URL>http://myserver.com/myscript.com</URL>
<Parameter>email</Parameter>
<Default></Default>
<AastraIPPhoneInputScreen>
XML Screen Example:
%MAIL
%MAIL!DDRESS
3YMBOLS
"ACKSPACE
$OThv
41-001160-00, Release 2.1, Rev 04
G-27
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Time and Date Formats (User Input Screens)
The AastraIPPhoneInputScreen object allows you to specify US ( (HH:MM:SS
am/pm and MM/DD/YYYY) or International (HH:MM:SS and DD/MM/YYYY)
time/date formats for an XML user input screen on the IP phone.
Note: You use this time/date format in an XML script that displays in an
XML window. This time/date format does NOT affect the time/date
format configured under the Options Menu on the phone.
Using this AastraIPPhoneInputScreen object, you can specify the following
attributes for date/time format to create the user input screen:
•
“timeUS”
•
“timeInt”
•
“US Date”
•
“Int Date”
You can use these XML attributes in an application that requires the user to
specify a time or a date, for example, when scheduling a meeting. The user could
press a softkey that gets the XML script asking you to enter a time/date. This time/
date is then forwarded to a script that schedules the meeting or reports a conflict.
XML Examples:
The following example illustrates the AastraIPPhoneInputScreen object using the
time/date attributes.
United StatesTime
<AastraIPPhoneInputScreen type="timeUS">
<Title>US Time</Title>
<Prompt>Enter Current Time:</Prompt>
<Parameter>Time</Parameter>
</AastraIPPhoneInputScreen>
G-28
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
IP Phones 55i, 57i/57i CT
IP Phone 53i
Appendix G
Enter Current Time:
12:00:00am
US Time
Enter Current Time:
12:00:00am
=Cancel
=Enter
Cancel
Done
International Time
<AastraIPPhoneInputScreen type="timeInt">
<Title>Int Time</Title>
<Prompt>Enter Current Time:</Prompt>
<Parameter>Time</Parameter>
<Default>14:23:22</Default>
</AastraIPPhoneInputScreen>
IP Phones 55i, 57i/57i CT
IP Phone 53i
Enter Current Time:
12:23:22
Int Time
Enter Current Time:
14:23:22
=Cancel
=Enter
Cancel
Done
Note: If you don’t specify a time, the XML script uses the following
default values:
- 12:00:00am (US)
- 00:00:00 (International)
41-001160-00, Release 2.1, Rev 04
G-29
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
United States Date
<AastraIPPhoneInputScreen type="dateUS">
<Title>US Date</Title>
<Prompt>Enter Birthday:</Prompt>
<Parameter>Date</Parameter>
<Default>12/22/1980</Default>
</AastraIPPhoneInputScreen>
IP Phones 55i, 57i/57i CT
IP Phone 53i
Enter Birthday:
12/22/1980
US Date
Enter Birthday:
12/22/1980
=Enter
=Cancel
Cancel
Done
International Date
<AastraIPPhoneInputScreen type="dateInt">
<Title>Int Date</Title>
<Prompt>Enter Birthday:</Prompt>
<Parameter>Date</Parameter>
</AastraIPPhoneInputScreen>
IP Phones 55i, 57i/57i CT
IP Phone 53i
Enter Birthday:
26/5/2006
Int Date
Enter Birthday:
26/5/2006
=Cancel
=Enter
Cancel
Done
G-30
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Multiple Input Fields (User Input Screens)
You can have multiple input fields per AastraIPPhoneInputScreen object.The
following specifications apply to this feature:
•
Multiple input fields are applicable to 55i, 57i, and 57i CT IP phones only.
•
Each AastraIPPhoneInputScreen object can support up to 6 input fields.
•
Each input field supports its own set of custom softkeys (these take
precedance over any softkeys configured outside of the <InputField> tags.
•
The phone treats softkey information specified outside of the <InputField>
tags as a default value.
•
Each AastraIPPhoneInputScreen object supports only 1 URL.
The following tags support this feature.
Tags for Multiple Input Fields
New tags within the <InputField>
tags:
Note: This tag supports the type, <Prompt>
<Parameter>
password, and editable
<Default>
attributes. If specified, they
<Softkey>
override the default values
provided in the root tag.
Note: These tags override the values
specified outside of the <InputField>
tags.
<InputField>.......</InputField>
<Selection>.......</Selection>
41-001160-00, Release 2.1, Rev 04
Any data specified between the
<Selection> tags is appended to the
URI in the form Selection = <DATA>.
G-31
Appendix G
Note: If you don’t specify a date, the XML script uses the current date in
the specified format.
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
You use the following attributes to create multiple input fields using the
AastraIPPhoneInputScreen object.
New AastraIPPhoneInputScreen Attributes
defaultIndex
Allows you to set an integer value from 1 - 6 that specifies which
input field the edit cursor starts in. Default is 1.
displayMode
Allows you to set a specific display mode for the screen: “normal”
or “condensed”.
Default is “normal” mode.
Normal Mode - Prompts and inputs each appear on separate lines
on the display. The user can scroll through the lines.
Notes:
1. An <InputField> tag with a type set to “empty” creates two blank
lines in “normal” mode.
2. All inputs fields are left justfied in “normal” mode.
Condensed Mode - Prompts and inputs appear on the same line
(up to 5 inputs on a single screen).
Notes:
1. Title tag wrapping limits the number of fields per screen to 1 or 3
in condensed mode.
2. An <InputField> tag with a type set to “empty” creates a blank
line in “condensed” mode.
Example
The following is an example AastraIPPhoneInputScreen script using the multiple
input field feature:
<AastraIPPhoneInputScreen type="string">
<Title>Test</Title>
<URL>http://10.50.10.117/test.pl</URL>
<Default/>
<InputField>
<Prompt>Name:</Prompt>
<Parameter>name</Paramter>
<Default>Robert</Default>
<SoftKey index="3">
<Label>NameDone</Label>
<URI>Softkey:Submit</URI>
</SoftKey>
G-32
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Appendix G
</InputField>
<InputField type="timeUS">
<Prompt>Time:</Prompt>
<Parameter>time</Paramter>
<Default>10:50:24AM</Default>
</InputField>
<InputField type="dateUS>
<Prompt>Date:</Prompt>
<Parameter>date</Paramter>
<Default>01/24/07</Default>
<SoftKey index="5">
<Label>DateDone</Label>
<URI>Softkey:Submit</URI>
</SoftKey>
</InputField>
</AastraIPPhoneInputScreen>
Posting the above AastraIPPhoneInputScreen XML script displays the following
screens on the IP phone.
Screen 1
Test
Name:
Robert |
Time:
10:50:24 AM
____________________
Cursor
- NameDone
Screen 1 Note: Notice that the cursor is active within the first element field and
that the phone is displaying the InputField #1 softkey.
41-001160-00, Release 2.1, Rev 04
G-33
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Scolling down changes to the next input field.
Screen 2
Test
Name:
Robert
Time:
10:50:24 AM
____________________
Cancel Done -
Screen 2 Note: Notice that the softkeys change to reflect the new input type,
timeUS.
Scrolling down again goes to the next page of inputs.
Screen 3
Test
Date
11/24/07
____________________
DateDone -
Screen 3 Note: Notice that the softkeys change again to reflect the current input
item on the screen (Date).
G-34
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Condensed Mode Screen
Screen 4
Test
Name: Robert |
Time: 10:50:24 AM
Date: 11/24/07
____________________
- NameDone
41-001160-00, Release 2.1, Rev 04
G-35
Appendix G
If you use the attribute “displayMode = “condensed” in the root tag (Screen 4),
the display changes to have prompt and inputs on the same line. The behavior of
the screens using “condensed” mode is the same as Screens 1 through 3 but
without the scrolling.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Directory Object (Directory List Screen) (57i only)
The Directory object allows you to browse an online directory in real time. It
displays an automatically numbered list of contacts. By selecting a contact with
the cursor, the contact can be dialed directly by pressing the "Dial" softkey or
picking up the receiver. The Directory object has the optional softkeys of
"Previous" and "Next" which can be linked to other XML objects.
Implementation
The following is how you would implement the Directory object in XML.
Note:
1. For all available parameters you can use for the Directory object, and
for an explanation of each parameter, see Aastra Telecom’s
"XML Developer’s Guide".
2.
If the URI entry contains a "?" the phone appends an "&" instead.
Softkeys:
• 1=Dial,
• 6= Done,
• 2=Previous (optional),
• 5=Next (optional)
XML Description:
<AastraIPPhoneDirectory destroyOnExit="no" next="uri"
previous="uri">
<!-Attributes are optionalà
<Title>Directory Title</Title>
<Menu Item>
<Prompt>Contact Name</Prompt>
<URI>number</URI>
</Menu Item>
<!-Additional Menu Items may be added -->
</AastraIPPhoneDirectory>
G-36
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Example:
Appendix G
<AastraIPPhoneDirectory next="more.xml" previous="back.xml">
<Title>My Directory</Title>
<MenuItem>
<Prompt>57i - John Doe 1</Prompt>
<URI> 10.50.10.49</URI>
</MenuItem>
<MenuItem>
<Prompt>53i - John Doe 2</Prompt>
<URI>4326</URI>
</MenuItem>
<MenuItem>
<Prompt>57i CT - John Doe 3</Prompt>
<URI>9982691234</URI>
</MenuItem>
</AastraIPPhoneDirectory
XML Screen Example::
My Directory (1/6)
1. 480i John Doe 1
2. 9133i John Doe 2
3. 480iCT John Doe 3
Dial
Previous
Next
Cancel
Note: The maximum number of items to be included in a Directory
object is 15 per page. In this example, there are six pages.
41-001160-00, Release 2.1, Rev 04
G-37
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Status Message Object (Idle Screen)
The IP phones support an XML AastraIPPhoneStatus object for displaying
status messages on a single designated line on the phone’s idle screen. The
messages display when the server pushes XML information to the phone.
The 57i/57i CT phones display messages on the second line in the phone window.
(where “No Service” would display if there was no service. If there is no service
on the phone, the “No Service” message overrides the XML object message). The
53i phone displays messages on the first line (overriding the DisplayName). The
phone truncates long messages that are wider then the phone screen.
If the phone receives multiple messages, the first message received displays first
and the remaining messages scroll consecutively one at a time. Messages remain
displayed until they are removed (by the server) or the phone reboots. The
AastraIPPhoneStatus object feature is always enabled.
Note: You can set the amount of time, in seconds, that a message displays
to the phone before scrolling to the next message. For more information
about this feature, see “Scroll Delay Option (configurable via config files
and Aastra Web UI only)” on page G-58.
AastraIPPhoneStatus Structure
The AastraIPPhoneStatus object describes the structure of the XML document
that you can use to send status messages to the phone. The basic structure of the
AastraIPPhoneStatus object is:
<AastraIPPhoneStatus>
<Session>My session ID</Session>
<Message index="Msg index">Message</Message>
<! -- Additional status messages may be added under new Message tags-->
<AastraIPPhoneStatus/>
The ”My Session ID” attribute must be unique to the application sending the
XML object to the phone. The application generates the session ID, which could
be a combination of letters and numbers. There is a maximum of one <Session>
tag per PhoneStatus object, so the <Session> tag is optional.
G-38
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Examples
<AastraIPPhoneStatus>
<Session>abc12345</Session>
<Message index="3">Server side call forwarding disabled</Message>
<AastraIPPhoneStatus/>
In this example, the AastraIPPhoneStatus object sends the default behavior with
the status message (i.e., the status message is added to the scroll list).
Example 2: You can also use the AastraIPPhoneStatus object to remove status
messages from the display, by setting an empty tag for the <Message index> tag.
The following example removes the status message that was posted to the phone
in Example 1.
<AastraIPPhoneStatus>
<Session>abc12345</Session>
<Message index="3"/>
<AastraIPPhoneStatus/>
41-001160-00, Release 2.1, Rev 04
G-39
Appendix G
Example 1: The following is an example of using the AastraIPPhoneStatus
object:
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Execute Commands Object (for executing XML commands)
An AastraIPPhoneExecute object on the IP phones allows the phone to execute
commands using XML. The phones support the following execute object
commands:
•
Reset - This command waits until the phone is idle and then executes a reset.
You can use this command in an XML script to enable the server to force
phone firmware changes and/or for troubleshooting purposes.
•
NoOp - This command has no affect on the IP phone. It is made up of a blank
URI. You can use this feature when you need to press a key on the phone to
access a feature, and it is not necessary to display anything.
•
FastReboot - This command allows an administrator to perform a fast reboot
of the IP phone when required.
Note: For FastReboot commands, you must set the XML push server list
in the Aastra Web UI from where the XML HTTP post is being sent.
•
XML Softkey/Programmable Key LED Behavior - The URI=”Led:
<softkey or programmable key type>=<execute command>”/ controls the
behavior of XML softkey or programmable key LEDs. The softkey or
programmable key must be configured for XML before you enable this
feature.
The following paragraphs describe the AastraIPPhoneExecute object and the
commands you can use with this object.
AastraIPPhoneExecute Object Structure
The AastraIPPhoneExecute object describes the structure of the XML document
that you can use to send a command to the phone. It delivers multiple execution
requests to the phone. The basic structure of the AastraIPPhoneExecute object is:
<AastraIPPhoneExecute>
<ExecuteItem URI ="the URL or URI to be executed"/>
<! -- Additional execution items may be added under new ExecuteItem tag-->
</AastraIPPhoneExecute>
G-40
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Using the Reset Command
The following example shows an AastraIPPhoneExecute object using the Reset
command:
<AastraIPPhoneExecute>
<ExecuteItem URI="Command: Reset"/>
</AastraIPPhoneExecute>
Note: If you specify a command as a URI attribute (instead of a URL),
the keyword "Command" must be prepended in the value of the URI
attribute so that the phone recognizes it as a URI attribute value. If you
enter a URI and leave out the “Command” keyword, the phone interprets
the value in the URI attribute as a URL containing network resources.
The following example shows the AastraIPPhoneExecute object using a URL:
<AastraIPPhoneExecute>
<ExecuteItem URI="http://aastraserver/message.xml"/>
</AastraIPPhoneExecute>
When the phone receives this object, it displays the specified XML URI page.
Using the NoOp Command
You can use the AastraIPPhoneExecute object as an object to create a blank
display (it has no affect on the IP phone). It is made up of a blank URI. You can
use this feature when you need to press a key on the phone to access a feature, and
it is not necessary to display anything. You can also use the
AastraIPPhoneExecute object and this command with other objects in an XML
script.
The following example shows an AastraIPPhoneExecute object using a blank
URI:
<AastraIPPhoneExecute>
<ExecuteItem URI=””/>
<AastraIPPhoneExecute>
41-001160-00, Release 2.1, Rev 04
G-41
Appendix G
The <ExecuteItem URI =""/> tag can be entered with the command the phone
should execute. Upon receiving an AastraIPPhoneExecute object, the phone
begins executing the URL or URI specified.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Using the FastReboot Command
Using an XML post, the FastReboot feature forces a phone to reboot in the idle
state. It does not check for new firmware and only downloads language packs if
there is a change in the supported filenames of the language packs. The phone
DOES do a DHCP lookup on every “fast reboot”. It also only downloads the
Directory files if the names have changed.
Note: For FastReboot commands, you must set the XML push server list
in the Aastra Web UI from where the XML HTTP post is being sent.
The following example shows an AastraIPPhoneExecute object using the
FastReboot command.
<AastraIPPhoneExecute>
<ExecuteItem URI=“Command:FastReboot”/>
</AastraIPPhoneExecute>
XML Softkey or Programmable Key LED Behavior Command
You can control the behavior of XML softkey or programmable key LEDs using
the command URI=”Led: <softkey or programmable key type>=<execute
command>”/ with the AastraIPPhoneExecute object.
This LED feature is applicable to XML softkeys (top or bottom), programmable
keys, and expansion module softkeys. The softkey or programmable key must be
configured for XML before you enable this feature.
The following table describes the behaviors you can assign to the XML key
LEDs, and the attribute you enter in the AastraIPPhoneExecute script.
G-42
LED Behavior
XML Attribute
on
URI = “Led: <softkey type>= on”/
off
URI = “Led: <softkey type>=off”/
fastFlash
URI = “Led: <softkey type>=fastflash”/
slowFlash
URI = “Led: <softkey type>=slowflash”/
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
<AastraIPPhoneExecute>
<ExecuteItem URI=”Led:
<ExecuteItem URI=”Led:
<ExecuteItem URI=”Led:
<ExecuteItem URI=”Led:
</AastraIPPhoneExecute>
topsoftkey20=on”/>
softkey1=off”/>
prgkey2=fastflash”/>
expmod2 key20=slowflash”/>
Notes:
1.
Using the Aastra Web UI, you must set the XML push server list
from where the XML HTTP post is being sent.
2.
The LED states specified in the AastraIPPhoneExecute script are
not saved after a reboot.
41-001160-00, Release 2.1, Rev 04
G-43
Appendix G
The command for LED control is sent using the XML HTTP post from one of the
XML push server lists. The following example shows an XML LED command in
an AastraIPPhoneExecute script.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Dynamic Configuration Object (to push a configuration to the phone)
The IP phones provide an XML feature that allows you to make configuration
changes to the phone that take affect immediately, without having to reboot the
phone. This feature involves creating XML scripts that push the changed
configuration parameter(s) from the server to the IP phones.
You can use the AastraIPPhoneConfiguration object in the XML scripts to
change configuration parameters or configure new parameters. However, since the
IP phone does not save new parameters created in XML scripts to the local.cfg
file, when the phone reboots, it does not save the new parameters on the phone. In
order for the phone to apply new configuration parameters, you have to enter the
parameters via the user interfaces (Telephone User Interface, Web User Interface,
or configuration files), or reapply the new parameters using the XML scripts after
every boot.
Specific configuration parameters are dynamic on the phone when pushed from
XML scripts on the server. See “Dynamic Configuration Parameters” on
page G-46 for more information about dynamic configuration parameters.
AastraIPPhoneConfiguration Object Structure
The AastraIPPhoneConfiguration object describes the structure of the XML
document that you can use to push the configuration to the IP phone. The basic
structure of the AastraIPPhoneConfiguration object is:
<AastraIPPhoneConfiguration>
<ConfigureItem>
<Parameter>Parameter name</Parameter>
<Value>Parameter value</Value>
</ConfigureItem>
<ConfigureItem>
<Parameter>Parameter name</Parameter>
<Value>Parameter value</Value>
</ConfigureItem>
.
.
.
<AastraIPPhoneConfiguration>
G-44
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
XML Example:
The following is an example of an XML configuration script that creates a softkey
you can press on the IP phone to push the configuration from the server to the
phone:
<AastraIPPhoneConfiguration>
<ConfigureItem>
<Parameter>softkey1 label</Parameter>
<Value>John Doe</Value>
</ConfigureItem>
<ConfigureItem>
<Parameter>softkey1 type</Parameter>
<Value>speeddial</Value>
</ConfigureItem>
<ConfigureItem>
<Parameter>softkey1 value</Parameter>
<Value>5551234</Value>
</ConfigureItem>
</AastraIPPhoneConfiguration>
41-001160-00, Release 2.1, Rev 04
G-45
Appendix G
Note: You can add more configuration items as applicable. There is a
limit of 5000 bytes (less than 5k) on the size of XML configuration
objects.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Dynamic Configuration Parameters
G-46
The following table identifies which configuration parameters change
dynamically when using XML configuration scripts to push the configuration to
the phone.
Dynamic Configuration Parameters
softkeyN type*
line7 ring tone
softkeyN label*
line8 ring tone
softkeyN value*
line9 ring tone
softkeyN line*
suppress dtmf playback
softkeyN states*
redial disabled**
prgkeyN type*
call transfer disabled
prgkeyN name*
conference disabled
prgkeyN value*
directory disabled**
prgkeyN line*
callers list disabled**
live dialpad
options password enabled
tone setv
time server disabled
ring tone
time reserved
audio mode
dst config
language
time server1
ringback timeout
time server2
headset tx gain
time server3
headset sidetone gain
time format
handset tx gain
date format
handset sidetone gain
time zone name
handsfree tx gain
time zone code
line1 ring tone
time zone minutes
line2 ring tone
dst minutes
line3 ring tone
dst start relative date
line4 ring tone
dst start month
line5 ring tone
dst start day
line6 ring tone
dst start week
dst start hour
sip intercom line
dst end relative date
sip allow auto answer
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Dynamic Configuration Parameters
sip silence suppression
dst end day
sip send mac
dst end week
sip send line
dst end hour
xml application URI
tftp server
xml application title
alternate tftp server
xml beep notification
use alternate tftp server
action uri registered
admin password
action uri incoming
user password
action uri outgoing
sip nat ip
action uri onhook
sip nat port
action uri offhook
sip dial plan
action uri startup
sip dial plan terminator
play a ring splash
sip digit timeout
map redial key to
sip blf subscription period
map conf key to
sip registration retry timer
download protocol
sip forward number
ftp server
sip forward mode
ftp username
sip ring number
ftp password
sip vmail
http server
sip dtmf method
http path
sip lineN forward number
directory 1***
sip lineN forward mode
directory 2***
sip lineN ring number
directory script
sip lineN vmail
auto resync time
sip lineN dtmf method
auto resync mode
Appendix G
dst end month
sip intercom type
sip intercom prefix code
sip intercom mute mic
*Changes to subscriptions (BLF or BLA) require a reboot.
**This parameter is dynamic so a user can’t access it or add to it. However, you need to
reboot the phone to clear the list.
*** You need to reboot the phone to download new directories.
41-001160-00, Release 2.1, Rev 04
G-47
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Image Objects (55i, 57i/57i CT only)
The 55i and 57i/57i CT IP phones provide an XML feature that allows you to load
images in XML applications that display to the LCD screen. The following table
describes the three types of image objects that you can use in an XML script:
XML Image Object
Image Type
Description
AastraIPPhoneImageScreen
Standalone Bitmap
Image
Displays a single bitmap image
according to alignment, height, and
width specifications.
AastraIPPhoneImageMenu
Menu Image
Displays a bitmap image as a menu.
Menu selections are linked to keypad
keys (0-9, *, #).
Press 0 - Company Info
Press 1 - Stock Market
Press # - Weather
This entire box is
a bitmap image.
Done
AastraIPPhoneTextMenu (Icon Menu)
Icon Menu Image
Displays a small icon before each item
in the menu.
IconMenu
1. Voicemail
2. Horoscope
Select
Done
G-48
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
You can include images with an XML object in two ways:
Using pixel data stored with specified tags
•
Using an internal bitmap loaded via a specified URI
Note: The actual resolution of the image on the LCD screen is dependent
on the phone model. The 55i screen has a resolution of 144 x 75 pixels.
The 57i/57i CT screens have a resolution of 144 x 128 pixels. However,
the display of the image is limited to 40 x 144 pixels high.
The following paragraphs describe each of the image objects and how you can use
them in the XML scripts.
AastraIPPhoneImageScreen Object
The AastraIPPhoneImageScreen object displays an image as a single bitmap
image on the LCD screen. You can specify the placement of the image on the
screen by setting the following attributes:
•
verticalAlign
•
horizontalAlign
•
height
•
width
The image is specified as a series of hexadecimal characters. Two hex characters
map to one byte of pixel data, where each bit represents a pixel. The image data
describes the bitmap from left to right and top to bottom. The data is padded on
an 8-bit boundary, so if the height and width do not match the pixel information,
then the image will not display correctly. The character strings map to the middle
and four corners of the screen. If desired, you can specify an integer as an absolute
pixel for customized displays.
Note: A special URI of "Image:Logo" is used to load the current logo
bitmap for the phone (Aastra or branded). In this case, the height and
width can be ignored.
41-001160-00, Release 2.1, Rev 04
G-49
Appendix G
•
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Example:
The XML script for the AastraIPPhoneImageScreen object is as follows:
<AastraIPPhoneImageScreen>
<Image verticalAlign = "top,middle,bottom,'pixel'",
horizontalAlign = "left,middle,right,'pixel'"
height="'integer'", width="'integer'">
FF00F800FF00FFFFFFFFFFFF00FF00FF00FFF8F200
</Image>
<!-vertical and horizontal default to "middle" ->
<!-height and width must match the image data ->
</AastraIPPhoneImageScreen>
Note: This object supports the destroyOnExit attribute.
XML Screen Example:
G-50
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
AastraIPPhoneImageMenu
•
verticalAlign
•
horizontalAlign
•
height
•
width
The image is specified as a series of hexadecimal characters. Two hex characters
map to one byte of pixel data, where each bit represents a pixel. The image data
describes the bitmap from left to right and top to bottom. The data is padded on
an 8-bit boundary, so if the height and width do not match the pixel information,
then the image will not display correctly. The character strings map to the middle
and four corners of the screen. If desired, you can specify an integer as an absolute
pixel for customized displays.
XML Example:
The XML script for the AastraIPPhoneImageMenu object is as follows:
<AastraIPPhoneImageMenu>
<Image verticalAlign = "top,middle,bottom,'pixel'",
horizontalAlign = "left,middle,right,'pixel'"
height="'integer'", width="'integer'">
FF00F800FF00FFFFFFFFFFFF00FF00FF00FFF8F200
</Image>
<!-Base attribute is optional-->
<URIList base = "http://someserver/">
<URI key = "0">link1.php</URI>
<URI key = "1">link2.php</URI>
<URI key = "#">link3.php</URI>
</URIList>
</AastraIPPhoneImageMenu>
41-001160-00, Release 2.1, Rev 04
G-51
Appendix G
The AastraIPPhoneImageMenu object allows you to use a bitmap image to
display as a menu. Each menu item is linked to a keypad key (0-9, *, #). You can
use this type of image object when you want to display menu choices as a
non-ASCII character set or with pictures only. You can specify the placement of
the image on the screen by setting the following attributes:
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
Each URI is appended to the “base” URI if one exists. The default softkey is a
“Done” key at the bottom right position. It is a parse error if two URIs specify the
same index.
Note: This object supports the destroyOnExit attribute.
XML Screen Example:
This entire box is
a bitmap image.
Press 0 - Company Info
Press 1 - Stock Market
Press # - Weather
Done
G-52
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
AastraIPPhoneTextMenu (Icon Menu)
XML Example:
The XML script for the AastraIPPhoneTextMenu (Icon Menu) object is as
follows:
<AastraIPPhoneTextMenu>
<Title> Icon Menu </Title>
<MenuItem base = http://someserver/,
icon="1">
<Prompt> Voicemail </Prompt>
<URI>scripts/voicemail.php</URI>
</MenuItem>
<MenuItem icon="2">
<Prompt> Horoscope</Prompt>
<URI> scripts/horoscope.php </URI>
</MenuItem>
<IconList>
<Icon index = "1"> Icon:Envelope </Icon>
<Icon index = "2"> FFFF0000FFFF0000 </Icon>
</IconList>
</AastraIPPhoneTextScreen>
The “icon=1” attribute in the above example tells the phone to display the icon
specified in the IconList called “<Icon index = “1”> Icon:Envelope </Icon>”.
For more information about the “IconList”, see “Using the <IconList>” on
page G-54.
41-001160-00, Release 2.1, Rev 04
G-53
Appendix G
The AastraIPPhoneTextMenu (Icon Menu) object is identical to the “Text Menu
Object (Menu Screens)” described on page G-6, except a small icon image
appears after the menu number and before the text item. The Text Menu object
allows application developers to create a numerical list of menu items on the IP
phones. The AastraIPPhoneTextMenu (Icon Menu) object allows users to
navigate the application, by linking HTTP requests and icons to menu items.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Screen Example:
IconMenu
1. Voicemail
2. Horoscope
Select
Done
Using the <IconList>
You can incorporate the use of an <IconList> attribute in the XML script to
define the images you will use with the AastraIPPhoneTextMenu object. After
you define the icons in the <IconList>, you can then call those icons as you need
them throughout the script. This also allows you to assign the icons to softkeys on
the phone.
You can load images in the <IconList> in two ways:
•
By specifying the image after a special prefix called “Icon:”
For example:
<IconList>
<Icon index = “1”> Icon:Envelope </Icon>)
<IconList>
•
By specifying the image in hexidecimal format
For example:
<IconList>
<Icon index = “2”> FF00F3 </Icon>)
<IconList>
G-54
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
You can use one or both ways to load images within the same XML script. The
softkey icons display at the edge of the screen. Any XML object that supports
softkeys can support the optional <IconList> tag.
XML Example:
The following example illustrates the use of the <IconList> attribute to create
images for softkey prompts.
<AastraIPPhoneTextScreen>
<Title> Directory List </Title>
<Text> Welcome to the Directory. </Text>
<SoftKey index = "4" icon="2">
<Label> Listing </Label>
<URI> http://server/page.php </URI>
</SoftKey>
<SoftKey index = "3" icon="1">
<Label> Exit </Label>
<URI> http://server/otherpage.php </URI>
</SoftKey>
<IconList>
<Icon index = "1"> FF00F3 </Icon>
<Icon index = "2"> Icon:ArrowRight </Icon>
</IconList>
</AastraIPPhoneTextScreen>
41-001160-00, Release 2.1, Rev 04
G-55
Appendix G
Note: For a list of icons that are internal to the IP phone when specifying
the “Icon:<uri name>”, see the section “IP Phone Internal Icon Images”
on page G-56.
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
XML Screen Example:
DirectoryList
Welcometothe
Directory
ArrowRight Icon
Exit Icon
Listing
Exit
IP Phone Internal Icon Images
The IP phones have internal icon images you can use when specifying the
“Icon:<uri name>” attribute in the <IconList>. The following table lists the
internal icons you can specify.
URI Name
Displays this:
PhoneOnHook
PhoneOffHook
PhoneRinging
DND
None
ArrowRight
ArrowLeft
Speaker
G-56
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
URI Name
Displays this:
Appendix G
ArrowUp
ArrowDown
ArrowsUpandDown
FilledCircle
EmptyCircle
Envelope
Prohibit
Square
Ellipse
TailArrowUp
TailArrowDown
41-001160-00, Release 2.1, Rev 04
G-57
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
Attributes/Options to Use with XML Objects
Beep Attribute
(configurable via XML objects, config files, or Aastra Web UI)
You can enable or disable a “Beep”option to indicate a status on the phone using
the Status Message object (AastraIPPhoneStatus), the configuration files, or the
Aastra Web UI.
Note: For enabling/disabling a status message beep using the
configuration files and the Aastra Web UI, see Chapter 5, the section,
“Enabling/Disabling a Beep for Status Message Displays” on page 5-200.
When the phone receives a status message, the BEEP notifies the user that the
message is displaying. The following attribute in the AastraIPPhoneStatus object
enables/disables the BEEP from being heard:
< AastraIPPhoneStatus Beep="yes|no">
(case sensitive)
This attribute is optional. If notification is required, the attribute must be in the
ROOT. If the BEEP attribute is set to "yes" (i.e. Beep="yes") then it is an
indication to the phone to sound a beep when it receives the object. If the Beep
attribute is set to "no" (i.e. Beep="no") or not present, then the default behavior is
no beep is heard when the object arrives to the phone.
Note: The value set in the configuration files and Aastra Web UI override
the attribute you specify for the AastraIPPhoneStatus object.
Scroll Delay Option
(configurable via config files and Aastra Web UI only)
The IP phones support a scroll delay option that allows you to set the time delay,
in seconds, between the scrolling of each status message on the phone. The default
time is 5 seconds for each message to display before scrolling to the next message.
You can configure this option via the configuration files or the Aastra Web UI.
Changes are dynamic and apply to the phone immediately.
Note: For more information about setting the scroll delay option, see
Chapter 5, the section, “Scroll Delay Option for Status Messages” on
page 5-201.
G-58
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
The XML “Timeout” attribute allows you to specify a timeout value for the LCD
screen display. You must use the “Timeout” aattribute in the ROOT. When the
phone receives an XML object with this attribute, it overrides the default 45
second timeout specified for custom applications. Setting the “Timeout” attribute
to zero (0) disables this feature.
XML Example:
The following example illustrates the use of the “Timeout” attribute with the
AastraIPPhoneFormattedTextScreen object. The result would cause the LCD
screen to timeout in 30 seconds.
<xs:element name="AastraIPPhoneFormattedTextScreen">
<xs:attribute name="Beep" default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="DestroyOnExit" default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:AastraIPPhoneFormattedTextScreen Timeout= “30" default = “45”>
<xs:simpleType>
<xs:restriction base="xs:number/>
</xs:simpleType>
</xs:attribute>
41-001160-00, Release 2.1, Rev 04
G-59
Appendix G
Timeout Attribute
(configurable via XML objects only)
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
LockIn Attribute
(configurable via XML objects only)
The XML “LockIn” attribute allows you to specify whether or not the
information on the LCD screen stays displayed when other events occur (such as
pressing buttons on the keypad).
Note: This attribute is ignored during incoming calls. If this attribute is
set, and the phone receives an incoming call, the LCD screen exits the
XML information and displays the information about the incoming call.
You must use the “LockIn” aattribute in the ROOT. The settings for the LockIn
attribute are “Yes” for enabled, and “No” for disabled.
XML Example:
The following example illustrates the use of the “LockIn” attribute with the
AastraIPPhoneFormattedTextScreen object. The result would cause the LCD
screen to lock in the display of the XML information even if other events occur
(except for an incoming call).
<xs:element name="AastraIPPhoneFormattedTextScreen">
<xs:attribute name="Beep" default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="DestroyOnExit" default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:AastraIPPhoneFormattedTextScreen LockIn= “yes” default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
G-60
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
The XML “cancelAction” attribute allows you to specify a URI that a GET is
executed on when the user presses the default CANCEL key.
Note: The URI must be fully qualified.
You can add this optional feature at the end of any of the XML objects. The
format is:
<Hardkey action="Cancel">
<Label>Label to Display</Label>
<URI>URI to Get</Label>
</Hardkey>
XML Example:
The following illustrates the AastraIPPhoneTextScreen object using the “Cancel”
attribute:
<AastraIPPhoneTextScreen cancelAction=”http://10.50.10.117/
ft.xml”>
<Title>Test</Title>
<Text>This is a test of the cancel action</Text>
</AastraIPPhoneTextScreen>
When this XML script is sent to the phone, and the user presses the default
CANCEL key, the script executes a GET on http://10.50.10.117/ft.xml.
Note: If the “cancelAction” attribute was not used in the above script,
then pressing the CANCEL key would simply cancel the current screen.
41-001160-00, Release 2.1, Rev 04
G-61
Appendix G
CancelAction Attribute
(configurable via XML objects only)
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
HTTP Post
In addition to initiating a request to an XML application from the Services menu,
an HTTP server can push an XML object to the phone via HTTP Post. The phone
parses this object immediately upon receipt and displays the information to the
screen.
The HTTP post packet must contain an "xml=" line in the message body. The
string to parse is located after the equals sign in the message. HTML forms that
post objects to the phone must use a field named "xml" to send their data. See the
following examples (Example 1 and Example 2) for a sample HTTP post packet
and php source code.
Example 1:
POST / HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-powerpoint,
application/vnd.ms-excel, application/msword,
application/x-shockwave-flash, */*
Referer: http://10.50.10.53
Accept-Language: en-us..Content-Type: application/
x-www-form-urlencoded
Accept-Encoding: gzip, deflate..User-Agent: Mozilla/4.0
(compatible;MSIE 6.0;
Windows NT 5.0; .NET CLR 1.1.4322)
Host: 10.50.10.49
Content-Length: 194..Connection: Keep-Alive
Cache-Control: no-cache..Authorization: Basic YWRtaW46MjIyMjI=
xml=%3CAastraIPPhoneTextScreen%3E%
%3CTitle%3E57i+Tester%3C%2FTitle%3E
%3CText%3EMessage+to+go+on+phone.++Limit+to+512+bytes.%3C%2FText%3E
%2FAastraIPPhoneTextScreen%3E%
Note: The XML object cannot be larger than 2150 bytes. The phone
denies any posts larger than this limit.
G-62
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Example 2:
Appendix G
Below is a sample php source code which sends an XML object to an Aastra
phone.
<?php
#
function push2phone($server,$phone,$data)
{
# url-encode the xml object
$xml = "xml=".urlencode($data);
$post
$post
$post
$post
$post
$post
= "POST / HTTP/1.1\r\n";
.= "Host: $phone\r\n";
.= "Referer: $server\r\n";
.= "Connection: Keep-Alive\r\n";
.= "Content-Type: application/x-www-form-urlencoded\r\n";
.= "Content-Length: ".strlen($xml)."\r\n\r\n";
$fp = @fsockopen ( $phone, 80, $errno, $errstr, 5);
if($fp)
{
@fputs($fp, $post.$xml);
flush();
fclose($fp);
}
}
##############################
$xml = "<AastraIPPhoneTextScreen>\n";
$xml .= "<Title>Push test</Title>\n";
$xml .= "<Text>This is a test for pushing a screen to a phone </
Text>\n";
$xml .= "</AastraIPPhoneTextScreen>\n";
push2phone("172.16.96.63',"172.16.96.75",$xml);
?>
41-001160-00, Release 2.1, Rev 04
G-63
IP Phone Administrator Guide
How to Create an XML Application
Appendix G
HTTP Refresh Header
You can use an HTTP refresh header with the XML screen objects on the IP
phones. This feature provides the following:
•
All current XML screen objects have the ability to be refreshed by adding a
Refresh and URL setting to the HTTP headers. (see Refresh setting format
below)
•
The Refresh setting is set by the XML application and it is up to the
application to decide which objects it wants to refresh.
Note: This HTTP refresh header feature only applies to objects that
display to the screen.
The Refresh setting must be included in the HTTP header. The XML application
decides which objects it wants to use with this setting. The phone recognizes this
setting when parsing the HTTP header. If the setting is present, then it passes
along the refresh timeout and the URL to the ParserData object, which all XML
screen objects inherit from. The ParserData class also has a timer, which must be
set to expire at the next refresh time. When the timer expires (time to refresh the
screen), the phone requests the URL again and displays the refreshed screen.
Refresh Setting Format
The following is the Refresh setting format for the HTTP header:
Refresh: <timeout>; URL=<page to load>
The following example is a Refresh setting for use in an HTTP header:
Refresh: 3; URL=http://10.50.10.140/cgi-bin/update.xml
Note: You must use the Refresh and URL parameters in order for this
feature to work in the HTTP header.
G-64
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
HTTP Language Header
Note: This HTTP language header feature only applies to objects that
display to the screen.
XML Schema File
After creating an XML application for your IP phone, you can validate the XML
objects using the Schema file provided in this section. This helps you find any
parsing errors that may exist, and verify that your XML objects conform to the
Aastra API.
Note: Aastra IP phonees do not contain validating XML parsers. There
are many free XML validators available on the Web
(i.e., http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx) that
can perform validation using the schema file.
XML Schema
<?xml version="1.0" encoding="ISO-8859-1" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="AastraIPPhoneTextScreen">
<xs:complexType>
<xs:sequence>
<xs:element name="Title" type="xs:string" />
<xs:element name="Text">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="1000" />
</xs:restriction>
</xs:simpleType>
41-001160-00, Release 2.1, Rev 04
G-65
Appendix G
You can use an HTTP language header with the XML screen objects on the IP
phones. By including the language information in the HTTP header, the HTTP
GET includes the phone model, the firmware and the MAC address of the phone.
When the user selects a language on the phone, the selected language is sent to the
XML application and the application displays to the screen in that language.
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
</xs:element>
</xs:sequence>
<xs:AastraIPPhoneTextScreen LockIn="yes" default="no">
<xs:simpleType>
<xs:restriction base="xs:string>
<xs:pattern value="yes|no"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:AastraIPPhoneTextScreen Timeout="30" default="45">
<xs:simpleType>
</xs:complexType>
</xs:element>
<xs:element name="AastraIPPhoneTextMenu">
<xs:complexType>
<xs:sequence>
<xs:element name="Title" type="xs:string" />
<xs:element name="MenuItem" minOccurs="1" maxOccurs="15">
<xs:complexType>
<xs:sequence>
<xs:element name="Prompt" type="xs:string" />
<xs:element name="URI" type="xs:string" />
</xs:sequence>
<xs:attribute name="base" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="destroyOnExit" default="no">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="yes|no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="AastraIPPhoneInputScreen">
<xs:complexType>
G-66
41-001160-00, Release 2.1, Rev 04
Creating an XML Application
How to Create an XML Application
Appendix G
<xs:sequence>
<xs:element name="Title" />
<xs:element name="Prompt" />
<xs:element name="URL" />
<xs:element name="Parameter" />
<xs:element name="Default" />
</xs:sequence>
<xs:attribute name="type">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="IP|string|number" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="password" default="no">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="yes|no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="destroyOnExit" default="no">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="yes|no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="AastraIPPhoneDirectory">
<xs:complexType>
<xs:sequence>
<xs:element name="Title" type="xs:string" />
<xs:element name="MenuItem" minOccurs="1" maxOccurs="15">
<xs:complexType>
<xs:sequence>
<xs:element name="Prompt" type="xs:string" />
<xs:element name="URI" type="xs:string" />
41-001160-00, Release 2.1, Rev 04
G-67
Appendix G
IP Phone Administrator Guide
How to Create an XML Application
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="destroyOnExit" default="no">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="yes|no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="next" type="xs:string" />
<xs:attribute name="previous" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:schema>
G-68
41-001160-00, Release 2.1, Rev 04
Limited Warranty
If replacement parts are used in making repairs, these parts may be refurbished, or
may contain refurbished materials. If it is necessary to replace the telephone set, it
may be replaced with a refurbished telephone of the same design and color. If it
should become necessary to repair or replace a defective or malfunctioning
telephone set under this warranty, the provisions of this warranty shall apply to the
repaired or replaced telephone set until the expiration of ninety (90) days from the
date of pick up, or the date of shipment to you, of the repaired or replacement set,
or until the end of the original warranty period, whichever is later. Proof of the
original purchase date is to be provided with all telephone sets returned for
warranty repairs.
Exclusions
Aastra Telecom does not warrant its telephone sets to be compatible with the
equipment of any particular telephone company. This warranty does not extend to
damage to products resulting from improper installation or operation, alteration,
accident, neglect, abuse, misuse, fire or natural causes such as storms or floods,
after the telephone is in your possession.
Aastra Telecom shall not be liable for any incidental or consequential damages,
including, but not limited to, loss, damage or expense directly or indirectly arising
from the customers use of or inability to use this telephone, either separately or in
combination with other equipment. This paragraph, however, shall not apply to
consequential damages for injury to the person in the case of telephones used or
bought for use primarily for personal, family or household purposes.
This warranty sets forth the entire liability and obligations of Aastra Telecom with
respect to breach of warranty, and the warranties set forth or limited herein are the
sole warranties and are in lieu of all other warranties, expressed or implied,
including warranties or fitness for particular purpose and merchantability.
41-001160-00, Release 2.1, Rev 04
-1
Limited Warranty
Aastra Telecom warrants this product against defects and malfunctions during a
one (1) year period from the date of original purchase. If there is a defect or
malfunction, Aastra Telecom shall, at its option, and as the exclusive remedy,
either repair or replace the telephone set at no charge, if returned within the
warranty period.
IP Phone Administrator Guide
Limited Warranty
Warranty Repair Services
Should the set fail during the warranty period:
In North America, please call 1-800-574-1611 for further information.
Outside North America, contact your sales representative for return instructions.
You will be responsible for shipping charges, if any. When you return this
telephone for warranty service, you must present proof of purchase.
After Warranty Service
Aastra Telecom offers ongoing repair and support for this product. This service
provides repair or replacement of your Aastra Telecom product, at Aastra
Telecom's option, for a fixed charge. You are responsible for all shipping charges.
For further information and shipping instructions:
In North America, contact our service information number: 1-800-574-1611.
Outside North America, contact your sales representative.
Repairs to this product may be made only by the manufacturer and its authorized
agents, or by others who are legally authorized. This restriction applies during and
after the warranty period. Unauthorized repair will void the warranty.
-2
41-001160-00, Release 2.1, Rev 04
Index
Index
A
pickup parked call (pickupsprecode global
setting) 3-20
play call waiting tone 3-21
send dial plan terminator 3-19
status scroll delay 3-21
stuttered dial tone 3-21
suppress dtmf playback 3-20
UPnP mapping lines 3-22
xml beep support 3-21
Aastra Web UI
advanced settings description 2-13
basic settings description 2-12
enabling and disabling 2-14
operation description 2-10
status description 2-10
ACD
subscription period 5-133
action URIs 3-58, 5-209
beep, for xml applicaton 5-198
action URIs, configuring 5-211
beeping, status message 1-58
Administration Guide, for IP phone 1-xiv
blacklist duration 6-17
administrator options 3-1, 4-1
BLF
configuring 5-117
directed call pickup 5-81
on Asterisk 5-116
on BroadSoft 5-116
overview 5-114
setting 5-114
subscription period 5-120
subscription period, configuring 5-120, 5-133
auto call distribution
acd auto available 3-29
acd auto available timer 3-29
subscription period 5-133
Auto Call Distribution (ACD) key 5-99
auto-answer 5-61, 1-123
about 5-60
auto-answer, delay before 5-61
BLF key 5-98
B
BLF List,setting 5-115
barge in 5-62, 1-124
BLF/List key 5-98
Basic Preferences 3-19
Bridged Line Appearance (BLA)
about BLA 5-144
configuring 5-145
Basic settings
call waiting 3-20
digit timeout 3-19
display dtmf digits 3-20
goodbye key cancels incoming call 3-21
incoming call interrupts dialing 3-21
local dial plan 3-19
MWI Line 3-22
park call (sprecode) (global setting) 3-20
41-001160-00, Release 2.1, Rev 04
BLF subscription period 5-120
C
call forwarding 5-168
configuraton method for 5-170
configuring 5-170
enabling/disabling 5-169
Index-1
call waiting 5-43
Index
call waiting tone 5-44
call waiting tones 5-78
callers list
downloading to phone 5-178
enabling/disabling 5-176
overview 5-174
using on phone 5-176
Callers List key 1-10, 1-15
callers list key 5-101, 5-108
CancelAction, for XML applciations 5-199
Codecs 4-65
customized preference list of 4-66
conf key 5-101, 5-109
conference key
enabling/disabling 5-66
mapping as speeddial 5-67
Conference softkey 1-11, 1-15
config server
alternate TFTP 3-60
auto resync mode 3-63
auto resync time 3-64
download path 3-62
download protocol 3-59
download server 3-62
FTP password 3-61
FTP server 3-60
FTP username 3-60
HTTP path 3-61
HTTP server 3-61
primary TFTP 3-59
select TFTP 3-60
XML application post list 3-65
configuration
file precedence 1-22
methods for performing 2-2
configuration file, description of 1-21
configuration files
installing 1-23
using 2-15
configuration server 4-79
configuring 4-79
configuration server settings 3-59
Index-2
D
delete key 1-7
DHCP 4-4
configuring 3-6, 4-6
not using 1-18
using 1-18
dial plan
configuring 5-33
dial plan terminator
overview 5-32
dial plan, emergency 5-15
dial plans
overview 5-30
Dial softkey 1-11, 1-15
dial tones, stuttered
about 5-46
configuring 5-46, 5-52, 5-54, 5-56, 5-58
DiffServ QoS 4-31
Directed call pickup
configuring 5-84
description of 5-81
directed call pickup
enable/disable 3-28
play ring splash 3-28
prefix setting 3-28
Directed Call Pickup (DCP) key 5-99
Directory key 1-10, 1-15
directory key 5-101, 5-108
directory list
download behavior 5-187
downloading procedures 5-191
downloading to server 5-186
limitations for 5-187
overview 5-182
using 5-188
DND
configuring 5-136, 5-142
overview 5-142
DND key 5-99
DSCP 3-39, 4-33
DTMF digits
configuring display of 5-41, 5-44
41-001160-00, Release 2.1, Rev 04
displaying 5-41
DTMF methods 4-68
DTMF, out-of-band 4-67
DTMF, suppressing playback 5-39
E
HTTP and HTTPS support 2-5
Index
DTMF playback, configuring suppression for 5-39
H
HTTPS
client functions 2-6
client/server configuration 4-23
security method for 1-23, 1-24
server functions 2-6
using via Aastra Web UI 2-7
emergency dial plan, defining 5-15
empty key 5-102
encryption
methods for 7-2
overview 7-2
procedure for 7-3
I
icom key 5-108
incoming call interrupts dialing 5-52
Installation 1-6
expansion module, 536M 1-4
Installation Guide, for IP phone 1-xiv
expansion module, 560M 1-4
expansion module, customizing columns for 5-227,
1-166, 1-168, 1-170
intercom feature
configuring 5-62
incoming calls 5-61
outgoing calls 5-60
F
Intercom key 1-15
feature keys 5-93
configuring 5-106
feature keys, configuring 5-111
feature keys, guidelines for programming 5-107
intercom settings, incoming
allow barge in 3-23
auto-answer 3-22
microphone mute 3-23
play warning tone 3-23
firmware
configuration server requirement for 1-20
description of 1-21
installation considerations 1-18
installation methods 1-18
installing 1-23
intercom settings, outgoing
line 3-24
prefix code 3-24
type 3-23
firmware updates 3-66
K
flash key 5-100, 5-110
G
General Preferences 3-19
Goodbye Key
canceling incoming call using 5-54
Group Call Pickup (GCP) key 5-99
IP phone UI 2-2
key mapping
map conf key to 3-25
map redial key to 3-25
key mapping, enable/disable Redial, Xfer, Conf
Keys 5-66
L
Language
language 1 thru 4 3-30
41-001160-00, Release 2.1, Rev 04
Index-3
Index
language
overview 5-21
specifying on IP phone 5-24
WebPage Language 3-30
LAN Port 3-34
NAT IP 3-35
NAT RTP port 3-36
NAT SIP Port 3-35
Nortel NAT 3-36
Nortel NAT timer 3-36
NTP time servers 3-37
PC Port 3-34
primary DNS 3-33
secondary DNS 3-34
subnet mask 3-33
Time Servers 1 thru 3 3-37
UPnP 3-35
language pack settings 1-110
language settings 1-109
last call return (lcr)
configuring 5-164
how it works 5-164
lcr key 5-100
line key 5-98, 5-108
line settings 3-56
lockIn, for xml applications 5-199
locking keys, on the IP phone 5-28
locking keys, procedures 5-29
locking softkeys and programmable keys 1-163,
1-166, 1-168, 1-170
locking/unlocking the phone 5-9
M
microphone mute 1-123
missed calls indicator
accessing and clearing 5-181
enabling/disabling 5-180
overview 5-180
N
NAT
configuring 4-18
configuring NAT address and port 4-21
Nortel Networks 4-18
overview 4-16
router configuration 4-17
network configuration 4-4
network parameters 1-6
network settings
DHCP 3-32
gateway 3-33
HTTPS block XML HTTP Posts 3-38
HTTPS Client Method 3-37
HTTPS redirect 3-38
IP Address 3-32
Index-4
network settings, advanced 3-35, 4-16
network settings, basic 3-32, 4-4
network settings, configuring 4-8
none key 5-98, 5-108
Nortel Proxy 4-17
O
operational features 5-4
operational features, advanced 6-3
configuring line number 6-5
configuring MAC address 6-5
configuring message sequence for blind
transfer 6-7
options
via Aastra Web UI 3-7
via Configuration Files 3-9
via IP Phone UI 3-3
options menu, simplified 1-5
P
parameters
53i and 55i programmable key 1-145
55i, 57i, 57i CT softkeys 1-137
Aastra Web UI 1-12
acd auto-available timer 1-131
ACD subscription period 1-69
Action URIs 1-92
advanced SIP 1-62
audio transmit and receive adjustment
settings 1-125
41-001160-00, Release 2.1, Rev 04
41-001160-00, Release 2.1, Rev 04
updating caller ID 1-173
UPnP 1-25
VLAN 1-26
voicemail 1-84
whitelist proxy 1-175
XML settings 1-89
Index
auto-answer settings 1-121
blacklist duration 1-175
BLF subscription period 1-68
blind transfer setting 1-172
boot sequence recover mode 1-173
call forward settings 1-87
call waiting settings 1-101
Callers List settings 1-86
centralized conferencing 1-60
configuration server 1-13
customized callers list and services keys 1-86
dial plan 1-39
directed call pickup 1-128
directory settings 1-85
DSCP 1-30
DTMF digits 1-120
emergency dial plan 1-11
global ring tone settings 1-94
global SIP 1-41
goodbye key cancels incoming call 1-99
HTTPS client and server settings 1-23
incoming call interrupts dialing 1-98
incoming intercom 1-123
Intercom settings 1-121
language 1-109
language pack 1-110
MAC Address/Line Number 1-63
message waiting indicator 1-102
missed call summary subscription period 1-71
missed call summary subscription, global 1-70
missed call summary subscription, per-line 1-71
Missed Calls Indicator settings 1-88
NAT 1-20
outgoing intercom 1-121
park and pickup global settings 1-132
password 1-9
per-line ring tone settings 1-97
per-line SIP 1-50
priority alert settings 1-103
RTP, Codec, DTMF global settings 1-77
silence suppression settings 1-80
SIP registration retry timer 1-67
softkeys, programmable keys, feature keys 1-136
stuttered dial tone setting 1-100
Suppress DTMF Playback 1-119
time server 1-31
ToS 1-30
Transport Layer Security (TLS) 1-72
parameters, list of configurable 1-5
key settings 1-136
time server settings 1-31
parameters, setting in configuration files 1-4
park key 5-100, 5-109
park/pickup
about parked/pickup calls 5-35, 5-153
configuring a static configuration 5-37
configuring programmable configuration using
config files 5-155
configuring programmable configuration using Web
UI 5-157
programmable configuration of 5-153
static configuration of 5-35
using on the IP phone 5-162
password, resetting user’s 5-6
passwords
for a user 5-4
for an administrator 5-8
phone lock key 5-102
Phone Status
Firmware Version 3-11
IP&MAC Address 3-11
LAN Port 3-11
PC Port 3-11
phone status settings 3-10
pickup key 5-100, 5-109
play warning tone 5-61, 1-124
priority alerting
about 5-75
configuring 5-79
priority alerting settings
auto call distribution 3-27
community 1 thru 4 3-27
emergency 3-27
enabling 3-26
external 3-27
group 3-26
Index-5
Index
internal 3-27
priority 3-27
S
Programmable key settings
53i, 55i 1-145
save key 1-7
programmable keys 5-93
configuring 5-103
screen timeout, for XML 5-198
public key 5-110
scrolling, status message 5-201, 1-58
Q
Services key 1-10, 1-15
QoS 4-31
silence suppression 4-69
R
redial key
enabling/disabling 5-66
mapping as speeddial 5-67
repair 0-2
requirements, IP phone 1-19
restarting IP phone 3-13
ring tone
global ring tone 3-26
patterns used for 5-76
per-line ring tone 3-26
tone set setting 3-26
ring tone sets 5-72
configuring 5-73
ring tones 5-70
configuring 5-73
ring tone 3-26
tone set 3-26
RTP
basic codecs for 4-65
configuring 4-64, 4-70
customized codec preference list 4-66
dtmf method 4-68
encryption method (SRTP) 4-68
out-of-band DTMF 4-67
RTP port 4-65
silence suppression 4-69
rtp encryption 4-68
RTP port 4-65
RTP settings 3-54
SBG and ALG proxy 4-17
scroll delay 5-198
services key 5-102
SIP
advanced settings 4-58
configuring 4-50
overview of 4-45
parameter precedence 4-48
SIP settings, advanced 3-49
acd subscription period 3-52
blacklist duration 3-53
BLF subscription period 3-52
explicit mwi subscription 3-49
explicit mwi subscription period 3-49
missed call summary subscription 3-49
missed call summary subscription period 3-50
registration failed retry timer 3-51
registration renewal timer 3-52
registration timeout retry timer 3-51
send line number in REGISTER message 3-50
send MAC address in REGISTER message 3-50
session timer 3-50
timer 1 and timer 2 3-51
transaction timer 3-51
transport protocol 3-51
whitelist proxy 3-53
SIP settings, basic 3-43
auth name 3-44
BLA number 3-45
caller ID 3-44
display name 3-44
line mode 3-45
password 3-44
phone number 3-44
screen name 3-43
screen name 2 3-43
user name 3-44
SIP settings, network
Index-6
41-001160-00, Release 2.1, Rev 04
SIP Settings, RTP
Basic Codecs 3-54
customized Codec preference list 3-55
DTMF method 3-55
Force RFC2833 Out of Band DTMF 3-54
RTP encryption 3-55
RTP port 3-54
silence suppression 3-55
troubleshooting 9-2
solutions to common problems 9-7
Tx/Rx adjustments
about 5-218
configuring 5-219
Index
backup proxy port 3-46
backup proxy server 3-46
backup registrar port 3-48
backup registrar server 3-48
outbound proxy port 3-47
outbound proxy server 3-47
proxy port 3-46
proxy server 3-46
registrar port 3-47
registrar server 3-47
registration period 3-48
type of service
RTCP 3-39
RTP 3-39
SIP 3-39
U
upgrading, firmware 8-2
UPnP
configuring 4-28, 1-25
description of 4-27
upnp gateway 3-35
upnp manager 3-35
Softkey settings 1-136
User Guide, for IP phone 1-xiv
softkeys 5-93
configuring 5-103
usernames
administrator 2-9, 3-7, 4-3
configuring for FTP server 4-84
configuring for SIP authentication 4-52
for FTP 1-15
for SIP authentication 4-46, 4-47, 1-42, 1-51
global BLA 5-145
per-line BLA 5-146
user 2-9
Softkeys and Programmable Keys
locking 5-29, 5-227, 1-163
softkeys, state-based 5-94
speeddial key 5-98
sprecode key 5-100
SRV lookup, configuring 4-49
status message beep
configuring in configuration files and Web
UI 5-200
status message scrolling 1-58
configuring in configuration files and Web
UI 5-201
T
time and date
date format 3-29
time format 3-29
time servers, configuring 4-42
ToS 4-31
ToS, DSCP 3-39
Transfer softkey 1-11, 1-15
41-001160-00, Release 2.1, Rev 04
V
VLAN 3-40
configuring 4-31
DSCP Range 4-33
global priority non-IP packet 3-40
global VLAN enable 3-40
LAN Port SIP, RTP, RTCP Priority 3-41
LAN Port VLAN ID 3-40
PC Port priority 3-42
PC Port VLAN ID 3-42
priority mapping 4-33
voicemail
configuring 5-193
overview 5-193
using 5-195
Index-7
W
Index
warranty 0-1
warranty exclusions 0-1
whilte list proxy 6-19
X
xfer key 5-101, 5-109
Xfer key, enabling/disabling 5-66
XML
configuring 5-203
configuring on IP phone 5-202
customized services 5-196
overview 5-196
push requests 5-203
using on phone 5-208
XML action URIs 5-209
xml beep support 5-48, 5-50
XML Get timeout 5-198
XML key 5-99
XML softkey URI 5-214
Index-8
41-001160-00, Release 2.1, Rev 04
SIP IP Phone Administrator Guide
Models 53i, 55i, 57i, and 57i CT
© 2007 Aastra Telecom Inc.
If you’ve read this owner’s manual and consulted the Troubleshooting section and
still have problems, please visit our website at www.aastratelecom.com or call 1-800-574-1611
for technical assistance.
41-001160-00
Release 2.1, Rev 04
August 2007
Download PDF

advertising