R E L E A S E N O T E S ShoreTel 9.
Document and Software Copyrights Copyright © 1998–2009 by ShoreTel, Inc., Sunnyvale, California, U.S.A. All rights reserved. Printed in the United States of America. Contents of this publication may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without prior written authorization of ShoreTel, Inc. ShoreTel, Inc.
Table of Contents System Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Server Device Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents ShoreWare Server Release Notes Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Shared Call Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Introduction . . . . . . . . .
ShoreWare Server Release Notes Table of Contents ShoreTel 9 – System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents ShoreWare Server Release Notes Server Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 System Failover Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 System Failback Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 CDR Reports – Codecs . . . . . . . . . .
ShoreWare Server Release Notes Table of Contents DID Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Usage Information. . . . . . . . .
Table of Contents ShoreWare Server Release Notes Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Call Handling Mode Delegation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Definition . . . . . . . . . . . . . . . . .
ShoreWare Server Release Notes Table of Contents Mobile Call Manager – Location Based Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 History . . . . . . . . . . . . . . . . . . . . .
Table of Contents Page 10 ShoreWare Server Release Notes
System Specifications
System Specifications Hardware and Software Requirements Server Device Requirements Operating Systems ShoreWare 9.1 server software is supported on the following operating systems: • Windows Server 2003 SP2 (Standard or Enterprise) ShoreWare Version 9.1 is not supported on Windows 2003 SP1 • • Windows Server 2003 R2 Enterprise Edition, 32-bit (Standard or Enterprise) Windows Server 2008 (Standard or Enterprise) ShoreWare is supported only on 32-bit operating systems. There is no 64-bit support.
System Specifications ShoreWare Server Release Notes To maintain high server performance and reliability, ShoreTel recommends Gigabit Ethernet Interface for all configurations regardless of the number of users or network load. Although the 100 Base-T interface can provide acceptable performance and reliability for the specified configurations, administrator intervention is frequently required to properly configure the IP network and prioritize real-time information during peak network traffic conditions.
ShoreWare Server Release Notes System Specifications Agent, Supervisor, Operator (<500 extension presences) Pentium 4 – 3.0 GHz 150 MB 150 MB 1 GB 1 GB All Versions, VGA Video Dual-Core 1.6 GHz 150 MB 150 MB 1 GB 1 GB All Versions, XGA Video Core 2 Quad 2.4 GHz 150 MB 150 MB 1 GB 1 GB Table 4 Client Device Hardware Requirements a. Call Manager memory requirements during normal operation.
System Specifications • • • • • • ShoreWare Server Release Notes ShoreGear E1k ShoreGear 120 ShoreGear 60 ShoreGear 40 ShoreGear T1 ShoreGear E1 ShorePhone Telephones Version 9.1 supports the following ShorePhone Telephones • • • • • • • • • • • • • • IP565 IP560g IP560 IP530 IP265 IP230g IP230 IP212k IP210 IP115 IP110 IP8000 AP110 AP100 Upgrade Paths and Application Support Upgrade Path ShoreTel supports single step upgrades to ShoreWare 9.1 from Version 9, Version 8.1, and Version 7.5.
ShoreWare Server Release Notes System Specifications Contact Center Version 9.1 supports interoperability for Contact Center 4.66.05 and above. SIP-BRI 8 Version 9.1 supports interoperability for SIP-BRI 8 Build R3.T_2006-10-04 and above. SIP Devices Version 9.1 supports the following SIP devices as SIP extensions: • IP8000 Character Sets This version of ShoreWare supports only ISO 8859-1, also known as Latin -1 or Microsoft Windows CP1252 character set (see http://www.microsoft.
System Specifications • ShoreWare Server Release Notes ShoreGear Switches — 60 switches per site if DRS is not enabled. — 500 switches per site if DRS is enabled. • ShoreGear Voicemail Model Switches — 50 Voicemail Model switches per site — 100 Voicemail Model switches per system. • Servers — One main server. — 20 distributed servers. • IP Phones — 5 ShorePhones per ShoreGear port. — 100 SIP Proxies per ShoreGear port. • Desktop Clients — — — — — — • 10,000 Call Manager instances per system.
ShoreTel 9.
Windows Server 2008 Support Introduction ShoreWare 9.1 supports the Windows 2008 operating systems as a platform for the following ShoreWare components: • ShoreWare Main Server – Windows Server 2008, Standard and Enterprise (32-bit) editions. • ShoreWare Distributed Server – Windows Server 2008, Standard and Enterprise (32bit) editions. ShoreWare 9.1 continues to support all operating system platforms that are supported by ShoreWare 9.
Windows Server 2008 Support ShoreWare Server Release Notes Application Server Role Figure 2 displays the required roles for the Application Server for ShoreTel. Selecting IIS and COM+ ensures the installation of these services. Step 1 Click the Server Manager icon on the Task bar or, select Start -> Programs -> Administrative Tools -> Server Manager. Step 2 In Server Manager right-click Roles and select Add Roles from the pop-up menu.
ShoreWare Server Release Notes Figure 2 Windows Server 2008 Support Required Server Roles Web Server (IIS) Role Servers Figure 2 displays the Web Server required roles. The following Web Server (IIS) role services should be installed. Figure 3 Required Web Server Roles Step 1 Access the Web Server Role by selecting Server Manager Step 2 Right click on Server->Add Roles Step 3 Select Web Server (IIS)-> Role Services ShoreTel 9.
Windows Server 2008 Support ShoreWare Server Release Notes Web Server Roles • Select all Common HTTP Features • Select all Application Development Features • Select the following Health and Diagnostics Features — — — — HTTP Logging Logging Tools Request Monitor Tracing • Select all Security options • Select all Performance options NOTE: You may need to scroll down the Web Role Server window to see all the available options.
ShoreWare Server Release Notes Windows Server 2008 Support Step 1 Access the Services table by selecting Server Manager -> Configuration -> Services. Step 2 Open the Simple Mail Transfer Protocol (SMTP) Properties panel by right clicking Simple Mail Transfer Protocol and selecting Properties on the context menu. Figure 5 Selecting SMTP Properties . ShoreTel 9.
Windows Server 2008 Support Figure 6 ShoreWare Server Release Notes SMTP Properties panel Step 3 Select Automatic on the Startup Type drop down menu, then click the OK button. Step 4 Return to the Services table. Step 5 Open the FTP Publishing Service properties panel by right clicking FTP Publishing and selecting Properties on the context menu. Step 6 Select Automatic on the Startup Type drop down menu, then click the OK button.
ShoreWare Server Release Notes Windows Server 2008 Support Upgrading ShoreWare Servers from Windows 2003 to Windows 2008 Upgrading Servers Running ShoreWare 9.1 The following procedure is required when upgrading to Windows Server 2008 on a server that is running ShoreWare 9.1 server software. Warning: Active Directory settings must be disabled before proceeding with the upgrade process.If active directory is not disabled, you will not be able to start ShoreWare Director after upgrading.
Windows Server 2008 Support • Shoreline Communication • FTPRoot ShoreWare Server Release Notes Refer to the Planning and Installation Guide for instructions on uninstalling ShoreWare Server software. NOTE: Make sure Windows PowerShell is not present. Refer to Microsoft support for information on uninstalling Windows PowerShell. Step 4 Upgrade the server operating system to Windows Server 2008.
ShoreWare Server Release Notes Windows Server 2008 Support Upgrading Servers Running ShoreWare Versions ShoreWare 9.1 is the only ShoreWare version that supports Windows Server 2008. Servers running earlier versions of ShoreWare must upgrade to Version 9.1 to ensure database compatibility before upgrading to Windows Server 2008. ShoreWare versions that can be directly upgraded to Version 9.1 include Versions 7.5, 8.1, and 9.
Windows Server 2008 Support ShoreWare Server Release Notes Step 5 Uninstall the ShoreWare Server software 9.1 and delete the following folders. • Shoreline Data • Shoreline Communications • FTPRoot Refer to the Planning and Installation Guide for instructions on uninstalling ShoreWare Server software. NOTE: Make sure Windows PowerShell is not present. Refer to Microsoft support for information on uninstalling Windows PowerShell.
ShoreWare Server Release Notes Windows Server 2008 Support Upgrading ShoreWare Distributed Voicemail Server from Windows 2003 to Windows 2008 Upgrading Distributed Voicemail Server Running ShoreWare 9.1 The following procedure is required when upgrading to Windows Server 2008 on a ShoreWare Distributed Voicemail Server that is running ShoreWare 9.1 server software.
Windows Server 2008 Support ShoreWare Server Release Notes Step 4 Upgrade the server operating system to Windows Server 2008. After the operating system is upgraded, you must activate the operating system prior to installing ShoreWare Distributed Voicemail Server software. Refer to Microsoft documentation and the Installation Requirements section, starting on page 21. NOTE: Do not use Autorun from the Windows Server 2008 CD. Autorun will only allow a new installation of Windows 2008.
ShoreWare Server Release Notes Windows Server 2008 Support NOTE: ShoreTel recommends that you back up these databases to a storage device separate from the server you intend to upgrade. Step 3 Uninstall the ShoreWare Distributed Voicemail Server software 9.1 and delete the following folders. • Shoreline Data • Shoreline Communications • FTPRoot Refer to the Planning and Installation Guide for instructions on uninstalling Distributed Voicemail Servers software.
Windows Server 2008 Support Page 34 ShoreWare Server Release Notes
Call Manager on 64-Bit Vista Introduction ShoreTel 9.1 extends support for running Call Manager on 64-bit platforms to include Microsoft Windows Vista – Business edition.
Call Manager on 64-Bit Vista Page 36 ShoreWare Server Release Notes
Single Sign On – Instant Messaging Introduction ShoreTel 9.1 supports Single Sign On (SSO) for logging into the OCS 2007 server. Background ShoreTel 9 integrated Active Directory with the ShoreTel directory. Single sign on to Call Manager and Director were among the Active Directory features introduced in ShoreTel 9.
Single Sign On – Instant Messaging Figure 13 Page 38 ShoreWare Server Release Notes SSO – Inactive Instant Messaging Logon Options
SIP Header Enhancement – Integration with 911 Enable Introduction ShoreTel 9.1 modifies the SIP Header structure in packets handled by the ShoreTel system. The MAC address is added to the From Header. This change accommodates a third party solution for providing emergency services to devices in an IP network without requiring PSTN access. Background The emergence of centralized IP-PBX deployments and greater employee mobility requires a reliable 911 option.
SIP Header Enhancement – Integration with 911 Enable ShoreWare Server Release Notes Description 911 Enable is a third party vendor that markets a reliable method of routing calls from IP network devices to emergency service providers.
Shared Call Appearance Introduction Definition Shared Call Appearance is a ShoreTel client feature that establishes common Bridged Call Appearance between a user (executive) and at least one other user (assistant). A Shared Call Appearance is typically established to allow one or more assistants to manage inbound calls and initiate outbound calls for an executive.
Shared Call Appearance ShoreWare Server Release Notes button is programmed by the administrator to perform a specific function when clicked and can contain text that relays function status. Programmable IP Phone Buttons Programmable IP Phone buttons is a ShorePhone feature that provides access to ShoreTel call management functions. Each button is programmed by the user or administrator to perform a specific function when pushed contains an LED indicator which may display function status.
ShoreWare Server Release Notes Figure 15 Shared Call Appearance Configuring the Executive Extension • aBCAs are not editable from the Bridged Call Appearance Director panel. aBCA settings and parameters are configured from the user’s Edit User panel. • aBCAs are created when a ShoreTel extension is converted to a executive extension. To create a executive extension, open the Edit User panel for the desired user and select the Share Call Appearances option.
Shared Call Appearance ShoreWare Server Release Notes Figure 16 Edit Panel – Executive Bridged Call Appearances aBCA names have the form __, where — first name is the first name of the user — last name is the last name of the user — extension is the user’s extension number Step 2 Open the edit panel for the aBCA, as shown in Figure 16, by clicking the name of the desired aBCA on the Bridged Call Appearance List panel.
ShoreWare Server Release Notes Shared Call Appearance Refer to the ShoreTel Administrator Guide for information about programmable buttons. Bridged Call Appearance Monitor The Bridged Call Appearance Monitor is a Call Manager window that displays all Bridged Call Appearances accessible to the user’s extension through all devices assigned to the user. The BCA Monitor consolidates all of a user’s aBCA activity into a single panel.
Shared Call Appearance ShoreWare Server Release Notes The following sections describe the set up and performance of Shared Call Appearance and Hotline circuits for this typical scenario. Configuring Setting up a Shared Call Appearance – Hotline connection between a executive extension (executive) and an assistant user requires the following steps: Step 1 Convert the executive’s extension to a Executive Extension, as described in Executive Extension on page 42.
ShoreWare Server Release Notes Shared Call Appearance NOTE: The called party will see the executive's bBCA or the assistant’s aBCA's caller ID based on the BCA Caller ID registry setting. Step 2 The assistant user calls the recipient and prepares the recipient for the executive’s call. Step 3 The assistant user places the call on hold. Step 4 The assistant user presses the hotline button to call the executive.
Shared Call Appearance Page 48 ShoreWare Server Release Notes
Silent Coach Introduction Definition Silent Coach is a ShoreTel client feature that allows a user to intervene in another user’s active call and communicate with that user. The initiator can speak to the specified user and listen to all other call participants. The specified user is the only call participant that can hear the initiator. A Telephony Class of Service assigns Silent Coach rights. Silent Coach can be initiated through various ShorePhone models or through Call Manager.
Silent Coach ShoreWare Server Release Notes connected – they cannot hear or speak with each other. A Telephony Class of Service sets Whisper Page rights. Description Synopsis Silent Coach is a ShoreTel client feature that allows a user to intervene in a specified user’s active call and communicate with that user. The initiator can speak to the specified user and listen to all other call participants. The specified user is the only call participant that can hear the initiator.
ShoreWare Server Release Notes Silent Coach Implementation Configuring Silent Coach Permissions Silent Coach access is controlled through Telephony CoS settings. Permissions for monitoring calls and for having calls monitored are configured through the Silent Monitor / Silent Coach option on the Telephony Class of Service Edit panel, as shown in Figure 17.
Silent Coach ShoreWare Server Release Notes Enabling the Silent Coach Warning Tone ShoreWare provides an option for playing a Silent Coach Warning Tone to all call participants when a Silent Coach session is initiated and if the Silent Coach Warning Tone option is enabled. The Warning Tone setting applies to all Silent Coach sessions on the system.
ShoreWare Server Release Notes Figure 19 Silent Coach Programming IP Phone Button – Silent Coach If this field is left blank, pressing the IP Phone button queries the initiator to enter a number in the Telephone User Interface before the session begins. Step 5 Click Save to store panel changes.
Silent Coach ShoreWare Server Release Notes Figure 20 Silent Coach Dialog box To perform a Silent Coach from a Call Manager toolbar button: Step 1 Press the programmable Silent Coach button, as shown in Figure 21. If the button specifies a Silent Coach recipient, the system immediately initiates a Silent Coach session with that user. Skip the remaining steps. If the button does not specify a Silent Coach recipient, Call Manager displays the Silent Coach dialog box.
ShoreWare Server Release Notes Silent Coach Step 3 Click the Silent Coach button. To transition a Silent Coach session into a Silent Monitor or Barge In session, perform one of the following: • Right click the call cell and select the desired session type on the context menu. Figure 21 displays the context menu during a Silent Monitor Session. • If available, press the Monitor or Barge In programmable button. Figure 21 displays Silent Monitor, Silent Coach, and Barge In programmable buttons.
Silent Coach ShoreWare Server Release Notes Softkey options available to the Silent Coach recipient: • Consul: Places the active call on hold and establishes a two-way voice path between with the Silent Coach initiator. While the recipient consults with the initiator, soft key options include: — Resume: Restarts the recipient’s original call. — Show: Displays all call participants. — HangUp: Terminates the call. Page 56 • Show: Displays all call participants in the Telephone User Interface.
Hotline Introduction Definition A Hotline is a bi-directional ringdown circuit accessed through IP Phone or Call Manager buttons. A hotline call is initiated by pressing the assigned button. Hotline calls can be configured as speed dial or intercom calls. The Hotline feature is implemented without Bridged Call Appearances. Background Previous ShoreTel versions provided Hotline functionality through Ringdown call appearances.
Hotline ShoreWare Server Release Notes Figure 23 Programming a Hotline button Usage Users access the hotline circuit from Call Manager or ShorePhones through programmable buttons. Hotlines calls are presented as normal voice calls to users that have not assigned a button for that hotline. Refer to the ShoreTel Administrator Guide for information about programmable buttons.
Mobile Call Manager – Device Support Enhancements Introduction Definition ShoreTel 9.1 provides support for the following mobile devices: • • HTC TyTN II Nokia E71 Feature Support Although basic MCM functions are available on all supported devices, the implementation of some functions varies between devices because of the inherent devices differences. The following sections list MCM features that are available on models introduced in ShoreTel 9.
Mobile Call Manager – Device Support Enhancements Page 60 ShoreWare Server Release Notes
ShoreTel 9 – System Features
Active Directory Introduction ShoreTel 9 integrates Active Directory with the ShoreTel directory to provide the following functions: • • • Bulk Import of user accounts Synchronize ShoreTel user accounts with Active Directory user records Authentication of Active Directory users Active Directory compliant directories centrally stores information for all users, computers, and other entities.
Active Directory ShoreWare Server Release Notes When AD Integration is enabled, only users that have Administrative Permissions can log into Director. This requires the explicit definition of at least one administrator role and the assignment of users requiring Director access to an administrative role.
ShoreWare Server Release Notes Active Directory To add a system user, select Administration -> Users -> Individual Users from the Main Menu. Refer to the ShoreTel Administration Guide for more information. Step 4 Assign Administrative Rights to the new user account. To assign rights, press the New button in the Administrators List panel that is accessed by selecting Administration -> System Parameters -> Administrative Permissions -> Administrators panel.
Active Directory • ShoreWare Server Release Notes LDAP-GUID: Used internally by the ShoreTel system when performing subsequent user updates from the AD database. Authenticating AD Users ShoreTel supports AD authentication for users logging into Call Manager, Web Client, and Director, permitting access to these programs without providing the ShoreWare username or password.
ShoreWare Server Release Notes Active Directory Non-AD User Logged into the domain Users that are not configured for AD within ShoreWare that are logged into the domain network are directed to a Director Login panel, as shown in Figure 26. Users access Director from this panel by entering their ShoreTel username and password in the respective data fields.
Active Directory ShoreWare Server Release Notes Users that are not authenticated through AD are required to enter their name, password and server name. After verifying the user’s credentials, Call Manager guides the user through the setup process. Logging into Call Manager Attempts to log into Call Manager after the initial setup are handled on the basis of the user’s AD configuration. Active Directory users are authenticated by SSO through the verification of their AD credentials.
ShoreWare Server Release Notes Active Directory Synchronizing AD and Director User Records Director provides an interface for adding, updating, and deleting AD users from the ShoreTel database. Synchronization is performed on individual users and does not affect the AD directory.1 Enabling AD for a ShoreTel User When AD Integration is enabled, the first parameter on the Edit User: General panel enables Active Directory for the user, as shown in Figure 29.
Active Directory ShoreWare Server Release Notes Bulk Provisioning of User Accounts ShoreTel supports the bulk provisioning of user accounts from AD records through a two step process: Step 1 Export AD records to a CSV file. Exporting AD Records describes this step. Step 2 Import CSV records to the ShoreTel user database. Importing the CSV File on page 71 describes this step. Exporting AD Records ShoreTel provides a VBScript file to export data records from an Active Directory database to a CSV file.
ShoreWare Server Release Notes Active Directory The following command line executes the AD to CSV file import: cscript ldaptocsv.vbs outputCSVfile LDAPpath [modifiedInLastN#OfDays] where outputCSVfile specifies the name of the output file LDAPpath specifies the path to the AD database [modifiedInLastN#OfDays] The resulting CSV file can be modified though a spreadsheet program to customize user settings for import to the ShoreTel database. Importing the CSV File DBImport.
Active Directory Page 72 ShoreWare Server Release Notes
LLDP / 802.1x Introduction Version 9 enhances ShorePhones to support LLDP-MED and 802.1x. The Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) is an enhancement to the Link Layer Discovery Protocol (LLDP) that addresses the following: • • • • Device location discovery to support location databases and VoIP E911 services. Auto-discovery of LAN policies to support “plug and play” networking. Extended and automated power management of PoE endpoints. Inventory management.
LLDP / 802.1x ShoreWare Server Release Notes — — — — — Config File DHCP (if active) LLDP (if active) Setup Command Default values 802.1x A component of IEEE 802.1 group of networking protocols, 802.1x addresses port-based Network Access Control. It provides an authentication mechanism for devices attaching to a LAN port to either establish a point-to-point connection or prevent the device from accessing the port if authentication fails. 802.1x is based on the Extensible Authentication Protocol (EAP).
Unicode Character Set Support Introduction Feature Description ShoreTel 9 supports Unicode Character sets by incorporating the v5.1 MySQL ODBC connector, resulting in databases that support Unicode Character sets. ShoreTel 9 does not localize any ShoreTel application, including Director, not localized in a previous version. Support of Unicode Character sets extends to the ShoreTel system and CDR databases.
Unicode Character Set Support Figure 31 ShoreWare Server Release Notes Reporting Options panel Chinese Traditional font is installed on the Headquarters server by default. Access reports from a client machine or using a different Asian font requires a font installation through the Reporting Options panel.
SRTP-AES Introduction Definition ShoreTel 9 supports SRTP for encrypting, authenticating, and replaying media streams for ShoreGear switches and ShorePhones that support encryption.
SRTP-AES ShoreWare Server Release Notes SRTP-AES Description System Support ShoreTel 9 supports SRTP for encrypting, authenticating, and replaying media streams for ShoreGear switches and ShorePhones that support encryption. ShoreWare encrypts RTP (payload) packets sent within the ShoreTel network. Call control packets are not encrypted. ShoreTel 9 retains the proprietary 128-bit encryption algorithm that is available in previous version as an alternative to SRTP encryption.
ShoreWare Server Release Notes SRTP-AES Call Manager and ShorePhones display a padlock icon for each call utilizing SRTP encryption. The Call History list also uses the padlock icon to denote encrypted calls. ShorePhones IP210, IP110, and IP115 do not display the encrypted call padlock icon. The padlock icon indicates that the call media is secure on the ShoreTel network. ShoreTel cannot guarantee call security outside of the network, such as calls that terminate across an analog or digital trunk.
SRTP-AES ShoreWare Server Release Notes To configure encryption: Step 1 Open the Call Control: Options panel by selecting Administration -> Call Control > Options from the main menu. Step 2 Select the desired option from the Media Encryption drop down menu, as shown in Figure 32. Step 3 Press the Save button at the top of the panel.
Disaster Recovery Enhancements Introduction ShoreTel 9 introduces Disaster Recovery Enhancements to improve system compatibility with supported failover solutions. Disaster Recovery Enhancements implements primary and secondary IP addresses to distinguish the Headquarters server from its backup server.
Disaster Recovery Enhancements ShoreWare Server Release Notes Failover and failback operations typically require between five to 20 minutes, depending on the system configuration. During these periods, no Headquarter server services are available. Failover and failback operation effects are resolved after the operations are complete and the secondary (for failover) or primary (failback) server is functioning as the Headquarters server.
ShoreWare Server Release Notes Figure 33 Disaster Recovery Enhancements Designating Primary and Secondary IP Addresses When the primary and secondary servers are in different subnets, their IP addresses must be static. The DNS server accessed by a ShoreTel system must associate the same server name to the primary and secondary servers if • The primary and secondary servers are configured with static IP addresses.
Disaster Recovery Enhancements ShoreWare Server Release Notes License Compliance After a failback operation transfers Headquarters server control to the secondary server, license status on the secondary server is non compliant. To restore the system to compliance, reinstall all licenses that were originally purchased for the secondary server. MCM Failback Requirements To assure proper MCM client operation and performance after a Failback, the browser cache must be cleared.
CDR Reports – Codecs Introduction Definition ShoreTel 9 enhances the CDR database and CDR reports to support the following: • • codecs added in ShoreTel 8 references to codec strings added by the administrator Refer to the Glossary for a definition of the following terms used in this release note: • • • Call Detail Record (CDR) CDR Database Codec Background ShoreTel 8 supports the following codecs: • • • • • • • • • • • G711μ G711a L16/16000 DVI4/8000 G729A/8000 G729B/8000 L16/16000 G722/8000 BV32/1
CDR Reports – Codecs • • • • Page 86 9 BV32 10 BV16 11 AAC_LC32000 12 Custom ShoreWare Server Release Notes BV32/16000 BV16/8000 AAC_LC/32000 Codec added by administrator
Failover Introduction Definition ShoreTel 9 implements the following Failover enhancements: • IP Phone Calls Continue Through Failover feature enhances IP Phone Failover to continue a voice call, even after the managing switch becomes unavailable, until the normal completion of the call • Spare Switch Failover introduces spare switches for handling IP Phones that failover.
Failover ShoreWare Server Release Notes IP Phone Calls Continue Through Failover Feature Description The IP Phone Calls Continue Through Failover feature maintains active calls through the normal completion of the call even when the call manager switch handling the call becomes unavailable.
ShoreWare Server Release Notes Failover IP Phone Behavior during Failover ShorePhone – Local Endpoint During the Pending Failover stage, the telephone user interface (TUI) displays a No Service message until the phone is assigned to a new switch. Call control operations are not available on surviving calls. All inbound calls to the local endpoint are routed to the destination specified by the current Call Handling Mode.
Failover ShoreWare Server Release Notes resources are available, ShoreWare searches the site and its ascendant sites until a dormant spare switch is identified. The spare switch is assigned to the site requiring the resource, after which a call manager resource is assigned to the IP Phone performing the failover. Active spare switches only service IP Phones that failover from losing call manager resources.
ShoreWare Server Release Notes Failover IP phones managed by the switch are moved to other switches after failback operation. If the site does not have sufficient capacity to cover IP phones when a failback is initiated, the spare switch performs another failover. Failback is performed from the Maintenance – Switch Summary panel in Director.
Failover ShoreWare Server Release Notes To access the Edit Spare Switch List, select Administration -> Switches -> Spare from the Director Main Menu, then click the Go text at the top of the panel to add a switch or click the desired switch name to edit that switch. Enabling IP Phone Failover IP Phone Failover must be enabled from the Edit IP Phone Options panel.
Call Manager on 64-bit Windows Terminal Server Introduction ShoreTel 9 supports running Call Manager on Windows Terminal Server 64-bit operating system.
Call Manager on 64-bit Windows Terminal Server Page 94 ShoreWare Server Release Notes
ShoreTel 9 – Director Enhancements
DiffServ / ToS Support Introduction Definition ShoreTel 9 extends DiffServ/ToS packet marking as follows: • The existing DiffServ/ToS marking for voice IP packets is extended to voice, voicemail, workgroup, account code collection, and contact center calls. • DiffServ/ToS marking for video IP packets is introduced.
DiffServ / ToS Support Figure 39 Page 98 ShoreWare Server Release Notes DiffSrv / ToS Parameter
Support of 256 Workgroups Introduction Definition ShoreTel 9 increases the number of Workgroups supported by ShoreWare to 256. Background ShoreTel 8.1 supports up to 128 workgroups, with up to 300 members per workgroup. A workgroup enables a group of users to appear as a single unit to calling parties. Calls can be routed in top-down, longest-idle, round-robin, and simultaneous-ring fashion. Workgroups are typically used by support and sales groups to automate call handling.
Support of 256 Workgroups Page 100 ShoreWare Server Release Notes
SIP Trunk Profiles Introduction Definition SIP Trunk Profiles is a Director enhancement that supports custom SIP Trunk parameter settings to specify third party service provider configurations. In addition to a generic profile, ShoreWare provides a profile that supports ATT BVOIP.
SIP Trunk Profiles ShoreWare Server Release Notes • User Agent: This parameter is the expression ShoreWare uses to identify devices covered by the profile. ShoreWare compares this expression to the User Agent field in the header of SIP packets handled by the system. • Priority: This parameter determines the order by which the profiles are evaluated against the SIP packet header. Profiles with larger priority values are evaluated before profiles with smaller priority values.
ShoreWare Server Release Notes ShoreTel 9.
SIP Trunk Profiles Page 104 ShoreWare Server Release Notes
DID Enhancements Introduction Definition ShoreTel 9 modifies DID assignment fields and labels on User, Workgroup, Route Point, Menu, Hunt Group, and Bridge Call Appearance panels. Refer to the Glossary for a definition of the following terms used in this release note: • • • Available DID numbers DID Range Direct Inward Dialing Usage Information DID assignment sections on Director panels consist of two parameters: DID Range and DID Number. Figure 45 displays these parameters on the Edit User panel.
DID Enhancements Figure 46 ShoreWare Server Release Notes DID Range parameter – drop-down menu Unassigned numbers within a DID range may not be available if the number is assigned as a DNIS in the same trunk group. • Page 106 The DID Number parameter assigns the specified DID number to the entity. The prefix located left of the data entry field and the range located right of the data entry field are based on the selected DID range.
ShoreTel 9 – Client Features
Announced Find Me Introduction Definition Announced Find Me is an enhancement of Find Me that provides for the recording of the caller’s name for calls routed to Find Me destinations. This feature provides the capacity for all inbound callers to be identified when their call is routed to a Find Me destination.
Announced Find Me ShoreWare Server Release Notes Users can receive Announced Call Me introductions for all callers or restrict the introductions to calls for which Caller ID is not available. Enabling Announced Find Me from Director Administrators enable Announced Find Me for system users from the Find Me and External Assignment panel.
ShoreWare Server Release Notes Announced Find Me To enable Announced Find Me from Call Manager, perform the following: Step 1 Open the Options and Preferences panel by executing one of the following actions: • • • • Select Tools -> Options from the Main menu. Click the Application Button and select Options. Right click the ShoreTel icon in the System Tray and select Options. Press Ctrl+O.
Announced Find Me Figure 49 ShoreWare Server Release Notes Enabling Announced Find Me from Web Access Usage Information Caller Functions When the Announced Find Me parameter is enabled, callers that are routed to a Find Me extension are prompted to record their name under each of the following conditions: • The call is from a source external to the ShoreTel system and the number is not available through Caller ID.
Personalized Call Handling Introduction Definition Personalized Call Handling defines flexible handling methods for inbound calls from different callers received at various times and dates. Possible applications for Personalized Call Handling includes: • Requiring unidentified callers to announce their name by routing them to Announced Find Me. • Assigning different ringtones for selected callers, such as family, personal contacts, external contacts.
Personalized Call Handling ShoreWare Server Release Notes Description Introduction A Call Routing Plan manages a user's inbound voice calls. The plan consists of call handling rules, each of which specifies a method of handling a call when a condition set is valid. The plan enables and prioritizes selected rules. The user's inbound calls are evaluated against the call handling rules. The highest priority rule with conditions that are satisfied define the handling method for the call.
ShoreWare Server Release Notes Personalized Call Handling • I am on the phone: This criterion is satisfied when the user’s phone is busy. • Call Handling Mode: This criterion is satisfied when the user’s active Call Handling Mode matches the specified mode. • Time of day: This criterion is satisfied when the call is received during the specified time ranges. Time of day entries are based on the timezone setting of the site to which the user is assigned.
Personalized Call Handling ShoreWare Server Release Notes Execution When a user receives an inbound call, the system evaluates the characteristics against the highest priority call handling rule that is enabled. If all of the criteria comprising the condition of that rule matches the call characteristics, the call is routed as specified by the rule’s action and the plan execution is complete.
ShoreWare Server Release Notes Figure 50 ❋ Personalized Call Handling Options and Preferences: Personalized Call Handling panel Press the Delete Rule button to remove the highlighted rule from the Rule Table. — Rule List: The Rule list displays the list of call handling rules defined by the user. Rules are listed in order of their usage priority; higher priority rules are listed first. List columns include: ❋ Rule: This column displays the name of the rule.
Personalized Call Handling Figure 51 ShoreWare Server Release Notes Condition Setup panel • Condition Description field: The Condition Description field displays the selected conditions and the parameter setting that the call characteristic must match. Hypertext links denote a condition that requires a parameter setting. Clicking the link opens a dialog panel that assigns a value to the parameter. • Button bar: The button bar is located at the bottom of the panel.
ShoreWare Server Release Notes Personalized Call Handling Action Setup panel The action setup panel, as shown in Figure 53, specifies the call handling action performed on the call when the rule conditions match the call characteristics. To access the Action Setup panel, press the Next button in the Condition Setup panel.
Personalized Call Handling ShoreWare Server Release Notes Name Setup panel The Name Setup panel, as shown in Figure 55, specifies the label by which the call handling rule is referred by the Personalized Call Handling panel. To access the Action Setup panel, press the Next button in the Action Setup panel. Figure 55 Action Setup panel Director User Interface Panels The Personalized Call Handling Rules panel, as shown in Figure 56, displays the Call Handling Rules created by the specified user.
ShoreWare Server Release Notes Personalized Call Handling Step 2 Open the Personal Options panel for the desired user by clicking the name of the desired user in the Individual User List, then selecting Personal Options on the menu bar toward the top of the Edit User panel. Step 3 Click Personalized Call Handling Rules, located in the middle of the Personal Options panel, as shown in Figure 57.
Personalized Call Handling ShoreWare Server Release Notes Creating and Editing Call Handling Rules Personalized Call Handling Rules are created or edited from the Options and Preferences: Personalized Call Handling panel, as shown in Figure 58. Figure 58 Personalized Call Handling panel To create a Call Handling Rule: Step 1 Press the New Rule button, located at the top of the panel. Call Manager displays the Personalized Call Handling Setup panel, as shown in Figure 59.
ShoreWare Server Release Notes Personalized Call Handling Step 2 Select all conditions in the Choose Condition to handle inbound calls section located in the top half of the panel. The Condition Description section, located in the bottom half of the panel, displays the set of conditions that an inbound call must meet to be filtered by the rule. Blue hypertext regions link to dialog boxes that define specific criteria for filtering calls.
Personalized Call Handling Figure 61 ShoreWare Server Release Notes Personalized Call Handling Setup panel – choosing action The new rule appears in the Rule list of the Options and Preferences: Personalized Call Handling panel, as shown in Figure 62.
ShoreWare Server Release Notes Personalized Call Handling To edit an existing Personalized Call Handling Rule: Step 1 Highlight the desired rule in the rule list in the top half of the Personalized Call Handling panel. Step 2 Press the Modify Rule button at the top of the panel. Step 3 Modify rule parameters, using the same steps that create a Call Handling Rule.
Personalized Call Handling Page 126 ShoreWare Server Release Notes
Parked Call Enhancements Introduction Definition Parked call enhancements support the following changes to the parked call feature: • Provide caller ID information to users attempting to pick up calls parked or held on any extension. • Provide caller ID and return notification for bounced parked calls that are returned to the extension that parked the call. • Extend the capability of Monitor Extension Programmable Buttons to access parked and held calls on the monitored extension’s call stack.
Parked Call Enhancements ShoreWare Server Release Notes These options are enabled by selecting the Show Caller ID Name and Number for Other Extensions and Enumerate Individual Held Calls for Unpark options on the Edit Telephony Features Permissions Class of Service panel, as shown in Figure 64. Figure 64 Enumerate Individual Held Calls for Unpark option Implementation Call Manager Users unpark calls from a monitored user’s call stack by pressing a Monitored Extension button.
ShoreWare Server Release Notes Figure 65 Parked Call Enhancements Unparked Call Button Drop-Down Menu Distinguish Bounced Calls from New Calls Background Bounced calls are unanswered parked calls that are returned to the extension from where they were parked after a specified period. Bounced calls are returned as new calls; the extension is not notified that the call was previously parked.
Parked Call Enhancements ShoreWare Server Release Notes Monitoring Extensions: Parked Calls Background Extension monitoring is a ShoreTel feature that permits a user to view the extension status of another user and answer inbound or held calls to that extension. Description This feature extends the Extension Monitoring function to monitor parked calls on the subject extension. Users can unpark a call by pressing the programmable button. Multiple users can monitor the same extension’s call stack.
ShoreWare Server Release Notes Figure 68 Parked Call Enhancements Extension Monitor – Park button The user retrieves a parked call from the monitored extension by pressing the blinking button. ShoreTel 9.
Parked Call Enhancements Page 132 ShoreWare Server Release Notes
Call Handling Mode Delegation Introduction Definition ShoreTel 9 expands Call Handling Rule Delegation by permitting users to designate other users that can change their current call handling mode. As originally implemented, CHM delegation permissions were managed by an administrator through Director. Users modify the current call handling mode of other users through the following tools: • • Operator Call Manager, by right clicking a user in the Contact Viewer.
Call Handling Mode Delegation ShoreWare Server Release Notes Step 2 Type a name or number in the edit box, as shown in Figure 70. A drop down menu displays a list of system users, filtered by the edit box contents. Figure 70 Entering the Names of Users allowed to Change the Mode Step 3 Select the Add button to add a user to the list: Parameters added to the Call Handling Mode panel include: • Allow these users to change current call handling mode: The edit box is a Quick Dial type window.
Voicemail Enhancements Introduction Definition ShoreTel 9 Voicemail enhancements include: • • Voicemail Timestamps standardization Voicemail Deletion Notification Control Refer to the Glossary for a definition of the following terms used in this release note: • Site Voicemail Timestamps Background The time stamp of voice messages is based on the time of the server where the message is received.
Voicemail Enhancements ShoreWare Server Release Notes The first warning is sent two weeks before the expiration deadline. A second message is sent one week prior to the deadline. After the time limit passes, the user receives a message stating that the messages were deleted. Description ShoreTel 9 provides administrator control over Voicemail deletion notification messages. Voicemail deletion message notification control is a Class of Service setting.
ShoreTel 9 – Client Device and Application Enhancements
IP 110 – On-Hook Dialing Introduction ShoreTel 9 adds On-hook Dialing to the IP110 ShorePhone. Description On-hook dialing supports number dialing by pressing keyboard digits without picking up the handset. When dialing a number without picking up the handset, ringback and the connected call media stream is played through the IP110 speaker. Because the IP110 does not have a microphone, users must pick up the handset to speak to the other party.
IP 110 – On-Hook Dialing Page 140 ShoreWare Server Release Notes
Call Manager – IM Privacy Introduction Definition IM Presence Privacy is a ShoreTel 9 feature that provides users the capacity to manage the visibility of their IM presence status. Restricting access to IM Presence information also prevents blocked users from sending instant messages to users restricting their access.
Call Manager – IM Privacy ShoreWare Server Release Notes Administrators can configure Class of Service options to require users to approve privacy requests or to automatically accept all requests. Users that are required to approve privacy requests are only able to view other users privacy from the Contact list. Contacts that are denied access to a user’s presence information appear as Offline in the user’s Contact list and QuickDialer fields.
ShoreWare Server Release Notes Figure 73 Call Manager – IM Privacy Presence Invitation Handling parameter • Auto accepts Invitation: All user invitations are accepted. Notification popups are displayed when a user receives a request to indicate a requestor was granted access to the recipient’s presence settings. • Prompt to Accept Invitation: Users receive a popup when another user requests access to their presence. The recipient processes the request by clicking an option on the popup.
Call Manager – IM Privacy ShoreWare Server Release Notes Privacy Invitation settings The Privacy Invitation settings section, located at the top of the Instant Message-Privacy panel, determines the user’s Presence access request method when the CoS for the user is set to User Defined. The invitation handling section provides the following options: • auto accept invitation: All requests are accepted.
ShoreWare Server Release Notes Call Manager – IM Privacy Pressing the snooze button closes the popup for the period listed on the button. If the contact is still available after the period elapses, the popup is displayed again. If the contact is not available, the popup is displayed immediately after the contact becomes available. Figure 75 Presence Change Alert popup Installation New Installations In newly installed systems: — Invitation handling for all users is set to Prompt.
Call Manager – IM Privacy Presence state of new contacts ShoreWare Server Release Notes OCS 2007 eDial Contact’s presence is displayed until access is blocked. Presence state is offline until access is allowed. Request Generation Each time new subscribers enter. Only first time new subscribers enter. Privacy and Contact Privacy and Contact lists are separate. lists Subscriber and permission lists are separate. Deleting user permission list does not generate new notification.
Call Manager – Contact Import Introduction ShoreTel 9 Call Manager supports the import of data records from CSV or XML files for display in the Directory Viewer. The CSV and XML files contain lists of personal contacts and are formatted specifically for integration with Call Manager. The CSV and XML files are not modified by the import process, nor are the contacts permanently added to the user’s Call Manager database.
Call Manager – Contact Import Figure 76 ShoreWare Server Release Notes ContactImportLocation key viewed in the Registry Editor Viewing the Contacts Directory View Contacts imported from CSV or XML files appear in the Directory Viewer, as shown in Figure 78. When contacts are grouped by data source, they appear under a heading that lists the Data Source.
ShoreWare Server Release Notes Call Manager – Contact Import Directory Item Details Details of contacts imported from the CSV or XML files are visible from the Directory Item Details panel, access by right clicking a contact and selecting View Directory Item Detail. The Directory Item Details panel, as shown in Figure 78, indicates the source of the file in the first data field and states that the record contents are not editable.
Call Manager – Contact Import ShoreWare Server Release Notes Column Heading Fields Unless otherwise specified, a contact record should contain only one instance of each field. The only mandatory data entry field is Contact ID. At least one name field and one other column heading field must contain information for each contact. The column heading fields include the following: • Contact ID: This field uniquely identifies the contact record within the file.
ShoreWare Server Release Notes Call Manager – Contact Import • Fields that do not contain double quotes or commas with double quotes may be surrounded with double quotes. • Data fields with no information translate into blank entries in Call Manager. Record Types Each line in a CSV files corresponds to one data record. The end of a record is denoted by a Carriage Return and Line Feed.
Call Manager – Contact Import ShoreWare Server Release Notes — Business Phone 2: Directory Viewer displays contents under the Business 2 column. — Home Phone: Directory Viewer displays contents under the Home column. — Home Phone 2: Directory Viewer displays contents under the Home 2 column. — Mobile Phone: Directory Viewer displays contents under the Mobile column. — Pager: Directory Viewer displays contents under the Pager column. — Business Fax: Directory Viewer displays contents under the Fax column.
ShoreWare Server Release Notes Call Manager – Contact Import XML Files XML files contain a structure set of elements. The following sections describe required file components and XML elements recognized by Call Manager. XML File Name Elements The following elements are recognized by Call Manager Contact XML files. Level 1 Elements Each file contains one Contacts element.
Call Manager – Contact Import ShoreWare Server Release Notes — valid attributes: value Example: • phone: This element specifies the contact’s phone numbers. A contact element may contain multiple phone elements, subject to the following: — valid attributes: type, name, value Type: The type attribute must be equal to one of the following: Business, Home, Mobile, Pager, and Fax.
ShoreWare Server Release Notes Call Manager – Contact Import Example The following is an example of a Call Manager Contact Integration XML file: PAGE 156Call Manager – Contact Import Page 156 ShoreWare Server Release Notes
Mobile Call Manager – Location Based Service Introduction Definition ShoreTel 9 adds Location Based Service functions to Mobile Call Manager (MCM). Refer to the Glossary for a definition of the following terms used in this release note: • • • • • • • • Active Call Handling Mode Call Handling Modes Coordinate Global Positioning System Location based service Office Anywhere Office Anywhere Extension Waypoint History MCM, introduced in ShoreTel 7.
Mobile Call Manager – Location Based Service • ShoreWare Server Release Notes OA is set for a home or office phone and MCM is turned on in a location identified by a waypoint as valid for a different calling device. Process Description Preparation Before a mobile device can run MCM LBS, the user must configure the polling method and waypoint set. • Polling Method: The polling method specifies the conditions under which the device searches for a GPS signal.
ShoreWare Server Release Notes • Mobile Call Manager – Location Based Service The CHM setting remains unchanged. Manual CHM or OA setting changes have higher priority than GPS generated settings. Manual settings remain in effect until the next GPS poll that meets the following criteria: • LBS and waypoint are re-initiated. • The new LBS coordinate either maps to a new waypoint or does not map to a waypoint.
Mobile Call Manager – Location Based Service ShoreWare Server Release Notes Step 2 Press the Menu button to display the context menu, as shown in Figure 80. Figure 80 Toggling Location-based Services Activity Step 3 Select Toggle button. Step 4 Press the Trackball. Polling Rate Selection The Polling Rate parameter, located below the Enable Location-based Service parameter, specifies the condition and rate that MCM searches for a GPS signal.
ShoreWare Server Release Notes Mobile Call Manager – Location Based Service Managing Waypoints Waypoints are accessed from the Location-based Services panel, as shown in Figure 82. All configured Waypoints are listed below the Waypoint text. Office Anywhere numbers referenced by waypoints should be defined before configuring the waypoint. Figure 82 • Selecting a Waypoint To add a new waypoint, press the Menu button and select Add Waypoint. The Waypoints Settings panel opens for the new waypoint.
Mobile Call Manager – Location Based Service • ShoreWare Server Release Notes The Range specifies the radius of the waypoint. Valid parameter settings depend on the language setting: — For English US or English UK, valid settings are 100 feet and 1000 feet. — For all other languages, valid settings are 100 meters and 1000 meters. • The Attach to parameter specifies the parameter setting selected by MCM when it receives a GPS signal that is located within the region defined by the waypoint.
ShoreWare Server Release Notes Mobile Call Manager – Location Based Service When manually selecting a current Call Handling Mode or Office Anywhere destination, the LBS initials indicate an option that is attached to at least one waypoint. Figure 85 displays three Call Handling Modes – Standard, Extended Absence, and Custom – that are attached to at least one waypoint. Figure 85 ShoreTel 9.
Mobile Call Manager – Location Based Service Page 164 ShoreWare Server Release Notes
Mobile Call Manager – Enhancements Introduction Definition ShoreTel 9 enhances the following Mobile Call Manager (MCM) features: • • • • • • Office Anywhere Voicemail Call History QuickDialer Installation enhancements Navigating through messages using the existing TUI when using visual voicemail.
Mobile Call Manager – Enhancements • ShoreWare Server Release Notes Permanent Extensions: Two permanent OA extensions are available for each user. Permanent extensions cannot be deleted or renamed. MCM permanent extensions include: — Home Extension: The Home Extension refers to the device connected to the user’s home port, as configured through Director. You cannot modify, rename, or delete the Home Extension. — External Extension: The External Extension is specified from Call Manager or Web Access.
ShoreWare Server Release Notes Figure 87 • • Mobile Call Manager – Enhancements Edit panel – User Defined Extensions A default OA extension is not selected. LBS is active and the Active OA Extension was specified by entry into the current waypoint. Users can change the Active Office Anywhere extension by pressing the Menu button and selecting Set Office Anywhere.
Mobile Call Manager – Enhancements ShoreWare Server Release Notes Call History ShoreTel 9 supports the following MCM Call History access enhancements: • Call History supports Delete and Delete All commands. • Call History maintains 50 entries after changing OA settings or restarting the MCM server. • The Missed Call counter is reset when the user views Call History. • Call History displays the most recent missed call in bold.
ShoreWare Server Release Notes Mobile Call Manager – Enhancements MCM client displays an incompatibility warning message indicating that an upgrade is required. The panel includes an Upgrade button that sends the user to the URL that provides download access to updated application. The MCM Client will not run until the new version has been installed and launched. When a user initiates an upgrade, the device launches an Internet browser while exiting or moving MCM to the background.
Mobile Call Manager – Enhancements Figure 89 ShoreWare Server Release Notes Notify Users panel – Selecting Mobile Call Manager Director displays an Internet Explorer panel indicating that the notifications were sent. Provisioning Changes The provisioning server entry text field accepts alphanumeric characters for supporting DNS name entries.
ShoreWare Server Release Notes • • • • • Mobile Call Manager – Enhancements Nokia E61i Series Nokia E65 Series Nokia E90 Series Nokia N95 Series HTC Mogul Series (Sprint PPC – 6800 version only) Feature Support Although basic MCM functions are available on all supported devices, the implementation of some functions may vary between devices because of the inherent differences of the devices.
Mobile Call Manager – Enhancements ShoreWare Server Release Notes RAZR V3 and Mogul devices do not support PIM. Network Speed Setting The default network speed setting on the Blackberry 7290 and Motorola RAZR devices is Slow 2/2.5G/CDMA. The default setting on all other devices is High Speed/Wi-Fi. DTMF Handling Some devices do not support DTMF signaling during a call when MCM is the foreground application.
Glossary 802.1x A component of IEEE 802.1 group of networking protocols that addresses port- based Network Access Control. It provides an authentication mechanism for devices attaching to a LAN port to either establish a point-to-point connection or prevent the device from accessing the port if authentication fails. 802.1x is based on the Extensible Authentication Protocol (EAP).
Glossary ShoreWare Server Release Notes Information provided by a CDR includes the number of the originating party, the number of the recipient, the time that the call started, and the duration of the call. ShortTel CDRs contain additional information. Call Handling Mode A call handling mode is a ShoreTel variable that defines a method of handling specified inbound calls. Each user is assigned five call handling modes, one of which is active and determines the user’s current call handling method.
ShoreWare Server Release Notes Glossary DID Range A DID range is a list of consecutive DID numbers assigned to a Trunk Group. Ranges assigned to a trunk group cannot overlap. A DID number can be assigned to multiple trunk groups. Differentiated Services Differentiated Services is a computer networking architecture that specifies a method for managing network traffic and providing Quality of Service (QoS) guarantees on IP networks.
Glossary ShoreWare Server Release Notes IP Phone Failover IP Phone Failover is a ShoreTel feature that continues a voice call after the ShorePhone loses communication with the its call manager switch. When IP Phone Failover is implemented, ShorePhones are configured to send a signal to their ShoreGear Call Manager switch every four minutes and to expect an acknowledgment from the switch. When a phone does not receive the return signal, it connects to another switch located at the same site.
ShoreWare Server Release Notes Glossary Office Anywhere (OA) Office Anywhere is a ShoreWare user feature that forwards calls to a designated device – either a system IP phone device or a remote telephone connected to the PSTN. Office Anywhere requires administrative authorization. Office Anywhere Extension An OA Extension is a phone number to which a user’s callers can be routed when the user has enabled Office Anywhere.
Glossary ShoreWare Server Release Notes Secure Real-Time Transport Protocol (SRTP) Secure Real-Time Transport Protocol defines a profile for providing encryption, message authentication and integrity, and replay protection to RTP data streams. Session Description Protocol (SDP) Session Description Protocol is a format for describing streaming media initialization parameters. The IETF published a revised specification as an IETF Proposed Standard as RFC 4566 in July 2006.
