ISDN RELEASE 8.0 VERSION 1.10

FIELD CHANGE INSTRUCTION

This Field Change Instruction (FCI) is intended to assist Customer Service and Installation Personnel involved in the installation and support of the Mitel® ISDN PRI Card.

 

 

 

 

 

 

 

 

NOTICE

The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks Corporation (Mitel). The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate changes.

®, ™- Trademark of Mitel Networks Corporation.

© Copyright 2001, Mitel Networks Corporation. All rights reserved.

56003129, Issue 1, August 2001

Printed In Canada.

 

1. OVERVIEW *

1.1 CHANGES IN ISDN RELEASE 8.0 Version 1.10 *

1.1.1 Converged IMAT Release 7.1 Version 0.2 *

1.1.2 Enhanced QSIG Support *

1.1.2.1 Call Diversion *

1.1.2.2 Q.SIG – Call Forwarding *

1.1.2.3 Call Transfer *

1.1.2.4 Call Offer *

1.1.2.4.1 With Path Retention *

1.1.2.4.2 Without path Retention *

1.1.2.5 Message Waiting *

1.1.2.6 Path Replacement *

1.1.2.7 Connected Name/Number & Busy Name/Number *

2. APPLICATION REQUIREMENTS *

3. HARDWARE REQUIREMENTS *

3.1 RECOMMENDED HARDWARE/CIRCUIT CARD FIELD LEVEL’S *

4. DOCUMENTATION REQUIREMENTS *

5. INSTALLATION AND UPGRADE NOTES *

5.1 NEW INSTALLATION Release 8.0 Version 1.10 or later *

6. CUSTOMER REPORTED PROBLEMS NOT FIXED IN THE SOFTWARE RELEASE. *

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  1. OVERVIEW

    2. This FCI details enhancements introduced in ISDN Release 8.0, software Version 1.10. Hardware and documentation requirements for this software release are also discussed.

    1. CHANGES IN ISDN RELEASE 8.0 Version 1.10

      2. The following enhancements have been added to ISDN Release 8.0.1.10:

      1. Converged IMAT Release 7.1 Version 0.2

        2. IMAT is now converged across all ISDN products (ISDN/PRI, R2 System, SX200, BRI, Ipera/2KNT). As well, all older releases of ISDN are supported by selecting the appropriate System Type. When selecting PRI (SX200/SX2000), the database version used will be version DB8.0.0.0. When selecting R2, the database version used will be version DB7.0.0.0.

      2. Enhanced QSIG Support
        1. Call Diversion

          2. Call Diversion is a method of diverting a call based on features enabled on the set (Forwarding/Rerouting). When a call is diverted, the forwarding/reroute information is passed directory back to the originating PBX. This allows for better use of DPNSS and QSIG trunking.

          PRI will convert QSIG diversion messaging from the QSIG network to DPNSS messages and pass them to the SX2000. Similarly, DPNSS diversion messaging from the SX2000 will be converted to QSIG diversion and passed to the QSIG network.

        2. Q.SIG – Call Forwarding

Provide Call Forwarding feature support in Q.SIG for Centralized Voicemail and Centralized Attendants:

  1. Activation and Deactivation can be performed by the served user. Activation and Deactivation correspond to SX2000 Remote Third Party Forwarding features.
  2. Interrogation requests the call forwarding status of a remote set. DPNSS has no equivalent to this feature.
  1. automatically when incoming call arrives;
  2. after call remains unanswered for a predefined time;
  3. or as a result of destination set action when alerted of incoming call.
  4. Maps to functionality provided in DPNSS.
        1. Call Transfer

          2. Allows user to transfer a call to another destination over Q.SIG trunks. This feature is already provided by other trunking systems (ie. DPNSS). Supports QSIG Call Transfer by Join, but no Call Transfer by Rerouting.

        2. Call Offer
          1. With Path Retention

            2. Call Offer is the same as Campon. It is supported on Originating, Transit, and Terminating SX2000 nodes. Provides an information element in the initial SETUP message to notify the Terminating PINX of a list of possible services that may be requested during the call:

            For example, if Busy is encountered at the terminating party, this fact is signaled back to the Originating PINX without clearing the call. The busy indication can then be presented to the caller who can decide whether to apply Campon, etc… If the user requests Campon, this fact is signaled to the Terminating PINX as part of the initial call. There is no DPNSS equivalent to this functionality.

             

             

             

          2. Without path Retention

          Call Offer is the same as Campon. It is supported on Transit and Terminating SX2000 nodes. It works similar to DPNSS Call Offer:

          For example, if an ISRM is sent to the terminating PBX and a CRM with clearing cause 8 (busy) is returned, the original call is cleared and busy tone and display are presented to the caller. The user can choose to campon (I Will Wait). A second ISRM is then sent with the SIS-CO string included to indicate that campon is required.

        3. Message Waiting

          4. QSIG Message Waiting activation and deactivation map directly to DPNSS callback messaging, with the exception of QSIG interrogation functionality. QSIG message waiting service delivers more parameters than DPNSS, therefore these extra parameters will be lost.

        4. Path Replacement

          5. The PRI will convert QSIG path replacement messaging received from the QSIG network to DPNSS messages and pass them to the SX2000. Similarly DPNSS route optimization messages from the SX2000 are converted to QSIG path replacement messages and passed to the QSIG network.

          Path Replacement is the same as Route Optimization. It is supported when it is requested from an Originating PBX, with the optimizing call made from the Terminating PBX, towards the Originating PBX.

          It is not supported when requested from Transit nodes, Terminating nodes, or if the optimizing call is made from the Originator towards the Terminator, except when the SX2000 is acting as a transit node only.

        5. Connected Name/Number & Busy Name/Number

