Avaya Communication Manager green features description

Every Avaya PBX has Special Applications–so-called “Green Features”–built in switch software but not active by default. They are listed using “display system-parameters special-applications” command and as I said, by default only one or two of them are turned on, depending on switch software. Most of these features used to be paid options but starting with CM 5.2.1 almost all of them are free for use, you can turn them on with “change system-parameters special-applications” command. If you have CM4 or older, you can still order these in Avaya. Problem is, these functions are often named rather cryptically and it is unclear what they mean and when they can be used.  Here goes the document I found some years ago that describes some of these. I dunno if this document is for internal use only but it didn’t bear “Proprietary” and “Do not publish” stigmata on it so I guess it’s all right to share it. Be careful with any green feature though–if it blows up your switch I’m not guilty. :)



This special application contains two separate but related modifications to the ISDN PRI operation on the DefinityG3 switch. The current specification of the AT&T PRI standard that is implemented in the Definity G3 does not include some modifications to the AT&T PRI standard that would allow complete operation with the Northern Telecom DMS250/100 products. The modification to the Definity G3 allows network names display transparency with Northern Telecom DMS250/100 switches by supporting the Northern Telecom Codeset 0 Display Information Element for both the transmission and reception of the Calling Party Name in the ISDN SETUP message, and supporting the Northern Telecom ISDN NOTIFY message for both the reception and transmission of the Connected Party Name.

In a standard DEFINITY Generic 3, incoming calls directed to the attendant queue will remain in queue until answered by an attendant. When night service is activated, calls can be redirected to designated night stations or the TAAS feature which allows a voice terminal user to dial the TAAS access code to answer the call. This feature allows any voice terminal to pickup a call from the attendant queue when the number of calls in queue has reached the administered warning level by dialing the TAAS access code regardless of whether the system is in night service or not. The calls in the attendant queue may consist of both internal and external parties. Priorities can be assigned to the various facility types using the administration terminal to alter the order in which the calls will be answered by the attendant or by the TAAS pickup operation. The external alert equipment or ’TAAS gong’ will not alert when a call is waiting in the attendant queue during the day as is does in night service. Night service will continue to operate normally.

This feature will change the operation of CDR (Call Detail Recording) such that the actual party that answers a call is considered to be the destination party on the record. In the case where the dialed party answers the call, then no change is seen from the standard operation. If the call has been redirected due to coverage, then the party that answers the call first (coverage point or principal) will be considered as the destination address on the CDR record for the call. This feature will operate with intra-switch CDR as well as trunk group CDR records.

For analog stations with the call waiting feature(s) activated and the Flash for Answer/Hold field active, this Special Application provides automatic hard-hold activation when the called-party flash-hooks upon receiving the call-waiting indication. It also provides automatic unhold of hard held calls for those same stations.
In standard Definity G3iV3, when a call-waiting indication is received and the called-party flashes the switch hook, the current call is put on soft-hold. The called-party then has to dial the Answer Hold-Unhold feature access code to answer the waiting call. The soft held call at that time becomes a “hard” held call. The user can then perform any operation that does not involve the held call, or toggle back and forth between the two calls via flash-hook and the Answer Hold-Unhold feature access code.
In a standard Definity Generic 3, a hotline station is always routed to the pre-stored number once the hotline station goes off-hook. Therefore, PBX station features cannot be accessed by the hotline station. This Special Application will allow stations to access station features administered on the system, e.g. Call Forwarding, Abbreviated Dialing etc., by dialing the digit ’*’ as the first digit after the hotline station goes off-hook or after a non-hotline station has dialed the ARS feature access code.
When a hotline station (with the ARS FAC as its pre-stored number), goes off-hook the system will provide ARS dial tone. If the first digit dialed by this hotline user is ’*’, then a second dial tone will be provided to the hotline user to indicate that the system is treating the hotline user as if it is a “regular” single-line user, i.e. all PBX station features available to this station will be accessed in a normal manner. If the first digit dialed is other than ’*’, then the system will treat the call as a normal hotline call. A non-hotline station will also receive PBX dial tone if ’*’ is dialed after dialing the ARS access code.

This feature will check to see if the attendant group is in night service before determining if the external or internal coverage criteria should be used to find a coverage path. If the attendant group is in night service, then all calls will be considered internal calls. If the attendant group is not in night service, then a call from an external source will be treated as an external call. This feature will be desirable for customers that desire a night/day service change for the external coverage criteria. This is useful when the operation is staffed during the day to handle the external callers, but at night desires to use the internal path to include voice mail services in the coverage path.

All feature operation changes will be to the “Emergency Alert Redirected to a Station” feature. Emergency alert to the attendant remains unchanged. This feature provides features, which are particularly useful with multi-line (e.g. digital) voice terminals that have displays. Therefore, it is recommended that stations, which are to receive Emergency Calls, be multi-line stations with displays.
The following feature changes have been made, and will only be activated when the SA feature bit is set:
· When an Emergency call comes in to a station, the station will receive priority (usually triple, it is now administrable) ringing. Currently it receives single ringing. If a station is off-hook when the emergency call comes in, it will receive only 1 cycle of priority ringing.
· When an Emergency call comes in to a station, the station display will indicate an emergency. Currently it indicates a redirected call. If the Emergency Station is equipped with a display it will show a message of the format:
n=<calling party name> <calling party extension> EMERGENCY
where “n” is the appearance (a through j) and “calling party name” is the name assigned to the station through standard administration. For example, if an Emergency Call rings on the first appearance, a display might show:
a=Cafeteria 4701 EMERGENCY
If more than one call is ringing at a Crash Phone, only the information from the first call is displayed. If the first Emergency Call is answered, then the information from the second Emergency Call is displayed.
· When an Emergency call comes in to a line with bridged appearances and is answered at one of the appearances, the other appearances will continue to ring until answered or the call is finished. Currently the ringing stops when a bridged appearance answers.

