Avaya E-169 IP Deskphone Release Readme. This file is the Readme for the Avaya E-169 IP phone R1.0.1 Release.

Transcription

1 E-169 Release Readme This file is the Readme for the Avaya E-169 IP phone R1.0.1 Release. This phone is supported by CM/Aura/SBC and IP Office. The information in this document is accurate as of the issue date and subject to change. Please refer to the Advisements in this file for important information prior to deploying this phone. Overview of E-169 Product This is a simple SIP phone with some unique features. The phone is composed of a base (media station) and a soft client application hosted on the user s own smart device (ios or Android, phone or tablet). The media station has a handset with its own dial pad and small display. The media station also has 6 hands free speakers and 4 microphones to provide an excellent audio experience. The unique feature this media station has is the ability to connect with the user s smart device by either or both USB and Bluetooth. The hosted app on the smart device provides users with a UI to control the media station (separate from the handset controls). The UI provides menus for controlling the setup and registration of the phone, a contact list, a log of recent calls and a large dial pad. The media station can be operated when powered with a provided 12v external power supply unit or by PoE. When the user s smart device is physically connected to the media station, the smart device can be re-charged. Operation in office with CM/Aura and Session Manager is an effective deployment of the phone (both with and without MDA). The phone can also be deployed remotely through the SBC (again with and without MDA). Issued 13 February 2014 Page 1 of 17

2 E-169 Product Features Users should expect to successfully use the basic telephony features of the phone. Users should not expect those features to fully emulate the full suite of features of a 96X1 product. Similarly, users should expect that the interactions with the UI on the app hosted on their smart device should follow much of the intuitive behaviors they are used to on other simple apps on their device. Users should keep in mind that all apps operate a bit differently from one another and different smart devices and their different versions of operating systems also imbue such products with different behaviors. Users will discover the outstanding audio experience both during hands-free calls and while they play music stored on their smart devices and output to the media station via Bluetooth. Please refer to the documents mentioned below. Issued 13 February 2014 Page 2 of 17

3 Documentation for E-169 R1.0.1 The following documentation has been updated to support the deployment of this phone. Avaya E169 IP Media Station Overview and Specification Installing and Maintaining the Avaya E169 IP Media Station Using the Avaya E169 IP Media Station Avaya E169 IP Media Station Quick Reference Issued 13 February 2014 Page 3 of 17

4 E-169 R1.0.1 release Package Content The E-169 First release package points all the files necessary to upgrade Avaya new E-169 IP Deskphone. - Base firmware IOS available at Avaya Apple store, under Avaya Media Station ; please refer to Using the Avaya E169 IP Media Station guide. - Android available at Avaya Google store, under Avaya Media Station ; please refer to Using the Avaya E169 IP Media Station guide. This package contains: o Base firmware E169_7_20_23.bin o Upgrade file - E1x9MSUpgrade.txt o Settings file E169Settings.txt - Release letter - Documentation mentioned above - All open source and its modifications used in this fw Advisements with E-169 R1.0.1 Post upgrade calibration Please Note, this load contains calibration of the device to accommodate the environment. Calibration is expected to occur once after the initial upgrade or in case factory default is performed. The calibration does not require any user action, but may result with some soft sounds from the device on the first minute after he device was upgraded to the new load and rebooted. This is per design and is not expected on next reboots unless factory default is performed. Upgrading the E-169 to the latest release. Please Note, Beta Factory out of box phones currently have load which has software limitations with addressing settings file, therefor and only for the first time users are required to change their current 46xxupgrade.scr file ahead All future FW changes will be handled thru the E1xMSUpgrade.txt file For phones running load , please use directions below. If the phone is running a different load, please refer to Installing and Maintaining the Avaya E169 IP Media Station (also referred below as Admin guide) Customers on-site preparation a. Copy the upgrade file (E1x9MSUpgrade.txt) that is delivered with the beta fw and put it on a designated HTTP server that can be accessed with both TCP (HTTP) AND TLS (HTTPs). b. If this HTTP server also hosts a file called 46xxupgrade.scr, you must append the following lines before the #END clause IF $MODEL SEQ E169 GOTO E169_FW # E169_FW SET APPNAME E169_7_20_19.bin GOTO END # END Issued 13 February 2014 Page 4 of 17

