This action might not be possible to undo. Are you sure you want to continue?
Date: June 7, 2010
Avaya one-X Deskphone SIP for 9600 Telephones Release SIP 2.6
This file is the readme for the Avaya one-X™ Deskphone SIP Edition release 2.6 for 9620, 9620C, 9620L, 9630, 9630G, 9640, 9640G, 9650, and 9650C model IP Telephones. This readme file describes the contents of the Release 2.6 software distribution package. Avaya one-X® Deskphone SIP 2.6 is software for the 9600 IP Telephones that supports the SIP protocol. This release is required by and should be use ONLY with Session Manager 6.0 and Communication Manger 6.0. This release should NOT be used with SES or any release of CM prior to 6.0 This firmware package is recommended for the setups having Avaya Aura™ Session Manager 6.0 and Avaya Aura™ Communication Manager 6.0 environments .
New features introduced as part of Release 2.6
Setup Environment Feature Feature description
Common Feature List Applicable for all CM/SES,CM/SM Setup
All CM/SES/SM setup Updated LLDP support Updated handling for LLDP MED Network Policy TLVs with Application types 1 and 2 or with a zero value improves inter-operation with recent releases of Cisco IOS. Avaya one-X Deskphone SIP shall download information from PPM using HTTP 1.1 so that a single connection is used for all downloads during the phone’s login sequence. The phone can identify the type of registered proxy server (e.g., SES/Session Manager/Branch Session Manager/Generic proxies
All CM/SES/SM setup
Support HTTP 1.1 for connection reuse
All CM/SES/SM setup proxy
Identification of the type of
Copyright Avaya 2010 All rights reserved Page 1 of 22
96xx Release R2.6 Readme
such as Audiocodes, Cisco 2811 ISR, I55). All CM/SES/SM setup MWI Added Support for third-party When used with CM 4.0+, Deskphone SIP shall properly handle a PPM messages allocating one or more autmsg-wt buttons and, when an MWI notification is received for other than the primary extension, sets the Message Waiting Indicator on the corresponding button.
Feature List Applicable for CM 6.0 environment
Requires CM 6.0 Call pickup alerting. When used with CM6.0+, Deskphone SIP alerts (ring or flash) when a phone in a provisioned call pickup group alerts.
Requires CM 6.0
Improved Call Unpark behavior
When used with CM6.0+ and either SES5.2 or SM6.0+, a call unpark button should only appear on phones provisioned on CM or SMGR. Avaya one-X Deskphone SIP R2.6 shall support Direct Media as supported by CM 6.0 and later. Avaya one-X Deskphone SIP shall support SDP capability negotiation as defined by draft-ietf-mmusic-sdpcapability-negotiation-10.txt and supported by CM 6.0 and later.
Requires CM 6.0
Support SIP Direct Media.
Requires CM 6.0
Support SDP Capability Negotiation.
New and Enhanced features Applicable SM 6.0
Requires SM 6.0 Handling of a redirect response to a REGISTER request. When a user is moved from Session Manager #1 to SM #2, if a phone tries to register the user on SM #1, it responds with a redirect to SM #2. This means that a user will be able to login after the home SM is changed, but before the information is propagated to
Copyright Avaya 2010 All rights reserved Page 2 of 22
Without this change.96xx Release R2.0 Setting of voice mail destination can be set through PPM set in the System Manager The voice mail destination number can be set in System Manager for individual users instead of administering it in the settings file. An extended call pickup button will appear on phones provisioned for extended call pickup on CM. network or server failure. Avaya one-X Deskphone SIP shall simultaneously register with the three highest priority registrars specified by any of the supported provisioning mechanisms.” the phone accepts an incoming INVITE from any of its Available Controllers. Requires SM 6.0 Improved user-friendly phone number display format For example. a telephone number such as “5381234” in the display portion of PAI or Contact header might be formatted in a more readable fashion as “538-1234” before it is displayed on the phone.0 Support simultaneous registration with up to 3 proxies. When the SIPREGPROXYPOLICY parameter is “simultaneous. Requires SM 6. an incoming call would be dropped if it is received after a controller switch happens while a user is on another call. Requires SM 6.0 Support geo-redundant Session Requires SM 6.0 New extended call pickup behavior Copyright Avaya 2010 All rights reserved Page 3 of 22 . Requires SM 6. Ensures that a telephone user can always receive incoming calls even when another call is active and the call controller has changed due to maintenance. regardless of which one is active.6 Readme System Manager.
bin When the phone is failed over to a non-Avaya secondary controller (AudioCodes/Cisco): We expect all the phones in the environment are operating in same transport protocol.96xx Release R2. There may be a few call-based issues if the phones are using different transport protocols.avaya. Copyright Avaya 2010 All rights reserved Page 4 of 22 .124-20. the recommended firmware revision. 5. the minimum firmware revision is c2800nm-ipbasek9-mz.6 Recommended SIP Transport Protocols SIP Proxy / Phone Connection Type SES (as primary controller ) Avaya Session Manager primary controller) (as UDP Supported Supported Supported TCP Recommended Recommended Recommended TLS Recommended Recommended Supported AudioCodes MP-series analog and BRI gateways (as secondary controller ) Cisco 2811 ISR (as secondary controller) I55(as secondary controller) Supported Supported Recommended Recommended Not supported Not supported Teldat Vyda gateway Supported Recommended Supported Table of Phone Connection Types for Survivability Configurations ‘Recommended’ means minimal latency in the detection of a Failover condition The Audiocodes SIP gateways tested for interoperability are the MP114 and MP118.005.502 --. is available at the Avaya Support Site location http://support. the name fields are reversed.010.6 Patch releases merged in this release R2.60A.YA2.com/css/appmanager/public/support/Downloads/P1341/C20090710164 61675250960 The Cisco gateways tested for interoperability are the Cisco [ISR] . and Contacts Details from the Call Log display name as First Name R2.506 Cut-thru delay audio Known Limitations of Release 2. R2.6 Readme Field Issues Addressed in Release R2.When adding Contacts from the Call Log.504 ---96XX SIP not setting DSCP on 200 OKs from UPDATEs.
As long as the SIP R2. 9620C/9620L-. the Emergency Soft key is displayed even though the phone is not able to connect calls.1 or greater Always provision ‘None’ encryption (setting 9) as one of the encryption selections in the settings file and on CM NAT 96xx SIP telephones should not be provisioned behind a NAT with private network addresses when the CM and SES switching fabric are provisioned on a different network. Workaround: This issue can be avoided by not logging in with different extension after failover. Phone will not play dial tone during its in a state of detection of Network failure condition Workaround: Wait for 20 seconds When two phones having two different primary controllers and when one of the phone whose controller is available on active call. and if there is failure of its primary SM. Known Issues of Release 2.0. Workaround: Clear the phone and then reprogram it. and the user attempts to bridge onto the BCA. then the phone detects failover and registers with the secondary server and the user logs out and logs in as a different user. Copyright Avaya 2010 All rights reserved Page 5 of 22 .0.0 little app.6 big app is loaded into 9620C and 9650C phones that already contain a SPICE 3. If the customer has an EAP-TLS network /and OR little app is not 3. Sometimes Phone doesn’t retain value of group and SSON parameter while upgrading from 2. then the BCA may appears as lock up.0 boot file to load SIP firmware on 9620C/9620L. tries to hold and resume while the other controller is not available in network. If a phone with a BCA that is alerting.6 Readme SRTP The Avaya Gateway firmware version must support SDES SRTP Crypto suites must match Requires CM 4. HTTP Server a phone can retain a HTTPS file server setting set by DHCP after DHCP is later set to “No” in CRAFT menu. Workaround: Wait for failover to occur.6 binary.then the customer need to make sure that they have the S3.6 or previous releases : If the user makes changes in the options and settings when failover has not yet been detected.6 and Auto failback policy is recommended.96xx Release R2. Failover Issues When the phone is in Failover and not connected to a controller. the changes are displayed to the new user. it may be observed sometimes as No talk path or one way Audio Workaround: Drop the call If phone is alerting during the state of Network failure detection for primary Controller then the phone will be failed over to secondary after delayed time of unto three minutes after answering the ringing call. Recommended Failback Policy Admin failback not recommended in R2. there shouldn't be a problem.6 Issues Observed specific to 2.
rotating web displays. Workaround: Admin failback not recommended in R2. Workaround: Do not use the customized logo image on the WMLIDLEURL page. Formatted Avaya long form number is displayed instead of Avaya Extension short form on SBM24 and aux buttons on 9650 When the phone is unlocked during an active or alerting call then user cannot invoke any applications. If phones are found hung as a result of rotating web displays. then this will not be get reflected on the phone. Audio Issues Sometimes distorted noise is sent from the phone Direct IP turned to No on CM Workaround: It’s recommended to keep Direct Media ‘ON’ in Communication Manager. No audio path with G. reboot them. and it will again get reflected as administered on the phone. UI and application issues When AutoDial is configured on CM.726 codec on non shuffled calls Workaround: Recommendation is to have shuffled calls in case of G. When SRTP CAPNEG is enabled on CM and phone and if alerting call is answered very quickly and this happens 3-4 times then there is no more voice path on the phone. If the web screen saver (setting WMLIDLEURI) uses the same image file as the custom logo. • Workaround: Dial with short form number if dialing with Long form is not allowed. If users are on active call originated on secondary SM or BSM then manual failback triggered during the active call won’t work and another trigger needs to be sent after the calls end causing the phones to failback to primary SM. Workaround: Do not use timed. Phone is displaying long form number in redial list even if user dials the short form number. Not able to retrieve 250 contacts from PPM since PPM doesn't send gCL response. If the contact Nickname been added and modified. Workaround: Restart the phone to resolve the issue.6. Workaround: Session Manager Recommendation is to save only 50 contacts in contact list. Incorrect character display inside Calendar meeting requests for Hebrew and Arabic languages.726 codec.6 Readme Workaround: log off and log back in again. Workaround: Drop the call and now the applications can be invoked properly. Simultaneously Holding the call and resuming it during the state of Network failover detection phase and when the secondary server is not been detected (Limbo State ) will bring in the phone in weird state and failback will not happen.96xx Release R2. Copyright Avaya 2010 All rights reserved Page 6 of 22 . the Web screen saver page is not displayed properly. Workaround: Phone require to logout and login back. the “Edit” softkey may not be displayed for the Busy Indicator feature immediately after editing the label for the AutoDial feature Workaround: Navigate out of the A-menu and then return – the “Edit” softkey will then be displayed Long labels on the SBM button module may be truncated in the middle of a displayed character Workaround: shorten button labels on the SBM Rotating Web displays used as screen saver can cause the phone to hang over long time periods.
96xx Release R2. Public Numbering Call Appearance will not activated at principal if Bridge Appearance Button was pushed on NotPrincipal station Workaround—Configuration of the Avaya Handles with Avaya SIP type recommended on System Manager Copyright Avaya 2010 All rights reserved Page 7 of 22 . and if the user has invoked (enabled) features such as EC500. Audix-Record is not displayed on aux button in 9650/9650C phones. Workaround: Drop the call and now the applications can be invoked properly. Call park feature invoked for active call on Bridged Call Appearance is not working. If any user is logged in with enterprise canonical long form number for which there is short form mapping on CM.6 Readme Features Related Issues Assigning number to unlabeled autodial configured feature gives error beep and not allowed message on the top line and hence not able to assign the number when phone is registered with Session manager. then the feature indication status is available on phone . Workaround: Use the configured for Audix Record. Configuration Issues Any configuration parameter that is set through the CRAFT menu to its default value will be ignored and the value set via DHCP or 46xxsettings file will be used. will show deactivated after logout/login. Workaround: If the user invokes the feature twice. Sendcalls. Auto Call Back feature invoked by holding the active call received on bridged call appearance does not work. set them in DHCP or the 46xxsettings file. When the phone is unlocked during an active or alerting call then user cannot invoke any applications.This problem is not been observed when the user is log in with short form. Workaround: To explicitly set default values for parameters.
2 Features from prior SIP phone releases that have dependencies on CM and SES versions are shown in the table below: Prior SIP Release Feature Compatibility Matrix Visiting User (Applicable for SES environment only) Extend Call SRTP All features other than those noted in this these tables Minimum CM Version Required 5.96xx Release R2.0 5.6 depend on recent CM and SES versions as shown in the table below.1 5.0.6 Readme Feature Compatibility Matrix for Communication Manager (CM) and SIP Enablement Server (SES) A number of the new features in Release 2.0 Minimum SES Version Required 5.2 5. Release 2.1 4.1.0 5.0 n/a 4.0 Minimum SES Version Required 5.0 5.6 Feature Compatibility Matrix SBM-24 button module – Feature button assignments and operation SBM-24 button module – Autodial assignments and operation SBM-24 button module – Bridged Call Appearance (BCA) and Call Appearance (CA) operation Auto Answer Deactivation of Call Forward On Busy Do Not Answer Minimum CM Version Required 5.0 Basic steps for setting up 96xx SIP telephones: The basic steps for setting up 96xx SIP telephones: Copyright Avaya 2010 All rights reserved Page 8 of 22 .2 5.0 5.1.0 5.1 5.0 4.2 5.
9640SIP. specified in TPSLIST.Proxy2:<port>.transport=tcp.conf) Copyright Avaya 2010 All rights reserved Page 9 of 22 . All proxies are assumed to support the same domain.wml then the TPSLIST should contain 192.transport=tcp SIP_CONTROLLER_LIST (setting through Windows DHCP server): In DHCP scope option set as SIP_CONTROLLER_LIST="Proxy1:<port>. port. (e.96xx Release R2. SIP_CONTROLLER_LIST: This parameter consolidates SIP controller parameters for IP address.5 and later for enabling PUSH functionality on the phone.: if the push URI is: http://192. SIP_CONTROLLER_LIST (setting through Linux DHCP server (httpd.transport=xxx” In the later case. the first controller will take default port (5061) and transport type (TLS) and second controller will take assigned values in the SIP_CONTROLLER_LIST. appropriate DHCP scope needs to be provisioned on the phone. 4620SIP and for CM 5.g. OR: SIP_CONTROLLER_LIST="Proxy1.proxy2:5060. And xxx and yyy are the transport protocols of respective server. The parameter setting should be a list of controller information where the format for each controller entry is “host[:port][. The string representing the Trusted server list.transport=yyy" Where: Proxy1 is the primary SES server address and Proxy2 is the secondary SIP server address. Setting up Primary and Secondary Controllers The minimal settings required for provisioning SIP Proxies are: SIPDOMAIN: The domain name that the phones operate in.transport=xxx.12.63:80 that is it includes the port number).63:80/display. and transport protocol into a single configuration parameter.9630SIP. The following changes must be done for R2.transport=xxx]” Example: SET SIP_CONTROLLER_LIST proxy1:5060.168.168. Recommended configuration is only long form should be configured on system manager and user should register with only the long form.12.Proxy2:<port>.2 and later provision as 9620SIP. should contain a server specification that completely matches the server specified in the push URI. if DHCP is used in the network.1 and prior releases provision as -9600SIP set types ) Optionally.6 Readme Define an HTTP Server to host the telephone firmware downloads and settings files Define a list of SIP Proxies Define SIPDOMAIN Define a Time Server (SNTP protocol) and parameters Provision CM/SES for 96xx telephones (For CM 5.9600SIP set type .
the Copyright Avaya 2010 All rights reserved Page 10 of 22 . RDS_INITIAL_RETRY_ATTEMPTS: Parameter that indicates how many times PPM adaptor should try to download from PPM before giving up on connecting to the PPM server.6 Readme In below examples Proxy1 is the primary SES server address and Proxy2 is the secondary SIP server address.xxx.5 release. the phones will never autonomously attempt to leave a working server.e. which means that the support for AST will be determined automatically. DISCOVER_AVAYA_ENVIRONMENT: Indicates how server support for Avaya SIP Telephony (AST) capabilities will be determined. When using Multiple SIP CONTROLLERs .transport=t cp. If set to 'simultaneous'. the phones will only register to one server at a time. When using single SIP CONTROLLER "HTTPSRVR=aaa.SIP_CONTROLLER_LIST=\"xxx.aaa. if the phones detect that a disabled primary server has recovered.aaa. Please leave this parameter to its default value i.1.xxx:5060. Setting DISCOVER_AVAYA_ENVIRONMENT to "0" (NO) means that the SIP proxy server does not support AST. Further settings are optional: CONFIG_SERVER_SECURE_MODE When the phone is using HTTPS to communicate with PPM. FAILBACK_POLICY: This is a string 'admin' or 'auto'.aaa.xxx.SIP_CONTROLLER_LIST=\"xxx. The default value is 15 attempts and provisioning is through the settings file and can be set in the range of 1 to 30 attempts.aaa.yyy. 'alternate' or 'simultaneous'. If set to 'alternate' (the default). 0 for use HTTP 1 for use HTTPS(default) 2 for use HTTPS if SIP transport mode is TLS.yyy:5060. use HTTP Note : Default value is 1 in SIP 2. SIPREGPROXYPOLICY: This is a string.transport=t cp\"".aaa. This parameter applies only to 96xx model phones.xxx:5060. otherwise. And xxx and yyy are the transport protocols of respective server.96xx Release R2.xxx.yyy. The default value is 2 seconds and provisioning is through the settings file and can be set in the range of 2 to 60 seconds. they will attempt to register to the highest priority available controller in the SIP proxy server list. Only proxies entered through the Craft menu can be deleted. If set to ‘admin’.Specifies the communication mode used to access the configuration server.we would have to use '\' as an escape character for quoting the value inside the already quoted name = value pair. Admin failback needs to be invoked from the system manager for that particular user. eg.aaa. o Note: When viewing the SIP proxy list from the Craft menu.yyy. The default value is 600 seconds and provisioning is through the settings file and can be set in the range of 2 to 3600 seconds.xxx. RDS_MAX_RETRY_TIME: Parameter that indicates the maximum delay interval before giving up on connecting to the PPM server.6 and 0 in SIP 2. For Linux. please follow below examples "HTTPSRVR=aaa. it may contain additional proxies obtained from other data sources which cannot be deleted through the Craft menu.transport=tcp\"". When set to 'auto' (the default). it reuses the connection per HTTP 1. The default setting is "1" (AUTO). ‘Auto’ RDS_INITIAL_RETRY_TIME: Parameter that indicates the initial delay for a retry for connecting to the PPM server. and will stop using the Secondary.
accessed through Craft procedures.96xx Release R2.txt file supports the inclusion of one setting.## SET SDPCAPNEG 1 Invalid Proxy Settings If an invalid proxy server address is programmed on the phone (via the administration screen. The valid proxy values can be re-programmed by adding them to the settings file before the reboot.6 onwards the default value if CONFIG_SERVER_SECURE_MODE is 1 indicating that PPM download will happen over HTTPS. or SM-nonAST. then phone sends 100rel in Supported header and responds any 18x response with PRACK. The official documentation for this setting is as follows: Copyright Avaya 2010 All rights reserved Page 11 of 22 . The default value for SIMULTANEOUS_REGISTRATIONS 3 for 2. The default value for this SDP CAP NEG is 1 for 2. with respect to DTMF being sent in-band or out-of-band. SEND_DTMF_TYPE. or through phone programming from the CRAFT menu during the boot. rebooting the phone is not sufficient to recover as the phone will continue to attempt to contact the invalid proxy. SDPCAPNEG: Controls the SDP capability negotiation. press the “Program” soft key to present the CRAFT menu. Procedure for erasing an invalid proxy server address: During the re-boot sequence.6 and above releases.6 and above.6 and above. or via the settings file) and a login is attempted and cancelled.5 releases respectively. When we set it to default value as 1. The default value for ENFORCE SIPS URI is 1 for 2. that characterizes the endpoint’s DTMF treatment.6 and 0 for 2. The range is from 1-3. So this disables the reliable response capability on the phone. o Recommendation is alternate for SES environment environment recommendation is simultaneous or SM-nonAST. select the CLEAR option to clear the phone values and reboot the phone. 100REL_SUPPORT: If we set 100REL_SUPPORT 0 then phone doesn't 100rel in Supported header and so in case of any 18x response phone doesn't respond with PRACK. o Recommendation is alternate for SES environment environment recommendation is simultaneous. ENFORCE_SIPS_URI: Controls the enforcement of SIPS URI with SRTP. SIMULTANEOUS_REGISTRATIONS: The number of Session Managers in the configuration that the phone will simultaneously register with. The range is from 0-1. For SM Note: From 2. The range is from 16-3600 seconds. For SM ASTCONFIRMATION: Sets the time that the phone waits to validate an active subscription when it subscribes to the "avaya-cm-feature-status" package.6 Readme phones will maintain an active registration on all provisioned servers which is only supported for SM environment. The default value for ASTCONFIRMATION is 32 seconds for 2. Specification of SEND_DTMF_TYPE Setting The 46xxsettings. The range is from 0-1.
Specification of SYMMETRIC_RTP Setting Beginning with 96xx SIP Release 2. Communication Manager (CM) Compatibility and Encryption SRTP is not enabled in the endpoints.txt file supports the inclusion of one setting. SYMMETRIC_RTP. As noted earlier.96xx Release R2. This new setting allows the relaxation of the port restriction so that the ports on each end of a session can be asymmetric. Please note that this setting has no influence on the IP address on either end of the RTP stream. or out-of-band. The endpoint will enforce the symmetric restrictions on RTP streams when the SYMMETRIC_RTP is set to 1. The variable is named SYMMETRIC_RTP. as Regular audio. If this setting is not included in a setting file. The endpoint will always send DTMF out-of-band. The IP address must be the same no matter which setting is chosen for the port value (symmetric or asymmetric). using RFC 2833 procedures. If this setting is included in the setting file with a value of 0. SRTP is supported. no matter what setting is provisioned for SEND_DTMF_TYPE2 (1 or 2). 1 for in-band Please note that. which characterizes the endpoint’s treatment of RTP port security. It can take on two values: 0 and 1. as in: SET SYMMETRIC_RTP “0” The endpoint will relax the restrictions on the RTP streams so that they can terminate on differentlynumbered ports on each end of an RTP session. it is recommended that the CM must be provisioned with the SRTP IP codec policy of: 1-srtp-aescm128-hmac80 9-none Copyright Avaya 2010 All rights reserved Page 12 of 22 . out of the box. Once this has been verified SRTP may be provisioned in the following manner. following the scheme specified in IETF RFC 2833. the SIP 96xx endpoints enforce the restriction that ports be symmetric. For SRTP operation. the 46xxsettings. but requires that the gateway software versions also support SRTP (not all do). That still cannot change after the establishment of the session. By default. as in: SET SYMMETRIC_RTP “1” This is the default behavior (which pre-dates 96xx SIP Release). it behaves as though it were included with a value of 1. Please note that this relaxation is only true for the port in the RTP stream. or not included in the setting file at all.0. the endpoint will treat DTMF as though 2 were specified for this setting.6 Readme ## DTMF Transmission Method ## ## ## ## Specifies whether DTMF tones are sent in-band.
Note that this file is designed for environments in which all 9620.6 SIP. 96xx SIP Release 2. .9620C.9" And.6 SIP boot application – The 9600 R2. the phone allows either SIP URI or SIPS URI for incoming SRTP media encryption calls and uses only SIP URI for outgoing SRTP media encryption calls. DO NOT EDIT this file.com/css/P8/documents/100059292 Note that. and 9640G endpoints will be upgraded to the 9600 R2. 9640. this can be accomplished with the inclusion of the following setting in the 46xxsettings. ID 03-300509) at http://support. the following media encryption setting is provisioned: SET MEDIAENCRYPTION "2. Copyright Avaya 2010 All rights reserved Page 13 of 22 . when any encryption is selected.6.bin SIP96xx_2_6_0_0. in another phone.6 Package Contents The package contains the readme file and all the files necessary to upgrade Avaya 9600 IP telephones to 96xx SIP Release 2.6 Readme On the 96xx SIP phone.txt – This file is downloaded by the Avaya 9600 IP telephones and instructs the telephones on how to upgrade. When the ENFORCE_SIPS_URI paramter is 0. in one phone the following media encryption setting is provisioned: SET MEDIAENCRYPTION "1. or just 9 (if no media encryption is desired).6. 2. if. 9630G. You MUST USE the 96xxupgrade. For more details.txt file included in this package to upgrade to R2. CM setting must include all unique media encryption values – in this case 1. This parameter has been introduced in 2.96xx Release R2. the phone accepts and uses only SIPS URI for incoming and outgoing calls with SRTP media encryption. In general.9620L 9630.9" Then. see Administering Avaya Aura™ Communication Manager Administering Avaya Aura™ Communication Manager (Doc. For example. The following files are included in each package hb96xxua3_00. having different Media Encryption settings on different sets requires the union of all the encryption settings in CM.txt file: SET MEDIAENCRYPTION "1.6 SIP phone application.bin – The 9600 R2. it is necessary to also include ‘9-none’ as a fallback.9" When the ENFORCE_SIPS_URI parameter is 1. and 9.6 SIP phone application 96xxupgrade.avaya.
xml KoreanRT4.xml KoreanRT3. Fifteen predefined language files: Mlf_Arabic.txt av_sipca_pem_2027.96xx Release R2.xml Mlf_English.xml KoreanRT8.xml Mlf_CanadianFrench.xml KoreanRT2.xml Mlf_Italian.txt av_sipca_pem_2011.xml Mlf_ParisianFrench. release.xml KoreanRT5.323 and SIP 96xx deployments . Copyright Avaya 2010 All rights reserved Page 14 of 22 .6 Readme Alternative 96xxupgrade file for mixed H.xml Mlf_Japanese.xml Mlf_BrazilianPortuguese.txt Avaya Avaya Avaya Avaya Call Server CA certificate with an expiration date of 2032 Product Root CA certificate with an expiration date of 2033 SIP Root CA certificate with an expiration date of 2011 SIP Root CA certificate with an expiration date of 2027 System specific parameters should be entered into the 46xxsettings.xml KoreanRT7.xml Mlf_Chinese.xml Four certificate files: av_csca_pem_2032.6: Unzip executable file in the root directory of the outbound file directory of your HTTP server. See the Avaya support website for additional information for how to edit this file and setup the SIG setting (the Signaling Procedure) in the 96xx phones.xml Mlf_Dutch.xml Mlf_German.xml Eight extended Korean ring tone files: KoreanRT1.xml Mlf_LatinAmericanSpanish.xml Mlf_Hebrew.com the alternate_96xxupgrade.txt file.xml Mlf_Korean. To upgrade your Avaya 9600 IP Telephones to 96xx SIP Release 2.avaya.xml Mlf_CastilianSpanish. which is available for separate download at support.txt file.com.txt file is designed for environments that will support 96xx upgrades for both the H323 and SIP modes of operation.xml KoreanRT6.txt av_prca_pem_2033.Available at support.avaya.xml – An XML-format text file that is designed to be used with Avaya Integrated Management (AIM) through the Software Update Manager (SUM). Make any adjustments required by your environment to your 46xxsettings.xml Mlf_Russian.
10.20. Once in the “Admin Procedures” menu.1 HTTP file server: 10.1 255.20.0 SIP telephone gateway: 10. default so not explicitly specified in setting AudioCodes/Cisco IP address(secondary controller ): 10.20 10.10.10.255.200 Reset your Avaya 9600 IP Telephones.com Time zone where IP telephone is provisioned: Eastern Daylight Savings Time (following the current rules where Daylight Savings Time begins on the first Sunday of April and ends on the last Sunday of October – for more information on provisioning DST see the 4600 Series IP Telephone LAN Administration Guide) The following are a minimum group of settings for the 46xxsettings.10.20 SIP telephone network mask: 255.192 o TLS transport protocol.10.10. explicitly set in setting file SNTP Server IP address: 10.30.147 -5:00 1 1SunApr2L LSunOct2L SET SIP_CONTROLLER_LIST 10.10.193:5060.10.10.transport=tls. the “ADDR” submenu will allow the administrator to provision the following fields: Phone: Router: Mask: HTTP File Server: 10.147 The SIP domain: mynetwork.10. through the use of the phone administration menu. it must be provisioned on the phone.10. itself.0 10.255. Assumptions: 96xx SIP telephone IP address: 10.20.10.193 o TCP transport protocol.30.transport=tcp SET SIP_MODE SET SIPDOMAIN 0 mynetwork.96xx Release R2.10.255. Copyright Avaya 2010 All rights reserved Page 15 of 22 .com If the 96xx SIP telephone is not acquiring its address courtesy of a DHCP server.192:5061.10.10.10.18.104.22.168.20.txt file to make the 96xx telephone operational: SET SNTPSRVR SET GMTOFFST SET DSTOFFSET SET DSTSTART SET DSTSTOP 10.200 SES IP address (primary controller): 10.6 Readme One provisioning example may be helpful.
22.214.171.1249. Austria Pat.286.51383. and 6. 218409. 6. 216023.227.549. INCLUDING.0.549.2238414B. and additional patent applications are pending.com) All rights reserved Copyright (c) 1998-2007 The OpenSSL Project.org/)" 4. AT221222. 2221268. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND Copyright Avaya 2010 All rights reserved Page 16 of 22 .573. 6.278. No. 5. No. Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.I. 2. are permitted provided that the following conditions are met: 1. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. with or without modification.307. Hudson (tjh@cryptsoft. Nos.9.646. 66959.928. Redistributions of source code must retain the above copyright notice.595.480.0). Nos. (http://www. 9609807-4.7g Copyright (c) 1998-2008 The OpenSSL Project.548. BUT NOT LIMITED TO.945. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. 3492981. 2. Nos.307.818.187. 1 010 057 (98903671. No. this list of conditions and the following disclaimer.541. Redistribution and use in source and binary forms. People's Republic of China Pat.com). Nos. 1 018 069 (98950708.6. 2. 5. 746674. Mexico Pat.96xx Release R2.064.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES.AT225534. 2214620. 71979. 727539. Nos.953. 6. 5.011. KR201211B1.554.org. ZL96196739.2). 2206118. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. Brazil P.437. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www. and Copyright (C) 1995-1998 Tim J. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. RussianFederation Pat.6 Readme License Agreements T9 Text Input and other products are covered by one or more of the following patents: U. Canada Pat. Hong Kong Standard Pat. 402252.openssl. 3532780.904. Nos. please contact opensslcore@openssl. 747901. Nos.2. 5. United Kingdom Pat. Republic of Singapore Pat.636. Japan Pat. Nos. KR226206B1. For written permission. 6. All rights reserved. Redistributions in binary form must reproduce the above copyright notice. 1. Nos.openssl. Pat. 208141. European Pat.S. This program includes Fribidi software to which Avaya is licensed under a commercial license from Behdad Esfahbod and Peter Grobgeld GoAhead Server OpenSSL 0.Republic of Korea Pat. Nos.331. 3. Australia Pat.970.302. 6. HK1010924. No.057.
LOSS OF USE.com)" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-). WHETHER IN CONTRACT. If this package is used in a product. 4. etc. Original SSLeay License ----------------------Copyright (C) 1995-1998 Eric Young (eay@cryptsoft. 2. DES. OR PROFITS. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. This library is free for commercial and non-commercial use as long as the following conditions are aheared to. SPECIAL. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. OR PROFITS. BUT NOT LIMITED TO.6 Readme FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. WHETHER IN CONTRACT. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft. SPECIAL. Redistributions in binary form must reproduce the above copyright notice. 3.com) All rights reserved. EXEMPLARY. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. OR CONSEQUENTIAL DAMAGES (INCLUDING. Redistributions of source code must retain the copyright otice. INCLUDING. lhash. The following conditions apply to all code found in this distribution.com).com). INCIDENTAL. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. be it the RC4. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. code. EXEMPLARY. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft. with or without modification.com)" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. OR CONSEQUENTIAL DAMAGES (INCLUDING. This product includes cryptographic software written by Eric Young (eay@cryptsoft. Copyright Avaya 2010 All rights reserved Page 17 of 22 . STRICT LIABILITY. BUT NOT LIMITED TO. this list of conditions and the following disclaimer. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT. This product includes software written by Tim Hudson (tjh@cryptsoft. Eric Young should be given attribution as the author of the parts of the library used. INDIRECT.96xx Release R2. INCIDENTAL. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. and as such any Copyright notices in the code are not to be removed.. DATA. DATA. INDIRECT. RSA.com). BUT NOT LIMITED TO. are permitted provided that the following conditions are met: 1. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. Redistribution and use in source and binary forms. The implementation was written so as to conform with Netscapes SSL. not just the SSL code. This package is an SSL implementation written by Eric Young (firstname.lastname@example.org). LOSS OF USE. STRICT LIABILITY. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright remains Eric Young's.
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. All rights reserved. modify. THE SOFTWARE IS PROVIDED \"AS IS\". TORT OR OTHERWISE. Copyright Avaya 2010 All rights reserved Page 18 of 22 . publish. copy. The MIT License Copyright (c) <year> <copyright holders> Permission is hereby granted. including without limitation the rights to use. WITHOUT WARRANTY OF ANY KIND. and to permit persons to whom the Software is furnished to do so. Created 1991. merge.se>. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM. THE SOFTWARE IS PROVIDED "AS IS". to any person obtaining a copy of this software and associated documentation files (the "Software"). License to copy and use this software is granted provided that it is identified as the "RSA Data Security. distribute. TORT OR OTHERWISE. to deal in the Software without restriction. i.15. subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. free of charge. sublicense. WHETHER IN AN ACTION OF CONTRACT.e. copy. Permission is hereby granted. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY. Inc. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY. DAMAGES OR OTHER LIABILITY. to deal in the Software without restriction. <daniel@haxx. 2000 Thai Open Source Software Center Ltd and Clark Cooper Copyright (c) 2001. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. RSA Data Security. ARISING FROM. All rights reserved.EXPRESS OR IMPLIED. and to permit persons to whom the Software is furnished to do so. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM. subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. and/or sell copies of the Software. WHETHER IN AN ACTION OF CONTRACT.1 Copyright (c) 1996 . MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.] libcurl 7. to any person obtaining a copy of this software and associated documentation files (the \"Software\"). Expat 2. MD5 Message-Digest Algorithm (RFC 1321) Copyright (C) 1991-2. 2006 Expat maintainers.0 Copyright (c) 1998. sublicense. 2005. 1999. modify. ARISING FROM. including without limitation the rights to use. EXPRESS OR IMPLIED.2009. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 2004. WITHOUT WARRANTY OF ANY KIND. free of charge.96xx Release R2. and/or sell copies of the Software. DAMAGES OR OTHER LIABILITY. 2003.6 Readme The licence and distribution terms for any publically available version or derivative of this code cannot be changed. Inc. merge. 2002. distribute. Daniel Stenberg. publish.
ConvertUTF Copyright 2001-2004 Unicode. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. Cambridge.3 Copyright (c) 1997-2008 University of Cambridge Copyright (c) 2007-2008. The basic library functions are written in C and are freestanding. Release 7 of PCRE is distributed under the terms of the "BSD" licence. England. Inc.uk University of Cambridge Computing Service. Inc. If this file has been purchased on magnetic or optical media from Unicode. Disclaimer This source code is provided as is by Unicode. No claims are made as to fitness for any particular purpose. It is provided "as is" without express or implied warranty of any kind. PCRE is a library of functions to support regular expressions whose syntax and semantics are as close as possible to those of the Perl 5 language.. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. as specified below. Inc. These notices must be retained in any copies of any part of this documentation and/or software. supplied in the "doc" directory. hereby grants the right to freely use the information supplied in this file in the creation of products supporting the Unicode Standard. Limitations on Rights to Redistribute This Code Unicode. The documentation for PCRE. Also included in the distribution is a set of C++ wrapper functions.96xx Release R2. and to make copies of this file in any form for internal or external distribution as long as this notice remains attached.ac. The recipient agrees to determine applicability of information provided. Google Inc. THE BASIC LIBRARY FUNCTIONS --------------------------Written by: Philip Hazel Email local part: ph10 Email domain: cam. Inc. Inc. PCRE 7.6 Readme License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security. No warranties of any kind are expressed or implied. Copyright Avaya 2010 All rights reserved Page 19 of 22 . Inc. RSA Data Security. the sole remedy for any claim will be exchange of defective media within 90 days of receipt. is distributed under the same terms as the software itself.
OR PROFITS. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. Google Inc. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. INCLUDING. are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice.6 Readme Copyright (c) 1997-2008 University of Cambridge All rights reserved. DATA. Copyright (c) 2007-2008. WHETHER IN CONTRACT. BUT NOT LIMITED TO. All Rights Reserved. Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES. this list of conditions and the following disclaimer. STRICT LIABILITY. INCIDENTAL. nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.96xx Release R2. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. Copyright Avaya 2010 All rights reserved Page 20 of 22 . SPECIAL. LOSS OF USE. OR CONSEQUENTIAL DAMAGES (INCLUDING. THE C++ WRAPPER FUNCTIONS ------------------------Contributed by: Google Inc. HTTP Server functionality is provided by the GoAhead WebServer 2. THE "BSD" LICENCE ----------------Redistribution and use in source and binary forms. EXEMPLARY.1. All rights reserved. * Redistributions in binary form must reproduce the above copyright notice. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright (c) 2004 GoAhead Software. INDIRECT. BUT NOT LIMITED TO. * Neither the name of the University of Cambridge nor the name of Google Inc. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. with or without modification.
Changes and corrections to the information in this document may be incorporated in future releases. additions. or information described or offered within them. whether as stand-alone Products or pre-installed on Hardware. originally licensed by Avaya and ultimately utilized by End User. services. serial number.96xx Release R2. All Rights Reserved. and or use can be a criminal. Avaya may require the Designated Processor(s) to be identified by type.com/ThirdPartyLicense/ Avaya fraud intervention Copyright Avaya 2010 All rights reserved Page 21 of 22 . location or other specific designation.6 Readme 2010 Avaya Inc. and Avaya does not necessarily endorse the products. Third-party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (“Third Party Components”). or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Link disclaimer Avaya Inc. or deletions to the original published version of this documentation unless such modifications. End User may install and use each copy of the Software on only one Designated Processor. Copyright Except where expressly stated otherwise. the Product is protected by copyright and other laws respecting proprietary rights. is not responsible for any modifications.com/LicenseInfo/ (“GENERAL LICENSE TERMS”). License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT http://support. unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. as well as a civil. “Designated Processor” means a single stand-alone computing device. “Hardware” means the standard hardware Products. originally sold by Avaya and ultimately utilized by End User.avaya. IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS. YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. “Software” means the computer programs in object code. unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users. Unauthorized reproduction. The applicable number of licenses and units of capacity for which the license is granted will be one (1). We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. which may contain terms that expand or limit rights to use certain portions of the Product (“Third Party Terms”).avaya. transfer.Avaya grants End User a license within the scope of the license types described below. Avaya Inc. Documentation disclaimer. can assume no liability for any errors. Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this Documentation. Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya’s web site at: http://support. feature key. offense under the applicable law. or deletions were performed by Avaya. License Type(s): Designated System(s) License (DS). Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing. additions.
avaya.com/support ~~END OF FILE~~ of documentation.6 Readme If you suspect that you are being victimized by toll fraud and you need technical assistance or support.com/support Trademarks Avaya. All other trademarks are the property of their respective owners.avaya. and certain other jurisdictions. in the U. call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. and COMMUNICATIONS MANAGER and the Avaya logo are registered trademarks and/or service marks of Avaya Inc. Document ordering information: For the most current versions http://www. DEFINITY. go to the Avaya support Web site: Copyright Avaya 2010 All rights reserved Page 22 of 22 .avaya.com.S. The support telephone number is 1 800 242 2121 in the United States. Suspected security vulnerabilities with Avaya Products should be reported to Avaya by sending mailto: securityalerts@avaya. see the Avaya Web site: http://www. For additional support telephone numbers.com/support Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your contact center. AUDIX. see the Avaya Web site: http://www. For additional support telephone numbers.96xx Release R2.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.