The coverage feature in the standard G3 switch has an option to route calls differently depending on whether the call being covered is an internal (station) call versus an external (trunk) call. This decision is based on the originator of the call. If the originator of the call is a trunk or attendant, the call will use the external coverage criteria.  If an incoming trunk call is answered by a station and then the station attempts to transfer or conference with another station, and that call goes to coverage, the internal coverage will be used because a station originated the call. This feature changes that operation. With the green feature bit set the system will now check for a “soft held” call associated with the existing call, and if the soft held call was originated by a trunk, then external coverage will be used.  With the green feature bit set, when an incoming trunk call is transferred from one station to another and subsequently goes to coverage, the external coverage path will be used. This feature is desirable for specific customers who never want incoming trunk calls to go to an internal coverage path.

SA7491 – EXPAND DS1’S TO 332 (G3R) AND 556 (S8700) LINE SIDE ONLY
This special development will increase the maximum DS1 circuit pack assignments from 166 to 332 for the system (G3r (line-side only) and from 400 to 566 for S8700, when the green bit for Expand DS1s is set to “(y) es” in the ‘system-parameters special-applications’ form.

The directory feature will be changed to be able to find names on other switches in the DCS network. To do this there needs to be connections to the other switches in the network. The IDS+ feature will use Non-Call Associated Temporary Signaling Connections (NCA TSC) to accomplish this. A new application type of NCA TSC, called ids+, will be created. Each switch that wishes to be connected in the IDS+ network needs to have one IDS+ TSC to each other switch in the IDS+ network. All switches in the IDS+ network need to be in the same DCS network, but not all switches in the DCS network need to be connected to the IDS+ network. Furthermore, there could be more than one IDS+ network within a DCS network. From the user perspective, the feature functions the same as the original directory feature. The directory mode is entered using the directory button, next is used to scroll through valid names, and call display will call the person currently displayed on the directory display. The user perceptible difference is that the user will now find names on other switches in the network when they use the directory feature. When a digit or the “next” button is pressed while in directory mode, the system will first look up the matching name on the local switch. It will then build an ISDN message that will be sent to all TSCs with the application type of ids+.  The system will then wait for all the responses to be returned, and display the alphabetically earliest of all the responses. Requires minimum of Release

This feature is an enhancement to provide better operation in situations where a set of users on a system desire the conference tone feature, but the conference tone feature should not be activated for all users.  SA7666 will check to see if any member of a conference call has the “Conference Tone” flag set to “y” on their COS before applying the conference tone to the call. If the conference call has only trunks on the call, then conference tone will always be applied. This feature will be desirable for customers that do not require the system-wide activation of the conference tone feature.

This feature provides the user with the capability to display up to 27 characters for both the name of the called party and calling party along with the extensions and redirect reason. If the set type is an 8434 then the display uses 27 character names otherwise the display will be the standard 15 character names. The Enhanced Display for 8434 Terminals for Redirected Calls 27 character display is determined by the destination terminal type. On a redirected call using 27-character name, both lines of the display will be used to show the calling party’s name and extension, called party’s name and extension and a redirect reason. If ANI is available from an incoming trunk then the digits will be displayed on the first line instead of the calling party’s information.  Feature b requires a minimum of R6. or R8.

This feature provides the user with the capability to display up to 27 characters for both the name of the called party and calling party along with the extensions on a bridge appearance of the called party’s terminal. The 27-character display is determined by the called party’s terminal type, which must be a 2×40 2-line display terminal. Terminals that are 2×40 2 line display sets include: 8434D, 7444D, 7407+, 7407D, and Callmasters. The top line of the display will have the calling party’s name or trunk name, up to 27 characters, and the extension or trunk access code. The second line will have the called party’s name, up to 27 characters, and the extension followed by the redirect reason. If ANI is available from an incoming trunk then the digits will be displayed on the first line instead of the calling party’s information.

This feature to allow displaying the in-dialed digits for isdn-pri trunk groups. The customer currently can route all calls to an isdn-pri trunk group to a VDN by using the call-by-call features on the 2nd page of the isdn-pri trunk group form. They delete the in-dialed digits and insert the VDN. This works great, but they have no backup mechanism if the link to ASAI is down. By displaying the in-dials to the agent, the agent can quickly type in the dialed number and bring up the customer account.

This feature is to allow a call center to close for the night and direct all calls to the Night Service destination. This Night service destination will probably be to another switch within the customers network. The customer will do this by inserting the aar access code and a prefix in front of the dialed digits by using the digit insertion on page 1 of the DID trunk group form. The “Night Service:” destination will be administered to a VDN. The vector that the VDN points to will “route to digits”. This will send the call off according to the AAR digit analysis administration, thus routing the call to another switch within their network.

This feature is to provide a station button that will display certain information contained in the UUI field of an ISDN setup message. This will be used when the customer networks their call centers together via an ISDN private network.

The Enhanced DID Routing feature provides for a total Data Base bypass for incoming DID calls, where all 1-16 digit in-dials are valid numbers if the DID trunk group is administered to redirect to a VDN, Hunt Group or Station Extension.
The Enhanced DID Routing feature allows all calls to a specified DID trunk group to be routed to the same destination independent of the number dialed. The Enhanced DID Routing operation is initiated by administering the “Incoming Destination:” and the “Expected Digits:” fields on the DID trunk group form. If the “Incoming Destination:” field is NOT administered on the DID trunk group form, then the trunk group will work as a normal DID trunk group. The “Incoming Destination:” field may be administered to a Hunt Group, Station extension or a VDN. The “Expected Digits:” field is to be administered to the number of digits expected from the Central Office (CO) and may contain a value from 1 – 16.

This feature gives options for Call Vectoring to allow the user to enter data using the # and * keys in addition to the digits 0 through 9. Without these options, the * key causes entry to start over after dropping previously entered digits, and the # indicates end-of-entry. There are system-wide options, applying only to “Vector Collect” call vectoring steps, but applying to all “Vector Collect”’s in all vectors. The digits collected are made available to the ASAI interface via the “adjunct” step. The # will have the value Hex 23 (0x23) and the * will have the value Hex 2a (0x2a).  These options are available so that customers may prompt for entry of account codes or other information which contains # or *, and have that information transmitted over ASAI to a host. These options will be referred to below as the Collect Literally Options. There will be an option for * and an option for #; both options may be active together.

Currently, when service observing a non-ACD station, the observer dials the number to be observed. The observer will then observe any calls that are active on that extension number, whether they are call appearances or bridged appearances of the extension. This feature, when administered, will allow the observer to observe any active call on the set, which contains the call appearances of the dialed extension. This allows the service observer to observe a particular physical set, regardless of whether the user is active on their own call appearance or a bridged appearance of some other extension. This feature can be activated on a system-wide basis only. When administered, all service observing calls will be treated the new way.

There currently exists an interaction with Call Coverage and Send All Calls where a calling party receives ring back even though no terminating parties are available. A calling party will receive ring back in the following scenario: called voice terminal has Call Coverage administered, called voice terminal has activated the Send All Calls feature, and no coverage points available. Calls redirected via Call Coverage maintain an appearance on the called voice terminal if a call appearance is available to handle the call. This feature operation is considered a feature debt between Definity® G2 and Definity® G3. This green feature, when administered, will apply busy tone to the calling party and drop the called voice terminal when the called voice terminal has activated the Send All Calls feature and no coverage point is available. A call appearance, if available, on the called voice terminal will be maintained of the redirected call and the calling party will receive silence during the Caller Response Interval (CRI). Once the CRI has expired and the determination made that there are no coverage points available the calling party will receive busy tone and the call appearance on the called voice terminal will be dropped. This feature can be activated on a system-wide basis. Once the green feature is administered, all calls with Send All Calls active and Call Coverage administered will be treated in the same manner.

When an extension is to be moved from one switch to another using the Extension Number Portability feature, an entry for the extension to be moved is made in the UDP table. This table is currently limited to 50,000 entries on the G3r. The 80000 UDP Extension Records feature will increase the size of this table to 80,000 entries. This feature affects only the G3r.

The Dial By Name feature is a method for incoming calls to a PBX to be routed to a destination based on the name of the person to be reached.  The incoming call will receive an announcement prompting them for the various choices that the call can be routed to. This development will include an additional option, the Dial By Name feature. When this option is chosen, the user will then be prompted by announcements to instruct them how to dial the name. When a unique match with a name in the database has been found, the user will be routed to the appropriate extension.

This feature provides the user with the capability to enter a CDR account code with a length variable from 1 to the maximum number of digits assigned in the system parameters cdr form. When fewer than the maximum number of digits is desired, a “#” terminates the account code and dial tone is returned to the user as if the maximum number of digits was dialed.

This enhancement increases the number of Facility Busy Indicators on the large MIPS processor from 10,000 to 25,000. The number of buttons tracked per resource will remain the same at 500 for the mips. This enhancement is to close the gap from the capacity of G2, which are 32,000.

This feature causes DEFINITY to send an ISDN Redirecting Number IE (or its Nortel equivalent, the Original Called Number IE) when a call is forwarded or covers off-switch over an ISDN trunk group. The IE is included in the outgoing SETUP message, and contains the number of the originally called party. The number is formatted according to the Numbering Format administered for the outgoing trunk group.

Special equipment is used in the power industry to access “ADASE” tie trunks using carrier systems. The word ADASE (pronounced adacee), a transliteration of the Russian abbreviation “power network equipment for long distance automatic communications”, is used to refer to this special equipment. Its purpose is to allow direct high priority access by “dispatchers” to the tie trunks while allowing the PBX low priority use of the trunks when they are not needed by the dispatchers. The TN2209 Circuit Pack, an analog 4-wire tie trunk circuit, developed as an “integrated converter” using the TN760D software interface, can be used for this application. The present document assumes that these changes have been made. An “ADASE port” consists of one 4-wire trunk port (TN2209) “associated” with a 2-wire line port (e.g. TN746-). There may be as many as 140 ADASE ports in a system. Each trunk port provides 4-wire access to an ADASE carrier channel, two signaling leads to the dispatcher consoles and one signaling lead to optional, locally provided, alarm reporting equipment. Each line port provides 2-wire “Tip/Ring” access to the dispatcher consoles which appear as “telephone extensions” (this is like the multiple telephone extensions in your house, i.e. 1 analog line loop with multiple telephones on the loop). There may be as many as 8 dispatcher consoles in a system.  The tie trunks must be administered as immediate start both incoming and outgoing, and the dial type must be rotary both incoming and outgoing.

The Support Calling Party Category on QSIG Code Set 5 feature identifies the category of a calling party on an outgoing call over a QSIG trunk. The CPC on QSIG feature is described in ECMA 143 specifications. This feature is supported in many European vendors’ PBXs, however DEFINITY® ECS does not currently support the CPC feature since it follows ISO standards which do not include the CPC capability.  The ECMA 143 standard supports four party categories: unknown, extension, operator and emergency extension. A fifth category, data, will be added for compatibility with other switches and for inter-working with R2 MFC signaling systems so that DEFINITY® may be configured as an endpoint or a transit between QSIG trunks and R2 MFC trunks.

When the SA8140 field is set to “y”, several new fields will appear on the console parameters screen. Two new administrable columns will appear titled “Route to Priority Group?” and “Emergency Tone?” For each priority level, the customer can specify whether calls to that priority will go to the priority attendant group, and whether calls of that priority will give emergency tone. To designate the attendant group a priority will route to, enter “y” to have calls for that priority level answered by the Priority attendant group, “n” to have calls with that priority routed to the non-priority attendant group.
If the entry for “Emergency Tone?” for a priority is “y”, then all calls routed to the attendant group for that priority would give emergency tone to the attendants in that group (that are not already on an emergency tone call) until the call is answered.
There will also be a new entry for “Attendant Group Redirection Extension” on the console parameter form. This field may be left blank, or may contain the extension of a vector, hunt group, or station. If the Attendant Redirection Extension field contains a valid extension, a call to the attendant that would be routed to the non-priority attendant group will be routed to the Redirection Extension instead. Once the call is routed to the redirection extension, it will no longer use the attendant queue priority that was associated with the call (since this priority is used only by the attendant queue.)

When the SA8141 field is set to “y”, a new column will be added on the “change listed-directory-number” screen This column will be titled “Pr” (for Priority) and it will appear as a __ for each LDN. To assign a priority for this LDN, the user will enter a priority level 1-12 on the line. (A priority of 1 is the highest.)  When a calling party dials an LDN and the call cannot be answered immediately (it must go into the attendant queue), if a priority is assigned to this LDN, the call will be placed in the queue with the LDN’s priority. If no priority is specified for the dialed LDN, the priority will be based on call type. Once in the attendant queue, calls of highest priority will be answered first. If two calls are of the same priority, they will be serviced according to the time they entered the queue.
This feature can be used alone, or along with SA8156 – Priority Attendant Queuing by COR. If a station dials an LDN the calland if the station’s COR has a priority assigned (using SA8156), and there is a priority assigned for the LDN, will be placed in the attendant queue according to the highest of the two priorities (station COR or LDN priority). If no priority level is administered for this station’s COR (either because SA8156 is not active in the system, or SA8156 is active but there is no priority assigned to this caller’s COR), the call will be placed in the queue with a priority based on the LDN priority. If no priority is specified for either the calling party COR or the dialed LDN, the priority will be based on call type. In a multi-switch arrangement, the priority of the calling party’s COR is passed between switches in a DCS message.

This feature is used to suppress a stations’ extension number when calling other stations. Stations will have this feature active by a new field on the COR form that indicates whether this stations’ number should be suppressed. However, if one of these stations calls a station that has console permissions COS, and the “override by COS” feature bit is set, then the stations’ number will be displayed.

The Update Display for Redirected Calls feature enables the originator of a call to see the name and extension to which a call is being redirected. The redirections that are supported are call forwarding all, call forward busy/don’t answer, call coverage, send all calls, and station hunting. Intraswitch redirections will update the originator’s display with the principal station name, the redirection reason, the “redirected to” name and number.
For interswitch calls, between two Definity® switches supporting this feature connected via isdn-pri, originating station’s display will be updated with the redirection reason, the “redirected to” station name and extension. If the principal terminating station is on the same switch the display will also contain the principal station’s name. The “redirected to” information will be made available at the originator’s switch through the use of a NOTIFY message containing a Display IE and a Redirection Number IE.
Redirections from a Definity® switch offnet to a NORTEL switch will not utilize this feature’s display updates, however will follow the standard Definity display requirements. Calls offnet to a NORTEL switch will cause the display to be updated with “redirected to” number if the call subsequently redirects from the NORTEL switch.  The display updates will occur only during alerting when the redirection is able to terminate (i.e. ringing).

SA8156 field is set to “y”, a new field titled “Attendant Queue Priority: ” will appear on the Class of Restriction administration form. To assign a priority for this class of restriction, enter a priority level 1-12, (a priority of 1 being the highest).  When a station or trunk dials the attendant group (normally “0”) and the call can not be answered immediately (it must go into queue), if the station’s COR has a priority assigned, the call will be placed in the attendant queue according to the priority of the station’s COR. If no priority level is administered for this station’s COR, the call will be placed in the queue with a priority based on the call type. Once in the attendant queue, calls of highest priority will be answered first. If two calls are of the same priority, they will be serviced according to the time they entered the queue.  If the station makes an Emergency Access call to the Attendant, the call will be queued based on the higher priority (the emergency access priority or the station’s COR priority). If the call is of any other call type, the call will be queued based only on the COR priority (or, if no COR priority exists, the call type priority).
In the event of an interposition call to the attendant, or a call to the individual attendant extension, the call to the individual attendant extension will be queued with the priority of the caller’s COR, and will be serviced before calls of a lower priority that are already in queue, but after calls of a higher priority.
In a multi-switch arrangement, the priority is passed between switches in a DCS message. If the DCS signaling link is not operational, the originator’s priority is not passed between switches and the priority will be based on the incoming trunk group COR. In addition, each switch in a multi-switch arrangement must have the “Attendant Priority Queuing by COR” feature active for the priority scheme to exist across switches.

This feature is not to be made available to general call center customers since the provision of announcements or music without returning answer supervision is only allowable (based on public telephone network requirements) when the switch/PBX is part of the PTT/carrier network and is providing service such as Directory Assistance. Generally call centers are required to return answer supervision when providing anything other than a tone (ringback, busy or reorder). A custom/customer option is required to restrict access to this feature.
A new “Delay ISDN CONNECT for Announcement” option will be added to the Vector Directory Number (VDN) administration form that when set to “y” prevents the ISDN “Connect” message from being sent when an announcement is played via the “announcement” vector step. The application of this option for a call is based on the active VDN for the call. That is, VDN Override applies to this option. The field on the VDN form will only be displayed when the “Toll Free Announcements until Answered” option added to the “change system-parameters special applications”.

Five new keywords are added to the second page of the “system-parameters cdr” form. This page is dynamically created when the user selects custom as the “Primary Output Format” on the first page of the “system-parameters cdr” form. Prior to this feature start time, start date, four digit start date and four digit end date were not available for customizing the CDR. In the standard version the date and time are end date and time. Time is displayed in HHMM without seconds in the standard version. This feature will add seconds to the start and end times along with adding seconds to the duration time.  The call processing format function formats and prints the CDR data. This function in the standard version is capable of formatting and printing the custom CDR. The ability to print the start time, start date, four digit start and end time and the seconds is added to the format function. This is the only call processing modifications needed to support this feature.

When a user goes onhook on a multi-appearance telephone set, the system will automatically select an appearance on the set. This gives the selected appearance preference the next time the user goes offhook to make a call. The red light next to the selected appearance is illuminated to indicate this. The appearance that is normally selected is the first appearance on the user’s set. Depending upon an option on the station administration form, the system may restrict itself to selecting the first call appearance on the set or it may select either a call appearance or a bridged appearance, whichever comes first. The system may also select an appearance other than the first appearance if there is a ringing call on one of the appearances on the set and the set has Ringing Appearance Preference active or if there is an active call on the first appearance and the set has Idle Appearance Preference active.  The location of the selected appearance (and the red light) may change while the set is onhook if the user manually selects another appearance or if a ringing call comes in to one of the appearances on the set and the set has Ringing Appearance Preference active. When the user eventually goes offhook again, he/she will be connected to whichever appearance has the red light illuminated at that time.
The Prime Appearance Preference feature will allow an appearance other than the first appearance to be specified as the prime appearance for the set. Either a call appearance or a bridged appearance may be specified as the prime appearance. The station administration form is used to specify the prime appearance. If a prime appearance is specified for a set and there are no ringing calls on the set. The prime appearance will be selected when the user goes onhook. If nothing happens to change the appearance selection, the user will be connected to the prime appearance when he/she next goes offhook.  Requires minimum Release

This feature will add the capability for a user to add or remove an FBI from the users station. The feature will be
accessible by either a feature access code or feature button on the set. The user must have a class of restriction that allows the use of the feature. The extension to be used for the FBI must have a class of restriction that allows the extension to use as an FBI extension.  This feature will not change the FBI functionality.

SA8312 – Meet Me Paging
It is the intent of the SA8312 software to maintain the Meet-Me Page feature user operation as identically as possible to the SD6915 basic Meet-Me Page feature operation. For example, the SA8312 software will still allow a paged user to retrieve the page call by dialing the ‘#’ followed by the page line extension number.
In the SD6915 environment, it is necessary to configure the network such that all paging adjunct interfacing is done through a page switch and a page call normally is retrieved from a non-page switch. However, in an SA8312 network, it is no longer necessary to dedicate a switch purely for the paging purpose. The SA8312 network can be configured as a centralized or a distributed network when it is connected to the Glenayre Page Adjunct.

The Idle Appearance Preference option allows users to receive an idle appearance when lifting the handset even if there is an incoming call at another appearance. However, the user does not receive a display for the incoming call.  The SA8323 Idle Appearance Display Enhancement allows a user with Idle Appearance Preference option set to receive a display of incoming call information.  Requires minimum Release

The X-Station Mobility Feature will allow phones remote over a trunk interface to be controlled by DEFINITY as if they were directly connected to it. This is accomplished by administering a station record for each station of type “X-Mobile.”
These “X-Mobile” stations will have additional administration information further describing the capabilities of the remote station. If the call or other signal needs to be sent to an X-Mobile station DEFINITY will use a D-Channel in the BRI trunk group associated with the X-mobile station. Additionally, when a call arrives over a D-Channel, which carries X-Mobile traffic, that call will be analyzed to check if an X-Mobile remote station originated it.
If it was, then the call is re-associated in call processing as an internally originated call from the local X-Mobile station. This will allow a large number of DEFINITY features to work for the remotely controlled station, including bridging. This feature will be used to provide DEFINITY feature integration with Denso 300M wireless handsets.  Currently, DEFINITY Wireless DECT Release 2.0 uses this capability to field a competitive wireless offering.
This Green Feature Specification will define a BRI trunk used as the X-Mobility trunk interface. In addition, the basic X-Station mobility feature set will be expanded to handle adjunct to adjunct roaming, and adjunct-to-adjunct handovers. Four new R8.1 features will also be explicitly supported in the X-Station Mobility feature set: Group Call Pickup, Reset Shift Call, Transfer Recall, and Circular Station Hunting.  The collection of these changes will allow the Denso 300M to provide a near seamless integration of PHS wireless stations that are controlled through DEFINITY.

This development will enable the MCIWorldCom Network Call Identifier to be mapped into an encoded equivalent value of the UCID in DEFINITY for the purpose of easier call tracking within the call processing at Compaq Call Centers as well as aiding in trouble reporting. It will also provide the ability to recreate the same UCID by the same methodology when a call is transferred through the MCIWorldCom network to another DEFINITY Call Center. This will benefit the end user insofar as it allows for the call data record to be re-associated with it at the secondary call-handling site. This functionality is required since the end user is served by MCIWorldCom’s “Take back and Transfer” functionality which is executed by DTMF in-band signaling being sent back to the network on a particular “B” channel and the network disconnecting the call to the DEFINITY. Since the Network Call Identifier stays the same throughout the life of the call, the mapping to the same UCID in multiple DEFINITYs with this Special Application is possible. The following assumptions are the basis for this development.
MCIWorldCom indicates that this development will provide a unique UCID number for Compaq.
The DEFINITY receiving the call will provide an incoming gateway function for this functionality.
The DEFINITY receiving the call from the network will be able to tandem the call to another DEFINITY, if the connection is with private network facilities, utilizing normal DEFINITY to DEFINITY UUI.
The DEFINITY will not provide outgoing gateway functionality back into the public network.
In other words, if a DEFINITY routes a call back into the public network, it will result in a new Network Call Identifier in the network and the DEFINITY will not provide mapping of the UCID to attempt to create a similar number for the network to track with. During the “life” of a call, the Network Call Identifier is never changed. Hence, that ID is always mapped into the same UCID at every DEFINITY that the call is delivered to with the Special Application active.  Requires minimum release

This feature will provide the user with the capability to control the ring behavior for each line appearance and bridged appearance from the station. The feature will be accessible by either a feature access code or a feature button on the set. In order to assign the new feature button to the set, Per Button Ring Control must be enabled on the station form.  After assigning a button, Per Button Ring Control can only be disabled after the feature button has been removed.  Secondly, this feature will add a new feature button, which will allow the user to display the type of ringing assigned to a line or bridged appearance.  Requires or in controlled introduction.

The purpose of Special Application SA8434 is to provide a new Green feature that allows the capability of answering an incoming ISDN trunk call routed to a logged-in Definity ACD agent without sending an ISDN CONNECT message to the Public Switched Telephone Network (PSTN). By doing this, there is no PSTN switch billing for the call as required initially for the operation of the Telecom Italia Directory Assistance systems in Italy. Currently, the ISDN CONNECT message is always sent when an incoming ISDN call is answered by a Definity ACD agent.  In addition to the above, this Green feature also causes the ISDN PROGRESS message to be sent to the PSTN instead of the ISDN Alerting message for the “converse-on” vector step. This is required to prevent the PSTN switches in Italy from applying their own switch ringback to a call when the Definity sends the normal ISDN Alerting message for this vector step. It is necessary to prevent any internal PSTN switch ringback since there is no ISDN CONNECT sent when the agent answers a call when this Green feature is activated (i.e., there is no ISDN message sent to stop the PSTN switch’s internal ringback and do a cut-through after agent answer).  The operation of this Green feature on a call-by-call basis is achieved by a new “Delay ISDN CONNECT message on Agent Answer” field on the Definity VDN system administration form. This Green feature is only applied to an incoming ISDN call that is routed through a VDN whose “Delay ISDN Connect message on Agent Answer” field is set to “y”.   Requires minimum Release

The purpose of Special Application SA8439 is to provide a new Green feature that allows the capability of forwarding the Calling Party Number of an on-hold ISDN call to the SETUP message of the outgoing ISDN trunk for the second leg of a call transfer or call conference operation. The operation of this Green feature is provided on a call-by-call basis for only ACD calls that have been routed through a VDN where the “Forward Held-Call CPN” field is set to “y” on its VDN system administration form, routed to a DEFINITY ACD agent via a “queue-to” or “backup” vector step, and then placed on-hold in order for the call transfer or call conference operation to take place.  The forwarding of the held ISDN call’s CPN provided by this Green feature applies to call transfers or call conferences done by a station user using the “Transfer” or “Conference” station buttons. Also, this same capability is provided when the call transfer or call conference is done via an ASAI “Transfer” and “Merge” operation invoked by a CTI application. However, it is important to note that the reliable operation of this feature for ASAI call transfers or
call conferences is dependent on only one ISDN call being on-hold when an ASAI call transfer or call conference operation takes place. Otherwise, with more than one ISDN call on-hold, the correct CPN may not be forwarded in the SETUP message of the second leg of the call.   Requires minimum Release

Definity currently supports the QSIG call forwarding feature. If a call comes into Definity over an ISDN trunk administered for supplementary service option B and the call terminates to a station with call forwarding currently activated to an offnet number, Definity sends an ISDN facility message back toward the switch from which the call originated. This message contains the number of the forwarded-to party and is intended to allow the originating switch to pick a better route to reach the forwarded-to party. Definity generates the number included in the facility message by taking the number entered when call forwarding was activated and then processing it to generate a complete number. Depending upon the number, this processing may include UDP, ENP, AAR and/or ARS digit conversion and analysis, route pattern digit manipulation, and other steps.
The Unmodified QSIG Reroute Number feature allows the option of bypassing the number manipulation that is used to generate the number that is included in the facility message. If the feature is active and the call arrived over a trunk group with the appropriate administration, the number placed in the facility message will be the exact digits entered when call forwarding was activated with no change or processing. In particular, if the digit string entered when call forwarding was activated includes an AAR or ARS feature access code, that feature access code will be included in the number placed in the facility message.

Expand memory to accommodate up to 2,000 Call Coverage Paths and 2,000 Remote Coverage points on G3si. On G3r expand to accommodate 10,000 Remote Coverage points to match the current limit of the Call Coverage paths.

SA8481 – Replace Calling Party Number with ASAI ANI
This green feature allows an ASAI application that is placing an outgoing ISDN call via the third party make call operation to supply information that will be used by Definity to build the calling party information associated with the outgoing call. The ASAI application does this by including the desired calling party information in the User to User information element portion of the third party make call request. In order to use this green feature, a customer-supplied ASAI application is required along with the standard ASAI libraries.

SA8500 – Expanded UUI Display
This special application will provide for a new button on Callmaster IV display terminals. This new button will enhance the User-to-User Information (info button).
The button display information will contain thirty-seven (37) characters for the following:
10 – Digit ANI
4 – Digit DNIS
4- Last four digits of SSN
16 – Digit account number
3 – spaces
This information will be displayed on the second line on the Callmaster IV.

SA8507 – Support H245 DTMF Tones
Currently, R11.2 load 111 and earlier, when an MV is connected to a third party vendor H323 VOIP gateway, sometimes no DTMF tones were passed through from MV to the other vendors and vice versa. Vendors like CISCO and Clarent are known to have this problem when they interop with MV.
In H323 standard, DTMF tones are passed via the H245 link. When MV connects with vendors like CISCO or Clarent, neither side of the call tried to bring up the H245 channel and no H245 channels were established, thus no DTMF were passed through. Between MV and MV, this was not a problem. MV has its own proprietary way of passing DTMF tones. This problem is only seen when other vendors support FastStart call setup procedure, which is a procedure to setup call without establishing the H245 link.

SA8508 – Multiple Emergency Access Codes
Multiple Emergency Access Codes is a special development for the Mayo Clinic. SD6915 provided Mayo with the ability to have up to 10 emergency access codes with unique displays. However, standard G3 Emergency Access to the Attendant feature only allows one access code. Since the Mayo Clinic is currently using only 2 of the ten available access codes, this feature will only provides one additional access code.

SA8510 – Support PSTN Sub-Address in UUI
This Green feature maps Called Party “Sub address IE” digits sent with an incoming call’s ISDN SETUP message into the ISDN UUI IE information stored by the MultiVantage call-processing for the call. When this call is routed to a VDN or station where ASAI event-notification has been set up by a CTI application, then the call’s ISDN UUI IE information (i.e., the Sub address IE digit information) is sent to the CTI application in the “UUI data IE” field of an ASAI event message. This feature is supported for PRI, BRI, and IP trunks only.
This SA8510 Green feature is intended only for the NTT customer in a field load of the MV 1.2 GA release. This Green feature is not intended for general usage by any other customer than NTT since it overwrites ISDN UUI IE information that may be sent with an incoming ISDN call for screen-pop purposes.

SA8517 – Authorization Code by COR
The standard MV Authorization Code (Auth Code) feature provides a control of system users’ calling privileges. The user’s calling privilege is generally enforced via the COR (Class of Restriction) and FRL (Facility Restriction Level). The Auth Code feature allows a terminal user to acquire a higher FRL belongs to the entered authorization code in order to access a facility that is prohibited for the calling terminal. However, in certain circumstances if a high FRL authorization code unknowingly becomes unsecured, then all users knew the auth-code could access facilities from any terminal, which is restricted to access such facilities in the first place. To alleviate such situation, SA8517 special application is thus implemented.
SA8517 special application is developed as green feature. The SA8517 will introduce an extra level of permission validation after an authcode is entered from a terminal. A new permission table is introduced via the existing COR administration. The table element is valid and visible only if the SA8517 green feature is enabled.

SA8518 – Automatic Callback with Called Party Queuing
Currently, the standard MultiVantage Automatic Callback feature allows station users who placed a call to a busy or unanswered a station in the network to be called back automatically when the called station becomes available. This green feature enhances the Automatic Callback feature by removing the standard restriction of one active callback per extension. Additionally, this feature allows callbacks to be activated for soft numbers (i.e. AWOH stations), as long as the soft number has at least one bridged call appearance on a physical station.

SA8520 – Hoteling Application of IP Terminals
This feature is designed to work with customer installations which use a computer based scheduling system to reserve office space for their mobile workforce. Currently Avaya supports these applications with DCP digital terminals but not with IP terminals. The feature will allow the customer to reassign the extension number for a registered IP telephone using only the SAT interface.

SA8558 – Expand VuStats/MWI Buttons

Currently, CM is limited to 1800 Remote Message Waiting Indication and 1000 VuStat buttons on the S8700 platform.  This enhancement will expand the capabilities of the S8700 platform to allow for up to 5000 Automatic Message Waiting Indication (MWI) and up to 5000 VuStat buttons per system.

SA8567 – PHS X-Station Mobility over IP
This feature aims to provide user with PHS wireless phone solution over IP network. Integration of the MultiVantage and the PRIMANET shall provide user with equivalent features to existing PHS solution that is integration of DEFINITY R8.1 BRI interface PHS X-Station Mobility feature [2] and the DEFINITY-MX PHS adjunct system. (Formerly DENSO-300MX)

SA8569 – Service Observing Warning Tone
The Service Observing feature allows a supervisor to monitor the performance of a call center agent by listening to his/her calls. A warning tone is normally played to all parties connected to a call that is being service observed. This tone lets everyone know that the call is being observed. An agent could use the presence of the warning tone to modify his/her behavior, based on whether a particular call is being observed. If the ‘No Service Observing Tone Heard by Agent’ feature is active, the service observing warning tone will be played to all parties on the call except for the call center agent. This fulfills the requirement of letting the caller know that a call is being monitored without letting the agent know. This feature will be implemented as a green feature.

SA8573 – Call Xfer via ASAI on CAS Main
This feature provides the user with the capability to allow CAS Main calls to route to IVR ports or live agents, and then redirect this call via ASAI message to an extension/live agent either on the CAS Main or CAS Branch location.

SA8582 – PSA Location and Display Enhancements
The (SA8582) PSA Location and Display Enhancements green feature enhances the existing PSA feature. The PSA feature, in general terms, allows a user to associate a compatible terminal to the user’s station translated preferences and permissions. PSA makes it convenient for users to use a pool of phones at different times and locations.

SA8587 PSA over QSIG Networking
This feature enables served users on a server to divert their calls to another server in their private network and receive calls as if they were on their “home” server.

SA8589 – Background BSR Polling
The MultiVantage Background BSR Polling (BBP) Green feature is intended to provide a solution for Avaya call center customers who wish to use Best Service Routing (Avaya. Virtual Routing) to poll a large number of MultiVantage sites via a “star” polling strategy, and then interflow the call to one of these locations with a less than 1-second delay. The BBP feature accomplishes this by constantly updating current “BSR best” location information via a continually executing “background” MultiVantage call-processing task that loops through a sequence of “consider” vector steps. The BBP task stores the results of the its BSR polling in a “global” BSR status information table accessible to a new incoming call doing BSR call-routing to allow immediate interflow of the call.

SA8601 – Two-Digit AUX reason code

The Special Application SA8601 “Two-Digit Aux Reason Code” Green feature is provided in a post-CM 2.0 GA release to allow Avaya call center agents to enter the auxiliary “Aux Work” work-mode state with an associated “Aux Reason Code” from 10-99.  This can be done by –

  • Pressing an “Aux-Work” work-mode station button administered with a 0-99 Aux Reason Code;
  • ·Pressing an “Aux-Work” work-mode station button not administered with an Aux Reason Code and subsequently entering a 1-99 Aux Reason Code via the station’s digit keypad; or

SA8608 – Increased Crisis Alert Stations

Currently, CM is limited to 10 Crisis Alert stations on the S8700 platform. This enhancement will expand the capabilities of the S8700 platform to allow for up to 250 Crisis Alert stations

SA8622 – Enhanced Call Pickup Alerting
Currently when a call comes into a user that is in a call pickup group, the other group members are notified via the lamp on the call pickup button. One requested enhancement is to also update the group member’s display during ringing to allow the user to decide whether to pick up the call based on the calling party. Another request is to be able to administer different alerting options for the group members including, silent (today), single alert, single if active, and continuous alerting.

SA8623 – Chained Call Forwarding
This feature is to allow call forwarding to be chained to follow each stations call fwd status. Currently if StationA is forwarded to StationB and StationB is forwarded to StationC, calls to StationA continue to ring at StationB until answered, covered or dropped. The described feature enhancement is to allow this type of call to terminate at StationC.

SA8654 – Crisis Alert Call Monitoring and Recording

This document specifies the internal software design for the SA8654 Crisis Alert Call Monitoring and Recording feature, a CM2.1 green feature. This feature enhances the existing standard Crisis Alert feature to provide the CM software with the capability of monitoring and/or recording emergency calls from the station terminals with the “crss-alert” button administered.  This capability is realized via implicit integration with the barge-in capability from the Service Observing feature for call monitoring and explicit integration with the Audix One-Step Recording feature for call recording.

SA8661 – Increased Automatic Wakeup Calls

This feature increases wakeup limits to allow 200 wakeup calls per minute. Currently, S8700 & S8500 limit the number of wakeup calls to 950 per 15-minute interval.  This results in a maximum limit of about 63 calls per minute.  This feature increases this limit to 3000 per 15-minute interval to allow 200 calls per minute.

SA8662 – Expanded PMS Name and Number

This feature expands the PMS extension length from 5 to 7 digits, and expands the PMS name to 27-characters from 15.

Requires minimum Release R012. or later.

SA8684– PMS Wakeup Message

This feature introduces a new PMS message called “Automatic Wakeup”.  This new message allows the PMS to schedule and cancel wakeup calls.  In addition, the PMS can query for the current scheduled wakeup call for a particular guest.  Requires minimum Release R012. or later

SA8693 – Connectivity for Direct IP Shuffling

The request is to provide a feature enhancement ensuring that the inter network region IP calls do not shuffle in case the two endpoints can not talk to each other directly via IP. Suggestion is that CM instructs the IP endpoints involved in an inter network region call to ping each other to verify connectivity before the call is shuffled. Ideally this check should take place as early in the call setup as possible to minimize the impact of the time this test takes. If there is no positive

confirmation of this ping being successful within a given time, the call shall stay unshuffled and would be served through the TDM links of the Center Stage Switch.

SA8694 – Enhanced redirection notification

Currently, CM doesn’t have the capability to display to the station user, when redirection features such as Do Not Disturb, Send All Calls and Call Forwarding are active.  This enhancement will enable the CM to display on the station the feature activation through messages like “Send All Calls Activated”.  Display will be updated on phones having capability, a special tone will be provided to indicate one of the features is active.

SA8702 – Enhanced Network CDR

This feature provides the user with the capability to customize the CDR (Call Detail Record) using five new keywords. These five new keywords allow the user to add UCID, internal and trunk codecs, a 32-bit sequence number and a combined charge field.   Also, the SA8702 Green feature adds the “Copy UCID for Station Conference/Transfer” field to the “system–parameters features-related” form.  When this field is set to “y”, the UCID associated with a call is preserved for the second call-legs associated with station call-conference/drop and station call-transfer operations on a system wide basis.

SA8744 – Block name for room to room calls

For room-to-room calls, the guest’s name will be replaced with the administered room information from the site data section of the station form.  A call is considered to be room-to-room call when both the caller and called party are administered as a “client room” COS.  If nothing is administered on the station form the display will show the extension number.

SA8749 – Increase to 2000 vectors

The SA8749 Green feature includes changes to CM call processing, CM system administration fields, the CM-to CMS message protocol, and various CMS standard/custom report fields to provide an increase from 999 to 2000 vectors for the S8500, S8700, S8710 and S8720 Linux switch platforms.   The SA8749 Green feature has no impact on ASAI  (Adjunct Switch Application Interface)/CTI (Computer Telephony Interfaces) operations.  NOTE:  Avaya customers who activate the SA8749 Green feature must upgrade to the standard CMS R13 GA release to obtain CMS tracking for vectors 1000-2000 if any of these vectors are associated with a VDN administered as “measured/external” or “measured/both”.  Contact Renee Armstrong in the Denver ATAC at +1-720-444-7807 or rarmstrong@avaya.com if assistance is needed to order the standard CMS R13 release.

SA8758 – Automatic Exclusion

Modify automatic exclusion to block the principal from bridging onto an active call.  Currently, auto exclusion will block any station that has a bridged appearance from joining an existing call but the principal can always join.

SA8759 –  Invoke NCR Transfer on Answer Only

For the MCI Network Call Transfer, Two B-Channel Transfer, and ETSI Explicit Call Transfer protocols supported by the Avaya Network Call Redirection (NCR) feature, the switch invokes NCR for a call-transfer or call-conference/drop when an ALERTing or CONNECT ISDN message is received from the far-end switch over the second call-leg.  This Green feature allows the Avaya customer to specify that NCR will be invoked only when a CONNECT ISDN message is received over the second call-leg. This means that when the second call-leg call is in the ALERTing ISDN call-state, the transferring party still has control of the call and can drop the second call-leg to route the call to a different PSTN endpoint before NCR is invoked.  Note that this Green feature has no effect on the invocation of NCR by call vectoring using the “route-to number ~r” or “queue-to best” vector steps.

, ,


  • liquidvw says:

    Good list. Thanks for posting.

    • dwalin says:

      Vladimir, thanks for the link. You see, with that new Avaya website layout you never know where to find something you need. :)

  • Manish Mishra says:


    I need your help. We owns 2 numbers i.e. 0207 663 0000 and 0207 665 0000. Currently both the numbers going to Queue 7000.

    We need to direct one of these numbers 0207 665 0000 to be diverted to Hunt Group 5056. As our Avaya system recognizes the DDIs with its last 4 digits, If I am doing command ”change aar digit-conversion 0000“ in ASA, there only one entry to amend and its pointing to Queue 7000.

    Kindly advise how I can recognize these 2 numbers distinctly and do the changes.

    Thanks in advance.

    Best Regards,
    Manish Mishra

  • Mike Cassidy says:

    Need to track Ring No answer for collection, on CM 6.3.2 with ISI Call Accounting application. Avaya no help, their suggested only works in their lab, not on our switch

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>