5 GET 96xxsettings.txt c. If the HTTP server does not already have a file called 46xxupgrade.scr, please copy the E1x9MSUpgrade.txt file delivered with this load and rename it to 46xxupgrade.scr. i. This is a 1 time modification to the 46xxupgrade.scr file. ii. All future changes will be made in the E1x9MSUpgrade.txt file d. Configure DHCP option 242 to have the IP of the designated HTTP server under the parameter HTTPSRVR (please make sure to use capital letters only). e. Make sure the settings file you were referring to in the upgrade file (in this example 46xxsettings.txt) resides on that HTTP server. It may be a file shared with other Avaya phone models. A sample minimal settings file can be found with the GA package. Additional possible parameters can be found in the admin guide. *NOTE: for customers that can t change their DHCP settings we can offer an alternative approach. See below Note 1&2 below. f. Put the FW file E169_7_20_19.bin in the designated HTTP server Note 1: If for some user, the customer can t set DHCP 242 option to the designated HTTPs server. They can use the Smart App and put the IP address of the designated HTTPs server in the Alternate Provisioning URL in the Advanced Parameters menu item. Note 2: IP Office Customers must follow the Instructions in Note 1 because the IP Office can t currently host the E169 FW file. Note 3: Other required configuration, specifically SIP Domain and SIP Controller List must be set in the settings file or via the manual admin screen of the APP (SIP Controller might also be set in DHCP option 242). This is a required step to complete the configuration. Headsets Culebra currently introduces limited support for headsets, headset support would continue to expand and improve up to GA and in future releases. Headset jack (even though can be found physically on the device) is not supported for our first release. The following headsets have been tested to work with the phone. Jabra USB 9470 & Jabra USB 9460 Please note: USB Jabra headset must be configured manually as PC Softphone type OTHER in order to work properly (The headset will then present the phone as PC); Headset dialpad is not supported. Chaining The E169 connection to the network while in the office needs to be a direct Ethernet connection. It should not be chained from the PC port of another phone or PC to avoid potential problems with the VLAN. 96X1 phones appear to function well if chain from the PC port of the E169. Note that the E169 does not provide any PoE outbound from the PC port so second phones will need their own power supply units. Using the E169 config file Issued 13 February 2014 Page 5 of 17

6 The config file includes configurations to enhance phone behaviors to Avaya Aura environment. It is recommended to use it even if there are no changes done by the administrator. Please use the recommended settings file that is delivered with this release, which contains all parameters explicitly set to their defaults. Please Note: Phone is saving the last settings configured. In case you change any settings and then comment it out or remove it from the settings file or direct the phone to a different settings file which does not contain this value the last configured setting remains and the phone does not go back to the default. In case you change any parameter and later on wish to revert it back to its default, please do so explicitly by configuring it back to its default value. It is not recommended to use a shared settings file with other non-e169 Avaya phones, in case for some reason you have done so, please note that once marking out a parameter the behavior and result is different between E169 and other Avaya phones (such as 96x1, 96xx etc). Anyways executing Factory reset on the phone, will make all parameters return to its defaults. Issued 13 February 2014 Page 6 of 17

7 What s new with this release This release contains the same functionality as R1.0 but also includes a resolution to an issue that appeared on specific E169 devices exhibiting popping sound during audio playing. This load contains a resolution to that continues popping. In case you have previously experience continues popping, and still encounter the same issue after the upgrade, please leave the device completely idle for an hour \overnight (no smart device connected, no device connected over Bluetooth and no audio playing\calls). The problem should be resolved after that time period. If you still experience any issue, please contact Avaya. Unresolved issues with this release The following table includes unresolved issues with this release which were known as of the issue date of this document. User interface 938 Please Note, this load contains calibration of the device to accommodate the environment. Calibration is expected to occur once after the initial upgrade or in case factory default is performed. The calibration does not require any user action, but may result with some soft sounds from the device on the first minute after he device was upgraded to the new load and rebooted. This is per design and is not expected on next reboots unless factory default is performed. 598 Please note that call log history is being saved in the base. In case you logout from your extension and another user dock in his phone, he might view your call log. 744 If you are currently on mute and your call is being transferred by the far end, after the transfer is completed, mute will go off and the new call is no longer muted (as indicated by the application and base). This may defer from other Avaya endpoints 506 When using Android device, there is no headline to indicate that an active call is a conference call. Please pay attention once merging calls into a conference. 484 Handset hook switch can also interact with magnets in the base station itself. Users need to be aware that laying the handset directly on top of the base station can have the same result as placing the handset on its Issued 13 February 2014 Page 7 of 17

