2.5 INTEGRATION WITH AVAYA IP PHONE SYSTEMS ................................................................. 12 2.5.1 Call Model .................................................................................................................. 12 2.5.2 Call Signalling ............................................................................................................ 12 2.5.3 Telephony features ...................................................................................................... 12
2.6 ADMINISTRATION AND PROVISIONING ................................................................................. 12 2.6.1 Field Upgradeability................................................................................................... 12 2.6.2 Manual (Local) Administration .................................................................................. 12 2.6.3 DHCP Based provisioning.......................................................................................... 12 2.6.4 TFTP Scripting............................................................................................................ 12 2.6.5 Status / Statistics. ........................................................................................................ 13
3.1 TELEPHONY FEATURES ........................................................................................................ 14 3.1.1 Server Provisioned Features....................................................................................... 14 3.1.2 Server Based Features ................................................................................................ 14
3.1.3 Local Features ............................................................................................................ 14 3.2 CORE FEATURES .................................................................................................................. 15
3.3 NETWORK QOS SUPPORT .................................................................................................... 17 3.3.1 802.1Q/VLAN support................................................................................................. 17 3.3.2 QoS Tagging support .................................................................................................. 17
4 GENERAL OPERATION........................................................................................................ 18
4.1 4690 IP CONFERENCE PHONE APPEARANCE TO AVAYA PBX.............................................. 18 4.2 SUPPORT FOR AVAYA CALL PROCESSING(ACP).................................................................. 18 4.3 SUPPORT FOR DIGITAL COMMUNICATIONS PROTOCOL(DCP).............................................. 18 4.4 MEDIA ENCRYPTION ............................................................................................................ 18 4.5 LINK BOUNCE ...................................................................................................................... 19 4.6 BOOT PROCESS .................................................................................................................... 19
4.6.1 Power Up and Reset.................................................................................................... 19 4.6.2 Power Up Reset Interval............................................................................................. 19 4.6.3 Software Upgrade and File Naming ........................................................................... 19 4.6.4 System Constants, System Values and System Initialization Values........................... 19 4.6.5 Script Files .................................................................................................................. 20
4.7 SUPPORT FOR LOCAL PROCEDURES ..................................................................................... 20 4.8 USER INTERFACE ................................................................................................................. 20
4.8.1 Icon Support................................................................................................................ 20 4.8.2 LED Lamp States ........................................................................................................ 21 4.8.3 Idle Display................................................................................................................. 21 4.8.4 Selecting a call appearance ........................................................................................ 22 4.8.5 Offhook/Dialing/Connected Display........................................................................... 23 4.8.6 Call Hold Display ....................................................................................................... 24 4.8.7 Incoming Call Display ................................................................................................ 24 4.8.8 Transfer/Conference Display...................................................................................... 24 4.8.9 Server Provisioned Features....................................................................................... 25 4.8.10 Local Menu/Options.................................................................................................... 26
The Avaya 4690 IP Conference Phone is a product developed by Polycom based on the Furby platform and will be provided to Avaya under the terms of an OEM business agreement. The 4690 IP will be a high quality conference room audio communications terminal for TCP/IP and Ethernet based networks that will interoperate with Avaya’s existing IP telephony environment. The phone contains state-of-the-art audio processing technology and an implements the Avaya call model using the Digital Communications Protocol (DCP).
For the purpose of this document, Furby shall refer specifically to the hardware platform and 4690 IP shall refer to the final product.
This document serves as the product requirements document for this product and will reference the following Avaya documents:
• Avaya Call Processing (ACP) Single Connect IP Protocol Specification for the 4602 Telephone, Issue 1.7, December 3, 2002. Compas ID 90435
• DCP Protocol Specification for the 4602 IP Telephone, Issue 1.1, February 28, 2002. Compas ID 90460
• Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003. Compas ID 95746
• Eurofont Requirements for ADT Terminals, Issue 1.0, March 12, 1996. Compas ID 51069
• Memo from Renee Krahn dated December 11, 2002, Subject: Feature button labels on the 4620 IP Telephones. Doc file name: 24204620labels.pdf
• E46xx IP Telephones Media Encryption Requirements, Issue 1.8, February 9 2003, Compas ID 96406
• Registration/Admission/Status (RAS) Procedures FOR R2.1+ 46xx IP Telephones, Issue 2.1.2, April 27 2004, Compas ID104266
• E46xx IP Telephone Media Encryption Requirements, Issue 1.8, February 9, 2003 updated to include Compas MR 48990
• Requirements for AES Media Encryption, Issue 1.0
• Advance Encryption Standard (AES) FIPS PUB 197
This document, once approved by Avaya, will be included as an appendix to the contract. The contract between Avaya and Polycom will be the controlling document on non-technical issues.
Ordering and packaging information will be provided as separate documents.
1.1 Document Control Process Upon approval of this document by Avaya and Polycom, this document will be published as Revision 2.0 in PDF format. Revision 2.0 of this document will be placed into revision control at Polycom with PVCS or CVS.
All future revisions of this document will be managed through PVCS or CVS.
2 General Requirements The requirements for this product were previously provided to Avaya in the Polycom document marked Product Requirements Document – SoundStation IP Plus – Avaya dated January 20, 2003 Revision D.
The following is a summary of the requirements for the 4690 IP Conference phone delivered to Avaya on January 20, 2003 with updates based on Avaya recommendations. This section is included as a reference only. Sections 3 through 5 contain the controlling product requirement for the 4690 IP design.
2.1 User Interface Elements The 4690 IP offers a simple user interface to facilitate an easy and intuitive experience for conference room users in general.
a=303
Hold More
Ext 301 10:44am 6/10/03
Drop
2.1.1 Liquid Crystal Display (LCD) The 4690 IP will have an LED backlit graphical LCD with a resolution of 248x68 pixels.
The display will support the Avaya EuroFont character set as defined in the document Eurofont Requirements for ADT Terminals, Issue 1.0 Compas ID 51069 provided by Avaya to Polycom. The Katakana font will be considered for a future release of the product.
The display will show up to three soft key labels at any given time aligned with the the three soft keys on the lower edge of the display.
Other areas of the display will be allocated to show date/time and phone extension of the phone.
Three lines of the display will be used for call information for both incoming and outgoing calls. These lines will be allocated as one line per call appearance up to a maximum of three.
2.1.2 Keypad The keypad consists of the standard 12 key telephone keypad with two raised dimples on the ‘5’ Key.
Dedicated keys are provided for On-hook/Off-Hook, Redial, Mute and Volume UP/DOWN functions.
Three context sensitive softkeys are located on the bottom edge of the display that will line up with display based key labels.
A menu key is provided to allow a user to access local setup menus. Navigations of these menus will be performed with Scroll Up/Down keys and a Select key is provided to select a menu option or feature. An exit key is grouped with these keys to exit menus or feature lists.
2.1.3 Visual Indicators Three bi-color LED’s are provided to signal the status or mode of operation of the phone. Supported conditions include:
• Ringing: Green flashing LED indicators
• Call Connected: LED indicators are solid green
• Microphone Mute: LED indicators are flashing red
• Message Waiting Indicator: Not supported
2.1.4 Audible Indicators Audible tones are available for these following conditions:
• Ringing: User selectable ring tones are played to indicate incoming calls
• Telephone keypad press: A short tone is played to indicate that a key on the 12 button dial pad is pressed. The microphone is muted when these tones are played. Tones are not supported on non-dial pad keys.
• Server-based feature invocation: Local tones are not provided to indicate that a server-based feature has been invoked. Feedback will be provided to the user in the form of a display indication or a server provided tone.
2.2.1 Power The 4690 IP requires AC power and is supplied with a universal power brick that can convert 110/220V (100V in Japan) at either 50 or 60 Hertz to the DC voltage required by the phone.
Country kits are available, consisting of country specific cord kits that connect the universal power brick to local AC outlets. The power cords will be 10’ in length.
2.2.2 Single cable design To minimize desktop clutter, the 4690 IP is supplied with a Power Interface Module (PIM) that combines the power from the AC adapter and the Ethernet connection into a single cable that runs up to the tabletop to connect to the phone.
2.2.3 Regulatory compliance The 4690 IP will conform to the following regulatory specifications: Safety
At FCS (First Customer Shipment), the product will have regulatory compliance for the entire North American market (US, Canada & Mexico,) as well as EMEA, Japan, Australia & New Zealand). It is proposed that compliance with Korean and Chinese agencies be performed as a 2nd phase activity that ties in with Asian language support on the product.
2.2.4 Environmental specifications Operating temperature: 32° - 104° F (0° - 40° C)
Relative humidity: 20%-85% (non-condensing)
Storage temperature: -22° - 131°F (-30° - 55° C)
2.2.5 Physical form factor / labeling The 4690 IP is manufactured from ABS plastics that meet or exceed UL requirements. The appearance of the product is shown below:
The phone will be labeled with the Avaya trademark and the model number 4690 IP.
2.2.6 Extension microphones The Furby platform has the necessary jacks to accept the connection of two extension microphones to increase the microphone pick-up to support larger rooms. The expansion microphones each offer a Mute key as well as an LED indicator to indicate the current Mute state1. The extension microphones are not labeled with a specific company brand or product name. Extension mic cables will be 7’ in length each.
1 Pressing the Mute key on any of the expansion microphones toggles the Mute state of the entire phone – not just that microphone.
2.3.1 Full-duplex operation The phone will operate as Type 1 full-duplex devices providing acoustic echo cancellation as defined under the IEEE 1329 methodology for measurements. The 4690 IP will implement gated microphone technology to minimize transmission of extraneous near end noise from the mics furthest from the active speaker.
2.3.2 Room coverage The 4690 IP will provide 360 degree room coverage by utilizing a 3 microphone design. This product is suited for conference rooms with approximate dimensions of 20’x20’ when no external mics are used and up to 20’x30’ when extension mics are installed
2.3.3 Loudspeaker The console speaker on the 4690 IP will have a frequency response of 350 to 3500 Hz with a peak volume of 86.5 dB volume (peak) at 0.5 meters.
Receive frequency response is tested to the following frequency mask published in TIA/EIA IS-810-A.
2.3.4 Voice compression The 4690 IP supports G.711(A-Law and µ-Law) and G.729a voice compression as negotiated during call setup.
During silence periods, and when silence suppression has been requested during call setup, no packets are being sent to the remote end (this includes no silence indication
packets and no comfort noise packets). Therefore silence suppression is handled by stopping any packets transmission, packet transmission resumes during speech period.
Comfort noise is locally generated as an adaptive “noise fill” to the local user upon silence period detection.
For G.729a compression, SID frames can be received if sent by the remote end and comfort noise (“noise fill”) will be locally generated to the user.
2.4 Networking
2.4.1 Ethernet connectivity A single IEEE 802.3 compliant 10/100 Base-T Ethernet port is available. It provides for auto-sensing half or full duplex operation.
The phone will ship with two Ethernet Cat-5 cables. The cable supplied for the connection from the PIM to the network is 7’ in length and the cable supplied to connect from the PIM to the main 4690 IP console will be 25’ in length.
There is no support for Powering over Ethernet.
2.4.2 IP Configuration That 4690 IP supports both DHCP and statically assigned IP addresses. DHCP is enabled by default.
2.4.3 DNS DNS is supported in the phone.
2.4.4 QoS The 4690 IP supports packet tagging at both Layer 2 and Layer 3, allowing customers to create VLAN environments or to support network environments that have specific QoS architectures.
• Layer 2: 802.1 p/Q
• Layer 3: TOS, IP Precedence
2.4.5 Date/Time Synchronization Date/Time will be provided by the call server.
2.5.1 Call Model The 4690 IP will implement the Avaya Single Connect Call Model as defined in the Avaya document labeled Avaya Call Processing (ACP) Single Connect IP Protocol Specification for the 4602 Telephone, Issue 1.7, December 3, 2002, Compas ID 90435.
2.5.2 Call Signalling Polycom will implement the Avaya Digital Communications Protocol as defined in the Avaya document labeled DCP Protocol Specification for the 4602 IP Telephone, Issue 1.1, February 28, 2002, Compas ID 90460.
2.5.3 Telephony features The 4690 IP will emulate the Avaya 4620 IP telephone. As such it will have access to the Avaya 4620 IP telephone feature set and will offer server programmable feature buttons. Since the 4690 IP has a limited number of soft keys and fairly limited display size relative to the 4620, the presentation of the feature set to the user will be modified to suit the available UI components of the 4690 IP.
2.6 Administration and Provisioning
2.6.1 Field Upgradeability The 4690 IP uses the TFTP protocol to enable automatic phone firmware upgrades in the field. Any device reboot will trigger the cycle of determining if an upgrade is necessary.
2.6.2 Manual (Local) Administration This mode of operation allows for configuration data to be viewed and/or edited at the phone (using the phone’s UI).
2.6.3 DHCP Based provisioning The phone will interpret DHCP parameters as per the Avaya 46xx phones to provision:
• IP addresses and network parameters
• Call Server information
• QoS Tagging and VLAN settings
2.6.4 TFTP Scripting This will be supported as per the Avaya specification Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003. Compas ID 95746.
3.1 Telephony Features Three classes of telephony features are supported by the 4690 IP. They are server-provisioned features, server based features and local features. Access to these features will be adapted to the available 4690 IP UI elements and described in the section marked User Interface.
3.1.1 Server Provisioned Features The 4690 IP Conference phone will support the server provisioned feature set for the Avaya 4620 IP phone. The features are provided by the server in the form of a set of feature button labels with corresponding key ID’s. These features will be accessed via a scrolling list that is accessed by pressing the ‘Select’ key from either the idle display or during a call.
Supported server provisioned features are defined in the Avaya document labeled 24204620labels.pdf titled Feature Button Labels on 4620 IP Telephones. All labels shown in Table 1 of 24204620labels.pdf will be supported.
Please refer to the UI section for a description of how these features will appear on the display and how they will be accessed.
3.1.2 Server Based Features These features correspond to those on the 4620 that have hard feature keys but are server based. These features will be accessed via soft keys with locally controlled soft key labels.
The features that fall into this category are:
• Hold
• Transfer
• Conference
• Drop
Please refer to the UI section for a description of how these features will appear on the display and how they will be accessed.
3.1.3 Local Features Local features are features that have fixed keys assigned and the functionality is provided locally.
G.729a Compression support (8K) (20ms packet sizes)
Jitter Buffer Dynamic
3.2.2 Audio Delay The Avaya specification Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003. Compas ID 95746 Section 4602TP.3.4.600 requires that the one way end to end audio delay must be less than 55 milliseconds for the specified G.711 packet
size and network conditions. The 4690 IP audio delay is expected to be in the approximate range of 55 ms but may not meet the stated requirement. Actual delay will be determined at a later date through measurements.
3.2.3 Networking Features Table 2 – Supported Network Features
Networking Features
DHCP Supported Options
Description
1 Subnet Mask
3 Router addresses
6 DNS Server
15 Domain Name
66 TFTP
SSON (default 176)
Name=value pairs
Static IP Router/TFTP options must be manually configured
DNS Supported
TFTP Supported
TCP Supported
UDP Supported
RTP Supported
SNMPv2c Standard MIB II and Avaya 46xx specific MIB is supported in read-only mode
3.3.1 802.1Q/VLAN support The 4690 IP will support 802.1Q and VLANs within the range of 0-4094. The default VLAN id will be set to ‘0’.
3.3.2 QoS Tagging support The 4690 IP sets the IP Class Of Service (COS) and IP Type Of Service (TOS) bits as follows. The packets are tagged only when a VLAN is configured. Both Layer 2 and Layer 3 tags can be applied to RTP traffic and signalling traffic on a individual basis.
4.1 4690 IP Conference Phone Appearance to Avaya PBX
The 4690 IP Conference Phone will register to an Avaya PBX as an Avaya 4620 IP phone. Since all of the features supported by the 4620 may not be available on the 4690 IP, signaling received by the 4690 IP relating to these unsupported features will be discarded.
4.2 Support for Avaya Call Processing(ACP)
The 4690 IP will support the procedures outlined in the Avaya document, Avaya Call Processing (ACP) Single Connect IP Protocol Specification for the 4602 Telephone, Issue 1.7, December 3, 2002, Compas ID 90435 to establish a connection to the server upon startup.
4.3 Support for Digital Communications Protocol(DCP) The 4690 IP will upon registration with the Avaya server as described in section 4.2, will be set up to send and receive Digital Communications Protocol (DCP) messages tunneled within H.225 INFORMATION messages. This is implemented as per the Avaya Document labeled DCP Protocol Specification for the 4602 IP Telephone, Issue 1.1, February 28, 2002, Compas ID 90460 with the some minor exceptions:
• Section 4.9.1.1 Lamp Update – Message Waiting Indication will not be supported.
• Section 4.9.4.1 Alerting/Ringer Update – Support for distinctive ring will utilize ring tones available in the existing Furby codebase and may not match the ring tones defined in 4602RFS.3.4.600. Inside and outside calls will map to the user selected ring tone. All other tones will map to a brief tone.
• Section 4.9.16.3 Display Control Message is not required to be supported.
4.4 Media Encryption Rel 2.0 of the 4690 IP will support AES media encryption as defined in Avaya documents:
• Requirements for AES Media Encryption, Issue 1.0 • E46xx IP Telephones Media Encryptions Requirements, Issue 1.8, February 9, 2003
4.5 Link Bounce Rel 2.0 of the 4690 IP will support Link Bounce functionality as defined in the Avaya document Registration/Admission/Status (RAS) Procedures for R2.1+ 46xx IP Telephones, Issue 2.1.2, April 27 2004,, Compas ID 104266.
4.6 Boot Process
4.6.1 Power Up and Reset The 4690 IP will comply with the requirements for Power Up and Reset as defined in the Avaya document labeled Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 4602TP.3.1.100 with the following exceptions:
• A secondary Ethernet interface is not supported
• Since message waiting indicator is not supported, the three LED indicators will light with a red solid indication prior to the initializing display during the boot sequence
4.6.2 Power Up Reset Interval The 4690 IP will not comply with the requirement specified in the Avaya document labeled Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 4602TP.3.1.150 requiring that DHCP DISCOVER will start within 20 seconds of power up or a hard reset if an IP address is not manually assigned. The standard boot sequence where a software upgrade is not required will be approximately 40-50 seconds.
4.6.3 Software Upgrade and File Naming The 4690 IP will comply with the requirements for software downloadability and file naming as defined in the Avaya document labeled Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 4602TP.3.0.100.
4.6.4 System Constants, System Values and System Initialization Values The 4690 IP will comply with the requirements for System Constants, System Values and System Initialization Values as defined in the Avaya document labeled Telephone
Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 4602TP.3.0.200 with the following exceptions:
• The only valid value for PHY1STAT is a value of ‘1’
• PHY2STAT and HUBSTAT is not supported since the 4960 only has one Ethernet port
4.6.5 Script Files The 4690 IP will comply with the requirements for TFTP Script Files as defined in the Avaya document labeled Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 4602TP.3.1.200.
4.7 Support for Local Procedures The 4690 IP will comply with the requirements for support of local procedures as defined in the Avaya document labeled Telephone Requirements for The Polycom Speakerphone, Issue 8.0, May 21, 2003, Compas ID 95746 as defined in Section 3.2 with the following exceptions:
• Section 4602TP.3.2.500 INTerface control – Is not supported.
• Section 4602TP.3.2.550 LOGging enable/disable – Is not supported
4.8 User Interface The 4690 IP implements a user interface based on elements from the Avaya 4602 and 4620 IP telephones. Every effort will be made to maintain a consistent user experience for existing Avaya IP telephone users. Deviations are dictated by the available UI elements on the Furby platform.
Detailed user interface operation will be supplied in the draft user guide document for the 4690 IP to be supplied to Avaya with the release of the product to Avaya’s interop test phase.
4.8.1 Icon Support The 4690 IP will support the following icons on the LCD. Table 3 – Supported Icons
Soft hold – Indicates that a line is on hold pending a conference or transfer
Hold – Indicates that a line is on hold
4.8.2 LED Lamp States The Furby platform contains bi-color LEDs that are used to notify the user of what state the phone is in. The supported states are contained in Table 4. Table 4 - LED States
Call State LED Status
4690 IP Off All Off
4690 IP Powering On
Red On
4690 IP Idle All Off
Off hook Green On
Dialing Green On
Connected Green On
Mute Red Blinking
Hold Red On
Incoming Call Green Blinks with Ring
4.8.3 Idle Display The following diagram is an example of the idle display. The phone extension will be limited to 10 characters excluding the ‘Ext’ prefix.
4.8.4 Selecting a call appearance The 4690 IP UI supports up to three call appearances with one line of display reserved for each call appearance to be consistent with the 4620 display.
Since the 4690 IP does not have a UI component that is equivalent to the line keys on the 4602 or 4620, the line key on the 4690 IP is implemented by using the scrolling arrow keys to highlight the desired call appearance followed by the select key to select it.
This procedure will be used to:
1. Answer a call when total call appearances exceeds one.
2. Retrieving calls from hold.
3. Placing calls on specific call appearances when there is at least one call active.
From an idle display, in all cases, the first call appearance can be selected by pressing hookswitch button.
The following diagram shows two active calls and a third which is an incoming call. Pressing the down scroll highlights the third call appearance as shown. Pressing the select key answers call appearance ‘c’ and terminates call appearance ‘a’.
The line labeling designation of the letters ‘a-c’ will be applied to the three available call appearances. The display of the call appearances is designed to be consistent with the 4602 call appearance display.
The following is an example of the offhook/dialing display.
a=303
Hold More
Ext 301 10:44am 6/10/03
Drop
When digit collection is completed, the display is updated with information for the called party as shown below by the server
Ext 301 10:44am 6/10/03
a=Simon 303
Hold MoreDrop
During these phone states, three soft key labels are displayed on the lower portion of the display that provide access to the server based feature set. From the initial set of soft key labels, selecting the ‘More’ key allows access to Transfer and Conference. The third activation of the ‘More’ soft key will return the user back to the original soft key menu and in effect, behaves as a toggle function between the Hold/Drop and Transfer/Conference features. Examples below show the available soft key displays.
4.8.6 Call Hold Display The following diagram is an example of a call that has been placed on hold.
Ext 301 10:44am 6/10/03
a=Simon 303
Hold MoreDrop
Retrieving the call from hold requires the user to select the appropriate call appearance as described in Section 4.6.4.
4.8.7 Incoming Call Display The following is an example of the display when there is a incoming call. The ringing icon indicates that Line ‘a’ has an incoming call and the caller information is displayed.
Ext 303 10:44am 6/10/03
a=Travis 301
The 4690 IP can display up to a maximum of 31 characters of call information. These 31 characters include the icon and line name (e.g. ‘a=’).
4.8.8 Transfer/Conference Display While in a call, if the user selects either the Transfer or Conference features, the active call is placed on hold indicated by the soft hold icon. A second line appearance is displayed with the label ‘b=’ with the corresponding off-hook icon.
4.8.9 Server Provisioned Features Server provisioned features can be accessed at any time via a secondary feature menu accessible by pressing the ‘Select’ key.
Arrows on the right side of the display area are shown to indicate that there are additional features available by scrolling up or down. Scrolling through the server provisioned feature list is accomplished with the up and down arrow keys to the right of the display. The currently selection is highlight with a solid black bar and the feature name text inverted. The feature is selected by pressing the ‘Select’ key.
Server responses to feature activations will be displayed on the main UI screen in the place of the extension and time/date display when provided by the server. An examples of this is the Button View feature where the button label will be displayed on the top row of the display if this feature is activated.
Although support of server provisioned features is based on the Avaya document 24204620labels.pdf which requires support for feature button labels of up to 13 characters, the 4690 IP display can accept and display in excess of 20 characters per button label. The actual number of characters will vary depending on the width of the characters as proportionally spaced fonts are supported.
The following is an example of the server provisioned feature display:
Call PickupCall Park
DoNotDisturb
Toggle Swap
Lamp updates to indicate when a feature has been activated will appear on the UI by highlighting the feature label in inverted text.
The user can exit the server provisioned feature list by pressing the ‘Exit’ key at any time.
4.8.10 Local Menu/Options From the idle display, pressing the menu key brings up a local menu similar to the ‘Options’ key on the Avaya 4620. This menu allows the user to change ring tone and display contrast. A third option is available to display system configuration information. No changes can be made to the system configuration from this menu.
5.1 Power Requirements Furby requires AC power and is supplied with a universal power supply that can convert 110/220V (100V in Japan) at either 50 or 60 Hertz to the DC voltage required by the phone.
Country kits are available, consisting of country specific cord kits that connect the universal power brick to local AC outlets.
5.2 Regulatory Standards Requirements The following tables specify regulatory compliance for the 4690 IP Conference Phone.
5.2.1 Regulatory Standards Compliance
Specification Description
Regulatory Compliance
Products shall bear CE Marking indicating compliance with the 89/336/EEC and 73/23/EEC directives, which includes the following safety and EMC standards.
![Avaya ethernet routing switch 2500 series product presentation [level 4 - tdi][1]](https://static.documents.pub/doc/80x56/55758066d8b42adb7e8b50e7/avaya-ethernet-routing-switch-2500-series-product-presentation-level-4-tdi1.jpg)
