Standard SCN Features
The following features are supported across all Small Community Networks:
| • | Absence Text/Call Tagging |
| • | Directory
Inclusion of SCN users and groups in the DIR directory of each system. |
| • | IP Office system directory are not automatically shared by default. For IP Office 5.0, IP Office systems can be configured to import directory record using HTTP. |
| • | User DSS/BLF
Monitoring of user status only. |
| • | The ability to use additional features such as call pickup via a USER button will differ depending on whether the monitored user is local or remote. |
| • | Indication of new voicemail messages provided by Phone Manager/SoftConsole user speed dial icon is not supported across an SCN. |
| • | Voicemail Support - Centralized Voicemail using Voicemail Pro
Within a Small Community Network, a single Voicemail Pro can be used to provide voicemail services for all the IP Office systems. For full details of installation and setup refer to the Voicemail Pro documentation. The Voicemail Pro is licensed and hosted by a chosen central IP Office system and provides full operation for that system. The voicemail features supported for the other remote IP Offices are listed below: |
| • | For pre-IP Office 5.0 IP500 systems, centralized voicemail does not require the remote systems to be running in IP500 Professional mode. Only the IP500 hosting the Voicemail Pro server is required to have an IP500 Upgrade Standard to Professional license. |
| • | Call recording.
Recording of incoming call routes is only supported for destinations on the same IP Office system, not for remote SCN destinations. |
| • | Breakout
Requires that the numbers used are routable by the system hosting the voicemail server. |
| • | Announcements
Using IP Office 4.0 announcements. Pre-4.0 announcements are only supported for queues on the system hosting the voicemail server. |
| • | ContactStore
This application is supported but requires each individual IP Office to have a VMPro Recordings Administrator license. |
| • | UMS Web Services
Users for UMS Web Services (IMAP and or web voicemail) are licensed through the UMS Web Services license on their host IP Office system. This applies even if the user remote hot desks to another system in the Small Community Network. |
IP Office 4.0: Advanced SCN Networking Features
IP Office 4.0+ allows a number of additional features. For pre-IP Office 5.0 systems, these feature require the IP Offices to have Advanced Small Community Networking licenses.
| • | Advertised Hunt Groups
A hunt group can be set to be 'advertised'. Hunt groups that are advertised can be dialed by users on other systems within the Small Community Network (SCN) without the need for short codes. |
| • | Distributed Hunt Groups
Hunt groups on a system can include users located on remote IP Office systems within the SCN network. A distributed hunt group can only be edited on the system on which they were created. |
| • | Remote Hot Desking
Users can hot desk between IP Office systems within the network. The system on which the user configured is termed their 'home' IP Office, all other systems are 'remote' IP Offices. |
| • | When a user logs in to a remote IP Office system; |
| • | The users incoming calls are rerouted across the SCN. |
| • | The users outgoing calls uses the settings of the remote IP Office. |
| • | The users own settings are transferred. However some settings may become unusable or may operate differently. |
| • | Users settings are transferred but user rights are not. |
| • | If user rights with the same name exist on the remote system then they will be used. The same applies for user rights applied by time profiles, if a time profile with the same name also exists on the remote system . |
| • | Appearance buttons configured for users on the home system will no longer operate. |
| • | Various other settings may either no longer work or may work differently depending on the configuration of the remote system at which the user has logged in. For example T3 phones the personal directory is not transferred with the user. |
| • | If a remote user's home system is no longer visible within the SCN, they are automatically logged out after 24 hours. |
| • | Break Out Dialing
This feature allows the user to select an IP Office system in the network from a displayed list and then dial a subsequent number as if dialing locally on the select system. This feature is triggered either by a programmable button or short code. |
IP Office 4.2
| • | Music on Hold Source Selection
The 4 possible music on hold sources are numbered 1 to 4, with 1 being the IP Office System Source. Where the source number to associate with a call is changed by an Incoming Call Route or Hunt Group, that number is retained when the call is rerouted across the SCN. If the receiving switch has a matching numbered alternate source that source is used. |
| • | Mobile Call Control
Licensed mobile call control users who remote hot desk to another IP Office within the SCN take their licensed status with them rather than consuming (if available) a license on the system to which they hot desk. |
IP Office 5.0
| • | Fallback
IP Office 5.0 systems can provide fallback support for Avaya H323 phones, advertised hunt groups and centralized voicemail. |
| • | Centralized Personal Directory
The personal directory numbers stored in the IP Office for each use can now be viewed and called using T3 and 1600 Series phone. If the user hot desks to another IP Office system in the Small Community Network, their personal directory is still available. |
| • | Centralized Call Log
The centralized call log features include support for users hot desking within a Small Community Network. |
| • | The user's call log records are stored by the IP Office system that is their home system, ie. the one on which they are configured. When the user is logged in on another system, new call log records are sent to the user's home system, but using the time and date on the system where the user is logged in. |
| • | Hunt group call log records are stored on the IP Office system on which the hunt group is configured. |
| • | T38 Fax Relay
For an IP500 system with an IP500 VCM card, T38 Fax relay can be configured on SIP lines and extensions. Within a Small Community Network, fax calls can transition from T38 to Fax Transport Support to be routed over the SCN. |
© 2009 AVAYA
15-601011 Issue 23.p.-
07:07, 30 October 2009
(scn_supported_scn_features.htm)
Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing
by Avaya before they become applicable to any particular order or contract. The company reserves the right to
make alterations or amendments at its own discretion. The publication of information in this document does not
imply freedom from patent or any other protective rights of Avaya or others.
All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other
trademarks are the property of their respective owners.
Last Modified: 29/04/2009
|