8 magnetic cradle. 27 If handset is resting upside down on magnetic cradle such that display and keypad are face up, user may see voic number on the handset display while the media station dials from the voic icon. In order to enter the password from the handset - please lift the handset fully from the cradle. 86 Users should only use one Avaya app at a time. User can get BT for the speaker and mike from their smartphone while using the Avaya Flare or Mobile 1-X client. But should not attempt to have both apps operational on media station at same time. 572 Once putting a call on hold and getting an incoming call, the phone will not play second incoming call alert tone. The user will have clear indication of the second incoming call on the application UI / Handset UI. 436 IOS: Volume button on iphone will not control volume of E In order to see Directory Number on iphone App, user is required to swipe left to right on the clock at the top of the app. On ipad, the Directory Number is visible on the home screen. 500 Placing a conference call on Hold is not supported. 431 In case of enabling the SRTP setting option from Advanced Parameters signing out and then signing in with another extension this option goes back to default and is then disabled. If desired, please enable it again after login to another extension. 492 Android Samsung: When plugging in and out the same device many times, connection to the base may be lost. This is a bug with Android. In order to recover, you can kill and re-launch our Android application. The original bug for android OS 4 years ago and patch proposed by the community but never integrated in android (4.4.2 does not have it) When the contact exist on both icloud and Google and merged automatically by Apple, dialing a number might result in calling a different number of the same contact. Issued 13 February 2014 Page 8 of 17

9 Clear indication of the number is seen on screen. Workaround: Remove the contact from either google or icloud or recreate it as complete 534 Once user disconnect and reconnect the handset in between calls and using the handset, application UI might reflect wrong indication of the speaker soft key Workaround: In order to refresh the phone when in such state, please reboot the phone 65 User cannot open settings menu page after selecting the Proxy option on ipad mini. Workaround: upgrade to IOS 7 4 On rare cases, in case of rebooting the device while an ipad is connected, the extension might not be visible on the application, but rather only seen on the handset. This is ipad limitation, in order to work around it, user may toggle Bluetooth on and off to recover visibility of extension. 623 IOS: In case of changing voice mail number, application will not refresh correctly until killing it and re launching. All functionality works correctly you will be able to get calls and make calls. 556 When getting an incoming call during an handset call and selecting Hold + Answer, after ending the second call and un-holding the first call, voice path moves to the speaker User can then switch back to handset manually (using application\phone button) 599 When dialing FAC starting with *, it is shown on call log as Unknown (no possibility to redial it from Redial option) 637 In case wishing to change the language in IOS, Please do so through IOS settings - the parameter that takes affect is under international using Region Format and not language. 608 Current daylight savings date plans for future years, as published on May 2014 are embedded within the phone fw. In case any country will change its daylight saving time, a new fw with an update to that date will be required. If this were to happen in your local, please contact your admin and Avaya as soon as you know. 702 Check update button on the application may not Issued 13 February 2014 Page 9 of 17

10 trigger fetch of the upgrade file at times Workaround: Trigger will be done by preconfigured timer set by administrator. You may also reboot the phone to trigger an upgrade. 715 When creating a conference call by adding 2 parties, in case of pressing end button on the handset, only the last call added will be dropped. If you press it twice, both calls will be ended. Workaround: In case you would like to hung up both calls, please do so from the application or press the end button on the handset again. 717 When getting a second incoming call and answering using Hold+Answer button, pressing call button on the base will end both calls. If you would like only one call to be dropped, please do so from the application or the handset 718 IOS: In case of plugging in\out the ipad several times, incoming call alert might not be seen on the application. You would still see an indication on the base and hear the incoming call ringing. This is a limitation on IOS expected to be resolved once IOS 8.0 is released. Workaround: User will need to kill the application and launch it again or reboot the base in order to sync the application to show incoming call indication again. 723 Daylight savings time for each country is embedded within the Avaya Media Station application. In case of daylight savings change that occurred after the release of this version, you will need to adjust your device manually once you wish the new daylight savings date to take effect and reflect on the Avaya Media Station application. You can do so by changing the time zone of the smart device to a country with the new offset. 736 Please note mute is correlated with a current call only. When transferring a call during mute, when dialing the second party that call will not be muted. This may defer from other Avaya endpoints 739 Please note when pressing call icon under the application s contacts, the call will go through GSM and not as a SIP call. In case you wish to dial a SIP call from the contacts, please do so by pressing the phone number and choosing a SIP call. Issued 13 February 2014 Page 10 of 17

