Avaya 3631 Manuel de configuration - Page 8

Parcourez en ligne ou téléchargez le pdf Manuel de configuration pour {nom_de_la_catégorie} Avaya 3631. Avaya 3631 8 pages. Co-existence with ip wireless handset offering

Imprimer la page

7 Verification Tests and Troubleshooting

Careful verifications tests are mandatory it a mixture of 3631 phones and 364x phones shall

be installed. First modify the configuration of the existing 3631 phones and WLAN

infrastructure, if necessary. Verification tests shall ensure that the existing installation of

3631 phones goes into service again undisturbed.

Then configure a few new 364x phones, connect them to the network and verify that they

go into service. Finally verify the co-existence of both phone types (calls between 3631

phones and 364x phones, QoS if 3631 and 364x phones are associated to the same WLAN

Access Point, ...).

1. 364x Phones gets 'No Reg Domain' error message

Resolution: 364x Phones needs to be set to the Regulatory Domain without which is does not

start the boot process. 3631 has no such limitation.

2. There are few other settings that are mandatory for the 364x Phones to start the boot process.

They are as below:

•

SSID (and the security parameters associated with this SSID)

•

QoS Settings - Standard WMM or AVPP (AVPP is the Default Value for 364x Phone)

•

364x Phone uses DHCP SSON 176 (3631 phone uses SSON 242).

For more details please refer the Admin Guide of the 364x Phones.

3. If a new CM feature is added, then the 364x Phones needs to be rebooted to get those

feature. 3631 Phone doesn't need a reboot.

Enhanced Dialing Parameters are needed to be able to make a successful callback from the

Call Log. 3631 phone gets these values from the 46xxsettings file. Needs to be enabled and

set using Admin Menu or through HAT in the 364x Phones.

- 8 -