Provisioning The Ip Softphone 3456 - Avaya CS 1000M SG Installation And Commissioning Manual

Provisioning the IP Softphone 3456

.
ATTENTION
This document contains information about manual configuration. For information
about automatic provisioning, contact Avaya technical support.
The IP Softphone 3456 can be configured to gather account and
configuration data from a central provisioning server. This feature
can facilitate large-scale rollouts of the phone across the enterprise
infrastructure. When started for the first time, the application requests
a user name and password for server authentication purposes. If the
user operates the phone in an environment with a provisioning server
configuration data is transferred from the server to the phone when they
log on.
This document contains information about manual configuration; therefore,
server authentication is not required.
Provisioning details
For the IP Softphone 3456, implement the following provisioning details:
•
Disable the provisioning server on the phone. On the phone, navigate
to Preferences > Advanced > No login server available.
To disable the provisioning server on the phone, see
"Disabling the login feature" (page
•
Configure only the G.711 and G.729 voice codecs for the IP Softphone
3456.
•
Ensure that the fixed single port is defined. Navigate to Account
Settings > Topology > Port Range to set the port.
•
Ensure the registration refresh time is set to 5 minutes. This keeps the
registration timer short enough to recover quickly in case of network
failure.
•
To make the IP Softphone 3456 DTMF work with the Media Application
Server (MAS), ensure that SIP > Account > Topology > Enable ICE
is not selected.
Use the following steps to bypass authentication and disable the login
feature.
Procedure 2
Disabling the login feature
Step Action
1 Launch the IP Softphone 3456 from Programs > Avaya > IP
Softphone 3456.
Avaya Communication Server 1000
Avaya IP Softphone 3456 Installation and Commissioning Guide
NN43080-600 02.01
Launching the IP Softphone 3456 19
19).
November 2010
Procedure 2