Connected Name/Number and Busy Name/Number have been added to QSIG Rel2.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  1. APPLICATION REQUIREMENTS

    2. Minimum levels of Application software to function correctly with the ISDN Release 8.0 Version 1.10 are tabled below.

    APPLICATIONS

    SOFTWARE LEVEL REQUIREMENTS

    COMMENTS

    SX-2000

    LW31 R1

    LW31 R1 required for Qsig Rel2.

    SX-2000

    LW29 R3

    LW30 R1

    LW30 R1 required for basic Qsig.

    IMAT

    7.1.0.2

    		  

    Microsoft Windows Dial-up Networking (msdun12.exe or medun13.exe) on IMAT PC

    1.2 or 1.3

    WIN95,98 Only

    The following SX-2000 PBX system features must be present for the full functionality of the ISDN PRI card to work correctly:

    SYSTEM FEATURE

    DEFINITION

    ANI/DNIS/ISDN Number Delivery

    Allows ANI/DNIS digits to be displayed on PBX peripheral devices.

    MSDN/DPNSS Data (optional - for data calls only)

    Allows PBX dataset calls and Network-side Interface PRI device calls.

    MSDN/DPNSS Public Network Access

    Allows stations or trunks to make outgoing calls over the public-switched network via MSDN/DPNSS.

    MSDN/DPNSS Voice I

    Allows MSDN call setup capabilities between the PBX and the ISDN Network Gateway.

    MSDN/DPNSS Voice III (optional)

    Allows incoming calling name to be displayed at a display set. Allows outgoing calling name to be presented to ISDN network.

    MSDN/DPNSS Voice V

    Allows the PBX to select another route since step-back on busy is enabled.

    PRI CARD - NFAS (optional)

    Allows one ISDN D channel to control multiple ISDN links.

    PRI Card - D Channel Backup (optional)

    All a second ISDN D channel to be designated as a backup in case the first D channel fails in an NFAS setup.

    PRI Card - Remote LAN access (optional)

    All for a PRI circuit to be connected to a network device such as a router.

    PRI Card - Min/Max (optional)

    Allows automatic limiting of the number of inbound and outbound calls.

    PRI Card - Auto Min/Max (optional)

    Allows for time of day switching of different Min/Max scenarios.

    PRI Card - Qsig (optional)

    Allows Qsig and Qsig Rel2 protocols to be selected

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

  2. HARDWARE REQUIREMENTS

    3. This section details Mitel’s requirements for the PRI Card to function. Also included in this section are details related to any new hardware or major changes to existing hardware. Finally the recommended hardware/circuit card field levels are laid out.

    1. RECOMMENDED HARDWARE/CIRCUIT CARD FIELD LEVEL’S

    This section identifies Mitel’s recommended field levels for the ISDN PRI and related hardware. To ensure the best level of service; Mitel encourages customers to meet these hardware levels. Recommended field levels on hardware may change without notice.

    SX-2000

    PART NUMBER

    CARD TYPE

    RECOMMENDED REVISION

    		  

    MC270AA

    T1 PRI Card

    1.5

    		  

    MC269AA

    E1 PRI Card

    1.5

    		  

    MA225AA

    PRI Stub Card

    2.3

    		  

    50000730

    CEPT Interface Card

    A.2

    		  

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

  3. DOCUMENTATION REQUIREMENTS
    4.

    Part Number

    Title

    Notes

    9125-030-001-NA Issue 1

    SX-2000 Technical Documentation on CD-ROM

    		  

    9125-030-100-NA Issue 1

    SX-2000 Technicians Handbook

    		  
     

    IMAT On Line Help

    In the IMAT program

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

  4. INSTALLATION AND UPGRADE NOTES
    1. NEW INSTALLATION Release 8.0 Version 1.10 or later

