Application Note

FS; Reviewed:

SPOC 09/07/2010

Solution & Interoperability Test Lab Application Notes

40 of 44

11xx12xx-SM

8. Verification Steps

All features shown in Table 2 were tested using the sample configuration. The following steps

can be used to verify and/or troubleshoot installations in the field.

Step Description

After rebooting the telephone, use the More and Prefs soft keys at the phone to verify that

the parameters set in the phone configuration file have been loaded. Verify registration

with Session Manager by the appearance of the idle screen. If this is the first time

registration is being attempted and multiple domains have been configured, enter the

appropriate domain (“avaya.com” in the sample configuration). Verify that the line

appearance shows the Communication Manager extension for that phone.

Verify basic feature set administration by lifting the handset (or pressing the speaker

button), and making calls to other phones. Test supported features according to Table 2

and feature deployment plans at the site.

Using the SAT interface, enter the status trunk n command, where n is the SIP trunk

configured in Section 5.6. Note down the Member with Service State set to in-

service/active. In this example, 0060/006 and 0060/007 are active and either member can

be used to verify whether calls shuffled and which codec was used.

status trunk 60 Page 1

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports

Busy

0060/001 T00199 in-service/idle no

0060/002 T00200 in-service/idle no

0060/003 T00201 in-service/idle no

0060/004 T00202 in-service/idle no

0060/005 T00203 in-service/idle no

0060/006 T00204 in-service/active no T00094

0060/007 T00205 in-service/active no T00063