Page 1 of 11 TECHNICAL BULLETIN COMMERCIAL - IN - CONFIDENCE Controlled Release - Level 7.2 & 7.1.1 Software Level 7.2 Available on Controlled Release from 8 th June 1998, Level 7.2 provides the software platform to support two new trunk interface cassettes for the international markets. Also incorporated are a number of functionality enhancements which are summarised as follows Support of the 2 M/bit R2 Cassette (Not available in the UK) Support of the Alog R Cassette (Not available in the UK) VPN Over ISDN (Not available in the UK) DPNSS Enhancements ISDN Enhancements Security Enhancements Alarm Calls on POT s Compatibility Level 7.2 software will only run on the CPU V, and is compatible with the Global Voice Manager 5.9, the Seltek Voice Manager 4.6, ACD 4.2/5.1/5.2 (for CPU s 200/400/800) and ACD 5.2 for use with the CPU100. Level 7.2 software will not support the Flat Bed (ACU) Operator Console. Note: During the trial of Level 7.2 an issue was identified with the Primary Rate Euro ISDN cassette. When a route list contains multiple Euro ISDN routes, if the Primary route was to fail the INDeX would not automatically switch to the secondary route. This was not common to 7.2 software and was apparent in previous versions of INDeX software. This issue is resolved with the combination of 7.2 and E-PRI software version 1.4. The E-PRI software 1.4 can be found on the SDX Web Page or on the CPU-V Level 7.2 disk (38YMD00001SGA) in directory A:\ PRI. The Cassette Software Upload procedure can be found in the SDX INDeX Installation & Maintenance (Level 7.0) Manual page number 48. Future shipments of E-PRI cassettes will include the new issue of software, this will move the Cassette PCS level up to 4. The PCS 4 E-PRI cassette is backward compatible with previous versions of INDeX software but will not fix the problem without the CPU running 7.2 software.
Page 2 of 11 Level 7.2 Software Upgrades INDeX Level 7.2 software, Product Description and Technical Manual Addendum will be made available FOC via the SDX Web page. A Level 7.2 upgrade pack may be ordered using the code INDEX-72 RSP 500 (normal MLD applies). CPUs will continue to be despatched at 7.1 software. The upgrade packs will contain software at controlled release version level 7.2. Also included in the pack are the Level 7.2 Technical Manual Addendum and Product Description. The electronic serial number of a CPU does not change when it is upgraded to Level 7.2. Therefore the licence keys previously supplied with CPUs remain valid after upgrading to Level 7.2. The licence key LIC-ACD has been removed in 7.2. The agent licence will be replaced with a new mechanism in Level 8.0. In Level 7.2 the Voice Licence key LIC-VVI controls the availability of events essential for the integration of Voicemail. This licence will continue to be shipped FOC with every system. However, this may be reviewed when INDeX Level 7.2 moves to General release. Level 7.2 Training Unlike other releases of INDeX software, it is not mandatory that engineers receive technical update training for Level 7.2. The documented changes in the Level 7.2 Addendum & Product Description will provide the information an engineer will require to understand the changes from 7.1 to level 7.2. However, the INDeX workshop (T81) now includes Level 7.2 and 7.1 functionality. If any Reseller would like to attend this workshop, please contact Carol Bell on 01707 364154. Level 7.2 Controlled Release Registration To ensure that the controlled release process is a success and that the appropriate level of support is available, it is important that we have complete visibility of all systems with Level 7.2. Therefore, please notify SDX Business Systems when upgrading an existing system to Level 7.2 by completing section 3 (Controlled Release Items) of the Registration & Order Form which is attached to Reseller Update 154. 2M/bit R2 MFC Cassette INDeX level 7.2 is the first version of switch software to support the R2 MFC cassette. R2 MFC is a form of Channel Associated Signalling. This cassette provides connection for up to 30 R2 channels. The connection to the network
Page 3 of 11 is made via an RJ45 connection, a cable is supplied with the cassette.the code for this cassette is E1R2-30. Please note: This cassette has been developed for the Czech Republic, and may require modification before the cassette will operate elsewhere. Alog R Cassette The Alog R will be delivered in two variants, the 8/0 and the 8/4. The first digit represents the number of Loop start trunk circuits that can be used for both incoming and outgoing calls. The loop start circuits also have the ability to detect line reversal. The second digit represents the number of DID channels that the board is equipped with. The DID signalling is in the form of R2 MFC, these four channels are incoming only. The code for these cassettes are ALR-8-0-Z1 and ALR-8-4D-Z1. Please note: This cassette has been developed for the Singapore market, and may require modification before the cassette will operate elsewhere. VPN Over ISDN Level 7.2 introduces three new ETSI compliant ISDN supplementary services, one of which is User to User Signalling. Although currently not available in the UK, User User signalling is now becoming more widespread within other European PTT s. User to User signalling allows the user to send and receive a limited amount of user generated information to and from another user interface. The INDeX implementation of User to User signalling provides DPNSS type functionality over either ETSI compliant Basic Rate or Primary Rate connections. The method of signalling is proprietary and therefore will only work between INDeX switches capable of supporting this feature. DPNSS Enhancements Level 7.2 will deliver improvements to the way DPNSS network calls are presented to the user. In order to hide the DPNSS connection, the following changes have been made: On previous versions of INDeX software, a network call would be presented in a similar way to an external call. In Level 7.2 the network call is presented as though it was an internal call. The calling extension will see the called extension name and number, when using a display handset. The called
Page 4 of 11 party will also see the calling party s name and number, as well as being presented with internal ring cadence. If a call originates from the PSTN and delivered over DPNSS, then the called party will receive the call with external ring cadence, similarly the WOC/NOC will be presented with the call on the external queue. A call that is diverted over the DPNSS network will be presented with the calling parties name and extension number in association with directory number of the diverting extension. If the call is transferred over the network and recalls back to the originator, the recall details are displayed. If the target extension has programmed an absent text message against the extension, then the person calling the extension over DPNSS will be presented with the Absent Text message. (See planning rules). Level 7.2 is the first version of INDeX software to allow display DT s and Windows Based Operator Consoles to dial ahead over the network, giving the caller the status of the remote target extension (free, busy etc..). If a network of INDeX switches were each programmed with a common group number, a user is able to page that group number and the broadcast will be simultaneously presented at every INDeX configured with that group number. For Example, if two INDeX telephone systems are linked with DPNSS, and both have a Group 10. When the page to group 10 is made from switch A, the page is also simultaneously delivered through the handsets to Group 10 members at switch B. A user on switch A can also retrieve an external call that is parked at switch B by simply dialling the line number. An incoming DPNSS call to an extension will be presented with internal ring cadence, the same call to a WOC/NOC will be presented on the internal queue. It is possible for a user to remotely forward their extension when located at a remote site connected via DPNSS. The destination that the extension is forwarded to can either be on switch or over the network. Planning Rules The following rules apply, if the network wishes to use the functionality made available in Level 7.2. The network should use unique extension and line numbering across the networked switches. The node numbers should be the same amount of digits. It is recommended that the network uses a linked 4 digit numbering scheme.
Page 5 of 11 Group 10 Group 10 Node 800 Extn 2000 to 2400 DPNSS Network Node 801 Extn 3000 to 3199 Group 10 Node 802 Extn 4000 to 4349 The paging group numbers should be the same across switches to allow for wide area paging. (Rotary Groups will not generate a wide area page.) In order for absent text messages to work correctly across the network, the absent text messages should be configured to ensure that the default text is common across the network. For example: If the default text for message number one is On holiday until, then the same message should be associated with message number one on all switches wishing to apply absent text across the network. ISDN Enhancements Two further ETSI ISDN features introduced with 7.2 are Advice of Charge and Calling Line Identity Presentation. AOC(E) With Advice of Charge enabled on the users ISDN connection, the PTT will send the call cost information to the INDeX following the call being terminated. The call cost information will vary depending on what PTT you are connected to. The charge information will either contain the cost of the call in local currency or the units used on the call. In the UK, BT are currently planning to start rolling out AOC(E) during the third quarter of 1998. On receipt of the Advice of Charge information, the INDeX will print out the call charge in the second line of the SMDR call record. The statistics for the device will be updated to include the new call cost information. The charge information will be automatically passed through to future ACD developments, allowing the ACD to automatically update the outgoing call reports with the precise call charge.
Page 6 of 11 Calling / Connected Line Presentation CLIP/ COLP The CLIP supplementary service provides the called party with the possibility of receiving the identification of the calling party s calling line identity. The COLP supplementary service provides the calling party with the possibility of receiving the identification of the connected party s connected line identity. These features are available on both Basic Rate and Primary rate ETSI compliant ISDN connections. It is possible to define the CLIP and COLP number from the terminal menu of the INDeX, giving the user the ability to define the number sent to the network. The number is usually expected to be the individuals DDI number or the Switchboard number. The terminal menu/ personal status contains 3 fields 1. CLI on Outgoing - Yes or No (determines whether the CLI is sent on an outbound call) 2. CLI on Incoming Yes or No (determines whether the CLI is sent to the calling party on receipt of an incoming call) 3. Personal CLI (Allowing up to 20 digits to be entered as the number sent for either of the two options above) Note: If option 1or 2 are set to yes and the Personal CLI is left empty, the installation number will be sent to line. The implementation of this feature will enable users to send their true CLI, allowing features such as using the 1471 style callback method much more workable. Other applications that will benefit include CTI applications and ACD type lost call reports. The calling party number sent by the calling user will be verified by the network to check that the number is within the set of numbers allocated to the access. In case of unsuccessful verification or if no calling party number is received, the network will insert the default number with the screening indicator set to network provided. In case of successful verification the screening indicator will be set to user provided, verified and passed. Note: If an INDeX has multiple ISDN connections each with different DDI ranges, it is important to remember that the CLIP/COLP number will be checked by the PTT, ensuring that the CLIP number is within the DDI range for that ISDN connection. In order to prevent this from happening the switch should be configured to ensure that the users requiring to send their CLIP
Page 7 of 11 number are dialling out on the appropriate ISDN connection. (See Diagram Overleaf). INDeX 7.2 Switch ISDN Pipe A PTT No. 01707 3644150-199 Personal CLI used. Personal CLI: 01707 364155 PSTN ISDN Pipe B PTT No. 01707 364600-799 Personal CLI not used. PTT CLI used or call rejected. Security Enhancements Unauthorised Access to an INDeX can lead to telecom fraud or damage to a customers database, where the overall outcome is additional expense. The INDeX has eight fully secure passwords, however these are often left at the defaults which are widely known within the industry. Level 7.2 includes improvements in the password protection of the INDeX, making unauthorised access increasingly difficult. Level 7.2 will include the following security enhancements: If a system is started up with a new CPU or following a database reset, the user is asked to enter the password that they wish to use for the engineers level of access. Once in to the programming of the INDeX, the remaining seven system passwords are disabled. These passwords can then be enabled and there access levels defined. The INDeX will lock the unauthorised user out for one hour following three unsuccessful attempts to log in. If the INDeX has the mains cycled the user will have the ability to re-enter for a further 3 entries. The lock out condition does not affect other signalling (eg. CTI, SMDR, etc) using the serial ports. Alarm Calls On POT s The personal alarm call facility previously available on a DT3, 4 or 5 has been made available to a POT user. The alarm call is invoked as follows. To set an alarm call: *8 time in 24hr format with # to complete the entry. To clear an alarm call *8 and * to clear with # to complete the entry. To overwrite an alarm setting *8 followed by the time in 24hr format with # to complete the entry.
Page 8 of 11 The alarm is immediately cancelled following the alarm being activated. This prevents the same alarm being continually activated at the same time every day. When the alarm is activated the phone will ring for 20 seconds. The alarm can be cleared by the user going off and on hook. For Example: A Hotel Guest may wish to receive a wake up call at 7 o clock the following morning. The guest would lift the handset of the room telephone and key in *80700#. If the user requires a wake up call at the same time for the following day, the guest would have to re-enter the code from the handset. Note: The alarms available on the POT are only personal alarms. System Alarms will not work with a POT. Other Feature Enhancements INDeX Search Enhancements The INDeX search only includes the internal directory names and does not include system speed dials. The System Speed dial names are now accessed via the Speed Dial key. on pressing the Speed Dial key, the user is prompted with three options, these are: OWN Personal Speed dials dialled by numbers 00-09 SYSTEM System speed dials dialled by system number 100-999. INDeX System Speed dial numbers dialled by the Speed dial name. When the end of an INDeX search is reached, the user can scroll back rather than having to press AGAIN (as on previous releases of INDeX software). Back Busy on DDI Enhancements The feature introduced in 7.1 that limits the maximum number of calls to a particular DDI has enhanced to operate in two modes: 1. The original mode Calls accepted where the incoming caller will be returned busy when the number of calls connected and waiting exceeds the threshold set on the pilot number. 2. Or the new mode Calls waiting where the incoming caller will be returned busy when the number of calls waiting (ie. Calls queued) exceeds the threshold set on the pilot number.
Page 9 of 11 As with 7.1, if the threshold is set to zero the back busy feature is deactivated. This feature is only available on DDI calls directed at a pilot number. Absent Messaging Enhancements Absent messages are now displayed on the terminal when set. The terminal does not have to be in No Calls without a Divert all number set. Internal callers to the extension see the Absence message on their phone's display (unless a Divert All/Busy number is in use in which case the call diverts immediately as normal). On previous releases of INDeX software a user who had a DDI number could not use the absent text message, as using No Calls to invoke the feature would result in an external caller being returned number unobtainable. The implementation in Level 7.2 allows the user to continue using Absent Text along with being presented with DDI calls Alpha Tagging Priorities On versions previous to Level 7.2, the highest display priority was given to the Group name on incoming calls. New products now utilise the Group name for several features which means that most groups will be named overriding the display of DDI, pilot and CLI/speed dial names when set. For Level 7.2 the priority on displayed name for external calls is in the following order: Name Priority DDI Name 1 Pilot Name 2 Trunk Name 3 CLI or Speed Dial 4 Name Group Name Toggle to View Note: If the Group Name is programmed the text can be viewed by pressing the top right context sensitive key. DDI Names The DDI Names table as it is has a maximum of 8 DDI digits, with the introduction of the ETSI compliant ISDN services, the amount of DDI digits have been increased beyond 8 digits. In order to adapt to the larger digit
Page 10 of 11 length received on a DDI call, the last 8 digits are used to determine what DDI name is tagged to the call from the DDI Names table. For Example: A call on DDI number 01707 364444 will be presented with the DDI digits 1707364444. The last 8 digits will be used to apply a DDI name to the incoming call. The DDI names table will have an entry for 07364444 = alpha tag. Note: For DDI call routing, ARS string analysis still needs to be applied to all the digits received and not just the last eight digits used for DDI naming. Database Back Up Database back up is now performed on a daily basis rather than an hourly basis. The default back up time is midnight, this is soft programmable. Class of Service CTI Command A new CTI command is supported which allows the modification of the day or night service class of service of an extension. Language Support The INDeX now supports 3 new languages Slovenian, Czech and Spanish. Database Verification A new menu called Database Verification has been introduced within the Database Management screen. Database Verification can be used to spot inconsistencies such as trunks in a terminal group, etc. It is intended that the Database Verification utility should only be used by the SDX engineering team Flat Bed Operator Console (ACU) Please note that Level 7.2 will not support the Old Flat Bed Operator (ACU) Console. Level 7.1.1 INDeX Level 7.1 currently has a number of patches addressing several field issues. INDeX Level 7.1.1 will include these patches and will only be available for the original CPU. There will not be a Level 7.1.1 for the CPU V, as 7.2 includes these patches along with additional functionality. Level 7.1.1 and 7.2 will both be available from the Web page from the 8 th May 1998. For more detail on what patches are available for Level 7.1, please refer to Technical Tip number 79.
Page 11 of 11 Note: Level 7.1.1 is purely a maintenance release and does not include any additional functionality over 7.1. Issued by Dave Garwood (ext 4306)