Refer to the appropriate section of the CD-ROM Documentation for detailed information.

IMPORTANT When Upgrading

Follow this order

The ISDN PRI card is now programmed as a Universal T1 card on the SX2000 as of LW31 Rel1.

Due to the large increase in file size for the PRI software, the traditional upgrade procedure has changed.

When upgrading from a release earlier than 8, it is strongly suggested that you follow these steps.

IMPORTANT When Upgrading

Follow this order

Requirements PC/Laptop with a CD drive and Imat rls 7.1.0.2 installed and tested and WinZip 7.0 or greater installed and working.

  1. Connect to the card using IMAT
  2. Load database from the PRI card and save it to the Imat PC’s C: drive. (Give it a valid name)
  3. Disconnect from remote site.
  4. Exit Imat.
  5. Create a folder on the "C" drive of the Imat PC with a valid name eg: "priupg"
  6. Put the ISDN rls 8.0.1.10 in the CD drive and using "Explore" open the Pri_install folder

  7. Double click on the Pricard.zip. (a WinZip pop-up window will appear)

    8.

     

  8. Choose the option to extract (a WinZip pop-up window will appear)

    9.
  9. Navigate in the "Extract to" box to the newly created "priupg" folder on the "C" drive and choose click the Extract button.
  10. This should have installed all 10 files in to the "priupg" directory
  11. Using "Explore" now navigate to the Pri_Database folder and open it.

  12. Using "Edit, Select all, Copy" then navigate to the "priupg" "Edit, Paste" copy all the files in to the "priupg" folder
  13. The following files should now be in the "priupg"

    14.
  14. On the sx2000 log in to maintenance at system level and enter "sub reset off magic wxyyx". The system will return with > Subsystem reset info: Subsystem resetting has been disabled.

    15. (Error traps will go to LLD)

  15. Connect to the Pri card with a VT100 terminal emulator such as Procomm (38400 8N1)
  16. Reboot (reseat) the card
  17. At the first output to the screen hit <any> key to stop the boot process, (3 second timer).
  18. Type R (upper case) to put the card in to listen mode ( R will reformat the flash drive on the PRI Card)

    19. The following is output:

    Press *any* key to stop this auto-boot...

    3 (counts down)

    [MC269AA Boot]-: R

    Attached TCP/IP interface to qu0.

    Attaching network interface lo0... done.

    Formatting flash.

    creating flash device

    calling dosFsInit

    mounting flash - Flash mounted on c:/

    cd'd to c:/

    starting ftp daemon

    listening for ppp

     

  19. Close Terminal Emulator
  20. Open a DOS window and change to the directory created eg: "priupg" with the 22 files in it by using the following commands:

    21. Cd\

    Cd priupg

    The PC should now have a Eg: C:\PRIUPG>

  21. Type <FTP 10.0.0.1>

    22. <enter> for user

    <enter> for password

    Type bin enter

    Type prompt enter

    Type mput *.* (star dot star) enter

    Should report as files are transferred (takes approximately 45 min.)

    PC will show files being transferred and report when complete

    Type quit enter

    Type exit enter

  22. Reseat the card
  23. The Pri card will come back up with a default database
  24. Reconnect to the PRI card with Imat
  25. Load the database saved in step 2
  26. Be sure to convert to rls 8 database
  27. Save the database to the card
  28. After database is saved go to Maintenance, remote reset and restart the PRI card
  29. The card will now come back up with rls 8 running the customers database
  30. Complete a check of placing and receiving calls

    31. Important !!!

  31. Last you must turn back on the subsystem by entering "Sub reset on magic wxyyx" from maintenance
  32. Upgrade complete

 

 

 

 

 

 

 

 

 

 

 

 

  1. CUSTOMER REPORTED PROBLEMS NOT FIXED IN THE SOFTWARE RELEASE.

For any outstanding customer reported problems refer to the "Known Bug List" on Mitel On Line at http://www.mitel.com.