11 When adding a second call, the call will go through SIP or GSM, depending on the way dialed if dialed through the dialer, it will go through SIP; If dialed from contacts it will be the same as mentioned above 741 Mute indication is not synced with the base in case of a GSM call. In case of using the phone as a speaker device and placing the call on mute using your dialer this won t be reflected in the base mute indicator. In case of muting the call using the base mute button, this won t be reflected in your dialer. Anyways the call will be muted, regardless of the way you chose to mute it. Please refer to the dialer\ base indication according to the one you ve used to mute the call to know it s current status. 751 E169 does not accept octothorpe (# sign) as part of the dialed string when initiating a call. E169 do not support using # as end of dial terminator as an indicator to dial the number, users should use the equivalent operation by pressing the green Send button. E169 do not support staged dialing where the phone dials numbers after the # after the call is answered BT 468 After performing factory reset on the base, BT pairing to smart phone (specific Samsung models) may not work. Workaround: clear BT subscription on the smart phone 449 Samsung S3: connection lose or incorrect BT indication had been seen. This is an open bug with Samsung. As a workaround, when noticing this, turn Bluetooth Off and On again. 697 When using Android S# device, in case of disabling BT connectivity from the smart device (i.e. unpairing) during an active call, the call may drop. Please do not disable BT during a call with this smart device. 627 When E169 is connected via POE, a smart device is docked via USB, ringing & alert & music volume are set to maximum and at the same time user initiate Bluetooth pairing to the device the device may reboot due to high power consumption (depending on POE switch configuration). Workaround: User may avoid all the above actions Issued 13 February 2014 Page 11 of 17

12 simultaneously or may connect the device via an external power supply instead of USB to avoid this. USB Headset 465 Only the following capabilities will be support when using Jabra 9460/70 headset: Answering a call. Ending a call. Volume control + mute. 713 When connected via headset, in case of pressing mute during ringing mute will not function correctly during the following call. There may be cases in which the base and application will show the mute led lit, as was pressed during ringing, and the call will be muted when using Speaker or handset, but the call won t be muted through the headset. Workaround: When using headset, please refrain from pressing mute during ringing. If that was done please do not use mute on the following call or switch to Speaker/Handset in order to use mute. 619 On some occasions, when on headset call, getting an incoming call and pressing End+Answer, answering the second call may fail. 620 Adding a call when on active call with Jabra headset may fail. Please refrain from adding a second call on this setup or switch an audio device in order to do so 442 Once going out of Bluetooth range and coming back, features activated in the base (such as mute) will not be reflected on the application UI 422 Some Samsung devices might appear as if not charging when connected to USB, although it charging no in full capacity. Extra info: E169 provides up to 2A/5V to tablets, max 1A on POE. When Samsung detects that it is charging, but not on maximum capacity (tablet decides to charge at -500ma) red X might be seen on the battery and might appear not to be charging. It might take several hours without the screen activated to charge even 1%. There is enough power however to operate the device even if it is not charging well. Samsung galaxy tab 2 refused to charge due to a problem on the tablet itself. Look at Galaxy tablet. 413 Please note, only base station volumes are reported on Issued 13 February 2014 Page 12 of 17

13 the UI of the smart devices. 405 In case of configuring several codecs behind SBC, if any issues are seen when transferring a call from E169 to another phone, please contact Avaya to verify the configuration IPO 509 FW upgrade thru IPO is not supported. Please refer to upgrade procedure in the admin guide, by using an external http server (not IPO) While all files (upgrade, settings and fw) may be placed in the external http server. If desired, IPO users may use IPO to serve the settings and upgrade file and the external http server to serve the fw.bin file only. In that case the phone should point to the IPO as an http server and customers are required to perform the following change in the upgrade file so it will then direct the phone to the binary - remove APPNAME parameter and replace that with SET DOCK_MANAGEMENT_SERVER externalhttpserver.com/<current_e169_binary_name> If this is desired, please use the following procedure: 1. Install an external http server and upload to it the E169_7_20_18.bin file delivered with this package 2. In E1x9MSUpgrade.txt, please change SET APPNAME E169_7_20_18.bin To SET DOCK_MANAGEMENT_SERVER put your external HTTP Server IP or name>/e169_7_20_18.bin This should be your new E1x9MSUpgrade.txt IF $MODEL SEQ E169 GOTO E169_FW # E169_FW ##SET APPNAME <current_e169_binary_name> SET DOCK_MANAGEMENT_SERVER http server.com/<current_e169_binary_name> GOTO GET_SETTINGS # GET_SETTINGS GET E169settings.txt GOTO END # END 3. Upload E1x9MSUpgrade.txt and E169settings.txt to IPO Issued 13 February 2014 Page 13 of 17

14 676 For IPO users: On IPO main System tab there is a check box Avaya HTTP clients only. Enabling this check box is not supported by E169. If enabled and attempting to use IPO as an http server - you may see in the HTTP trace the following error - HTTP server allows Avaya Clients only. Workaround: Customers must deselect Avaya HTTP clients only and save the config. Administration 591 Phone is saving the last settings configured. In case you change any settings and then comment it out, remove it from the settings file or direct the phone to a different settings file which does not contain this value the last configured setting remains and the phone does not go back to the default. Please use the recommended settings file provided with this release which contains all parameters explicitly set to their defaults. In case you change any parameter and later on wish to revert it back to its default, please do so explicitly by configuring it back to its default value. It is not recommended to use a shared settings file with other non-e169 Avaya phones, in case for some reason you have done so, please note that once marking out a parameter the behavior and result is different between E169 and other Avaya phones (such as 96x1, 96xx etc). Anyways executing Factory reset on the phone, will make all parameters return to its defaults. 707 Upgrade is not supported from HTTP servers which does not have range support. Such may be some flavors of MVIPTEL or IPO as HTTP server, for example. An indication to this would be that the phone is requesting for the binary, but not able to download it fully and complete the upgrade. Workaround: Enable range support on the server, if possible; Or use a different HTTP server for the upgrade. 730 LLDP is not supported. Please do not try to configure VLAN tagging through LLDP but use DHCP 242 option or settings file in order to do so. 607 In case this is a phone from the factory with an early load (prior to ) it may have an issue with VLAN tagging which is resolved in the GA load Users are obligated to upgrade to a GA version prior to usage - If this issue causes any upgrade problem in your environment, work around is to make sure the path in HTTPDIR is in format "HTTPDIR=/xxxxx" and the L2Q information are present in the first provisioning file downloaded 445 After the far end hang up the call, you will hear 5 tones Issued 13 February 2014 Page 14 of 17

15 as an indication 550 After performing deny service from SMGR and getting the phones to subscribe to the second to the BSM and then performing "Accept new services" on SMGR while the phone is on active call, phone moves subscription to the primary SM. No limitation is caused to the user. Workaround: To avoid this, do not perform Accept new services on SMGR while there are active calls. 529 If E169 is set with secure media set to mandatory, any involved network elements including SBC if must be configured such that the basic SDP offer uses SRTP. E169 does not support the SIP Capability Negotiation primitives. 581 Phone is downloading certificate after every polling period. This is expected in order to handle any changes done in the certificate file. If there are no changes from previous deploy, no farther actions will be taken. 615 In case of having 3 IP addresses configured as Proxy servers, in case of deleting the third proxy configured from the application proxy menu, the media application will exist. Please re-launch the application and continue your activity, your changes will be saved anyways. 577 Issues might be seen when trying to fetch upgrade and settings file via HTTPS Please use HTTP for these procedures Issued 13 February 2014 Page 15 of 17

16 Appendix 1 New/Changed E169Settings.txt parameters This is a new release, please refer to Installing and Maintaining the Avaya E169 IP Media Station guide to view all relevant parameters. Issued 13 February 2014 Page 16 of 17

17 License Agreements Third Party Notice for E169 version 1.0 Third Party Components. Certain software programs or portions thereof included in the Software may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those Products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation, readme file, or on Avaya s website at: or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components. Please use the following direct link to view full Notice file and relevant licenses to our product You may also view the relevant Notice file on each application menu (Android/Apple & including Base). On the application, please go to settings Licenses; Under Application you would see the relevant application notice file, and under Avaya Media Station you will see the base s. Issued 13 February 2014 Page 17 of 17