EXS ExchangePlus Software Operations Guide
ExchangePlus Software Release 3.1 Document Number: 08-0075-02
Important Notice General Disclaimer This document provides general information regarding Lucent Technologies products. It does not represent any commitment by Lucent to develop or deliver any specific product or capability, or to support any stated or implied product application requirements. The contents of this document are subject to change without notice; therefore, the information presented herein shall not be construed as a commitment or warranty. Lucent Technologies shall not be liable for any technical or editorial errors or omissions contained herein or for incidental or consequential damages resulting from the performance, furnishing, reliance on, or use of this material.
Patents and Trademarks Certain equipment and software described in this document is protected by issued and pending U.S. and foreign patents. Microsoft Windows, Microsoft NT, Microsoft Windows 98, and Microsoft Windows 95 are trademarks of Microsoft Corporation. Sun, Sun Microsystems, Solaris, Netra, and AXi are trademarks of Sun Microsystems. Exceed is a registered trademark of Hummingbird Communications Ltd. All products and services are trademarks or registered trademarks of their respective manufacturer.
Copyright This document contains confidential and proprietary information protected by copyright. All rights reserved. Copying or other reproduction of all or parts of this document is prohibited without the permission of Lucent Technologies.
Year 2000 Compliance All EXS products have been tested for Year 2000 Compliance. Lucent has received certification from Information Technology Association of America (ITAA) that Lucent meets the information technology industry’s best software development practices for addressing the Year 2000 issue.
Technical Support Lucent Technologies is dedicated to providing prompt and effective support. Within United States: 1-800-541-7002 International: 1-508-862-3366 Fax: 1-508-862-3351 Email: xltechsupport@lucent.com
Copyright © 2000 by Lucent Technologies
Lucent Technologies 255 Independence Drive • Hyannis, MA • 02601 Phone: 508-862-3000 • Fax: 508-862-3030 • Website: www.xl.com
EXS ExchangePlus Software Operations Guide
Table of Contents Before You Begin Audience........................................................................................................................................... x Other Documentation ....................................................................................................................... x Technical Support ............................................................................................................................ x Required Items ................................................................................................................................ xi
Chapter 1 Introduction Overview ....................................................................................................................................... 1-1 System Concepts ........................................................................................................................... 1-3 ExchangePlus Call Flow ............................................................................................................... 1-3 How Information is Loaded and Saved on ExchangePlus ............................................................ 1-9 ExchangePlus User Interfaces ..................................................................................................... 1-10 Windows-based User Interface ................................................................................................... 1-10 Curses Interface........................................................................................................................... 1-13
Chapter 2 Setting Up Access to ExchangePlus Overview ....................................................................................................................................... 2-1 Accessing the Host from a Windows Platform ............................................................................. 2-2 Obtaining Host Name and IP Address 2-3 Installing Exceed on a Windows Platform 2-4 Adding the ExchangePlus Host to Exceed 2-5 Accessing the Host using Exceed 2-7
Accessing the Host from a Non-Windows Platform ................................................................... 2-10 Accessing the Host using Telnet 2-11 Accessing the Host from a UNIX-based System 2-13 Using Command Shortcuts 2-14 Changing Icons on the Command Shortcuts Menu 2-17
Chapter 3 Setting up System Options Overview ....................................................................................................................................... 3-1 Setting Up Scheduled Tasks using cron ........................................................................................ 3-2 Starting the cron Job 3-5
Setting up Call Detail Record Parameters..................................................................................... 3-6 Setting the CDR File Format 3-7 Setting the Time Duration recorded in CDRs 3-9
Configuring Additional Options.................................................................................................. 3-11 Using the Outbound Translation Option 3-12 Using the Interpret Digits Option 3-14 Using the Translate with Prefix Option 3-16 Selecting the Master Host 3-18 Disabling the Custom Application Feature 3-20 Synchronizing Switch Timing 3-22 Synchronizing Clocks on Redundant Hosts 3-25
iii
EXS ExchangePlus Software Operations Guide
Chapter 4 Redundant Hosts Overview........................................................................................................................................4-1 Setting up Redundant Hosts 4-2 Saving Configuration Files on Redundant Hosts 4-6 Master and Standby Database Synchronization 4-7 Forcing Switchover between Hosts 4-8 Upgrading Software on Redundant Hosts 4-9
Chapter 5 Configuration Overview Introduction....................................................................................................................................5-1
Chapter 6 Configuration Procedures Overview........................................................................................................................................6-1 Adding or Changing a T1 Span 6-3 Adding or Changing an E1 Span 6-6 Adding or Changing DSP Resources 6-9 Adding or Changing Trunk Groups 6-12 Deleting Trunk Groups 6-16 Adding or Changing Routes 6-17 Deleting Routes 6-22 Adding Trunks to Trunk Groups 6-23 Deleting Trunks from Trunk Groups 6-25 Adding or Changing ANI Tables 6-26 Deleting ANI Entries 6-31 Adding or Changing DNIS Translations 6-32 Sorting Entries in DNIS Translation Table 6-48 Deleting DNIS Translations 6-49 Adding and Changing Exception Tables 6-50 Deleting Exceptions 6-53 Adding or Changing Announcements 6-54 Deleting Announcements 6-56 Downloading Announcements 6-57 Configuring Time of Day (TOD) Routes 6-58 Deleting Time of Day Routes 6-61 Configuring Day of Week (DOW) Routes 6-62 Deleting Day of Week Routes 6-64 Saving Configuration Changes via xmenu 6-65 Making Configuration Changes via UNIX 6-68 Saving Configuration Changes via UNIX 6-71 Printing the Configuration 6-72 Rolling Over CDRs Manually 6-73
Chapter 7 SS7, ISDN, and E1R2 Overview........................................................................................................................................7-1 Setting up a Span to use SS7 Signaling 7-2 Setting up a Span to use ISDN Signaling 7-25 Setting up an E1 Span to use E1R2 Signaling 7-44
Chapter 8 Custom Applications Overview........................................................................................................................................8-1
iv
EXS ExchangePlus Software Operations Guide
Custom Application Description ................................................................................................... 8-1 Installing Custom Applications 8-3 Activating Custom Applications 8-5 Deleting Custom Applications 8-9 Reloading Custom Applications 8-10 Defining Custom Application Flag Names 8-12
Chapter 9 Monitoring Status Overview ....................................................................................................................................... 9-1 Checking Span Status 9-2 Checking Status of Channels on a Span 9-3 Checking Channel Status 9-4 Checking Matrix Cards Status 9-5 Checking DSP Card Status 9-6 Checking SS7 Card Status 9-7 Checking ISDN Card Status 9-8 Checking Line Card Status (T1 or E1) 9-9 Checking Standby I/O Card Status 9-10 Checking VRAS Status 9-11 Checking Synchronization Status 9-12 Checking Link Status 9-13 Checking Node(s) Status 9-14 Checking Ring(s) Status 9-15 Checking Version Status 9-16 Viewing User Log 9-17 Viewing System Log 9-18
Chapter 10 Call Statistics Overview ..................................................................................................................................... 10-1 Configuring Call Statistics 10-2 Viewing Call Statistics 10-4
Chapter 11 Monitoring Trunk Activity Overview ..................................................................................................................................... 11-1 Setting the Watcher Monitoring Intervals 11-3 Configuring Watcher to Monitor Trunk Parameters 11-4 Configuring Watcher for Paging 11-6 Configuring Watcher for E-Mail 11-7 Viewing Watcher Log 11-8 Viewing Watcher Page Log 11-9 Viewing Watcher E-mail Log 11-10
Chapter 12 SNMP and Alarm Monitoring Overview ..................................................................................................................................... 12-1 Quick Start Reference for the SNMP Agent 12-2 Setting up the SNMP Application 12-3
HP OpenView SNMP Network Node Manager.......................................................................... 12-4 Loading an EXS ExchangePlus MIB 12-6 EXS-LE EMAC Alarm Panel Hardware Setup 12-9 Upgrading the Alarm Panel’s Embedded Software 12-11
v
EXS ExchangePlus Software Operations Guide
Upgrading the Alarm Panel’s EPROM 12-12 EXS-LE Alarm Panel Setup for Multi-Cabinets 12-13 Setting up the Alarm Panel Hostname 12-15 Alarm Panel and Pager Configuration 12-16 Clearing an Alarm Panel Condition 12-21 Viewing Alarm Panel Events 12-22
Chapter 13 Backup Overview......................................................................................................................................13-1 Backup for ExchangePlus 13-2
Chapter 14 Maintenance and Troubleshooting Overview......................................................................................................................................14-1 Starting the Host Controller 14-2 Restarting a Host 14-6 Stopping the cron Job 14-9 Starting the cron Job 14-10 Changing the Host Name 14-11 Removing Old CDR Files 14-13 Taking a Span Out of Service (OOS) 14-14 Taking Trunks Out of Service 14-15 Deleting or Re-assigning a T1 or E1 Span 14-16 Bouncing the Channels 14-18 Reloading Trunk Instructions 14-19 SS7 Channels Are Not Processing Traffic 14-21 Cannot Write CDRs 14-23 Changing Time Zones on ExchangePlus Hosts 14-25 Calls Stop on a Particular Node 14-27 Downloading Firmware 14-28
Appendix A xmenu Functions Overview.......................................................................................................................................A-1 System Menu ................................................................................................................................A-2 Status Menu ..................................................................................................................................A-3 Maint Menu...................................................................................................................................A-4 Database Menu .............................................................................................................................A-5 SS7 Menu......................................................................................................................................A-6 ISDN Menu...................................................................................................................................A-7 E1R2 Menu ...................................................................................................................................A-8
Appendix B Trunk Types and Flags Overview....................................................................................................................................... B-1
Appendix C Call Detail Record Formats Overview....................................................................................................................................... C-1
Appendix D Table Sizes Overview.......................................................................................................................................D-1
vi
EXS ExchangePlus Software Operations Guide
Appendix E UNIX Reference Overview .......................................................................................................................................E-1 General UNIX Information ...........................................................................................................E-1 UNIX Commands..........................................................................................................................E-4 UNIX Permissions.......................................................................................................................E-12
Appendix F Error Messages/Response Status Values Overview .......................................................................................................................................F-1 General Information ......................................................................................................................F-1 Categories of Error Messages........................................................................................................F-2 API Response Status Values .........................................................................................................F-3
Appendix G SS7 and ISDN Protocols Overview ...................................................................................................................................... G-1 SS7 ............................................................................................................................................... G-1 SS7 Cause Codes.......................................................................................................................... G-6 ISDN........................................................................................................................................... G-11
Appendix H SNMP and MIB Reference SNMP ........................................................................................................................................... H-1
Appendix I Traps Reference ExchangePlus Traps .......................................................................................................................I-1
Appendix J Alarm Panel Switch Alarms Overview ....................................................................................................................................... J-1
Glossary Index
vii
EXS ExchangePlus Software Operations Guide
viii
EXS ExchangePlus Software Operations Guide
Before You Begin This guide provides the user with operational procedures which will be used when working with EXS ExchangePlus (referred to as ExchangePlus). It assumes that the system has been installed and started initially by Lucent Technologies personnel and does not describe those activities. •
Chapter 1 provides an introduction and some basic system concepts.
•
Chapter 2 describes basic tasks that are performed when the system is first installed and setup. This chapter is intended as a reference.
•
Chapter 3 describes setting up a number of options that you may need depending on your configuration. This chapter is intended as a reference.
•
Chapter 4 covers initial setup and recovery procedures for redundant hosts. Redundancy is automatically handled by the system and so this chapter is primarily for reference.
•
Chapter 5 offers a high level overview of how to configure network connections.
•
Chapter 6 and 7 provide step-by-step details of switch provisioning.
•
Chapter 8 describes how to set up the system to use custom applications.
•
Chapter 9 describes how to monitor status of the system.
•
Chapter 10 describes how to set up and monitor call statistics.
•
Chapter 11 describes how to monitor trunk activity using the Watcher function.
•
Chapter 12 describes how to use the Simple Network Management Protocol (SNMP) for network monitoring and how to set up and use the alarm panel.
•
Chapter 13 provides a backup procedure.
•
Chapter 14 describes maintenance and troubleshooting tasks.
•
Appendix A provides a list of all system functions available via xmenu.
•
Appendix B provides a listing of trunk flags and trunk types.
•
Appendix C provides a listing of the Release 2.x and Release 3.x CDR formats.
•
Appendix D provides a list of table sizes allowed in this release.
•
Appendix E provides an overview of basic UNIX commands.
•
Appendix F describes the format of error messages and provides a list of all the response status values.
•
Appendix G provides general information on SS7 and ISDN protocols.
ix
Audience
EXS ExchangePlus Software Operations Guide
•
Appendix H provides a description of the ExchangePlus SNMP Agent and MIB.
•
Appendix I provides a description of the ExchangePlus SNMP traps.
•
Appendix J provides a description of the ExchangePlus alarm panel and switch alarms.
Audience This guide is intended for you if you are: • • • •
Operating Administering Maintaining Provisioning
EXS ExchangePlus Release 3.1
Other Documentation In addition to this document, the EXS ExchangePlus Hardware Installation and Operation Manual contains information on the ExchangePlus hardware. You may also want to refer to the Excel Switching Software Reference Manual, Version 5.3 (Document Number 08-2109-00) and the Excel Switching Software Developer’s Guide, Version 5.3, Extended API (Document Number 08-2112-00) for additional information.
Technical Support Lucent Technologies is dedicated to providing prompt and effective support. • • • •
x
Within United States: 1-800-541-7002 International: 1-508-862-3366 Fax: 1-508-862-3351 Email: xltechsupport@lucent.com
EXS ExchangePlus Software Operations Guide
Required Items
Required Items Some or all of the following may be required to operate ExchangePlus: • • • •
Hummingbird Communications Exceed software Telnet software A text editor, such as vi Microsoft Excel, Visual FoxPro, or some other program used for reading and processing Call Detail Records (CDRs).
xi
Required Items
xii
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
1 Introduction Overview As a turnkey solution, EXS ExchangePlus (ExchangePlus) is a full-featured tandem and international gateway switch for service providers. The architecture of ExchangePlus supports both 24- and 32-channel interfaces in compliance with ANSI and ITU standards. This gives you: • • • • •
Signaling flexibility for simple creation and modification of in-country variants Scalability to accommodate bandwidth and cost needs Ease of use and detailed reporting for close monitoring and system control Reliability in both reporting and redundancy High-level Application Programming Interface (API) for creating customized services
ExchangePlus uses EXS Signaling. This software enables you to access signaling from a higher level, so modifications can be made without altering internal system code.
Usability
ExchangePlus provides a graphical user interface (GUI) for all system functions that are user-controlled. Some of these include routing, reporting and operations, administration, and maintenance (OA&M). ExchangePlus provides flexible routing criteria such as day-of-week and time-ofday. Numerous hunting algorithms are also available, including round robin, low-tohigh, high-to-low and even/odd circuit identification code (CIC). The system also features 20 trunk groups per route list and trunk group partitioning. This subdivides the switch and thus assigns independent routing and translation tables to discrete traffic segments. You can configure the routing tables in cascading order and evaluate your criteria for call completion if an attempt is unsuccessful. This helps you ensure that calls get completed. As part of its ability to support any international numbering plan, ExchangePlus provides 23-digit translations and interworking between signaling variants. You are able to modify routing tables in real time, as well as access them remotely for close system monitoring. The reporting capabilities are detailed and include statistics such as: inbound, outbound, outseize, connected, answered, route, trunk group, and percent-answered.
1-1
Overview
EXS ExchangePlus Software Operations Guide
Reports can be generated as often as one a minute, allowing you to closely monitor traffic conditions. The SNMP agent provides easy integration into network operations centers or other central management systems. The system also has an alarm panel. This alarm panel allows the switch to be programmed to page support personnel when it detects critical errors.
Summary of Features
Signaling Protocols
• • • • • • • •
T1 and E1 network interfaces A-law and/or µ-law and conversions Scalable from 192 ports to more than 20,000 Any number of trunks in a group Switch partitioning All components can be hot-swappable Scalable in eight span increments Seismic Zone 4 compliance
Signaling protocols are all configurable for in-country or proprietary variants. SS7/C7 (ITU and ANSI), ISDN-PRI, MFR1, MFCR2/CAS, E&M, FXO, FXS, DTMF, MF, DP, FGA-FGD, DID
Routing and Translation Features
• • • • • • • • • •
Least-cost routing Virtual private networks (VPN) Time-of-day routing Configurable hunting (linear, first idle, round-robin) Day-of-week routing ANI translation to 23 digits Paired-trunk routing DNIS translation to 23 digits (supports international standards) Up to 20 trunk groups per route list ANI//DNIS matching to 23 digits
OA&M Features
• • • • • •
Menu-based user interface Real-time and programmable alarming Local and remote maintenance Performance reporting Up to five simultaneous users SNMP support for alarms
CDR Features
• • • • •
Real-time CDR Automatic CDR archiving DBF CDR format CDR reporting to multiple locations Over 60 CDR fields supported
1-2
EXS ExchangePlus Software Operations Guide
System Concepts
Optional System Redundancy
• • • • • • •
No single point of failure 1+1 power supply load sharing, dual power feeds N+1 DSP load sharing 1+1 CPU active standby 1+1 SS7 and 1+1 ISDN active standby Host protection N+1 line card redundancy
Optional Voice Announcements
• • •
User-programmable announcements Integrated announcements Announcement capacity—2048 per system selectable language
System Concepts This section provides some background information on ExchangePlus including: •
A simplified call flow to show how calls are processed by the system.
•
A description of how data is saved on the ExchangePlus system.
•
A description of the user interfaces available on ExchangePlus.
ExchangePlus Call Flow This section provides a high-level description of how calls are processed through the ExchangePlus system. This information is provided as background material to help you understand how to configure and operate your system. It is also provided to introduce some of the terminology used with ExchangePlus. Some of the details have been excluded to allow you to focus on the basic call flow. More detail will be added in the explanation below and in the chapters describing configuration. Figure 1-1 and Figure 1-2 show the simplified call flow. The text following the figures describes the call flow. The numbers beside the steps in the figures correspond to the numbered items in the text.
1-3
ExchangePlus Call Flow
EXS ExchangePlus Software Operations Guide
1
Incoming Call
2
Is ANI Screening enabled on the incoming trunk?
No
Go to Step 7 in Figure 1-2.
Yes Search ANI Table.
Is there a match in the table?
No
Go to Exception 29 (No ANI exists)
Yes Perform translation on the calling number and set the Nature of Address and Restriction for the Calling Number.
3
Is the restriction B or T?
4
5
Yes
Go to Exception 27 (for B) or 28 (for T).
No 6
Restriction = U or R, so the matching entry specifies the Search Partition to use in DNIS Translation table.
Go to Step 7 in Figure 1-2.
Figure 1-1 Simplified Call Flow
1-4
EXS ExchangePlus Software Operations Guide
ExchangePlus Call Flow
7
Incoming Call
Search the appropriate partition in the DNIS Translation Table.
Is there a match in the table?
No 8
Use Default Route.
Yes 9
Perform translation on the called number. Obtain route and routing flags.
10
Go to Route List Table to obtain trunk group on which to send the call.
11
Go to Trunk Group Table to obtain partition of the outgoing trunk group.
Is outbound translation enabled?
No
Yes 12
13
Go to DNIS Translation table and translate the called number again. Go to Trunk Table to obtain trunk on which to send the call.
14
Is there an idle trunk available?
No
Send release with “No circuit available� to incoming trunk for common signaling or send reorder (fast busy) for inband call.
Yes Route the call on 15 the selected route.
Figure 1-2 Simplified Call Flow (continued)
1-5
ExchangePlus Call Flow
EXS ExchangePlus Software Operations Guide
1. When a call comes into the switch, ExchangePlus determines if Automatic Number Identification (ANI) screening is enabled on the incoming trunk. If it is, the system accesses the ANI table. If not, the system accesses the DNIS Translation table (see Step 7). 2. The system uses the calling number and the partition number of the incoming trunk group to determine how the calling number should be translated and whether or not the call should be blocked based on the calling number. 3. If there is no match in the table, the call is routed to Exception 29 (No ANI exists). This is a pre-specified exception. You can choose the action that occurs for the exception. For example: you could route to a tone, play an announcement, etc. 4. If there is a match in the ANI table, the calling number is translated according to the translation in the matching entry. Digits may be added or stripped from the calling number or the number may be left as is. The matching entry may also specify the Nature of Address for the calling number (specified in the NOA field) and the Restriction for the call (specified in the REST field). The Restriction determines whether or not the call is blocked based on the calling number. 5. If the Restriction is B (permanently blocked) or T (temporarily blocked), the call is routed to an exception 27 or 28, respectively. These are prespecified exceptions. You can choose the action that occurs for each exception. 6. If the Restriction is U (unblocked) or R (restricted), then the matching entry determines the Search Partition to use in the DNIS Translation table. This determines how to translate and route the Called Number. Unblocked (U): Call is not blocked and calling number can be displayed on Caller ID boxes. Restricted (R): Call is not blocked, but calling number cannot be displayed on Caller ID boxes. 7. The system accesses the DNIS Translation table. Based on the partition of the incoming trunk group or from the ANI table, the system attempts to match the dialed or called number (CLD). A matching entry in the DNIS Translation table will determine how the called number should be translated and what route should be used for the call.
1-6
EXS ExchangePlus Software Operations Guide
ExchangePlus Call Flow
NOTES •
The partition is a subtable within the DNIS Translation table. Individual subtables (or partitions) are usually defined for each carrier and allow you to specify call treatments based on the carrier. The partitions (or subtables) are used to determine which entries can be matched in the DNIS Translation table and which entries can be used in the Exception table. In the DNIS Translation table, the system attempts to match the partition and called number to one of the entries in the table.
•
Also, if the Interpret Digits option has been enabled, then the called number will be normalized (digits may be stripped or added) before it is matched to an entry in the DNIS Translation table.
8. If there is no match, a default route is selected. (The default route is determined from the Trunk table.) 9. If there is a match in the DNIS translation table, the called number is translated according to the translation in the matching entry. Digits may be added or stripped from the called number or the number may be left as is. This matching entry also specifies the route list that will be used to route this call. Valid choices are a route list (Rn), Exception (Xn), Announcement (An), Conference (Cn), Time of Day (Dn), or Day of Week (Wn) table. 10. Assuming the call is routed to the route list, the Route List table will determine the trunk group(s) and the order in which different trunk groups will attempt the outbound call. The outbound trunk group is selected. 11. The system accesses the Trunk Group table to determine the partition of the outgoing trunk group. 12. If Outbound Translation is not enabled, go to Step 13. When outbound translation is enabled and if: • •
The partition of the outgoing trunk group is different from the partition of the incoming trunk group, and There is a match in the DNIS Translation table
Then •
The called number may be translated again and the NOA flag may be reset.
13. Once the trunk group has been selected and outbound translation has been performed (if enabled), the system uses the trunk table to determine if there are any trunks available to route the call. 14. If a trunk is available, the call is sent out over the selected trunk.
1-7
ExchangePlus Call Flow
EXS ExchangePlus Software Operations Guide
15. If: •
The selected route list contains only one entry,
And •
There are no idle trunks in the specified trunk group,
Then: •
A release with “No circuit available” is sent back to the to the incoming trunk for common signaling calls,
Or •
1-8
A re-order (fast busy) is played on the incoming trunk for inband calls. If the route list contains more than one entry, then each entry will be tried in order.
EXS ExchangePlus Software Operations Guide How Information is Loaded and Saved on ExchangePlus
How Information is Loaded and Saved on ExchangePlus Figure 1-3 illustrates how configuration information is loaded and saved in an ExchangePlus host.
readcfg (command line) or Load Switch Config (xmenu)
Shared Memory Tables
dbcp dbcp1
Export Tables or Save Slot Config Seed Files switch.cfg board.cfg
Database Files <xxx.dbf>
xmenu or menu
Figure 1-3 How Configuration Information is Saved
When the host is brought into service, the system is configured using two files called switch.cfg and board.cfg. These are seed files which load the initial configuration into the system. Switch.cfg is loaded using the command readcfg and board.cfg is loaded when you start the host. When the files are loaded, the configuration is stored in shared memory tables. During installation, the installer runs a program called dbcp to save the configuration loaded from switch.cfg to database files. Once dbcp has been run, any changes you make to the configuration using either the Windows interface (xmenu) or the character-based interface (menu) are automatically updated in the shared memory tables and the database files. If you have a redundant host, the changes in the shared memory of the master host are sent automatically to the shared memory in the standby host. As soon as these changes are received, the shared memory in the standby host sends an update to its own database files. At this point, the shared memory and database files in the master and standby host should be synchronized. If one of the hosts go down, ExchangePlus will automatically attempt (using the cron task) to restart it using the configuration currently loaded in shared memory. If you want to save configuration changes to a file (for backup purposes, for example), you can use a function called Export Tables to take the information from the shared memory tables and save them back to switch.cfg (the seed file) or some other file that you specify.
1-9
ExchangePlus User Interfaces
EXS ExchangePlus Software Operations Guide
ExchangePlus User Interfaces ExchangePlus provides two interfaces from which you can perform most functions: â&#x20AC;˘
xmenu: The Windows-based graphical user interface can be used on a PC. It is an easy to use point-and-click interface and is most often used when you are operating locally. It requires more bandwidth than is often available for a remote connection.
â&#x20AC;˘
menu: The Curses interface is a character-based interface that can be used on a VT100 or other dumb terminal.
In addition to these two interfaces, there are a limited number of commands that must be performed from the UNIX command line. This section provides a brief overview of both the Windows and the Curses interface. This guide describes only the Windows interface in detail.
Windows-based User Interface Figure 1-4 shows the main window of the Windows interface.
Figure 1-4 Main Menu for the Windows Interface
1-10
EXS ExchangePlus Software Operations Guide
Using the Windows Interface
Steps
Windows-based User Interface
This section provides a high-level description of how to use the Windows interface. NOTE: Appendix A, â&#x20AC;&#x153;xmenu Functionsâ&#x20AC;? contains a complete listing of all functions provided in the Windows interface and a brief description of each function. 1. Use the mouse to click on the menu of interest in the menu bar at the top of the window. When you click on a menu, the menu selections appear in a dropdown menu (Figure 1-5)
Figure 1-5 Example of a Drop-Down Menu from the Windows Main Menu
2. Use the mouse to choose the menu item of interest. Often, when you make a selection from the menus, another window appears such as the one shown in Figure 1-6.
1-11
Windows-based User Interface
EXS ExchangePlus Software Operations Guide
Figure 1-6 A Sample Window That Appears When You Choose a Menu Item
3. Enter data in the fields by typing on the keyboard or make selections by pointing and clicking with the mouse. In some cases, a command line appears instead of a window. In that case, enter the information requested in the command line in the specified format and press <Enter> in the command. This document describes how to perform all of the functions using the Windows interface (xmenu).
1-12
EXS ExchangePlus Software Operations Guide
Curses Interface
Curses Interface Figure 1-7 shows the main menu of the Curses interface.
Figure 1-7 Main Menu for the Curses Interface
Using the Curses interface
Steps
This section provides a high-level description of how to use the Curses interface (a character-based interface). You may choose to use this interface if you are connected to the ExchangePlus system remotely. 1. Use the down arrow key (↓) to display the system menu on the Curses interface. 2. Once that menu is displayed, use the left (←) or right (→) arrow keys to display the menu of interest (Figure 1-8).
1-13
Curses Interface
EXS ExchangePlus Software Operations Guide
Figure 1-8 Drop-Down Menu from the Curses Interface
3. Use the up (â&#x2020;&#x2018;)and down (â&#x2020;&#x201C;) arrow keys to select the menu item of interest. 4. Often as a result of selecting a menu item, a command line appears asking you to enter specific information. If such a command appears, enter the information (in the specified format) and press <Enter> (Figure 1-9).
Figure 1-9 Command Line from the Curses Interface
This document does not describe how to perform all of the various functions using the Curses menu.
1-14
EXS ExchangePlus Software Operations Guide
Overview
2 Setting Up Access to ExchangePlus Overview This chapter describes some of the basic setup tasks that you may need to perform the ExchangePlus system options. These setup tasks include: • • •
Accessing the Host from a Windows Platform Accessing the Host from a Non-Windows Platform Using and Changing ExchangePlus Command Shortcuts
NOTE: Most of the procedures in this chapter are usually performed only once during setup and they are global settings. Before changing any of these settings, contact Lucent Technologies Technical Support. The following table lists the setup procedures and the page number where they can be found. Procedure Name
Page
Procedure 1 Obtaining Host Name and IP Address
2-3
Procedure 2 Installing Exceed on a Windows Platform
2-4
Procedure 3 Adding the ExchangePlus Host to Exceed
2-5
Procedure 4 Accessing the Host using Exceed
2-7
Procedure 5 Accessing the Host using Telnet
2-11
Procedure 6 Accessing the Host from a UNIX-based System
2-13
Procedure 7 Using Command Shortcuts
2-14
Procedure 8 Changing Icons on the Command Shortcuts Menu
2-17
2-1
Accessing the Host from a Windows Platform
EXS ExchangePlus Software Operations Guide
Accessing the Host from a Windows Platform If you will be using ExchangePlus remotely from a Windows platform, Lucent Technologies recommends that you use a software package called Exceed by Hummingbird Communications. Exceed is the ExchangePlus host interface to the UNIX operating system. UNIX is the operating system of the ExchangePlus system’s rack-mounted hosts. In providing this interface, Exceed emulates the UNIX client environment. The following sections describe: • • • •
2-2
Obtaining Host Name and IP Address Installing Exceed on a Windows platform Adding the ExchangePlus Host to Exceed Accessing the Host using Exceed
EXS ExchangePlus Software Operations Guide
Procedure 1
Obtaining Host Name and IP Address
Obtaining Host Name and IP Address This procedure describes how to obtain the name and IP address of the ExchangePlus host. You need to know the name and IP address of the host in order to configure Exceed.
Requirements
Steps
•
You have a null modem serial cable and a Maintenance PC (either a laptop computer with a serial port or a VT100 terminal with a serial port). Note that the null modem cable must be used with a male-to-female adaptor to allow connection to a Sun AXi Host. For more information, refer to the EXS ExchangePlus Hardware Installation and Operation Manual.
•
The host is powered ON.
•
You know the user name and password of the host.
1. Connect a null modem cable between the Maintenance PC serial port and the rack-mounted Host serial port. The Sun Netra serial port is the lower 25-pin port labeled “A”, while the Sun AXi serial port is the upper 25-pin port. The Maintenance PC will require a DB9 connector while the rack-mounted Host requires a DB25 connector. 2.
Log into the host by entering the user name and password.
3. Type: cat /etc/hosts
A list of the host names and IP addresses for this host and all adjacent hosts is displayed.
2-3
Installing Exceed on a Windows Platform
Procedure 2 Requirements
Steps
EXS ExchangePlus Software Operations Guide
Installing Exceed on a Windows Platform If you do not know the IP Address of the ExchangePlus host, see Procedure 1 Obtaining Host Name and IP Address on page 2-3. Install Exceed on your Windows platform according to manufacturerâ&#x20AC;&#x2122;s instructions. Follow the Exceed Auto Setup procedure. Setup in the ExchangePlus host Windows NT/98 environment is routine with the following exception: During the installation of Exceed you will be prompted to install to all profiles, select this item. If you do not, Exceed will be difficult to work with when you use multiple profiles. NOTE: During Exceed installation, you are prompted to password protect your Xconfig (X-windows configuration). Itâ&#x20AC;&#x2122;s your choice whether or not to password protect your X-windows configuration. Protecting Xconfig will deny others access to Exceed and prohibit them from changing any of your settings. If you choose to use the password option, do not forget the password. If you do, you will have to reinstall Exceed to change any options within Xconfig.
2-4
EXS ExchangePlus Software Operations Guide
Procedure 3
Adding the ExchangePlus Host to Exceed
Adding the ExchangePlus Host to Exceed The procedure describes how to add an ExchangePlus host to Exceed so that you can access the host remotely. You only need to perform this procedure once. After the setup is complete, you can then access the host anytime you want by following the steps in Procedure 4 Accessing the Host using Exceed on page 2-7.
Requirements
Steps
If you do not know the IP address of the host to which you want to connect, see Procedure 1 Obtaining Host Name and IP Address on page 2-3. 1. From your Windows desktop, click on the Start button in the task bar, and then select Start >Programs > Exceed > Xconfig. The exceed.cfg - Xconfig window appears. 2. Double click on the Communication icon. The Communication window appears (Figure 2-1).
Figure 2-1 Communication Window
3. Verify that the Mode field is set to XDMCP-query. Click on Configure... 4. The XDMCP Startup Modes window appears (Figure 2-2).
2-5
Adding the ExchangePlus Host to Exceed
EXS ExchangePlus Software Operations Guide
Figure 2-2 XDMCP Startup Modes Window
5. Enter the name or the IP address of the host in the Connect Host field. 6. Click OK. You are returned to the Communication window. 7. Click OK again. If you are adding a new host, the system will indicate that you need to perform a restart in order to save the information you just entered. After restarting, you can connect to the host from your PC running Exceed. Proceed to Procedure 4 Accessing the Host using Exceed on page 2-7.
2-6
EXS ExchangePlus Software Operations Guide
Procedure 4 Assumptions
Steps
Accessing the Host using Exceed
Accessing the Host using Exceed You have already added the ExchangePlus host to Exceed by following Procedure 3 Adding the ExchangePlus Host to Exceed on page 2-5. From your Windows desktop, click the Start button in the task bar, and then select Programs > Exceed > Exceed. The Hummingbird Exceed Startup window appears briefly. 8. A window appears allowing you to log onto the ExchangePlus host. Enter the user name and password and click OK. 9. The Sun Solaris Welcome window appears briefly and is replaced with an empty window displaying the Common Desktop Environment (CDE) tool bar across the bottom.
2-7
Accessing the Host using Exceed
EXS ExchangePlus Software Operations Guide
10. You can operate the system using icons or by typing commands from a terminal window. To use icons, go to Procedure 7 Using Command Shortcuts on page 2-14. Continue with this step to use commands. Open a terminal window and do the following: Place the cursor on the empty window and click on the right mouse button to bring up the Workspace menu. Select Programs > Terminal. A terminal window appears (Figure 2-3).
Figure 2-3 Terminal Window Connected via Exceed
11. Change the active directory by typing the following at the /usr/isos prompt: cd bin
Now you can open either the Windows-based interface or the Curses interface. You can perform all of the functions of the ExchangePlus software from either of these interfaces. 12. To open the Windows-based interface, type: xmenu&
To open the character-based interface (Curses), type: export TERM=xterm menu
NOTE: The use of the ampersand (&) following the command is optional. It causes the program to run in the background and allows you to re-use the window for other purposes, as required. If you do not run the program in the background, you may need to open a second terminal window to perform other UNIX functions.
2-8
EXS ExchangePlus Software Operations Guide
Accessing the Host using Exceed
Figure 2-4 and Figure 2-5 shows the Windows-based interface and characterbased interface, respectively.
Figure 2-4 Windows-based Interface
Figure 2-5 Curses Interface
When you open either of these two interfaces, you can begin performing the functions of the ExchangePlus software.
2-9
Accessing the Host from a Non-Windows Platform
EXS ExchangePlus Software Operations Guide
Accessing the Host from a Non-Windows Platform If you will be using ExchangePlus remotely from a non-Windows platform, Lucent Technologies recommends that you use Telnet. Telnet allows you to connect to the host running ExchangePlus from a remote location. The following sections describe: â&#x20AC;˘ â&#x20AC;˘
2-10
Accessing the Host using Telnet Accessing the Host from a UNIX-based System
EXS ExchangePlus Software Operations Guide
Procedure 5 Requirements
Steps
Accessing the Host using Telnet
Accessing the Host using Telnet •
Telnet software is running on the platform being used to access the ExchangePlus host.
•
There is a network connection between the host and your platform using TCP/IP.
•
If you do not know the IP address of the ExchangePlus host, see Procedure 1 Obtaining Host Name and IP Address on page 2-3.
1. In a terminal window, type: telnet <IP address of host>
2. You may be asked to log onto the ExchangePlus host. Enter the user name password. 3. A terminal window appears (Figure 2-6).
Figure 2-6 Terminal Window Connected via Telnet
4. Change the active directory by typing the following at the /usr/isos prompt: cd bin
Now you can open the Curses interface. 5. To open the Curses interface, type: export TERM=vt100 menu
If your Telnet program does not support line drawing characters, try typing: menu -V
If the arrow keys do not work and you are using Microsoft Telnet, you can set the arrows to “vt100 arrows” under Terminal > Preferences.
2-11
Accessing the Host using Telnet
EXS ExchangePlus Software Operations Guide
Figure 2-7 shows the Curses Interface.
Figure 2-7 Curses Interface
Once you have opened this interface you can begin performing the functions of the ExchangePlus software.
2-12
EXS ExchangePlus Software Operations Guide
Procedure 6
Accessing the Host from a UNIX-based System
Accessing the Host from a UNIX-based System This procedure describes how to use a UNIX-based machine as a maintenance PC from which you can operate ExchangePlus.
Requirements
Steps
â&#x20AC;˘
The host (Sun Netra or AXi) is running Sun Solaris 7 and the maintenance system is a PC or workstation running a UNIX operating system, such as Sun Solaris, SCO UNIX, etc.
â&#x20AC;˘
You know the IP address of the ExchangePlus host and the UNIX-based maintenance PC.
1. On the command line of the maintenance PC, type: xhost +
This disables access control. 2. On the command line of the maintenance PC, type: telnet <IP address of host>
3. When you are connected, log on to the host and go to the /usr/isos/bin directory by typing: cd /usr/isos/bin
4. On the command line of the host, type: export DISPLAY=<IP address of the UNIX-based system>
This sets the display to the UNIX-based maintenance PC. 5. At the command line of the host, type: xmenu&
This will display the xmenu main menu on the UNIX-based maintenance PC.
2-13
Using Command Shortcuts
Procedure 7
EXS ExchangePlus Software Operations Guide
Using Command Shortcuts ExchangePlus provides shortcuts for some of the most commonly used commands. These shortcuts allow you to select common tasks from a menu that is available from the Common Desktop Environment (CDE) tool bar. This is the tool bar that appears at the bottom of the window when you connect to a Solaris host.
Assumptions
Steps
â&#x20AC;˘
The shortcuts are currently supported on Sun Solaris CDE only.
â&#x20AC;˘
You are connected to a Solaris host and are about to log in.
1. As you connect to the Solaris host using Exceed, you are asked to log onto the ExchangePlus host. Enter the user name and password and click OK. 2. The Sun Solaris Welcome window appears briefly and is replaced with an empty window displaying only the CDE tool bar across the bottom of the window (Figure 2-8).
HOST Icon Figure 2-8 CDE Toolbar
The HOST icon on the left side of the CDE tool bar allows you to access the most common ExchangePlus commands which are usually executed from a terminal window. Click on the arrow above the HOST icon to open the Command Shortcut menu.
2-14
EXS ExchangePlus Software Operations Guide
Using Command Shortcuts
The Command Shortcut menu is shown in Figure 2-9.
Figure 2-9 Command Shortcut Menu
3. To select a function, click on the appropriate icon. For example: When you click on the Open Xmenu icon from the Command Shortcut window, the Windows-based user interface (xmenu) opens automatically. In this case, using this icon would save you from opening a terminal window, navigating to the /usr/isos/bin directory, and then typing xmenu. The last icon in the menu is a folder labeled isos. Click on this icon to open a window containing a complete list of all the command shortcuts that are available (only a subset of these appear in the Command Shortcut menu).
2-15
Using Command Shortcuts
EXS ExchangePlus Software Operations Guide
The following is a list of all command shortcuts that are available: • • •
• • • • • • • • • • • • • • •
2-16
Create DB - creates database files from information in shared memory by running the dbcp command Create DB_1 - updates shared memory with the information in the database files by running the dbcp1 command Kill Process -Kills a process by running the pkill command. The system will ask you to enter the name of the process you want to kill. After you enter the process name and press <Enter>, the process is killed. List Process - List all ExchangePlus related processes by running the listit command Open Menu - Runs the menu command which opens the character-based user interface Open Xmenu - Runs the xmenu command which opens the Windows-based user interface Open Xterm - Runs the xterm command which opens an X-terminal window Read Switch Config - Runs the readcfg command to read the configuration files into shared memory Remote Login - Runs the rlogin command which performs a remote log in Startup - Runs the startup command which starts the host Stopit - Runs the stopit command which stops the host processes Telnet - Open a Telnet session Text Editor - Open a text editor View boardcfg - Opens the board.cfg file in a text editor View Logs - Displays a listing of all logs available and allows you to select one and view it View Reports - Displays a listing of reports available and allow you to select one and view it View switch.cfg - Opens the switch.cfg file in a text editor isos - Displays all the command shortcuts that are available, not just the ones that appear in the Command Shortcut menu.
EXS ExchangePlus Software Operations Guide
Procedure 8
Changing Icons on the Command Shortcuts Menu
Changing Icons on the Command Shortcuts Menu This procedure describes how you can change the icons displayed on the command shortcuts menu.
Steps
1. To change the commands displayed on the Command Shortcut menu, you can drag any of the icons from the isos window containing all the possible shortcut commands and drop them onto the Install Icon at the top of the menu. The number of icons that can be included in the menu depends on the height of your screen. If you want to delete some of the icons on the menu and replace them with different icons, right-click on an icon in the menu to be deleted, then select Delete from the drop-down menu. The selected icon will be deleted from the menu, giving you room to add additional icons. 2. To add another icon, choose the icon of interest from the isos window, then drag it over the Install Icon selection on the menu. Release the mouse button over the Install Icon. The new icon will be added to the Command Shortcut menu.
2-17
Changing Icons on the Command Shortcuts Menu
2-18
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
3 Setting up System Options Overview This chapter describes how to configure the basic system options for the ExchangePlus environment. These options include: • • •
Setting Up Scheduled Tasks using cron Setting Up Call Detail Record Parameters Configuring Additional Options
NOTE: Most of the procedures in this chapter are usually performed only once during setup and they are global settings. Before changing any of these settings, contact Lucent Technologies Technical Support. The following table lists the system option procedures and the page number where they can be found. Procedure Name
Page
Procedure 9 Starting the cron Job
3-5
Procedure 10 Setting the CDR File Format
3-7
Procedure 11 Setting the Time Duration recorded in CDRs
3-9
Procedure 12 Using the Outbound Translation Option
3-12
Procedure 13 Using the Interpret Digits Option
3-14
Procedure 14 Using the Translate with Prefix Option
3-16
Procedure 15 Selecting the Master Host
3-18
Procedure 17 Synchronizing Switch Timing
3-22
Procedure 18 Synchronizing Clocks on Redundant Hosts
3-25
3-1
Setting Up Scheduled Tasks using cron
EXS ExchangePlus Software Operations Guide
Setting Up Scheduled Tasks using cron ExchangePlus contains a cron task which automatically performs two functions at a customer-specified time interval. The cron task periodically: â&#x20AC;˘
Checks to see if the ExchangePlus software is running on the host. If it is not running, the software is restarted automatically.
â&#x20AC;˘
Rolls over (saves) the Call Detail Record (CDR) files. CDR data that has been collected is written to a call detail record file (either cdr.txt or cdr.dbf). When this file is rolled over, it is renamed and time-stamped and a new call detail record file is started. NOTE: It is very important that the task that rolls over the CDRs occurs on a frequent basis so that CDRs are never lost. The operator needs to coordinate the frequency of the rollover with the maximum number of CDR records that can be saved in the CDR queue.
The default cron task is called cron.dat and is located in /usr/isos/bin directory. The script in the cron.dat file checks if the software is running at a set interval (once a minute) and if it is not running, it restarts the ExchangePlus host software. NOTE: You must not change this restart interval for ExchangePlus redundancy to function properly. The script also rolls over CDR files at a set interval. Figure 3-1 shows an example cron.dat file, which specifies the roll over time as 4:07 PM every day (the default value).
Figure 3-1 The cron.dat File
NOTE: If you want to change the interval of the rollover task, you can modify this file using a text editor, such as vi. To change the cron.dat file, edit this file to modify the line starting with 7 16 * * *. This line contains six fields. The first five fields are integer patterns that specify the minute, hour, day of month, month of year, and day of week.
3-2
EXS ExchangePlus Software Operations Guide
Setting Up Scheduled Tasks using cron
For example: * * * * *
or 7 16 * * *
Each pattern may contain: • • • •
a number in the valid range (see table below) two numbers separated by a minus (indicating an inclusive range such as 3-5) a list of numbers separated by commas (meaning all of these numbers) an asterisk (meaning all legal values)
The sixth field is a string that is executed by the shell at the specified time (for example, /usr/isos/bin/restart > /dev/null). The first line in the file containing asterisks (*) indicates the time interval for the restart. The second line in the file containing asterisks indicates the time interval for the CDR rollover. Do not change the restart line of cron.dat. The table describes the value and range for each of the first five fields and gives examples of possible settings you might use for the CDR rollover interval: Minute (0-59)
Hour (0-23)
Day of Month (1-31)
Month of Year (1-12)
Day of Week (0-6, 0=Sun.)
Runs once a minute. Since there are no values in any of the fields, it runs once a minute (the smallest possible increment).
*
*
*
*
*
Runs once a day at 16:07.
7
16
*
*
*
Runs three times a day at 14:00, 18:00, and 20:00
00
14, 18, 20
*
*
*
Runs once a week, on Tuesday at 9:00 pm (21:00)
00
21
*
*
2
Runs at midnight (00:00) on the first and fifteenth day of every month. Also runs at midnight on every Monday.
0
0
1,15
*
1
Description
The following show some examples of complete lines in the cron.dat file that you might want to use: To have CDRs roll over every hour, on the hour: 0 * * * * /usr/isos/bin/rollover > /dev/null
To have CDRs roll over every 15 minutes, on the quarter hour: 0,15,30,45 * * * * /usr/isos/bin/rollover > /dev/null
To have CDRs roll over every 24 hours, at 4:15AM: 15 4 * * * /usr/isos/bin/rollover > /dev/null
3-3
Setting Up Scheduled Tasks using cron
EXS ExchangePlus Software Operations Guide
To have CDRs roll over every hour at 10 minutes before the hour: 50 * * * * /usr/isos/bin/rollover > /dev/null
CDR data is collected in the /usr/isos/bin directory. The data is stored as ASCII text or in dBase III database format (which can be read using Visual FoxPro or Microsoft Excel, for example). The following table shows the different CDR files that you may see, depending on the type of data that was selected when the software was ordered. The type of CDR written is controlled by a file called cdr.cfg via the ASCIICDRS setting. File Name
Description
cdr.txt
The CDR data in clear text (ASCII) format
cdr.dbf cdr.cdx
The CDR data in database format. Two files are required:
â&#x20AC;˘ â&#x20AC;˘
.dbf contains the actual data .cdx is an index file
When CDR files are rolled over, a timestamp is appended to the file name. The timestamp is of the form: YYYYMMDDHHMMSS
where YYYY = four digit year MM = two digit month DD = two digit day HH = two digit hour (using a 24 hour clock) MM = two digit minute SS = two digit second The timestamp indicates when the last CDR in the file was written. For example: After CDR files have been rolled over, you might have CDR files named: cdr.txt.19990510024503 cdr.dbf.19990510024503 cdr.cdx.19990510024503
These files contain the call detail records that you may want to transfer from the host to your billing system.
3-4
EXS ExchangePlus Software Operations Guide
Procedure 9
Starting the cron Job
Starting the cron Job If the cron job has not been started, start it when you start the system. Once started, you should not need to restart it unless it has been manually stopped.
Requirement
This task must be started by the system user, ISOS, not the ROOT. Otherwise undesired system operation may occur. To determine which user you are logged in as, type: whoami
at the UNIX command line.
Steps
To start the cron job: 1. Go to the terminal window and type: crontab cron.dat
2. To check if the cron job is running, type: crontab -l
If the result is crontab:canâ&#x20AC;&#x2122;t open your crontab file
then the cron is not running and you need to restart it as described above. If the crontab is running, the result will be similar to the following: # # # # # # * 7
Module: cron.dat SCCS ID 1. This script will check the ISOS if not, then it will start it Minute, Hour, Day, Month, Month * * * * /usr/isos/bin/restart > 15 * * * /usr/isos/bin/rollover
to see if it is running of year, Day of week /dev/null > /dev/null
3-5
Setting up Call Detail Record Parameters
EXS ExchangePlus Software Operations Guide
Setting up Call Detail Record Parameters This section describes how to set up options related to call detail records (CDRs). These include: • •
Setting the CDR File Format Setting the Time Duration Recorded in the CDRs
You set these parameters in the host.cfg and cdr.cfg files. The settings that you make in these files are system-wide. NOTES: 1. Before the changes described in this section take effect, the host must be stopped and then restarted. 2. Most of the procedures in this section are usually only performed once during setup. Before changing any of these settings, contact Lucent Technologies Technical Support. 3. The format of the CDR file was modified from Release 2.x to Release 3.x. Release 3.x contains all the fields that had been in 2.x and it contains three additional fields. The Release 3.x format can also be saved in either Database format (DBF) or ASCII format. All customers are encouraged to use Release 3.x format; however, if your billing system is set up for use with the Release 2.x CDR format, you may want to continue to use the Release 2.x format. 4. If, while performing any of the CDR setup procedures, you are unable to access host.cfg, check the permissions of the file. (See “UNIX Permissions” on page E-12.) If you do not have write permission, change the permissions by accessing /isos/usr/bin and typing: chmod u+w <host.cfg>
A complete listing of the Release 3.x and the Release 2.x CDR file formats are provided in “Call Detail Record Formats” on page C-1.
3-6
EXS ExchangePlus Software Operations Guide
Procedure 10
Setting the CDR File Format
Setting the CDR File Format ExchangePlus provides two CDR file formats: •
Release 3.x CDR format (the default)
•
Release 2.x CDR format
The Release 3.x format contains all data in the Release 2.x format plus some additional fields. All customers are encouraged to use the Release 3.x CDR format. However, if you choose to use the Release 2.x CDR format (because your billing system is already set up for that format, for example), this procedure describes how to select it. NOTE: Only use this procedure if you want to use the Release 2.x CDR format instead of the default Release 3.x CDR format.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-2.
Figure 3-2 A sample host.cfg file
If R2CDRFORMAT=0, use the Release 3.x CDR file format. NOTE: If you are unable to access host.cfg, check the permissions of the file. (See “UNIX Permissions” on page E-12.) If you do not have write permission, change the permissions by accessing /isos/usr/bin and typing: chmod u+w <host.cfg>
3-7
Setting the CDR File Format
EXS ExchangePlus Software Operations Guide
4. To use the R2.x CDR file format, edit the file as follows: R2CDRFORMAT=1
5. Save the file. 6. Open the /usr/isos/bin/cdr.cfg file using a text editor such as vi. The cdr.cfg file will be displayed. It will look similar to Figure 3-3.
Figure 3-3 A sample cdr.cfg file
7.
To use the Release 2.x CDR file format, you must set the file format to ASCII (the default). Verify that: ASCIICDRS=1
It is recommended that you leave the file format set to ASCII, as it is easier to read. If ASCIICDRS=0, the file will use the Database format (DBF) instead of ASCII. 8. Save the file. You are now ready to use the R2.x CDR file format.
3-8
EXS ExchangePlus Software Operations Guide
Procedure 11
Setting the Time Duration recorded in CDRs
Setting the Time Duration recorded in CDRs The flag, TIMEFIRSTRELEASE, specifies the time duration recorded in all CDRs that are saved. You can either set the time duration: â&#x20AC;˘ â&#x20AC;˘
Steps
To be based on the initial release message received in the call, or To be based on the final call clearing message that is received.
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-4.
Figure 3-4 A sample host.cfg file
3-9
Setting the Time Duration recorded in CDRs
EXS ExchangePlus Software Operations Guide
4. To set the time duration that is recorded in CDRs, edit the following line in the host.cfg file: TIMEFIRSTRELEASE=
Enter the appropriate value for the TIMEFIRSTRELEASE flag. The possible options are listed below: Value
Description
0 (Default)
Time duration recorded in CDRs is based on the time of the final call clearing message for the call.
1
Time duration recorded in CDRs is based on the time of the initial release message for the call.
5. Save the file.
3-10
EXS ExchangePlus Software Operations Guide
Configuring Additional Options
Configuring Additional Options This section describes some of the parameters that can be configured. The settings you select are system-wide. For example, if the Outbound Translation option is enabled, then that option is used in all routing, not just routing on a particular trunk group. You can configure the following options: Option
Description
Outbound Translation
Specifies whether the outbound translation option is turned on.
Interpret Digits
Specifies whether the interpret digits option is turned on.
Translate with Prefix
Specifies whether the translate with prefix option is turned on.
Set Master
Specifies whether a host is a master or not.
Custom Applications
Specifies whether the custom application feature is enabled or disabled.
Synchronizing Switch Timing
Specifies the time reference used for synchronization.
Synchronizing Clocks on Redundant Hosts
Specifies how to synchronize clocks on the master and standby hosts.
NOTES: 1. Most of the procedures in this section are usually performed only once during setup and they are global settings. Before changing any of these settings, contact Lucent Technologies Technical Support. 2. If, while performing any of the additional options, you are unable to access host.cfg, check the permissions of the file. (See â&#x20AC;&#x153;UNIX Permissionsâ&#x20AC;? on page E-12.) If you do not have write permission, change the permissions by accessing /isos/usr/bin and typing: chmod u+w <host.cfg>
3-11
Using the Outbound Translation Option
Procedure 12
EXS ExchangePlus Software Operations Guide
Using the Outbound Translation Option This procedure indicates whether or not an outbound translation may be performed. Enabling the option allows you to perform a second translation on the called number if the partition of the outbound trunk group is different than the partition of the inbound trunk group. 1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-5.
Figure 3-5 A sample host.cfg file
4. To set the outbound translation option, edit the following line in the host.cfg file: OUTBOUNDTRANSLATION=
3-12
EXS ExchangePlus Software Operations Guide
Using the Outbound Translation Option
Enter the appropriate value for the OUTBOUNDTRANSLATION flag. The possible options are listed below: Value
Description
0 (Default)
There is no outbound translation.
1
A translation is performed on the called number if the partition of the outgoing trunk group is different than the partition of the incoming trunk group.
2
A second translation is performed on the called number (after it has already been translated via the DNIS Translation table) if the partition of the outgoing trunk group is different than the partition of the incoming trunk group.
5. Save the file.
3-13
Using the Interpret Digits Option
Procedure 13
EXS ExchangePlus Software Operations Guide
Using the Interpret Digits Option This procedure indicates how to set the interpret digits option. NOTE: This option can only be used in North America. Do not use the INTERPRETDIGS flag in international systems. This option allows the system to analyze the digits in the dialed number and determine the type of the call as: • • • •
an international operator call (01+) an international call (011+) a national operator call (0+) a national call (1+)
The call type information will be stored in the Nature of Address field and the incoming Call Type field. The system then “normalizes” the dialed number, by stripping the prefix from the number and storing the resulting number as the called number. The system normalizes the numbers so that dialed numbers coming in either inband (which may have prefixes) or via SS7 (which usually do not have prefixes) look the same when they are used as input for the DNIS Translation table. For example: Suppose the Interpret Digits option is turned on. If a call comes in from partition 0 with a dialed number is 0115088621234, the system looks at the number and determines that it is an international call. It sets the Nature of Address field and incoming Call Type field to international and then strips the 011 from the number and saves it in the Called Number. The number 5088621234 is used as input for the DNIS Translation table.
Requirements
Steps
In order to use this function, INTERPRETDIGS (a system parameter) must be set to 1 in host.cfg. 1.
Open a terminal window and go to /usr/isos.
2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-6.
3-14
EXS ExchangePlus Software Operations Guide
Using the Interpret Digits Option
Figure 3-6 A sample host.cfg file
4. To set the interpret digits option, edit the following line in the host.cfg file: INTERPRETDIGS=
Enter the appropriate value for the INTERPRETDIGS flag. The possible options are listed below: Value
Description
0 (Default)
Interpret digits option is turned off. The system does not attempt to interpret the incoming digits as described in this section.
1
Interpret digits option is turned on. The system will attempt to analyze the incoming digits (dialed number) and determine the type of call that is being made based on those digits. It will save the call type in the Nature of Address and Call Type fields and then strip the 01, 011, 1, or 0 prefixes from the dialed number. The results will be stored in the Called Number. The Called Number will be used as input for the DNIS Translation table.
5. Save the file.
3-15
Using the Translate with Prefix Option
Procedure 14
EXS ExchangePlus Software Operations Guide
Using the Translate with Prefix Option This procedure specifies how to set the Translate with Prefix option. This option indicates whether or not to translate the called number with a prefix. NOTE: This option can only be used in North America. Do not use the TRANSLATEWITHPREFIX flag in international systems. This flag is often used in conjunction with the INTERPRETDIGS flag. If INTERPRETDIGS and TRANSLATEWITHPREFIX are turned On (set to 1), the system looks at the Nature of Address field and incoming Call Type field and determines the call type. It then appends the appropriate prefix to the Called Number before the number is used as input to the DNIS Translation table. For example: Suppose the TRANSLATEWITHPREFIX option is turned on. If a call comes in from partition 0 with a called number that is 5088621234 and the Nature of Address and incoming Call Type fields indicate that the call is an international call, then the system appends the prefix 011 to the Called Number before it inputs the number into the DNIS Translation table.
Steps
1.
Open a terminal window and go to /usr/isos.
2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-7.
Figure 3-7 A sample host.cfg file
3-16
EXS ExchangePlus Software Operations Guide
Using the Translate with Prefix Option
4. To set the translate with prefix option, edit the following line in the host.cfg file: TRANSLATEWITHPREFIX=
Enter the appropriate value for the TRANSLATEWITHPREFIX flag. The possible options are listed below: Value
Description
0 (Default)
Translate with Prefix option is turned off. The system does not attempt to add prefixes based on Nature of Address and Call Type fields as described in this section.
1
Translate with Prefix option is turned on. A prefix (either 011 for international calls or 1 for national calls) will be added to the called number before it is used as input into the DNIS Translation table.
5. Save the file.
3-17
Selecting the Master Host
Procedure 15
EXS ExchangePlus Software Operations Guide
Selecting the Master Host This procedure allows you to specify whether a host is a master or standby. It should only be used on a non-redundant system. It prevents the redundancy process from running when it is not required. The default setting is that the host is not a master (SETTOMASTER=0).
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to the following file (Figure 3-8).
Figure 3-8 A sample host.cfg file
3-18
EXS ExchangePlus Software Operations Guide
Selecting the Master Host
4. To specify whether or not a host is a master, edit the following line in the host.cfg file: SETTOMASTER=
Enter the appropriate value for the SETTOMASTER flag. The possible options are listed below: Value
Description
0 (Default)
0 should be used for a redundant host system. It indicates that the hosts will arbitrate to determine which one will be the master.
1
1 should be used for a single host system.
5. Save the file.
3-19
Disabling the Custom Application Feature
Procedure 16
EXS ExchangePlus Software Operations Guide
Disabling the Custom Application Feature This procedure specifies how to disable the custom application feature. By default the feature is automatically enabled. The custom application feature allows you to load and use custom applications that have been developed by Lucent Technologies. To disable the custom application feature, you set the ENABLECUSTOMAPP flag in the host.cfg file to 0.
Steps
1.
Open a terminal window and go to /usr/isos.
2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 3-9.
Figure 3-9 A sample host.cfg file
4. To disable the custom application feature, edit the following line in the host.cfg file: ENABLECUSTOMAPP=
3-20
EXS ExchangePlus Software Operations Guide
Disabling the Custom Application Feature
Enter the appropriate value for the ENABLECUSTOMAPP flag. The possible options are listed below: Value
Description
0
Disables the custom application feature to prevent you from use any of the custom applications developed by Lucent Technologies.
1 (Default)
Enables the custom application feature. See Chapter 7 for more information on using Custom Applications.
5. Save the file.
3-21
Synchronizing Switch Timing
Procedure 17
EXS ExchangePlus Software Operations Guide
Synchronizing Switch Timing This procedure describes how to set up the synchronization priority list. This list prioritizes the order in which the switch selects a synchronization clock source. The synchronization clock source synchronizes the incoming T1, E1, and J1 spans in the switch. Failure to select a proper clock source may result in “frame slips” and high data rate error rates. Synchronization is in the following forms: •
Reference Timing Generated by an external clock source to the EX/CPU card through the EX/CPU I/O. The sources must be all ones. The EX/CPU I/O must be the correct module number to support the clock speed you want to connect to. You must have a clock SIMM on the EX/CPU card for reference timing. Clock SIMMs are available for T1 (1.544 Mbs), E1 (2.048 Mbs), or J1 (64 Kbs).
•
Loop Timing Synchronize the system to an incoming T1, E1, and J1 span. When using loop timing, first designate which span you want to use to extrapolate the clock. You must designate the span to use before you set the priority list of the clock sources.
•
Free Running Based on the internal clock source of 2.048 Mbs. Use this option only for test environments; not for network operations.
The default synchronization prioritizes as follows: 1. External Reference Clock 1 (Primary) 2. External Reference Clock 2 (Secondary) 3. Loop Timing 1 (Primary) 4. Loop Timing 2 (Secondary) 5. Free Running clock (Internal) The switch continuously monitors all synchronization clock sources and uses the highest priority clock source currently available. For example, if you use the default configuration, the switch checks for availability of the first priority source (External Reference Clock). If this is not available, the switch continues to check each clock source, one after the other, until it finds an available source. The switch automatically changes synchronization priority when a higher priority source becomes available.
3-22
EXS ExchangePlus Software Operations Guide
Steps
Synchronizing Switch Timing
The following procedure describes how to synchronize switch timing. There are two major steps to this procedure: 1. Specify the synchronization priority list. 2. Specify the spans that will be used for Primary and Secondary Loop Timing (if you are going to use that type of timing).
Specifying Priority of Clock Sources
Use this procedure to specify the priority list of the clock sources. The switch will attempt to use the highest priority clock source (Priority 1). If that clock source is not available, it will attempt to use the next highest priority clock source, and so on. If the switch is using a lower priority clock source and a higher priority one becomes available, it will automatically switch to use the highest priority clock source available. 1. Pull down the Maint menu and select Set Sync Priority. The Sync Priority window appears (Figure 3-10).
Figure 3-10 Sync Priority Window
2. Select a clock source from each of the drop-down text boxes labeled Priority 1 through Priority 5. Your choices will be: • • • • •
Primary Reference Secondary Reference Primary Loop Secondary Loop Free Running
You may only use each selection once. Figure 3-10 shows the default priority list, but you arrange the list in any order. 3. Click Apply to save your selections.
3-23
Synchronizing Switch Timing
Specifying Spans for Loop Timing
EXS ExchangePlus Software Operations Guide
Use this procedure to set up both the Primary and Secondary Loop Timing clock sources. Complete steps 1-3 for each source (primary and secondary). 1. Pull down the Maint menu and select Set Loop Timing. The Set Loop Timing Resources window appears (Figure 3-11). You will use this window to set up both the Primary Loop Timing clock source and the Secondary Loop Timing clock source.
Figure 3-11 Set Loop Timing Resources Window
2. The following table lists the fields on the window that you need to complete: Value
Description
Slot
From the drop-down text box, select the physical slot containing the T1, E1, or J1 card that will be used as the loop timing clock source (either primary or secondary) that you are specifying.
Span
Enter the Span from which you will get the clock. Span numbers are zero-based.
Loop Timing Type
Specify whether the span you entered in the Span field is the Primary Loop Timing source or the Secondary Loop Timing source.
Loop Timing Action
Specify whether you are turning loop timing on (Set) or off (Clear).
3. Click Apply. 4. Repeat this procedure to set up an additional Loop Timing clock source.
3-24
EXS ExchangePlus Software Operations Guide
Procedure 18
Synchronizing Clocks on Redundant Hosts
Synchronizing Clocks on Redundant Hosts In ExchangePlus systems with redundant hosts, it is imperative that hosts maintain clock synchronization. This procedure describes how to configure one or both hosts to synchronize their system clock to an external reference. The following files are assumed to be pre-installed during the factory installation of ExchangePlus. These files are included as part of the ExchangePlus installation. •
/etc/timeservers
•
/usr/bin/synctime
There are two ways to synchronize clocks: •
Synchronizing both hosts to one precision external time standard
•
Synchronizing one host to the other. In this case the hosts are synchronized from the standard internal clock of one of the hosts.
The following procedures describe how to synchronize the clocks in either of these two ways:
Synchronizing to an External Time Standard
Follow this procedure on both hosts. 1. Use the su command to become the root user. 2. Edit the file /etc/timeservers using a text editor such as vi. This file should contain one or more IP addresses of time reference systems. The reference system should be set to either a standard Internet time reference or an internal time reference on the customer site that is referenced to a standard time source. By default, there are IP addresses in the file for two Internet-based standard time systems: •
IP1: tick.uh.edu (University of Houston)
•
IP2: navobs1.wust1.edu (U.S. Naval Observatory, USNO)
You can choose to use the default references or choose one or more of your own reference systems. The system will synchronize from the first available system in the list (for example, IP1). 3. Save the file and close vi. 4. Use the su command to become the root user. 5. Save the current crontab for the root to a temporary file by typing: crontab -l > newroot.dat
3-25
Synchronizing Clocks on Redundant Hosts
EXS ExchangePlus Software Operations Guide
6. Use a text editor, such as vi, to add a line similar to the following as the last line of the newroot.dat file: 0 23 * * */usr/bin/synctime >> /usr/adm/synctime.log
This line sets up a cron job to be performed daily at 11:00 pm. 7. Save the file and close vi. 8. Register the newroot.dat as the new crontab by typing: crontab newroot.dat
9. Use the exit command to exit out of the root user mode.
Synchronizing One Host to the Other
In this case, one host will be synchronized to the other. You choose one host to be the â&#x20AC;&#x153;master clock.â&#x20AC;? Typically you would choose your primary host to be the master clock. It will use its own standard internal clock. The other (secondary) host is synchronized to the master clock in the primary host. On the secondary host, perform the following: 1. Use the su command to become the root user. 2. Edit the file /etc/timeservers using a text editor such as vi. This file should contain one or more IP addresses of time reference systems. The reference system should be set to the IP address of primary host (the one with the master clock). 3. Save the file and close vi. 4. Save the current crontab for the root to a temporary file by typing: crontab -l > newroot.dat
5. Use a text editor, such as vi, to add a line similar to the following as the last line of the newroot.dat file: 0 23 * * */usr/bin/synctime >> /usr/adm/synctime.log
This line sets up a cron job to be performed daily at 11:00 pm. 6. Save the file and close vi. 7. Register the newroot.dat as the new crontab by typing: crontab newroot.dat
8. Use the exit command to exit out of the root user mode.
3-26
EXS ExchangePlus Software Operations Guide
Overview
4 Redundant Hosts Overview This chapter describes how redundant hosts operate and provides associated procedures. Procedure Name
Page
Procedure 19 Setting up Redundant Hosts
4-2
Procedure 20 Saving Configuration Files on Redundant Hosts
4-6
Procedure 21 Master and Standby Database Synchronization
4-7
Procedure 22 Forcing Switchover between Hosts
4-8
Procedure 23 Upgrading Software on Redundant Hosts
4-9
If you have redundant hosts, it means that you have two computers running ExchangePlus software. One host is considered to be the master and the other host is the standby. All call states, channel states, status changes, and CDRs are reported to the master host. The standby host monitors the master host in real-time. If the master host fails, then the standby host will become the master host and continue to process calls. During a switchover from the master host to the standby host, all active calls will not be affected, but calls in setup mode may be affected. The master host communicates with the master matrix cards and the standby host communicates with the standby matrix cards. There is a swtchcom process running on each host for each node. The two hosts also communicate with each other via the Ethernet. For example, if you have redundant hosts and three nodes (switches), the master host has swtchcom0, swtchcom1, and swtchcom2 processes running. This means that: Swtchcom0 on the master host communicates with the master matrix card on node1, swtchcom1 on the master host communicates with the master matrix card on node2, and swtchcom2 on the master host communicates with the master matrix card on node3. The same arrangement applies to the standby. Swtchcom0 on the standby host communicates with the standby matrix card on node1, etc.
4-1
Setting up Redundant Hosts
Procedure 19
EXS ExchangePlus Software Operations Guide
Setting up Redundant Hosts This procedure describes how to set up redundant hosts.
Assumptions
ExchangePlus software has been loaded on both hosts. In this procedure, it is assumed that the host names are LucentOne and LucentTwo and you are logged into LucentOne as the master host.
Steps
1. Access the command line on the host LucentOne through Exceed to set up the master host. 2. Go to the /etc/inet directory and verify that the hosts file has the IP address and the name of the adjacent host system. An example of the hosts file for LucentOne is: 217.21.21.175
LucentTwo
3. Save the file if necessary. 4. Next, go to the /usr/isos/bin directory. 5. Edit the startup file by typing: vi startup
6. Scan through the file and find the line that begins with nohup testredu
7. Make sure that line is not commented out with a # symbol. The word after testredu is the name of the adjacent host such as LucentTwo is listed in the following example: nohup testredu LucentTwo > ../log/system.log 2>&1
8. Save the file. 9. Edit the redu.cfg file by typing: vi redu.cfg
Redu.cfg is the redundant manager configuration file.
4-2
EXS ExchangePlus Software Operations Guide
Setting up Redundant Hosts
10. Set the ADJACENTHOST variable to the name of the adjacent host such as LucentTwo is listed in the following example: ERRLOG=redu.err DBGLOG=redu.dbg DBGLEVEL=0 ERRLEVEL=0 LOGERROR=1 LOGDEBUG=0 ADJACENTHOST=LucentTwo
11. Save the file. 12. Edit the copydb file by typing: vi copydb
Copydb copies over all configuration files such as board.cfg, switch.cfg, and database files to the standby host from the master host. 13. Verify that the name listed after the rcp command on each line is the name of the adjacent host. The following is an example of the copydb file: rcp rcp rcp rcp
-p -p -p -p
LucentTwo:/usr/isos/bin/*.dbf . LucentTwo:/usr/isos/bin/*.cdx . LucentTwo:/usr/isos/bin/switch.cfg . LucentTwo:/usr/isos/bin/board.cfg .
14. Save this file. 15. Access the /usr/isos directory. Edit the .rhosts file by typing: vi .rhosts
Add the name of the adjacent host to this file. LucentTwo
The .rhosts is a file which lists the computers that are given remote access permissions to the local computer. 16. Save this file. 17. Edit the switch.cfg file by typing: vi switch.cfg
Look for the SWITCHAPPTABLE section of the file and ensure that the following line is included: redu redu.cfg, redundancy mgr, 0, 0
18. Save this file. 19. Access the command line on the adjacent host LucentTwo through Exceed to set up the standby host. 4-3
Setting up Redundant Hosts
EXS ExchangePlus Software Operations Guide
20. Go to the /etc/inet directory and verify that the hosts file has the IP address and the name of the adjacent host system. An example for LucentTwo is: 217.21.21.121
LucentOne
21. Next go to the /usr/isos/bin directory. 22. Edit the startup file by typing: vi startup
23. Scan through the file and find the line that begins with nohup testredu
24. Make sure that line is not commented out with a # symbol. The word after testredu is the name of the adjacent host such as LucentOne is listed in the following example: nohup testredu LucentOne > ../log/system.log 2>&1
25. Edit the redu.cfg file by typing: vi redu.cfg
Redu.cfg is the redundant manager configuration file. 26. Set the ADJACENTHOST variable to the name of the adjacent host such as LucentOne is listed in the following example: ERRLOG=redu.err DBGLOG=redu.dbg DBGLEVEL=0 ERRLEVEL=0 LOGERROR=1 LOGDEBUG=0 ADJACENTHOST=LucentOne
27. Save the file. 28. Edit the copydb file by typing: vi copydb
Copydb copies over all configuration files such as board.cfg, switch.cfg, and database files to the standby host from the master host. 29. Verify that the name listed after the rcp command on each line is the name of the adjacent host. The following is an example of the copydb file: rcp rcp rcp rcp
30. Save this file. 4-4
-p -p -p -p
LucentOne:/usr/isos/bin/*.dbf . LucentOne:/usr/isos/bin/*.cdx . LucentOne:/usr/isos/bin/switch.cfg . LucentOne:/usr/isos/bin/board.cfg .
EXS ExchangePlus Software Operations Guide
Setting up Redundant Hosts
31. Access the /usr/isos directory. Edit the .rhosts file by typing: vi .rhosts
Add the name of the adjacent host to this file. LucentOne
The .rhosts is a file which lists the computers that are given remote access permissions to the local computer. 32. Save this file. 33. Edit the switch.cfg file by typing: vi switch.cfg
Look for the SWITCHAPPTABLE section of the file and ensure that the following line is included: redu redu.cfg, redundancy mgr, 0, 0
34. Save this file.
4-5
Saving Configuration Files on Redundant Hosts
Procedure 20
EXS ExchangePlus Software Operations Guide
Saving Configuration Files on Redundant Hosts This procedure describes how to save new configuration files that are only resident on the master host to the standby host.
Assumptions
LucentOne is the master host and LucentTwo is the standby host. This procedure assumes you have used xmenu to change configuration files and save them to board.cfg and switch.cfg. For instructions on how to save switch.cfg, see Procedure 47 Saving Configuration Changes via xmenu on page 6-65. To save board.cfg, pull down the Systems menu and select Save Slot Config.
Steps
1. Go to the command line on the master host LucentOne. 2. Go to /usr/isos/bin by typing: cd /usr/isos/bin
Copy the board.cfg files and switch.cfg files to the standby host as follows: rcp -p switch.cfg LucentTwo:/usr/isos/bin/ rcp -p board.cfg LucentTwo:/usr/isos/bin/
4-6
EXS ExchangePlus Software Operations Guide
Procedure 21
Master and Standby Database Synchronization
Master and Standby Database Synchronization Once the master and standby hosts have been brought up and the system is operational, any changes to active memory in the master are written to the database. These changes are also written across to the standby hostâ&#x20AC;&#x2122;s database. The database files in both hosts should always be the same. If synchronization is lost for any reason (for example, a card configuration does not load properly) then the database files in the master and standby hosts must be resynchronized. To do this, perform the following steps: 1. Enter the /usr/isos/bin directory on the standby host by typing: cd /usr/isos/bin
2. Stop all processes on the standby host with this command: stopit
3. The cron job checks once each minute to verify whether the host is running. Within a minute of the stopit command, the cron job will restart the host. When the standby has been restarted, all changes that have been made in the master are downloaded to the standby. The two hosts should then be synchronized. To verify that the hosts are synchronized: 1. Select Database>Export Tables from xmenu on both hosts to save the configuration in switch.cfg. Save the file to another name, such as switch.xpt in order to preserve your original switch.cfg file. 2. Copy the switch.xpt file on the master to a temporary directory on the standby host using the following command: rcp -p switch.xpt <hostname>:/tmp
3. Run the sdiff utility to perform a line-by-line comparison of the master host switch.xpt file and the switch.xpt file resident in the standby. Use the -s option for large files, since it suppresses the printing of identical lines and therefore reduces output. Type: sdiff -s <filename><filename2>
The sdiff command will print the two files side by side, marking any differences. The greater than symbol (>) marks a line that appears only in the second file. The less than symbol (<) marks a line that appears only in the first file. And the pipe symbol (|) | marks lines that appear in both files but are different. You can also use the diff utility, although the results will not be as specific for comparison. If there are differences between the files, you must restart the standby host. If cron is operating, LucentOne will be restarted automatically.
4-7
Forcing Switchover between Hosts
Procedure 22
EXS ExchangePlus Software Operations Guide
Forcing Switchover between Hosts This procedure describes how to force a switchover from the master host to the standby host.
Assumptions Steps
LucentOne is the master host and LucentTwo is the standby host. 1. Verify that the adjacent host LucentTwo is operating as standby. 2. From the main menu on the master host LucentOne, pull down the System menu and select the Terminate Host Control. LucentOne will go into a down state. The standby host, LucentTwo, will automatically become master. 3. To bring LucentOne back into service as a standby, on the main menu of From LucentOne, pull down the System menu and select Start Host Control. Choose 0 in the Start Level field.
4-8
EXS ExchangePlus Software Operations Guide
Procedure 23
Upgrading Software on Redundant Hosts
Upgrading Software on Redundant Hosts This procedure describes how to upgrade the software on redundant hosts.
Assumptions
This procedure assumes you know UNIX and are familiar with the ExchangePlus software. LucentOne is the master host and LucentTwo is the standby host. The following are high-level steps for upgrading software on redundant hosts and should be done solely by Lucent Technologies personnel. This procedure goes through upgrading the standby host first to the new software revision and then taking down the master host. This action forces a switchover to the new software located on the standby host. Load the new software on the old master and then bring it up to the standby mode.
Steps
1. From the master host LucentOne, export the tables to get the latest switch configuration by pulling down the Database menu and selecting Export Tables. 2. Copy the new switch.cfg file to the standby host LucentTwo. 3. On LucentTwo, make copies of the files menu, xmenu, host, and swtchcom to names such as menu.bak, xmenu.bak, host.bak, and swtchcom.bak. 4.
Stop LucentTwo.
5. Extract the upgrade software on the LucentTwo by typing: tar -xvf <<tar filename>>
6. Start LucentTwo with the upgrade software. 7. On LucentOne, make copies of the files menu, xmenu, host, and swtchcom to names such as menu.bak, xmenu.bak, host.bak, and swtchcom.bak. 8. Stop LucentOne. LucentTwo should become master. 9. Check that traffic is going through properly on the master host, LucentTwo. 10. Perform a remote copy to copy the upgrade files menu, xmenu, host, and swtchcom from LucentTwo to the adjacent host LucentOne by typing: rcp rcp rcp rcp
-p -p -p -p
LucentTwo:/usr/isos/bin/menu . LucentTwo:/usr/isos/bin/xmenu . LucentTwo:/usr/isos/bin/host . LucentTwo:/usr/isos/bin/swtchcom .
11. Start LucentOne with the upgrade software to bring it up to standby.
4-9
Upgrading Software on Redundant Hosts
4-10
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Introduction
5 Configuration Overview Introduction This chapter contains a list of the high-level tasks you may perform while configuring your ExchangePlus system. The detailed procedures required to complete configuration are provided in the remaining chapters of this guide. The following table lists the high-level tasks included in this chapter and the corresponding page number. Procedure Name
Page
Adding and Modifying New Connections
5-2
Deleting Connections
5-7
5-1
Introduction
EXS ExchangePlus Software Operations Guide
Adding and Modifying New Connections This procedure describes how to add or modify new connections regardless of the connection type (MF (multi-frequency), SS7 (signaling system 7), IDSN (Integrated Services Digital Network), etc.) It is possible that you may only need to perform a subset of these steps depending on the function you are trying to perform. For example, if you are adding a completely new carrier (such as MCI or Sprint), you should step through this entire procedure. If you are adding another span to increase the capacity, you need to add the span and define new trunks in the trunk group, but you do not have to define new routing. This procedure helps guide you from start to finish. If you are adding an SS7, ISDN, or E1R2 connection, the procedure is the same except you perform some additional configuration steps.
Assumptions
There are spans available to be configured.
Requirements
Before you can add a connection you need to define the following: • • • • • • • • • • • • • •
The type of circuit to be used (T1, E1). If you are using an existing span, specify the span number. The location of the span (node number, card number, span number) The direction of the circuit (inbound, outbound, or bi-directional) The format of the spans (Coding, Framing, Error Checking, Hunting type, Point Codes, etc.) The type of signaling being used (MF, SS7,. ISDN, etc.) The point codes, network indicators, type of switch at each end, type of interface The type of termination services (national, international) The numbering plan (to help specify translations required) The trunk groups and their associated attributes (type, flag, search type, etc.) The channel assignments including trunk group number, timeslot, channel (trunk number) and type (CIC, Framing, voice, signaling, etc) If the span uses SS7 signaling, identify CIC groups, Stack, Link Set, Links, Routes, and Timers If the span uses ISDN, identify D channels, backup D channels, D channel attributes and facilities, B channels, and B channel attributes Identify DSX Assignments Determine if your system will use outbound translation, interpret digits, translation with prefix flags, and ANI screening.
It is recommended that prior to adding new connections, you update your network diagram with the new connection.
5-2
EXS ExchangePlus Software Operations Guide
Introduction
For example, if you were going to add an SS7 connection between Boston and Dallas, you may add the following to your network diagram (Figure 5-1):
Boston 3-1-2 Route1
Node 1, Span 2, Trunk Group 2 (ANSI) CIC 401-423, Stack 1, Signaling LInk 4, Link Set 4
Dallas 3-1-3 Route 5
Figure 5-1 Example of a New Connection
Steps
1. If your system is set up to use the Outbound Translation, Interpret Digits, or Translate with Prefix flags, verify that they have been set correctly in the host.cfg file. See Setting up Call Detail Record Parameters on page 3-6. 2. Configure span(s) to be used for new connection(s), if they have not already been configured. See Procedure 24 Adding or Changing a T1 Span on page 6-3 or Procedure 25 Adding or Changing an E1 Span on page 6-6. When you finish configuring a new span, it will be automatically brought into service if it is configured correctly. 3. Add or modify trunk groups, as necessary. Be sure to specify trunk type, trunk flag, search pattern, and partition. See Procedure 27 Adding or Changing Trunk Groups on page 6-12. 4. Add trunks to any newly created trunk groups, as necessary. See Procedure 31 Adding Trunks to Trunk Groups on page 6-23. If the connections use SS7 signaling, you need to specify the starting CIC number and the CIC increment. As with spans, the trunks are automatically brought into service if the configuration is correct (unless they are SS7 or ISDN connections). 5. Add or modify the route list, as necessary. Be sure to specify routing for the trunk groups you added in the previous step. To add or modify the routing list, see Procedure 29 Adding or Changing Routes on page 6-17). 6. Add or modify the Exception table, if exceptions are used for routing. Be sure to define exceptions for the partitions you have defined that require exceptions. To add or modify exceptions, see Procedure 38 Adding and Changing Exception Tables on page 6-50. 7. Add or modify the Announcement table, if announcements are used for routing. To add or modify announcements, see Procedure 40 Adding or Changing Announcements on page 6-54.
5-3
Introduction
EXS ExchangePlus Software Operations Guide
8. Add or modify the Time of Day or Day of Week tables if those features will be used for routing. If you are using Time of Day Routing, see Procedure 43 Configuring Time of Day (TOD) Routes on page 6-58. If you are using Day of Week routing see Procedure 45 Configuring Day of Week (DOW) Routes on page 6-62. 9. Add or modify ANI screening, as necessary, on the ANI table. Be sure to define translations for each of the partitions you have defined. See Procedure 33 Adding or Changing ANI Tables on page 6-26. 10. Add or modify dialed number translations, as necessary, on the DNIS Translation table. Be sure to define translations for each of the partitions you have defined. See Procedure 35 Adding or Changing DNIS Translations on page 6-32). 11. SS7 Only: If the new connection uses SS7, configure SS7 as described in Procedure 52 Setting up a Span to use SS7 Signaling on page 7-2. When the CICs are configured, the SS7 connections are automatically brought into service. 12. ISDN Only: If the new connection uses ISDN, configure ISDN as described in Procedure 53 Setting up a Span to use ISDN Signaling on page 7-25. When the B channels are configured, the ISDN connections are automatically brought into service. 13. E1R2 Only: If the new procedure uses E1R2, configure E1 R2 as described in Procedure 54 Setting up an E1 Span to use E1R2 Signaling on page 7-44 14. Save the configuration. All changes that have been made to the configuration are automatically saved to the database files as the changes are being made via xmenu. However, once the configuration of a new connection is completed, save the updated configuration to the switch.cfg file using the Database>Export Tables menu selection. Doing so allows you to recover your configuration changes in the event of a loss of the database files. See Procedure 47 Saving Configuration Changes via xmenu on page 6-65 for detailed instructions on saving the configuration.
5-4
EXS ExchangePlus Software Operations Guide
Introduction
15. To verify that the configuration has been entered correctly, you can view the entire configuration file (in /usr/isos/bin/switch.cfg) by using a text editor, such as vi. When reviewing the configuration, be sure to look at: • • • • • • • • • • • •
Spans Trunk Groups Route List Exception table Announcement table Time of Day table ANI table Day of Week table DNIS Translation table SS7 configuration (if configured) ISDN configuration (if configured) E1R2 configuration (if configured)
to insure that no mistakes were made during configuration. 16. If the configuration is correct, the spans and trunks will have been brought into service automatically as they were added. To verify the spans are activated, check Span Status as described in Procedure 60 Checking Span Status on page 9-2. All trunks should be Activated as shown in Figure 5-2.
Figure 5-2 Span Status Showing Spans are in Service
To verify channel (trunk) status, check Channel Status, as described in Procedure 62 Checking Channel Status on page 9-4. All channels should be Idle as shown in Figure 5-3.
5-5
Introduction
EXS ExchangePlus Software Operations Guide
Figure 5-3 Channel Status Showing Channels are in Service
SS7 Only: If this is an SS7 connection, check Link Status, as described in Procedure 71 Checking Link Status on page 9-13. All links should be Available and will list the span and channel being used (Figure 5-4).
Figure 5-4 Link Status Showing SS7 Links are in Service
ISDN Only: If this is an ISDN connection, check D channel status, as described in Procedure 62 Checking Channel Status on page 9-4. All channels should be Idle as shown in Figure 5-3. You should check the D channels being used. If the status of any of these items is not as described above, see Chapter 14 â&#x20AC;&#x153;Maintenance and Troubleshootingâ&#x20AC;? on page 14-1. 17. If status of all the items are as described in the previous step, the connection is up and should be able to pass traffic.
5-6
EXS ExchangePlus Software Operations Guide
Introduction
Deleting Connections This procedure describes how to delete connection regardless of the connection type. This procedure helps guide you from start (taking the physical connection out of service) to removing the trunks, trunk groups, CIC (if SS7) and D and B channels (if ISDN).
Assumptions Steps
You are not passing traffic on the connections to be deleted. 1. Take spans out of service. See Procedure 104 Taking a Span Out of Service (OOS) on page 14-14. If you check the span status, it should be reported as out of service. 2. Take channels out of service. See Procedure 105 Taking Trunks Out of Service on page 14-15. If you check the channel status, it should be reported as out of service. 3. Remove the trunks from the configuration. See Procedure 32 Deleting Trunks from Trunk Groups on page 6-25. 4. Remove all other information from the configuration that is no longer used such as trunk groups, route list entries, DNIS translations. If you do not remove these items, they will not affect your system operation unless you accidentally attempt to use them. See Chapter 6 “Configuration Procedures” on page 6-1. 5. Remove CICs (SS7 only). See “Deleting CICs” on page 7-19. 6. Remove D and B channels (ISDN only). See See “Deleting D Channels” on page 7-28. and “Deleting B Channel Groups” on page 40.
5-7
Introduction
5-8
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
6 Configuration Procedures Overview This chapter describes configuration procedures that you may need to perform in order to keep your network configuration up to date. The procedures described in this chapter assume that your switches and host(s) have been installed by Lucent Technologies and that there is a basic configuration in place. These procedures explain how to make additions, changes, and deletions from an existing configuration. Refer to the ExchangePlus call flow on page 1-3 for more information about how calls are routed through the system.
Caution
To insure that you do not lose data in the event of a failure, you should save your configuration anytime you make changes to it. To save the configuration, see Procedure 47 Saving Configuration Changes via xmenu on page 6-65.
Caution
When you are adding data to tables, be sure not to save a table that contains empty rows. Doing so may cause a core dump. If this happens, restart xmenu and resume your work.
The following lists the procedures and the corresponding page number. Procedure Name
Page
Procedure 24 Adding or Changing a T1 Span
6-3
Procedure 25 Adding or Changing an E1 Span
6-6
Procedure 26 Adding or Changing DSP Resources
6-9
Procedure 27 Adding or Changing Trunk Groups
6-12
Procedure 28 Deleting Trunk Groups
6-16
Procedure 29 Adding or Changing Routes
6-17
Procedure 30 Deleting Routes
6-22
Procedure 31 Adding Trunks to Trunk Groups
6-23
6-1
Overview
6-2
EXS ExchangePlus Software Operations Guide
Procedure Name
Page
Procedure 32 Deleting Trunks from Trunk Groups
6-25
Procedure 33 Adding or Changing ANI Tables
6-26
Procedure 34 Deleting ANI Entries
6-31
Procedure 35 Adding or Changing DNIS Translations
6-32
Procedure 36 Sorting Entries in DNIS Translation Table
6-48
Procedure 37 Deleting DNIS Translations
6-49
Procedure 38 Adding and Changing Exception Tables
6-50
Procedure 39 Deleting Exceptions
6-53
Procedure 40 Adding or Changing Announcements
6-54
Procedure 41 Deleting Announcements
6-56
Procedure 42 Downloading Announcements
6-57
Procedure 43 Configuring Time of Day (TOD) Routes
6-58
Procedure 44 Deleting Time of Day Routes
6-61
Procedure 45 Configuring Day of Week (DOW) Routes
6-62
Procedure 46 Deleting Day of Week Routes
6-64
Procedure 48 Making Configuration Changes via UNIX
6-68
Procedure 47 Saving Configuration Changes via xmenu
6-65
Procedure 49 Saving Configuration Changes via UNIX
6-71
Procedure 50 Printing the Configuration
6-72
Procedure 51 Rolling Over CDRs Manually
6-73
EXS ExchangePlus Software Operations Guide
Procedure 24
Adding or Changing a T1 Span
Adding or Changing a T1 Span This procedure describes how to add or change a T1 span.
Assumptions
•
If you are adding new spans, this procedure assumes that you have spans available on a line card that are not currently configured. If you need to add or swap a line card to add new spans, refer to the EXS ExchangePlus Hardware Installation and Operation Manual to install the hardware.
•
If you are adding new spans, you must determine the physical location (slot and span offset) within the card cage of an available span.
•
If you are changing an existing T1 span, you do not have to take the span out of service. Make the necessary changes and click Apply. The span is automatically taken out of service, updated, and automatically put back in service. Calls on that span will be interrupted during the update.
•
Before you can add a new span you need to know the format of the span. For example: bit framing, line coding, clear channel.
•
If the switch goes down due to a power failure, the switch will not reload the slot instructions. To avoid problems: • •
Steps
When creating initial configuration, assign all spans in sequential order, even if they are not being used. Configure unused spans for Clear Channel.
1. From the System menu, select Edit Slot Config. A drop-down menu appears listing the cards in each slot of the switch. 2. Select the slot containing the T1 Span you want to add or change. The Line Card Configuration window appears (Figure 6-1).
6-3
Adding or Changing a T1 Span
EXS ExchangePlus Software Operations Guide
Figure 6-1 Line Card Configuration Window for T1 Card
NOTE: The values displayed in Figure 6-1 are typical defaults. 3. On the Line Card Configuration window, enter the Span ID. Spans are uniquely numbered within a system (which may go across more than one node). The spans on the first card on the first node should be numbered 1-16. Spans on second card on the first node might be 17-32, etc. Node 1 will contain spans 1-80, Node 2 will contain spans 81-160, etc. 4. Specify the format of the span by selecting values for the following parameters:
6-4
Parameter
Value
Description
Format: Bit Framing
D4 ESF
T-1 framing formats
Format: Line Coding
B7ZS B8ZS
Bit 7 zero suppressing Binary 8 Zero suppression
Format: Clear Channel
Yes No
Specifies the signaling method. If Yes, then the full bandwidth of the circuit is available for communications. If your span uses SS7 or ISDN, then select Yes for this parameter.
Line Length
000-133 feet 134-166 feet 167-299 feet 300-533 feet 534-655 feet G703 ITU-T (not used for T1)
Select the line length. This is the distance (in feet) between the switch and the last amplification stage (usually the compression equipment). Typically, you choose 000-133 feet for T1 and J1.
EXS ExchangePlus Software Operations Guide
Adding or Changing a T1 Span
5. Click Apply. When you select Apply, the span will be taken out of service, updated with the new configuration information, then brought back into service automatically. Any calls on that span will be interrupted. If this is an SS7 span, see Procedure 52 Setting up a Span to use SS7 Signaling on page 7-2. If this is an ISDN span, see Procedure 53 Setting up a Span to use ISDN Signaling on page 7-25.
6-5
Adding or Changing an E1 Span
Procedure 25
EXS ExchangePlus Software Operations Guide
Adding or Changing an E1 Span This procedure shows how to add or change an E1 span.
Assumptions
Steps
•
If you are adding new spans, this procedure assumes that you have spans available on a line card that are not currently configured. If you need to add or swap a line card to add new spans, refer to the EXS ExchangePlus Hardware Installation and Operation Manual to install the hardware.
•
If you are adding new spans, you must determine the physical location (slot and span offset) within the card cage of an available span.
•
If you are changing an existing E1 span, you do not have to take the span out of service. Make the necessary changes and click Apply. The span is automatically taken out of service, updated, and automatically put back in service. Calls on that span will be interrupted during the update.
•
Before you can add a new span you need to know the format of the span before you start. For example: line coding, error correction, and signaling.
•
If the switch goes down due to a power failure, the switch will not reload the slot instructions. To avoid problems: •
When creating initial configuration, assign all spans in sequential order, even if they are not being used.
•
Configure unused spans for Clear Channel.
1. From the System menu, select Edit Slot Config. A drop-down menu appears listing the cards in each slot of the switch. 2. Select the slot containing the E1 Span you want to add or change. The Line Card Configuration window appears (Figure 6-2).
6-6
EXS ExchangePlus Software Operations Guide
Adding or Changing an E1 Span
Figure 6-2 Line Card Configuration Window for E1 Card
NOTE: The values displayed in Figure 6-2 are typical defaults. 3. On the Line Card Configuration window, enter the Span ID. Spans are sequentially numbered within a system and may go across more than one node. The spans on the first card on the first node should be numbered 1-16. Spans on second card on the first node might be 17-32, etc. Node 1 will contain spans 1-80, Node 2 will contain spans 81-160, etc.
6-7
Adding or Changing an E1 Span
EXS ExchangePlus Software Operations Guide
4. Enter the format of the span by selecting values for the following parameters: Parameter
Value
Description
Format: Coding
AMI HDB3
Coding method Alternate Mark Inversion (AMI) or High-Density Bipolar Three-Bit Substitution (HDB3)
Format: CRC-4
No Yes
CRC-4 Error Correction Enabled
Format: FEBE
No Yes
FEBE (Far End Block Error) Enabled
Format: Clear Channel
No Yes
Specifies the signaling method. If Yes, then the full bandwidth of the circuit is available for communications. (Inband signaling is not used). If your span uses SS7 or ISDN, then select Yes for this parameter.
Format: Transmit All 0â&#x20AC;&#x2122;s
No Yes
Specify whether to format to transmit all zeros.
Format: Layer 1
E1 Euro-ISDN Austel-ISDN
Specify the format of Layer 1.
Line Length
000-133feet (not used for E1) 134-166 feet (not used for E1) 167-299 feet (not used for E1) 300-533 feet (not used for E1) 534-655 feet (not used for E1) G.703 ITU-T (not used for E1) 75 Ohm 120 Ohm
Select the line length. You should choose either 75 Ohm or 120 Ohm for E1, depending on the type of I/O card you have. Other choices are available, but should not be used.
SA Registers
Bit 4: Reset, Set Bit 5: Reset, Set Bit 6: Reset, Set Bit 7: Reset, Set Bit 8: Reset, Set
Select to set or reset the SA Registers for Bit 4, 5, 6, 7, and 8.
TS16 Register
SpareBitx1: Reset, Set SpareBitx3: Reset, Set SpareBitx4: Reset, Set
Set or reset the TS16 Register for SpareBitx1, SpareBitx3, SpareBitx4.
5. Click Apply. When you select Apply, the span will be taken out of service, updated with the new configuration information, then brought back into service automatically. Any calls on that span will be interrupted. If this is an SS7 span, see Procedure 52 Setting up a Span to use SS7 Signaling on page 7-2. If this is an ISDN span, see Procedure 53 Setting up a Span to use ISDN Signaling on page 7-25. 6-8
EXS ExchangePlus Software Operations Guide
Procedure 26
Adding or Changing DSP Resources
Adding or Changing DSP Resources This procedure shows how to add or change DSP resources. You can configure each DSP to perform any one of following functions DSP Function Type
Encoding Format Âľ-law
A-law
Tone Reception DTMF
0x01
0x03
MFR1
0x02
0x04
MFR2
0x06
0x05
CPA
0x08
E1 Dial Pulse
0x07 0x09
Energy Detection
0x0A
DTMF High Pass Filter
0x0C
0x0D
Tone Generation DTMF
0x10
0x11
MFR1
0x12
0x13
Bong Tone
0x1A
0X1B
MFR2 Forward
0x17
0x16
MFR2 Backward
0x19
0x18
CPT4
0x14
0x15
Conferencing Standard
0x1E
0x1F
Mixed
0x20
Monitor
0x21
Announcement Generation VRAS
0x1C
Only one function can be configured on each DSP. You must configure at least one DSP in the system for a function in order to make that function available to the system. Individual DSPs may be programmed without affecting other DSPs on the same SIMM. For detailed information on configuring DSPs, see Excel Switching Software Reference Manual, Version 5.3, Chapter 6.
Steps
1. From the System menu, select Edit Slot Config. A drop-down menu appears listing the cards in each slot of the switch. 2. Select the slot containing the DSP card (either the MFSDP or the DSP-ONE card) you want to add or change. The DSP Card Configuration window appears (Figure 6-3).
6-9
Adding or Changing DSP Resources
EXS ExchangePlus Software Operations Guide
Figure 6-3 DSP Card Configuration Window
3. On the DSP Card Configuration window, you specify the DSP resource to use on each SIMM (0-3) of each DSP (0-3). To change or add a DSP resource, click on the box of interest. For example: If you wanted to change or add a DSP resource on SIMM 1 of DSP 1, click on the box located in the second row and the second column labeled MFR1-G-u on Figure 6-3. 4. Clicking on any of the fields in the DSP Card Configuration window brings up the DSP Function Configuration window (see Figure 6-4).
6-10
EXS ExchangePlus Software Operations Guide
Adding or Changing DSP Resources
Figure 6-4 DSP Function Configuration Window
5. From this window choose the DSP resource you want to use for DSP/SIMM you selected. 6. When you have made your selection for a particular DSP, click Apply. You are returned to the DSP Card Configuration window. Apply commits the change immediately by downloading it to the switch. If you click OK instead of Apply, the changes are saved to memory, but are not downloaded to the switch. 7. If you want to make more changes to the DSP settings, click on the next DSP/SIMM box. Repeat steps 4-6. When you are done making changes to the DSP/SIMM settings, click Close on the DSP Card Configuration window.
6-11
Adding or Changing Trunk Groups
Procedure 27
EXS ExchangePlus Software Operations Guide
Adding or Changing Trunk Groups This procedure describes how to add and change trunk groups. A trunk group is a group of circuits that all have common signaling characteristics. The voice circuits of the switch are set up as a series of trunk groups. Each trunk group typically goes to a particular switch or carrier. The trunk group set up is used to determine the following attributes associated with a group of circuits. Trunk groups are then assigned to a span/channel as described in Procedure 31 Adding Trunks to Trunk Groups on page 6-23.
Steps
1. Pull down the Database menu and select Trunk Group Setup. The Trunk Group table appears (Figure 6-5). This table shows all the trunk groups that have been configured for a particular node.
Figure 6-5 Trunk Group Table
2. To add a new trunk group, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the values for the new trunk group on the new line or you can copy some or all of an existing trunk group definition from the table and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys, or the <Tab> key to move from field to field, as necessary. For example, if you copy the definition of trunk group 5 into a new line, you may want to change the trunk group number from 5 to something else, say 20. 6-12
EXS ExchangePlus Software Operations Guide
Adding or Changing Trunk Groups
6. To change an existing trunk group, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7. The following table lists the fields that you need to complete: Parameter
Value
Description
TG
integer
Trunk Group number.
NPA
3 digits
Area code (or country code) for filed ANIs.
NXX
3 digits
Exchange (or city code) for filed ANIs.
Line
4 digits
Last digits of a phone number.
OZZ
A routing code used in North American signaling. The default OZZ code used for equal access routing using North American signaling.
Car
integer
The carrier number.
Name
A text string (up to 8 characters)
A text field which identifies the trunk.
Type
See the Trunk Types table on page B-1.
The trunk type determines the physical characteristics of the trunk group and its direction.
Flag
See the Trunk Flag and Signaling Format tables starting on page B-3.
The type of signaling and any application defined flags.
SType
See the Search Type table starting on page 6-15.
The type of search pattern to use when looking for a nonbusy trunk when trying to route a call.
Part
0-9999
Specifies the partition assigned to this trunk group. The ANI table, DNIS Translation table can have up to 9999 partitions. The Exception table can each have up to 32 partitions. A partition is a subtable within the main table. By defining a particular partition for a trunk group, you are specifying a subtable within the main ANI table, DNIS Translation table, or the Exception table that this trunk group will use.
PPL
For trunk groups controlled by PPL, this is an index to PPLControl. It identifies the section of PPL Control to use to configure PPL controlled channels.
6-13
Adding or Changing Trunk Groups
EXS ExchangePlus Software Operations Guide
Parameter
Value
Description
COT
An integer 0=no continuity check
Controls how often a continuity check is performed on the outbound call. If you enter 0, there is no continuity check performed. If you enter a non-zero (n) number, then every nth call will perform a continuity check. For example, if COT=1, every outbound call to that trunk group will perform a continuity check. If COT=5, every 5th call will perform a continuity check.
Retry
6-14
integer
The number of re-attempts to make on SS7 trunks for a failed seizure. If the entry is greater than zero, it will retry one more time (just once) for SS7 ISUP COT failure. For other failures, it will not retry.
Min
Used for SS7 overlap sending/receiving configuration. Defines the minimum number of digits that ExchangePlus has to receive in order to route the call on the incoming trunk.
Max
Used for SS7 overlap sending/receiving configuration. Defines the maximum number of digits that ExchangePlus will receive before it can release the incoming call, when no outbound trunk can be found. If the call can be routed out based on received digits, this field has no effect. But, if the call cannot be routed based on received digits (because no translation is found, for example), ExchangePlus will not release the incoming call unless at least MAX number of digits have been received. If there are not enough digits, ExchangePlus will wait for more digits before routing the call.
Timeout
Used for SS7 overlap sending/receiving configuration. Defines the timeout values (in seconds) required before the call can be routed out. If the timer expires and the call is still not routed (either because the MIN digits were not received or the MAX digits have not been received, and there is no outbound trunk yet), then the call will be released.
Flag1
N/A
For use in a future release.
Flag2
N/A
For use in a future release.
EXS ExchangePlus Software Operations Guide
Adding or Changing Trunk Groups
The following is the search type table used in the trunk group definition. Search Types
Description
None (or no entry in the field)
The trunks (or CICs) will be searched in a â&#x20AC;&#x153;round robinâ&#x20AC;? fashion, starting at the first trunk and continuing through to the last trunk in the group. Each new search starts where it left off on the previous attempt.
Even
The even trunks are searched first, followed by a search for any free trunk if the search for even trunks fails. This helps eliminate glare conditions on two way trunks.
Odd
The odd trunks will be searched first, followed by a search for any free trunk if the search of odd trunks fails. This helps eliminate glare conditions on two way trunks.
ECIC (for SS7 only)
The even CICs will be searched first, followed by a search for any free CIC if the search for even CICs fails. This helps eliminate glare conditions on two way trunks.
OCIC (for SS7 only)
The odd CICs will be searched first, followed by a search for any free CIC if the search for odd CICs fails. This helps eliminate glare conditions on two way trunks.
HiLow
Search from the highest channel to the lowest channel.
LowHi
Search from the lowest channel to the highest channel.
Assign
The LNASSIGN table will be used to determine the offset within the trunk group (thus the channel) to be used to seize outbound.
ACD
The longest idle search method will be used when distributing calls.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 8. To save the changes you make to the Trunk Group table, pull down the File menu and select Save. 9. When you are finished editing the Trunk Group table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes.Click Cancel to go back to the Trunk Group Table window where you can save your changes.
6-15
Deleting Trunk Groups
Procedure 28
EXS ExchangePlus Software Operations Guide
Deleting Trunk Groups This procedure describes how to delete trunk groups.
Steps
1. Pull down the Database menu and select Trunk Group Setup. The Trunk Group table appears (Figure 6-6). This table shows all the trunk groups that have been configured for this node. You can delete any of these trunk groups.
Figure 6-6 Trunk Group Table
2. To delete a trunk group in a Trunk Group table, you delete the line containing its definition. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Trunk Group table, pull down the File menu and select Save. 4. When you are done editing the Trunk Group table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Trunk Group Table window where you can save your changes.
6-16
EXS ExchangePlus Software Operations Guide
Procedure 29
Adding or Changing Routes
Adding or Changing Routes This procedure describes how to add or change routes. A route list is a set of trunk groups arranged in priority or by the percentage of calls to be routed via a particular trunk group. When the list is arranged by priority and the switch is searching for a route via a route list, it will select the route by looking for an available circuit in the first trunk group (TG1) in the list. If no circuit is available, it will proceed through the list of trunk groups to the last trunk group or until it encounters a -1. The switch will always choose the first available trunk group in the list which has circuits that are available when routing. Percentage routing is used to distribute the calls among the trunk groups within a route list according to the percentages specified. When the route list is configured with percentages, and the switch is searching for a route via the route list, it will select the route based on the percentages that are specified for each trunk group. For example: Suppose you have the following entries in the Route List table: ROUTE 1 2
TG1 1 1
% 0 20
TG2 % 2 0 2 50
TG3 % -1 0 3 30
TG4 -1 -1
% 0 0
The first entry indicates that if the matching entry in the DNIS Translation table indicated that you should use Route 1, then the switch would first try to route the call over Trunk Group 1. If that was not available, it would try Trunk Group 2. The second entry indicates that if the matching entry in the DNIS Translation table indicated that you should use Route 2, then the switch would route approximately 20% of the calls to Trunk Group 1, 50% of the calls to Trunk Group 2, and 30% of the calls to Trunk Group 3. Percentage routing uses a pseudo-random number generator that distributes the calls to approximate the percentages configured. If the call volume is small, the calls may not be distributed according to the configured values, but as the call volume increases, the percentage of calls routed to a particular trunk group will be distributed according to the assigned percentages. . If the total percentage in a particular route list is not equal to 100%, the percentage assigned to the last trunk group in the list will be adjusted to make the total equal 100%. For example: Suppose you had the following entries in the Route List table. ROUTE TG1 1 1 2 2
% TG2 50 2 50 6
% TG3 10 4 20 3
% TG4 10 5 20 8
% 20 20
6-17
Adding or Changing Routes
EXS ExchangePlus Software Operations Guide
The total percentage assigned in Route List 1 is 90%. When calls are routed, 30% of the calls will be routed to Trunk Group 5, although the table entry only specifies 20%. The system automatically adds an extra 10% of the calls to Trunk Group 5 (the last trunk group in the list) to make to total percentage equal 100%. Similarly, the total percentage assigned in Route List 2 is 110%. When calls are routed, only 10% of the calls will be routed to Trunk Group 8, although the table entry specifies 20%. The system automatically deducts 10% of the calls from Trunk Group 8 (the last trunk group in the list) to make the total percentage equal 100%. Once the trunk group has been selected, the system searches for a trunk in that trunk group to use. If one is available, is passes the called number (or the called number that was translated based on the match in the DNIS Translation entry) over the specified trunk. NOTE: If you are adding more than one trunk group to a route list, make sure that you list all the trunk groups in a â&#x20AC;&#x153;non-breakingâ&#x20AC;? order. In other words, list all the trunk groups to be assigned one after the other (with no entries of -1 between the non-zero entries). For example, if you want the primary trunk group to be 5, followed by a secondary trunk group of 8, and a third trunk group of 4, the entry should look like the following:
The entry should not have trunks assigned to -1 in between the entries with the 5, 8, and 4. NOTE: If you are using percentage routing, make sure that the sum of the percentages in each Route List table entry is 100.
Steps
1. Pull down the Database menu and select Route List Setup. The Route List table appears (Figure 6-7). This table shows all the route lists that have been configured for a particular node.
Figure 6-7 Route List Table
6-18
EXS ExchangePlus Software Operations Guide
Adding or Changing Routes
2. To add a route list, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the values for the new route list on the new line or you can copy some or all of an existing route list definition from the table and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy the definition of Route List 5 into a new line, you may want to change the route list number from 5 to something else, say 20. 6. To change an existing route list, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
6-19
Adding or Changing Routes
EXS ExchangePlus Software Operations Guide
7. The following table lists the fields in the table that you need to complete. NOTE: The sum of the percentages in each route list (row) must equal 100. If the sum does not equal 100, the system will automatically adjust the percentage specified in the last trunk group in the row to make the total equal 100. Parameter
Value
Description
Route
integer
Route list number
TG1
integer
The number of the first trunk group that the switch will use to route traffic for this route number.
%
integer between 0 and 100
Use this field only if you are configuring percentage routing. It indicates the approximate percentage of calls that will be sent to this trunk group. Set this value to 0 if percentage routing is not used.
TG2
integer
The number of the second trunk group that the switch will try to use to route traffic for this route number. If this field contains a -1, it indicates that there are no more trunk groups that can be used for this route number. Do no insert trunk group numbers into TG fields in an entry if you have already inserted a -1 in a previous TG field in that same entry.
%
integer between 0 and 100
Use this field only if you are configuring percentage routing. It indicates the approximate percentage of calls that will be sent to this trunk group. Set this value to 0 if percentage routing is not used.
TGn (where n is the TG number)
integer
The number of all remaining trunk groups that the switch will try to use to route traffic for this route number. If this field contains a -1, it indicates that there are no more trunk groups that can be used for this route number. Do no insert trunk group numbers into TG fields in an entry if you have already inserted a -1 in a previous TG field in that same entry.
%
integer between 0 and 100
Use this field only if you are configuring percentage routing. It indicates the approximate percentage of calls that will be sent to this trunk group. Set this value to 0 if percentage routing is not used.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved.
6-20
EXS ExchangePlus Software Operations Guide
Adding or Changing Routes
8. To save the changes you make to the Route List table, pull down the File menu and select Save. 9. When you are done editing the Route List table, pull down the File menu and select Quit. If you have not saved all the change, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Route List Table window where you can save your changes.
6-21
Deleting Routes
Procedure 30
EXS ExchangePlus Software Operations Guide
Deleting Routes This procedure describes how to delete routes.
Steps
1. Pull down the Database menu and select Route List Setup. The Route List table appears (Figure 6-8). This table show all the routes that have been configured for this node. You can delete any of these routes.
Figure 6-8 Route List Table
2. To delete a route you delete the line containing the definition from the Route List table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Route List table, pull down the File menu and select Save. 4. When you are done editing the Route List table, pull down the File menu and select Quit. If the changes are not saved, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes or click Cancel to go back to the Route List Table window where you can save your changes.
6-22
EXS ExchangePlus Software Operations Guide
Procedure 31
Adding Trunks to Trunk Groups
Adding Trunks to Trunk Groups This procedure describes how to assign trunks to trunk groups.
Steps
1.
Pull down the Database menu and select Trunk Setup. The Trunk table appears (Figure 6-9). This table show all the trunks that have been configured for this node. You can add new members to trunk groups or change existing trunk group members.
Figure 6-9 Trunk Table
2. To assign a new trunk to a trunk group or to change the assignment of a trunk, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new trunk on the new line or you can copy an existing trunk definition from the table and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line from the table, use the mouse to highlight the selected line, then pull down the Edit menu and select Copy. Use the mouse to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary.
6-23
Adding Trunks to Trunk Groups
EXS ExchangePlus Software Operations Guide
For example: Change the number of the trunk that you copied to a new number. 6.
The following table lists the fields in the table that you need to complete:
Parameter
Value
Description
Group
integer
The trunk group the circuits are assigned to. This sets up the signaling and circuits directions as set up in the Trunk Group table.
Span1, Chan1
integer
The starting point of the range of trunks that will be assigned on this line.
Span2, Chan2
integer
The ending point of the range of trunks that will be assigned on this line.
Route
Rn - route to the route specified by n The default route list. This route is used to Xn - route to the exception pointed select the outbound trunk, if there is no to by n An - route to the announcements pointed to by n Cn - route to the conference Dn - route to Time of Day route specified by n Wn - route to Day of Week route specified by n
route based on the called number. It selects the default route based on the incoming trunk group (column 1 of this table).
CIC
integer
It is the starting Circuit Identification Code (CIC) number in the group. The CIC is only necessary if the circuit is controlled via an SS7 link.
INC
integer
The increment for the CICs. Typically the increment is 1, but it can be set to the appropriate value.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Trunk table, pull down the File menu and select Save. 8. When you are done editing the Trunk table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Trunk Table window where you can save your changes.
6-24
EXS ExchangePlus Software Operations Guide
Procedure 32
Deleting Trunks from Trunk Groups
Deleting Trunks from Trunk Groups This procedure describes how to delete members (trunks) from a trunk group.
Steps
1. Pull down the Database menu and select Trunk Setup. The Trunk table appears (Figure 6-10). This table show all the trunks that have been configured for this node. You can delete any of these trunks.
Figure 6-10 Trunk Table
2. To delete one or more trunks from a trunk group, you delete one or more lines from the trunk table. NOTE: Remember that the lines in this table may cover a range of trunks, so you want to use care when removing trunks. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the Trunk table, pull down the File menu and select Save. 5. When you are done editing the Trunk table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Trunk Table window where you can save your changes.
6-25
Adding or Changing ANI Tables
Procedure 33
EXS ExchangePlus Software Operations Guide
Adding or Changing ANI Tables This procedure describes how to add or modify ANI table entries. The entries are used to translate the calling number (ANI) and to determine if the call should be blocked or restricted, based on the calling number. When a call comes into the switch, ExchangePlus determines if ANI screening is enabled on the incoming trunk. If it is, the system accesses the ANI table. The system uses: • •
The calling number, and The partition number of the incoming trunk group to which the trunk belongs
to determine • •
How the calling number should be translated, and Whether or not the call should be blocked based on the calling number.
If there is no match in the ANI table, the call is routed to an exception in the Exception table. The possible exceptions it can be routed to are: • • •
27: Blocked exception 28: Temporarily blocked exception 29: ANI does not exist
Assumptions
In order to use ANI screening, the incoming trunk must have the ASCRN (ANI screening) flag set. This flag enables ANI screening and it is set in the Trunk Group table. To enable ANI screening on a particular trunk group, include the ASCRN flag in the Flag field on the Trunk Group table for the trunk group of interest. For example, the Flag field might be set to: ISDN+ASCRN.
Steps
To add or change entries in the ANI table: 1. Pull down the Database menu and select Edit ANI. The ANI Table window appears (Figure 6-11). You can add or change entries in the ANI table.
Figure 6-11 ANI Table
2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the values for the new translation on the new line or you can copy an existing translation from the table and paste it into the blank line.
6-26
EXS ExchangePlus Software Operations Guide
Adding or Changing ANI Tables
3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys, the <Tab> key to move from field to field, as necessary. 6. To change an existing translation, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7.
Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary (for example, change the number of the partition that you copied to a new number).
6-27
Adding or Changing ANI Tables
EXS ExchangePlus Software Operations Guide
8. The following tables lists the fields that you need to complete for each entry. Parameter
Value
Description
Part
0-9999
The partition number specifies the individual subtable within the ANI table. Be sure to define entries in the ANI table for each partition defined in the Trunk Group table.
ANI
The digits of the number from which the call originated.
The calling number. This is the number from which the call was dialed.
Wild cards are supported in the ANI number field. See the Wild card table on page 6-30. Trans
NOA
A value of -1 indicates that no translation will be performed. Wild cards are supported in the CLG number field. See the Wild card table on page 6-30.
The digits that will be substituted for the CLG number and sent outbound. The translation is optional.
0-5, where 0=Spare 1= Subscriber 2=Unknown 3=National 4=International >4=Preserve the incoming value
Nature of Address field for the Calling Number.
The setting of the NOA maps to Nature of Address for SS7 and Calling Number Type for ISDN. The mapping is as follows: NOA Nature of Calling Number Address (SS7) Type (ISDN) 0 0 3 1 1 4 2 2 0 3 3 2 4 4 1 >4 Preserve incoming value
The output of this translation is the number that will be sent outbound.
Used for SS7 and ISDN only.
â&#x20AC;˘
â&#x20AC;˘
For SS7 it specifies the Nature of Address on the ANI sent with the outbound call. For ISDN it specifies the Calling Number Type on the ANI sent with the outbound call.
For example, if you set NOA to 3 in an SS7 connection then the Nature of Address=3. If you set NOA to 3 in an ISDN connection, the Calling Number Type=2. COS
6-28
Not used. Set to NONE.
Class of Service. This field is not used.
EXS ExchangePlus Software Operations Guide
Adding or Changing ANI Tables
Parameter
Value
Description
REST
T=Temporarily blocked B=Permanently blocked U=Unblocked (calling number may be displayed on Caller ID box) R=Restricted (called number is may not be displayed on Caller ID box)
Restriction. This value specifies whether or not the call is blocked. If the call is blocked (T or B) the call is routed to an exception. If the call is not blocked (U or R), the SRCH field specifies the search partition in the DNIS Translation table that will be used to determine how the call will be routed.
CPA
Set 0 or 1 (Either value has no effect.)
Reserved for future use.
Srch
0-9999 or -1 Set this field to -1 to indicate that you should use the partition of the trunk on which the call came in (the partition of the incoming trunk).
The number of the search partition in the DNIS Translation table that will be searched to determine how the call will be routed. The search partition is only used if the call is not blocked (REST= U or R).
Type
0 or 1=Completely replaces the calling number with the translation. 3=Wild card translation is allowed.
Indicates the type of translation to be performed on the calling number. It determines how the translation of the calling number will be performed. The most common settings are 0 and 3. Use 0 when no wild cards are present and 3 when wild cards are used.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 9. To save the changes you make to the ANI table, pull down the File menu and select Save. 10. When you are done editing the ANI table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the ANI Table window where you can save your changes.
6-29
Adding or Changing ANI Tables
EXS ExchangePlus Software Operations Guide
11. If wild card translation is used, the digits that match the wild cards are carried over from the calling number to the translated number exactly as they appear in the calling number. The following table describes the two wild cards that can be used. Wild Card
Description
& (ampersand)
The “&” matches any number of digits. For example, if you had the entry 011541& in the ANI field of the ANI table, then all of the following Calling Numbers would match it: 0115417 0115413000 0115417273000 Any calling number starting with 011541 and having any number of digits after the 011541 will match 011541&. If the Translation field in the ANI table was 541&, then Calling Number 0115417 would become 5417 Calling Number 0115413000 would become 5413000 Calling Number 0115417273000 would become 5417273000
- (hyphen)
The “-” matches a single digit. For example, if you had the entry 972---- in the ANI field of the ANI table, then the following Calling Numbers would match that entry: 9723000 9723543 However, the following numbers would not match 972---because they do not have four digits (one to correlate with each of the hyphens) following 972: 9721 972345 9728623000 If the Translation field in the ANI table was 3----, then Calling number 5083000 would become 33000 Calling number 5083543 would become 33543
Matching Criteria
6-30
Matching Criteria used to match the calling number to an entry in the ANI table is the same as the matching criteria used with the DNIS Translation table, except that for the ANI table, the calling number is matched (not the called number as in the DNIS Translation table). See “Matching Criteria” on page 6-39.
EXS ExchangePlus Software Operations Guide
Procedure 34
Deleting ANI Entries
Deleting ANI Entries This procedure describes how to delete entries from the ANI table.
Steps
1. Pull down the Database menu and select Edit ANI. The ANI Table window appears (Figure 6-12). You can delete entries in the ANI table.
Figure 6-12 ANI Table
2. To delete one or more entries, you delete one or more lines from the ANI table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the ANI table, pull down the File menu and select Save. 5. When you are done editing the ANI table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the ANI Table window where you can save your changes.
6-31
Adding or Changing DNIS Translations
Procedure 35
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations This section provides a basic overview of the DNIS Translation table followed by a procedure on how to add or change the DNIS Translation table. Figure 6-13 shows a sample of the DNIS Translation table.
Figure 6-13 DNIS Translation Table
Overview
The DNIS Translation table refers to the “dialed number” translation. It is used to • •
Translate incoming numbers, and Route calls
Every incoming call is looked up in the DNIS Translation table. ExchangePlus tries to find the best match for the call based on the Matching Criteria defined on page 6-39. When a match is found, the outgoing route is selected and translation is performed (if it is specified in the table). The digits are outpulsed and an application specific flag which specifies the characteristics of the call are set in the Outgoing Call Type. See Figure 6-14 for an illustration of this process.
6-32
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations
Dialed number is looked up in the DNIS Translation table.
Is match found?
No
Number is outpulsed on default route without any translation. Default route is specified in trunk setup.
Yes The outgoing route is selected from the matching entry.
The dialed number is translated based on the translation field in the matching entry.
Digits are outpulsed and the value of NOA is assigned to the outgoing call type.
Figure 6-14 Processing Calls Through DNIS Translation Table
The DNIS Translation table is divided into up to 9999 subtables called partitions as shown in Figure 6-15.
DNIS Translation table Partition 1
Partition 2
Partition 3
Partition 4
...
Partition 9999
Figure 6-15 DNIS Translation Table Divided Into Partitions
Partitions are subtables within one large DNIS Translation table that allow calls to be translated and routed based on the trunk group on which they were received. This allows you to translate and route traffic differently based on the carriers using the trunks. For example, one set of trunks may be used to carry calls from MCI and another may carry calls from Bell Atlantic. Each of these carriers would use a different partition and calls are translated and routed based on the partition used. (Instead of having partitions, other systems that you might be familiar with have multiple translation and routing tables that are used for different sets of trunk groups.
6-33
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
ExchangePlus uses a single table for translation and routing, but divides it into up to 9999 subtables or partitions). Each partition (subtable) contains a series of entries that are used to match the incoming calls. Each trunk group is associated with a partition (subtable). When the dialed number for a call is looked up in the DNIS Translation table, it is only looked up in the partition (subtable) associated with the trunk group on which the call was received. For example, if a call comes in on Trunk Group 1 and Trunk Group 1 is associated with Partition 1, then the dialed number is only matched to the DNIS Translation table entries in Partition 1. If a call comes in on Trunk Group 2 and Trunk Group 2 is associated with Partition 2, then the dialed number is only matched to the entries in Partition 2. If you had the following Trunk Group Setup table configuration, (see the TG and PART fields):
and, if the following calls came in, they would be looked up in the partitions as follows:
DNIS Translation table
6-34
Calls coming in on trunk group 1 (associated with Partition 1): 1-508-862-3000 1-617-555-1212 1-972-727-1640
Entries in Partition 1
Calls coming in on trunk group 2 (associated with Partition 2): 1-508-862-3000 1-617-555-1212 1-972-727-1640
Entries in Partition 2
Calls coming in on trunk group 3 (associated with Partition 3): 1-508-862-3000 1-617-555-1212 1-972-727-1640
Entries in Partition 3
PART 0001 0001 0001
PART 0002 0002 0002
PART 0003 0003 0003
CLD TRANS INFO 1508& 508& xxx 1617& 617& xxx 1972& 972& xxx
CLD TRANS 1508& & 1617& & 1972& &
CLD TRANS 1508& 1972& 1617& 1972& 1972& -1
INFO xxx xxx xxx
INFO xxx xxx xxx
ROUTE NOA... R1 3 R2 3 R3 3
ROUTE NOA... R5 3 R4 3 R6 3
ROUTE NOA... R7 3 R8 3 R9 3
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations
You can use the DNIS Translation table to route calls without performing a translation. To do this, enter a -1 in the Translation field. In this case, the call will be matched to a DNIS Translation entry and the route will be selected, but the dialed number will be outpulsed as is, instead of being translated first. There are two important flags on the DNIS Translation table that must be set (NOA and Type). NOA characterizes the Nature of Address that will be output (national or international, for example). Type which indicates the type of translation to be performed. These are described later in this chapter. There are three additional options which may affect the translation and routing. The following options will be described starting on page 6-43: • • •
Interpret Digits Translate with Prefix Outbound Translation
Procedure
This procedure describes how to add or modify DNIS Translation table entries. The entries are used to route calls based on the number that was dialed. When a call comes into the switch, the switch looks at the number that was dialed and attempts to match the number to one of the DNIS Translation table entries. If it finds a match, it then translates the number according to the matching entry in the DNIS Translation table and routes the call to the specified route. A route can be an outgoing trunk group, an exception, an announcement, or a Time of Day or Day of Week route.
Steps
To add or change entries in the DNIS Translation table: 1. Pull down the Database menu and select DNIS Translation. The DNIS Translation Table window appears (Figure 6-16). You can add or change entries in the DNIS Translation table.
Figure 6-16 DNIS Translation Table
2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the values for the new translation on the new line or you can copy an existing translation from the table and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row.
6-35
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys, the <Tab> key to move from field to field, as necessary. 6. To change an existing translation, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7.
Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary (for example, change the number of the partition that you copied to a new number).
8. The following tables lists the fields that you need to complete for each entry. NOTE: A number of examples follow this procedure. Use these examples as models when you are writing your DNIS Translation table entries. Parameter
Value
Description
Part
0-9999
The partition number specifies the individual subtable within the DNIS Translation table. Be sure to define entries in the DNIS Translation table for each partition defined in the Trunk Group table.
CLD
The digits in the incoming dialed number.
The called number. This is the number that was dialed
Wild cards are supported in the CLD number field. See the Wild card table on page 6-38. Trans
A value of -1 indicates that no translation will be performed. Wild cards are supported in the CLD number field. See the Wild card table on page 6-38.
The digits that will be substituted for the CLD number and sent outbound. The translation is optional. The output of this translation is the number that will be sent outbound.
NOTE: Several examples of translations are provided starting on page 6-39. Info
6-36
User defined text string
A text description of the translation. The DNIS Translation table can be sorted based on this field. See Procedure 36 Sorting Entries in DNIS Translation Table on page 648.
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations
Parameter
Value
Description
Route
Rn - route list that contains up to 10 routes that may be used to send the call outbound. Xn - route to the exception specified by n An - route to the announcement specified by n Cn - route to a conference Dn - route to the time of day route specified by n Wn - route to the day of week route specified by n
The route (or other treatment) to be used to dial outbound. The other treatments are described starting on page 6-50.
NOA
0-5, where 0=Spare 1= Subscriber 2=Unknown 3=National 4=International >4=Preserve the incoming value
Nature of Address field. Used for SS7 and ISDN only. For SS7 this flag is used to specify the Nature of Address on the outbound call. For ISDN this flag is used to specify the Called Number Type on the outbound call.
The setting of the NOA maps to Nature of Address for SS7 and Called Number Type for ISDN. The mapping is as follows: NOA Nature of Called Number Address (SS7) Type (ISDN) 0 0 3 1 1 4 2 2 0 3 3 2 4 4 1 >4 Preserve incoming value For example, if you set NOA to 3 in an SS7 connection then the Nature of Address=3. If you set NOA to 3 in an ISDN connection, the Called Number Type=2. Flag2
Not used.
Application defined connection type
Type
0 or 1=Completely replace the called number with the translation. 2=Smart wild card translation. This is only used with the Interpret Digits option described on page 6-43.) 3=Wild card translation is allowed.
Indicates the type of translation. It determines how the translation of the called number will be performed.
APP1, APP2, APP3, ... APP8
Custom Application flag. This flag specifies the name of the custom application used by calls.
AppFlag
The most common settings are 0 and 3. Use 0 when no wild cards are present and 3 when wild cards are used.
UFlag1
User defined flag.
UFlag2
User defined flag
6-37
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 9. To save the changes you make to the DNIS Translation table, pull down the File menu and select Save. 10. When you are done editing the DNIS Translation table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the DNIS Translation Table window where you can save your changes. 11. If wild card translation is used, the digits that match the wild cards are carried over from the called number to the translated number exactly as they appear in the called number. The following table describes the two wild cards that can be used. Wild Card
Description
& (ampersand)
The “&” matches any number of digits. For example, if you had the entry 011541& in the CLD field of the DNIS Translation table, then all of the following Called Numbers would match it: 0115417 0115413000 0115417273000 Any called number starting with 011541 and having any number of digits after the 011541 will match 011541&. If the Translation field was 541&, then Called Number 0115417 would become 5417 Called Number 0115413000 would become 5413000 Called Number 0115417273000 would become 5417273000
- (hyphen)
The “-” matches a single digit. For example, if you had the entry 972---- in the CLD field of the DNIS Translation table, then the following Called Numbers would match that entry: 9723000 9723543 However, the following numbers would not match 972---because they do not have four digits (one to correlate with each of the hyphens) following 972: 9721 972345 9728623000 If the Translation filed was 3----, then Called number 5083000 would become 33000 Called number 5083543 would become 33543
6-38
EXS ExchangePlus Software Operations Guide
Examples
Matching Criteria
Adding or Changing DNIS Translations
This section shows a number of examples of DNIS Translation table entries that help describe how to set up these tables. The examples are divided into categories to show different functions of the table. When calls come into the DNIS Translation table, they are matched according to the following rules: 1. The longest digit string match takes precedence. For example, if there are the following entries in the CLD field of the DNIS Translation table: 011541& 01154& and the incoming called number is 0115417271234, then entry 011541& will be selected. This is because six digits of the called number match 011541& while only five digits match 01154&. 2. If there is no exact match, the single replacement wild card (-) match will be tried. 3. If there are no exact matches or single replacement matches, then the ampersand (&) wild card match will be tried. For example: If you have the following DNIS Translation table:
then a call from partition 0 with 0115419722345 will find Entry3 (exact match), but a call from partition 0 with 0115418 will find Entry4 (single replacement match). A call from partition 0 with 011541972 will find Entry1 (wild card match with longest digit string match) and a call from partition 0 with 01154872345 will only find Entry2. Another example: If a call comes in with 9727271640, then the following translation matches will be found:
6-39
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
All three matches are valid and would be found during DNIS Translation analysis. However, according to the matching criteria listed above, Entry22 is the longest digit match and would be used for the translation and routing. Entry21 is the second closest match (single replacement match) followed by Entry20. Routing
When the dialed number is matched with an entry in the DNIS Translation table, the call is translated as required and then outpulsed to the route specified in the ROUTE field. The route can be a route list, an exception, an announcement, a Time of Day route, or a Day of Week route. The following DNIS Translation table shows some examples of different routes:
The entries are referred to in the text below by the text in the INFO field. For example, Entry1 is the first entry and Entry3 is the third entry. Calls that match Entry1 will be sent out based on information in the Route List table. The value R1 in the ROUTE field indicates the system will look up the outgoing route in the Route List table (using the entry containing ROUTE=1). Calls that match Entry2 will be sent out based on information in the Time of Day table. The value D3 in the ROUTE field indicates the system will look up the outgoing route in the Time of Day table (using the entry containing INDEX=3). Calls that match Entry3 will be sent out based on information in the Day of Week table. The value W7 in the ROUTE field indicates the system will look up the outgoing route in the Day of Week table (using the entry containing INDEX=7). Calls that match Entry4 reference the Announcement table which causes an announcement to be played back to the caller. The value A4 in the ROUTE field indicates that the system will look up the announcement to be used in the Announcement table (using the entry containing ID=4). Calls that match Entry5 reference the Exception table which specifies how the call should be treated. The value X2 indicates that the system will look up the exception in the Exception table (using the entry containing EXCEPTION=2).
6-40
EXS ExchangePlus Software Operations Guide
NOA Field
Adding or Changing DNIS Translations
As described earlier, the NOA field is used for SS7 or ISDN. The setting in the NOA field maps to Nature of Address for SS7 and Called Number Type for ISDN. The mapping is as follows:
Nature of Address (SS7)
Called Number Type (ISDN)
0=Spare
0
3
1=Subscriber
1
4
2=Unknown
2
0
3=National
3
2
4=International
4
1
Preserve incoming value
Preserve incoming value
NOA
>=5
For example, if you set NOA to 3 in an SS7 connection the Nature of Address=3. If you set NOA to 3 in an ISDN connection, the Called Number Type=2. The following DNIS Translation table shows some examples of different NOA fields:
Calls that match Entry1 will be passed through with a national flag. Calls that match Entry2 will be passed through with a national flag. Calls that match Entry3 will be passed through with an international flag.
6-41
Adding or Changing DNIS Translations
General Examples
EXS ExchangePlus Software Operations Guide
Figure 6-17 shows some additional examples that combine many of the concepts described in this chapter. The entries are referred to by the text in the Info fields. For example, the “no trans” entry is the first entry in the table and the “no route” entry is the last entry. The first five entries are valid only for incoming calls on partition 0. The second five entries are valid only for incoming calls on partition 1.
Figure 6-17 Sample DNIS Translation Entries
The “no trans” entry will be passed outbound on Route 1 (ROUTE=R1). It will not be translated (TRANS=-1) and will be passed through as a National number (NOA=3). The “new area code” entry would replace the 1+area code (214) with 1+new area code (972). The call would be sent out on Route 1 with Nature of Address passed through (NOA=5). The “strip 011508” entry strips off 011508 from the called number, so called number 0115088623000 would become 8623000.The call would be sent out on Route 1 with Nature of Address passed through (NOA=5) The “append 011” entry adds 011 to the beginning of called number. The called number 5088623000 becomes 0115088623000 and will be sent out on Route 1 as an international number (NOA=4). The “new prefix” entry strips off 011 and appends 1 to the called number. Called number 0115088623000 becomes 15088623000 and will be sent out on Route 1 as a national number (NOA=3). The “pass through” entry routes all calls beginning with area code 214 to Route 4. The “add area code” entry will route all 7-digit called numbers to Route 6 after appending the 214 area code to the front of the number. The “add prefix” entry appends a 9 in front of all dialed numbers beginning with area code 214 and routes the numbers to Route 6. The “operators” entry routes all dialed numbers starting with zero to Announcement 108. The “no route” entry routes all dialed numbers that were not matched by any of the other entries to Exception 4 (reorder tone).
6-42
EXS ExchangePlus Software Operations Guide
Interpret Digits Option
Adding or Changing DNIS Translations
This section describes the Interpret Digits option and provides some examples of the DNIS Translation table with Interpret Digits turned on and turned off. For more details on how to enable Interpret Digits, see Procedure 13 Using the Interpret Digits Option on page 3-14. This option can only be used in North America. Do not use the Interpret Digits option in international systems. This option allows the system to analyze the digits in the dialed number and determine the type of the call as: • • • •
an international operator call (01+) an international call (011+) a national operator call (0+) a national call (1+)
The call type information will be stored in the Nature of Address field and the incoming Call Type field. Once the Call Type is stored, the system then “normalizes” the dialed number, by stripping the prefix from the number and storing the resulting number as the called number. The system normalizes the numbers so that dialed numbers coming in either inband (which may have prefixes) or via SS7 (which usually don’t have prefixes) look the same when they are used as input for the DNIS Translation table. NOTE: Smart wild card translation must be turned on to use the Interpret Digits option. To set smart wild card translation, set the Type field in the DNIS Translation to 2. Examples: Interpret Digits Off If Interpret Digits is turned Off and the following numbers come into the switch: • •
0119727272345 9727272345
You would need two entries in the DNIS Translation table: •
One to match the number starting with 011, and
•
One to match the number starting with 972.
The entries would be as follows:
Routing of both numbers would be the same, but two entries are still required.
6-43
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
Interpret Digits On If Interpret Digits was turned On and the same numbers came into the switch, you would only need a single entry in the DNIS Translation table because 0119727272345 would be normalized (011 would be stripped and the Incoming Call Type would be set to international). The DNIS entry would be as follows (note that Type is set to 2 - smart wild card translation is required when you are using Interpret Digits).
For more information on the Interpret Digits option, see Procedure 13 Using the Interpret Digits Option on page 3-14.
Translation with Prefix Option
This section describes the Translate with Prefix option and provides some examples of the DNIS Translation table with Translate with Prefix turned on and turned off. For more details on how to enable Interpret Digits, see Procedure 14 Using the Translate with Prefix Option on page 3-16 This option can only be used in North America. Do not use the Translate with Prefix option in international systems. If Translate with Prefix is turned on, the system looks at the Nature of Address field and incoming Call Type field and determines the call type (national or international, for example). It then appends the appropriate prefix to the Called Number before the number is used as input to the DNIS Translation table. For example: Suppose the TRANSLATEWITHPREFIX option is turned on. If a call comes in from partition 0 with a called number that is 8621234 and the Nature of Address and incoming Call Type fields indicate that the call is an international call, then the system appends the prefix 011 to the Called Number before it inputs the number into the DNIS Translation table. Translate with Prefix Off If Translate with Prefix is turned off and the following numbers come into the switch: • •
9727272345 (NOA and Incoming Call Type are International) 0119727272345
You would need two entries in the DNIS Translation table:
6-44
•
One to match the number starting with 9727272345, and
•
One to match the number starting with 011972.
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations
The entries would be as follows:
Routing of both numbers would be the same, but two entries are still required. Translate with Prefix On If Translate with Prefix was turned on and the same numbers came into the switch, you would only need a singe entry in the DNIS Translation table because 011 would be appended to the 9727272345 number because the NOA and Incoming Call Type were set to International. The DNIS entry would be as follows (note that Type is set to 2 - smart wild card translation is required when you are using Interpret Digits).
The Translate with Prefix option is often used in conjunction with the Interpret Digit option. This allows you to make dialed numbers that do or do not have prefixes all look the same so that the number of entries in the DNIS Translation table can be reduced. .
Outbound Translations
The following section explains how the Outbound Translation feature operates. The outbound translation option allows you to perform a second translation on the called number if the partition number of the outbound trunk group is different than the partition number of the inbound trunk group. See Procedure 12 Using the Outbound Translation Option on page 3-12 for information on how to enable this option. After the initial pass through the DNIS Translation table, the called number may or may not be translated and the call will be routed according to the matching entry in the table. If the route assigned specifies that call will be routed outbound to a trunk in a different partition than the partition on which the call was received (the incoming partition) and the Outbound Translation option is enabled, then the called number may be translated a second time. The system looks at the outgoing partition number and the called number (or the translated called number if OUTBOUNDTRANSLATION is set to 2) and attempts to find a match in the DNIS Translation table. If a match is found, the called number is translated again and NOA (the Nature of Address) flag may also be changed. The routing assigned to the outbound call is not changed during this second translation.
6-45
Adding or Changing DNIS Translations
EXS ExchangePlus Software Operations Guide
If no match if found, the original translation (based on the incoming partition) and value of NOA will be used in the outgoing call. For example: If Outbound Translation is enabled and you had the following Route List and DNIS Translation tables: Route List table:
DNIS Translation table:
When a call comes in from partition 0 with the number 9727271640, it matches Entry1 (the only entry that uses partition 0). The called number is translated to 0119727271640, NOA is set to 3 (international) and the call is routed to R1. Using the Route List table, R1 determines that the call will be routed over Trunk Group 1. Trunk Group 1 is in Partition 1 (this is specified on the Trunk Group List). When outbound translation is turned on and the outgoing partition (1) is different than the incoming partition (0), the outgoing partition and the called number are used to search the DNIS Translation table again for a match. This time 972727160 matches entry 2 (the only entry that uses partition 1). The called number (9727271640) is translated to 2147271640 and NOA will be set to 3 (national). The call is routed over R1 again. The route to be used is determined by the first match in the DNIS Translation table (based on the incoming partition number), not the match based on the outgoing partition number. Figure 6-18 shows how calls are processed in the DNIS Translation table when the Outbound Translation option is enabled. The shaded boxes show the differences in call processing due to Outbound Translation.
6-46
EXS ExchangePlus Software Operations Guide
Adding or Changing DNIS Translations
Dialed number is looked up in the DNIS Translation table.
Is match found?
No
Number is outpulsed on default route without any translation. Default route is specified in trunk setup.
Yes The outgoing route is selected from the matching entry.
Is partition the same?
No
The dialed number is translated based on the translation field in the matching entry.
Yes Dialed number is looked up in the DNIS Translation table again (with the new partition)
Digits are outpulsed and the value of NOA is assigned to the outgoing call type.
The dialed number is translated based on the translation field in the matching entry. Value of NOA is set based on matching entry.
Digits are outpulsed on the route specified in the first translation.
Gray indicates steps added when outbound translated is enabled.
Figure 6-18 Processing Calls Through the DNIS Translation Table Using Outbound Translation
6-47
Sorting Entries in DNIS Translation Table
Procedure 36
EXS ExchangePlus Software Operations Guide
Sorting Entries in DNIS Translation Table You can sort entries in the DNIS Translation table according to the text in the Info field. If you chose this option, the entries will be reordered into alphabetical order based on the text included in the Info field. The order of the entries in the table has no effect on how the entries are matched with called numbers. That matching depends on the partition of the incoming trunk and the matching criteria described in â&#x20AC;&#x153;Matching Criteriaâ&#x20AC;? on page 6-39.
Steps
1. Pull down the Database menu and select DNIS Translations. The DNIS Translation table appears. 2. Pull down the Edit menu and select Sort by Info (Figure 6-19)
Figure 6-19 Sort DNIS Translation Table by Info
This selection causes the DNIS Translation table to be sorted according to the Info field (items in that field are placed in alphabetical order).
6-48
EXS ExchangePlus Software Operations Guide
Procedure 37
Deleting DNIS Translations
Deleting DNIS Translations This procedure describes how to delete a translation from the DNIS Translation table.
Steps
1. Pull down the Database menu and select DNIS Translation. The DNIS Translation Table window appears (Figure 6-20). You can delete entries in the DNIS Translation table.
Figure 6-20 DNIS Translation Table
2. To delete one or more translations, you delete one or more lines from the DNIS Translation table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the DNIS Translation table, pull down the File menu and select Save. 5. When you are done editing the DNIS Translation table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the DNIS Translation Table window where you can save your changes.
6-49
Adding and Changing Exception Tables
Procedure 38
EXS ExchangePlus Software Operations Guide
Adding and Changing Exception Tables This procedure describes how to add or change the Exception table. The Exception table assigns specific treatments to specific calls. After you set up the Exception table you can specify the exceptions in the DNIS Translation table or the Routing table. Exceptions are prefixed by the letter â&#x20AC;&#x153;Xâ&#x20AC;?.
Steps
1. Pull down the Database menu and select Exception. The Exception Table window appears (Figure 6-21). You can add or change entries in the Exception table.
Figure 6-21 Exception Table
NOTE: The number of partitions allowed in the Exception table PART field is restricted to 32 (0-31). However, if there is a match in the DNIS Translation table from a partition greater than 31 and that matching entry routes to an exception, the system will try to find an exception in a partition greater than 31. Since there are no partitions greater than 31 in the Exception table, anytime the partition number specified by an entry in the DNIS Translation table is greater than 31, the call will be routed to the specified exception in partition 0. Therefore, partition 0 must be configured in the Exception table if any partitions greater than 31 are defined in the DNIS Translation table. 2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new exception on the new line or you can copy an existing exception from the table and paste it into the blank line.
6-50
EXS ExchangePlus Software Operations Guide
Adding and Changing Exception Tables
3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 6. To change an existing exception, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7.
Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary. For example, change the number of the partition that you copied to a new number.
6-51
Adding and Changing Exception Tables
EXS ExchangePlus Software Operations Guide
8. The following tables lists the fields in the table that you need to complete: Parameter
Value
Description
Partition
0-31
The number of the partition to which this entry applies. There is one exception table per partition. Be sure to define exceptions for each partition defined in the Trunk Group table. If no entry is defined for a partition or if the partition number is greater than 31, the entry in Partition 0 will be used by default.
Exception
NOTE: The first 64 exceptions are reserved for ExchangePlus. The next 64 are used defined.
The Exception ID. This is the number that follows the letter X when the exception appears in the DNIS Translation or Trunk table.
Treatment
T=tone R=route list A=announcement
ID
integer
ID of the exception (Tone, Route List, or Exception)
Reps
-1=not used or infinite
The number of cycles to use.
Description
text string
A text field describing the exception. For example, it could be: Dialtone, Ringback, Busy, Reorder, Warning, etc.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 9. To save the changes you make to the Exception table, pull down the File menu and select Save. 10. When you are done editing the Exception table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Exception Table window where you can save your changes.
6-52
EXS ExchangePlus Software Operations Guide
Procedure 39
Deleting Exceptions
Deleting Exceptions This procedure describes how to delete an exception from the Exception table.
Steps
1. Pull down the Database menu and select Exception. The Exception Table window appears (Figure 6-22). You can delete entries in the Exception table.
Figure 6-22 Exception Table
2. To delete one or more exceptions, you delete one or more lines from the Exception table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4.
To save the changes you make to the Exception table, pull down the File menu and select Save.
5. When you are done editing the Exception table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Exception Table window where you can save your changes.
6-53
Adding or Changing Announcements
Procedure 40
EXS ExchangePlus Software Operations Guide
Adding or Changing Announcements You add and change announcements to be used by the system in the VRAS Announcement table. After you designate the announcements in the VRAS Announcement table, you can specify the announcement to be played when certain calls are received in the DNIS Translation table or the Routing table. Announcements are prefixed by the letter â&#x20AC;&#x153;Aâ&#x20AC;?.
Steps
1. Pull down the Database menu and select VRAS. The VRAS Announcement Table window appears (Figure 6-23). You can add or change entries in the VRAS Announcement table.
Figure 6-23 VRAS Announcement Table
2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new announcement on the new line or you can copy an existing announcement from the table and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 6. To change an existing announcement, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
6-54
EXS ExchangePlus Software Operations Guide
Adding or Changing Announcements
7. Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary (for example, change the number of the partition that you copied to a new number). 8. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
NodeID
integer
The ID of the node.
ID
integer
The ID of the announcement. This number will follow the “A” when the announcement is listed in the DNIS Translation or Trunk table.
Slot
integer
The slot containing the DSP card.
SIMM
1-4
The SIMM on the DSP from which the announcement will be played.
Format
0=µ-law 1=A-law
The format of the audio file (mulaw, etc.)
File
alphanumeric string xxx.vox
The name of the audio file that is used when loading the SIMM.
Description
text string
A text message describing the announcement. For example, it could be: Not in Service, etc.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 9. To save the changes you make to the VRAS Announcement table, pull down the File menu and select Save. 10. When you are done editing the VRAS Announcement table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the VRAS Announcement Table window where you can save your changes. NOTE: After you add new announcements, you have to download them before they can be used. See Procedure 42 Downloading Announcements on page 6-57.
6-55
Deleting Announcements
Procedure 41
EXS ExchangePlus Software Operations Guide
Deleting Announcements This procedure describes how to delete a announcements from the VRAS Announcement table. NOTE: Deleting announcement entries in the VRAS Announcement table does not mean that the announcement was deleted from the DSP SIMM.
Steps
1. Pull down the Database menu and select VRAS. The VRAS Announcement Table window appears (Figure 6-24). You can delete entries from the VRAS Announcement table.
Figure 6-24 VRAS Announcement Table
2. To delete one or more announcements, you delete one or more lines from the VRAS Announcement table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the VRAS Announcement table, pull down the File menu and select Save. 5. When you are done editing the VRAS Announcement table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the VRAS Announcement Table window where you can save your changes.
6-56
EXS ExchangePlus Software Operations Guide
Procedure 42
Downloading Announcements
Downloading Announcements This procedure describes how to download VRAS announcements so that they can be used by your switch. You have specified the announcement in the VRAS Announcement table. If you have not done this, see Procedure 40 Adding or Changing Announcements on page 6-54.
Requirements Steps
You must have one of the SIMMS on your DSP card set up with VRAS. 1. Pull down the Maint menu and select Download VRAS. The Download VRAS window appears (Figure 6-25). A window appears which provides the options for downloading announcements.
Figure 6-25 Download VRAS window
2. On this window, enter the number of the option you want to perform: • • • • •
1 - Download a single announcement 2 - Download an entire VRAS SIMM 3 - Download an entire node, 4 - Download everything 99 - Abort the download process If you select 1, 2, or 3 you will be asked to enter additional information (the announcement number for 1, Node ID, slot number of DSP card, and SIMM number for 2, and Node ID for 3). If you enter 4, the download will begin immediately. If you enter 99, you will exit from this window without performing a download.
Once the announcement has been downloaded, it can be played by the switch at the appropriate time.
6-57
Configuring Time of Day (TOD) Routes
Procedure 43
EXS ExchangePlus Software Operations Guide
Configuring Time of Day (TOD) Routes This procedure describes how to set up your switch to allow you to configure routes based on the time of the day. When calls are routed to a Time of Day route, the system looks at the selected route, then determines what time it is and routes the call accordingly. Each entry specifies how calls are routed over a 24 hour period, in increments of one hour. For example: You could specify that for Time of Day route 1 (T1) the system uses • • •
Steps
Route 1 from:12:00AM to 7:59AM Route 2 from 8:00AM to 6:59PM Route 3 from 7:00PM to 11:59PM
1. Pull down the Database menu and select Time of Day. The Time of Day table appears (Figure 6-26). You can add or change entries in the Time of Day table.
Figure 6-26 Time of Day Table
2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in a new entry in the time of day table or you can copy an existing entry and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary.
6-58
EXS ExchangePlus Software Operations Guide
Configuring Time of Day (TOD) Routes
6. To change an existing time of day entry, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7.
Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary (for example, change the hours when a certain route is used).
8. The following table lists the fields in the table that you need to complete. Parameter
Value
Description
Index
integer
An ID for an entry in the Time of Day table. This index number, preceded by the letter “D” can be used in the translation and routing tables to indicate that the routing should be done based on the entry in the Time of Day table. Each entry must specify how calls are routed over a 24-hour period in increments of 1 hour.
RNG
RT
0-23. Number is based on a 24-hour clock in increments of 1 hour. 0=12:00AM-12:59AM 1=1:00AM-1:59AM ... 12=12:00PM-12:59PM 13=1:00PM-1:59PM ... 23=11:00PM-11:59PM
The range of hours during which the specified route should be used. For example, if you enter 0-8 in the RNG field and 2 in the RT field, then from 00:00AM to 08:59AM, route 2 will be used to route traffic.
Rn - route to the route specified by
The route that is used for the selected range of time.
n
Xn - route to the exception pointed to by n An - route to the announcements pointed to by n Cn - route to the conference NOTES: •
For each line in the Time of Day table, you need to have a RNG/RT value to cover each hour during a 24-hour day.
•
Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved.
6-59
Configuring Time of Day (TOD) Routes
EXS ExchangePlus Software Operations Guide
9. To save the changes you make to the Time of Day table, pull down the File menu and select Save. When you are done editing the Time of Day table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Time of Day table window where you can save your changes.
6-60
EXS ExchangePlus Software Operations Guide
Procedure 44
Deleting Time of Day Routes
Deleting Time of Day Routes This procedure describes how to delete Time of Day routes from the Time of Day table.
Steps
1. Pull down the Database menu and select Time of Day. The Time of Day window appears (Figure 6-27). You can delete entries from the Time of Day table.
Figure 6-27 Time of Day Table
2. To delete certain time of day routing entries, delete one or more lines from the Time of Day table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the Time of Day table, pull down the File menu and select Save. 5. When you are done editing the Time of Day table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Time of Day table where you can save your changes.
6-61
Configuring Day of Week (DOW) Routes
Procedure 45
EXS ExchangePlus Software Operations Guide
Configuring Day of Week (DOW) Routes This procedure describes how to set up your switch to allow you to configure routes based on the day of the week. When calls are routed to a Day of Week route, the system looks at the selected route, then determines what day it is and routes the call accordingly. Each entry specifies how calls are routed over a seven-day period starting with Sunday.
Steps
1. Pull down the Database menu and select Day of Week. The Day of Week table appears Figure 6-28. You can add or change entries in the Day of Week table.
Figure 6-28 Day of Week Table
2. To add a new entry, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in a new entry in the Day of Week table or you can copy an existing entry and paste it into the blank line. 3. To type values into the fields on the new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 4. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 5. After pasting information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary.
6-62
EXS ExchangePlus Software Operations Guide
Configuring Day of Week (DOW) Routes
6. To change an existing Day of Week entry, click on the field of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the field of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7.
Use the arrow keys to move from field to field in the new table entry and make any modifications that are necessary (for example, change the route used on a certain day).
8. The following table lists the fields in the table that you need to complete. Parameter
Value
Description
Index
integer
An ID for an entry in the Day of Week table. This index number, preceded by the letter â&#x20AC;&#x153;Wâ&#x20AC;? can be used in the translation and routing tables to indicate that the routing should be done based on the entry in the Day of Week table. Each entry must specify how calls are routed over a seven day period starting with Sunday.
Sun-Sat
Rn - route to the route specified by n Xn - route to the exception pointed to by
The route that is to be used for the selected day of the week.
n
An - route to the announcements pointed to by n Cn - route to the conference NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 9. To save the changes you make to the Day of Week table, pull down the File menu and select Save. 10. When you are done editing the Day of Week table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Day of Week table where you can save your changes.
6-63
Deleting Day of Week Routes
Procedure 46
EXS ExchangePlus Software Operations Guide
Deleting Day of Week Routes This procedure describes how to delete Day of Week routes from the Day of Week table.
Steps
1. Pull down the Database menu and select Day of Week. The Day of Week Table window appears (Figure 6-29). You can delete entries from the Day of Week table.
Figure 6-29 Day of Week Table
2. To delete certain time of day routing entries, delete one or more lines from the Day of Week table one at a time. 3. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete.The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 4. To save the changes you make to the Day of Week table, pull down the File menu and select Save. 5. When you are done editing the Day of Week table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Day of Week table window where you can save your changes.
6-64
EXS ExchangePlus Software Operations Guide
Procedure 47
Saving Configuration Changes via xmenu
Saving Configuration Changes via xmenu Figure 6-30 shows a simple illustration of how configuration information is saved in ExchangePlus.
readcfg (command line) or Load Switch Config (xmenu)
Shared Memory Tables
dbcp dbcp1
Export Tables or Save Slot Config Seed Files switch.cfg board.cfg
Database Files <xxx.dbf>
xmenu or menu
Figure 6-30 How Configuration Information is Saved
Initially, when the host is brought into service, the system is configured using two files called switch.cfg and board.cfg. These are seed files which load the initial configuration into the system. Switch.cfg is loaded using the command readcfg and board.cfg is loaded when you start the host. Once the files are loaded, the configuration is stored in shared memory tables. During installation, the installer runs a program called dbcp to save the configuration loaded from switch.cfg to database files. Once dbcp has been run, any changes you make to the configuration using either the Windows interface (xmenu) or the character-based interface (menu) are automatically updated in the shared memory tables and the database files. If you need to restart your host, you typically use the configuration that is currently loaded in shared memory or in the database files. In the unlikely event that the host needs to be restarted from the seed file (because the configuration in shared memory tables and the database files is not usable), it gets its configuration file from the switch.cfg and board.cfg files. You can save the current configuration to switch.cfg using a function from xmenu called Export Tables. Save hardware configuration information to board.cfg using a function from xmenu called Save Slot Config. NOTE: To insure that you do not lose data in the event of a failure, you should save the data in the tables to the switch.cfg and board.cfg files whenever you make significant changes to the configuration.
6-65
Saving Configuration Changes via xmenu
EXS ExchangePlus Software Operations Guide
It is recommended that you keep back up copies of your previous switch.cfg and board.cfg files in case you need to go back to the previous configuration. Therefore, before saving tables to switch.cfg or board.cfg, make copies of the existing switch.cfg and board.cfg file and give them other names. The following procedures describe how to save the latest configuration files from shared memory into the switch.cfg and board.cfg files.
Exporting Tables to switch.cfg
1. Go to a terminal window and make a backup copy of your original switch.cfg file by typing: cp switch.cfg switch.cfg.bak
2. Pull down the Database menu and select Export Tables. The Export Table window appears (Figure 6-31).
Figure 6-31 Export Tables Window
3. Enter a name of the file to which you want to save your configuration in the Export FileName field. As long as you have made a backup copy of your original switch.cfg file as described in Step 1, it is recommended that you use the name switch.cfg. This will ensure that in the unlikely event that your system must be restarted from the seed file, it will be loaded with the latest configuration data. If you have not made a copy of your original switch.cfg file, it is recommended you name this file something else. 4. To export all tables, check the Export All check box. When you make that selection, anything you enter in Export Tablename field is ignored. NOTE: This is the recommended selection.
6-66
EXS ExchangePlus Software Operations Guide
Saving Tables to board.cfg
Saving Configuration Changes via xmenu
1. Go to the terminal window and make a backup copy of your original board.cfg file by typing: cp board.cfg board.cfg.bak
2. Pull down the System menu and select Save Slot Config. The Save Slot Configuration window appears (Figure 6-32).
Figure 6-32 Save Slot Configuration Window
3. Enter a name of the file to which you want to save your configuration in the Input FileName field. As long as you have made a backup copy of your original board.cfg file as described in Step 1, it is recommended that you use the name board.cfg. This will ensure that in the unlikely event that your system must be restarted from the seed file, it will be loaded with the latest configuration data. If you have not made a copy of your original board.cfg file, it is recommended you name this file something else.
6-67
Making Configuration Changes via UNIX
Procedure 48
EXS ExchangePlus Software Operations Guide
Making Configuration Changes via UNIX In addition to making configuration changes via xmenu, you can also make changes to the Route List table, the DNIS Translation table, and the Line Assign table using the UNIX command line. These changes are made in the shared memory using a command called importcfg. importcfg is a useful command if you want to use a script to automatically make changes to your configuration at certain times of the day or on certain days of the week. It allows you to make configuration changes without operator intervention. When using the importcfg command, you specify a filename that includes new configuration information. If there is no configuration data in shared memory, the configuration data in the file named in the importcfg command will be added to shared memory. If there is already configuration data in shared memory, importcfg changes that configuration data. If any records in shared memory need to be deleted, you must insert a “D” at the beginning of the line in the new file. You can also add an “A” for additions or a “C” for changes, although they are not required as adds and changes are the default action. For example, suppose you had a configuration in shared memory that included a Route List table with entries for route list 1 and 2, but no entry for route list 3. To change route list 1, delete route list 2, and add route list 3, you would use the following command: importcfg newroute
where newroute = Line 1: Line 2: Line 3: Line 4: Line 5:
:ROUTELISTS C, 1, 1, 3, 4, -1 D, 2, 2, -1 A, 3, 1, 2, 4, -1 :END
Line 1 specifies that the changes are made to the Route List table. Line 2 changes existing route list 1 to the entry specified. Line 3 deletes the existing route list 2 entry. Line 4 adds a new route list 3. The same actions would be taken if the newroute file contained the following: :ROUTELISTS 1, 1, 3, 4, -1 D, 2, 2, -1 3, 1, 2, 4, -1 :END
6-68
EXS ExchangePlus Software Operations Guide
Making Configuration Changes via UNIX
In this table, the C and A at the beginning of lines 2 and 4 (respectively) have been removed as they are not required. NOTE: It is important that the names of each table to be modified are properly specified in the change file. The correct table names are: Table
Name Used In Change File
Route List table
ROUTELISTS
DNIS Translation table
DNISTRANS
Line Assign table
LNASSIGN
ANI table
ANI
When you issue the importcfg command, the data in the specified file updates the shared memory and database files in the host to which it is issued. It also updates the standby shared memory in the standby host if you are configuring a redundant system.
Steps
To use the importcfg file: 1. Type: cd usr/isos/bin
2. Using a text editor such as vi, create a file containing the changes you want to make to the Route List table, DNIS Translation table, and Line Assign table. This file must be in the format of the switch.cfg file. If you want to add a new entry, begin the line with A, If you want to change an existing entry, begin the line with C, If you want to delete an existing entry, begin the line with D, NOTE: Only the D, is required, but the A, and C, may be used to help you track the changes you are making. Also, the A, C, and D are not casesensitive. 3. Save the file containing the changes and close the text editor. 4. Type the command: importcfg <filename>
or use this command in a script as needed. The results of this command will be included in the user.log file. If you prefer, you can redirect the output of the importcfg command to a separate file. To do this, use the command above, but include the name of the file where you want to direct the output. For example, if your change file is called newroute and your output file is my.log, you would type: importcfg newroute my.log
6-69
Making Configuration Changes via UNIX
EXS ExchangePlus Software Operations Guide
In this case, the log containing the results would be written to my.log. If the import was successful the log indicates how many records were imported in each table, along with the table name. If errors occurred, the log file indicates the name of the table which encountered problems. This command causes the changes to be made in the shared memory and the database files of the host. If you have a redundant system, and the changes are made to the master host, then they are also passed to the standby host.
6-70
EXS ExchangePlus Software Operations Guide
Procedure 49
Saving Configuration Changes via UNIX
Saving Configuration Changes via UNIX ExchangePlus provides a second method to save configuration changes via the UNIX command line. The command exportcfg causes the database tables to be written to the file name that you specify. It performs the same function as the Database>Export Tables selection in xmenu, but this command can be used from the UNIX command line or it can be incorporated into a script that can be run automatically without operator intervention. NOTE: The exportcfg command only exports tables on the host on which it is run. If you want to save data (export tables) on more than one host, you need to run exportcfg on each host separately.
Steps
1. Go to the terminal window and make a backup copy of your original switch.cfg file by typing: cd usr/isos/bin cp switch.cfg switch.cfg.bak
2. To copy the information in the shared memory tables to the switch.cfg file, type: exportcfg <filename>
The filename is the name of the file where you want to save the configuration data. You can specify switch.cfg in this file or any other filename. The data in the shared memory tables is saved to the file you specify when this command is completed.
6-71
Printing the Configuration
Procedure 50
EXS ExchangePlus Software Operations Guide
Printing the Configuration In some cases, you may want to get a printout of your configuration file to use as reference material.
Requirements
Steps
â&#x20AC;˘
There is a printer connected to the system that has been defined as the default printer. You should know the name of this printer and its location.
â&#x20AC;˘
To print the latest configuration information, you need to have saved that information using the Export Tables function as described in Procedure 47 Saving Configuration Changes via xmenu on page 6-65.
1. Go to the /usr/isos/bin directory by typing: cd /usr/isos/bin
2. Type: lp <configuration file name>
where <configuration file name> can be either switch.cfg or any file name that you have assigned to the latest configuration file.
6-72
EXS ExchangePlus Software Operations Guide
Procedure 51
Rolling Over CDRs Manually
Rolling Over CDRs Manually This procedure describes how to rollover Call Detail Record (CDR) files to save the data. Typically the cron.dat file will automatically rollover CDRs automatically at a fixed interval. If this occurs, you can set up a script to run on a regular basis to copy the CDR files to your billing system. However, this manual process allows you to rollover CDRs manually any time you need to. You would use this procedure when you want to look at call detail records for a specific time or for a specific call immediately. For information on the different CDR formats available, Release 2.x and Release 3.x, see â&#x20AC;&#x153;Appendix C. Call Detail Record Formatsâ&#x20AC;?
Steps
1. Pull down the Maint menu and select Rollover CDRs. The CDRs are rolled over, although there are no messages indicating that the rollover is complete. 2. To check your CDRs, go to the terminal window and type: cd /usr/isos/bin ls -l
This shows a list of all the files in the /usr/isos/bin directory. If you scan through the list, you should see some CDR files that include a time-stamp of the time when you performed the Rollover CDR function. For example, if you save files in text format on May 10, 1999 at 11:22:54, you may see: cdr.txt.19990510112254
Or if you save files in database format, you may see: cdr.dbf.19990510112254 cdr.ndx.19990510112254
The time-stamp is of the form: YYYYMMDDHHMMSS
For example, if the CDR was rolled over on May 10, 1999 at 11:22:54 AM, then the time-stamp would be: 19990510112254
3. Once the CDR files are rolled over, you can use whatever method you choose bring them into your billing system.
6-73
Rolling Over CDRs Manually
6-74
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
7 SS7, ISDN, and E1R2 Overview This chapter describes configuration procedures that you may need to perform in order to set up signaling for SS7, ISDN, or E1R2. The procedures described in this chapter assume that your switches and host(s) have been installed by Lucent Technologies and that you have a basic configuration in place that includes spans. These procedures explain how to make additions, changes, and deletions to the signaling used in your network. Refer to the Excel Switching Software Reference Manual, Version 5.3, Basic and Extended, for API messages that may affect the configuration of each protocol.
Caution
To ensure that you do not lose data in the event of a failure, you should save your configuration anytime you make changes to it.
Caution
When you are adding data to tables, be sure not to save a table that contains empty rows. Doing so may cause a core dump. If this happens, restart xmenu and resume your work.
The following lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 52 Setting up a Span to use SS7 Signaling
7-2
Procedure 53 Setting up a Span to use ISDN Signaling
7-25
Procedure 54 Setting up an E1 Span to use E1R2 Signaling
7-44
7-1
Setting up a Span to use SS7 Signaling
Procedure 52
EXS ExchangePlus Software Operations Guide
Setting up a Span to use SS7 Signaling This procedure describes how to set up a span to use SS7 signaling. See Appendix G for additional information on the SS7 signaling protocol.
Assumption
Steps
Before configuring SS7 signaling, be sure to: •
Set up trunk groups for SS7.
•
Configure trunks with CICs defined.
•
Configure routing for the SS7 trunk groups.
The sequence for configuring SS7 signaling is divided into the following steps: SS7 Step 1: Configuring Signaling Stacks SS7 Step 2: Configuring Signaling Link Sets SS7 Step 3: Configuring Signaling Links SS7 Step 4: Configuring Signaling Routes SS7 Step 5: Configuring CICs SS7 Step 6: Set Protocol Timers SS7 Step 7: Configuring Pass/Block of Optional Parameters
7-2
EXS ExchangePlus Software Operations Guide
SS7 Step 1
Setting up a Span to use SS7 Signaling
Configuring Signaling Stacks Configuring multiple signaling stacks allows the switch to interface with multiple SS7 networks. A stack consists of three layers: • • •
MTP Call Control User Part (ISUP or TUP) L3P
If using TUP, you must also configure L3P TUP. Each layer is assigned a variant per ITU-TS or ANSI standards. The switch supports up to four signaling stacks, identified by a Stack ID. There is no limitation on how you can allocate SS7 stacks among SS7 cards. For example, you can configure multiple signaling stacks on a single SS7 card or you can configure one signaling stack on each SS7 card, up to a maximum of four stacks per switch. There should be no more than two SS7 cards per switch. If there are two SS7 cards in a switch, the two cards will be configured as redundant cards. In other words, all stacks in one switch will reside in one SS7 card (either the single card or the primary card). Signaling stacks are assigned to SS7 objects (CICs, links, link sets, routes) as each object is configured. To set up the signaling stack protocol for the designated stack, pull down the SS7 menu and select SS7 Area. The SS7 Area Table window appears (Figure 7-1).
Figure 7-1 SS7 Area Table
Adding or Changing Signaling Stacks
1. To add a new SS7 stack or to change an existing SS7 stack, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new SS7 stack on the new line or you can copy an existing SS7 stack definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row.
7-3
Setting up a Span to use SS7 Signaling
EXS ExchangePlus Software Operations Guide
3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy the definition of SS7 Stack 2 on Node 1 to SS7 Stack 3 on Node 2, you may want to change the Protocol from ANSI to ITU. 5. To change an existing SS7 Stack definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: The node and stack are part of the key. Do not change these fields. 6. The following table lists the fields in the table that you need to complete: Parameter
Value
Node
7-4
Description Node ID
Stack
1-4
Stack ID
Protocol
usually ITU (for E1) ANSI (for T1) PTUP (for ITU TUP or Philippine TUP)
Variant
0=ANSI 1=ITU
Valid for ITU only. In ITU, the variant determines the point code format. 0=3-8-3 1=6-4-4. For ANSI the point code format is always 8-8-8.
OPC
network-cluster-node
Enter the Originating Point Code (OPC) for this stack in the form of â&#x20AC;&#x153;network-cluster-nodeâ&#x20AC;?. For 24-bit point codes (ANSI), the OPC must be in the range of 0x000000000x00FFFFFF. For 14-bit point codes (ITU) the range is 0x000000000x00003FFF.
PID
1-20
Protocol ID. 1-10 indicate the PPL Protocol ID of a custom protocol. Values 11-20 indicate the default SS7 protocol.
EXS ExchangePlus Software Operations Guide
Setting up a Span to use SS7 Signaling
Parameter
Value
Description
NI
0=International 1=Spare 01 2=National 3=Spare 11
Network Indicator. Loads the Network Indicator in applicable outgoing SS7 messages.
Load PPL
Yes=custom PPL file will be loaded when the stack is configured. No=No custom PPL file will be loaded
Used to specify whether or not a custom PPL file will be loaded when the specified stack is configured. If you select Yes in this field, the name of the file containing the API messages to be loaded must be of the format stackpplx.cfg, where x is the stack ID number from 1-4. You also need to put the raw API messages in the stackpplx.cfg file and place that file in the /usr/isos/bin directory.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the SS7 Area table, pull down the File menu and select Save. 8. When you are done editing the SS7 Area table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the SS7 Area table where you can save your changes.
7-5
Setting up a Span to use SS7 Signaling
Deleting Signaling Stacks
EXS ExchangePlus Software Operations Guide
1. Pull down the SS7 menu and select SS7 Area. The SS7 Area Table window appears (Figure 7-2). This table show all the routes that have been configured for this node. You can delete any of these stacks.
Figure 7-2 SS7 Area Table
2. To delete an SS7 stack, the line containing the definition from the SS7 Area table. Use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save changes, pull down the File menu and select Save. 4. When you are done editing the SS7 Area table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the SS7 Area table where you can save your changes.
7-6
EXS ExchangePlus Software Operations Guide
SS7 Step 2
Setting up a Span to use SS7 Signaling
Configuring Signaling Link Sets A signaling link is an abstract path between the switch and an adjacent point code, to which physical signaling links are added. The same signaling stack must be assigned to all links in a link set. A typical configuration consists of two link sets, but you are not limited to this number. Signaling links in a link set are â&#x20AC;&#x153;load sharing"; that is, signaling traffic is distributed equally on the links to optimize efficiency. When you configure multiple stacks on an SS7 card, the link set IDs assigned to each signaling stack must be different. You can not have link set 1 assigned to both Stack 1 and Stack 2. However, if you configure multiple signaling stacks on different SS7 cards, the link set IDs assigned to the stacks are independent. Link set ID 1 can be assigned to Stack 1 on one card and to Stack 2 on another card. To set up the signaling link sets for a stack, pull down the SS7 menu and select SS7 Link Set Info. The SS7 Link Set Information Table window appears (Figure 7-3).
Figure 7-3 Link Set Information Table
Adding or Changing Signaling Link Sets
1. To add a new link set or to change an existing one, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new link set on the new line or you can copy an existing link set definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste.
7-7
Setting up a Span to use SS7 Signaling
EXS ExchangePlus Software Operations Guide
4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy to definition of link set 1 to link set 3, you may want to change the Adjacent Point Code for the new link set. 5.
To change an existing link set definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: The node, stack, and linkset are part of the key. Do not change these fields.
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Node
Description Node ID
Stack
1-4
Stack ID for the node
Link Set
0-35
Link Set ID
APC
For ANSI: network-cluster-node
Adjacent Point Code. The point code of the equipment on the other end of the links (usually a signal transfer point (STP)). The APC is entered in the form “network-cluster-node” for ANSI standard or “zone-area-node” for ITU. NOTE: You are typically given your point codes and have little or no choice in selecting them.
For ITU: zone-area-node
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Link Set Information table, pull down the File menu and select Save. 8. When you are done editing the Link Set Information table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Link Set Information table where you can save your changes.
7-8
EXS ExchangePlus Software Operations Guide
Deleting Signaling Link Sets
Setting up a Span to use SS7 Signaling
1. Pull down the SS7 menu and select SS7 Link Set Info. The Link Set Information Table window appears (Figure 7-4). This table show all the routes that have been configured for this node. You can delete any of these link sets.
Figure 7-4 Link Set Information Table
2. To delete a link set, you delete the line containing the definition from the Link Set Information table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Link Set Information table, pull down the File menu and select Save. 4. When you are done editing the Link Set Information table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Link Set Information table where you can save your changes.
7-9
Setting up a Span to use SS7 Signaling
SS7 Step 3
EXS ExchangePlus Software Operations Guide
Configuring Signaling Links A signaling link is a point-to-point connection between two SS7 point codes (for example, between a switch and an STP). A physical location in the switch (timeslot) and a previously configured Signaling Link Set are assigned to each signaling link. Each SS7 card supports up to 16 signaling links in increments of two, depending on the model and license you purchase. For a redundant SS7 card pair, support is up to 32 links, but Link ID numbers 17-32 are assigned to the secondary card. NOTE : When you configure multiple stacks on one SS7 card, the Link IDs assigned to the signaling stacks are independent. For example, if Link ID 1 can be assigned to Stack 1, it cannot be assigned to Stack 2. To set up signaling links, pull down the SS7 menu and select Link Info. The Link Info Table window appears (Figure 7-5).
Figure 7-5 Link Information Table
Adding or Changing Signaling Links
1. To add a new signaling link or to change an existing signaling link, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new signaling link on the new line or you can copy an existing signaling link definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy to definition of signaling link 2 to signaling link 3, you may want to change the Rate from 56K to 64K.
7-10
EXS ExchangePlus Software Operations Guide
5.
Setting up a Span to use SS7 Signaling
To change an existing signaling link definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: The node, stack, and link are part of the key. Do not change these fields.
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Node
Description Node ID
Stack
1-4
Stack ID
Link
1-16 for primary card 17-32 for the secondary card
Link ID
Span, Channel
integer
The span and channel number (or timeslot) that is assigned to the signaling link.
SLC
0-15
Signaling Link Code. The SLC is assigned to the link that is sent as part of the protocol. It must be the same on both ends of the link. This value is typically assigned by the SS7 provider.
Rate
56K 64K (The K must be uppercase.)
The data rate of the signaling link. NOTE: The K is case-sensitive; it must be uppercase. If you enter anything besides 64K, the value will be set to 56K.
Link Set
1-32
The link set for the specific link. Signaling link sets 1-32. Deconfigure the specified signaling link
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Link Information table, pull down the File menu and select Save. 8. When you are done editing the Link Information table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Link Information table where you can save your changes.
7-11
Setting up a Span to use SS7 Signaling
Deleting Signaling Links
EXS ExchangePlus Software Operations Guide
1. Pull down the SS7 menu and select Link Info. The Link Information Table window appears (Figure 7-6). This table show all the routes that have been configured for this node. You can delete any of these links.
Figure 7-6 Link Information Table
2. To delete a signaling link, you delete the line containing the definition from the SS7 Area table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Link Information table, pull down the File menu and select Save. 4. When you are done editing the Link Information table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Link Information table where you can save your changes.
7-12
EXS ExchangePlus Software Operations Guide
SS7 Step 4
Setting up a Span to use SS7 Signaling
Configuring Signaling Routes A signaling route defines a path between a signaling stack and a Destination Point Code (DPC.) Each SS7 card supports up to 255 routes, identified by a Route ID ranging from 0x00 to 0xFE. When you configure multiple stacks on an SS7 card, the Route IDs assigned to each signaling stack must be different. For example, if Route ID is assigned to Stack 1, it cannot also be assigned to Stack 2. However, if you configure multiple signaling stacks on different SS7 cards, the Route IDs assigned to the signaling stacks are independent. For example, Route ID 1 can be assigned to Stack 1 on one card and Stack 2 on another card. To set up the signaling routes, pull down the SS7 menu and select Route Setup. The Route Setup Table window appears (Figure 7-7).
Figure 7-7 Route Setup Table
Adding or Changing Signaling Routes
1. To add a new signaling route or to change an existing signaling route, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new signaling route on the new line or you can copy an existing signaling route definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste.
7-13
Setting up a Span to use SS7 Signaling
EXS ExchangePlus Software Operations Guide
4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy to definition of signaling route 2 to signaling route 3, you may want to change the Priority from 1 to 6. 5.
To change an existing signaling route definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: The node, stack, and route are part of the key. Do not change these fields. The following table lists the fields in the table that you need to complete: Parameter
Value
Node
Description Node ID
Stack
1-4
Stack ID
Route
1-256
Route ID
DPC
x-x-x
Destination Point Code. The endpoint of the signaling route.
Link Set
1-32
The link set used to get to the DPC. The call may go on any available CIC within the link set.
Priority
1-24 1=lowest 24=highest
The priority is used to create primary and secondary routes to a DPC. If priority is equal, routes will load share.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 6. To save the changes you make to the Route Setup table, pull down the File menu and select Save. 7. When you are done editing the Route Setup table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Route Setup table where you can save your changes.
7-14
EXS ExchangePlus Software Operations Guide
Deleting Signaling Routes
Setting up a Span to use SS7 Signaling
1. Pull down the SS7 menu and select Route Setup. The Route Setup Table window appears (Figure 7-8). This table show all the routes that have been configured for this node. You can delete any of these signaling routes.
Figure 7-8 Route Setup Table
2. To delete a signaling route, you delete the line containing the definition from the Route Setup table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Route Setup table, pull down the File menu and select Save. 4. When you are done editing the Route Setup table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Route Setup table where you can save your changes.
7-15
Setting up a Span to use SS7 Signaling
SS7 Step 5
EXS ExchangePlus Software Operations Guide
Configuring CICs Voice circuits controlled by SS7 signaling links are identified by a Circuit Identification Code (CIC). A specified voice circuit is identified in the network by its unique DPC-CIC combination. CICs can be assigned to any timeslot in the system. CICs in a CIC group must be on the same span. CICs and signaling links can reside on the same span. The CIC group ID can start from “1” for any stack. For example, stack 1 and stack 2 can both have CIC groups 1 to 10. For an E1 channel, channels 15, 16, and 31 (only if used as a voice channel) should be in separate CIC groups. To set up CIC groups, pull down the SS7 menu and select CIC Group Setup. The CIC Group Setup Table window appears (Figure 7-9).
Figure 7-9 CIC Group Setup Table
7-16
EXS ExchangePlus Software Operations Guide
Adding or Changing CICs
Setting up a Span to use SS7 Signaling
1. To add a new CIC group or to change an existing CIC group, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new CIC group on the new line or you can copy an existing CIC group definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy to definition of CIC Group 2 to CIC Group 3, you may want to change the DPC from 2173-0 to 2-190-1. 5.
To change an existing CIC group definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: The node, stack, and route are part of the key. Do not change these fields.
7-17
Setting up a Span to use SS7 Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete:
Parameter
Value
Node
Description Node ID
Stack
1-4
Stack ID
CIC Group
any number that can be addressed in a two byte field
DPC
x-x-x
Destination Point Code
TG
integer
Trunk Group
BSPN
integer
Beginning Span number. Logical Span ID of first CIC in group.
BCHN
integer
Beginning Channel Number. Logical channel number of first CIC in group.
BCIC
integer
Beginning CIC Number. ID for the first CIC in group. It must be unique.
#CICS
integer
The number of CICs in a group. The number cannot extend beyond one span.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the CIC Group Setup table, pull down the File menu and select Save. 8. When you are done editing the CIC Group Setup table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the CIC Group Setup table where you can save your changes.
7-18
EXS ExchangePlus Software Operations Guide
Deleting CICs
Setting up a Span to use SS7 Signaling
1. Pull down the SS7 menu and select CIC Group Setup. The CIC Group Setup Table window appears (Figure 7-10). This table shows all the CIC Groups that have been configured. You can delete any of these CIC groups.
Figure 7-10 CIC Group Setup Table
2. To delete a CIC Group, you delete the line containing the definition from the CIC Group Setup table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the CIC Group Setup table, pull down the File menu and select Save.
7-19
Setting up a Span to use SS7 Signaling
EXS ExchangePlus Software Operations Guide
4. When you are done editing the CIC Group Setup table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the CIC Group Setup table where you can save your changes.
7-20
EXS ExchangePlus Software Operations Guide
SS7 Step 6
Setting up a Span to use SS7 Signaling
Set Protocol Timers ISUP, MTP2 and MTP3 timers are protocol timers that are usually configured if the network does not conform to specified timer values. They are configured with the PPL Timer Configure API. If you select any of these timer configurations, the following command line appears: Enter CompId (hex), TimerId:
You need to enter the appropriate timer ID for the associated protocol. The CompId (component ID) and TimeId for that component can be found in the Excel Switching Software Reference Manual, Version 5.3, Chapter 10, â&#x20AC;&#x153;PPL Informationâ&#x20AC;?. The timer value is in 10 ms. If the wrong TimerId is entered or none is entered, the following date-stamped messages will be displayed: 01/05/00 15:19:12 NULL parameter found in config line 01/05/00 15:19:12 Invalid CompId
7-21
Setting up a Span to use SS7 Signaling
SS7 Step 7
EXS ExchangePlus Software Operations Guide
Configuring Pass/Block of Optional Parameters Optional SS7 message parameters in ISUP IAM, CPG, ACM and CONNECT messages can be passed with, or blocked from the outgoing message. You specify the optional parameters to pass or block in the configuration file ss7optparm.cfg in the directory /usr/isos/bin. NOTES: •
Some parameters require use of the menu -s (support mode). Lucent recommends that you consult with Lucent Technologies Technical Support before you configure the passing or blocking of optional parameters using the support mode.
•
If you plan to pass ACM messages, the ISUP default configuration must be loaded by Lucent Technologies Technical Support.
The ss7optparm.cfg configuration file has the format: ; Define the optional parameters that need to be passed through here. ; MsgId (Hex), ParmId (hex), PassOrNot (1/0) 1, 1, 1, 1,
8, 1d, 3, C5,
1 1 1 1
The first hexadecimal number in the line entry indicates the message identifier; a 1 indicates an IAM message. The second hexadecimal number is the parameter identification, such as C5. The third number is either a 1 (to pass), or 0 (to block) the optional parameter. NOTE: The specifications ANSI T1.113 (Signaling System 7 ISDN User Part) and ITU Q.763 (Signaling System No. 7 - ISDN user part formats and codes) define the parameter IDs. Additionally, the Q.763 specification defines the ISUP IAM and CPG Message IDs. Example: To pass the Carrier Identification parameter in an outgoing IAM message when the incoming message includes it, type 1, C5, 1 as shown in the last line in the above ss7optparm.cfg file. The first 1 indicates an IAM message, the C5 (0xC5) indicates the Carrier Identification parameter, and the second 1 indicates that the parameter will be passed. The first line in the configuration file indicates that optional Forward Call Indicator (0x8) is passed. Refer to the EXS Switch Software Developer’s Guide Part 2: Common Channel Signaling for information on the optional message parameters.
7-22
EXS ExchangePlus Software Operations Guide
Setting up a Span to use SS7 Signaling
NOTE: Some optional parameters require a change in the ISUP format on the card to recognize the parameter. Refer to the SS7 ISUP Message Format Configure in the API Reference Guide for details.
7-23
Setting up a Span to use SS7 Signaling
Passing and Blocking of Optional Parameters
EXS ExchangePlus Software Operations Guide
1. Using a text editor such as vi, create or edit the optional parameters file ss7optparm.cfg in the directory /usr/isos/bin if the file does not already exist. 2. Configure the file with with the optional parameters you require to be passed or blocked by typing a 1 or 0 in the third field for each parameter line as described above. Then, save the file and quit vi. 3. To activate the new or changed entries while the system is running, pull down the SS7 menu and select Reload ss7 opt parm. If the system is not running, the system will read the ss7optparm.cfg file during startup.
7-24
EXS ExchangePlus Software Operations Guide
Procedure 53
Setting up a Span to use ISDN Signaling
Setting up a Span to use ISDN Signaling The ExchangePlus ISDN PRI implementation is based on ITU-T Q.921 and Q.931 specifications. Each implemented variant references the appropriate interface document supplied by the equipment manufacturer. The interface document is usually a variant of the ITU-T recommendations. Since each manufacturer supports different services, the host manages the information to send and receive in specific messages. This lets you access many features and services at the host layer. Each ISDN PRI card supports 32 D channels. Each D channel provides the High Data Link Control (HDLC) communications over T1 or E1 on one timeslot on the span. Each D channel controls up to nine other spans in addition to the span on which it is located. Depending upon the provisioning requirements, you can have one D channel per span [Facility Associated Signaling (FAS)], or one D channel managing 10 spans [Non-Facility Associated Signaling (NFAS)]. You can control a total of 32 spans using all FAS D channels, or 10 spans per NFAS D channel (to a maximum of 64 per system). You can mix both FAS and NFAS D channels on a card with each supporting a different variant. NFAS spans can be configured dynamically during call processing. You can insert multiple ISDN PRI cards in any line card slot in the switch. ExchangePlus recommends using Channel 24 (T1) or channel 31 (E1) as a D channel. It currently does not support using Channel 1 as a D channel.
Assumption
Steps
Before configuring ISDN, be sure to: •
Set up trunk groups for ISDN
•
Configure trunks
•
Configure routing for the ISDN trunk groups
The sequence for configuring ISDN is divided into the following steps: ISDN Step 1: Configuring D Channels ISDN Step 2: Configuring Backup D Channels ISDN Step 3: Configuring D Channel Attributes ISDN Step 4: Configuring D Channel Facilities ISDN Step 5: Configuring B Channel Groups ISDN Step 6: Configuring B Channel Attributes
7-25
Setting up a Span to use ISDN Signaling
ISDN Step 1
EXS ExchangePlus Software Operations Guide
Configuring D Channels Each D channel provides the High Data Link Control (HDLC) communications over T1 or E1 on one timeslot on the span. Each D channel controls up to nine other spans in addition to the span on which it is located. The following describes how to assign D channels and configure the connection type. Pull down the ISDN menu and select D Channel. The D Channel Table window appears (Figure 7-11).
Figure 7-11 D Channel Table
Adding or Changing D Channels
1. To add a new D channel or to change an existing D channel, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new D channel on the new line or you can copy the existing D channel from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy the definition of D Channel 1 to D Channel 2, you may want to change the Span from 2 to 3. 5. To change an existing D channel definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: D Chan is the key and should not be changed.
7-26
EXS ExchangePlus Software Operations Guide
Setting up a Span to use ISDN Signaling
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Slot
integer
The slot containing the ISDN card controlling this D channel.
Span
integer
The logical span containing the D channel.
Chan
integer
The logical channel containing the D channel - usually 24 (or maybe 31). For most applications, the D channel resides on the 24th channel of the T1 span and Timeslot 16 of the E1 span.
SType
T1, E1
Indicates whether the ISDN PRI spans are T1 or E1.
DChan
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the D Channel table, pull down the File menu and select Save. 8. When you are done editing the D Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the D Channel table where you can save your changes.
7-27
Setting up a Span to use ISDN Signaling
Deleting D Channels
EXS ExchangePlus Software Operations Guide
1. Pull down the ISDN menu and select D Channel. The D Channel Table window appears (Figure 7-12). This table shows all the D channels that have been configured. You can delete any of these D channels.
Figure 7-12 D Channel Table
2. To delete a D channel, you delete the line containing the definition from the D channel table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the D Channel table, pull down the File menu and select Save. 4. When you are done editing the D Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the D Channel table where you can save your changes.
7-28
EXS ExchangePlus Software Operations Guide
ISDN Step 2
Setting up a Span to use ISDN Signaling
Configuring Backup D Channels A backup D channel will take over signaling if the primary D channel fails. The standby D channel maintains active calls. This option is only applicable when using NFAS. D channel backup is supported only on T1 cards. NOTES: •
Skip this section if D channel backup is not being used.
•
The Backup is added to support ISDN PRI card D channel backup feature. It is only supported in IDSN PRI card, the ST1LC card, and the Tone card, and only for NFAS mode.
•
A primary D channel has at most one backup. The PrimaryDChanID is the backup D channel’s corresponding primary D channel’s ID as assigned in DCHANNEL.
Pull down the ISDN menu and select D Channel Backup. The D Channel Backup Table window appears (Figure 7-13).
Figure 7-13 Backup D Channel Table
Adding or Changing Backup D Channels
1. To add a new backup D channel or to change an existing backup D channel, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new backup D channel on the new line or you can copy the existing backup D channel from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste.
7-29
Setting up a Span to use ISDN Signaling
EXS ExchangePlus Software Operations Guide
4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy the definition of Backup D Channel 1 to Backup D Channel 2, you may want to change the Span from 2 to 3. 5. To change an existing backup D channel definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: ID is the key and should not be changed. 6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
DChan
integer
The D channel being backed up.
Span #
integer
The logical span containing the backup D channel.
Chan
integer
The logical channel containing the backup D channel - usually 24
Facility
1-9
The facility number assigned to span number. Use the secondary facility (1) to configure the backup D channel. The facility number must not be in conflict with the facility assignment in FACILITIES. That is, if the span is assigned Facility 1, it should not be assigned any other facility number in FACILITIES
ID
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Backup D Channel table, pull down the File menu and select Save. 8. When you are done editing the Backup D Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Backup D Channel table where you can save your changes.
7-30
EXS ExchangePlus Software Operations Guide
Deleting Backup D Channels
Setting up a Span to use ISDN Signaling
1. Pull down the ISDN menu and select D Channel Backup. The Backup D Channel Table window appears (Figure 7-14). This table shows all the backup D channels that have been configured. You can delete any of these backup D channels.
Figure 7-14 Backup D Channel Table
2. To delete a backup D channel, you delete the line containing the definition from the Backup D Channel table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Backup D Channel table, pull down the File menu and select Save. 4. When you are done editing the Backup D Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Backup D Channel table where you can save your changes.
7-31
Setting up a Span to use ISDN Signaling
ISDN Step 3
EXS ExchangePlus Software Operations Guide
Configuring D Channel Attributes This procedure describes how to configure D channel attributes (parameters). The same D channel can appear in multiple lines if more attributes need to be assigned. NOTE: ExchangePlus now only supports the ISDN PRI card. Pull down the ISDN menu and select D Channel Attributes. The D Channel Attributes Table window appears (Figure 7-15).
Figure 7-15 D Channel Attributes Table
Adding or Changing D Channel Attributes
1. To add new D channel attributes or to change an existing D channel attributes, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the new attributes for the D channel on the new line or you can copy the existing attributes for the D channel from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. NOTE: When entering values for “entity” or “value”, enter decimal values. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. For example, if you copy the attributes of D Channel 1 to D Channel 2, you may want to change the Entity/Value pair from 1:35 to 2:6. 5. To change the attributes of an existing D channel, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
7-32
EXS ExchangePlus Software Operations Guide
Setting up a Span to use ISDN Signaling
NOTE: Index is the key and should not be changed. 6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the D Channel Attributes table.
Entity
hex number
The entity in the Entity:Value pair. To determine the entity, refer to Excel Switching Software Reference Manual, Version 5.3 The revision of the manual should match the software revision you are running on the switch. Refer to the 0x60 ISDN Interface Configure message.
Value
hex number
The entity value in the Entity:Value pair. To determine the entity value, refer to Excel Switching Software Reference Manual, Version 5.3 The revision of the manual should match the software revision you are running on the switch. Refer to the 0x60 ISDN Interface Configure message.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the D Channel Attributes table, pull down the File menu and select Save. 8. When you are done editing the D Channel Attributes table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the D Channel Attributes table where you can save your changes.
7-33
Setting up a Span to use ISDN Signaling
Deleting D Channel Attributes
EXS ExchangePlus Software Operations Guide
1. Pull down the ISDN menu and select D Channel Attributes. The D Channel Attributes Table window appears (Figure 7-16). This table shows all the D channel attributes that have been configured. You can delete any of these D channel attributes.
Figure 7-16 D Channel Attributes Table
2. To delete D channel attributes, you delete the line containing the definition from the D Channel Attributes table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the D Channel Attributes table, pull down the File menu and select Save. 4. When you are done editing the D Channel Attributes table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the D Channel Attributes table where you can save your changes.
7-34
EXS ExchangePlus Software Operations Guide
ISDN Step 4
Setting up a Span to use ISDN Signaling
Configuring D Channel Facilities The procedures describes and defines the NFAS facility (FAC) list. The facility list (FAC1 to FAC9) is the list of spans associated with and controlled by a D channel. Each primary D channel assumes it is the span on which the D channel is located is the Facility 0. If a D channel is configured as FAS, then there should be no facility list for the D channel; i.e., the facility list for that D channel should be empty. For FAC1 through FAC9, each facility gets assigned a span ID number. For example, â&#x20AC;&#x153;FAC1 is 4â&#x20AC;? means that Facility 1 is span 4. You can add up to 9 facilities, excluding the span (Facility 0) where the D channel is located. Pull down the ISDN menu and select D Channel Facilities. The D Channel Facilities Table window appears (Figure 7-17).
Figure 7-17 D Channel Facilities Table
Adding or Changing D Channel Facilities
1. To add new D channel facilities or to change existing D channel facilities, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new D channel on the new line or you can copy existing D channel facilities from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. The value is the span ID of that facility. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5. To change existing D channel facilities, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. 7-35
Setting up a Span to use ISDN Signaling
EXS ExchangePlus Software Operations Guide
NOTE: DChan is the key and should not be changed. 6. The following table lists the fields in the table that you need to complete: Parameter
Value
DChan
Description The D channelâ&#x20AC;&#x2122;s ID. Always Facility 0.
Fac1
integer
The Span ID for Facility 1.
Fac2-Fac9
integer
The Span ID for Facilities 2-9.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the D Channel Facilities table, pull down the File menu and select Save. 8. When you are done editing the D Channel Facilities table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the D Channel Facilities table where you can save your changes.
7-36
EXS ExchangePlus Software Operations Guide
Deleting D Channel Facilities
Setting up a Span to use ISDN Signaling
1. Pull down the ISDN menu and select D Channel Facilities. The D Channel Facilities Table window appears (Figure 7-18). This table shows all the D channel facilities that have been configured. You can delete any of these D channel facilities.
Figure 7-18 D Channel Facilities Table
2. To delete D channel facilities, you delete the line containing the definition from the D Channel Facilities table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the D Channel Facilities table, pull down the File menu and select Save. 4. When you are done editing the D Channel Facilities table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the D Channel Facilities table where you can save your changes.
7-37
Setting up a Span to use ISDN Signaling
ISDN Step 5
EXS ExchangePlus Software Operations Guide
Configuring B Channel Groups The following describes how to define B channel groups associated with a D channel. A B channel or â&#x20AC;&#x153;bearerâ&#x20AC;? channel is a component of the ISDN interface. It is full duplex at 64,000 bps. B channels are circuit-switched and can be configured for either voice or data. Pull down the ISDN menu and select B Channel. The B Channel Table window appears (Figure 7-19).
Figure 7-19 B Channel Table
Adding or Changing B Channel Groups
1. To add a new B channel or to change an existing B channel, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new D Channel on the new line or you can copy the existing B channel from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5. To change an existing B channel definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: OutBgroup is the key and should not be changed.
7-38
EXS ExchangePlus Software Operations Guide
Setting up a Span to use ISDN Signaling
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
DChan
integer
The primary D channel ID as assigned in DCHANNEL.
SSpan#
integer
Starting Span ID
SChan#
integer
Starting channel number
OutBGroup
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the B Channel table, pull down the File menu and select Save. 8. When you are done editing the B Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the B Channel table where you can save your changes.
7-39
Setting up a Span to use ISDN Signaling
Deleting B Channel Groups
EXS ExchangePlus Software Operations Guide
1. Pull down the ISDN menu and select B Channel. The B Channel Table window appears (Figure 7-20). This table shows all the B channels that have been configured. You can delete any of these B channels.
Figure 7-20 B Channel Table
2. To delete B channels, you delete the line containing the definition from the B Channel table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the B Channel table, pull down the File menu and select Save. 4. When you are done editing the B Channel table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the B Channel table where you can save your changes.
7-40
EXS ExchangePlus Software Operations Guide
ISDN Step 6
Setting up a Span to use ISDN Signaling
Configuring B Channel Attributes This procedure describes how to set outgoing B channel attributes (parameters). The Entity:Value pairs follow the same rules as the D channel attributes. NOTE: ExchangePlus now only supports the ISDN PRI card. Pull down the ISDN menu and select B Channel Attributes. The B Channel Attributes Table window appears (Figure 7-21).
Figure 7-21 B Channel Attributes Table
Adding or Changing B Channel Attributes
1. To add new B channel attributes or to change existing D channel attributes, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in new attributes for the B channel on the new line or you can copy attributes for an existing B channel from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Fill in values for each field in the new row. NOTE: When entering values for entity” and “value”, enter in decimal values. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5. To change the attributes for an existing B channel, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: Index is the key and should not be changed.
7-41
Setting up a Span to use ISDN Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
A key that uniquely identifies an entry in the B Channel Attributes table.
Entity:Value
The Entity:Value pair is in hexadecimal in two digits. To determine the entity and entity value, refer to Excel Switching Software Reference Manual, Version 5.3. The revision of the manual should match the software revision you are running on the switch. Refer to the 0xC8 B Channel Configure message.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the B Channel Attributes table, pull down the File menu and select Save. 8. When you are done editing the B Channel Attributes table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the B Channel Attributes table where you can save your changes.
7-42
EXS ExchangePlus Software Operations Guide
Deleting B Channel Attributes
Setting up a Span to use ISDN Signaling
1. Pull down the ISDN menu and select B Channel Attributes. The B Channel Attributes Table window appears (Figure 7-22). This table shows all the B channel attributes that have been configured. You can delete any of these B channel attributes.
Figure 7-22 B Channel Attributes Table
2. To delete B channel attributes, you delete the line containing the definition from the B Channel Attributes table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the B Channel Attributes table, pull down the File menu and select Save. 4. When you are done editing the B Channel Attributes table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the B Channel Attributes table where you can save your changes.
7-43
Setting up an E1 Span to use E1R2 Signaling
Procedure 54
EXS ExchangePlus Software Operations Guide
Setting up an E1 Span to use E1R2 Signaling This procedure describes how to set up an E1 span to use E1R2 signaling. NOTE: For the trunk group that uses E1 R2/DTMF, you should add PPL to the TYPE and E1R2 as the FLAG (even if it is E1 DTMF). You’ll also need to assign protocol ID in the PRTCLID field if it is not the standard CCITT R2 (the protocol ID can be found in the PPL DSD file for the variant). If it is the CCITT R2 standard, you can use 0 as the PRTCLID. You then need to assign Inseize (INSZ) and Outseize (OUSZ) values, which are indices to the INSEIZECONTROL and OUTSEIZECONTROL, respectively.
Assumption
The trunk groups must be added if they do not already exist. ExchangePlus provides a default E1R2 configuration that should work in most cases. If it does not, configure E1R2 signaling as follows: Before configuring E1R2, be sure to:
Steps
•
Set up trunk groups for E1R2.
•
Configure trunks.
•
Configure routing for the E1R2 trunk groups.
The sequence for configuring E1R2 signaling is divided into the following steps: E1R2 Step 1: Configuring Stage Parameters E1R2 Step 2: Configuring Inseize Instructions E1R2 Step 3: Configuring Outseize Instructions E1R2 Step 4: Configuring Inseize Control E1R2 Step 5: Configuring Outseize Control E1R2 Step 6: Configuring PPL Transmit Sig E1R2 Step 7: Configuring PPL Timers E1R2 Step 8: Configuring PPL Control
7-44
EXS ExchangePlus Software Operations Guide
E1R2 Step 1
Setting up an E1 Span to use E1R2 Signaling
Configuring Stage Parameters E1R2 signaling has specific Stage Parameters. A stage is set during call setup, after the upstream switch sends some data to the downstream switch, and before the data is acknowledged. The default E1R2 configuration in the initial switch configuration file already defines 13 different types of Stage Parameters, and they should cover most cases. To set up the Stage Parameters for the designated PPL, pull down the E1R2 menu and select Stage Parm. The Stage Parameters Table window appears (Figure 7-23).
Figure 7-23 Stage Parameters Table
Adding or Changing Stage Parameters
1. To add a new Stage Parameter or to change an existing Stage Parameter, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new Stage Parameter on the new line or you can copy an existing Stage Parameter definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy, pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
To change an existing Stage Parameter definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes. NOTE: Index is the key and should not be changed.
7-45
Setting up an E1 Span to use E1R2 Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete (for more information on the Method, Data, and Type fields, see Excel Switching Software Reference Manual, Release 5.3, Chapter 4): Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the Stage Parameters table.
Str#
integer
Number of strings for the stage.
Timeout
integer
The timeout value for receiving digits in the stage (in 10ms)
AST
3 for E1R2 1 for E1 DTMF
Address signaling types for the stage.
Mthd1 (String1)
Usually 1 for Fixed Number of Digits
String collection method for string 1
Data1 (String1)
The number of digits (for E1R2) 0xFF (if the number of digits is unknown or varies)
String collection data for String 1
Type1 (String1)
CLD - called party number CLG - calling parting number (ANI) CATCLG - category+ANI, CLDRM - remaining digits of called party number CAT - category digit, CRI - Country routing information
The type of the string1 digits
Mthd2 (String2)
Usually 1 for Fixed Number of Digits
String collection method for string2, if any.
Data2 (String2)
The number of digits (for E1R2) 0xFF (if the number of digits is unknown or varies)
String collection data for string2, if any.
Type2 (String2)
CLD - called party number CLG - calling parting number (ANI) CATCLG - category+ANI, CLDRM - remaining digits of called party number CAT - category digit, CRI - Country routing information
The type of the string2 digit, if any.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved.
7-46
EXS ExchangePlus Software Operations Guide
Setting up an E1 Span to use E1R2 Signaling
7. To save the changes you make to the Stage Parameters table, pull down the File menu and select Save. 8. When you are done editing, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Stage Parameters table where you can save your changes.
7-47
Setting up an E1 Span to use E1R2 Signaling
Deleting Stage Parameters
EXS ExchangePlus Software Operations Guide
1. Pull down the E1R2 menu and select Stage Parm. The Stage Parameters Table window appears (Figure 7-24). This table shows all the Stage Parameters that have been configured. You can delete any of these Stage Parameters.
Figure 7-24 Stage Parameters Table
2. To delete Stage Parameters, you delete the line containing the definition from the Stage Parameters table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Stage Parameters table, pull down the File menu and select Save. 4. When you are done editing the Stage Parameters table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Stage Parameters table where you can save your changes.
7-48
EXS ExchangePlus Software Operations Guide
E1R2 Step 2
Setting up an E1 Span to use E1R2 Signaling
Configuring Inseize Instructions This section lists the Inseize Instructions you may use. To set up the Inseize Instructions for the designated PPL, pull down the E1R2 menu and select Inseize Instructions. The Inseize Instructions Table window appears (Figure 7-25). The default E1R2 configuration in the initial switch configuration file already defines twelve different types of Inseize Instructions, and they should cover most cases.
Figure 7-25 Inseize Instructions Table
Adding or Changing Inseize Instructions
1. To add a new Inseize Instruction or to change an existing Inseize Instruction, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new Inseize Instruction on the new line or you can copy an existing Inseize Instruction definition from that table and paste it into the blank line. 2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
To change an existing Inseize Instruction definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
7-49
Setting up an E1 Span to use E1R2 Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the Inseize Instructions table.
Type
integer
Inseize instruction type
Data1
decimal number (not hex)
Data field
Data2
decimal number (not hex)
Data field
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Inseize Instructions table, pull down the File menu and select Save. 8. When you are done editing the Inseize Instructions table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Inseize Instructions table where you can save your changes.
7-50
EXS ExchangePlus Software Operations Guide
Deleting Inseize Instructions
Setting up an E1 Span to use E1R2 Signaling
1. Pull down the E1R2 menu and select Inseize Instruction. The Inseize Instructions Table window appears (Figure 7-26). This table shows all the Inseize Instructions that have been configured. You can delete any of these Inseize Instructions.
Figure 7-26 Inseize Instructions Table
2. To delete Inseize Instructions, you delete the line containing the definition from the Inseize Instructions table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Inseize Instructions table, pull down the File menu and select Save. 4. When you are done editing the Inseize Instructions table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Inseize Instructions table where you can save your changes.
7-51
Setting up an E1 Span to use E1R2 Signaling
E1R2 Step 3
EXS ExchangePlus Software Operations Guide
Configuring Outseize Instructions The default E1R2 configuration in the initial switch configuration file already defines five different types of Outseize Instructions, and they should cover most cases. To set up the Outseize Instructions for the designated PPL, pull down the E1R2 menu and select Outseize Instructions. The Outseize Instructions Table window appears (Figure 7-27).
Figure 7-27 Outseize Instruction Table
Adding or Changing Outseize Instructions
1.
To add a new Outseize Instruction or to change an existing Outseize Instruction, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new Outseize Instruction on the new line or you can copy an existing Outseize Instruction definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
7-52
To change an existing Outseize Instruction definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
EXS ExchangePlus Software Operations Guide
Setting up an E1 Span to use E1R2 Signaling
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the Outseize Instructions table.
Type
integer
Outseize instruction type
Data1
decimal number (not hex)
Data field
Data2
decimal number (not hex)
Data field
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Outseize Instructions table, pull down the File menu and select Save. 8. When you are done editing the Outseize Instructions table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Outseize Instructions table where you can save your changes.
7-53
Setting up an E1 Span to use E1R2 Signaling
Deleting Outseize Instructions
EXS ExchangePlus Software Operations Guide
1. Pull down the E1R2 menu and select Outseize Instruction. The Outseize Instructions Table window appears (Figure 7-28). This table shows all the Outseize Instructions that have been configured. You can delete any of these Outseize Instructions.
Figure 7-28 Outseize Instruction Table
2. To delete Outseize Instructions, you delete the line containing the definition from the Outseize Instructions table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Outseize Instructions table, pull down the File menu and select Save. 4. When you are done editing the Outseize Instructions table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Outseize Instructions table where you can save your changes.
7-54
EXS ExchangePlus Software Operations Guide
E1R2 Step 4
Setting up an E1 Span to use E1R2 Signaling
Configuring Inseize Control This section lists the Inseize Control for different PPLs which control the inseizure differently indexed by the Inseize (INSZID) value of the PPL Control table. The default E1R2 configuration in the initial switch configuration file already defines six different types of Inseize Control, and they should cover most cases. To set up the Inseize Control for the designated PPL, pull down the E1R2 menu and select Inseize Control. The Inseize Control Table window appears (Figure 7-29).
Figure 7-29 Inseize Control Table
Adding or Changing Inseize Control
1.
To add a new Inseize Control or to change an existing Inseize Control, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new Inseize Instruction on the new line or you can copy an existing Inseize Control definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
To change an existing Inseize Control definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
7-55
Setting up an E1 Span to use E1R2 Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the Inseize Control table.
S1-S4
integer
The values are the indices to the STAGEPARAMETER section for stage 1stage4, respectively. 0 means this stage is not used.
I2-I12
integer
These stand for Instructions #2 to instruction #12 and are the indices to the INSEIZEINSTRUCTIONS section. It is assumed that the first Inseize Instruction is always Generate Inseize Ack.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Inseize Control table, pull down the File menu and select Save. 8. When you are done editing the Inseize Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Inseize Control table where you can save your changes.
7-56
EXS ExchangePlus Software Operations Guide
Deleting Inseize Control
Setting up an E1 Span to use E1R2 Signaling
1. Pull down the E1R2 menu and select Inseize Control. The Inseize Control Table window appears (Figure 7-30). This table shows all the Inseize Control that have been configured. You can delete any of these Inseize Control.
Figure 7-30 Inseize Control Table
2. To delete Inseize Control, you delete the line containing the definition from the Inseize Control table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Inseize Control table, pull down the File menu and select Save. 4. When you are done editing the Inseize Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Inseize Control table where you can save your changes.
7-57
Setting up an E1 Span to use E1R2 Signaling
E1R2 Step 5
EXS ExchangePlus Software Operations Guide
Configuring Outseize Control The default E1R2 configuration in the initial switch configuration file already defines four different types of Outseize Control, and they should cover most cases. To set up the Outseize Control for the designated PPL, pull down the E1R2 menu and select Outseize Control. The Outseize Control Table window appears (Figure 7-31).
Figure 7-31 Outseize Control Table
Adding or Changing Outseize Control
1.
To add a new Outseize Control or to change an existing Outseize Control, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new Outseize Control on the new line or you can copy an existing Outseize Control definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
7-58
To change an existing Outseize Control definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
EXS ExchangePlus Software Operations Guide
Setting up an E1 Span to use E1R2 Signaling
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the Outseize Control table.
S1-S4
integer
The values are the indices to the STAGEPARAMETER section for Stage 1Stage 4, respectively. 0 means the stage is not used.
I2-I12
integer
These stand for Instructions #2 to Instruction #12 and are the indices to the OUTSEIZEINSTRUCTIONS section.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the Outseize Control table, pull down the File menu and select Save. 8. When you are done editing the Outseize Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the Outseize Control table where you can save your changes.
7-59
Setting up an E1 Span to use E1R2 Signaling
Deleting Outseize Control
1.
EXS ExchangePlus Software Operations Guide
Pull down the E1R2 menu and select Outseize Control. The Outseize Control Table window appears (Figure 7-32). This table shows all the Outseize Control that have been configured. You can delete any of these Outseize Control.
Figure 7-32 Outseize Control Table
2. To delete Outseize Control, you delete the line containing the definition from the Outseize Control table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the Outseize Control table, pull down the File menu and select Save. 4. When you are done editing the Outseize Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the Outseize Control table where you can save your changes.
7-60
EXS ExchangePlus Software Operations Guide
E1R2 Step 6
Setting up an E1 Span to use E1R2 Signaling
Configuring PPL Transmit Signal If the PPL needs to change the default transmit signals that are not listed in the initial configuration, they can be added here. To set up the PPL Transmit Signal values for the designated PPL, pull down the E1R2 menu and select PPL Transmit Sig. The PPL Transmit Signal Table window appears (Figure 7-33).
Figure 7-33 PPL Transmit Signal Table
Adding or Changing PPL Transmit Signal
1.
To add a new PPL Transmit Signal or to change an existing PPL Transmit Sig, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new PPL Transmit Signal on the new line or you can copy an existing PPL Transmit Signal definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. NOTE: Enter the values in decimal for the 4 states. If only two of states need values different from the default, then for other states that use the default value simply enter 0, or leave it blank. For example, if only OOS is set to 00000101(0x5) and IDLE needs to be 00001101(0xd), then you can set the entry as OOS
IDLE
BREAK
MAKE
5
13
0
0
3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary.
7-61
Setting up an E1 Span to use E1R2 Signaling
5.
EXS ExchangePlus Software Operations Guide
To change an existing PPL Transmit Signal definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the PPL Transmit Signal table.
OOS
Decimal
Out-of-Service.
Idle
Decimal
Idle state.
Break
Decimal
Interrupted state.
Make
Decimal
Connection.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the PPL Transmit Signal table, pull down the File menu and select Save. 8. When you are done editing the PPL Transmit Signal table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the PPL Transmit Signal table where you can save your changes.
7-62
EXS ExchangePlus Software Operations Guide
Deleting PPL Transmit Signal
Setting up an E1 Span to use E1R2 Signaling
1. Pull down the E1R2 menu and select PPL Transmit Sig. The PPL Transmit Signal Table window appears (Figure 7-34). This table shows all the PPL Transmit Signal that have been configured. You can delete any of these PPL Transmit Signals.
Figure 7-34 PPL Transmit Signal Table
2. To delete PPL Transmit Signal, you delete the line containing the definition from the PPL Transmit Signal table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the PPL Transmit Signal table, pull down the File menu and select Save. 4. When you are done editing the PPL Transmit Signal table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the PPL Transmit Signal table where you can save your changes.
7-63
Setting up an E1 Span to use E1R2 Signaling
E1R2 Step 7
EXS ExchangePlus Software Operations Guide
Configuring PPL Timer If the PPL needs a timer value other than the default and it is not listed in the existing PPL timer table, you must add it here. To set up the PPL Timer for the designated PPL, pull down the E1R2 menu and select PPL Timer. The PPL Timer Table window appears (Figure 7-35).
Figure 7-35 PPL Timer Table
Adding or Changing PPL Timer
1.
To add a new PPL Timer or to change an existing PPL Timer, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new PPL Timer on the new line or you can copy an existing PPL Timer definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
7-64
To change an existing PPL Timer definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
EXS ExchangePlus Software Operations Guide
Setting up an E1 Span to use E1R2 Signaling
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the PPL Timer table.
ID
integer
ID of PPL timer ID
Val
integer
Val of PPL Timer (in 10 ms units).
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the PPL Timer table, pull down the File menu and select Save. 8. When you are done editing the PPL Timer table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the PPL Timer table where you can save your changes.
7-65
Setting up an E1 Span to use E1R2 Signaling
Deleting PPL Timer
EXS ExchangePlus Software Operations Guide
1. Pull down the E1R2 menu and select PPL Timer. The PPL Timer Table window appears (Figure 7-36). This table shows all the PPL Timer that have been configured. You can delete any of these PPL Timer.
Figure 7-36 PPL Timer Table
2. To delete PPL Timer, you delete the line containing the definition from the PPL Timer table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the PPL Timer table, pull down the File menu and select Save. 4. When you are done editing the PPL Timer table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the PPL Timer table where you can save your changes.
7-66
EXS ExchangePlus Software Operations Guide
E1R2 Step 8
Steps
Setting up an E1 Span to use E1R2 Signaling
Configuring PPL Control A PPL Control record defines how the PPL is controlled to do inseize and/or outseize for E1R2 or E1 DTMF. The index is used by a trunk group in its PRTCLID field. To set up the PPL Control for the designated PPL, pull down the E1R2 menu and select PPL Control. The PPL Control Table window appears (Figure 7-37).
Figure 7-37 PPL Control Table
Adding or Changing PPL Control
1.
To add a new PPL Control or to change an existing PPL Control, pull down the Edit menu and select Add. A blank line is added to the bottom of the table. You can either type in the attributes for the new PPL Control on the new line or you can copy an existing PPL Control definition from that table and paste it into the blank line.
2. To type values into the fields on a new line, use the mouse, the arrow keys, or the <Tab> key to select the first field in the new line and type a value into that field. Use the mouse, the arrow keys, or the <Tab> key to move from field to field. Fill in values for each field in the new row. 3. To copy an existing line and paste it into the new row, use the mouse to highlight the line containing the information you want to copy. Pull down the Edit menu and select Copy. Use the mouse again to highlight the blank line that you added to the bottom of the table, then pull down the Edit menu and select Paste. 4. After pasting the information into the new line, you may want to edit the new line by typing into the fields. Again, use the arrow keys or the <Tab> key to move from field to field, as necessary. 5.
To change an existing PPL Control definition, click on the field(s) of interest with the mouse or use the arrow keys or the <Tab> key to select the field of interest. Type the necessary changes into the fields of interest. Move from field to field using the mouse, the arrow keys, or the <Tab> key until you have made all the necessary changes.
7-67
Setting up an E1 Span to use E1R2 Signaling
EXS ExchangePlus Software Operations Guide
6. The following table lists the fields in the table that you need to complete: Parameter
Value
Description
Index
integer
A key that uniquely identifies an entry in the PPL Control table.
PrtclID
Default = 0
Protocol ID assigned to the PPL. The default CCITT E1R2 protocol ID can use 0 or 12. (1-10 are reserved for custom protocols).
TXSigID
Default = 0
Specifies entry in PPL Transmit Signal table.
TimerID
Default = 0
Specifies entry in PPL Timer table.
InSZID
Default = 0
Specifies entry in Inseize Control table.
OutSZID
Default = 0
Specifies entry in Outseize Control table.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 7. To save the changes you make to the PPL Control table, pull down the File menu and select Save. 8. When you are done editing the PPL Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving the last changes. Click Cancel to go back to the PPL Control table where you can save your changes.
7-68
EXS ExchangePlus Software Operations Guide
Deleting PPL Control
Setting up an E1 Span to use E1R2 Signaling
1. Pull down the E1R2 menu and select PPL Control. The PPL Control Table window appears (Figure 7-38). This table shows all the PPL Control that have been configured. You can delete any of these PPL Control.
Figure 7-38 PPL Control Table
2. To delete PPL Control, you delete the line containing the definition from the PPL Control table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: You can only delete one line at a time. 3. To save the changes you make to the PPL Control table, pull down the File menu and select Save. 4. When you are done editing the PPL Control table, pull down the File menu and select Quit. If you have not saved all the changes you have made, a message appears stating that the table was modified but not saved and asks if you want to quit. Click OK to quit without saving your latest changes. Click Cancel to go back to the PPL Control table where you can save your changes.
7-69
Setting up an E1 Span to use E1R2 Signaling
7-70
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
8 Custom Applications Overview This chapter describes how to set up Custom Applications in the ExchangePlus system. The following table lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 55 Installing Custom Applications
8-3
Procedure 56 Activating Custom Applications
8-5
Procedure 57 Deleting Custom Applications
8-9
Procedure 58 Reloading Custom Applications
8-10
Procedure 59 Defining Custom Application Flag Names
8-12
Custom Application Description The advantage of this feature is that the developer or customer can write an application in their own code to create a library. This library can then be loaded from the xmenu user interface during runtime without having to restart the host. The custom applications can be very flexible and powerful, but should be used carefully because they may affect the entire system depending on how they are activated. This feature uses shared libraries or objects in UNIX, which are similar to the DLLâ&#x20AC;&#x2122;s in Windows. Each node can have up to 32 custom applications. There can be multiple applications per node, but only one application per call. A custom application is installed in the Custom Application table. The application for any given call is then specified in either the Trunk Group table or the DNIS Translation table.
8-1
Custom Application Description
EXS ExchangePlus Software Operations Guide
For example, you may have FGA+DTMF+APP1 (APP1 is the flag used for a custom application) in the Flag field of an entry in the Trunk Group table, but you would not have FGA+DTMF+APP1+APP2 (both APP1 and APP2 are flags used for custom applications). This is because if the Flag field for an incoming call has both APP1+APP2 provisioned, then the software may not know which custom application to call. A sample custom application ships with the ExchangePlus software. It intercepts the idle function and prints a message. Several custom applications are being developed and will be documented in stand-alone Custom Application Notes. These notes describe how to install and activate the applications. The following is a quick reference of how to install and activate a custom application: 1. Install the custom application (typically loaded from a CD). 2. Activate the custom application. Depending on the application, you do this using the Custom Application table, the Trunk Group table, or the DNIS Translation table. These procedures assume that the host administrator has a working knowledge of UNIX and is ready to install a specific custom application. This chapter also provides some additional procedures for custom applications that you may need to perform.
Caution
8-2
When you add data to tables, be sure not to save a table that contains empty rows. Doing so may cause a core dump. If this happens, restart xmenu and resume your work.
EXS ExchangePlus Software Operations Guide
Procedure 55
Installing Custom Applications
Installing Custom Applications This procedure describes how to install a custom application. All steps, except Step 1 are performed from the xmenu user interface.
Steps
1. Copy the custom application library file (or files) into the /usr/isos/bin directory. The libraries or application files typically start with the prefix lib and end with the .so extension (for shared objects). For example, libcallcnt.so libpart.so
2. From the Database menu select Custom App. The Custom Application Table window appears (Figure 8-1), showing all the custom applications that have been previously loaded in ExchangePlus.
Figure 8-1 Custom Application Table
3. To add a new custom application, pull down the Edit menu and select Add.
8-3
Installing Custom Applications
EXS ExchangePlus Software Operations Guide
4. Add a custom application by entering the following information in the fields on the blank line: Parameter
Description
Index
Enter the number of the custom application table entry. Usually you start with 1 on the first line and increment this number as you add custom applications.
Filename
Enter the name of the custom application or library shared object file. The library files typically start with the prefix lib and
end with the .so extension (for shared objects). Some applications also have other supporting files, such as .cfg (configuration) files. AppFlag
Enter the name of the flag associated with this custom application. If the application will be used system-wide, use the reserved flag, SYSAPP in this field. If the is not used system-wide, name it by entering one of the reserved application flags, APP1-APP8. The name you choose in this field will be used when you activate the custom application in either the Trunk Group table or the DNIS Translation table. If you prefer to give the AppFlag a more descriptive name, you can define your own AppFlag name (see Procedure 59 Defining Custom Application Flag Names on page 8-12.
Node1 ... Node 10
Enter Yes or No (or Y or N) in each of the appropriate ten fields to indicate the number of the node associated with this custom application.
NOTE: Before saving, move the cursor off any field you just entered. If you do not do this, the changes will not be saved. 5. To save the changes in the Custom Application table, pull down the File menu and select Save. After you select Save, the host terminal should print out â&#x20AC;&#x153;Loading LibraryNameâ&#x20AC;? and will look similar to the following: <01/07/00 12:51:51>[host2.0]Loading DLL: libcallcnt.so <01/07/00 12:51:51>[host1.0]Loading DLL: libcallcnt.so <01/07/00 12:51:51>[host2.0]Loading DLL libcallcnt.so Done. <01/07/00 12:51:51>[host1.0]Loading DLL libcallcnt.so Done. <01/07/00 12:51:51>[host2.0]Loading DLL: libpart.so <01/07/00 12:51:51>[host1.0]Loading DLL: libpart.so <01/07/00 12:51:51>[host2.0]Loading DLL libpart.so Done. <01/07/00 12:51:51>[host1.0]Loading DLL libpart.so Done. Pull down the File menu and select Quit to leave the Custom Application table. Installing a custom application is only part of the procedure. Next, you need to activate the custom application.
8-4
EXS ExchangePlus Software Operations Guide
Procedure 56
Activating Custom Applications
Activating Custom Applications This procedure describes how to activate a custom application from: • • •
Setting up a Custom Application Table
The Custom Application table, or The Trunk Group table, or The DNIS Translation table
Activate the Custom Application in the
If the:
Custom Application table
Application applies to all calls system-wide and required no activation in the Trunk Group table or the DNIS Translation table.
Trunk Group table
Application applies to all calls on an inbound trunk group.
DNIS Translation table
Application is phone-number specific, or it applies to a certain group of phone numbers (for example, all calls beginning with a specific area codes, such as 508).
If the custom application applies to all calls system-wide, set the AppFlag field on the Custom Application table to SYSAPP. See Procedure 55 Installing Custom Applications on page 8-3. The custom application is available immediately after installing and activating it.
Setting up a Trunk Group Table
The following procedure describes how to activate a custom application via the Trunk Group table. 1. From the Database menu select Trunk Group Setup. The Trunk Group Table window appears (see Figure 8-2). This table shows all trunk groups that have been configured for a particular node (the entire window is not shown in this figure, but the FLAG field, which is discussed below, is shown).
Figure 8-2 Trunk Group Table
8-5
Activating Custom Applications
EXS ExchangePlus Software Operations Guide
For the Trunk Group table, the custom application starts if a call on an inbound trunk has the APPn flag specified in the FLAG field. Figure 8-2 shows an example of two way Trunk Groups TG1 and TG2. They each use custom application APP1 along with other flags (FGD+DTMF in this example) in the FLAG field. 2. You can either change an existing table entry or add a new table entry so that a trunk group uses the APP1 flag in the FLAG field. •
To change an existing entry, click on the FLAG field and enter all the previous flag settings if any, then enter the following in the same field: + <custom application flag name>
For example add +APP1 to the information in the FLAG field. •
To add a new entry, pull down the Edit menu and select Add. A blank line appears at the bottom of the table. Complete the fields in the Trunk Group table according to the description in “Appendix B. Trunk Types and Flags”. In addition, enter the following in the FLAG field: + <custom application flag name>
For example, add +APP1 to the entry you make in the FLAG field. NOTE: Before saving the changes, move the cursor off of any field you have edited. If you do not do this, the changes will not be saved. 3. To save the changes you make to the Trunk Group table, pull down the File menu and select Save. 4. When you finish editing the Trunk Group table, pull down the File menu and select Quit. If you have not saved the changes, a message appears stating that the table was modified, but not saved and asks if you want to quit. Either click OK to quit without saving your latest changes, or click Cancel to go back to the Trunk Group Table window where you can save the changes. The custom application is available immediately after installing and activating it.
Setting up a DNIS Translation Table
The following procedure describes how to activate a custom application via the DNIS Translation table. To be used in the DNIS Translation table, set the APPFLAG (see Figure 8-3) to be the same as the AppFlag specified in the Custom Application table (see Figure 8-1). For example: If you have a Custom Application table entry set so that libnoani.so uses APP1, then the DNIS Translation table should have an entry that specifies APP1 in the APPFLAG field (Figure 8-3). The DNIS Translation table entry activates the custom application for any call routed through it.
8-6
EXS ExchangePlus Software Operations Guide
Activating Custom Applications
To activate a custom application for calls based on the outbound trunk group, Outbound Translation must be enabled, and the outbound trunk group must have a different partition than the inbound trunk group partition. (See Procedure 12 Using the Outbound Translation Option on page 3-12 to enable outbound translation.) During outbound dialing, the DNIS Translation table is searched for the outbound partition and called number. The DNIS Translation table entry for the outbound partition must have the APPFLAG field set to match the Custom Application table flag (AppFlag). For example: If you have a Custom Application table entry set so that libnoani.so uses APP1 (see Figure 8-1), then the DNIS Translation table entry for outbound partition 0003 (see Figure 8-3) could be: & in the CLD field, -1 in the TRANS field, and APP1 in the APPFLAG field. The other fields do not matter. If this is the only DNIS Translation table entry for the outbound partition, then all calls will use the No ANI custom application. 1. From the Database menu select DNIS Translations. The DNIS Translation Table window appears.
Figure 8-3 DNIS Translation Table
2. To activate a custom application, you can either change an existing table entry, or add a new table entry as follows: â&#x20AC;˘
To change an existing entry, click on the APPFLAG field and enter the appropriate custom application flag, such as APP1, as shown in Figure 8-3.
â&#x20AC;˘
To add a new entry, pull down the Edit menu and select Add. A blank line appears at the bottom of the table. Complete the fields in the DNIS Translation table according to the description in Procedure 35 Adding or Changing DNIS Translations on page 6-32. Enter the appropriate custom application flag, such as APP1, in the APPFLAG field.
NOTE: Before saving the changes, move the cursor off of any field you have edited. If you do not do this, the changes will not be saved. 3. To save the changes you make to the DNIS Translation table, pull down the File menu and select Save.
8-7
Activating Custom Applications
EXS ExchangePlus Software Operations Guide
4. When you are finished editing the DNIS Translation table, pull down the File menu and select Quit. If you have not saved the changes, a message appears stating that the table was modified but not saved and asks if you want to quit. Either click OK to quit without saving your latest changes, or click Cancel to go back to the DNIS Translation Table window where you can save the changes. The custom application is available immediately after installing and activating it.
8-8
EXS ExchangePlus Software Operations Guide
Procedure 57
Deleting Custom Applications
Deleting Custom Applications This procedure describes how to delete custom applications.
Steps
1. Pull down the Database menu and select Custom App. The Custom Application Table window appears (Figure 8-4). This table show all the custom applications that have been configured. You can delete any of these custom applications.
Figure 8-4 Custom Application Table
2. To delete custom applications you delete the line containing the definition from the Custom Application table. To do this, use the mouse to highlight the selected line, then pull down the Edit menu and select Delete. The line is deleted without a confirmation message. NOTE: If you highlight more than one line, only the first line selected is deleted. 3. To save the changes you make to the Custom Application table, pull down the File menu and select Save. 4. When you are done editing the Custom Application table, pull down the File menu and select Quit. If you have not saved the changes, a message appears stating that the table was modified but not saved and asks if you want to quit. Either click OK to quit without saving your latest changes, or click Cancel to go back to the Custom Application Table window where you can save the changes.
8-9
Reloading Custom Applications
Procedure 58
EXS ExchangePlus Software Operations Guide
Reloading Custom Applications This procedure describes how to reload custom applications.
Steps
1. Pull down the Database menu and select Custom App. The Custom Application Table window appears (Figure 8-5). This table show all the custom applications that have been configured. You can reload any of these custom applications.
Figure 8-5 Custom Application Table
2. To reload a custom application you highlight the selected line in the Custom Application table, then pull down the Edit menu and select Reload. The custom application that was highlighted will reload. Reload means an application will be reloaded without going through the Delete/Add sequence. This method is used to upgrade applications with a minimum impact on service. The custom application reload drop-down menu (Figure 8-6) is shown below:
Figure 8-6 Reload Drop-down Menu
8-10
EXS ExchangePlus Software Operations Guide
Reloading Custom Applications
3. The host terminal should print out “Unloading LibraryName” and then “Loading LibraryName”. The following is an example: 01/07/00 12:52:16 Reload message sent successfully <01/07/00 12:52:16>[host1.0]Unloading DLL: libivrthost.so <01/07/00 12:52:16>[host1.0]Unloading DLL libivrthost.so Done. <01/07/00 12:52:16>[host1.0]Loading DLL: libivrthost.so <01/07/00 12:52:16>[host2.0]Unloading DLL: libivrthost.so <01/07/00 12:52:16>[host2.0]Unloading DLL libivrthost.so Done. <01/07/00 12:52:16>[host2.0]Loading DLL: libivrthost.so <01/07/00 12:52:16>[host1.0]Loading DLL libivrthost.so Done. <01/07/00 12:52:16>[host2.0]Loading DLL libivrthost.so Done. NOTE: If you highlight more than one line, only the first line selected is reloaded. 4. To save the changes you make to the Custom Application table, pull down the File menu and select Save. 5. When you are done reloading the custom application, pull down the File menu and select Quit. If you have not saved the changes, a message appears stating that the table was modified but not saved and asks if you want to quit. Either click OK to quit without saving your latest changes, or click Cancel to go back to the Custom Application Table window where you can save the changes.
8-11
Defining Custom Application Flag Names
Procedure 59
EXS ExchangePlus Software Operations Guide
Defining Custom Application Flag Names In most cases, you can use the trunk flags APP1-APP8 for your custom application; however, if you have more than one custom application, you may want to use more descriptive names to help you identify the different custom applications.
Steps
1. Copy the custom application library file (and any other associated application files) into the /usr/isos/bin directory. The libraries typically start with the prefix lib and end with the .so extension (for shared objects). For example: libmyapp.so 2. Run the vi editor and open the trnkdefs.cfg file. The file contents should look similar to the following:
Figure 8-7 Sample trnkdefs.cfg file
8-12
EXS ExchangePlus Software Operations Guide
Defining Custom Application Flag Names
3. Edit the trnkdefs.cfg file. In the extra trunk flags section (near the end of the file) replace one of the APP flags (APP1-APP8) with the new custom application flag name, such as CALLCNT or NEWAPP. You can rename any extra trunk flag which is not used by the ExchangePlus baseline; however you need to use extreme care not to change the name of a trunk flag that is used by the baseline software. Also, be sure that the name you choose is unique and that you do not use any reserved words. The application flag name can be up to eight characters in length. 4. Save the file and exit vi. 5. Restart xmenu so that the new flags in the trnkdefs.cfg file take effect. You can now use the new application flag in the Custom Application table.
8-13
Defining Custom Application Flag Names
8-14
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
9 Monitoring Status Overview This chapter describes how to monitor your ExchangePlus system. It includes a number of monitoring procedures available from the Status menu. The following table lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 60 Checking Span Status
9-2
Procedure 61 Checking Status of Channels on a Span
9-3
Procedure 62 Checking Channel Status
9-4
Procedure 63 Checking Matrix Cards Status
9-5
Procedure 64 Checking DSP Card Status
9-6
Procedure 65 Checking SS7 Card Status
9-7
Procedure 66 Checking ISDN Card Status
9-8
Procedure 67 Checking Line Card Status (T1 or E1)
9-9
Procedure 68 Checking Standby I/O Card Status
9-10
Procedure 69 Checking VRAS Status
9-11
Procedure 70 Checking Synchronization Status
9-12
Procedure 71 Checking Link Status
9-13
Procedure 72 Checking Node(s) Status
9-14
Procedure 73 Checking Ring(s) Status
9-15
Procedure 74 Checking Version Status
9-16
Procedure 75 Viewing User Log
9-17
Procedure 76 Viewing System Log
9-18
9-1
Checking Span Status
Procedure 60
EXS ExchangePlus Software Operations Guide
Checking Span Status This procedure shows how to check the status of all spans or a particular span or set of spans in your system.
Steps
1. Pull down the Status menu and select Span(s). The Span Status window appears (Figure 9-1).
Figure 9-1 Span Status Window
2. Enter the starting and ending span numbers for which you want to obtain status. 3. Click Apply. The status of the selected spans is displayed.
9-2
EXS ExchangePlus Software Operations Guide
Procedure 61
Checking Status of Channels on a Span
Checking Status of Channels on a Span This procedure shows how to check the status of all channels on a particular span.
Steps
1. Pull down the Status menu and select Span Status. The Span Status window appears (Figure 9-2).
Figure 9-2 Span Status Window
2. Enter the number of the span on which you want to check channel status. 3. Click Apply. The status of the channels on the selected spans is displayed.
9-3
Checking Channel Status
Procedure 62
EXS ExchangePlus Software Operations Guide
Checking Channel Status This procedure shows how to check the status of all channels or a particular channel or set of channels in your system.
Steps
1. Pull down the Status menu and select Channel(s). The Chan Status window appears (Figure 9-3).
Figure 9-3 Chan Status Window
2. Enter the starting and ending span numbers for which you want to obtain status. 3. Click Apply. The status of the selected spans and channels is displayed. The following is a list of the possible channel states: • • • • • • •
•
ACTIVATED - Trunk up and ready for traffic CMDBUSY - Trunk forced busy via menu CMDDOWN- Trunk forced inactive BUSY - Trunk in use ISOFFHOOK - Inbound side of trunk seized and off hook OSOFFHOOK - Outbound side of trunk seized and off hook SPNACTIVATED - Span is in synchronization with the carrier side in regard to span framing. This does not reflect the status of the channels within the span. The channels may be IDLE, BUSY, or DEACTIVATED. BUSYBACK
NOTE: SS7 signaling channel status does not reflect the status of the signaling channel. It may show IDLE or DEACTIVATED regardless of the SS7 link carried on that channel is really up or down. The same applies for ISDN signaling channels (D channels) except if the channel status is showing DEACTIVATED we can be sure that the signaling link is down. However, if it is showing IDLE, the signaling link may be either up or down.
9-4
EXS ExchangePlus Software Operations Guide
Procedure 63
Checking Matrix Cards Status
Checking Matrix Cards Status This procedure shows how to check of Matrix Cards.
Steps
1. Pull down the Status menu and select Matrix Card. The Matrix Status window appears (Figure 9-4).
Figure 9-4 Matrix Status Window
2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The Matrix card status is displayed.
9-5
Checking DSP Card Status
Procedure 64
EXS ExchangePlus Software Operations Guide
Checking DSP Card Status This procedure shows how to check the status of the DSP Card(s).
Steps
1. Pull down the Status menu and select DSP Card(s). The DSP Card Status window appears (Figure 9-5).
Figure 9-5 DSP Card Status Window
2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The DSP card status is displayed.
9-6
EXS ExchangePlus Software Operations Guide
Procedure 65
Checking SS7 Card Status
Checking SS7 Card Status This procedure shows how to check the status of the SS7 Cards.
Steps
1. Pull down the Status menu and select SS7 Card(s). The SS7 Card Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The SS7 card status is displayed.
9-7
Checking ISDN Card Status
Procedure 66
EXS ExchangePlus Software Operations Guide
Checking ISDN Card Status This procedure shows how to check the status of ISDN cards.
Steps
1. Pull down the Status menu and select ISDN Card(s). The ISDN Card Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The ISDN card status is displayed.
9-8
EXS ExchangePlus Software Operations Guide
Procedure 67
Checking Line Card Status (T1 or E1)
Checking Line Card Status (T1 or E1) This procedure shows how to check the status of T1 or E1 line cards in your system.
Steps
1. Pull down the Status menu and select either T1 Card or E1 Card. The T1 or E1 Line Card Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The status of the selected line card(s) is displayed
9-9
Checking Standby I/O Card Status
Procedure 68
EXS ExchangePlus Software Operations Guide
Checking Standby I/O Card Status This procedure shows how to check the status of the standby I/O card.
Steps
1. Pull down the Status menu and select Standby I/O. The Standby I/O Card Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The Standby I/O status is displayed.
9-10
EXS ExchangePlus Software Operations Guide
Procedure 69
Checking VRAS Status
Checking VRAS Status This procedure shows how to check VRAS status.
Steps
1. Pull down the Status menu and select VRAS Status. The VRAS Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The VRAS status is displayed.
9-11
Checking Synchronization Status
Procedure 70
EXS ExchangePlus Software Operations Guide
Checking Synchronization Status This procedure shows how to check the Synchronization status. It shows where the current span timing is being derived from. The system is set up in the initial configuration to synchronize in the following order: • • • • •
Primary span (1) Secondary span (2) Primary Reference Clock Secondary Reference Clock Free Running Clock
Timing is often derived from Span 1, but this is configurable.
Steps
1. Pull down the Status menu and select Synchronization. The Synchronization Status window appears (Figure 9-6).
Figure 9-6 Synchronization Status Window
2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The synchronization status is displayed on the Main Menu window. The status may look like either one of the following: 04/20/99 14:05:00 Synchronized from Primary Loop Clock Signal 04/20/99 14:05:00 Synchronized from Free Running Clock
9-12
EXS ExchangePlus Software Operations Guide
Procedure 71
Checking Link Status
Checking Link Status This procedure shows how to check Link status.
Steps
1. Pull down the Status menu and select Link Status. The Link Status window appears. 2. Enter the node for which you want to obtain status (1 or 2). 3. Click Apply. The link status is displayed.
9-13
Checking Node(s) Status
Procedure 72
EXS ExchangePlus Software Operations Guide
Checking Node(s) Status This procedure shows how to check the status of nodes in your system.
Steps
9-14
Pull down the Status menu and select Node(s). The status of the selected node(s) is displayed.
EXS ExchangePlus Software Operations Guide
Procedure 73
Checking Ring(s) Status
Checking Ring(s) Status This procedure shows how to check the status of Ring(s).
Steps
Pull down the Status menu and select Ring(s). The status of the ring(s) is displayed. Release 3.1 supports up to four rings. The status query reports messages similar to the following: Ring 1 on node 1 in service (0x03)
The number is parentheses is a bit map indicating which ring(s) are in service and which are configured as transmit receive. In the example above, 0x03 is binary 0011. This means that Ring 1 and Ring 2 are in service and they are also configured as transmit/receive mode. NOTE: A ring can be in service even if itâ&#x20AC;&#x2122;s configured as receive only; however, any node must have at least one ring that is in service and in transmit/receive mode in order for it to receive traffic from other nodes.
9-15
Checking Version Status
Procedure 74
EXS ExchangePlus Software Operations Guide
Checking Version Status This procedure shows how to display the version of the ExchangePlus software.
Steps
Pull down the Status menu and select Version. The version of the ExchangePlus software and the version of the switch firmware are displayed on the Main Menu window. This information will be particularly useful to a service representative who may be helping you to troubleshoot a problem.
9-16
EXS ExchangePlus Software Operations Guide
Procedure 75
Viewing User Log
Viewing User Log This procedure shows how to view the user log. The user log displays all the actions taken by the user and the results of those actions.
Steps
Pull down the System menu and select View User Log. The user log is displayed (Figure 9-7).
Figure 9-7 User Log
9-17
Viewing System Log
Procedure 76
EXS ExchangePlus Software Operations Guide
Viewing System Log This procedure shows how to view the system log. The system log displays errors. It includes the contents of the host message log transcribed into a readable form.
Steps
Pull down the System menu and select View System Log. The system log is displayed (Figure 9-8).
Figure 9-8 System Log
9-18
EXS ExchangePlus Software Operations Guide
Overview
10 Call Statistics Overview Report Manager is a process that generates a report based on the following statistical data: • • • • •
Call statistics by trunks Outbound call completion statistics by trunks Call statistics by trunk groups Outbound call completion statistics by trunk groups Outbound call completion statistics by route lists
The report can be configured for different time intervals by editing a configuration file parameter. The format of the report is an ASCII text file that is written to a report directory and can be viewed using the vi editor. This chapter describes how to set up and monitor call statistics for ExchangePlus by using the Report Manager. The following table lists all the procedures and the page number on which you can find the procedure.
Assumptions
Procedure Name
Page
Procedure 77 Configuring Call Statistics
10-2
Procedure 78 Viewing Call Statistics
10-4
•
The host administrator should have a working knowledge of UNIX.
•
The host administrator should have a working knowledge of the vi editor.
10-1
Configuring Call Statistics
Procedure 77
EXS ExchangePlus Software Operations Guide
Configuring Call Statistics This procedure shows how to configure the Report Manager to collect call statistics.
Steps
1. Open a terminal window and go to /usr/isos. 2. Verify that a directory called report is present. If it is not, then make a directory called report. 3. The Report Manager must be terminated when the rptmgr.cfg file needs to be edited. To terminate Report Manager manually, you must kill its process ID (PID). From the command line type: ps -ef|grep rpt
This command will list the PID number of the Report Manager. isos 221 22005 0 18:21:21 pts/0 5:01 rptmgr rptmgr.cfg
The PID of the query above would be 221. 4. Log in as superuser and kill the Report Manager process by typing: kill -9 221
Type quit to exit out of superuser. Note: When host control is terminated, the Report Manager is also terminated. 5. Verify that the Report Manager has been disabled by typing: ps -ef|grep rpt
There should be no PID found for Report Manager. 6. Go to /usr/isos/bin and edit the rptmgr.cfg file by typing: vi rptmgr.cfg
10-2
EXS ExchangePlus Software Operations Guide
Configuring Call Statistics
7. To configure the Report Manager, edit the lines in rptmgr.cfg below: REPORTINTERVAL=15 REPORTDIRECTORY=../report REPORTDAYS=3 Value
Description
ReportInterval
Specifies the number of minutes between each report. This example is configured for 15 minutes between reports. Every 15 minutes an ASCII text file will be written to the report directory. This interval is set for all of the reports that are generated by Report Manager. You can not configure individual reports for different time intervals. The valid range is 1 to 60.
ReportDirectory
Specifies the directory where the reports will be stored. The default directory should be /usr/isos/report.
ReportDays
Specifies the number of days before the oldest report files begin to be deleted. This example is configured for three days. All of the reports that are three days or older will be deleted from the /usr/isos/report directory. The valid value can be any positive integer, such as 1, 2, 3,..., but because there is always a limit on the total disk space available be careful when assigning a large number.
8. Save the file. 9. Edit the switch.cfg file by typing: vi switch.cfg
Look for the SWITCHAPPTABLE section of the file and verify that the following line is present: rptmgr
rptmgr.cfg,
report manager, 0, 0
The Node Manager monitors the Report Manager and will re-start the process automatically if it stops. If the Report Manager stops three times within five minutes, the Node Manager will not try to re-start it again. 10. Save the file. 11. To restart the Report Manager manually, type the following from the command line: nohup rptmgr rptmgr.cfg&
10-3
Viewing Call Statistics
Procedure 78
EXS ExchangePlus Software Operations Guide
Viewing Call Statistics This procedure shows how to view the individual call statistic reports that are generated by the Report Manager. This ASCII text report displays: • • • • •
Steps
Call statistics by trunks Outbound call completion statistics by trunks Call statistics by trunk groups Outbound call completion statistics by trunk groups Outbound call completion statistics by route lists
1. Access the Unix command line on the host through Exceed. 2. Change directory (cd) to the /usr/isos/report directory. View the contents of the directory by typing the following: ls -l | more
Press the space bar to view the next page, etc. 3. The contents of the report directory could be a very long list depending on the configuration settings that were set in rptmgr.cfg. The filenames are listed as report.log.yyyymmddhhmm. An example of a filename in this directory is: report.log.199910121845
This example report was saved on October 12th, 1999 at 6:45pm. 4. To view this report type the following: pg report.log.199910121845
10-4
EXS ExchangePlus Software Operations Guide
Viewing Call Statistics
5. The contents and length of the report depends on the number of spans, trunk groups and route lists that are configured. When a report is opened the ASCII text file contains call statistics for all of the spans, trunk groups and route lists configured in the system. An example of the Call Statistics by Trunks report is displayed below for Span 1: Call Statistics Report 1999/10/12 14:45:00 Call Statistics by Trunks:
SPAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN
1: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23:
--- 15 MINUTES --IN CONN OUT CONN 20 7 38 30 26 15 48 42 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
----- HOURLY ----IN CONN OUT CONN 96 85 110 97 75 65 94 82 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
--------- DAILY IN CONN 930 840 856 793 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
--------OUT CONN 972 951 897 881 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The three major column headings (15 Minutes, Hourly, and Daily) are the intervals between reports. The Hourly and Daily headings can not be reconfigured and will be displayed with each report. The 15 Minutes column is the ReportInterval configuration option that was set in the rptmgr.cfg file. For each trunk in each span the following call statistics are reported: Value
Description
In
Total inbound calls on this trunk during this time interval.
Conn
Total inbound connected calls to this trunk during this time interval.
Out
Total outbound calls on this trunk during this time interval.
Conn
Total outbound connected calls on this trunk during this time interval.
10-5
Viewing Call Statistics
EXS ExchangePlus Software Operations Guide
6. This report is for the Outbound Call Completion Statistics by Trunks for Span 1. Outbound Call Completion Statistics by Trunks:
SPAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN CHAN
1: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23:
--- 15 MINUTES --OUT CONN ANS PCT 35 30 23 76% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
----- HOURLY ----OUT CONN ANS PCT 110 97 68 70% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
---------- DAILY ---------OUT CONN ANS PCT 972 840 650 77% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
For each trunk in each span the following call statistics are reported:
10-6
Value
Description
Out
Total outbound calls on this trunk during this time interval.
Conn
Total outbound connected calls on this trunk during this time interval.
Ans
Total number of outbound calls answered on this trunk during this time interval.
Pct
The percentage of outbound calls answered on this trunk during this time interval.
EXS ExchangePlus Software Operations Guide
Viewing Call Statistics
7. This report is for the Call Statistics by Trunk Groups. Call Statistics by Trunk Groups:
TG 1: 2: 21: 22: 31: 32: 41: 42: 51: 52:
--- 15 MINUTES --IN CONN OUT CONN 7 5 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
------- HOURLY ------IN CONN OUT CONN 30 22 33 27 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
--------- DAILY --------IN CONN OUT CONN 330 246 358 292 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
For each trunk group the following call statistics are reported: Value
Description
In
Total inbound calls to this trunk group during this time interval.
Conn
Total inbound connected calls to this trunk group during this time interval.
Out
Total outbound calls on this trunk group during this time interval.
Conn
Total outbound connected calls on this trunk group during this time interval.
10-7
Viewing Call Statistics
EXS ExchangePlus Software Operations Guide
8. This report is for the Outbound Call Completion Statistics by Trunk Groups. Outbound Call Completion Statistics by Trunk Groups:
TG 1: 2: 21: 22: 31: 32: 41: 42: 51: 52:
--- 15 MINUTES --OUT CONN ANS PCT 8 6 4 66% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
------- HOURLY ------OUT CONN ANS PCT 33 27 14 51% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
---------- DAILY ---------OUT CONN ANS PCT 358 292 211 72% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
For each trunk group the following call statistics are reported:
10-8
Value
Description
Out
Total outbound calls on this trunk group during this time interval.
Conn
Total outbound connected calls on this trunk group during this time interval.
Ans
Total number of outbound calls answered on this trunk group during this time interval.
Pct
The percentage of outbound calls answered on this trunk group during this time interval.
EXS ExchangePlus Software Operations Guide
Viewing Call Statistics
9. This report is for the Outbound Call Completion Statistics by Route Lists. Outbound Call Completion Statistics by Route Lists:
ROUTE 1: 2: 21: 22: 31: 32: 41: 42: 51: 52: 99:
--- 15 MINUTES --OUT CONN ANS PCT 8 6 4 66% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
------- HOURLY ------OUT CONN ANS PCT 33 27 14 51% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
---------- DAILY ---------OUT CONN ANS PCT 358 292 211 72% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0%
End of Call Statistics Report
For each route list the following call statistics are reported: Value
Description
Out
Total outbound calls on this route list during this time interval.
Conn
Total outbound connected calls on this route list during this time interval.
Ans
Total number of outbound calls answered on this route list during this time interval.
Pct
The percentage of outbound calls answered on this route list during this time interval.
10-9
Viewing Call Statistics
10-10
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
11 Monitoring Trunk Activity Overview This chapter describes how to monitor trunks on your ExchangePlus system. It includes procedures on how to set up the Watcher monitoring process in ExchangePlus. Watcher is a very flexible and configurable task that monitors trunk activity on the switch and sends out an E-mail or a page alert when certain thresholds are exceeded. Features include: • • • • •
Minimal system impact by the monitoring process Easy to edit monitoring parameters Follows industry standards Allows rapid prototyping and changes Simple configurable paging and E-mail interface
Watcher consists of a number of processes and uses simple ASCII text files for configuration. The individual configuration files and tasks that are used in Watcher are located in the directory of /usr/isos/bin/watcher. The log files that are associated with Watcher are located in /usr/isos/log including watcher.log which logs all of the Watcher activities. Report Manager must be enabled before running the Watcher program. See “Call Statistics” on page 10-1 for more information on Report Manager. The following table lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 79 Setting the Watcher Monitoring Intervals
11-3
Procedure 80 Configuring Watcher to Monitor Trunk Parameters 11-4 Procedure 81 Configuring Watcher for Paging
11-6
Procedure 82 Configuring Watcher for E-Mail
11-7
Procedure 83 Viewing Watcher Log
11-8
Procedure 84 Viewing Watcher Page Log
11-9
Procedure 85 Viewing Watcher E-mail Log
11-10
11-1
Overview
Assumptions
11-2
EXS ExchangePlus Software Operations Guide
• • •
The host administrator should have a working knowledge of UNIX. The host administrator should have a working knowledge of the vi editor. The host administrator should have a working knowledge of the Report Manager call statistics reports.
EXS ExchangePlus Software Operations Guide
Procedure 79
Setting the Watcher Monitoring Intervals
Setting the Watcher Monitoring Intervals This procedure describes how to set the Watcher monitoring intervals.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3.
Open vi and edit cron.dat by typing: vi cron.dat
To edit the file, press the $ to go to the bottom of the page. Type: :r watcher/watcher.cron_entry
and press Enter. To save your changes and quit vi, type: :wq 4. To remove any cron task currently running, type: crontab -r
5. To start the new cron task which now includes watcher, type: crontab cron.dat
6. Verify that this new cron task is running by typing: crontab -l
Below is a sample cron.dat display with the watcher entry added: #Module: cron.dat #SCCS ID 1.3 #This script will check the ISOS to see if it is running #if not, then it will start it #Minute Hour, Day of Month, Month of Year, Day of Week *****/usr/isos/bin/restart>/dev/null 7 16 **/usr/isos/bin/rollover>/dev/null 5,20,35,5 **** /usr/isos/bin/watcher/watcher.sh >> /usr/isos/log/ watcher.log 2>&1
11-3
Configuring Watcher to Monitor Trunk Parameters
Procedure 80
EXS ExchangePlus Software Operations Guide
Configuring Watcher to Monitor Trunk Parameters This procedure shows how to configure Watcher to monitor trunk parameters and thresholds. The configuration file watcher_chan.cfg resides in /usr/isos/bin/watcher and receives its data from the Report Manager reports.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the watcher directory by typing: cd watcher
4. Start vi and edit the watcher_chan.cfg file by typing: vi watcher_chan.cfg
5. Enter the values for the Min, Max and Description fields.
11-4
Value
Description
Parameter
Specifies the type of calls in that time interval from the Report Manager call statistics reports.
Type
Is set to â&#x20AC;&#x153;Râ&#x20AC;? for range of values.
Min
Specifies the minimum value that you will allow in the Report Manager before a page or E-mail or both will be sent.
Max
Specifies the maximum value that you will allow in the Report Manager before a page or E-mail or both will be sent.
Description
User configurable text that will be displayed in the page and E-mails sent out. This description will also be attached to the watcher.log file that logs all Watcher activity.
EXS ExchangePlus Software Operations Guide
Configuring Watcher to Monitor Trunk Parameters
Below is a sample configuration display: #Call Threshold Limits. #--------------------------------------------------------------------#Parameter,Type,Min,Max,Description #--------------------------------------------------------------------TRUNKS_MINUTES_IN,R,0,5,total inbound calls per minute TRUNKS_MINUTES_IN_CONN,R,0,5,connected inbound calls per minute TRUNKS_MINUTES_OUT,R,0,5,total outbound calls per minute TRUNKS_MINUTES_OUT_CONN,R,0,5,connected outbound call per minute TRUNKS_HOURLY_IN,R,0,5,total inbound calls per hour TRUNKS_HOURLY_IN_CONN,R,0,5,connected inbound calls per hour TRUNKS_HOURLY_OUT,R,0,5,total outbound calls per hour TRUNKS_HOURLY_OUT_CONN,R,0,5,connected outbound calls per hour
6. Save the file.
11-5
Configuring Watcher for Paging
Procedure 81
EXS ExchangePlus Software Operations Guide
Configuring Watcher for Paging This procedure shows how to configure Watcher for paging when a monitored parameter value is out of range. The two configuration files, watcher.page and watcher_chan.page reside in /usr/isos/bin/watcher and have the names of the pager address or CAP codes and the names of the pager recipients respectively. This feature uses an E-mail based paging service. Pages are automatically logged to a file called watcher_page.log located in /usr/isos/log.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the watcher directory by typing: cd watcher
4. Start vi and edit the watcher.page file by typing: vi watcher.page
5. Edit the fields and add a name followed by the pager address of the person to be paged when a trunk parameter value is out of range. Below is a sample configuration display: David:2145551212@page.nextel.com Tony:2145551213@page.nextel.com Fred:2145551214@page.nextel.com Bob:2145551215@page.nextel.com
6. Save the file. 7. Open the watcher_chan.page file by typing: vi watcher_chan.page
8. Edit the fields and add the names of the people to be paged when a parameter value is out of range. Below is a sample configuration display: David Tony Fred Bob
9. Save the file.
11-6
EXS ExchangePlus Software Operations Guide
Procedure 82
Configuring Watcher for E-Mail
Configuring Watcher for E-Mail This procedure shows how to configure Watcher for E-mail when a monitored parameter value is out of range. The two configuration files, watcher.mail and watcher_chan.mail, reside in /usr/isos/bin/watcher and have the E-mail addresses and the names of the E-mail recipients respectively. E-mails are automatically logged to a file called watcher_mail.log located in /usr/isos/log.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the watcher directory by typing: cd watcher
4. Start vi and edit the watcher.mail file by typing: vi watcher.mail
5. Edit the fields and add a name followed by the E-mail address of the person to be E-mailed when a trunk parameter value is out of range. Below is a sample configuration display: David:david@mycompany.com Tony:tony@mycompany.com Fred:fred@mycompany.com Bob:bob@mycompany.com
6. Save the file. 7. Open the watcher_chan.mail file by typing: vi watcher_chan.mail
8. Edit the fields and add the names of the people to be E-mailed when a parameter value is out of range. Below is a sample configuration display: David Tony Fred Bob
9. Save the file.
11-7
Viewing Watcher Log
Procedure 83
EXS ExchangePlus Software Operations Guide
Viewing Watcher Log This procedure shows how to view the Watcher log. This file, watcher.log displays all activity in the Watcher program. This log file resides in /usr/isos/log.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the log directory by typing: cd log
4. Change directory (cd) to /usr/isos/log. 5. Open the watcher.log file by typing: pg watcher.log
Below is a sample configuration display: OVERRANGE SPAN=1 CHAN=2 MIN=5 VAL=13 "total inbound calls per minute" OVERRANGE SPAN=1 CHAN=2 MIN=5 VAL=14 "connected inbound calls per minute" OVERRANGE SPAN=1 CHAN=2 MIN=5 VAL=13 "total inbound calls per minute" OVERRANGE SPAN=1 CHAN=2 MIN=5 VAL=14 "connected inbound calls per minute"
11-8
Value
Description
OverRange Span
Specifies the span number that has exceeded the parameter value.
Chan
Specifies the channel or trunk number that has exceeded the parameter value.
Min
Specifies the minimum value that was set in parameter.
Val
Specifies the value that was reported for that span and channel or trunk.
Description
Specifies to the text that describes the event in error.
EXS ExchangePlus Software Operations Guide
Procedure 84
Viewing Watcher Page Log
Viewing Watcher Page Log This procedure shows how to view the Watcher page log. This file, watcher_page.log, displays the recipientâ&#x20AC;&#x2122;s name, the report name and the timestamp. This log file resides in /usr/isos/log.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the log directory by typing: cd log
4. Open the watcher_page.log file by typing: pg watcher_page.log
Below is a sample configuration display: watcher_page: Sent page to David for watcher_chan.rpt at Wed Sep 8 10:42:28 CDT 1999 watcher_page: Sent page to Tony for watcher_chan.rpt at Wed Sep 8 10:42:28 CDT 1999 watcher_page: Sent page to Fred for watcher_chan.rpt at Wed Sep 8 10:42:28 CDT 1999 watcher_page: Sent page to Bob for watcher_chan.rpt at Wed Sep 8 10:42:29 CDT 1999
11-9
Viewing Watcher E-mail Log
Procedure 85
EXS ExchangePlus Software Operations Guide
Viewing Watcher E-mail Log This procedure shows how to view the Watcher E-mail log. The file, watcher_mail.log, displays the recipientâ&#x20AC;&#x2122;s name, the report name and the timestamp. This log file resides in /usr/isos/log.
Steps
1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Go to the log directory by typing: cd log
4. Open the watcher_mail.log file by typing: pg watcher_mail.log
Below is a sample configuration display: watcher_mail: Sent email to David for watcher_chan.rpt at Wed Sep 8 10:42:29 CDT 1999 watcher_mail: Sent email to Tony for watcher_chan.rpt at Wed Sep 8 10:42:29 CDT 1999 watcher_mail: Sent email to Fred for watcher_chan.rpt at Wed Sep 8 10:42:29 CDT 1999 watcher_mail: Sent email to Bob for watcher_chan.rpt at Wed Sep 8 10:42:29 CDT 1999
11-10
EXS ExchangePlus Software Operations Guide
Overview
12 SNMP and Alarm Monitoring Overview This chapter describes how to set up and monitor the SNMP, Network Node Manager, and Alarm Panel for ExchangePlus. For more hardware information see the ExchangePlus Hardware Product Description manual. The following table lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 86 Quick Start Reference for the SNMP Agent
12-2
Procedure 87 Setting up the SNMP Application
12-3
Procedure 88 Loading an EXS ExchangePlus MIB
12-6
Procedure 89 EXS-LE EMAC Alarm Panel Hardware Setup
12-9
Procedure 90 Upgrading the Alarm Panelâ&#x20AC;&#x2122;s Embedded Software 12-11 Procedure 91 Upgrading the Alarm Panelâ&#x20AC;&#x2122;s EPROM
12-12
Procedure 92 EXS-LE Alarm Panel Setup for Multi-Cabinets
12-13
Procedure 93 Setting up the Alarm Panel Hostname
12-15
Procedure 94 Alarm Panel and Pager Configuration
12-16
Procedure 95 Clearing an Alarm Panel Condition
12-21
Procedure 96 Viewing Alarm Panel Events
12-22
12-1
Quick Start Reference for the SNMP Agent
Procedure 86
EXS ExchangePlus Software Operations Guide
Quick Start Reference for the SNMP Agent The following is a quick start reference to bring up the SNMP agent. For additional information see “SNMP and MIB Reference” on page H-1 and “Traps Reference” on page I-1.
Assumptions
Steps
The host administrator should have a working knowledge of UNIX, the EXS ExchangePlus system, and HP OpenView. 1. Open a terminal window and go to /usr/isos. 2. Go to the bin directory by typing: cd bin
3. Edit the snmp.sh file and change the MIB directory path variable (MIBDIR) to /usr/isos/bin/mibs. 4. Edit the snmpd.conf file in /usr/isos/bin and change the two trapsink entries under Trap Setup to point to the IP address of your SNMP monitor computer. Verify that the community is set to icc. 5. Log in as superuser root and run snmpd.sh from the /usr/isos/bin directory. 6. Verify that the tasks snmpd and redirlog isossnmpd are running. 7. Copy the file /usr/isos/bin/mibs/icc-mib.txt to the HP OpenView computer. Rename the file to icc.mib. Import the icc.mib file into the HP OpenView program.
12-2
EXS ExchangePlus Software Operations Guide
Procedure 87
Setting up the SNMP Application
Setting up the SNMP Application The following setup procedures are to be performed manually on an initial install of the EXS ExchangePlus SNMP. For additional information see “SNMP and MIB Reference” on page H-1 and “Traps Reference” on page I-1.
Assumptions
Steps
The host administrator should have a working knowledge of UNIX and the EXS ExchangePlus system. The EXS ExchangePlus SNMP agent must be running to have the EXS ExchangePlus host function properly. 1. Stop any other SNMP agent that is running currently. Login as superuser root and type: ps -ef | grep snmpd
Write down the process ID (PID) of snmpd and redirlog if any. Type this command: kill-9 <snmpd process ID redirlog process ID>
This stops the snmpd and redirlog processes. The ExchangePlus SNMP agent uses the standard SNMP ports, UDP 161 for communications and UDP 162 for traps. If another SNMP agent is using the same port, the ExchangePlus SNMP agent will not startup. 2. Exit out of superuser. 3. Start up the vi editor and open up the snmpd.sh file from the /usr/isos/bin directory. 4. Modify the MIBDIRS variable by setting the variable to the mibs directory path. Add the following line: MIBSDIR=/usr/isos/bin/mibs
5. Save the file. 6. Open the snmpd.conf file and modify the trapsink variable in the Trap Setup section to the IP address where your network manager monitor (HP OpenView, for example) is running. An example would look like: trapcommunity icctrap1 trapsink 186.25.5.116 trapcommunity icctrap2 trapsink 186.25.5.116
7. While still in the snmpd.conf file, verify that the community variable is set as follows: 12-3
HP OpenView SNMP Network Node Manager
EXS ExchangePlus Software Operations Guide
community 1 icc
8. Save the file. 9. Login as root. Run the script file snmpd.sh from the directory of /usr/isos/bin. This will start the SNMP and redirlog processes. 10. Verify that the tasks snmpd and redirlog isossnmpd are running by typing the following: ps -ef | grep snmp
Both tasks process IDs should be displayed on the screen.
HP OpenView SNMP Network Node Manager HP OpenView
This section describes a Network Node Manager and its functions within the EXS ExchangePlus system.
Overview
Network Node Manager (NNM) provides tools for fault, configuration, and performance management for multivendor TCP/IP and IPX/SPX networks. You can use the NNM to:
12-4
•
Automatically discover your network environment and allow you to monitor its status.
•
View the current topology of your network using NNM's automatic discovery and mapping.
•
Diagnose and automatically respond to network faults and performance problems from a central location.
•
Manage any vendor device that supports the Simple Network Management Protocol (SNMP). NNM manages both standard and enterprise-specific Management Information Base (MIB) objects.
•
Use forms, tables, and graphs to view network and system configuration information for the nodes on your network.
•
Use a graphical user interface (GUI) to build new MIB applications for enterprise-specific MIBs.
•
Customize your management station by adding other tools and applications to the NNM menu bar.
•
Plan for future networking needs by performing MIB data collection, storage, and graphing for trend analysis.
EXS ExchangePlus Software Operations Guide
HP OpenView SNMP Network Node Manager
NOTE: For additional information refer to your licensed copy of the HP OpenView documentation.
Basic Concepts
Network Node Manager is a manager system. It supplies managers, such as the SNMP MIB Browser or the Desktop Management Interface (DMI) Browser, that monitor and control agent systems on your network. An agent system is a device, such as a host, gateway, server, hub, or bridge, that has interface software called an agent. An agent performs network management tasks at the request of the manager. The SNMP manager and agent communicate using Simple Network Management Protocol. NNM supports SNMP version 1 and Community-based SNMP version 2. An SNMP agent uses a Management Information Base (MIB) to retrieve information about the device on which it resides. The MIB acts as an index to network-related information about the device: network addresses, status conditions, network traffic statistics, and so forth. Each type of information is called a MIB object. When you install the Network Node Manager, it creates: 1. A database of objects for all the nodes that it discovers on your network. (It also stores objects that you create.) 2. A map. The map is a conceptual layout of your network and its systems. You can define properties for a map, but you cannot view it directly. You view the submaps that comprise the map. The submaps are an interactive environment of windows that NNM creates so that you can manage objects on your network. Submaps are typically organized hierarchically to show an increasing level of detail. A submap is a schematic representation of all or part of the network map. Each submap provides a different view of the same network map. The submaps let you vary your view of the network map from something as small as the software components on a single system to something as large as a worldwide network. The submap’s schematic representation of the network is created from symbols that represent network segments and connections. Symbols can represent a variety of entities on the network: • • • • • • •
PC-board Computer Printer A group of computers or printers A subnet A connection between two computers The interface for an entire network
You can choose how to organize the display of your network. In addition you can include or exclude any entities you want, and group them to suit your needs.
12-5
Loading an EXS ExchangePlus MIB
Procedure 88
EXS ExchangePlus Software Operations Guide
Loading an EXS ExchangePlus MIB Below are the steps for loading an EXS ExchangePlus MIB. For additional information, see “SNMP and MIB Reference” on page H-1 and “Traps Reference” on page I-1.
Assumptions
The host administrator should have a working knowledge of HP OpenView. The Load/Unload MIB operation loads MIBs into the internal Network Node Manager MIB database. The MIB for a device must be loaded before you can use the Browse MIB, MIB Data Collection, or MIB Application Builder commands, or use applications built by the MIB Application Builder. You can use the Load/Unload MIBs: SNMP command on the Options menu in HP OpenView to: •
Include your own enterprise-specific MIBs, or the enterprise-specific MIB for a device that you use on your network, into the loaded MIB database. Once you have loaded the new MIB, you can manage any of the MIB objects defined in that MIB.
•
Load Internet-standard MIBs.
•
Remove MIBs from the loaded MIB database.
MIBs are defined using an Internet-standard language called the Structure of Management Information, or SMI. This MIB loader supports both the original SNMP version 1 SMI and the newer SNMP version 2 SMI. Using HP OpenView perform the following steps:
Steps
1. Obtain a copy of the MIB definition file icc-mib.txt. Rename the file to icc.mib. 2. Copy the MIB definition file to the default MIB directory snmp_mibs on the computer that is running HP OpenView. 3. Choose Load/Unload MIBs: SNMP from the Options menu. The Load/ Unload MIBs: SNMP dialog box appears. 4. Click Load. The Load MIB from File dialog box appears. 5. Highlight icc.mib in the Loaded SNMP MIBs list. 6. Or type the filename of the MIB you want to load, using the full pathname in the MIB File to Load field. You can also click Browse to view the directories in the Load MIB from File selection list and select the directory and file that the MIB is in and Click Open. 7. Click Load.
12-6
EXS ExchangePlus Software Operations Guide
Loading an EXS ExchangePlus MIB
8. Click Close. The program returns to the Load/Unload MIBs dialog box, and the new MIB appears in the Loaded MIBs selection list. You can now access the new MIB when you use the Browse MIB operation, configure NNM to collect MIB data, build new MIB operations through the MIB Application Builder, or run the applications built by the MIB Application Builder.
Browsing the MIB
You can use the SNMP MIB Browser command on the Tools Menu in HP OpenView to access the MIB on agents. Use the Browse MIB operation to:
Prerequisites
•
Learn which MIBs are available for building diagnostic applications that monitor MIB values.
•
Query and display MIB objects that you use infrequently.
•
Troubleshoot problems with other MIB operations.
The following are prerequisites for browsing the MIB: •
You must select a node on the map before you can access the Browse MIB operation. Only one node can be selected. Otherwise, the Browse MIB operation is unavailable (dimmed).
•
To navigate the MIB and look at the objects in a module, the MIB must be loaded into the MIB database. To load the MIB, choose Load/Unload MIBs: SNMP from the Options menu.
•
The community names configured on the management station must match the community names that are configured on the agents. If the community names do not match, use the SNMP Configuration command on the Options menu to change the configuration so the manager can access agent MIB values using the correct community name.
•
If the agent is an HP SNMP Agent, you must configure it with a specific community name before the agent can respond to SNMP SetRequests.
12-7
Loading an EXS ExchangePlus MIB
Behavior
12-8
EXS ExchangePlus Software Operations Guide
The Browse MIB window contains the following: •
Read-write fields where you can specify the name or address of the agent that you want to query, the agent's community name, MIB object ID, MIB instance, and SNMP Set values.
•
A list from which you can select a MIB object for query.
•
Buttons to request descriptions of the objects, start and stop a query of the MIB, and graph values.
•
A Results area where the MIB values from a MIB query are displayed.
•
A Messages area where any errors or informational messages related to the operation are displayed.
•
A MIB Instance field where you can specify specific instances to be queried, set, or graphed.
EXS ExchangePlus Software Operations Guide
Procedure 89
EXS-LE EMAC Alarm Panel Hardware Setup
EXS-LE EMAC Alarm Panel Hardware Setup
Overview
In order for the alarm panel to function properly several parameters will need to be set. If these parameters are not set properly the unit may cause problems on the network.
Assumptions
A VGA monitor and standard PC keyboard will be required to setup the alarm panel.
Steps
To setup the alarm panel follow the steps outlined below. DO NOT connect the alarm panel to the network until it has been setup. 1. Connect the monitor and keyboard to the designated ports on the back of the alarm panel unit. 2. Connect the –48 volt power supply to the power connector on the rear of the alarm panel. 3. Power on the alarm panel. It will begin to boot up. Wait for the blue status screen to be displayed on the monitor. 4. Once the status screen is displayed, type a capital S: S
to enter the setup screen. Use the TAB and Arrow keys to navigate the screen and fill in the following fields: Local IP Address The local IP Address is the IP address of the alarm panel. This field must be filled in or the unit will not operate. See your network administrator for an IP Address. The alarm panel does not have the ability to acquire its address from the network. Port This field is the application port. The default shall be port number 3434; ports 0-1024 shall not be used as these are designated as “well known ports”. In the UNIX operating system, one must be a Superuser to access well known ports. Subnet Mask The subnet mask is provided for the user that has sub nets. If you are not concerned with sub netting, leave this at its factory default of 255.255.255.000.
12-9
EXS-LE EMAC Alarm Panel Hardware Setup
EXS ExchangePlus Software Operations Guide
Gateway IP Addresses The alarm panel can support up to 3 gateways. If there are no gateways on your network, leave these fields set as 000.000.000.000. NOTE: After changing the gateway in setup, you must reboot for it to take effect. Client Addresses The alarm panel can send its alarm messages to 4 clientâ&#x20AC;&#x2122;s. Use these fields to enter the IP addresses of all the clients that should receive alarm messages. At least the first client field MUST be filled in. A client is the Host machine of the alarm application. Modem Use the + and - keys to select either an internal or external modem. MAC Devices These fields are used to let the agent know what devices are connected to it. Highlight the desired MAC Device and use the + and - keys to select the correct device type. See Procedure 92 EXS-LE Alarm Panel Setup for MultiCabinets on page 12-13 for more information about adding multiple alarm panels together. NOTE: Do not change the device type of the first MAC-device. 5. Once all the desired fields have been filled in, press the F10 key to save the changes and return to the status screen. NOTE: Power to the alarm panel must now be cycled off and then back on for the changes to take effect.
12-10
EXS ExchangePlus Software Operations Guide
Procedure 90
Upgrading the Alarm Panel’s Embedded Software
Upgrading the Alarm Panel’s Embedded Software
Assumptions
A VGA monitor and standard PC keyboard will be required to setup the alarm panel.
Steps
The alarm panel has been designed to allow its software to be easily upgraded. To upgrade the internal software, follow the steps below: 1. Connect a VGA monitor to the VGA connector located on the rear of the alarm panel. Connect a standard PC/AT keyboard to the connector labeled keyboard. The alarm panels monitoring screen should now be displayed. If it is not, cycle the alarm panel units power off then on. 2. To Exit the MacAgent software, press Escape <Esc>. The screen should now display the A:> prompt. 3. At the A:> prompt, type tftp serve
to start the TFTP server. The screen should now display PC/TCP TFTP Server Initialized
Connect to the network via the Ethernet connection on the rear of the alarm panel. 4. At any PC on the network, start a TFTP client and upload the new copy of macagent.exe to the alarm panel. To start a TFTP client, open a DOS window and “cd” to the directory where macagent.exe was saved. At the command line, type the following command: tftp [-I] host [get | put] source [destination]
An example of this would be: tftp -I 10.1.18.52 put macagent.exe
NOTE: The host field is the IP address of the alarm panel 5. To exit the TFTP server in the alarm panel, press e and the screen will return to the A:> prompt. 6. From the A:> prompt, type macagent.exe
then press Enter, and the blue monitoring screen will appear. The alarm panel will remember all of its previous settings so it is not necessary to reset the unit. The alarm panel is now ready for operation. 7. Disconnect the keyboard and monitor from the rear of the alarm panel.
12-11
Upgrading the Alarm Panelâ&#x20AC;&#x2122;s EPROM
Procedure 91
EXS ExchangePlus Software Operations Guide
Upgrading the Alarm Panelâ&#x20AC;&#x2122;s EPROM
Assumptions
The host administrator should have a working knowledge of the alarm panel hardware.
Steps
To upgrade the EPROM inside the alarm panel unit, follow the steps below: 1. Remove the front ears, face plate, and top cover. 2. Remove the front screw securing the embedded PC board. 3. Pivot the embedded PC board on its hinge to gain access to the EPROM IC chip. 4. Remove the EPROM (IC with the white label) and replace it with the newer version. 5. Return the board to its original position. 6. Replace the front screw, front ears, face plate and top cover.
12-12
EXS ExchangePlus Software Operations Guide
Procedure 92
EXS-LE Alarm Panel Setup for Multi-Cabinets
EXS-LE Alarm Panel Setup for Multi-Cabinets
Overview
In order for the EMAC server alarm panel to function properly with other ANN-2 client alarm panels, you need to follow the steps below.
Assumptions
The host administrator should have a working knowledge of the alarm panel hardware. The EMAC server alarm panel unit is already installed and working. A VGA monitor and standard PC keyboard will be required to setup the alarm panel.
Steps
To setup the alarm panels follow the steps outlined below. DO NOT connect the alarm panel to the network until it has been setup. 1. Connect the monitor and keyboard to the designated ports on the back of the EMAC alarm panel unit. Wait for the blue status screen to be displayed. 2. Once the status screen is displayed, type a capital S: S
to enter the setup screen. Use the TAB and Arrow keys to navigate the screen to the MAC Devices. These fields are used to let the agent know what devices are connected to it. Highlight the desired MAC Device and use the + and keys to select the correct device type. NOTE: Do not change the device type of the first MAC-device. This address should always be 0001. 3. Add the new ANN-2 alarm unit(s) to the MAC Devices list. Each additional ANN-2 address should be incremented by one (1). 0001 is the EMAC server alarm panel address and the next ANN-2 client alarm panel should start with 0010. 4. Before installing the new ANN-2 device(s), remove the top cover of the expansion device and set the dip switches for the ANN address.
12-13
EXS-LE Alarm Panel Setup for Multi-Cabinets
EXS ExchangePlus Software Operations Guide
5. Set the dip switches as specified in the table below: S3-2 Closed = Output Relays Remote Mode S3-2 Open = Output Relays Local Echo Mode S2-3 Open = EMAC Output Relays drive ANN alarm inputs (set this dip switch on the ANN unit). Position Number
S2 Mode Select
S3 Options
S4 Speed
1
Open
Open
Open
2
Open
Open
Open
3
Open
Open
Open
4
Open
Open
Open
5
Closed
Open
6
Closed
Open
7
Closed
Open
8
Open
Open
S5 Address ANN-2 Address
6. Install the ANN-2 device(s) into the 19 inch rack(s). 7. Connect a DATA cable(s) from the EMAC RS-485 Expand port to the ANN-2 COM2 RS-485 port. Do not use a standard telephone type cable that reverses the connections between ends. Use only a DATA type cable that maintains the same pin positions at each end. 8. Follow and verify that the steps in Procedure 93 Setting up the Alarm Panel Hostname on page 12-15 and Procedure 94 Alarm Panel and Pager Configuration on page 12-16 have been accomplished. Trigger alarms to and from the expansion ANN-2 device(s) to check for correct setup and communication on the RS-485 line.
12-14
EXS ExchangePlus Software Operations Guide
Procedure 93 Assumptions
Setting up the Alarm Panel Hostname
Setting up the Alarm Panel Hostname The host administrator should have a working knowledge of the ExchangePlus system and vi. Before the alarm panel can be enabled by the SNMP process snmpd, verify that the hosts file has the alarm panel hostname IP address listed. For more information see “SNMP and MIB Reference” on page H-1, “Traps Reference” on page I-1, and “Appendix J. Alarm Panel Switch Alarms” on page J-1.
Steps
1. Go into superuser mode by typing su and the password name. su <your password>
2. Go to the /etc directory. 3. Enter the editor mode by typing: vi hosts
Below is an example of a hosts file with two nodes. # # host table # 185.16.156.10 185.16.156.11 185.16.156.12 185.16.156.13 185.16.156.14 185.16.156.15 185.16.156.16
HOST1 HOST2 excel11 excel12 alarmpanel1 excel21 excel22
Verify that an IP address for the alarm panel is present. If it is not, check with the system administrator to get the IP address and add the alarmpanel1 line similar to above to the /etc/hosts file. The alarm panel hostname must be entered as alarmpanel<n> where n is a number from 1 to 6. Include the alarm panel names for all nodes on the site. Also, when new nodes are added, the /etc/hosts file must be updated for both the new node IP addresses and the alarm panel entry. 4. Save and quit the editor by typing: :wq! :q!
12-15
Alarm Panel and Pager Configuration
Procedure 94 Assumptions
EXS ExchangePlus Software Operations Guide
Alarm Panel and Pager Configuration The host administrator should have a working knowledge of the ExchangePlus system and vi. The snmpd.conf file is used to setup the following: • • • • • •
ExchangePlus SNMP agent Enable alarm panel Buzzer setup Pager setup for Numeric pagers Pager interval setup Pager number of retries setup
The alarmpanel.cfg file is used to setup the following: • •
Node to alarm panel mapping Alarm message mapping which consists of the alarm number, the alarm level, the alarm indicator, individual message paging option, and alarm message.
Both files are located in the /usr/isos/bin directory. For more information see “SNMP and MIB Reference” on page H-1, “Traps Reference” on page I-1, and “Appendix J. Alarm Panel Switch Alarms” on page J-1.
Steps
1. Using vi, open up the file snmpd.conf to edit the options listed below: vi snmpd.conf
Find the alarm panel setup section. The text messages after the # symbol are commented out. It should look similar to the following: # Alarm Panel Setup # # 0=Disabled # | enablealarmpanel 1 #
12-16
1=Enabled
EXS ExchangePlus Software Operations Guide
Alarm Panel and Pager Configuration
Input a 0 for disabled or a 1 to enable the alarm panel. # # Alarm Panel Pager Setup # # Pager Name # | # | Pager number # | | # | | Pager Type (N -numeric) # | | | # | | | (A - PIN Number, N - not used) # | | | | # | | | | pager1 2145645803 N 00000 #pager1 #pager2 #pager3 #pager4 #pager5
18005555555 18004444444 18002222222 18007777777 18005551212
N N N N N
33333 11111 00000 55555 12122
Type in the pager name/person name followed by the pager number, pager type of numeric, and the pager pin number if used. These pager numbers will be used for both the loss of poll paging and the critical alarm paging. Numeric pagers will display a decimal indication of the entity and alarm number. For more information on the alarms see â&#x20AC;&#x153;Appendix J. Alarm Panel Switch Alarmsâ&#x20AC;?. The system will initiate a numeric page starting with the first name indicated in the list. If the alarm is not cleared and pagernumberofretries is configured, the page will be resent within the paging interval up to the number of retries configured. If the alarm has not been cleared and there are additional paging entries, the system will continue to the next pager number in the list. If the system reaches the end of the list, it will start over at the first pager until such time as the alarm condition is cleared. # # Alarm Panel Pager Interval Setup # pagerinterval 3
The paging will repeat itself at the pagerinterval value until the alarm is acknowledged or until it has retried the pager for the pagernumberofretries value. The pagerinterval value is set in minutes and the default value is 5 minutes between pages. # # Alarm Panel Pager Retries Setup # pagernumberofretries 2
12-17
Alarm Panel and Pager Configuration
EXS ExchangePlus Software Operations Guide
The paging will be re-transmitted to that pager number up to the pagernumberofretries value before going on to the next pager number on the list. If the system reaches the end of the list, it will start over at the first pager until such time as the alarm condition is cleared. 2. Save the file snmpd.conf and exit. 3. Using vi, open up the file alarmpanel.cfg to edit the options listed below: vi alarmpanel.cfg
4. Edit the node number and alarm panel number to match your system. This is the default setup. Node is the logical switch node number. ANN is the server alarm panel or the client alarm panel ID number. The text messages after the # symbol are commented out. ######################################################## # NODE TO ALARM PANEL MAPPING ######################################################## # Node: EXS Logical Switch Node # ANN: EMAC or ANN Alarm Panel ID # # Node ANN #------------------------------------------------------NODE 1 1 NODE 2 1 NODE 3 2 NODE 4 2 NODE 5 2 NODE 6 2 NODE 7 3 NODE 8 3 NODE 9 3 NODE 10 3 NODE 11 4 NODE 12 4 NODE 13 4 NODE 14 4 NODE 15 5 NODE 16 5 #
5. Edit the alarm message mapping section to change the default settings for the EXS switch B9 alarms. You can configure the alarm level, informative indicator, page sent, and message. The map is sectioned off into general alarms, card alarms, span alarms, channel alarms, DSP alarms, EXS node alarms, alarm panel originated alarms, watcher alarms, and special messages.
12-18
EXS ExchangePlus Software Operations Guide
Alarm Panel and Pager Configuration
It should look similar to the following partial listing: # # # # ############################################################### # ALARM MESSAGE MAPPING SECTION ############################################################### # Alarm Number: For EXS Alarms is ’aabb ’where ’aa’ is hex # entity number and ’bb’ is isos alarm. For clear alarm # messages use ’aabb’ + 0x8000. # For other alarms use 4 digit hex number. # # Level: CRITICAL - Sounds critical alarm buzzer and # flashes critical red LED. # MAJOR - Sounds major alarm buzzer and # flashes red major LED. # MINOR - Sounds minor alarm buzzer and # flashes minor yellow LED. # INFO - Flashes green LED. # CLEAR - Resets flashing yellow LEDs to flashing # green LED state. # RESET - Sets all LEDs to green and silences alarm # buzzer. # # Indicators: POWER - POWER LED on Alarm Panels # SYNC - SYNC LED on Alarm Panel # CARD - CARD LED on Alarm Panel # CIRCUIT- CIRCUIT LED on Alarm Panel # EXNET - EXNET LED on Alarm Panel # SYSRES - SYSRES LED on Alarm Panel # CCSIG - CCSIG or COMM LED on Alarm Panel # REDUND - REDUND LED on Alarm Panel # HOST - HOST LED on Alarm Panel # APMAINT- APMAINT or MAINT LED on Alarm Panel # FAN - FAN/TEMP LED on Alarm Panel # TEMP - FAN/TEMP LED on Alarm Panel # EXTSW - EXTSW or DOOR LED on Alarm Panel # EXTHW - EXTHW or EXT LED on Alarm Panel # ALL - All LED’s # NONE - No LED’s # # Paging: Y - Send Page # N - Don’t Send Page # # Message: Decimal alarm numbers are sent to Numeric # Pagers. #
12-19
Alarm Panel and Pager Configuration
EXS ExchangePlus Software Operations Guide
#-------------------------------------------------------------# General Alarms # #-------------------------------------------------------------#Alarm Number Level Indicators Page Message #-------------------------------------------------------------0101 CRITICAL SYSRES Y System Busy Condition 0102 MAJOR SYNC N Clock Mode Switched 0103 MAJOR SYSRES N Hardware Cannot Support DSP Function Type 0104 MAJOR SYNC N Reference 1 Clock Source Lost 0105 MAJOR SYNC N Reference 2 Clock Source Lost
6. Save the file alarmpanel.cfg and exit. 7.
After editing the configuration files, you will need to restart the snmp. If you need to setup the SNMP application, please see Procedure 87 Setting up the SNMP Application on page 12-3. Log in as superuser root and type: ps -ef | grep snmpd
Write down the process ID (PID) of snmpd and redirlog if any. Type this command: kill-9 <snmpd process ID redirlog process ID>
This stops the snmpd and redirlog processes. The ExchangePlus SNMP agent uses the standard SNMP ports, UDP 161 for communications and UDP 162 for traps. If another SNMP agent is using the same port, the ExchangePlus SNMP agent will not startup. 8. Exit out of superuser. 9. Login as root. Run the script file snmpd.sh from the directory of /usr/isos/bin. This will start the SNMP and redirlog processes. 10. Verify that the tasks snmpd and redirlog isossnmpd are running by typing the following: ps -ef | grep snmp
Both tasks process IDs should be displayed on the screen.
12-20
EXS ExchangePlus Software Operations Guide
Procedure 95
Clearing an Alarm Panel Condition
Clearing an Alarm Panel Condition This procedure shows how to clear or reset an alarm panel condition located on the alarm panel in your system.
Assumptions
Steps
The host administrator should have a working knowledge of the ExchangePlus system. 1. Pull down the Maint menu and select Clear Alarm Panel. 2. All of the alarms (severity and informational) on the alarm panel and the buzzer should turn off (go to a steady green state). NOTE: Alarms and statuses are retained until the alarm condition changes.
12-21
Viewing Alarm Panel Events
Procedure 96
EXS ExchangePlus Software Operations Guide
Viewing Alarm Panel Events This procedure shows how to view the alarm panel events that are in the file system.log from the UNIX command line. See Procedure 76 Viewing System Log on page 9-18 about viewing the system.log file using xmenu. The system log displays errors and contains the contents of the host message log.
Assumptions
Steps
The host administrator should have a working knowledge of the ExchangePlus system and UNIX. 1. Open a terminal window and go to /usr/isos. 2. Go to the log directory by typing: cd log
3. View the contents of the file system.log by typing: more system.log
4. Press the spacebar to see the next page of events. All alarm messages include the following information:
12-22
•
Time and Date stamp
•
The severity of the event (Critical, Major, Minor or Informative)
•
An alarm description
EXS ExchangePlus Software Operations Guide
Overview
13 Backup Overview It is imperative that you make frequent backups system configurations. In the event of a disk crash, accidental deletion, or corruption of files, these files can be used to recover and restore the latest version of the data or program. A careful backup plan ensures the ability to minimize downtime.
Procedure Name
Page
Procedure 97 Backup for ExchangePlus
13-2
13-1
Backup for ExchangePlus
Procedure 97
EXS ExchangePlus Software Operations Guide
Backup for ExchangePlus The following procedure enables the backup of critical data for ExchangePlus via a telnet session. Use this procedure in addition to any routine backups performed on the entire computer system. Every file that contains vital system configuration or account information (such as CDRs) should be backed up daily into a separate directory. That information should be sent to an alternate host, preferably a remote system, backed up to a tape media, or to some other storage device. The backup script expects the CDRs to be in the /usr/isos/bin directory and will always back them up to the /usr/isos/backup directory.
Creating Compressed Files
This procedure describes how to use the backup script to backup your data. NOTES: 1. Prior to performing a backup, you must ensure the following conditions are met. Failure to follow these steps may result in the loss of CDRs. 2. This backup process does not remove any files from /usr/isos/bin. Therefore, if backup is run again before CDRs that have already been backed up have not been deleted, then those same CDRs will be backed up again. 3. If you are performing a backup to disk, ensure that: •
Sufficient disk space is available for the backup files.
•
Files are being written on a periodic basis. If you have a high call volume, you should check that files are backed up more often.
•
You remove .Z files periodically from the directory.
•
You do not remove the /usr/isos/bin/cdr.txt.<date> file until you are sure that the CDRs are safely in the .Z file. However, it is recommended that you delete these files once you have verified that they have been backed up.
4. If you have purchased the tape backup option and you are performing a backup to tape, ensure that:
13-2
•
Sufficient space is available on the tape for the backup file.
•
You do not remove the /usr/isos/bin/cdr.txt.<date> file until you are sure that the CDRs are safely in the .Z file. However, it is recommended that you delete these files once you verify that they have been backed up.
EXS ExchangePlus Software Operations Guide
Steps
Backup for ExchangePlus
1. Log into the system. Go to the /usr/isos/bin directory. You should see a prompt similar to: (XL909M241F) /usr/isos/bin (258)$
where XL909M241F is the host name 2. Type the following command and press <Enter>: backup <filetype> <destination>
where <filetype> is sys or cdr and <destination> is disk or tape (if you purchased the tape option). The exact command lines that are allowed are as follows: backup backup backup backup
sys cdr sys cdr
tape tape disk disk
This command generates the backup for the selected type of files. The process will run until all files have been compressed into the /usr/isos/backup directory for subsequent transfer to an alternate host. 3. The file will be date-stamped, and you will see the following message when the backup process is completed: Successfully generated backup file: ultra_cdr[or sys]Jan06_cdr[or sys]_153805.Z End of backup script
The format of the backup file name in the message is: <host name>_<cdr or sys>MMMDD_<cdr or sys>_HHMMSS.Z
The .Z has been added automatically to the end of the filename to show this file has been compressed. 4. When finished, you will be returned to the prompt: (XL909M241F) /usr/isos/bin (259)$
Identifying CDR Files
The following procedure allows you to identify CDR files that have been backed up. It is important to identify these files so they can be moved from the /usr/isos/bin directory to another safe storage location for two reasons: â&#x20AC;˘
So they do not get backed up again the next time the backup script is run (Your billing system may have problems if you have duplicate entries in different backups).
â&#x20AC;˘
So they can be easily deleted once you have verified that the CDRs have been safely backed up.
13-3
Backup for ExchangePlus
Steps
EXS ExchangePlus Software Operations Guide
To identify the CDR files have been backed up, do the following: 1. Just prior to running the backup script, type the following command in the /usr/isos/bin directory: ls -lrt cdr.txt.*
This lists the CDR files in the /usr/isos/bin directory in reverse time order. 2. Make a note of the timestamp on the last CDR file. In this document, this time is referred to as the â&#x20AC;&#x153;backup time.â&#x20AC;? 3. Run the backup script as described in the previous procedure. 4. When the backup is complete, type the following command again: ls -lrt cdr.txt.*
This command lists the CDR files in the /usr/isos/bin directory after the backup has been performed. If there are any files with a timestamp later than the backup time noted in Step 2, then these files were generated after the backup. All files generated after the backup should not be moved. 5. Once you know which files can be moved (all those with a timestamp before or at the backup time, use the UNIX move command (mv) to put the CDRs into another storage location (another directory on the host or on some other system). When you are able to verify that the CDRs have all been safely backed up, you can then delete them from the /usr/isos/bin directory.
Storing Compressed Files Steps
The following steps enable you to ftp the compressed file to the alternate host for storage using the put command. 1. On the prompt line you will see: (XL909M241F) /usr/isos/bin (262)$
Type in the ftp command and the host name or IP address of the alternate remote host where the file will be stored. The IP address shown here is an example: ftp 135.119.50.32
The successful response will be: Connected to 135.119.50.32. 220 XL914M25CD FTP server (SunOS 5.7) ready. Name (135.119.50.32:isos):
13-4
EXS ExchangePlus Software Operations Guide
Backup for ExchangePlus
2. Enter the telnet ftp session by typing the name: isos
The response will be: 331 Password required for isos. Password:
3. Type in a password and press <Enter>. The response will verify that you are logged on: 230 User isos logged in. ftp>
4. Type the following, then press <Enter>: hash
This command allows you to see the progress of the transfer later on. (Every 15-30 seconds, depending on the size of your file, you will receive hash marks as feedback, once the process begins.) The response will be: Hash mark printing on (8192 bytes/hash mark). ftp>
5. Type the following, then press <Enter>: bin
This command type sets the transfer mode to binary, which is very important. The response will be: 200 Type set to I. ftp>
6. Type the following at the in the following for the â&#x20AC;&#x153;Print Working Directoryâ&#x20AC;?: pwd
The response will be: 257 "/usr/isos" is current directory. ftp>
7. Change the directory by typing the following command and then press <Enter>: cd /usr/isos/bin
The response should indicate success: 250 CWD command successful. ftp>
13-5
Backup for ExchangePlus
EXS ExchangePlus Software Operations Guide
8. Enter the put command, which will transfer the file to the remote computer. Include the name of the file you want to put: put <filename>.isosbin.tar.Z
The response will be: 200 PORT command successful. 150 Binary data connection for <filename>.isosbin.tar.Z (135.119.50.31,32964).
The transfer begins at this point, and the hash marks will appear until the transfer is done. As many as ten lines or more of hash marks could appear, depending on the size of the file: #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### #####...###### ###
When the transfer is finished, the response will be: 226 Transfer complete. local: <filename>isosbin.tar.Z remote: <filename>.isosbin.tar.Z 21791420 bytes sent in 19 seconds (1106.33 Kbytes/s) ftp>
9. Close the ftp session by typing: bye
The response will be: 221 Goodbye.
You are now out of the ftp session and back to the original setup shown at the beginning of the telnet session with command number 259. You should remove the CDR files that were included in the .Z backup file from the /usr/isos/bin directory.
13-6
EXS ExchangePlus Software Operations Guide
Overview
14 Maintenance and Troubleshooting Overview This chapter describes a number of maintenance activities you may need to perform on your ExchangePlus system. The following table lists all the procedures and the page number on which you can find the procedure. Procedure Name
Page
Procedure 98 Starting the Host Controller
14-2
Procedure 99 Restarting a Host
14-6
Procedure 100 Stopping the cron Job
14-9
Procedure 101 Starting the cron Job
14-10
Procedure 102 Changing the Host Name
14-11
Procedure 103 Removing Old CDR Files
14-13
Procedure 104 Taking a Span Out of Service (OOS)
14-14
Procedure 105 Taking Trunks Out of Service
14-15
Procedure 106 Deleting or Re-assigning a T1 or E1 Span
14-16
Procedure 107 Bouncing the Channels
14-18
Procedure 108 Reloading Trunk Instructions
14-19
Procedure 109 SS7 Channels Are Not Processing Traffic
14-21
Procedure 110 Cannot Write CDRs
14-23
Procedure 111 Changing Time Zones on ExchangePlus Hosts
14-25
Procedure 112 Calls Stop on a Particular Node
14-27
Procedure 113 Downloading Firmware
14-28
14-1
Starting the Host Controller
Procedure 98
EXS ExchangePlus Software Operations Guide
Starting the Host Controller This procedure describes how to start the host controller on a redundant system from the UNIX command line. If your system is not redundant, skip the steps for the standby host (Steps 1-3 and Step 15). NOTE: This procedure should only be used the first time you are starting the system or in the unlikely event that you need to restart a system from the seed file, switch.cfg (because the configuration in memory is corrupted). Otherwise, you should always restart the system from memory (See Procedure 99 Restarting a Host on page 14-6.)
Requirement
This task must be started by the system user, ISOS, not the ROOT. Otherwise undesired system operation may occur. To determine what user you are logged in as, type: whoami
at the UNIX command line.
Steps
1. On the standby host, go to /usr/isos/bin by typing: cd /usr/isos/bin
2. If you are restarting a standby host that was running, stop the cron job by typing: crontab -r
You can verify that the cron job is stopped by typing crontab -l
The following message should be displayed if the cron job is stopped. crontab:canâ&#x20AC;&#x2122;t open your crontab file
3. Stop the host processes on the standby host by typing: stopit
4. On the master host, go to /usr/isos/bin by typing: cd /usr/isos/bin
5. If you are restarting a master host that was running, stop the cron job by typing: crontab -r
14-2
EXS ExchangePlus Software Operations Guide
Starting the Host Controller
You can verify that the cron job is stopped by typing: crontab -1
The following message should be displayed if the cron job is stopped. crontab:canâ&#x20AC;&#x2122;t open your crontab file
6. If you are using the Database format to save your CDRs, save cdr.dbf file to cdr.dbf.save. cdr.dbf contains the last CDRs that have not yet been rolled over. To do this type the following on the master host: cp cdr.dbf cdr.dbf.save
7. Stop the host processes on the master host by typing: stopit
8. Delete all *.dbf and *.cdx files on the master host by typing: rm *.dbf rm *.cdx
9.
Clear all shared memory on the master host by typing: cleanall ipcs
If the result is a listing of one to three entries, continue to the next step. If there are more than three entries, type: cleanall ipcs
again. If the result is a listing of one to three entries, continue to the next step. If there are more than three entries, call Lucent Technologies Technical Support. 10. Read the seed file (switch.cfg) into shared memory tables of the master host by typing: readcfg <filename>
You only need to enter the file name if your default switch configuration file is stored in a file other than switch.cfg. This command downloads the configuration file into shared memory tables. You can also perform this same function by pulling down the System menu in xmenu and selecting Load Switch Config. It will take a few minutes for the system to read and load the switch configuration file.
14-3
Starting the Host Controller
EXS ExchangePlus Software Operations Guide
11. Type the following on the master host: dbcp
to copy the configuration information from the shared memory tables to the database file. Once you have performed this function and restarted the system, any changes you make to the configuration using xmenu or menu should be automatically updated in both the memory and the database files. 12. To start the master host, type: startup <start level>
where <start level> is defined as: Start Level
Description
0
Restarts the host, using the configuration in the memory tables. The switch is not taken out of service as no configuration is downloaded to the switch. Use this level if the switch is already configured.
3
Takes the switch out of service by sending a new configuration to the switch based upon the shared memory tables in the host and in the board.cfg file.
7
Takes the switch out of service by sending a new configuration to the switch based upon the shared memory tables in the host and in the board.cfg file. Performs all Level 3 functions and also configures an EXNET ring.
NOTE: Depending on the start level selected, the host is either ready for use immediately (Level 0) or in several minutes (Level 3 or 7). 13. You can also start the master host via xmenu by pulling down the System menu and selecting Start Host Control. The Start Host window appears (Figure 14-1).
Figure 14-1 Start Host Window
Enter the appropriate Start Level (see the description of start levels above), then click Apply.
14-4
EXS ExchangePlus Software Operations Guide
Starting the Host Controller
14. Once the master host has been started, restart the cron job by typing: crontab cron.dat
If you cron job is started successfully, messages similar to the following will be displayed: # Module: cron.dat # SCCS ID 1. # # This script will check the ISOS running # if not, then it will start it # Minute, Hour, Day, Month, Month * * * * * /usr/isos/bin/restart > 7 15 * * * /usr/isos/bin/rollover
to see if it is
of year, Day of week /dev/null > dev/null
15. Go to the standby host and type the following to restart it at Level 0: crontab cron.dat
14-5
Restarting a Host
Procedure 99
EXS ExchangePlus Software Operations Guide
Restarting a Host Typically, when the system is installed and brought up, the host runs continuously and does not need to be restarted on a regular basis. However, in some circumstances you may need to restart the host. This procedure describes how to restart the hosts on a redundant system. If your system is not redundant, skip the steps for the standby host (Steps 1-3 and Step 11). NOTE: Anytime you stop the host, you stop call processing. Only restart the host (or both hosts in a redundant system) when absolutely necessary. By default, a scheduled job, called a cron job, runs on ExchangePlus. Every minute, it checks whether or not the host is running. If it finds the host is not running, it attempts to restart it automatically. Typically, you leave this cron task running all the time, so normally there should be no need to manually restart the system. If the switch goes down due to a power failure, use the following procedure. The switch will not reload the slot instructions. To avoid problems: • •
Requirement
When creating the initial configuration, assign all spans in sequential order, even if they are not being used. Configure unused spans for Clear Channel.
This task must be started by the system user, ISOS, not the ROOT. Otherwise undesired system operation may occur. To determine what user you are logged in as, type: whoami
at the UNIX command line.
Steps
To restart the host: 1. On the standby host, go to /usr/isos/bin by typing: cd /usr/isos/bin
2. If you are restarting a standby host that was running, stop the cron job by typing: crontab -r
You can verify that the cron job is stopped by typing crontab -l
The following message should be displayed if the cron job is stopped. crontab:can’t open your crontab file
14-6
EXS ExchangePlus Software Operations Guide
Restarting a Host
3. Stop the host processes on the standby host by typing: stopit
4. On the master host, go to /usr/isos/bin by typing: cd /usr/isos/bin
5. If you are restarting a master host that was running, stop the cron job by typing: crontab -r
You can verify that the cron job is stopped by typing: crontab -1
The following message should be displayed if the cron job is stopped. crontab:canâ&#x20AC;&#x2122;t open your crontab file
6. Stop any processes that are running on the master host by typing: stopit
7. Clear the shared memory on the master host by typing: cleanall
8. Copy the configuration from the database files to shared memory on the master host by typing: dbcp1
9. To start the master host, type: startup <start level>
where <start level> is defined as: Start Level
Description
0
Restarts the host, using the configuration in the memory tables. The switch is not taken out of service as no configuration is downloaded to the switch. Use this level if the switch is already configured.
3
Takes the switch out of service by sending a new configuration to the switch based upon the shared memory tables in the host and in the board.cfg file.
7
Takes the switch out of service by sending a new configuration to the switch based upon the shared memory tables in the host and in the board.cfg file. Performs all Level 3 functions and also configures an EXNET ring.
14-7
Restarting a Host
EXS ExchangePlus Software Operations Guide
NOTE: Depending on the start level selected, the host is either ready for use immediately (Level 0) or in several minutes (Level 3 or 7). You can also start the master host via xmenu by pulling down the System menu and selecting Start Host Control. The Start Host window appears (Figure 14-2).
Figure 14-2 Start Host Window
Enter the appropriate Start Level (see the description of start levels above), then click Apply. 10. Once the master host has been started, restart the cron job by typing: crontab cron.dat
If you cron job is started successfully, messages similar to the following will be displayed: # Module: cron.dat # SCCS ID 1. # # This script will check the ISOS running # if not, then it will start it # Minute, Hour, Day, Month, Month * * * * * /usr/isos/bin/restart > 7 15 * * * /usr/isos/bin/rollover
to see if it is
of year, Day of week /dev/null > dev/null
11. Go to the standby host and type the following to restart it at Level 0: crontab cron.dat
14-8
EXS ExchangePlus Software Operations Guide
Procedure 100
Stopping the cron Job
Stopping the cron Job ExchangePlus contains a cron job which automatically performs two functions at a customer-specified time interval. The cron job: • •
Periodically checks to see if the ExchangePlus software is running. If it is not running, it restarts it. Periodically rolls over the Call Detail Record (CDR) files. This means that the CDR data that has been collected is written to a file containing a timestamp in its name and new CDR data is collected in the active CDR file. By rolling CDR data over, you can use it for billing purposes.
The cron job is called cron.dat and the file is located in /usr/isos/bin directory. “Chapter 3. Setting up System Options” on page 3-1describes how to set up the cron job to perform the tasks at the desired interval. This procedure describes how to manually stop the cron job. You stop the cron job when you want to bring the host down to change the configuration. If you don’t stop the cron job, it will detect that the host is down and may attempt to restart it before the new configuration is loaded. This can result in your host coming up sooner than you expected and the correct configuration may not be installed in the host.
Steps
1. Go to the terminal window and type: crontab -r
2. To check if the cron job is running, type: crontab -l
If the result is: crontab:can’t open your crontab file
if the cron is not running.
14-9
Starting the cron Job
Procedure 101
EXS ExchangePlus Software Operations Guide
Starting the cron Job See Procedure 9 Starting the cron Job on page 3-5 for information on how to manually start the cron job.
14-10
EXS ExchangePlus Software Operations Guide
Procedure 102
Changing the Host Name
Changing the Host Name This procedure describes how to change the host name that is displayed in xmenu or menu, or the host name that appears in the command prompt. For example, you would use this procedure if you wanted to change the host name from XL11281025 to Hyannis1. If your host is one of the hosts in a redundant system, you will need to edit some files on the adjacent host, so that it knows the new name. If your are renaming both hosts in a redundant system, repeat this entire procedure for both hosts.
Assumptions Steps
You know the root password and have permissions to log in as root. 1. Log in as root. 2. Using a text editor such as vi, open the /etc/hosts file. An sample file is shown below: # # Internet host table # 127.0.0.1 localhost 135.119.51.60 XL11281025 10.10.138.10 excel11 10.10.138.11 excel12 135.119.51.1 gateway 135.119.51.62 mandrake
loghost
3. Edit the file to change the host name. In this file above you would edit the following line: 135.119.51.60
XL11281025
loghost
For example, to change the name XL11281025 to Hyannis1, you would change the line as follows: 135.119.51.60
4.
Hyannis1
loghost
Save the file.
5. Using vi, open the /etc/hostname.hme0 file. An sample file is shown below: # # Primary host name # XL11281025
14-11
Changing the Host Name
EXS ExchangePlus Software Operations Guide
6. Edit the file to change the host name. In this file, you would edit the following line: XL11281025
For example, to change the host name XL11281025 to Hyannis1, you would change the line as follows: Hyannis1
7.
Save the file.
8. At the command prompt, type: hostname <new host name>
In this example, <new host name> is Hyannis1. 9. If the host whose name has been changed is a host in a redundant system, then log onto the adjacent host and use vi to edit each of the following files: .rhost copydb redu.cfg startup
In each of these files you need to edit the adjacent host name to reflect the new name that you just added. Save each of the files when you have finished editing them. 10. Log out of the system and log back in to verify that the change took place. If you are working with a redundant system, and are renaming both hosts, repeat this procedure for the redundant host.
14-12
EXS ExchangePlus Software Operations Guide
Procedure 103
Removing Old CDR Files
Removing Old CDR Files Once a month you should clean out all the old CDR files in the /usr/isos/bin directory. Even if you have copied these files onto a billing system, the original timestamped files remain on the system.
Steps
1. Go to the /usr/isos/bin directory and determine if you have numerous old CDR files by typing: cd /usr/isos/bin ls -l cdr*
These commands list of all CDR files in the bin directory. Look for the files titled cdr.txt.<YYYYMMDDHHMMSS>. If you have already copied the files in this directory to the billing system, you may no longer need them. If this is the case, you can remove them. 2. To remove an individual file, type: rm cdr.txt.YYYYMMDDHHMMSS
3. To remove all CDR files from the previous month, type: rm cdr.txt.YYYYMM*
For example, if it is currently May and you want to remove all the old CDR files from April, type: rm cdr.txt.199904*
NOTE: If you use the wild card option, be careful not to remove any files that you want to save.
14-13
Taking a Span Out of Service (OOS)
Procedure 104 Steps
EXS ExchangePlus Software Operations Guide
Taking a Span Out of Service (OOS) 1. Go to the Maint menu and select Set Span State. The Set Span Service State window appears (Figure 14-3).
Figure 14-3 Set Span Service State Window
2. In the Span field, enter the number of the span you want to take out of service. NOTE: You need to know the range of spans in your system and the Span ID of the one you want to take out of service. 3. In the State field, select Down to take the selected span out of service. 4. Click Apply. The spans are taken out of service immediately. NOTE: The reverse of taking a span out of service is to bring it in service (INS). Do this by choosing Up in the State field.
14-14
EXS ExchangePlus Software Operations Guide
Procedure 105 Steps
Taking Trunks Out of Service
Taking Trunks Out of Service 1. From the Maint menu, select Set Channel State. The Set Channel Service State window appears (Figure 14-4).
Figure 14-4 Set Channel State Window
2. In the From and To fields, enter the range of spans and channels you want to take out of service. For example: Enter Span 1 Chan 2 in the From fields and Span 2 Chan 8 in the To field. 3. Select Down in the State field to take the selected channels out of service. 4. Click Apply. The channels are taken out of service immediately. NOTE: For SS7 trunks, do not set the status to Busy instead of Down to bring channels out of service. If you do this, it will cause the switch to be flooded with UCIC messages.
14-15
Deleting or Re-assigning a T1 or E1 Span
Procedure 106
EXS ExchangePlus Software Operations Guide
Deleting or Re-assigning a T1 or E1 Span This procedure shows how to delete or re-assign a T1 or an E1 span You may want to do this if you decide to remove a particular carrier or change to another carrier.
Assumptions
Steps
Before deleting or re-assigning a span, you must reroute the traffic that is likely to pass over that span. This includes modifying your routing tables to avoid the span that is being deleted. 1. Pull down the Maint menu and select Set Span State. The Set Span Service State window appears (Figure 14-5).
Figure 14-5 Set Span Service State Window
2. Enter the number of the span you want to take out of service in the Span field. 3. Select Down in the State field. 4. Click Apply. The span will be taken out of service so that you can delete or reassign it. 5. Pull down the System menu and select Edit Slot Config. A drop-down menu appears listing the cards in each slot of the switch. 6. Select the slot containing a T1 or an E1 Span you want to delete or reassign. The Line Card Configuration window appears. 7. On the Line Card Configuration window, edit the values to either delete the card or re-assign it. 8. If you choose to re-assign the card, put it back into service, by pulling down the Maint menu and selecting Set Span State. The Set Span State window reappears.
14-16
EXS ExchangePlus Software Operations Guide
Deleting or Re-assigning a T1 or E1 Span
9. Enter the number of the span you want to put back into service in the Span field and select Up in the State field. 10. Click Apply. The span will be brought back into service using the new configuration.
14-17
Bouncing the Channels
Procedure 107
EXS ExchangePlus Software Operations Guide
Bouncing the Channels This procedure describes how to take channels out of service and then bring them back into service. It should be the first procedure you attempt if your trunks are not in service.
Steps
1. Set the channels that are up to down by pulling down the Maint menu and selecting Set Channel State. The Set Channel Service State window appears. 2. In the FROM and TO fields, enter the range of the channels you want to take out of service. For example, you might enter Span 1 Chan 2 in the From fields and Span 2 Chan 8 in the To field. NOTE: Be sure not to include the channel containing the signaling link set itself. 3. Select Down in the State field to take the selected channels out of service. 4. Click Apply. The channels are taken out of service as soon as you click Apply. 5. Put the channels that you have taken out of service back into service. Do this by repeating steps 1-4, except set the STATE field to Up instead of Down. NOTE: Again, be sure not to include the channel containing the signaling link itself. 6. Verify that the channels have been activated, by checking the channel status as described in Procedure 62 Checking Channel Status on page 9-4. All channels should be Idle as shown in Figure 14-6.
Figure 14-6 Trunk Status
14-18
EXS ExchangePlus Software Operations Guide
Procedure 108
Reloading Trunk Instructions
Reloading Trunk Instructions This procedure describes what to do if you have trunks that report DEACTIVATED and you have already attempted to bounce the channels (bring then down and then bring them back up). Only use this procedure as a last resort as it reloads the configuration to the switch. This procedure takes the information in the configuration for a range of trunks and sends it to the switch in sequence. Often, it is all that is needed to bring trunks from a DEACTIVATED state into service.
Steps
1. Pull down the Maint menu and select Reload Trunk Instr. The Reload Trunk Instruction window appears (Figure 14-7).
Figure 14-7 Reload Trunk Instructions Window
2. Enter the range of channels you want to reload by specifying the starting span and channel and the ending span and channel on this window. NOTE: Do not include SS7 signaling links or D channels in the range of channels. 3. Click Apply. The configuration information for the selected trunks is downloaded to the switch.
14-19
Reloading Trunk Instructions
EXS ExchangePlus Software Operations Guide
4. Verify that the trunks have been activated, by checking the channel status as described in Procedure 62 Checking Channel Status on page 9-4. All channels should be Idle as shown in Figure 14-8.
Figure 14-8 Trunk Status
14-20
EXS ExchangePlus Software Operations Guide
Procedure 109
SS7 Channels Are Not Processing Traffic
SS7 Channels Are Not Processing Traffic This procedure describe what to do when some SS7 channels are IDLE, but other report a state other than IDLE and do not appear to be processing traffic. The following is a summary of the procedure: • • •
Steps
Update the CIC Status to set the actual state. This may correct the problem. If that does not clear the problem, bounce the channels (bring the down and then up). If that does not clear the problem, delete the CIC groups, then re-add them and bring the channels back into service.
1. Pull down the Status menu and select Update CIC Status. The Update CIC Status window appears (Figure 14-9)
Figure 14-9 Update CIC Status Window
2. Enter the span containing the first CIC in the Span1 field and enter the span containing the last CIC in the Span2 field. If you’re only interested in one span, enter that span number in both fields. NOTE: If you see an error message, such as the following: Error (status=14) sending command cic query:0
You were unable to obtain CIC status. Report any and all error messages of this type of to Lucent Technologies Technical Support. Review the output of the CIC Status. If all CICs are up and running normally, the status of each CIC should report: Flag=1 and Status=0. The following is an example of the output of an Update CIC Status command: 11/30/99 16:13:21 SPN=1,CHN=29,flag=1,status=0
In this case, no further action is necessary.
14-21
SS7 Channels Are Not Processing Traffic
EXS ExchangePlus Software Operations Guide
However, if the result of the CIC Status Update returns a NAK saying the CIC was not configured (indicates that one or more of the CIC do not have a status of Flag=1 and Status=0), then you need to call Lucent Technologies Technical Support for further instructions before proceeding. 3. If you are instructed by Lucent Technologies Technical Support to bounce the channels (take them out of service, then put them back into service), see Procedure 107 Bouncing the Channels on page 14-18. 4. Update the CIC status again, as described in Step 2. 5. If the CIC Status Update returns a NAK saying the CIC was not configured, then you need to delete the CIC Group, then re-add it. To determine the CIC group, pull down the SS7 menu and select CIC Group Setup. Determine the CIC group to be deleted then re-added by finding the CIC group containing the same Span and Channel that you entered in the CIC Group Status window. 6. Record the contents of the entry containing the CIC group you are going to delete on a piece of paper. 7.
To delete the CIC group, pull down the SS7 menu and select CIC Group Setup.
8. Highlight the line containing the CIC group you want to delete, then pull down the Edit menu and select Delete. 9. To re-add the CIC group, pull down the Edit menu and select Add. A blank line appears at the bottom of the table. 10. Enter the information that you recorded on a piece of paper in Step 6. 11. Pull down the File menu and select Save, then pull down the File menu and select Quit. 12.
Pull down the Maint menu and select Set Channel State.
13. In the From and To fields, enter the range of spans and channels you want to put into service. For example, you might enter Span 1 Chan 2 in the From fields and Span 2 Chan 8 in the To field. NOTE: Be sure not to include the channel containing the signaling link set itself. 14. Select Up in the State field to put the selected channels in service. 15. Click Apply. The channels are put into service as soon as you click Apply. NOTE: On certain ANSI channels, you may need to take the channels out of service (set State to Down), then put them back into service (set State to Up).
14-22
EXS ExchangePlus Software Operations Guide
Procedure 110
Cannot Write CDRs
Cannot Write CDRs This procedure describes what to do if you receive the following error message: Error:4. Unable to write CDR
This message indicates that the queue containing CDR messages is full and no additional CDRs will be written until the queue is emptied. If you receive this message, you may need to increase the size of the queue that temporarily stores CDR records until the are written to the CDR file (CDR.txt or CDR.cbf) by the CDR process. You increase the size of the queue by resetting the value of the MAXCDRMESSAGES flag in the host.cfg file. This flag specifies the maximum number of call detail records that can be saved in the CDR queue before the CDR process retrieves them and writes them to a file.
Steps
1. Open a terminal window and navigate to /user/isos. 2. Go to the bin directory by typing: cd bin
3. Open the host.cfg file using a text editor such as vi. The host.cfg file will be displayed. It will look similar to Figure 14-10.
Figure 14-10 A sample host.cfg file
NOTE: If you are unable to access host.cfg, check the permissions of the file. (See â&#x20AC;&#x153;UNIX Permissionsâ&#x20AC;? on page E-12.) If you do not have write permission, change the permissions by accessing /isos/usr/bin and typing: chmod u+w <host.cfg>
14-23
Cannot Write CDRs
EXS ExchangePlus Software Operations Guide
4. To set the maximum number of CDRs that can be stored in the queue, edit the line in the host.cfg file beginning with: MAXCDRMESSAGES=
Generally, you should set the MAXCDRMESSAGES to about 20 times the number of nodes in your system. For example: If you have four nodes, youâ&#x20AC;&#x2122;d set the MAXCDRMESSAGES to 4 times 20, or 80. NOTE: Do not set the value to more than 120. 5. Save the host.cfg file. 6. Restart the host as described in Procedure 99 Restarting a Host on page 14-6.
14-24
EXS ExchangePlus Software Operations Guide
Procedure 111
Changing Time Zones on ExchangePlus Hosts
Changing Time Zones on ExchangePlus Hosts Occasionally you may need to change the time zones on your ExchangePlus hosts. This procedure describes how to perform that process. NOTE: This procedure is typically performed by Lucent personnel. Consult Lucent Technologies Technical Support before performing this procedure.
Steps
1. Log in as superuser. The default superuser password is excel. 2. Use a text editor to open the /etc/TIMEZONE or etc/init so that you can edit the time zone. NOTE: /etc/TIMEZONE is a symbolic link to etc/init. 3.
Edit the line starting with: TZ=
by entering the appropriate time zone after the equals sign. For example, for Greenwich Mean Time, enter: TZ=GMT
A complete list of all valid time zones can be found in the etc/default/init directory. 4. Save the file. If you are unable to save the file because it is read only, issue the following command: wq!
then re-edit the file by entering the appropriate time zone on the line beginning with TZ=
5. To change the time using the date command, type: date mmddHHMM
where mm=two-digit month (00-12) dd=two-digit day (00-31) HH=two-digit hour based on 24 hour clock (00-23) MM=two-digit minute (00-59)
14-25
Changing Time Zones on ExchangePlus Hosts
EXS ExchangePlus Software Operations Guide
6. To activate these changes during the current boot, open the etc/profile file using a text editor and add: TZ=<time zone>
after the case/esac statement, but before the mask statement. 7. Save this file and log out. The change will take effect upon login.
14-26
EXS ExchangePlus Software Operations Guide
Procedure 112
Calls Stop on a Particular Node
Calls Stop on a Particular Node This problem may be caused by the swtchcom process getting locked up. If this happens swtchcom may stop talking to the switch.
Steps
In order to diagnose this type of problem, do the following: 1. From the command line type: qstat -k > queues.log
2.
If the queue is not operating properly, then get the core for the process that is putting messages in the queue and the process that is removing them by typing: gcore <process id>
The process IDs are listed in qstat. 3. Rename the resulting core. For example, get a core for swtchcom then rename it core.swtchcom. (Get a core for the swtchcom and host for the node in question.) 4. Copy the system.log, user.log and host_msgx.log (where x is the node) to another name. 5. Send all of this information the Lucent Technologies Technical Support along with the exact time of the event.
14-27
Downloading Firmware
Procedure 113
EXS ExchangePlus Software Operations Guide
Downloading Firmware This procedure describes when and how to download firmware to the switch Matrix card(s).
Caution
To avoid disruption to call processing, do not download the firmware on an active Matrix card.
The firmware is the embedded operating system. The firmware needs to be downloaded whenever any of the following events occur: • • •
Steps
During the first system startup A switch software upgrade If there has been a power loss to the switch for more than 12 hours. Battery backup source supplies power to the firmware for 12 hours following loss of power to the Matrix card(s).
1. Pull down the System menu and select Download Firmware. The Download Firmware window appears (Figure 14-11).
Figure 14-11 Download Firmware Window
2. When the system prompts you for which Matrix (CPU) card to download, look at the switch and determine which Matrix (CPU) card has the DIAG light on. Then, download to the other Matrix (CPU). If CPU1 has the DIAG light on, then enter the name such as excel12. If CPU2 has the DIAG light on then enter excel11 and then click on Apply. The first digit specifies the node, and the next digit identifies the Matrix card. For Matrix card 1 in node 3, the Matrix name would be excel31.
14-28
EXS ExchangePlus Software Operations Guide
Downloading Firmware
3. Download the firmware to each Matrix card in each node as appropriate. When the download is finished, the message Download Complete
appears in the Terminal window. 4. Restart the host. Refer to Procedure 99 Restarting a Host on page 14-6.
14-29
Downloading Firmware
14-30
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
A xmenu Functions Overview This appendix provides a reference of all the ExchangePlus functions available from the Windows-based graphical user interface. It provides a comprehensive list of all the functions.
A-1
System Menu
EXS ExchangePlus Software Operations Guide
System Menu System Menu Options
Function
Download Firmware
Downloads the switch firmware to the matrix cards.
Edit Slot Config
Edit the board.cfg file.
Save Slot Config
Saves the board.cfg file.
Load Config File
Loads any file in switch API format into shared memory
Edit Switch Config
Edits the switch.cfg file using the editor, â&#x20AC;&#x153;vi.â&#x20AC;?
Load Switch Config
Loads switch.cfg into active memory.
Start Host Control
Starts the host controller. There are several levels that can be used to start host control. Equivalent to the UNIX command, startup [n] where n is the startup level.
Startup Node
Starts up an individual node in an EXNET ring
Terminate Host Control
Manually stops the host controller. Equivalent to the UNIX command stopit.
Terminate Node
Terminates an node in an EXNET ring.
View User Log File
Shows a history of what has been typed at the system console. The file, user.log, is in the $HOME/log directory.
View System Log File
Shows a detailed history of logged events for the switch. The file, system.log is in the $HOME/log directory
Switch Sides
If the switch has a redundant matrix card, this command causes the switch to use the other matrix card that is not currently active.
Setup
Sets the followings options: - Database read access - Determines where ExchangePlus reads its setup data from. - Target for Database updates - Determines where ExchangePlus writes its setup data. - Remote print level - Sets the verbosity level of the switch communications level. The higher the number, the more information is printed. Local print level - Sets the verbosity of the system administration interface.
A-2
Set Current Node
Sets the current node in the xmenu.
Disable Auto Scroll
Disable auto scrolling of messages in the system log file that appear on the main window when you run xmenu. If auto scrolling is disabled, you have to use the scroll bars to scroll through the messages.
Quit
Quit the xmenu program.
EXS ExchangePlus Software Operations Guide
Status Menu
Status Menu
Status Menu Options
Function
Span(s)
Displays status of a range of spans.
Span Status
Displays the status of channels on a particular span.
Channel(s)
Displays status of a range of channels.
Matrix Card
Displays status of the switch matrix.
DSP Card(s)
Displays status of the digital signaling processing cards
SS7 Card(s)
Displays status of SS7 cards. If there are two, one will be displayed as master, the other as standby.
ISDN Card(s)
Displays status of the ISDN cards.
T1 Card(s)
Displays the status of all T1 cards.
E1 Card(s)
Displays the status of all E1 cards.
Standby IO
Displays the status of the standby I/O card.
VRAS Status
Displays the status of the VRAS SIMMs in the system.
Synchronization
Displays where the current span timing is being derived from.
Link Status
Displays the active link sets and which links within the set are active.
Update CIC Status
Sends CIC query to the switch and updates ExchangePlus channel status accordingly.
SS7 Circuits Query
Sends CIC query SS7 message CQM to the network.
Node(s)
Display the status of node(s) in your system.
Ring(s)
Displays the status of ring(s) in your system
Version
Displays the version of the ExchangePlus software.
A-3
Maint Menu
EXS ExchangePlus Software Operations Guide
Maint Menu Maint Menu Options
Function
Set Span State; Set Channel State;
Takes a span (or range of spans), channel (or range of channels), or DSP SIMM in or out of service.
Set DSP State
A-4
Set Standby Mode
Specifies whether a card should be used as the active or standby card.
Swap Standby Card
Swap a card from active mode back to standby (used after a fix has been made to the previously active card).
Set SS7 Link State Set SS7 Link Set State
Takes the SS7 link or link set in and out of service.
Reset SS7 Link
Reset SS7 card via software.
Set Card State
Takes a card in or out of service.
Reconfigure Card
Executes the slot instructions setup in board.cfg for a specified slot. Used to reset a card without removing it and reinserting it.
Reset Card
Resets the card via software to cause the card to be reconfigured.
Reload Trunk Inst
For trunks which have preloaded signaling instructions, this command reloads the instructions into a specified range of trunks.
Rollover CDRs
Manually rolls over a CDR file.
Configure PCR
Configures PCR mode in SS7.
Start/Stop CCR
Lets the switch start or stop SS7 circuit continuity request.
Send CVT
Lets the switch send an SS7 CVT message for a circuit.
Reset SS7 Redundancy
Resets SS7 redundancy.
Reset ISDN Redundancy
Resets ISDN redundancy.
Reset Exnet Controller
Resets the EXNET Controller in a node.
(Re)Set Ring State
Reset/Set the EXNET Ring state.
Ring Configure
Used to deconfigure/configure a ring.
Clear Alarm Panel
Clears alarm panel
Set Sync Priority
Sets the synchronization priority modes.
Set Loop Timing
Sets the loop timing resources.
Download VRAS
Downloads either a single SIMM, or the entire VRAS Announcement table.
EXS ExchangePlus Software Operations Guide
Database Menu
Database Menu
Database Menu Options
Function
Trunk Group Setup
Used to setup the attributes of a trunk group.
Route List Setup
Used to specify the trunk groups to be used for a particular route.
Services Setup
Assigns the service associated with a route.
Trunk Setup
Specifies the trunks in a particular trunk group.
DNIS Translation
Defines the DNIS translations which are used to determine routing.
Line Assign
Assigns an incoming phone number to a particular route.
Edit Ani
Defines the ANI translations which are used and also determines if the call will be blocked based on the calling number (ANI).
Switch Apps Setup
Defines switch applications that need to be run by the host control program.
Exception
Defines the exceptions that may be used for routing.
VRAS
Defines the VRAS Announcements that may be downloaded to the switch.
Day of Week
Defines the Day of Week routing information that can be used for routing.
Time of Day
Defines Time of Day routing information that can be used for routing.
Custom App
Defines the custom applications and the nodes they are associated with. These applications can be loaded without restarting the host.
Nodes
This is a node table to provision your nodes instead of provisioning them under switch.cfg. Four rings are now supported.
Export Tables
This command is used to create a switch.cfg file which contains a listing of all the tables used to setup the databases. This file can be printed, or read into memory using "readcfg" from the Load Switch Config option from the System menu.
A-5
SS7 Menu
EXS ExchangePlus Software Operations Guide
SS7 Menu
A-6
SS7 Menu Options
Function
SS7 Area
Used to set up the signaling stack protocol.
Link Set Info
Used to set up SS7 link sets.
Link Info
Used to assign links to link sets.
Route Setup
Used to define a set of link sets that will allow the SS7 signaling to reach a given Destination Point Code (DPC).
CIC Group Setup
Assigns CICs to trunk groups.
ISUP/TUP Timers
Used to set up the timer values for ISUP and TUP timers
MTP2 Timers
Used to set up the timer values for MTP2 timers.
MTP3 Timers
Used to se up the timer values for MTP3 timers
Reload ss7 opt parm
Reloads the file ss7optparm.cfg and passes all of the parameters in that file through.
EXS ExchangePlus Software Operations Guide
ISDN Menu
ISDN Menu
ISDN Menu Options
Function
D-Channel
Assigns the D channels and configure the connection type.
D-Channel Backup
Sets up a backup D channel, if required.
D-Channel Attributes
Configures D channel attributes.
D-Channel Facilities
Defines the NFAS facility list.
B-Channels
Defines B channel groups associated with a D Channel.
B-Channel Attributes
Sets up B channel attributes.
A-7
E1R2 Menu
EXS ExchangePlus Software Operations Guide
E1R2 Menu
A-8
E1R2 Menu Options
Function
Stage Parm
Set up stage parameters.
Inseize Instruction
Lists Inseize Instructions for Inseize Control.
Outseize Instruction
Lists Outseize Instructions for Outseize Control.
Inseize Control
Lists Inseize Control for different trunk groups.
Outseize Control
Lists Outseize Control for different trunk groups.
PPL Transmit Sig
Configures PPL Transmit Signal
PPL Timer
Configures PPL Timers
PPL Control
Configures PPL Control
EXS ExchangePlus Software Operations Guide
Overview
B Trunk Types and Flags Overview This appendix provides a listing of the trunk types and flags in the Trunk Group table used by ExchangePlus. It also provides a listing of some of the signaling formats used for the different trunk flags.
Common Questions
Answer the following questions so you can get a better understanding for configuring the trunks, tones and signaling that are required in your network. 1. Do you need Inband (E1, T1) or Out of Band (SS7, ISDN, Common Signaling System)? 2. Do you need DTMF or MF tones? 3. Which signaling do you need such as IXC, FGD, etc.? Inband is a signaling method in which network control and call-setup signals are sent over the same path as the userâ&#x20AC;&#x2122;s transmission. With inband call-setup signals occupying the communications pathway, transmission of the user message must wait until the call-setup process is completed. Out-of-band signaling is a generic term for the transmission of network control signals over a path separate from that employed for transmission of user messages. Out-of-band signaling may be accomplished by reserving a portion of the available bandwidth exclusively for signaling, or through a fully separate signaling network.
Trunk Types
The trunk type setup determines the direction of the trunk and also its hardware attributes. Common North American (T1) trunk types: E&M Wink E&M Immediate SS7, ISDN
IN+OUT+OWS+IWS IN+OUT+OFP+IFP IN+OUT
Common International (E1) trunk types: SS7, ISDN E1R2
IN+OUT IN+OUT+PPL
B-1
Overview
EXS ExchangePlus Software Operations Guide
Select the trunk types for each trunk group you configure from the following tables that are available in ExchangePlus. Trunk Types (Directional)
Description
IN
Inbound trunk
OUT
Outbound trunk
TWO
Inbound and Outbound Trunk. IN+OUT. Used with T1 and E1 service.
Trunk Types (North American Start Type)
B-2
Description
FXO
FXO trunk. Foreign Exchange Office. Used with channel banks and T1 service.
FXS
FXS trunk. Foreign Exchange Service. Used with channel banks and T1 service.
GS
Ground Start. Used with FXO, FXS and T1 service. A type of call signaling, in this scheme, when a call is routed to a subscriber, the phone company will apply a ground signal on the TIP side of the line even before a ring signal is sent. By detecting the signal, phone systems can immediately determine that the line is about to be in use and avoid call crashing.
LS
Loop Start. Used with FXO, FXS and T1 service. A type of calling signal that relies on a telecom device to allow DC current to flow when it goes into an off hook condition. The CO or PBX senses the current and intercepts it as a request for service. Also known as POTS.
DPO
Dial Pulse Originate. Used with T1 service.
DPT
Dial Pulse Terminate. Used with T1 service.
DID
Direct Inward Dial. Used with T1 service.
RBI
RBI Controlled. Used with T1 RBI service.
DFL
Default. Used with T1 and E1 service.
IWS
Inbound Wink Start. Used with E&M T1 service.
IDD
Inbound Direct Dial. Used with T1 service.
EXS ExchangePlus Software Operations Guide
Trunk Flags
Overview
Trunk Types (North American Start Type)
Description
IFP
Inbound Fixed Pause. Used with T1 service.
IDT
Inbound Dial Tone. Used with T1 service.
OWS
Outbound Wink Start. Used with E&M T1 service.
ODD
Outbound Direct Dial. Used with T1 service.
OFP
Outbound Fixed Pause. Used with T1 service.
ODT
Outbound Dial Tone. Used with T1 service.
Trunk Types (International)
Description
PPL
PPL Controlled. Used with E1 service.
Trunk Types (Release Mode)
Description
LRL
Set Local-end Release mode to release, default park. Used with T1 and E1 service.
DRL
Set Distant-end Release mode to release, default park. Used with T1 and E1 service.
The trunk flag setup table describes the type of signaling and any application defined flags that are available in ExchangePlus. Primary trunk flags are flags that can be used by themselves. Modifier trunk flags are flags that have to be used with a primary trunk flag. There are some universal modifiers that can go with most flags such as CPA, ANSCPA, INTL, IANS, APP1-8, and USR1-8. NOTE: See the â&#x20AC;&#x153;Signaling Format Examplesâ&#x20AC;? on page B-11 for more information.
B-3
Overview
Trunk Flags
Sample Modifier Trunk Flags
InBand or Out of Band Signaling
Signaling
Description
IXC (Primary)
CELLT, CELLE
Inband
MF
IntereXchange Carrier. Feature Group D interexchange carrier signaling. An IXC is a telephone company that provides long distance telephone service.
IXC+CELLT (Primary+Modifier)
CELLE
Inband
MF
Cellular Tandem protocol.
IXC+CELLE (Primary+Modifier)
CELLT
Inband
MF
Cellular Ericsson protocol. Similar to 0288 and 0222. It works the same way Inbound and Outbound.
FGD (Primary)
PAGING
Inband
MF
Feature Group D. Same as IXC inbound, but KP+CLD+ST outbound. Also referred to as "Equal Access". Feature Group D is trunk-side LATA access.
FGD+PAGING (Primary+Modifier)
Inband
MF
Use KP+CLD+ST on inbound and outbound.
MFLUCENT (Primary)
Inband
MF
This is a cellular protocol. Itâ&#x20AC;&#x2122;s singlestring MF signaling, like a Feature Group D with a CIC thrown in. There is no acknowledgement and no wink is accepted after the string. ExchangePlus accepts MFLUCENT inbound and outbound.
SFD3 (Primary)
Inband
MF
Sprint Feature Group D3. Cellular. It works like a modified Feature Group D. KP+CLD+ST+KPII+ANI+ST
EAEO (Primary)
Inband
MF
Equal Access End Office. Feature Group D Equal Access signaling.
Inband
MF
Feature Group C signaling which is primarily used with coin phones. A trunk-side switched access connection directly linking local phone company end offices with the long distance network of AT&T.
FGC+ANSW (Primary+Modifier)
Inband
MF
FGB (Primary)
Inband
MF
FGC (Primary)
B-4
EXS ExchangePlus Software Operations Guide
ANSW
Feature Group B signaling. A trunk-side switched access connection for originating and terminating traffic.
EXS ExchangePlus Software Operations Guide
Overview
Sample Modifier Trunk Flags
InBand or Out of Band Signaling
Signaling
Description
PVT (Primary)
DTMF, RGBK, ONE, TWO, FOUR, EIGHT
Inband
DTMF
Private line. Used mainly when connecting to channel banks and works like an extension phone. PVT by itself is also useful for "hotline" where no digits are collected.
PVT+DTMF (Primary+Modifier)
RGBK, ONE, TWO, FOUR, EIGHT
Inband
DTMF
Expects a pound termination or a 3 second time out between digits.
PVT+RGBK+DTMF (Primary+Modifiers)
ONE, TWO, FOUR, EIGHT
Inband
DTMF
Expects a pound termination and local ringback.
PVT+ONE+TWO (Primary+Modifiers)
DTMF, RGBK, FOUR, EIGHT
Inband
DTMF
Expects only 3 digits.
FGA (Primary)
DTMF, ANI, ONE, TWO, FOUR, EIGHT
Inband
DTMF
Feature Group A signaling. FGA by itself is also useful for "hotline" where no digits are collected. Called number supplied via DTMF signaling with a 5 second time out after the last digit. Lineside originating and terminating LATA access for which an originating subscriber dials an assigned telephone number that connects to a specific carrier network. The carrier network returns a tone to signal the caller to input additional tone-generated digits of the called number. FGA has a one second interdigit time out.
FGA+DTMF (Primary+Modifier)
ANI, ONE, TWO, FOUR, EIGHT
Inband
DTMF
FGA+ANI (Primary+Modifier)
DTMF, ONE, TWO, FOUR, EIGHT
Inband
DTMF
FGA+ONE+TWO (Primary+Modifiers)
DTMF, ANI, FOUR, EIGHT
Inband
DTMF
DID (Primary)
FOUR, SEVEN
Inband
DTMF
DID+FOUR (Primary+Modifier)
SEVEN
Inband
DTMF
DID+SEVEN (Primary+Modifier)
FOUR
Inband
DTMF
Trunk Flags
Direct Inward Dialing. DTMF called number.
B-5
Overview
Trunk Flags
EXS ExchangePlus Software Operations Guide
Sample Modifier Trunk Flags
Signaling
Description
Out of Band
Common Channel
Integrated Services Digital Network. ISDN signaling (D and B channel attributes are set up in the ISDN configuration section of this document).
Out of Band
Common Channel
ANSI SS7 CIC. American National Standards Institute Signaling System 7 Carrier Identification Code.
Out of Band
Common Channel
Out of Band
Common Channel
ITUSS7+ANI (Primary+Modifier)
Out of Band
Common Channel
ITUSS7+SWNK (Primary+Modifier)
Out of Band
Common Channel
If the incoming side is SS7 and that incoming trunk group flag is set to SWNK the ACM (Address Completed Message) that is sent back to the carrier will have BCI (Backward Call Indicator) hardcoded to be ‘0x6’ and ‘0x4’. BCI is a parameter in the ISUP message. ’0x6’ - Charge, Subscriber Free ’0x4’ - ISUP all the way
Out of Band
E1R2
E1 PPL controlled trunk.
Out of Band
E1R2
ISDN (Primary)
ANSISS7 (Primary)
ANI
ANSISS7+ANI (Primary+Modifier) ITUSS7 (Primary)
E1R2 (Primary) E1R2+ANI (Primary+Modifier)
B-6
InBand or Out of Band Signaling
ANI, SWNK
ANI
ITU SS7 CIC. International Telecommunications Union Signaling System 7 Carrier Identification Code.
J1 (Primary)
Japanese J1 interface.
VRU (Primary)
Voice Response Unit. Used for application support of VRUs. For more information, contact Lucent Technologies Technical Support.
CTUP (Primary)
Out of Band
Common Channel
China TUP trunk group.
IUP (Primary)
Out of Band
Common Channel
BT IUP trunk group.
PTUP (Primary)
Out of Band
Common Channel
Philippines TUP trunk group.
EXS ExchangePlus Software Operations Guide
InBand or Out of Band Signaling
Signaling
Description
CELLE (Modifier)
Inband
MF
Cellular Ericsson. Similar to 0288 and 0222. It works the same way Inbound and Outbound.
CELLT (Modifier)
Inband
MF
Cell Tandem. Similar to MFLUCENT.
PAGING (Modifier)
Inband
MF
Paging (Outbound only).
SWNK (Modifier)
Out of Band
Common Channel
If the incoming side is SS7 and that incoming trunk group flag is set to SWNK the ACM (Address Completed Message) that is sent back to the carrier will have BCI (Backward Call Indicator) hardcoded to be ‘0x6’ and ‘0x4’. BCI is a parameter in the ISUP message. ‘0x6’ - Charge, Subscriber Free ‘0x4’ - ISUP all the way
ANSW (Modifier)
Inband
MF
Answer Wink. Feature Group C signaling with an offhook received after the second stage has been delivered.
RGBK (Modifier)
Inband
DTMF
Ring Back. If you want to use the switch as a terminating switch. i.e., if you want to generate ring back tone back to the originator, add this flag to the outbound trunk group.
INCMPL (Modifier)
Out of Band
Common Channel
To set the calling party number’s ‘incomplete indicator’ to ‘incomplete’ in the outgoing SS7 IAM message.
Trunk Flags
Sample Modifier Trunk Flags
Overview
B-7
Overview
Trunk Flags
B-8
EXS ExchangePlus Software Operations Guide
Sample Modifier Trunk Flags
InBand or Out of Band Signaling
Signaling
Description
ANI (Modifier)
Inband and Out of Band
DTMF, Common Channel, E1R2
Automatic Number Identification. It isn’t usually used by itself. ANI does various things: For FGB, it requests ANI by going offhook. Otherwise it requests ANI by Wink. For SS7: For FGC, it works the same way as FGB -- you can either send the ANI or not. You can say FGB+ANI or if you’re using a *ANI Protocol, you can say FGA+ANI, which is either: *+calling number+ST+*+called number+ST Or the other way around, depending on how you have set it. If it’s *ANI Protocol which is supported on anything that’s partial to FGA, the Called Number comes before the Calling Number. So using FGA+ANI, the protocol is as follows: *+called number+*+calling number+* Using FGA, the protocol is as follows: *+calling number+*+called number+* If you put an ANI modifier in there (FGA+ANI) you can also put "+DTMF" in there if you want.
DTMF (Modifier)
Inband
DTMF
Dual Tone Multi-Frequency or Touch Tone. Number delimited DTMF called number inbound, DTMF outbound. DTMF is audible tones which conform to North American Telephone Standards. These are generated by push-button telephones to dial telephone numbers, as well as to provide control or data input to voice processing systems.
ONE (Modifier)
Inband
DTMF
Modifier trunk flag to indicate one digit expected. Use with FGA, DTMF, and DID.
TWO (Modifier)
Inband
DTMF
Modifier trunk flag to indicate two digits are expected. Use with FGA, DTMF, and DID.
ONE+TWO (Modifier)
Inband
DTMF
Modifier trunk flag to indicate three digits are expected. Use with FGA, DTMF, and DID.
EXS ExchangePlus Software Operations Guide
InBand or Out of Band Signaling
Signaling
Description
FOUR (Modifier)
Inband
DTMF
Modifier trunk flag to indicate four digits are expected. Use with FGA, DTMF, and DID.
EIGHT (Modifier)
Inband
DTMF
Modifier trunk flag to indicate eight digits are expected. Use with FGA, DTMF, and DID.
Trunk Flags
Sample Modifier Trunk Flags
Overview
PFX (Modifier)
Prefix. Works with SS7, SFD3, Feature Group D, MFLUCENT, and Cell Tandem trunks. It does not work with ISDN trunks. When PFX is turned on, it appends the following digits to the beginning of the dialed number, depending on the settings for the Incoming Call Type or Call Tags: 011 for international 1 for 1+ 01 for 0+ Before flexible translation was available, PFX was a way to force these digits.
ASCRN (Modifier)
ANI Screening. Can be added with any incoming call flags. Examples of use: • Blocked/Temporary Blocked • Restricted/Not Restricted (NonBlocked) • Translations ANI to a different ANI • Change the Nature of Address (NOA) • Change the partition to a different partition
FCLI (Modifier)
Forced Call Line ID. (Applies only to Outbound Trunk Groups.) It replaces the calling number with the ANI defined in the trunk group in the outbound call. It is a forced ANI. Can be added with any other outbound flags.
POUND (Modifier)
Pound or #. Force the # at the end of the digits on the outbound call. (Applies only to Outbound Trunk Groups.)
NOPND (Modifier)
No Pound or strip off pound. The outbound call number will not have a #. (Applies only to Outbound Trunk Groups.)
RORIG (Modifier)
Re-Originate.
B-9
Overview
Trunk Flags
B-10
EXS ExchangePlus Software Operations Guide
Sample Modifier Trunk Flags
InBand or Out of Band Signaling
Signaling
Description
CPA (Modifier)
Call Progress Analysis.
ANSCPA (Modifier)
Answer with Call Progress Analysis.
INTL (Modifier)
International. Rarely used. Sets the inbound partyâ&#x20AC;&#x2122;s international flag, if it is not already set.
IANS (Modifier)
Immediate Answer.
USR1-USR8 (Modifier)
User defined flags 1-8. Primarily designed for new signaling types.
APP1-APP8 (Modifier)
User defined flags 1-8. These specify if an application is attached or turned on to a specific trunk or trunk group.
EXS ExchangePlus Software Operations Guide
Signaling Format Examples Trunk Flags (Primary+Modifier)
Overview
The following table shows the signaling formats for the trunk flags that are available. in ExchangePlus. Modifier flags are denoted after the "+" in the Trunk Flags column.
Inbound
Outbound
Notes
FGA
Report seizure immediately application must collect digits
Called - defined by application
DTMF protocol. FGA has a one second interdigit time out.
FGA+EIGHT+TWO
10 DTMF digits
10 DTMF digits for called number
DTMF formats accepted: 1. NPA+NXX+XXXX 2. 1+NPA+NXX+XXXX 3. 0 4. 0+NPA+NXX+XXXX 5. 011+CC+NN 6. 01+CC+NN 7. NXX+XXXX CC - country code
FGA+FOUR+TWO+ONE
7 DTMF digits
Filed NPA+7 digits
See above.
DTMF for called number FGA+DTMF
DTMF digits -- collect all digits until # or until the string time outs.
If collected digits > 10 - All digits.
See above.
Else fill in missing digits with filed digits until 10 digits are available. FGB
KP+ACCESS+ST + Play Dialtone + DTMF Digits
KP+ST + Wait for Dialtone + DTMF Digits
See above. MF and DTMF protocols.
FGB+ANI
KP+ACCESS+ST + Wait for Offhook + KP+CLG+ST + Play dialtone + DTMF Digits
KP+ST + Wait for Offhook + KP+CLG+ST + Wait for dialtone + DTMF Digits
See above.
KP+CLD+ST + Wait for Wink + KP+I+CLG+ST
KP+CLD+ST + Wait for wink + KP+I+CLG+ST
CLD formats supported:
KP+CLD+ST + Wait for offhook + KP+I+CLG+ST
KP+CLD+ST + Wait for offhook + KP+I+CLG+ST
CLD formats supported:
FGC
FGC+ANSW
CLG - calling number. Assumed to be 10 digits outbound. Missing digits are filled in with the filed ANI. ACCESS number is not used.
1. 1+CC+NN 2. NPA+NXX+XXXX 3. NXX+XXXX
1. 1+CC+NN 2. NPA+NXX+XXXX 3. NXX+XXXX I - 1 information digit
B-11
Overview
Trunk Flags (Primary+Modifier) IXC
EXS ExchangePlus Software Operations Guide
Inbound
Outbound
Notes
KP+II+CLG+ST + KP+CLD+ST
Domestic: KP+II+CLG+ST + KP+CLD+ST
II - 2 information digits CLD formats supported: 1. 0 2. NN
International: KP+138+CARR+CCC+ST + KP+II+CLG+ST + KP+CLD+ST IXC+CELLT
KP+II+CLG+CIC+CLD+ST
KP+II+CLG+ST + KP+CLD+ST
3. NPA+NXX+XXXX 4. 0+NPA+NXX+XXXX 5. CCC+NNNN CARR - 3 digit carrier code CCC - country code II - 2 information digits CIC - 3 digit Carrier Identification
Code AT&T Cell Tandem
IXC+CELLE
KP+II+CLG+ST + KP+101+CIC+1+CLD+ST
KP+II+CLG+ST + KP+101+CIC+1+CLD+ST
Erickson Cellular II - 2 information digits CIC - 4 digit Carrier Identification
Code. FGD
KP+II+CLG+ST
KP+CLD+ST
II - 2 information digits
+ KP+CLD+ST FGD+PAGING
KP+CLD+ST
KP+CLD+ST
EAEO
KP+OZZ+CCC+STP + Wait for wink + KP+II+CLG+ST + KP+CLD+ST
KP+OZZ+CCC+STP + Wait for wink + KP+II+CLG+ST + KP+CLD+ST
CLD formats: See above.
Same as FGA inbound
Seizure outbound - no digits outpulsed
Used primarily for connecting channel banks to FXS trunks with phones.
PVT
B-12
II - 2 information digits OZZ - routing code
EXS ExchangePlus Software Operations Guide
Overview
Trunk Flags (Primary+Modifier)
Inbound
Outbound
Notes
E1R2
CCITT Generic
CCITT Generic
Called number with no calling number.
E1R2+ANI
CCITT Generic
CCITT Generic
E1R2 with the calling number
PAGING
KP+CLD+ST
ISDN
SETUP
SETUP
Formats are based on Q.931. Basic 1+ and international calls are supported as above.
MFLUCENT
KP+II + 10 digits of calling number + 4 digit CIC + 10 digits of called number+ST
II - 2 information digits
Sprint Feature Group D3
II - 2 information digits
SFD3
KP+CLD+ST + KPII+CLG+ST
CIC - Carrier Identification Code
KP+CLD+ST + KPII+CLG+ST
B-13
Overview
B-14
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
C Call Detail Record Formats Overview This appendix provides for record structures used to create the call detail record for ExchangePlus Release 3.x and Release 2.x. The Release 3.x format is different than the Release 2.x format used by in earlier version of ExchangePlus. You have the option of using either CDR format. The major differences between them are that the number of digits in the phone number fields have been increased from 16 to 23. The fields affected by this include cldNumber and clgNumber. There are also three new fields in Release 3.x: routeChoice, releaseCause, and dialedNumber. Lastly the Release 3.x CDR file can be saved in either ASCII or DBF (Database) format while the Release 2.x format can only be saved in ASCII.
CDR Release 3.x Format CDR Release 3.x Format Field
Field Description
Type and Length
Record Source
Always set to 1
CHAR 1
Company Number
Company Number
CHAR 5
Account Number
Account Number
CHAR 14
Sequence Number
The sequence number 1â&#x20AC;&#x201C;n
CHAR 19
Calling number
The calling number
CHAR 23
Calling number flags
Flags set to 10 for national calls and 20 for international calls.
CHAR 2
Called number
The called number
CHAR 23
Called number flags
Flags set to 10 for national calls and 20 for international calls.
CHAR 2
Bill number
Location for calling card/credit card/third number billing
CHAR 24
Access Number
Access number
CHAR 16
Project Code
Application defined. Set to 0 by default
CHAR 4
Expire Date
Expiration date of calling card/credit cards in MMYY format. Set to blanks by default.
CHAR 4
C-1
Overview
EXS ExchangePlus Software Operations Guide
CDR Release 3.x Format
C-2
Field
Field Description
Type and Length
Room Number
Room number if billing to a hotel. Set to blanks by default.
CHAR 4
Outgoing Call Type
Always set to 1 by default
CHAR 1
Call class
Call class â&#x20AC;&#x201C; set to 1 by default
CHAR 1
Date time Changes
Set to 00 by default. Number of date time changes
CHAR 2
Connect Date
Date of seizure by the calling party in YYMMDD
CHAR 8
Connect Time
Time of seizure by the calling party in HHMMSS
CHAR 6
Disconnect Time
Time of first release by either the called or the calling party in HHMMSS format
CHAR 6
System Time
Total time in seconds the call spent under ISOS control. Disconnect/Connect time in HHMMSS format
CHAR 6
Operator Time
Reserved. Set to 000000
CHAR 6
Charged Time
Time from the initial answer by the called party until the Disconnect Time in HHMMSS
CHAR 6
Initial period
Minutes for initial rating period
CHAR 2
Initial Period Rate
Rate for initial period $$.cc
CHAR 5
Additional Period
Minutes for additional rating period
CHAR 2
Additional Period Rate
Rate for additional period $$.cc
CHAR 5
Service Charge
Service charge $$cc
CHAR 4
Tax Percent
Percentage tax to charge
CHAR 4
Discount Before Rate Change Hour
Reserved
CHAR 2
Rate Change Hour
Reserved
CHAR 2
Discount After Rate Change Hour
Reserved
CHAR 2
Discount Applied to Initial Period
Reserved
CHAR 1
Call Amount
Used if the call amount is quoted $$$$cc
CHAR 6
Validation Codes
Reserved
CHAR 15
Reserved
Reserved
CHAR 3
EXS ExchangePlus Software Operations Guide
Overview
CDR Release 3.x Format Field
Field Description
Type and Length
Call Credits
Reserved
CHAR 1
Trouble Code
Defaults to all blank
CHAR 2
Call Digit
The info digits
CHAR 3
Completion Code
Currently set to 1
CHAR 1
Incoming Type
OPLUS – called began with a 0 – 2 OMINUS – called was just a 0 – 3 ONEPLUS – call began with a 1 – 4 DIRECTORY – 411 was dialed – 5 REPAIR – 611 was dialed – 6 EMERGENCY – 911 was dialed – 7
CHAR 1
Time and Charges Flag
Reserved
CHAR 1
Operator Id 1
Reserved
CHAR 3
Operator Id 2
Reserved
CHAR 3
Operator Id 3
Reserved
CHAR 3
Operator Position 1
Reserved
CHAR 3
Operator Position 2
Reserved
CHAR 3
Operator Position 3
Reserved
CHAR 3
Calling Trunk Group
The trunk group the calling party seized on
CHAR 5
Called Trunk Group
The trunk group the outbound party used
CHAR 5
Calling Trunk Number
The trunk number used by the calling party
CHAR 5
Called Trunk Number
The trunk number used by the called party
CHAR 5
Ozz Code
The numeric routing code used when interfacing to another tandem switch
CHAR 2
Carrier Code
The numeric carrier code of the incoming trunk group
CHAR 4
Flags
Reserved – Special Flags
CHAR 7
Name
Reserved – Name Field
CHAR 20
Calling CLLI code
Reserved (mobile clli code – calling)
CHAR 4
Calling Station
Reserved (mobile station number – calling)
CHAR 2
Called CLLI code
Reserved (mobile clli code – called)
CHAR 4
Called Station
Reserved (mobile station number – called)
CHAR 2
Validation Flags
Reserved – 6 flags for MAP
CHAR 6
C-3
Overview
EXS ExchangePlus Software Operations Guide
CDR Release 3.x Format Field
Field Description
Type and Length
Response Code
Response code from external validation
CHAR 3
mapID
Which MAP processed this message
CHAR 1
Country
Name of the destination country â&#x20AC;&#x201C; application provided
CHAR 20
Original Dialed Number
The original incoming called party ID (the dialed number).
CHAR 23
Release Cause
For calls being routed to outgoing SS7 trunks (ANSI or ITU), the SS7 release cause code which is transported in the call clearing message (i.e., REL or DISCONNECT messages).
CHAR 4
Route Choice Offset
In a route list, a number of secondary trunk groups can be defined. If all the trunk members in the primary trunk group, TG1, are unavailable, then an alternative trunk group is attempted (if defined), or else the call is routed to the default route. This is the route choice offset indicating when routing has selected a secondary trunk group or overflowed to the default route.
CHAR 4
Field
Field Description
Type and Length
Record Source
Always set to 1
CHAR 1
Company Number
Company Number
CHAR 5
Account Number
Account Number
CHAR 14
Sequence Number
The sequence number 1â&#x20AC;&#x201C;n
NUM 4
Calling number
The calling number
CHAR 16
Calling number flags
Flags always set to 10
CHAR 2
Called number
The called number
CHAR 16
Called number flags
Flags always set to 10
CHAR 2
CDR Release 2.x Format CDR Release 2.x Format
C-4
EXS ExchangePlus Software Operations Guide
Overview
CDR Release 2.x Format Field
Field Description
Type and Length
Bill number
Location for calling card/credit card/third number billing
CHAR 24
Access Number
Access number
CHAR 16
Project Code
Application defined. Set to 0 by default
CHAR 4
Expire Date
Expiration date of calling card/credit cards in MMYY format. Set to blanks by default.
CHAR 4
Room Number
Room number if billing to a hotel. Set to blanks by default.
CHAR 4
Outgoing Call Type
Always set to 1 by default
CHAR 1
Call class
Call class â&#x20AC;&#x201C; set to 1 by default
CHAR 1
Date time Changes
Set to 00 by default
CHAR 2
Connect Date
Date of seizure YYMMDD
CHAR 6
Connect Time
Time of seizure in HHMMSS
CHAR 6
Disconnect Time
Time of disconnect in HHMMSS format
CHAR 6
System Time
Total time in seconds the call spent under ISOS control. Disconnect/Connect time in HHMMSS format
CHAR 6
Operator Time
Reserved. Set to 000000.
CHAR 6
Charged Time
Time from the initial answer by the called CHAR 6 party until the disconnect time in HHMMSS
Initial period
Minutes for initial rating period
CHAR 2
Initial Period Rate
Rate for initial period $$.cc
CHAR 5
Additional Period
Minutes for initial rating period
CHAR 2
Additional Period Rate
Rate for additional period $$.cc
CHAR 5
Service Charge
Service charge $$cc
CHAR 4
Tax Percent
Percentage tax to charge
CHAR 4
Discount Before Rate Change Hour
Reserved
CHAR 2
Rate Change Hour
Reserved
CHAR 2
Discount After Rate Change Hour
Reserved
CHAR 2
Discount Applied to Initial Period
Reserved
CHAR 1
Call Amount
Used if the call amount is quoted $$$$cc
CHAR 6
C-5
Overview
EXS ExchangePlus Software Operations Guide
CDR Release 2.x Format
C-6
Field
Field Description
Type and Length
Validation Codes
Reserved
CHAR 15
Reserved
Reserved
CHAR 3
Call Credits
Reserved
CHAR 1
Trouble Code
Defaults to all blank
CHAR 2
Call Digit
The info digits
CHAR 2
Completion Code
Currently set to 1
CHAR 1
Incoming Type
OPLUS – called began with a 0 – 2 OMINUS – called was just a 0 – 3 ONEPLUS – call began with a 1 – 4 DIRECTORY – 411 was dialed – 5 REPAIR – 611 was dialed – 6 EMERGENCY – 911 was dialed – 7
CHAR 1
Time and Charges Flag
Reserved
CHAR 1
Operator Id 1
Reserved
NUM 2
Operator Id 2
Reserved
NUM 2
Operator Id 3
Reserved
NUM 2
Operator Position 1
Reserved
NUM 2
Operator Position 2
Reserved
NUM 2
Operator Position 3
Reserved
NUM 2
Calling Trunk Group
The trunk group the calling party seized on
CHAR 4
Called Trunk Group
The trunk group the outbound party used
CHAR 4
Calling Trunk Number
The trunk number used by the calling party
CHAR 4
Called Trunk Number
The trunk number used by the called party
CHAR 4
OZZ Code
The numeric routing code used when interfacing to another tandem switch
CHAR 2
Carrier Code
The numeric carrier code of the incoming trunk group
CHAR 4
Flags
Reserved
CHAR 7
Name
Reserved
CHAR 20
Calling CLLI code
Reserved (mobile)
CHAR 4
Calling Station
Reserved (mobile)
CHAR 2
EXS ExchangePlus Software Operations Guide
Overview
CDR Release 2.x Format Field
Field Description
Type and Length
Called CLLI code
Reserved (mobile)
CHAR 4
Called Station
Reserved (mobile)
CHAR 2
Validation Flags
Reserved
CHAR 6
Response Code
Response code from external validation
NUM 2
Application Processor ID
Reserved
CHAR 1
Country
Name of the destination country â&#x20AC;&#x201C; application provided
CHAR 20
C-7
Overview
C-8
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
D Table Sizes Overview This appendix provides a listing of the maximum table sizes for the various tables in ExchangePlus
Table Sizes Name of Table
Size (Number of entries)
General Tables Maximum Number of Nodes
10
Trunk Group Table
3000
Trunk Table
2560 per node. For a ten node system 25600 (10*2560)
Route List Table
20000
Trunk Groups in Each Route Entry maximum number of trunk groups in a route list)
20
DNIS Translation Table
32000 (up to 9999 partitions)
Exception Table (each Trunk Group partition has itâ&#x20AC;&#x2122;s own Exception table)
4096 (32 trunk group partitions * 128 exceptions per partition)
Announcement Tables (VRAS)
10240 (1024 per node * 10 nodes)
ANI Entries (ANI Table)
200,000 (up to 9999 partitions)
Day of Week Route Entries (Day of Week Table)
1000
Time of Day Route Entries (Time of Day Table)
1000
D-1
Overview
EXS ExchangePlus Software Operations Guide
Table Sizes Name of Table
Size (Number of entries)
SS7 Tables SS7 Work Area (stack)
4 per node. Stack ID is unique.
LinkSet
32 per node, but any linkset ID in any node can not exceed 32. The Linkset ID is unique per node.
Link
32 per node. Any link ID between 1 and 16 will be assigned to the primary Card. 17-32 will be assigned to the secondary card. Any link ID of any node cannot exceed 32. The Link ID is unique per node.
DPC Route
64 per node. Any DPC Route ID in any node cannot exceed 64. The DPC Route ID is unique per node.
CIC Groups
768 per stack. The CIC group ID is unique per stack, not per node.
ISDN Tables ISDN D Channel
80 per node. 32 D channels per ISDN PRI card.
ISDN D Backup
80 per node
ISDN D Attributes
80 per node
ISDN Outbound B Group
64 per node
ISDN Outbound B Attributes
64 per node
E1R2 Tables
D-2
E1R2 Stage Parameter Table
64
Inseize Instruction Table
32
Outseize Instruction Table
32
Inseize Instruction Control
32
Outseize Instruction Control
32
PPL TX Sig Table
24
PPL Timer Table
24, each entry can define up to 32 timers
PPL Control Table
34
EXS ExchangePlus Software Operations Guide
Overview
E UNIX Reference Overview Appendix E provides a basic UNIX reference guide. It will give you a basic overview of UNIX commands that you may need to use in order to operate ExchangePlus.
General UNIX Information The UNIX operating system is a set of programs that controls the computer, acts as a link between the user and the computer and provides various utilities to with which to work.
Description
UNIX is organized into four major components:
Kernel
File System
The kernel is a program that constitutes the nucleus of the operating system; it coordinates the functioning of the computer’s internals (such as allocating system resources). It is the layer of software that directly works with the hardware and underlies all of the application software.
The file system provides a method of handling data that makes it easy to store and access information. There are three main types of files: • • •
Ordinary files Directories Special files
Ordinary files are a collection of characters that are treated as a unit by the system. Ordinary files are used to store any information you want to save. They may contain text, or commands or instructions for the computer.
E-1
General UNIX Information
EXS ExchangePlus Software Operations Guide
A directory is a “super-file” that contains a group of related files. For example, a directory named log, may contain a group of files which log special information about other running programs. If a file is thought of as a sheet of paper, then a directory can be thought of as a file folder containing related papers or files. Special files constitute the most unusual feature of the file system. A special file represents a physical device such as a terminal, disk drive, tape drive or serial port device. The system reads and writes to special files in the same way it does to ordinary files. However the system's read and write requests do not use the normal file access mechanism; instead, they use the device handler associated with the file. There are several important directories used by UNIX and these are listed below: /bin - contains many executable programs and utilities /dev - contains special files that represent the peripheral devices like the disk, the terminal, the serial board etc. /etc - contains programs and data files for system administration. /lib - contains libraries for programs and languages /tmp - contains temporary files that can be created by any user.
Shell
Commands
The shell is a program that serves as the command interpreter. It acts as a liaison between the user and the kernel, interpreting and executing commands. The shell is interactive. ExchangePlus provides a program that “runs” on top of the shell that provides a simpler interface for most commands available on the host controller.
Commands are the names of programs that are executed by the computer upon the request of a user. Packages of programs are called tools. The operating system provides tools for jobs such as creating and changing text, writing programs, developing software and exchanging information. Command syntax is as follows: command options(s) argument(s)<CR> where a command is the name of the program you want to run, an option modifies how the command is run and argument specifies data on which the command is to operate (like the name of a directory or file).
E-2
EXS ExchangePlus Software Operations Guide
UNIX Operation
General UNIX Information
The following is a list of general UNIX procedures: •
Log in before you use UNIX. Remember your user name and password.
•
When you see a prompt such as $ or %, you can type a UNIX command.
•
When you see a prompt such as #, you are in superuser mode.
•
To back up and correct typos, try pressing the Backspace, Delete, # (Shift 3), or Ctrl-H.
•
To cancel what you have typed and try again, try pressing Ctrl-U or @ (Shift 2).
•
Type a space between the command name and any other information on the same line.
•
When you have typed the command, press the Enter or Return key.
•
When you log in, the working directory is your home directory.
•
To log out, type exit or press Ctrl-D.
•
A pathname is the path in which you can find a file or directory.
•
The root (main) directory of the disk is called / (slash).
•
If a pathname starts with a slash (/), it begins at the root directory.
•
If a pathname doesn't start with a slash, it begins at the working directory.
•
A pathname consists of directory names separated by slashes (/).
•
Capital (UPPERCASE) and small letters (lowercase) are different in filenames.
•
Filenames can contain letters, numbers, dots (periods), and underscores (_). Stay away from other punctuation. Slashes are special.
•
Filenames should not contain spaces.
•
The question mark (?) wild card stands for a single character in a filename.
•
The asterisk (*) wild card stands for any number (0 or greater) of characters in a filename.
•
An * by itself stands for all files in the working directory.
•
Files beginning with a dot (period) are special/hidden.
E-3
UNIX Commands
EXS ExchangePlus Software Operations Guide
UNIX Commands Utilities
Some specific commands for UNIX utilities are described in detail in the table below. cat This command is used to list the contents of a file or to concatenate one file to another. For example: To list a fileâ&#x20AC;&#x2122;s contents type: cat <filename>
To concatenate a file with another type: cat <filename1> <filename2> > <filename3>
chmod This command is used to change the permissions on a file. The permissions are: -r = read -w = write -x = execute If you execute the ls command with the -l option, you can examine the permissions on a file. To change them, use the chmod command. For example: chmod +x <filename>
will add execute permissions to a file. compress This command is useful for compressing a file before sending it or uploading it. cpio This command is another utility used to write files to tape. df This command is used to list the various partitions of the disk and any mounted drives. It is useful to see how much space is left df â&#x20AC;&#x201C;k This command shows space utilization in kilobytes. Otherwise, it is shown in blocks of 512 bytes.
E-4
EXS ExchangePlus Software Operations Guide
UNIX Commands
dos2unix Convert a text file from MSDOS format to Unix format – removes the ^M from the end of the file. du <pathname> This command shows “disk utilization”. It is useful to see how much space is used and where it is used. find Find a file on the disk. For example: find <starting directory> -name ‘<filename>’ -print
fsck Check out and fix minor disk problems, such as chkdsk for DOS. If the system cannot mount a disk, then you can do an fsck on it to fix it. For example: fsck /dev/usr
This command will check out the usr slice of the disk. ftp Useful for sending and receiving files remotely. Make sure and use the ‘b’ setting. ifconfig –a This command will list the current settings for any NIC cards in the system. init -q Rereads the inittab file and sets ports accordingly. init 6 Reboots the system. init 0 Shuts the system down. ipcrm Removes shared memory or queue resources. Common examples: ipcrm -m <memory id> ipcrm -M <memory key> ipcrm -q <queue id> ipcrm -Q <queue key>
E-5
UNIX Commands
EXS ExchangePlus Software Operations Guide
ipcs Obtains memory ids, keys and queue keys. Lists interprocess communication resource usage. For example: ipcs -q = lists the queue usage ipcs -m = lists the shared memory usage. qstat This command is actually provided by ICC and should be included with the Exchange Plus load. This will give a more readable status of queue usage. Options include: -k = show queue usage by key -a = show queues that have message in them -n = show the names of the processes using the queue kill This command is used to stop an individual process by process ID. Levels: 9 = stop the process instantly 15 = ask the process the stop (shut down gracefully) (same as kill with no argument) ls This command will provide a directory listing. One useful option is the -l option which provides a “long” listing. For example: ls -l In another option, if you want to know which file was last changed, the files will be listed in date order with the most recently changed file listed last (useful for looking at the error log directory). For example: ls -lptr mkdir This command allows you to create a new directory. mount Used to “attach” a disk to the directory structure. Useful mainly for attaching disks not already attached. For example: mount intercal2:/usr2 /usr2 mountall Check the /etc/fstab list and make sure all drives listed are mounted. This is mainly useful in mounting all normally mounted drives when in single-user mode.
E-6
EXS ExchangePlus Software Operations Guide
UNIX Commands
mv Used to rename a file to another name. netstat Show the static routing table for the network. This command is usually written netstat –rn to show the current table. For example: Routing Table Destination
Gateway
Flags
-------------------- -------------------- -----
Ref
Use Interface
----- ------ ---------
172.27.0.0
172.27.2.214
U
3
3621
hme0
224.0.0.0
172.27.2.214
U
3
0
hme0
default
172.27.2.95
UG
0
23
127.0.0.1
127.0.0.1
UH
0
73383
lo0
pg This command is used to paginate the output from a command as in: man cat | pg pkill This command is used to stop an individual process by name arguments. -k = stop by sending a kill –9 (the default is stop by sending a kill--15) -a = returns the process ID of the named process ps List the active processes. This is used to show all the programs that are currently running on the machine. ExchangePlus supplies a script called “listit” which will list just the ExchangePlus specific programs.For example: ps -ef rcp – remote copy. For example: rcp
<source servername>:<path> <destination servername>:<path>
rm Remove a file. For example: rm <filename>
route – used to add or delete network routes from the routing table. For example: route add default <gateway ip address>
swap –l This command is useful to check how much swap space is being used. E-7
UNIX Commands
EXS ExchangePlus Software Operations Guide
su Request super user mode. This is mainly used for UNIX system administration functions like changing the password. It allows you to do administration without logging out. sum <filename> This command shows the checksum of a file unix2dos Convert a text file from Unix format to MSDOS format. This command adds a carriage return on the end. umount Used to unmount a disk that has been mounted vi System text editor. This command is useful for all kinds of text editing.
List of Common UNIX Commands
E-8
To accomplish this...
Type this...
Cancel a command
Ctrl-U, Ctrl-X, or @
Change the working directory to /usr/isos
cd /usr/isos
Change to working directory back to your home directory
cd
Copy a file
cp <oldfile> <newfile>
Copy a file to another directory
cp <oldfile> <directoryname> (The directory name must already exist)
Copy several files to another directory
cp <oldfile*> <directoryname> (The directory name must already exist)
Copy all the files in this directory and in all its subdirectories
cp -r * /<newdirectory>
Erase a file
rm <junkfile>
Rename a file
mv <oldname> <newname>
Move a file to another directory
mv <oldfile> <directoryname> (The directory name must already exist)
List file names
ls
List file names with sizes and dates
ls -l
List hidden files too
ls -al
List files and pause when screen is full
ls | more
EXS ExchangePlus Software Operations Guide
UNIX Commands
List of Common UNIX Commands To accomplish this...
Type this...
Look at a text file
cat <filename>
Look at a long text file
more < <filename>
Make a new link (name) for a file
ln <oldname> <newname>
Make new links (names) for files in a directory
ln <directoryname>/* <newdirectory>
Combine two files
cat <file1> <file2> > <newfile>
Compare two files
diff <file1> <file2>
Look at the manual page for the ls command
man ls | more
Change your password
passwd
Create a directory
mkdir <directoryname>
Display your current working directory
pwd
Remove a directory
rmdir <directoryname>
Rename a directory
mv <olddirectoryname> <newdirectoryname>
Print a file
lp <textfile>
Print a file on a printer named laser
lp -d laser
Cancel a print job
cancel < requestid>
Check the printer queue
lpstat -a all
Archive a directory onto another disk
tar cvf <filename>.isosbin.tar *
To find out who you are logged in as
who am I
To find out who is using your machine
who
To find a file if you remember its name
find . -name <filename> -print
To find a file if you know that it contains the word isos
grep "isos" *
To remote login to another computer
telnet <computername>
To remote log out after using telnet
exit
To remote login to another UNIX system
rlogin <computername>
To remote log out after using rlogin
exit
To find out the date and time
date
To change your local time zone
tz
E-9
UNIX Commands
EXS ExchangePlus Software Operations Guide
Quick List of Common vi Commands
The vi text editor is a screen editor which displays the file on screen. Most vi commands are one letter long and are case sensitive. The editor has two modes: • •
Command mode which is waiting for a command Input mode which is waiting to accept text input
If you are in command mode and want to switch to input mode, you can add text: • •
After the character the cursor is on by using the add (a) command, or Before the current cursor position, by using the insert (i) command.
If you are in input mode and want to give a command, press the ESC key. To exit out of vi, press the ESC key at least three times (the computer should beep) or type the following line::q! This line tells vi to quit and not save any changes.
List of Common VI Commands
E-10
VI command
Description
ESC
Return to command mode
Enter or Return
Move to beginning of next line
+
Move to beginning of next line
-
Move to beginning of preceding line
$
Move to end of current line
Ctrl d
Move down one page
Ctrl u
Move up one page
0 (zero)
Move to beginning of current line
a
Add text after cursor
A
Add text at end of current line
cw
Change word
ccs
Change line
C
Change to end of line
dd
Delete entire current line
D
Delete from cursor to end of line
G
Move or go to the end of the file
1G
Move to beginning of file
h
Move one space left
i
Add text before cursor
EXS ExchangePlus Software Operations Guide
UNIX Commands
List of Common VI Commands VI command
Description
I (uppercase i)
Add text at beginning of current line
j
Move down one line
k
Move up one line
l
Move right one space
o
Add text on new line after current line
O
Add text on new line before current line
:q! (followed by Enter)
Quit vi, even if changes are not savedâ&#x20AC;&#x2DC;
R
Replace text
u
Undo last change
U
Undo changes to current line
x
Delete one character
:w (followed by Enter)
Save (write) file
:x (followed by Enter)
Exit vi - save file if changes are made
ZZ
Exit vi - save file if changes are made
E-11
UNIX Permissions
EXS ExchangePlus Software Operations Guide
UNIX Permissions Permissions determine who can use which file or directory and how they can use it. There are several attributes listed below that explain the permissions of each file or directory. This is a typical file listing: -rw-r--r--
1
isos
group
92872
Sep 21 13:21 ISOSINST
This is the above example with the characters numbered and the other fields described: 12345678910 linkcount owner group filesize date time filename
Types of Permissions
- (File): This attribute is used on character 1 to determine if the listing is a file. l (Symbolic link): This attribute is used on character 1 to determine if the listing is a symbolic link. d (Directory): This attribute is used on character 1 to determine if the listing is a directory. r (Read permission): This attribute lets you look at a file or directory. You can use cat or a text editor to either see what’s in a file that has read permissions or to copy this type of a file. Read permission for a directory lets you list the directory’s contents. w (Write permission): This attribute lets you make changes to a file but not necessarily delete it or rename it; because those actions fall under the ability to write in the directory in which the file resides. If you have write permission in a directory, you can create new files in the directory and delete files from it. x or s (Execute permission): This attribute lets you run the program contained in the file. The program can be a real program or a shell script. If the file doesn’t contain a program, execute permission can provoke the shell to complain as it tries to make sense of your file. For a directory, execute permission lets you open files in the directory and use cd to get to the directory to make it your working directory.
- (No permission): This attribute is used when there are no permissions allowed on characters 2 through 10. Using the example listed in this book lets you understand more about what the readout means. Type this line: ls -l ISOSINST.
The result is this for example: -rw-r--r--
E-12
1
isos
group
92872
Sep 21 13:21 ISOSINST.
EXS ExchangePlus Software Operations Guide
UNIX Permissions
If you donâ&#x20AC;&#x2122;t specify a filename, UNIX lists all the files in the directory, which can be very useful. For every file, like the above example, the listing shows all this information: There are 10 characters listed for the permissions of each file or directory. These are explained as characters 1 through 10 and they are read from the left to right. Each character will be described with all of the possible attributes and also the given attribute of the example shown above. Character 1: In this example, the - attribute indicates that this is a file. Character 1 describes whether it is a file, symbolic link, or a directory. The options for the first character are:
- A hyphen is used as the attribute for this character to describe this listing as a file. l This attribute is used to describe this listing as a symbolic link. d This attribute is used to describe this listing as a directory. Characters 2, 3, 4: These three characters are used for the Owner/User (designated by the letter u). In this example, the r and w tell you that the owner/user has read and write permission only. Character 4 is a - so there are no execute permissions for this file. Character 2 is the read attribute, Character 3 is the write attribute, and Character 4 is the execute attribute. The options for these three characters are:
-
A hyphen is used as the attribute for Characters 2, 3, and 4 to describe that the owner/user does not have permission for reading, writing and executing. r This attribute is used for Character 2 to describe that this listing has the read permission. w This attribute is used for Character 3 to describe that this listing has the write permission. x or s This attribute is used for Character 4 to describe that this listing has the execute permission. Characters 5, 6, 7: These three characters are used for the Group (designated by the letter g). In this example, the r tells you that the group has read permission only. Characters 6 and 7 are - so the group does not have write and execute permissions for this file.
-
A hyphen is used as the attribute for Characters 5, 6, and 7 to describe that the group does not have permission for reading, writing and executing. r This attribute is used for Character 5 to describe that this listing has the read permission. w This attribute is used for Character 6 to describe that this listing has the write permission. x or s This attribute is used for Character 7 to describe that this listing has the execute permission. Characters 8, 9, 10: These three characters are used for everyone else (designated by the letter o). In this example, the r tells you that everyone else has read permission only. Characters 9 and 10 are - so everyone else does not have write and execute permissions for this file.
E-13
UNIX Permissions
EXS ExchangePlus Software Operations Guide
- A hyphen is used as the attribute for Characters 8, 9, and 10 to describe that everyone else does not have permission for reading, writing and executing. r This attribute is used for Character 8 to describe that this listing has the read permission. w This attribute is used for Character 9 to describe that this listing has the write permission. x or s This attribute is used for Character 10 to describe that this listing has the execute permission. Link Count: This number describes how many links (names) this file has. In this example, an l is displayed. For directories, this number is the number of subdirectories the directory contains plus 2. For most files, this shows a l as in the example above. Owner: The next word is the owner of the file or directory. In this example it is isos. Group: The next word is the group to which the file or directory belongs. In this example it is group. File Size: The next number is the size of the file in bytes or characters. This files example has 92872 bytes. Date/Time: Next is the date and time the file was last modified. In this example, it was last modified on September 21. Filename: The last word in the lineup is the filename itself that you are looking at. This example shows the filename to be ISOSINST.
Absolute Permissions
Sometimes permissions are written with numbers instead of the letters r, w, and x. Numbered permissions are called absolute permissions. When permissions are expressed as a number, it is a 3-digit number. The first digit is the owner/user’s permissions, the second digit is the group’s permissions, and the third digit is everyone else’s permissions. Every digit is a number from 0 to 7. The following table lists what the digits mean. Absolute Permissions Decoded
E-14
Digit
Permissions
0
None
1
Execute only
2
Write only
3
Write and Execute
4
Read only
5
Read and Execute
6
Read and Write
7
Read, Write, and Execute
EXS ExchangePlus Software Operations Guide
Changing Permissions
UNIX Permissions
If you own a file or directory, you can change its permissions. You use the chmod (for change mode) command. You tell chmod the name of the file or directory to change and the new permissions you want the file or directory to have for yourself (the owner), your group, and everyone else. You can either type the numerical absolute permissions or use letters. You use a collection of letters and symbols to type permissions by using letters. They consist of the following: Whose permissions you are changing: u for owner/user (the file’s owner); g for the group; and o for other (everyone else). If the permission should be a + (on, yes, OK) or - (off, no, don’t let them). The type of permission you are dealing with: r for read, w for write, and x for execute. Here are a few examples of changing permissions: chmod u+x ISOSINST.
This example allows the owner/user to be able to execute the file "ISOSINST.". chmod ugo+r readme
This example adds the read permission to the owner/user, group and everyone else for the file readme. chmod go-w readme
This example removes the write permission from the group and everyone else for the file readme. chmod 660 readme
This example allows the owner/user and associated group to read or change the file readme. It sets everyone else’s permission to 0 which means they can’t do anything. Also, no one has any execute permissions with this change to the file readme.
E-15
UNIX Permissions
E-16
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
F Error Messages/Response Status Values Overview Appendix F explains the format of some error messages that exist in ExchangePlus. These error messages are always shown on the command line. This appendix includes a list of all Response Status values. This list can also be found in EXS Switch Software API Reference Manual, Basic and Extended.
General Information The start of each error message is shown in bold type “Error. The format is related to switch API, and is followed by an explanation for the error. Example: Most entries will resemble the following (after the directory and filename), with variables inserted according to the nature of the error: ("Error (status variable) configure entity[%d]=0x%02x for DBack Index=%d\n", ret, status, i, ISDNDChan[dChanId].entities[i].entity, index); The "status" value in the above statement is returned by the switch as a hex value. The other numbers describe the target of the operation. This example provides the entity number (ID) of the backup ISDN D channel as a decimal value n. In the above format, ’%’ is a format used to indicate variable numbers that will show up on the command line either in decimal format, as %d, or in hex format, as %x. NOTE: All status values are given in the API Reference manuals for Basic and Extended API messages.
F-1
Categories of Error Messages
EXS ExchangePlus Software Operations Guide
Categories of Error Messages The following are examples of possible error messages in ExchangePlus. These will appear according to the API messages that have been sent, and for which some problem occurred during transmission. Noteâ&#x20AC;&#x201D;Errors that do not relate to API messages and contain no entity description
should be referred to Technical Support.
ISDN
1. This first message gives a decimal entry for the ISDN D Channel facility as well as a hex value for the response status returned. "Error (facility=%d, status=%02x) sending spanStateConfigure\n", i, status);
2. The next message gives an index value for ISDN D Channel in decimal, along with the status in hex: "Error (index=%d, status=%02x) ppl configuring L3P B bearer capability on F#=%d\n", index, status, i);
Wrong Config File
If you receive an error message that resembles one of the following, it means that you have the wrong configuration file: "Error: Token(%d) parsing token (%s)\n",*token,buffer); "Error: No Base CIC defined for SS7 trunk\n");
ISUP
These two messages resemble those that will appear for ISUP Signaling, in this case the Circuit [Group] Query Message (CQM) and the Suspend (SUS) messages, respectively: "Error (%d, status=%02x) sending IsupMsgConfig(CQM) \n", ret, status ); "Error (%d, status=%02x) sending IsupMsgConfig(SUS) \n",
F-2
EXS ExchangePlus Software Operations Guide
API Response Status Values
API Response Status Values MSB - 0x00
The following values are reported in the LSB Status fields when the MSB is 0x00. Value
0x00–0x0F
0x10
Indication These values differ depending on the message they are returned from. See the format of the specific message for the response status values. Positive Acknowledgment (ACK) The message was successfully processed, and any required actions were successfully completed.
0x11
Bad Checksum The message checksum does not match the checksum calculated by the system. An error must exist or a field must be missing.
0x12
Invalid Logical Span ID A field reserved for a logical span ID contains a number larger than the capacity of the switching matrix. The valid range is 0–63 (or 0-511 for 8 nodes).
0x13
Invalid Channel Number A field reserved for a channel number is outside the range of 0–30 for E1 or 0–23 for T1. NOTE: For E1, you can reference channel 30 only if the channel is configured for CCS, with the E1 Span Configure message.
0x14
Message Invalid for Current Matrix State The EX/CPU is not in a state to accept this message.
0x15
Negative Acknowledgment (NACK) Message could not be successfully processed.0x16 Invalid Address Range The address range specified in a block configuration message is not valid.
0x17
Invalid Data Type Returned in response to a message with invalid data parameters.
0x18
Invalid Channel B State Channel B is in an invalid state for the action required. The More Status field indicates the state. NOTE: This does not pertain to ISDN B channels.
F-3
API Response Status Values
0x19
EXS ExchangePlus Software Operations Guide
Trunk Status Dead One of the parties involved in a Call Processing message is associated with a dead line.
0x1A
Inseize Failure Inseize could not be successfully completed. (for example, distant end signaling error).
0x1B
Outseize Failure, No Acknowledgment Outseize failed because acknowledgment signaling conditions were never met (for example, a channel of E&M wink start trunk did not receive a wink).
0x1C
Outseize Failure, Glare Outseize attempted on trunk involved in inseizure processing.
0x1D
Invalid Channel A State or Invalid PPL Event Channel A is in an invalid state for the action required. The More Status field indicates the state of Channel A. A PPL component has received an invalid event for the current PPL state.
0x1E
Memory Allocation Failure Channel configuration change failed due to lack of available memory.
0x1F
Invalid Group Number Reserved for future use.
0x20
Invalid Action Value Invalid decision parameter action value was received.
0x21
Invalid Time The value entered for the time is not valid.
0x22
First Outseize Instruction Not A Seize The first instruction in an Outseize Control message must be a Seize if the channel is idle.
0x23
Outseize “Seize” Instruction Not Allowed This response is returned if one of the following occurs: – An Outseize Instruction List Configure message is sent with a Seize instruction (a Seize instruction cannot be preprogrammed). – An Outseize Control message with a Seize instruction is sent when one has been sent previously and the call is still active.
0x24
Outseize Failed Due To No Answer Outseize failed due to no answer from the distant end.
F-4
EXS ExchangePlus Software Operations Guide
0x25
API Response Status Values
Invalid Encoding Format One of the following is invalid: the encoding format of RAN or the encoding format in a Conference Create message.
0x26
Invalid Conference Size Sent in response to a host initiated Conference Create message where the conference size indicated is less than 2 or greater than the maximum number of channels allowed to be conferenced together.
0x27
DSP Not Configured for Requested Function No DSPs are configured for the function requested by the host (for example, configuration for service).
0x28
DSP Resources Not Available No DSP resources are currently available for the requested DSP function. Applies to DSP functions which are not managed as shared resources, for example, Conference Create.
0x29
Invalid Conference Output Option Conference output option indicated in the Conference Create message is not valid.
0x2A
Invalid Conference ID Conference ID sent by the host is not associated with any conferences previously established through the Conference Create message.
0x2B
Conference Create Failure Conference creation failed while the conference was establishing (for example, the MFDSP card was removed).
0x2C
Conference Establishing Returned in a Delete Conference, Connect to Conference, or Connect 1-Way to Conference message if the conference associated with the conference ID is in the process of being created.
0x2D
Incompatible PCM Encoding for Conference Returned in a Connect to Conference and Connect 1-Way to Conference message when the channel encoding format doesnâ&#x20AC;&#x2122;t match that of the conference (for example, A-law encoded channel connected to a Âľ-law encoded conference).
0x2E
Conference Size Exceeded Returned in a Connect to Conference message when the conference size has been exceeded.
0x2F
Maximum Broadcast Number Exceeded Returned in a Connect 1-Way or Connect 1-Way to Conference message when the number of 1-Way broadcasts exceeds the maximum allowed.
F-5
API Response Status Values
0x30
EXS ExchangePlus Software Operations Guide
DSP Resource Already Allocated Returned in a Collect Digit String or DSP Service Request message if digit collection is already active on the specified channel.
0x31
EXS Channel Violation Returned if an EX/CPU 1000 matrix card is being used in a system with more than 1,024 channels.
0x32
Channels A and B Already Connected A connect request has been sent for two channels which are already connected.
0x33
SS7 Configuration Error
0x34
Ring Timeslot Inaccessible Remote timeslot is not accessible from this node. Check switch hardware.
0x35
Invalid Logical Ring ID
0x36
Unassigned Ring
0x37
Ring Already Assigned
0x38
Invalid Ring State
0x39
No Bandwidth Available
0x3D
Invalid ICB Data An information control block has invalid length or count field, or the data within the ICB is invalid.
0x40
SRecord Invalid Download aborted due to invalid SRecord.
0x41
Out of Sequence, Restart Download Restart download due to sequence problem.
0x42
BRecord Invalid BRecord not accepted due to invalid value.
0x43
Node Not Ready A valid Logical Node ID has not been assigned (therefore, Polls cannot be requested) or the switch is not in a valid state for the requested action (such as Download Begin during Boot State).
0x44
No Download Begin Message Received A Download SRecord or Download BRecord message was sent without a proceeding Download Begin SRecord or Download Begin BRecord message
0x45
Invalid Download Sent in response to a Download Complete message when the download does not validate due to an incorrect checksum.
F-6
EXS ExchangePlus Software Operations Guide
0x47
Invalid Ring Loop Timing
0x56
System Busy Condition on Remote Node
0x57
EXS Conferencing Disabled
0x58
Invalid Remote Timeslot for Connect 1-way Forced
API Response Status Values
B address is not a valid remote timeslot. 0x59
Outseize Failure, Blocked
0x60
Outseize Failure, Guard Timing Returned when the connection terminating party is in the guard state allowing for inseizures only.
0x61
Invalid Slot The slot specified is not valid for the message sent.
0x62
Invalid Span Offset Field reserved for span offset is outside the valid range for the line card (0–1 for 2-span, 0–3 for 4-span, 0–7 for 8-span).
0x63
Unassigned Span The host has not yet assigned the specified Logical Span ID to a physical span.
0x64
Unassigned Span A The host has not yet assigned that span number to a hardware location. If two span/channels exist in message, the first span address is unassigned.
0x65
Unassigned Span B The host has not yet assigned that span number to a hardware location. If two span/channels exist in message, the second span address is unassigned.
0x66
Outseize Failure, Busied Out Returned when connection terminating party is busied out.
0x67
Channel B Out of Service Returned when connection terminating party is out of service due to a span alarm condition, is disabled, or both. Also returned if terminating party is going through error recovery or if no release of the distant end is detected.
0x68
Channel B Not Idle Returned when the connection terminating party is currently involved in call setup or teardown with another call.
F-7
API Response Status Values
0x69
EXS ExchangePlus Software Operations Guide
Span Already Assigned Span selected to be assigned is already assigned.
0x6A
Span Offset Not Available A span has been previously assigned to that slot and offset.
0x6B
Span Providing Loop Timing Span selected to be unassigned has been selected as a loop timing source.
0x6C
Framing Error An incorrect framing type was specified.
0x6D
Zero Suppression Error An incorrect zero suppression type was specified.
0x6E
Invalid Cable Length An invalid cable length was specified.
0x6F
Card Out of Service The card in the slot specified is not in service.
0x70
Single Matrix Out of Service Attempt A single matrix cannot be taken out of service.
0x71
Channel Out of Service One or more of the specified channels is out of service.
0x72
Span In Service The span specified is in service.
0x73
Span Out of Service The span specified is out of service.
0x74
Invalid Card Type Incorrect card type for attempted operation.
0x75
Invalid Entity The entity is out of range.
0x76
DSP SIMM in Service The SIMM specified is in service.
0x77
Invalid DSP SIMM Value The value specified for SIMM is invalid.
0x78
Invalid DSP Function Type The type specified for SIMM is invalid.
F-8
EXS ExchangePlus Software Operations Guide
0x79
API Response Status Values
Invalid DSP SIMM Configuration The configuration specified for SIMM is invalid.
0x7A
Deletion of VRAS SIMM In Progress An attempt has been made to download a recorded announcement to a SIMM while the SIMM is in the process of being deleted.
0x7B
Another Announcement Download is in Progress An unsuccessful attempt has been made to download a recorded announcement while another recorded announcement download is in progress.
0x7C
No Recorded Announcement Download Initiate Message Received A Recorded Announcement Download message has been sent without a prior Recorded Announcement Download Initiate message sent.
0x7D
CCS Redundant I/O Card Not Available ISDN or SS7 card in a redundant system is missing or unavailable.
0x7E
RAN Download to Out of Service DSP An attempt was made to download a recorded announcement to a DSP that is out of service.
0x7F
Software module still locked. This value is returned when attempting to configure a locked module for which no product license has been downloaded. The value can be received only with the SS7 Signaling Stack Configure (0x5C) and SS7 CIC Configure (0x6A) messages.
0x80
Partial Dial Condition The receive inter-digit timer has expired.
0x81
Permanent Signal Condition The 1st receive digit timer has expired.
0x82
Failure to Receive Wink 1 The maximum receive wink 1 detection timer has expired.
0x83
Failure to Receive Wink 2 The maximum receive wink 2 detection timer has expired.
0x84
Failure to Receive Wink 3 The maximum receive wink 3 detection timer has expired.
0x85
Failure to Receive Wink 4 The maximum receive wink 4 detection timer has expired.
0x86
Failure to Receive Wink 5 The maximum receive wink 5 detection timer has expired.
F-9
API Response Status Values
0x87
EXS ExchangePlus Software Operations Guide
Failure to Receive Wink 6 The maximum receive wink 6 detection timer has expired.
0x88
Failure to Receive Wink 7 The maximum receive wink 7 detection timer has expired.
0x89
Failure to Receive Wink 8 The maximum receive wink 8 detection timer has expired.
0x8A
No SIMM In Service For Requested Function There is no SIMM currently in service and configured for tone generation or VRAS.
0x8B
No Outpulsing Data Available Outpulse data is not available for the stage indicated. NOTE: This response is also returned when connecting to an idle SS7 channel.
0x8C
No Action ICBs in Message An Outseize Control or Inseize Control message was sent without any action ICBs included.
0x8D
No Data ICBs in Message An Outseize Control message was sent without a required data ICB included.
0x8E
Wink Tolerance Exceeded Given incoming wink exceeded maximum allowed duration.
0x8F
Failure to Detect Off-hook An ANI request off-hook was not detected within the detection interval.
0x90
Failure to Detect Dialtone Dialtone not detected within detection interval.
0x91
Inpulsed Stage Not Collected Collection of given stage of incoming digits not indicated.
0x92
Inpulsing Complete Timeout Time for complete incoming digit string collection for a given stage exceeded maximum time allowed.
0x93
Invalid Inpulsed Source Span/Channel An invalid span/channel is indicated as the inpulsing channel.
0x94
No Valid Inpulsed Data to Outpulse An Outpulse Stage N with Previously Inpulsed Digits instruction was initiated, however, the specified inpulsing has not occurred or has failed.
F-10
EXS ExchangePlus Software Operations Guide
0x96
API Response Status Values
Invalid Configuration Request for Span Specified configuration request for span is invalid.
0x98
No ULC Module ULC module is missing.
0x99
Invalid Configuration Request Configuration request is invalid.
0x9A
Invalid Command for Card Type, Span, or Channel Message does not apply to this card, span, or channel.
0x9B
Illegal D Channel Function For ISDN D channel call control administration only.
0x9C
Invalid ISDN D Channel ISDN PRI D channel is not valid.
0x9D
Invalid ISDN B Channel ISDN PRI B channel is not valid.
0x9E
Invalid ISDN Facility ISDN facility is invalid.
0x9F
Invalid Value for Entity The value specified for entity is invalid.
0xA0
SIMM Not Present SIMM specified is not present.
0xA1
D Channel Assigned A D channel is assigned on span ID selected.
0xA2
Called Party Mandatory for ISDN Setup The called party digits are mandatory instruction elements over ISDN PRI.
0xA3
Card Not Ready for Configuration The card is not in a valid state to accept configuration data.
0xA4
ISDN D Channel Exceeds Max The ISDN card specified can not be configured for another D channel. Check the cardâ&#x20AC;&#x2122;s address mode.
0xA5
Invalid Option for Protocol Protocol assigned to channel in ranges does not allow for the function the host is trying to perform.
F-11
API Response Status Values
0xA6
EXS ExchangePlus Software Operations Guide
PPL Table Size Exceeds Max Size of table host wishes to download is too large.
0xA7
PPL Table Already Exists Table ID already in use.
0xA8
PPL Table Does Not Exist Table ID referenced does not yet exist.
0xA9
PPL Table Does Not Validate The table the host has downloaded does not validate. Further information can be found in Byte and Entity fields of message responding to this error.
0xAA
Insufficient Hardware The function the host is trying to perform can not be performed because the hardware needed is not present.
0xAB
PPL Table Part of Protocol Error occurred trying to delete a Primitive Table or State/Event Table. The protocol that the table is associated with must be deleted first.
0xAC
Invalid Command for ISDN Facility The command for the ISDN facility was not valid.
0xAD
DSP Resource Inconsistency Returned in a Collect Digit String or DSP Service Request message if digit collection is already active on the specified channel. Also returned when the host attempts to configure two transmitters on one card at the same time.
0xAE
Hardware Not Configured for DSP Function The DSP resource management software has been requested to provide a DSP resource which does not exist. Please check DSP configurations of MFDSP card by sending a Card Status Query message.
0xAF
PPL Layer Forward Signal Timeout Forward R2 Signal has not been detected within the maximum amount of time allowed.
0xB0
PPL Layer Backward Signal Timeout Backward R2 Signal has not been detected within the maximum amount of time allowed.
0xB1
PPL Layer Premature Answer Answer was detected on an outgoing call before call setup completion.
0xB2
PPL Layer Congestion Received Backward R2 Congestion Signal has been detected.
F-12
EXS ExchangePlus Software Operations Guide
0xB3
API Response Status Values
System Table in Use System software is using the table you are trying to modify/create. Please wait a few seconds and try again.
0xB4
Line Card Response To Matrix Timeout The matrix timed-out waiting for a response from a line card. Check configuration for channel ranges that span more than two cards.
0xB5
CPA Member Exceeds Maximum For Class The maximum number of call progress analysis patterns which can be included in a class has been reached.
0xB6
CPA Pattern Exceeds Maximum The maximum amount of call progress analysis patterns supported by the system has been reached.
0xB7
CPA Tone Group Exceeds Maximum The maximum amount of call progress analysis tone groups supported by the system has been reached.
0xB8
Invalid Pattern ID An invalid pattern ID has been specified for call progress analysis.
0xB9
Invalid Interval Descriptor Count An invalid interval descriptor count has been specified for call progress analysis.
0xBA
CPA Classes Exceeds Maximum The maximum amount of call progress analysis classes supported by the system has been reached.
0xBB
Invalid CPA Class An invalid call progress analysis class was specified in a configuration message.
0xBC
Invalid Data Found at Byte N The message became invalid because of data found at byte offset N. See the LSB of the More Status field of the message for the byte offset where data became invalid.
0xBD
Invalid Table Type The table type specified is invalid.
0xBE
Invalid Table ID The table ID specified is invalid.
0xBF
ISDN Response Wait Timeout ISDN-initiated message timed-out; waiting for a response from the network (for example, Register with no Release Complete).
F-13
API Response Status Values
0xC0
EXS ExchangePlus Software Operations Guide
Action Denied Action request denied.
0xC1
Action Rejected Action request rejected.
0xC2
Slot Assigned As Standby The slot number is assigned as a standby slot.
0xC3
Slot Not Assigned As Standby The slot number is not assigned as a standby slot.
0xC4
Standby I/O Relay State Mismatch The states of the relays of the I/O cards specified do not match (relays on one are enabled; relays on the other are disabled).
0xC5
Incompatible Line Card Types The line cards specified are not compatible.
0xC6
Redundant I/O Cards Not Present Redundant I/O cards are not present in one or more of the slots specified.
0xC7
Line Card Switchover Already Completed The Line Card Switchover requested has already been completed.
0xC8
Invalid SIMM Type Trying to perform VRAS functions on a non-VRAS SIMM.
0xC9
Invalid Recorded Announcement ID The recorded announcement ID is not in the range of 0x00â&#x20AC;&#x201C;0x3FF or the host has requested a recorded announcement ID that does not exist in the system.
0xCA
Recorded Announcement Already Exists The host has attempted to download an announcement using a recorded announcement ID that is already stored in the system.
0xCB
Insufficient Memory on VRAS SIMM Not enough memory to store the specified recorded announcement.
0xCC
Maximum Recorded Announcement Limit Reached on VRAS SIMM The host has attempted to download more than 300 recorded announcements to a particular VRAS SIMM.
0xCD
Invalid IE Length The host has sent an information element (IE) in an ICB with an incorrect length.
0xCE
Invalid IE Count The host has sent an ICB with an incorrect IE Count value.
F-14
EXS ExchangePlus Software Operations Guide
0xCF
API Response Status Values
Invalid Component Type The host has sent an ICB with an incorrect component type.
0xD0
ISDN D Channel Switchover Timed Out The D channel switchover could not be completed due to timer expiration.
0xD1
Invalid ISDN Connection Endpoint Identifier A valid Connection Endpoint Identifier could not be found for the addressed D channel.
0xD2
Invalid AIB The address information block (AIB) is not in the proper format, or it addresses an invalid PPL state machine or channel.
0xD3
Invalid Protocol ID A protocol ID specified in a PPL message is invalid.
0xD5
Channel Already In Service Applies to ISDN and SS7 only. Indicates that you attempted to either assign or de-assign a protocol to a channel that is in service.
0xD6
Invalid Command For Trunk Front End An invalid command was sent from the host for a trunk front end.
0xD7
End Of PPL Audit Data The end of the PPL auditing data has been reached. There are no more PPL auditing blocks in the PPL auditing logs.
0xD8
Invalid SS7 Signaling Stack ID (0–3) A signaling stack was specified that either: – Was greater than the allowed values (0–3), or – Did not match the signaling stack for the primary resource
0xD9
SS7 Signaling Stack Already Configured An attempt was made to configure an SS7 signaling stack that is already configured.
0xDA
Invalid SS7 Module Count An attempt was made to configure an SS7 signaling stack with an invalid number of modules. The module count must be 3.
0xDB
Duplicated SS7 Module An SS7 signaling stack configuration attempt specified the same SS7 model more than once.
F-15
API Response Status Values
0xDC
EXS ExchangePlus Software Operations Guide
Unsupported SS7 Module Variant An SS7 signaling stack configuration attempt specified an unsupported SS7 module variant.
0xDE
Invalid SS7 Module Type An SS7 signaling stack configuration attempt specified an invalid SS7 module type.
0xDF
Invalid SS7 Signaling Stack Configuration An SS7 signaling stack configuration attempt could not be interpreted correctly.
0xE0
SS7 Signaling Stack Not Configured An SS7 signaling stack configuration attempt specified a signaling stack ID that is not configured.
0xE1
Invalid SS7 Signaling Link ID An invalid SS7 signaling link ID was specified that was either: – Too large for the SS7 card model, or – An attempt was made to de-configure a link that is not configured.
0xE2
Invalid SS7 Signaling Link Set ID An invalid SS7 signaling link set ID was specified. Valid Link Set IDs are 0 to 35.
0xE3
SS7 Signaling Link Set Not Configured An SS7 configuration attempt specified a signaling link set that is not configured.
0xE4
SS7 Signaling Link Already Configured An SS7 configuration attempt expected the specified SS7 signaling link either: – Was not configured, or – Did not have configured SS7 signaling links
0xE5
Invalid SS7 SLC An SS7 configuration attempt specified an invalid SLC. Valid SLC codes are 0 to 15.
0xE6
SS7 Signaling Link Set Already Configured An SS7 configuration attempt expected either: – The specified SS7 signaling set was not configured, or – The specified SS7 signaling stack had no configured SS7 signaling link sets
0xE7
SS7 APC Already Configured An SS7 configuration attempt specified an adjacent point code (APC) that has already been associated with another link set. All links within a SS7 signaling stack that link to an adjacent signalling point must belong to a single link set.
F-16
EXS ExchangePlus Software Operations Guide
0xE8
API Response Status Values
Invalid SS7 Signaling Link Data Rate An SS7 configuration attempt specified an invalid signaling link data rate. Valid data rates are 64 Kbps (0) and 56 Kbps (1).
0xE9
SS7 SLC Already Configured An SS7 configuration attempt specified an SLC that has already been assigned to another link within the same link set.
0xEA
Invalid DCE-DTE Configuration An SS7 configuration attempt specified an invalid DCE-DTE configuration. SS7 V.35 is not supported in System Software Version 5.1.
0xEB
SS7 Signaling Route Already Configured One of the following is true: – An SS7 signaling route configuration specified a route ID that already exists, or – An SS7 signaling route configuration attempted to de-configure a destination for which CICs are still configured. – An SS7 signaling linkset configuration attempted to de-configure a linkset for which routes are still configured.
0xEC
Invalid SS7 Signaling Route Mode Configuration 1. An SS7 Signaling Route Configure message failed due to one of the following: – It specified a previously configured destination ID, but the specified stack ID or DPC did not match the previously configured destination ID. – It used a destination ID that was not previously configured, but a previously configured destination ID for the signaling stack has a matching DPC. – It reused the same link set to the same DPC (Route duplication) 2. An SS7 Signaling Route Query message failed due to one of the following: – An invalid destination ID (valid IDs are 0 to 63) – An invalid route ID (valid IDs are 0 to 254) – Either the specified route ID or destination ID is not configured to the specified stack ID – The specified destination ID and route ID are inconsistent
0xED
No SS7 Signaling Route Entry Available An SS7 Signaling Route Configure message was received and there were no unused route table entries. EXS 4.B1 supports up to 20 routes per stack.
0xEE
SS7 Signaling Destination Not Configured An SS7 configuration attempt specified a destination in the SS7 signaling stack that was not previously configured.
F-17
API Response Status Values
0xEF
EXS ExchangePlus Software Operations Guide
No SS7 Signaling DPC Entry Available An SS7 DPC-CIC Configure message was received specifying a DPC when no more DPC table space is available. The system allows for one DPC per span. NOTE: If you try to configure more than 128 CIC groups on one system, you will get this message.
0xF0
CCS Redundancy Already Configured A CCS redundancy configuration attempt specified a primary and/or secondary slot that has previously been configured.
0xF1
CCS Redundancy Not Configured A CCS redundancy configuration or query message was received before a CCS Redundancy Configure message was received.
0xF2
CCS Redundancy: Not A Primary Slot The CCS Redundancy Configure message attempted to reference the secondary card in a CCS redundant pair. You must reference the primary card only.
0xF3
Channel Already an SS7 CIC An SS7 CIC Configure message was received that specified a CIC (or group thereof) that has been previously configured for the same channel.
0xF4
Primary SS7 Slot Same As Secondary Slot An CCS Redundancy Configure message was received specifying the same slot as the primary and secondary slot.
0xF5
No SS7 Signaling Links Configured An SS7 configuration attempt specified one of the following: â&#x20AC;&#x201C; An SS7 signaling link that is not configured â&#x20AC;&#x201C; An SS7 signaling link set that has no configured SS7 signaling links
0xF6
No SS7 Signaling Routes Configured An SS7 configuration attempt specified a destination ID or route ID that was not configured.
0xF7
SS7 DPC-CIC Already Configured An SS7 DPC-CIC Configure message was received that specified a DPC-CIC (or group thereof) that has been previously configured for the same signaling stack.
0xF8
F-18
No SS7 Configuration Entity Available 1.
An SS7 signaling route configuration attempt failed because it specified an entity (destination ID or route ID) that was not currently configured, but may have been configured previously.
2.
An SS7 DPC-CIC configuration attempt failed because no free DPC-CIC resources were available.
EXS ExchangePlus Software Operations Guide
0xF9
API Response Status Values
Invalid Number of SS7 ISUP Parameters An SS7 ISUP Message Configure message was sent with an invalid number of parameters.
0xFA
Invalid SS7 ISUP Message Type An SS7 ISUP Message Configure message was sent with an illegal Message Configuration Entry value.
0xFB
Node Already Exists The Assign Logical Node ID message failed because node is already assigned.
0xFC
Invalid Node ID A node ID is invalid because it met one of the following conditions: â&#x20AC;&#x201C; Specified node ID is greater than maximum value of 31 (0x1F). â&#x20AC;&#x201C; Specified node ID is greater than maximum value allowed when EXS conferencing is enabled.
0xFD
Node ID Not Configured Assignment of spans failed because node is not yet assigned.
0xFE
MSB- 0x4D
Maximum Number of Redundant Objects Reached The following values appear in the LSB when the MSB is 0x4D.
LSB Data
Value 0x01
Indication Software key format not valid. This value may appear in the LSB of the Status field of a response. This value is returned if the first two bytes of the Product License field are not defined key types, or if the product license contains invalid data.
0x02
Data decrypted not valid. This value may appear in the LSB of the Status field of a response. This value is returned when a serial number decrypted from a product license cannot be matched against an existing serial number on a switch.
F-19
API Response Status Values
MSB - 0x50
F-20
EXS ExchangePlus Software Operations Guide
The following values appear in the LSB when the MSB is 0x50. 0x01
Response Timeout
0x02
Null Buffer
0x03
Queue Full
0x04
Feature Disabled
0x05
No ICBs
0x06
Invalid ICB Type (Message Not Processed)
0x07
Invalid ICB Type (Message Partially Processed)
0x08
Invalid ICB Subtype (Message Not Processed)
0x09
Invalid ICB Subtype (Message Partially Processed)
0x0A
Invalid Message (Message Not Processed)
0x0B
Invalid Message (Message Partially Processed)
0x0C
Unauthorized Command
0x0D
Incorrect ICB Data Length
0x0E
Host Not Connected
0x0F
Incorrect Host ID
0x10
Reserved
0x11
Maximum Number of Queries Exceeded
0x12
Multi Host Already Enabled
0x13
Multi Host Already Disabled
0x14
Multi Host Download In Progress
0x15
Multi Host Being Enabled, Wait 32 Sec
0x16
Odd ICB Data Count (Extended API)
0x17
Non-Unique Host ID
0x18
Invalid ICB Subtype
0x19
Host ID Assigned to Different Host
0x1A
Invalid ICB Data Entry
EXS ExchangePlus Software Operations Guide
MSB - 0x51
API Response Status Values
The following values appear in the LSB when the MSB is 0x51. 0x01
End of Route Table
0x02
Retry Limit Exceeded
0x03
Termination Error
0x04
Purge
0x05
No Destination Found
0x06
EXS Recursion
0x07
ACK Wait Timer Expired
0x08
No Common Resource Group Found
0x0A
Termination Validation Error
0x0B
Termination Busy Status
0x0C
End of Entry Data
0x0D
Invalid Routing Method
0x0E
Invalid Resource Group Table
0x0F
Invalid Route Table
0x10
Reserved
0x11
Invalid Resource Group
0x12
Invalid Criteria
0x13
Invalid Entry Data
0x14
System Error
0x15
Illegal Instruction
F-21
API Response Status Values
F-22
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
Overview
G SS7 and ISDN Protocols Overview Appendix G provides information on the Signaling System 7 (SS7) protocol and the Integrated Services Digital Network (ISDN) protocol.
SS7 SS7 (Signaling System 7) is a network protocol that provides control for telecommunications networks. SS7 achieves this control by creating and transferring the following tasks to various network components: • • •
Call Processing Network management Maintenance
SS7 uses out-of-band signaling, which means that all signaling information (control information) is sent across a dedicated 56 or 64 Kbps channel (called a signaling link) that is separate from the voice circuit used for telephone calls. This enables telephone calls to be set up more efficiently and more securely. SS7 is now an international standard (also termed C7).
SS7 Applications
The SS7 card allows the switch to act as a Signaling Point (SP) in the SS7 network architecture. The switch generates and receives SS7 messages to manage voice circuits and provide a transport mechanism for Advanced Intelligent Network (AIN) applications. The SS7 network and protocol are used for: • • • •
• •
Setting up and managing the connection for a call. Tearing down the connection when the call is complete. Billing records. Handling special features like call forwarding, calling party name, calling party number and number display, three-way calling, and other Intelligent Network (IN) services. Toll-free calls (800 and 888) and toll (900) calls. Call service for wireline and wireless, including mobile telephone subscriber verification and authentication, Personal Communication Service (PCS), and roaming with cellular calls.
G-1
SS7
SS7 Acronyms
EXS ExchangePlus Software Operations Guide
Typical industry-related SS7 acronyms are listed below: ANSI American National Standards Institute APC
Adjacent Point Code
CCIS
Common Channel Interoffice Signaling
CCS7 Common Channel Signaling System 7 CIC
Circuit Identification Code
CPC
Call Processing Control
DCE
Data Communications Equipment
DPC
Destination Point Code
DTE
Data Terminal Equipment
ISDN Integrated Services Digital Network ISUP
ISDN User Part
L3P
Layer 3 Plus
MPC
Maintenance Process Control
MTP
Message Transfer Part
OPC
Originating Point Code
SCCP Signaling Connection Control Part SCP
Service Control Point
SLC
Signaling Link Code
SPRC Signaling Procedure Control
SS7 Network Architectures
G-2
SSP
Service Switching Point
SS7
Signaling System 7
STP
Signal Transfer Point
Within an SS7 network, there are three major components: •
Service Switching Points (SSP) - are switches that perform call processing on calls that originate, tandem, or terminate at the switch.
•
Signal Transfer Points (STPs) - are switches that relay messages between network switches and databases.
•
Service Control Points (SCP) - contain centralized network databases, which provide enhanced services.
EXS ExchangePlus Software Operations Guide
SS7
The SS7 card permits the switch to act as an SSP in an Advanced Intelligent Network (AIN). The SS7 card supports the following two architectures:
Associated Mode Signaling
â&#x20AC;˘
International Telecommunications Union - Technology Sector (ITU)
â&#x20AC;˘
American National Standards Institute (ANSI)
Associated Mode Signaling, shown in Figure G-1, is the typical international (ITUTS) architecture. Voice circuits between the switch and the DPC are connected over T1, E1 or J1 carriers. SS7 signaling between the switch and the DPC is over a signaling link directly connecting the switch to the SP/SSP. There can be multiple signaling links between a switch and an SP.
EXS
DPC
Voice Circuits (E1)
Figure G-1 Associated Mode Signaling
Quasi-associated Mode Signaling
Quasi-associated Mode Signaling, shown in Figure G-2, is the typical North American (ANSI) architecture. A T1 carrier connects voice circuits between the switch and a Destination Point Code (DPC), typically either another switch as an SP or an SSP. SS7 signaling between the switch and SP/SSP is over a signaling link through one or more STPs.
SS7 Signaling
STP
STP
EXS
DPC Voice Circuits (T1)
Figure G-2 Quasi-Associated Mode Signaling
SS7 Point Codes
The point code in an SS7 network identifies a specific network node so that the SS7 protocol can route calls correctly. When you make a call, the dialed digits that make up the telephone number are a Global Title. The digits have to be translated from the Global Title format into an SS7 format by the STP. The process that does this is termed Global Title Translation.
G-3
SS7
SS7 Software Architecture
EXS ExchangePlus Software Operations Guide
SS7 software consists of the following modules: • • • • •
L3P ISUP L3P TUP TUP MTP
Each signaling stack must include MTP, L3P, and at least one user part. Selection of a specific module automatically uses the associated default PPL components. Figure G-3 and Figure G-4 show how the SS7 Signaling Stack integrates into the switch architecture. Default protocol component sets for each module are stored as part of system software and do not require downloading. Selection of a specific module automatically uses the associated PPL components.
Layer 5 Host
Layer 4 Common Call Processing
Layer 3 Plus (L3P)
SS7 Signaling Stack
ISUP
MTP2 and MTP3
Physical Layer
Figure G-3 SS7 Software Architecture (Single Stack)
G-4
EXS ExchangePlus Software Operations Guide
SS7
Layer 5 Host
Layer 4 Common Call Processing
Layer 3 Plus (L3P)
Layer 3 Plus (L3P)
ISUP
ISUP
MTP2 and MTP3
MTP2 and MTP3
Physical Layer Figure G-4 SS7 Software Architecture (Multiple Stacks)
Layer 3 Plus (L3P)
L3P is an interface between Layer 3 Call Control (ISUP/TUP) and Layer 4 EXS Call Control on the EX/CPU, and Layer 5 (the host application). It also manages application-specific variants for call control. L3P includes the following PPL Components:
Call Control
•
L3P CIC Control Formats the presentation of SS7 data to and from the host and manages call control.
•
L3P Link Management Manages signaling links and formats presentations of SS7 signaling link control to and from the host.
•
L3P Telephone User Part (TUP) L3P TUP is an interface between Layer 3 (TUP), Layer 4 EXS Call Control on the EX/CPU, and Layer 5 (the host). L3P TUP formats information from Layer 3 into the programmed format for the host and host formatted information for Layer 3. It also manages application-specific variants for call control.
Call control, circuit supervision, and maintenance can be managed using either the ISDN User Part (ISUP) or Telephone User Part (TUP) interfaces.
G-5
SS7 Cause Codes
EXS ExchangePlus Software Operations Guide
ISUP
TUP
ISUP is the protocol for voice and non-voice services. ISUP includes the following PPL components: •
ISUP CPC (Call Processing Control) CPC manages the call processing portion of ISUP. It manages both incoming and outgoing call setup and tear down.
•
ISUP SPRC SPRC acts as an ISUP message router. It validates and routes incoming ISUP messages to the correct ISUP state machine. It also sends outgoing messages to MTP.
•
ISUP MPC/CSC (Maintenance Process Control/Circuit Supervision Control) A collection of state machines that manage circuit maintenance, such as group blocking/unblocking and circuit reset.
TUP includes the following components: • • • •
China TUP
TUP CPC CPC manages incoming and outgoing call setup and tear down. TUP SPRC SPRC validates and routes incoming TUP messages to the correct TUP state machine. It also sends outgoing messages to MTP.
In China, TUP supports basic call processing. This TUP handles analog circuits only, not digital and data transmission capabilities.
SS7 Cause Codes ITU Standard Causes Normal Class
The following cause values, names and definitions are identified in Q.850 as pertaining to ISUP. Cause 1 Unallocated (unassigned) number - This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned). Cause 2 No route to specified transit network - This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network, while it does exist, does not serve the equipment that is sending this cause. This cause is supported on a network dependent basis.
G-6
EXS ExchangePlus Software Operations Guide
SS7 Cause Codes
Cause 3 No route to destination - This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network-dependent basis. Cause 4 Send special information tone - This cause indicates that the called party cannot be reached for reasons that are of long term nature and that the special information tone should be returned to the calling party. Cause 5 Misdialed trunk prefix - No procedures specified for US networks. Cause 8 Preemption - This cause indicates that the call is being preempted. Cause 9 Preemption - circuit reserved for reuse. This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange. Cause 16 Normal call clearing - This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network. Cause 17 User busy - This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy, it is noted that the user equipment is compatible with the call. Cause 18 No user responding - This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated. Cause 19 No answer from user (user alerted) - This value is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time. NOTE: This cause is not necessarily generated by Q.93l procedures but may be generated by internal network timers. Cause 20 Subscriber absent - This cause value is used when a mobile station has logged off, radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface. Cause 21 Call rejected - This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. The network may also generate this cause, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection. Cause 22 Number changed - This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this cause value, cause number 1, unallocated (unassigned) number shall be used.
G-7
SS7 Cause Codes
EXS ExchangePlus Software Operations Guide
Cause 27 Destination out of order - This cause indicates that the destination indicated by the user can not be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signaling message was unable to be delivered to the remote party; e.g., a physical layer or data link layer failure at the remote party, or user equipment off-line. Cause 28 Invalid number format (address incomplete). This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. NOTE: This condition may be determined: – Immediately after reception of an ST signal, or – On time-out after the last received digit. Cause 29 Facility rejected - This cause is returned when the network cannot provide a supplementary service requested by the user. Cause 31 Normal, unspecified - This cause is used to report a normal event only when no other cause in the normal class applies. Resource Unavailable Class
Cause 34 No circuit/channel available - This cause indicates that there is no appropriate circuit/channel presently available to handle the call. Cause 38 Network Out of order - This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time, e.g., immediately re-attempting the call is not likely to be successful. Cause 41 Temporary failure - This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time, e.g., the user may wish to try another call attempt almost immediately. Cause 42 Switching equipment congestion - This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic. Cause 43 Access information discarded - This cause indicates that the network could not deliver access information to the remote user as requested, i.e., user-to-user information, low layer compatibility, high layer compatibility, or sub-address, as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic. Cause 44 Requested circuit/channel not available - This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface. Cause 46 Precedence call blocked - This cause indicates that there are no preemptable circuits or that the called user is busy with a call of equal or higher preemptable level. Cause 47 Resource unavailable, unspecified - This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.
G-8
EXS ExchangePlus Software Operations Guide
Service or Option Unavailable Class
SS7 Cause Codes
Cause 50 Requested facility not subscribed - This cause indicates that the user has requested a supplementary service that is implemented by the equipment that generated this cause, but the user is not authorized to use. Cause 53 Outgoing calls barred within CUG – No procedure specified for US networks. Cause 55 Incoming calls barred within CUG – No procedure specified for US networks. Cause 57 Bearer capability not authorized - This cause indicates that the user has requested a bearer capability that is implemented by the equipment that generated this cause, but the user is not authorized to use. Cause 58 Bearer capability not presently available. This cause indicates that the user has requested a bearer capability that is implemented by the equipment which generated this cause but which is not available at this time. Cause 62 inconsistency in designated outgoing access information and subscriber class - This cause indicates that there is an inconsistency in the designated outgoing access information and subscriber class. Cause 63 Service or option not available, unspecified - This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.
Service/Option Not Implemented Class
Cause 65 Bearer capability not implemented - This cause indicates that the equipment sending this cause does not support the bearer capability requested. Cause 69 Requested facility not implemented - This cause indicates that the equipment sending this cause does not support the requested supplementary service. Cause 70 Only restricted digital information bearer capability is available - This cause indicates that the calling party has requested an unrestricted bearer service but that the equipment sending this cause only supports the restricted version of the requested bearer capability. Cause 79 Service or option not implemented, unspecified - This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.
Invalid Message (e.g. Parameter Out of Range) Class
Cause 87 User not member of CUG – No procedures specified for US networks. Cause 88 Incompatible destination - This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility, attributes (e.g., data rate) which can not be accommodated. Cause 90 Non-existent CUG – No procedures specified for US networks.
G-9
SS7 Cause Codes
EXS ExchangePlus Software Operations Guide
Cause 91 Invalid transit network selection - This cause indicates that a transit network identification was received which is of an incorrect format as defined in Annex C of TI.607 Cause 95 Invalid message, unspecified - This cause is used to report an invalid message event only when no other cause in the invalid message class applies. Protocol Error (e.g. Unknown Message) Class
Cause 97 Message type non-existent or not implemented - This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause. Cause 99 Information Element/Parameter non-existent or not implemented This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element identifier(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message. Cause 102 Recovery on timer expiry - This cause indicates that a procedure has been initiated by the expiry of a timer in association with error handling procedures. Cause 103 Parameter non-existent or not implemented â&#x20AC;&#x201C; pass on â&#x20AC;&#x201C; No procedures specified for US networks. Cause 110 Message with unrecognized parameter discarded - This cause indicates that the equipment sending this cause has discarded a received message which includes a parameter that is not recognized. Cause 111 Protocol error unspecified - This cause is used to report a protocol error event only when no other cause in the protocol error class applies.
Interworking Class
Cause 127 Interworking, unspecified This cause indicates that there has been interworking with a network which does not provide causes for actions it takes. Thus, the precise cause for a message that is being sent cannot be ascertained.
ANSI Standard Causes Normal Class
Cause 23 Unallocated destination number - This cause indicates failure of a business group call because the business group identifier is unknown. Cause 24 Undefined business group - This cause indicates failure of a business group call because the destination number is unallocated in the business group numbering plan. Cause 25 Exchange routing error - This cause indicates that the called party cannot be reached because of an error in exchange number translation tables used to route the call (results when the hop counter parameter value is decremented to 0).
G-10
EXS ExchangePlus Software Operations Guide
Resource Unavailable Class
ISDN
Cause 45 Preemption - (Used by T1.113-1988 and Tl.619-1992.) This cause indicates that the equipment sending this cause has preempted the circuit for a new call and the existing call should be cleared. Cause 46 Precedence call blocked - (Used by T1.113-1988 and T1.169-1992.) In case of a call with a precedence level higher than the lowest level (ROUTINE), this cause indicates that all circuits are busy on calls of equal or higher priority.
Service or Option Not Available Class
Cause 51 Call type incompatible with service request - This cause indicates that an action was rejected because it was not compatible with the bearer capability of the call. Cause 54 Call blocked due to group restrictions - This cause indicates failure of a business group call because it did not pass line privileges and/or subgroup screening.
ISDN An international standard for voice, data, and signaling is possible through the ISDN protocol. It uses a standard out-of-band signaling system, end-to-end digital transmission circuits, and makes significantly more bandwidth available to the desktop. The ISDN PRI is designed for switches, telephony, and voice processing systems. The ISDN PRI card provides Primary Rate ISDN D channel packet processing and call control for ExchangePlus. This card, in conjunction with the T1 and E1 network interface cards, interfaces to various equipment types supporting the ISDN PRI protocol. These include tandem (class 4) switches, end office (class 5) switches, PBXs, and proprietary implementations, not only in North America but throughout the world. The ISDN PRI card supports the following: • • • • • • • • •
32 D channels per-card over T1 or E1 ITU-T Q.921, Q.931 Compatibility National ISDN, Euro-ISDN, JATE, ITU-T Variants Network Side Euro-ISDN D Channel Backup NFAS Incoming B Channel Negotiation Flexible Information Element (IE) reporting and parsing (with PPL messages) Redundancy
The ExchangePlus ISDN PRI implementation is based on ITU-T Q.921 and Q.931 specifications. Each implemented variant references the appropriate interface document supplied by the equipment manufacturer. The interface document is usually a variant of the ITU-T recommendations.
G-11
ISDN
EXS ExchangePlus Software Operations Guide
Since each manufacturer supports different services, the host manages the information to send and receive in specific messages. This lets you access many features and services at the host layer and carry them out using PPL-controlled call control logic.
ISDN Channels
Each ISDN PRI card supports 32 D channels. Each D channel provides the High Data Link Control (HDLC) communications over T1 or E1 on one timeslot on the span. Each D channel controls up to nine other spans in addition to the span on which it is located. Depending upon the provisioning requirements, you can have one D channel per span [Facility Associated Signaling (FAS)], or one D channel managing 10 spans [Non-Facility Associated Signaling (NFAS)]. You can control a total of 32 spans using all FAS D channels, or 10 spans per NFAS D channel (to a maximum of 64 per system). You can intermix both FAS and NFAS D channels on a card with each supporting a different variant. You can insert multiple ISDN PRI cards in any line card slot in the switch. Each has unrestricted access to all timeslots, so you can configure any timeslot in the system as a D channel.
Redundancy
Installing an ISDN PRI Redundant I/O and two ISDN PRI cards provides redundancy for all 32 D channels. If the active card fails, or if you remove the card, the standby card takes over the call processing operations. All calls in a connected state are retained while others are purged.
Features
The ISDN PRI card supports the following features: • • • • •
D Channel Backup
ISDN Information Elements (IE)
G-12
D Channel Backup Information Element Library B Channel Negotiation ANI on Demand Vari-A-Bill Billing
The ISDN PRI card supports the D Channel backup procedure as defined by AT&T TR 41459. This procedure provides a standby D channel when using NFAS. When an active D channel fails, or if there is a span alarm, the switch converts to the standby D channel and maintains active calls. This is a provisioned option and is applicable only when using NFAS. D Channel backup is supported on the T1 cards only. ExchangePlus provides a format to send and receive IEs per D channel.
EXS ExchangePlus Software Operations Guide
B Channel Negotiation
ANI On Demand
Vari-A-Bill Billing
ISDN Software Architecture
ISDN
The ISDN PRI card supports B channel negotiation on incoming calls as defined in AT&T TR41459 for both E1 and T1 cards. This feature allows the user receiving the incoming call (SETUP) to negotiate for the selection of the B channel. Only B channels controlled by the same D channel are considered for the selection procedure. The ISDN PRI card supports the Automatic Number Identification (ANI) on Demand feature as specified in AT&T TR41459. This feature allows the host to request the call originating number (calling party number) from networks that support Automatic Number Identification such as AT&T MultiQuest. The ISDN PRI card supports the Vari-A-Bill feature as specified in AT&T TR41459. This feature allows the host to request a change in billing for an incoming call. You can use this feature after a call has been answered and only if the SETUP message indicates that the network supports the flexible billing service. The figure below illustrates the functional modules involved in the PRI implementation on the ISDN PRI card (Figure G-5).
Layer 3 Plus (L3P)
L3P Call Control
L3P BSM
L3P DSM
CFG
Layer 3 (L3) Q.931 L3 Call Control
L3 GCR
L3 DSM
L3 BSS
MGMT L2 (Q.921)
Figure G-5 ISDN PRI Software Architecture
The ISDN PRI software architecture includes the following modules: • • • • •
Layer 3 Plus Layer 3 Layer 2 Configuration Management
G-13
ISDN
EXS ExchangePlus Software Operations Guide
Layer 3 Plus
The Layer 3 Plus (L3P) module is an interface between Layer 3 and Layer 4 Central Call Processing (CCP) on the EX/CPU (switch matrix), and Layer 5 (host). L3P formats information from Layer 3 into the programmed format for the host. It also manages application specific variants for call control. It is made up of the following PPL components: •
L3P Call Control [Component (0x05), per D channel] This component is the interface between Layer 3 and Layer 4 central call processing, which resides on the EX/CPU. This component manages which messages to send internally for call processing as well as notifying the host of various events related to the protocol.
•
L3P D Channel Control [Component (0x06), per D channel] This component manages the enabling/disabling of the D channel per terminal (for PRI ISDN there is only one terminal). It manages the sending of the Alarm message when the D channel is establishing a connection, and informs the L3P B channel control component of the availability of D channel.
•
L3P B Channel Control [Component (0x07), per B channel) This component manages the service state of the channel based upon the following: – – – –
Layer 3
The Layer 3 (L3) module provides ITU-T Q.931 implementation. The L3 state diagrams mirror the SDL diagrams of the interface specifications. It consists of the following PPL components:
Layer 2
The Layer 2 (L2) module is the ITU-T Q.921 (LAPD) implementation. It performs flow control, sequence numbering (modulo 128), retry logic, and it also guarantees message delivery.
Configuration
G-14
Host service states Layer 1 states (span framed or not) D channel availability B channel availability from the network
The Configuration (CFG) module manages all configuration of parameters and options for the ISDN protocol. This task communicates with the EX/CPU during configuration. It also verifies battery backed data and card level configuration.
EXS ExchangePlus Software Operations Guide
SNMP
H SNMP and MIB Reference SNMP The ExchangePlus SNMP agent is a software product that is based on the UCD SNMP agent. The ExchangePlus SNMP agent enables status and monitoring of the host applications and the switching units from a local or remote Simple Network Management Protocol (SNMP) management workstation. The physical link between the ExchangePlus host workstation and the SNMP manager workstation must be an Ethernet LAN. The ExchangePlus SNMP agent currently only supports SNMP version 1 (SNMPv1) as defined in the Request For Comment (RFC) 1155: Structure and Identification of Management Information for TCP/IP-based Internets and RFC 1157: Simple Network Management Protocol, and Structure Management Information (SMI) V1. MIBs are defined using an Internet-standard language called the Structure of Management Information, or SMI. SNMPv1 is one of the versions of SMI and forms the basis for all existing SNMPv1-based MIBs. It is defined in RFC 1155 and is amended in RFC 1212: Concise MIB Definitions. RFCs can be accessed on the Internet by searching for the RFC and its number. The SNMP provides alarm and status information which includes: • • • • • • MIB
Equipment alarms DSP resource status ExchangePlus equipment component status Span status SS7 signaling link status SS7 signaling congestion status
A Management Information Base (MIB) is a collection of objects on the SNMP agent that you can access through SNMP from the network node manager. Conceptually, the information on the agent is known as the MIB. The MIB is not a physically distinct database, but rather logically encompasses configuration and status values normally available on the agent system. A specific type or class of management information is called a MIB object (for example, a system description or an interface status). The existence of a particular value for a MIB object in the agent database is called an instance. Some MIB objects have only a single instance for a given agent system (for example, system description). Other MIB objects have multiple instances for a given agent system (for example, interface status for each interface on the system).
H-1
SNMP
EXS ExchangePlus Software Operations Guide
MIBs are organized into MIB modules. A MIB module is a file defining all the MIB objects under a subtree. The foundation module is the Internet standards-based MIBII module defined by RFC 1213: Management Information Base of Network Management of TCP/IP Internets: MIB-II. In addition to the Internet-standard MIBII objects defined in RFC 1213, many hardware vendors, such as Hewlett-Packard, Cisco Systems, Wellfleet, and Novell, have developed MIB extensions for their own products. The MIBs defined by these various hardware vendors are referred to as enterprise-specific MIBs. MIB Organization
Conceptually, the MIB objects are organized in a hierarchical tree structure. Each branch in the tree has a unique name and numeric identifier (see the following figures). Intermediate branches of the tree serve as a way to group related MIB objects together. The leaves of the tree represent the actual MIB object. A subtree is used to refer to the entire group of branches and leaves under a particular intermediate branch. ExchangePlus uses the Internet MIB-II standard to define the common objects for managing TCP/IP networks. Figure H-1 illustrates the tree structure for the Enterprise branch.
iso(1) org(3) dod(6) internet(1)
directory(1)
management(2)
experimental(3)
mib-2(1)
Proteon(1)
private(4) enterprise(1)
InterCall(3959)
Comm Inc.(n)
Figure H-1 The Enterprise Branch - Object Identifier Hierarchy
A MIB object is uniquely identified (named) by its place in the tree. A full object identifier consists of the identifier of each branch along the path through the tree hierarchy, from the top of the tree (iso) down to the leaf (for example, InterCall). The object identifier is expressed in dot notation, by separating each branch identifier along the path with a period.
H-2
EXS ExchangePlus Software Operations Guide
SNMP
For example, the mib-2 subtree name is iso.org.dod.internet.mgmt.mib-2 and its numeric identifier is 1.3.6.1.2.1 As another example, the full MIB object identifier for InterCall is iso.org.dod.internet.private.enterprise.InterCall and its numeric identifier is 1.3.6.1.4.1.3959 These MIB object notations follow the standard notation defined in Abstract Syntax Notation One (ASN.1); the ASN.1 standard notation definition can be considered the template for MIBs. To avoid conflicts of object identifiers, each branch of the tree must be registered (that is, defined), through a designated organization. The Internet Activities Board (IAB) has authority over the Internet subtree, which includes the MIB-II Internet standard registered under the MIB subtree. MIB Access
ExchangePlus MIB
The network node manager accesses the SNMP agent’s MIB object instances using SNMP’s Get and Set operations. See “Chapter 12. SNMP and Alarm Monitoring” on page 12-1 for more information on accessing MIB’s. Figure H-2 illustrates the high level tree structure for the ExchangePlus MIB.
InterCall(3959)
iccGeneric(1)
iccProduct(2)
iccExperimental(3)
isos(1)
isosNumOfNodes(1)
isosNodeTable(2)
isosSoftware(3)
Figure H-2 The InterCall Object Identifier Hierarchy for ExchangePlus
Table H-1 describes Figure H-2 the ExchangePlus Object Identifier Hierarchy.
H-3
SNMP
EXS ExchangePlus Software Operations Guide
Table H-1. ExchangePlus Object Identifier Description Object Identifier Name
Description
isosNumOfNodes(1)
The number of nodes in EXNET.
isosNodeTable(2)
Contains a row for each node in the EXNET managed by this agent.
isosSoftware(3)
A high level heading for the ExchangePlus software.
Figure H-3 illustrates the tree structure for the isosNodeTable object.
isos(1)
isosNumOfNodes(1)
isosNodeTable(2)
isosSoftware(3)
isosNodeEntry(1)
isosNodeNum(1)
isosNodeLogicalID(2)
isosNodePhysicalID(3)
isosNodeType(4)
Figure H-3 isosNode Table Hierarchy
Table H-2 describes Figure H-3 the isosNodeTable Object Identifier Hierarchy. Table H-2. isosNodeTable Object Identifier Description Object Identifier Name
H-4
Description
isosNodeEntry(1)
Node entry.
isosNodeNum(1)
Node number.
isosNodeLogicalID(2)
Logical ID of the Node.
isosNodePhysicalID(3)
Physical ID of the Node.
isosNodeType(4)
Node Type.
EXS ExchangePlus Software Operations Guide
SNMP
Figure H-4 illustrates the tree branches for the isosSoftware object.
isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
Figure H-4 isosSoftware Object Identifier Hierarchy
Table H-3 describes Figure H-4 the isosSoftware Object Identifier Hierarchy. Table H-3. isosSoftware Object Identifier Description Object Identifier Name
Description
isosHostSoftwareTable(1)
Contains a row for each host software in the EXNET managed by this agent.
isosSlot(2)
Slot number of the switch.
isosSpan(3)
Span number of the switch.
isosChannel(4)
Channel number of the switch.
isosSystemAlarm(5)
System Alarm.
Under the isosSoftware branch, there are a number of additional branches that are illustrated and described below.
H-5
SNMP
EXS ExchangePlus Software Operations Guide
Figure H-5 illustrates the tree branches for the isosHostSoftwareTable object.
isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
isosHostSoftwareEntry(1)
isosNodeNum(1)
isosHostVersion(2)
isosHostStartup(3)
Figure H-5 isosHostSoftwareTable Hierarchy
Table H-4 describes Figure H-5 the isosHostSoftwareTable Object Identifier Hierarchy. This table contains a row for each host software in the EXNET managed by this agent. Table H-4. isosHostSoftwareTable Object Identifier Description Object Identifier Name
H-6
Description
isosHostSoftwareTable(1)
Host Software Table heading.
isosHostSoftwareEntry(1)
Host Software Entry heading.
isosNodeNum(1)
Indicates the node number in EXNET.
isosHostVersion(2)
The ISOS host version number.
isosHostStartup(3)
When set, this object triggers a Start or Stop of ExchangePlus software. (1=Start, 2=Stop)
EXS ExchangePlus Software Operations Guide
SNMP
Figure H-6 illustrates the tree branches for the isosSlot object. isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
isosSlotTable(1) isosSlotEntry(1)
isosNodeNum(1)
isosExcelSlot(2)
isosExcelCardType(3)
isosExcelStatus(4)
isosExcelTestResults(5)
isosExcelArtworkRev(6)
isosExcelFunctionalRev(7)
isosExcelRomMajRev(8)
isosExcelRomMinRev(9)
isosExcelRamMajRev(10)
isosExcelRamMinRev(11)
isosExcelSerialNum(12)
isosExcelRamSize(13)
isosExcelCardInfo(14)
isosExcelHardwareConfig(15)
isosExcelBoardID(16)
isosExcelRamBuildNum(17)
isosExcelConfigTag(18)
isosExcelAlarm(19)
Figure H-6 isosSlot Hierarchy
H-7
SNMP
EXS ExchangePlus Software Operations Guide
Table H-5 describes Figure H-6 the isosSlot Object Identifier Hierarchy. This table contains a row for each slot in the EXNET managed by this agent. Table H-5. isosSlot Object Identifier Description Object Identifier Name
H-8
Description
isosSlot(2)
Slot heading.
isosSlotTable(1)
Slot table heading.
isosSlotEntry(1)
Contains a row for each slot in the EXNET managed by this agent.
isosNodeNum(1)
Indicates the node number in EXNET.
isosExcelSlot(2)
Indicates the slot number 16 slots.
isosExcelCardType(3)
Indicates the card type.
isosExcelStatus(4)
Indicates the card status.
isosExcelTestResults(5)
Indicates the test result.
isosExcelArtworkRev(6)
This field has an ASCII character in the range ’A’ to ’Z’ (0x41-0x5B) which indicates the revision level of the cards printed circuit artwork.
isosExcelFunctionalRev(7)
Indicates the cards functional revision level.
isosExcelRomMajRev(8)
An ASCII string that represents the ROM major revision number of the card.
isosExcelRomMinRev(9)
An ASCII string that represents the ROM minor revision number of the card.
isosExcelRamMajRev(10)
An ASCII string that represents the RAM major revision number of the card.
isosExcelRamMinRev(11)
An ASCII string that represents the RAM minor revision number of the card.
isosExcelSerialNum(12)
Contains the serial number of the card.
isosExcelRamSize(13)
Indicates the amount of RAM that is on the card. The RAM is measured in 1K increments.
isosExcelCardInfo(14)
Indicates the Card Info.
isosExcelHardwareConfig(15)
Indicates the hardware configuration.
isosExcelBoardID(16)
Indicates the board ID.
isosExcelRamBuildNum(17)
Contains the RAM build number of the card.
isosExcelConfigTag(18)
Indicates the configuration tag.
isosExcelAlarm(19)
Indicates the alarm.
EXS ExchangePlus Software Operations Guide
SNMP
Figure H-7 illustrates the tree branches for the isosSpan object.
isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
isosSpanStatusTable(1) isosSpanStatusEntry(1)
isosSpanLogicalID(1)
isosSpanType(2)
isosSpanStatus(3)
Figure H-7 isosSpan Hierarchy
Table H-6 describes Figure H-7 the isosSpan Object Identifier Hierarchy. This table contains a row for each span in the EXNET managed by this agent. Table H-6. isosSpan Object Identifier Description Object Identifier Name
Description
isosSpan(3)
Span heading.
isosSpanStatusTable(1)
Span status table heading.
isosSpanStatusEntry(1)
Contains a row for each span in the EXNET managed by this agent.
isosSpanLogicalId(1)
Indicates the logical span ID (80 Max. per chassis). When this object returns 0 that span is unassigned, except for the very first span
isosSpanType(2)
Indicates the span type. (1=T1, 2=E1)
isosSpanStatus(3)
Indicates the span status. (1=Activated, 2=DeActivated)
H-9
SNMP
EXS ExchangePlus Software Operations Guide
Figure H-8 illustrates the tree branches for the isosChannel object.
isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
isosChannelStatusTable(1) isosChannelStatusEntry(1)
isosChannelNumber(1)
isosChannelStatus(2)
Figure H-8 isosChannel Hierarchy
Table H-7 describes Figure H-8 the isosChannel Object Identifier Hierarchy. This table contains a row for each channel in the EXNET managed by this agent. Table H-7. isosChannel Object Identifier Description Object Identifier Name
H-10
Description
isosChannel(4)
Channel heading.
isosChannelStatusTable(1)
Channel status table heading.
isosChannelStatusEntry(1)
Contains a row for each channel in the EXNET managed by this agent.
isosChannelNumber(1)
Indicates the channel number (2048 Max. per chassis).
isosChannelStatus(2)
Indicates the channel status.
EXS ExchangePlus Software Operations Guide
SNMP
Figure H-9 illustrates the tree branches for the isosSystemAlarm object. See also Appendix I, “Traps Reference” for more information.
isos(1)
isosSoftware(3)
isosHostSoftwareTable(1)
isosSlot(2)
isosSpan(3)
isosChannel(4)
isosSystemAlarm(5)
isosLastSysAlarmTrap(1) isosLastSysAlarmSeverity(2)
isosLastSysAlarmNodeNum(3)
isosLastSysAlarmSlotNum(4)
isosLastSysAlarmCardType(5) isosLastSysAlarmSpanNum(6) isosLastSysAlarmChannelNum(7) isosLastSysAlarmDspNum(8) isosLastSysAlarmSimmNum(9) isosLastSysAlarmTime(10) isosLastSysAlarmAibType(11)
isosLastSysAlarmPPLEvent(12)
isosLastSysAlarmComponentNum(13)
isosLastSysAlarmTrunkNum(14) isosLastSysAlarmSS7StackID(15)
isosLastSysAlarmSS7Direction(16)
isosLastSysAlarmSS7Status(17)
Figure H-9 isosSystemAlarm Hierarchy
Refer to Appendix I, “Traps Reference” to describe the objects in Figure H-9.
H-11
SNMP
H-12
EXS ExchangePlus Software Operations Guide
EXS ExchangePlus Software Operations Guide
ExchangePlus Traps
I Traps Reference ExchangePlus Traps This section describes the ExchangePlus MIB enterprise specific traps and Excel Switch traps. All Request For Comments (RFC) references can be found on the internet by searching for the RFC and its number.
Generic Traps
According to RFC 1215: A Convention for Defining Traps for use with the SNMP, there are six (6) generic traps that are used with SNMP. It is a convention that a coldStart trap is sent when an agent reinitializes itself such that the agentâ&#x20AC;&#x2122;s configuration may be altered. Further, an agent will send a warmStart trap to signify that the agent is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered.
ExchangePlus Specific Traps
According to RFC 1215: A Convention for Defining Traps for use with the SNMP, enterprise MIBs may define enterprise specific traps. In ExchangePlus, there are individual traps for each type of Lucent Technologies alarm. Use Table I-1 and Table I-2 to explain the ExchangePlus Alarm Specific Traps.
I-1
ExchangePlus Traps
EXS ExchangePlus Software Operations Guide
Table I-1. ExchangePlus Alarm Specific Traps Return Variable ID Number
I-2
Variable Name
Description
1
isosLastSysAlarmTrap
The last trap that has been sent by this agent.
2
isosLastSysAlarmSeverity
If ISOS alarm occurred and a trap was sent, then this object indicates the severity.
3
isosLastSysAlarmNodeNum
The physical node ID of the last node to encounter an alarm condition.
4
isosLastSysAlarmSlotNum
Indicates the slot number 16 slots.
5
isosLastSysAlarmCardType
Indicates the card type.
6
isosLastSysAlarmSpanNum
The span number of the last span to encounter an alarm condition.
7
isosLastSysAlarmChannelNum
The channel number of the last channel to encounter an alarm condition.
8
isosLastSysAlarmDspNum
The DSP number of the last DSP to encounter an alarm condition.
9
isosLastSysAlarmSimmNum
The SIMM number of the last SIMM to encounter an alarm condition.
10
isosLastSysAlarmTime
The time of last alarm condition. Seconds since Jan. 1, 1970.
11
isosLastSysAlarmAibType
The AIB type of last alarm condition. If applicable.
12
isosLastSysAlarmPPLEvent
The PPL event number of last alarm condition. If applicable.
13
isosLastSysAlarmComponentNum
The component number of last alarm condition. If applicable.
14
isosLastSysAlarmTrunkNum
The component number of last alarm condition. If applicable.
15
isosLastSysAlarmSS7StackId
The stack ID of the last SS7 signaling network congestion alarm.
16
isosLastSysAlarmSS7Direction
The direction of the last SS7 signaling stack congestion alarm.
17
isosLastSysAlarmSS7Status
The SS7 status of the last SS7 signaling stack congestion alarm.
EXS ExchangePlus Software Operations Guide
Switch Traps
ExchangePlus Traps
Table I-2 describes the Excel Switch Traps. NOTE: * The Additional Return Variables ID number used below applies to the â&#x20AC;&#x2122;Return Variable ID Numberâ&#x20AC;&#x2122; column of Table I-1. Table I-2. Switch Traps
Trap ID
Trap Name
Description
Severity
Additional Return Variables ID Number*
1
generalSystemBusyCondition
The switch sends this message when the matrix EX/CPU is flooded with messages. The switch will ignore all incoming calls until the alarm is cleared.
Critical
2, 3
2
generalClockModeSwitched
Lets the host know that the clock mode was automatically switched.
Critical
2, 3
3
generalInvalidDSPFunction
Older alarm that is no longer supported.
Informative
2, 3
4
generalRefClock1Lost
The switch will automatically switch the clock mode to the next available clock source.
Major
2, 3
5
generalRefClock2Lost
The switch will automatically switch the clock mode to the next available clock source.
Major
2, 3
6
generalDSPResourceBlocked
DSP resource block occurred.
Minor
2, 3
7
generalDSPFunctionNotConfigured
DSP resource function type not configured.
Informative
2, 3
8
generalDSPManagementInconsistent
DSP resource management inconsistent.
Minor
2, 3
9
generalDownloadRecordTimeout
Download Record Timeout
Minor
2, 3
10
generalPartialMessageAlarm
Partial Message Received (for example, incorrect checksum, zero length message, or message not starting with frame character, and so on).
Minor
2, 3
11
generalNoAnnouncement
Recorded announcement requested is no longer available in the system.
Minor
2, 3
12
generalUnacknowledgedMessage
Unacknowledged message.
Minor
2, 3
13
generalInconsistentAnnouncement
Recorded announcement ID inconsistency.
Minor
2, 3
14
generalSS7NetworkCongestion
SS7 signaling network congestion.
Critical
2, 3
I-3
ExchangePlus Traps
Trap ID
EXS ExchangePlus Software Operations Guide
Trap Name
Description
Severity
Additional Return Variables ID Number*
15
generalSS7RemoteISUPUnavailable
SS7 remote ISUP unavailable.
Minor
2, 3
16
generalNodeIdExists
Node ID already exists.
Major
2, 3
17
generalInvalidMsgLength
Invalid message length.
Minor
2, 3
18
generalSystemBusyWarning
System busy warning.
Critical
2, 3
19
generalResourceThresholdReached
Resource utilization threshold reached.
Critical
2, 3
20
generalSS7StackCongestion
SS7 signaling stack congestion.
Minor
2, 3
41
cardTakenOutOfService
Card taken out of service.
Major
2, 3, 4, 5
42
cardTypeNotSupported
Card type not supported.
Minor
2, 3, 4, 5
43
cardDownloadCorrupt
Card download is corrupt.
Major
2, 3, 4, 5
44
cardTypeNotRecognized
Card type not recognized.
Minor
2, 3, 4, 5
45
cardConfigurationResetToDefault
Cards configuration has been reset to defaults.
Major
2, 3, 4, 5
46
cardReset
Card reset.
Major
2, 3, 4, 5
47
cardConnectionMapFailure
Connection map failure.
Minor
2, 3, 4, 5
48
cardNoDownload
Software does not have download for card.
Minor
2, 3, 4, 5
49
cardALawNotSupported
Card does not support A-law encoding format.
Minor
2, 3, 4, 5
50
cardRevisionNotSupported
Card revision not supported by system software revision.
Minor
2, 3, 4, 5
51
cardBoardRemoved
Card removed.
Critical
2, 3, 4, 5
52
cardHardwareFailure
Hardware failure occurred on slot specified.
Critical
2, 3, 4, 5
53
cardHostLinkError
Ethernet host link error detected.
Critical
2, 3, 4, 5
54
cardNoFanTray
No fan tray installed.
Critical
2, 3, 4, 5
55
cardExnetPortACommFailure
EXNET Port A – communication failure.
Critical
2, 3, 4, 5
56
cardExnetPortBCommFailure
EXNET Port B – communication failure.
Critical
2, 3, 4, 5
57
cardExnetPortALaserFailure
EXNET Port A – fiber laser failure.
Critical
2, 3, 4, 5
58
cardExnetPortBLaserFailure
EXNET Port B – fiber laser failure.
Critical
2, 3, 4, 5
I-4
EXS ExchangePlus Software Operations Guide
Trap ID
Trap Name
ExchangePlus Traps
Description
Severity
Additional Return Variables ID Number*
71
spanDead
Carrier Group Alarm (CGA) or span dead.
Major
2, 3, 6
72
spanExcessiveSlips
Excessive burst of slips.
Major
2, 3, 6
73
spanJ1Failure
J1-specific failure.
Major
2, 3, 6
74
spanLogicalSpanIDExists
Logical span ID already exists on another node.
Minor
2, 3, 6
81
channelISDNDchannel
ISDN D-Channel establishing.
Minor
2, 3, 6, 7
82
channelPPLError
PPL state machine error.
Minor
2, 3, 6, 7
91
simmTakenOutOfService
DSP SIMM taken out of service.
Major
2, 3, 4, 9
92
simmVRASEraseComplete
VRAS erase complete.
Minor
2, 3, 4, 9
93
simmAnnouncementDownload Inconsistency
Recorded announcement download inconsistency.
Minor
2, 3, 4, 9
94
simmAnnouncementIDInconsistency
Recorded announcement ID inconsistency.
Minor
2, 3, 4, 9
95
simmAnnouncementDownloadReady-
Recorded announcement download ready.
Informative
2, 3, 4, 9
101
dspTakenOutOfService
DSP board taken out of service.
Major
2, 3, 4, 8, 9
111
exsNodeNotUsingEXAPI
The node is not using the Extended Application Programming Interface.
Minor
2, 3
112
exsNodeTimeslotCountChanged
Available EXS conferencing timeslot count changed.
Minor
2, 3
201
alarmClearedGeneralSystemBusyCondition
The switch sends this message when the matrix EX/CPU is flooded with messages. The switch will ignore all incoming calls until the alarm is cleared.
Critical
2, 3
202
alarmClearedGeneralClockModeSwitched
Lets the host know that the clock mode was automatically switched.
Critical
2, 3
203
alarmClearedGeneralInvalidDSPFunction
Older alarm that is no longer supported.
Informative
2, 3
204
alarmClearedGeneralRefClock1Lost
The switch will automatically switch the clock mode to the next available clock source.
Major
2, 3
205
alarmClearedGeneralRefClock2Lost
The switch will automatically switch the clock mode to the next available clock source.
Major
2, 3
I-5
ExchangePlus Traps
Trap ID
EXS ExchangePlus Software Operations Guide
Trap Name
206
alarmClearedGeneralDSPResourceBlocked
207
Description
Minor
2, 3
alarmClearedGeneralDSPFunctionNotConfigur DSP resource function type not ed configured.
Informative
2, 3
208
alarmClearedGeneralDSPManagementInconsis tent
DSP resource management inconsistent.
Minor
2, 3
209
alarmClearedGeneralDownloadRecordTimeout
Download record timeout.
Minor
2, 3
210
alarmClearedGeneralPartialMessageAlarm
Partial Message Received (for example, incorrect checksum, zero length message, or message not starting with frame character, and so on).
Minor
2, 3
211
alarmClearedGeneralNoAnnouncement
Recorded announcement requested is no longer available in the system.
Minor
2, 3
212
alarmClearedGeneralUnacknowledgedMessage Unacknowledged message.
Minor
2, 3
213
alarmClearedGeneralInconsistentAnnounceme nt
Recorded announcement ID inconsistency.
Minor
2, 3
214
alarmClearedGeneralSS7NetworkCongestion
SS7 signaling network congestion.
Critical
2, 3
215
alarmClearedGeneralSS7StackUnaccessible
SS7 remote ISUP unavailable.
Minor
2, 3
216
alarmClearedGeneralNodeIdExists
Node ID already exists.
Major
2, 3
217
alarmClearedGeneralInvalidMsgLength
Invalid message length.
Minor
2, 3
218
alarmClearedGeneralSystemBusyWarning
System busy warning.
Critical
2, 3
219
alarmClearedGeneralResourceThresholdReach ed
Resource utilization threshold reached.
Critical
2, 3
220
alarmClearedGeneralSS7StackCongestion
SS7 signaling stack congestion.
Minor
2, 3, 15, 16, 17
241
alarmClearedCardTakenOutOfService
Card taken out of service.
Major
2, 3, 4, 5
242
alarmClearedCardTypeNotSupported
Card type not supported.
Minor
2, 3, 4, 5
243
alarmClearedCardDownloadCorrupt
Card download is corrupt.
Major
2, 3, 4, 5
244
alarmClearedCardTypeNotRecognized
Card type not recognized.
Minor
2, 3, 4, 5
245
alarmClearedCardConfigurationResetToDefaul t
Cardâ&#x20AC;&#x2122;s configuration has been reset to defaults.
Major
2, 3, 4, 5
246
alarmClearedCardReset
Card reset.
Major
2, 3, 4, 5
247
alarmClearedCardConnectionMapFailure
Connection map failure.
Minor
2, 3, 4, 5
I-6
DSP resource block occurred.
Severity
Additional Return Variables ID Number*
EXS ExchangePlus Software Operations Guide
Trap ID
Trap Name
ExchangePlus Traps
Description
Severity
Additional Return Variables ID Number*
248
alarmClearedCardNoDownload
Software does not have download for card.
Minor
2, 3, 4, 5
249
alarmClearedCardALawNotSupported
Card does not support A-law encoding format.
Minor
2, 3, 4, 5
250
alarmClearedCardRevisionNotSupported
Card revision not supported by system software revision.
Minor
2, 3, 4, 5
251
alarmClearedCardBoardRemoved
Card removed.
Critical
2, 3, 4, 5
252
alarmClearedCardHardwareFailure
Hardware failure occurred on slot specified.
Critical
2, 3, 4, 5
253
alarmClearedCardHostLinkError
Ethernet host link error detected.
Critical
2, 3, 4, 5
254
alarmClearedCardNoFanTray
No fan tray installed.
Critical
2, 3, 4, 5
255
alarmClearedCardExnetPortACommFailure
EXNET port A – Communication Failure.
Critical
2, 3, 4, 5
256
alarmClearedCardExnetPortBCommFailure
EXNET port B – Communication Failure.
Critical
2, 3, 4, 5
257
alarmClearedCardExnetPortALaserFailure
EXNET port A – Fiber Laser Failure. Critical
2, 3, 4, 5
258
alarmClearedCardExnetPortBLaserFailure
EXNET port B – Fiber Laser Failure.
Critical
2, 3, 4, 5
271
alarmClearedSpanDead
Carrier group alarm (CGA) or span dead.
Major
2, 3, 6
272
alarmClearedSpanExcessiveSlips
Excessive burst of slips.
Major
2, 3, 6
273
alarmClearedSpanJ1Failure
J1 span specific failure.
Major
2, 3, 6
274
alarmClearedSpanLogicalSpanIDExists
Logical span ID already exists on another node.
Minor
2, 3, 6
281
alarmClearedChannelISDNDchannel
ISDN D-channel establishing.
Minor
2, 3, 6, 7
282
alarmClearedChannelPPLError
PPL state machine error.
Minor
2, 3, 6, 7
291
alarmClearedSimmTakenOutOfService
DSP SIMM taken out of service.
Major
2, 3, 4, 9
292
alarmClearedSimmVRASEraseComplete
VRAS erase complete.
Minor
2, 3, 4, 9
293
alarmClearedSimmAnnouncementDownloadIn consistency
Recorded announcement download inconsistency.
Minor
2, 3, 4, 9
294
alarmClearedSimmAnnouncementIDInconsiste ncy
Recorded announcement ID inconsistency.
Minor
2, 3, 4, 9
295
alarmClearedSimmAnnouncementDownloadR eady
Recorded announcement download ready.
Informative
2, 3, 4, 9
I-7
ExchangePlus Traps
Trap ID
EXS ExchangePlus Software Operations Guide
Trap Name
Description
Severity
Additional Return Variables ID Number*
301
alarmClearedDspTakenOutOfService
DSP board taken out of service.
Major
2, 3, 4, 8, 9
311
alarmClearedExsNodeNotUsingEXAPI
Node not using the Extended Application Programming Interface.
Minor
2, 3
312
alarmClearedExsNodeTimeslotCountChanged
Available EXS conferencing timeslot count changed.
Minor
2, 3
401
ss7PPLInvalidAibType
PPL, unrecognized AIB type in PPL event handler.
Informative
2, 3, 11
402
ss7PPLDspResourceAllocationFailure
DSP resource allocation failure.
Major
2, 3, 6, 7
403
ss7PPLRemoteInhibitConfirmation
PPL, remote inhibit confirmation.
Informative
2, 3, 6, 7
404
ss7PPLRemoteUninhibitConfirmation
PPL, remote uninhibit confirmation.
Informative
2, 3, 6, 7
405
ss7PPLLocalInhibitDenied
PPL, local inhibit denied.
Minor
2, 3, 6, 7
406
ss7PPLLocalInhibitTimeOut
PPL, local inhibit timeout.
Minor
2, 3, 6, 7
407
ss7PPLLocalInhibitConfirmation
PPL, local inhibit confirmation.
Informative
2, 3, 6, 7
408
ss7PPLLocalUninhibitConfirmation
PPL, local uninhibit confirmation.
Informative
2, 3, 6, 7
409
ss7PPLLocalUninhibitNotPossible
PPL, local uninhibit not possible.
Minor
2, 3, 6, 7
410
ss7PPLLocalUninhibitTimeout
PPL, local uninhibit time-out.
Minor
2, 3, 6, 7
411
ss7PPLLinkInService
PPL, link in service.
Informative
2, 3, 6, 7
412
ss7PPLL1Dead
PPL, link out of service (L1_DEAD). Major
2, 3, 6, 7
413
ss7PPLL5OutOfService
PPL, link out of service (L5_OOS).
Major
2, 3, 6, 7
414
ss7PPLUnknownEvent
Unknown PPL event.
Informative
2, 3, 6, 7, 12
415
ss7PPLIncomingContinuityFailure
PPL, incoming continuity failure.
Minor
2, 3, 6, 7
416
ss7PPLT8Expiration
PPL, T8 expiration.
Minor
2, 3, 6, 7
417
ss7PPLRlcT5Expiration
PPL, RLC T5 expiration.
Minor
2, 3, 6, 7
418
ss7PPLOutgoingContinuityFailure
PPL, outgoing continuity check failed.
Minor
2, 3, 6, 7
419
ss7PPLIncomingContinuityCheckFailure
PPL, incoming continuity check failed.
Minor
2, 3, 6, 7
420
ss7PPLFirstExpirationOfISUPT17
PPL, first expiration of ISUP T17.
Minor
2, 3, 6, 7
421
ss7PPLFirstExpirationOfT23Timer
PPL, first expiration of T23 Timer.
Minor
2, 3, 6, 7
422
ss7PPLNoCGRRFromL3P
PPL, no group response received from L3P after 15 seconds.
Minor
2, 3, 6, 7
I-8
EXS ExchangePlus Software Operations Guide
Trap ID
Trap Name
ExchangePlus Traps
Description
Severity
Additional Return Variables ID Number*
423
ss7PPLExpirationOfT19Timer
PPL, expiration of T19 timer.
Minor
2, 3, 6, 7
424
ss7PPLExpirationOfT21Timer
PPL, expiration of T21 timer.
Minor
2, 3, 6, 7
425
ss7PPLRangeAndStatusBitMaskError
PPL, CGBA or CGUA range and status parameter bit mask error.
Major
2, 3, 6, 7
426
ss7PPLLinkActivationFailed
PPL, link activation failed.
Major
2, 3, 6, 7
427
ss7PPLLinkFailure
PPL, link failure.
Major
2, 3, 6, 7
428
ss7PPLSignalingLinkFailure
PPL, signaling link test failure.
Minor
2, 3, 6, 7
429
ss7PPLT36Expiry
PPL, T36 expiry on continuity recheck.
Minor
2, 3, 6, 7
430
ss7PPLCOTFailure
PPL, COT failure ind.(dual seizure), process network IAM.
Informative
2, 3, 6, 7
431
ss7PPLT5Expiry
PPL, T5 expiry in wait for RLC state. Minor
2, 3, 6, 7
432
ss7PPLCPCNotIdle
PPL, CPC not IDLE ind
Minor
2, 3, 6, 7
433
ss7PPL1stContinuityRecheckFailed
PPL, first continuity recheck attempt failed.
Minor
2, 3, 6, 7
434
ss7PPLContinuityRecheckFailed
PPL, continuity recheck attempt failed.
Minor
2, 3, 6, 7
435
ss7PPLUnhandledComponent
PPL, unhandled component.
Informative
2, 3, 6, 7, 13
436
ss7PPLTUPProtocolViolation
PPL, TUP protocol violation for trunk.
Major
2, 3, 14
437
ss7PPLCOTReceived
PPL, COT received.
Informative
2, 3, 6, 7
438
ss7PPLCCFReceived
PPL, CCF receive.
Informative
2, 3, 6, 7
439
ss7PPLRcvFailedCLF
PPL, fail to receive CLF.
Minor
2, 3, 6, 7
440
ss7PPLRcvT5Expiration
PPL, T5 expiration received.
Minor
2, 3, 6, 7
441
ss7PPLRcvT7Expiration
PPL, T7 expiration received.
Minor
2, 3, 6, 7
442
ss7PPLRcvIncomingIAM
PPL, continuity in incoming IAM received.
Informative
2, 3, 6, 7
443
ss7PPLRcvUnknownTUPMsg
PPL, unknown TUP message type received.
Minor
2, 3, 6, 7
444
ss7PPLInvalidTUPMsgFormat
PPL, bad message in TUP message format.
Major
2, 3, 6, 7
445
ss7PPLUnassignedTUPCIC
PPL, unassigned TUP CIC.
Minor
2, 3, 6, 7
I-9
ExchangePlus Traps
Trap ID
EXS ExchangePlus Software Operations Guide
Trap Name
Description
Severity
Additional Return Variables ID Number*
446
ss7PPLRcvCLFFirstTime
PPL, received CLF first time.
Informative
2, 3, 6, 7
447
ss7PPLRcvCCFFirstTime
PPL, received CCF first time.
Informative
2, 3, 6, 7
448
ss7PPLReceivedCCF
PPL, received CCF.
Informative
2, 3, 6, 7
449
ss7PPLComponentFirstT19Expire
PPL, first T19 expired component.
Minor
2, 3, 6, 7, 13
450
ss7PPLRcvUCICStopReq
PPL, UCIC stop request received.
Minor
2, 3, 6, 7
451
ss7PPLIncorrectCGSMsg
PPL, incorrect circuit group supervision message type indicator.
Minor
2, 3, 6, 7
452
ss7PPLT28ExpiryRcvCQR
PPL, T28 expiry receiving CQR.
Minor
2, 3, 6, 7
501
ss7SPRCFormatError
PPL, SPRC: format error in incoming message.
Major
2, 3
502
ss7SPRCUndefinedCIC
PPL, SPRC: undefined CIC in incoming message.
Minor
2, 3
503
ss7SPRCUndefinedMessage
PPL, SPRC: undefined incoming message.
Minor
2, 3
504
ss7SPRCRcvConfusionMessage
PPL, SPRC: confusion message received.
Major
2, 3
505
ss7SPRCUndefinedEvent
PPL, undefined SPRC event.
Informative
2, 3, 12
506
ss7TUPSPRCUnknownMsgType
PPL, TUP SPRC: unknown TUP msg type.
Major
2, 3
507
ss7TUPSPRCBadMsgFormat
PPL, TUP SPRC: bad TUP msg format.
Major
2, 3
508
ss7TUPSPRCUnassignedCIC
PPL, TUP SPRC: unassigned CIC.
Minor
2, 3
509
ss7TUPSPRCIllegalPPLType
PPL, TUP SPRC: illegal span and channel specified in PPL type.
Major
2, 3, 6, 7, 12, 13
551
reduSwitchingSides
Redundancy MASTER, parent is not responding! switching sides. Exiting.
Major
2
552
reduMasterTransComplete
Redundancy CHKMASTER, communication with switch confirmed. Master transition complete.
Major
2
553
reduTransitioningToMaster
Redundancy STANDBY, Matrix comm confirmed transitioning to master â&#x20AC;&#x201C; adjacent dead.
Major
2
554
reduAdjHostDown
Redundancy STANDBY, standby connection disconnect detected.
Critical
2
I-10
EXS ExchangePlus Software Operations Guide
Overview
J Alarm Panel Switch Alarms Overview This appendix provides a description of the ExchangePlus alarm panel and the switch alarms. For more hardware information see the EXS ExchangePlus Hardware Product Description Manual.
Introduction
The primary purpose of the alarm panel is to alert operations personnel when the ExchangePlus is experiencing an issue which may require human intervention. The ExchangePlus subsystem is integrated with the switch management and traffic management software and will provide alarms in a wide variety of situations. These alarms may trigger LEDs, audible alarms or paging depending on the severity of the alarm and the configuration of the system. The host application software inputs alarm and status from both the switch and the alarm panel. Upon change of alarm status the host application software correlates the alarm message with the table provided later in this appendix. The host application then sends messaging to the alarm panel to activate LEDs, an audible alarm, and paging. The host also provides real time messaging indicating that an alarm has occurred. The host application maintains the status of all alarms present and has the capability to handle multiple simultaneous alarms. The host application provides the means to “clear” alarms by sending a clear command. This command will change the informational LEDs from flashing yellow to flashing green. The host application also provides a means for resetting all alarm indicators present on the server alarm panel and the client alarm panel(s). A reset is defined as turning off all red/yellow alarm LEDs, turning on the “all normal” green LEDs, and muting the buzzer.
Alarm Classifications
Critical Alarm
The requirements for the alarm subsystem are described below. The severity of the alarmed trouble notification shall be indicated by designating an alarm as critical, major, minor and informational. Critical problems severely affect service, traffic, billing and maintenance capabilities. These require immediate corrective action, regardless of time of day or day of week. Therefore, an immediate and clear indication of the alarm must be made to maintenance systems and personnel. If the snmpd.conf file is configured to enable paging on critical alarms, the system will initiate a numeric page when a critical alarm is generated.
J-1
Overview
EXS ExchangePlus Software Operations Guide
Critical problems are those that affect service and/or system operation, billing, maintenance or database function. This list includes: 1. A total system outage that results in a loss of all transaction processing capability. 2. Reduction in capacity or traffic handling capability such that the system cannot handle expected loads. 3. Any loss of safety or emergency capability (e.g. 911 calls). 4. Loss of system’s ability to perform automatic system reconfiguration. 5. Inability to restart a processor or the system. 6. Partial system outage (GR-929-CORE defines this as the loss of “64 terminations,” whereas GR-474-CORE defines a significant outage as the loss of 1% of the network terminations or 128 network terminations whichever is larger). 7. Loss of billing capability. 8. Corruption of billing or system databases that requires service affecting corrective action. 9. Loss or access for maintenance or recovery operations. 10. Loss of the systems ability to provide any required critical or major trouble indications. Major Alarm
Major alarms are used for hardware or software conditions that indicate a serious disruption of service or the malfunctioning or failure of important circuits. These troubles require immediate attention and response of maintenance personnel to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance.
Minor Alarm
Minor alarms are used for troubles that do not have a serious effect on service to customers or for troubles in circuits that are not essential to system operation. Minor alarms may trigger a LED.
Informational Alarm
J-2
In addition to the three severity levels of critical, major and minor there exist 13 informational alarm categories to indicate the type of alarm that is generated. Each alarm shall have exactly one severity and 1 informational message. These two messages shall be sent to the alarm panel for triggering the correct LEDs, buzzer tones, and possibly paging. Informational alarms are displayed on the host computer’s display and are logged in the system.log file located in the directory of /usr/isos/log.
EXS ExchangePlus Software Operations Guide
Overview
Alarm Indications EXS-LE Cabinet Visual Indications
LED Pairs
Alarms are displayed within the EXS-LE cabinet and on the alarm panel. Critical and major alarms are indicated with flashing red LEDs on the top row visible from the front of the alarm panel. Minor alarm and informational alarm indications are flashing yellow or amber LEDs on the top row. The software clear alarm state is indicated by a flashing green LED on the bottom row. The no alarm state (normal state) for all alarms are shown with a steady on green LED on the bottom row of all the indicators. The LED pair (critical and informational) determines the alarm panel messaging. System functional indicators correspond to the LED pairs for the server alarm panel and the client alarm panel(s). The colors below are listed as alarm state/normal state i.e., Red/Green. EMAC-XL-2 Alarm Panel
CRITICAL - Red/Green MAJOR – Red/Green MINOR – Yellow /Green POWER – Yellow /Green SYNC – Yellow /Green CARD – Yellow /Green CIRCUIT – Yellow /Green EXNET – Yellow /Green SYS RESOURCE – Yellow /Green REDUNDANCY – Yellow /Green COMM – Yellow /Green HOST – Yellow /Green MAINT – Yellow /Green FAN/TEMP – Yellow /Green DOOR – Yellow/Green EXT – Yellow/Green
J-3
Overview
EXS ExchangePlus Software Operations Guide
Audible Indications
General Message Notification
Remote Indications
An audible indication for critical, major, and minor alarms is provided if they are enabled. Alarms that are indicated audibly are configurable in the snmpd.conf file located in the /usr/isos/bin directory on the host system. Audible alarms have the following characteristics: •
The critical alarm stroke consists of a double stroke, the first separated from the second by approximately 0.5 seconds or less, followed by another double stroke approximately 1.5 seconds later. Each double stroke is clearly distinguishable from other double strokes.
•
The major alarm stroke rate consists of one stroke approximately every 1.5 seconds. Each stroke is clearly distinguishable as an evenly timed sequence of strokes.
•
The minor alarm is either a continuous stroke or a stroke lasting approximately 5 seconds (self retiring).
An automatic alarm message is generated at the host display. Each automatic output message includes the following information: •
Time and Date stamp.
•
The severity of the event (i.e., critical, major, minor and informational).
•
An alarm description.
Alarms may be viewed via a remote indicator panel if the J2 output relay contacts on the local status panel are utilized. Additionally, a capability to dial out to an external pager upon the setting of a critical alarm is provided. The dialed number is a configurable entity in the snmpd.conf file located in the /usr/isos/bin directory on the host system.
Paging
J-4
If the snmpd.conf file is configured to enable paging on critical alarms, the pager will initiate a numeric page starting with the first pager number listed in the list. If the alarm is not cleared and retry is configured, the page will be resent within the paging interval up to the number of retries specified in the configuration file. If the alarm has not been cleared and there are additional paging entries in the list, the system will continue to the next pager in the list. If the system reaches the end of the list, it will start over at the first pager on the list until such time as the alarm condition is cleared. For more information on configuring the paging options see “Switch Alarms” on page J-7 and Chapter 12, “SNMP and Alarm Monitoring.”
EXS ExchangePlus Software Operations Guide
Overview
Alarm Administration and Maintenance Alarm Logging
Alarms are logged and time stamped with the time of occurrence of the alarm indication in the system.log file located in the directory /usr/isos/log.
Alarm Clearing
Alarms and statuses are retained until the condition changes. After the trouble or failure has been cleared, a manual reset can be initiated from the ExchangePlus host maintenance menu.
Priority of Notification by Alarm Level
GR-474-CORE defines the following priority sequence for trouble notifications: 1. Critical alarms have the highest priority and are reported before any major or minor alarms. 2. Major alarms are reported before minor alarms. 3. Minor alarms are reported before informational alarms. 4. Continuous monitoring of the equipment power.
J-5
Overview
EXS-2000 Alarm API Messaging Indicator Mapping Overview
J-6
EXS ExchangePlus Software Operations Guide
The following tables map the EXS-2000 B9 Alarm API messages to the server alarm panel and the client alarm panel(s) indicators. Alarms are classified with both Severity and Informational tags. There are three levels of severity to classify alarms: Critical, Major, and Minor. There are 13 classifications of Informational alarms: Power, Synchronization, Card, Circuit, Exnet, Sys Resource, Comm or CC Sig (Command Channel Signaling), Redundancy, Host, Maint or AP Maintenance (Alarm Panel Maintenance), Fan/Temp, Door or Ext Sw (External Software such as databases and CDRâ&#x20AC;&#x2122;s), and Ext or Ext Hw (External Hardware such as channel banks or other equipment that uses alarming). There are corresponding buzzer tones to be sent for Critical, Major and Minor alarms. Numeric pages are only sent on Critical alarms. Paging is not enabled for Major and Minor alarms. There are some alarms that actually send an alarm cleared message. In order to turn off all of the alarms, you must perform a manual reset by selecting the menu option Clear Alarm Panel under the Maint pull-down menu using xmenu.
Alarm Example #1:
The EXS-2000 sends a B9 alarm message with entity of 0x01 (General) and Alarm Number 0x21 (Host Connection Dropped). The host application ExchangePlus receives this message and correlates it to the tables below. In this case, the Critical and Host LEDs change from steady green to flashing red and yellow respectively. Since the severity is equal to the Critical state, the critical buzzer tone will turn on and a page sent out. The alarm is acknowledged via a software clear alarm message and the result is the Host informational LED goes from flashing yellow to flashing green. The Critical severity LED will still flash red and the buzzer tone will still be sounding. The alarm can be manually reset by selecting the menu option Clear Alarm Panel under the Maint pull-down menu using xmenu. This action will Reset the alarms (make all of the LEDs turn to solid green) and turn the buzzer off.
Alarm Example #2:
The EXS-2000 sends a B9 alarm message with entity of 0x01 (General) and Alarm Number 0x04 (Reference 1 Clock Source Lost). The host application ExchangePlus receives this message and correlates it to the tables below. In this case, the Major and Sync LEDs change from steady green to flashing red and yellow respectively. Since the severity is equal to the Major state, the major buzzer tone will turn on and no page is sent. The alarm is acknowledged via a software clear alarm message and the result is the Sync informational LED goes from flashing yellow to flashing green. The Major severity LED will still flash red and the buzzer tone will still be sounding. The alarm can be manually reset by selecting the menu option Clear Alarm Panel under the Maint pull-down menu using xmenu. This action will Reset the alarms (make all of the LEDs turn to solid green) and turn the buzzer off.
EXS ExchangePlus Software Operations Guide
Switch Alarms
Overview
The following tables list the default alarm mapping. These alarm messages can be configured in the file alarmpanel.cfg located in the /usr/isos/bin directory. * These alarms may be followed by an alarm cleared message. ** Informational Only is a message that is logged in the system.log file but is not indicated on the alarm panel. ***For numeric pagers, the alarm numbers are converted to decimal and then sent to the pager. The decimal alarm number is represented in the ( ). # Corresponds to the actual number of the trunk, span or channel number. # # Corresponds to a hex number. For the Clear alarm messages, only the informational alarm will be set to a flashing green state on the alarm panel. It does not affect the severity alarm indicator. The alarms can be manually reset by selecting the menu option Clear Alarm Panel under the Maint pull-down menu using xmenu. This action will Reset the alarms (make all of the LEDs turn to solid green) and turn off the buzzer.
General Alarms 0x01 Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0101 (257)
System Busy Condition*
Critical and Sys Res
Y
0102 (258)
Clock Mode Switched
Major and Sync
N
0103 (259)
Hardware Cannot Support DSP Function Type
Major and Sys Res
N
0104 (260)
Reference 1 Clock Source Lost*
Major and Sync
N
0105 (261)
Reference 2 Clock Source Lost*
Major and Sync
N
0106 (262)
DSP Resource Block Occurred
Major and Sys Res
N
0107 (263)
DSP Resource Function Type Not Configured
Major and Sys Res
N
0108 (264)
DSP Resource Management Inconsistent
Minor and Sys Res
N
0109 (265)
Download Record Timeout
Major and Host
N
010A (266)
Partial Message Received
Minor and Host
N
010B (267)
Recorded Announcement Requested is No Longer Available in the System
Major and Sys Res
N
010C (268)
Unacknowledged Message
Minor and Sys Res
N
010D (269)
Recorded Announcement ID Inconsistency
Minor and Sys Res
N
010E (270)
SS7 Signaling Network Congestion
Major and Comm or CC Sig
N
010F (271)
SS7 Remote ISUP Unavailable
Major and Comm or CC Sig
N
0110 (272)
Node ID Already Exists
Major and Exnet
N
0111 (273)
Invalid Message Length
Minor and Host
N
J-7
Overview
Alarm Number (Decimal Number)***
J-8
EXS ExchangePlus Software Operations Guide
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0112 (274)
System Busy Warning
Major and Sys Res
N
0113 (275)
Resource Utilization Threshold Reached
Major and Sys Res
N
0114 (276)
SS7 Subrate Resources Unavailable
Major and Sys Res
N
0116 (278)
ISDN/SS7 Signaling Stack Congestion
Major and Comm or CC Sig
N
011D (285)
Flash Copy or Load Problem
Major and Sys Res
N
011E (286)
TFTP Alarm
Major and Host
N
011F (287)
System Memory Low
Critical and Sys Res
Y
0120 (288)
System Memory Satisfactory
Informational Only**
N
0121 (289)
Host Connection Dropped
Critical and Host
Y
0122 (290)
Exnet Ring Down
Critical and Exnet
Y
0191 (401)
Unrecognized AIB Type
Informational Only**
N
0192 (402)
DSP Resource Allocation Failure
Major and Host
N
0193 (403)
Remote Inhibit Confirmation At SPN # CHN #
Informational Only**
N
0194 (404)
Remote Uninhibit Confirmation At SPN # CHN #
Informational Only**
N
0195 (405)
Local Inhibit Denied At SPN # CHN #
Minor and Host
N
0196 (406)
Local Inhibit Timeout At SPN # CHN #
Minor and Host
N
0197 (407)
Local Inhibit Confirmation At SPN # CHN #
Informational Only**
N
0198 (408)
Local Uninhibit Confirmation At SPN # CHN #
Informational Only**
N
0199 (409)
Local Uninhibit Not Possible At SPN # CHN #
Minor and Host
N
019A (410)
Local Uninhibit Timeout At SPN # CHN #
Minor and Host
N
019B (411)
Link In Service At SPN # CHN #
Informational Only**
N
019C (412)
Link Out Of Service (L1_DEAD) At SPN # CHN #
Major and Host
N
019D (413)
Link Out Of Service (L5_OOS) At SPN # CHN #
Major and Host
N
019E (414)
Unknown PPL Event # #
Informational Only**
N
019F (415)
Incoming Continuity Failure On SPN # CHN #
Minor and Host
N
01A0 (416)
T8 Expiration On SPN # CHN #
Minor and Host
N
01A1 (417)
RLC T5 Expired On SPN # CHN #
Minor and Host
N
EXS ExchangePlus Software Operations Guide
Alarm Number (Decimal Number)***
Switch API Message
Overview
Primary LED Indicators (Severity and Informational)
Page
01A2 (418)
Continuity Check Outgoing Failure On SPN # CHN #
Minor and Host
N
01A3 (419)
Incoming Continuity Failure On SPN # CHN #
Minor and Host
N
01A4 (420)
First Expiration Of ISUP T17
Minor and Host
N
01A5 (421)
First Expiration Of T23 Timer
Minor and Host
N
01A6 (422)
No Group Reset Response Received for L3P After 15 Seconds
Minor and Host
N
01A7 (423)
Expiration Of T19 Timer At SPN # CHN #
Minor and Host
N
01A8 (424)
Expiration Of T21 Timer At SPN # CHN #
Minor and Host
N
01A9 (425)
SPN # CHN #: CGBA Status Parameter Bit Mask Error
Major and Host
N
01AA (426)
Link Activation Failed At SPN # CHN #
Major and Host
N
01AB (427)
Link Failed At SPN # CHN #
Major and Host
N
01AC (428)
Signaling Link Test Failure At SPN # CHN #
Minor and Host
N
01AD (429)
T36 Expiry On Continuity Recheck At SPN # CHN #
Minor and Host
N
01AE (430)
COT Failure Ind.(Dual Seizure), Process Network IAM At SPN # CHN #
Informational Only**
N
01AF (431)
T5 Expiry In Wait For RLC State At SPN # CHN #
Minor and Host
N
01B0 (432)
CPC Not IDLE Ind. At SPN # CHN #
Minor and Host
N
01B1 (433)
1st Continuity Recheck Attemp Failure At SPN # CHN #
Minor and Host
N
01B2 (434)
Continuity Recheck Attemp Failure At SPN # CHN #
Minor and Host
N
01B3 (435)
Unhandled PPL component = # #
Informational Only**
N
01B4 (436)
TUP Protocol Violation For Trunk #
Major and Host
N
01B5 (437)
COT Received SPN # CHN #
Informational Only**
N
01B6 (438)
CCF Received SPN # CHN #
Informational Only**
N
01B7 (439)
Fail To Rcv CLF Received SPN # CHN #
Minor and Host
N
01B8 (440)
T5 Expiration Received SPN # CHN #
Minor and Host
N
01B9 (441)
T7 Expiration Rcv On SPN # CHN #
Minor and Host
N
01BA (442)
Continuity In Incoming IAM Rcv On SPN # CHN #
Informational Only**
N
J-9
Overview
Alarm Number (Decimal Number)***
J-10
EXS ExchangePlus Software Operations Guide
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
01BB (443)
TUP CIC of SPN # CHN # Unknown TUP Msg Type
Minor and Host
N
01BC (444)
TUP CIC of SPN # CHN # Bad Msg In TUP Msg Format
Major and Host
N
01BD (445)
TUP CIC of SPN # CHN # Unassigned
Minor and Host
N
01BE (446)
CLF With 1st Time Rcv At SPN # CHN #
Informational Only**
N
01BF (447)
CCF With 1st Time Rcv At SPN # CHN #
Informational Only**
N
01C0 (448)
CCF Rcv At SPN # CHN #
Informational Only**
N
01C1 (449)
PPL Component # # 1st T19 Expire SPN # CHN #
Minor and Host
N
01C2 (450)
UCIC Stop Request Received
Minor and Host
N
01C3 (451)
SPN # CHN #: Incorrect Circuit Group Supervision Message Type Indicator
Minor and Host
N
01C4 (452)
T28 Expiry Receiving CQR At SPN # CHN #
Minor and Host
N
8101 (33025)
Clear System Busy Condition
Clear Sys Res
N
8102 (33026)
Clear Clock Mode Switched
Clear Sync
N
8103 (33027)
Clear Hardware Cannot Support DSP function Type
Clear Sys Res
N
8104 (33028)
Clear Reference 1 Clock Source Lost
Clear Sync
N
8105 (33029)
Clear Reference 2 Clock Source Lost
Clear Sync
N
8106 (33030)
Clear DSP Resource Block Occurred
Clear Sys Res
N
8107 (33031)
Clear DSP Resource Function Type Not Configured
Clear Sys Res
N
8108 (33032)
Clear DSP Resource Management Inconsistent
Clear Sys Res
N
8109 (33033)
Clear Download Record Timeout
Clear Host
N
810A (33034)
Clear Partial Message Received
Clear Host
N
810B (33035)
Clear Recorded Announcement Requested Is No Longer Available In The System
Clear Sys Res
N
810C (33036)
Clear Unacknowledged Message
Clear Sys Res
N
810D (33037)
Clear Recorded Announcement ID Inconsistency
Clear Sys Res
N
810E (33038)
Clear SS7 Signaling Network Congestion
Clear Comm or CC Sig
N
810F (33039)
Clear SS7 Remote ISUP Unavailable
Clear Comm or CC Sig
N
8110 (33040)
Clear Node ID Already Exists
Clear Exnet
N
EXS ExchangePlus Software Operations Guide
Alarm Number (Decimal Number)***
Switch API Message
Overview
Primary LED Indicators (Severity and Informational)
Page
8111 (33041)
Clear Invalid Message Length
Clear Host
N
8112 (33042)
Clear System Busy Warning
Clear Sys Res
N
8113 (33043)
Clear Resource Utilization Threshold Reached
Clear Sys Res
N
8114 (33044)
Clear SS7 Subrate Resources Unavailable
Clear Sys Res
N
8116 (33046)
Clear SS7 ISDN/SS7 Signaling Stack Congestion
Clear Comm or CC Sig
N
811D (33053)
Clear Flash Copy or Load Problem
Clear Sys Res
N
811E (33054)
Clear TFTP Alarm
Clear Host
N
811F (33055)
Clear System Memory Low
Clear Sys Res
N
8120 (33056)
Clear System Memory Satisfactory
Clear Informational Only**
N
8121 (33057)
Clear Host Connection Dropped
Clear Host
N
8122 (33058)
Clear Exnet Ring Down
Clear Exnet
N
Card Alarms 0x02 Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0201 (513)
Card Taken Out of Service
Major and Card
N
0202 (514)
Card Type Not Supported
Major and Card
N
0203 (515)
Card Download is Corrupt
Major and Card
N
0204 (516)
Card Type Not Recognized
Major and Card
N
0205 (517)
Reserved
Reserved
N
0206 (518)
Reserved
Reserved
N
0207 (519)
Cards Configuration Has Been Reset To Defaults
Major and Card
N
0208 (520)
Reserved
Reserved
N
0209 (521)
Card Reset
Major and Card
N
020A (522)
Connection Map Failure
Minor and Card
N
020B (523)
Software Does Not Have Download For Card
Major and Card
N
020C (524)
Card Does Not Support A-Law Encoding Format
Minor and Card
N
J-11
Overview
Alarm Number (Decimal Number)***
J-12
EXS ExchangePlus Software Operations Guide
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
020D (525)
Card Revision Not Supported By System Software Revision
Major and Card
N
020E (526)
Card Removed
Major and Card
N
020F (527)
Hardware Failure Occurred On Slot Specified*
Critical and Card
Y
0210 (528)
Ethernet Host Link Error Detected
Critical and Host
Y
0211 (529)
No Fan Tray Installed
Critical and Fan/Temp
Y
0212 (530)
Exnet Port A – Communication Failure
Critical and Exnet
Y
0213 (531)
Exnet Port B – Communication Failure
Critical and Exnet
Y
0214 (532)
Exnet Port A – Fiber Laser Failure
Critical and Exnet
Y
0215 (533)
Exnet Port B – Fiber Laser Failure
Critical and Exnet
Y
0216 (534)
Subrate Board Switchover
Major and Redund
N
0217 (535)
Software Error
Minor and Sys Res
N
0218 (536)
Remote SS7 Card Removed
Major and Comm or CC Sig
N
0219 (537)
Comm Resources Are Currently Controlled By Corresponding Rear Slot
Minor and Sys Res
N
021A (538)
Comm Resources Are Currently Controlled By Corresponding Front Slot
Minor and Sys Res
N
021B (539)
Internal Diagnostics Failure
Major and Exnet
N
021C (540)
Unrecoverable Ring Failure
Critical and Exnet
Y
8201 (33281)
Clear Card Taken Out of Service
Clear Card
N
8202 (33282)
Clear Card Type Not Supported
Clear Card
N
8203 (33283)
Clear Card Download is Corrupt
Clear Card
N
8204 (33284)
Clear Card Type Not Recognized
Clear Card
N
8207 (33287)
Clear Cards Configuration Has Been Reset To Defaults
Clear Card
N
8209 (33289)
Clear Card Reset
Clear Card
N
820A (33290)
Clear Connection Map Failure
Clear Card
N
820B (33291)
Clear Software Does Not Have Download For Card
Clear Card
N
820C (33292)
Clear Card Does Not Support A-Law Encoding Format
Clear Card
N
820D (33293)
Clear Card Revision Not Supported By System Software Revision
Clear Card
N
EXS ExchangePlus Software Operations Guide
Alarm Number (Decimal Number)***
Switch API Message
Overview
Primary LED Indicators (Severity and Informational)
Page
820E (33294)
Clear Card Removed
Clear Card
N
820F (33295)
Clear Hardware Failure Occurred On Slot Specified
Clear Card
N
8210 (33296)
Clear Ethernet Host Link Error Detected
Clear Host
N
8211 (33297)
Clear No Fan Tray Installed
Clear Fan/Temp
N
8212 (33298)
Clear Exnet Port A – Communication Failure
Clear Exnet
N
8213 (33299)
Clear Exnet Port B – Communication Failure
Clear Exnet
N
8214 (33300)
Clear Exnet Port A – Fiber Laser Failure
Clear Exnet
N
8215 (33301)
Clear Exnet Port B – Fiber Laser Failure
Clear Exnet
N
8216 (33302)
Clear Subrate Board Switchover
Clear Redund
N
8217 (33303)
Clear Software Error
Clear Sys Res
N
8218 (33304)
Clear Remote SS7 Card Removed
Clear Comm or CC Sig
N
8219 (33305)
Clear Comm Resources Are Currently Controlled By Corresponding Rear Slot
Clear Sys Res
N
821A (33306)
Clear Comm Resources Are Currently Controlled By Corresponding Front Slot
Clear Sys Res
N
821B (33307)
Clear Internal Diagnostics Failure
Clear Exnet
N
821C (33308)
Clear Unrecoverable Ring Failure
Clear Exnet
N
J-13
Overview
EXS ExchangePlus Software Operations Guide
Span Alarms 0x03 Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0301 (769)
Carrier Group Alarm (CGA) Or Span Dead*
Major and Circuit
N
0302 (770)
Reserved
Reserved
N
0303 (771)
Excessive Burst Of Slips
Major and Circuit
N
0304 (772)
J1-Specific Failure
Major and Circuit
N
0305 (773)
Logical Span ID Already Exists On Another Node
Major and Circuit
N
8301 (33537)
Clear Carrier Group Alarm (CGA) Or Span Dead
Clear Circuit
N
8303 (33539)
Clear Excessive Burst Of Slips
Clear Circuit
N
8304 (33540)
Clear J1-Specific Failure
Clear Circuit
N
8305 (33541)
Clear Logical Span ID Already Exists On Another Node
Clear Circuit
N
Channel Alarms 0x04 Alarm Number (Decimal Number)***
J-14
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0401 (1025)
Reserved
Reserved
N
0402 (1026)
ISDN D Channel Establishing
Informational Only**
N
0403 (1027)
PPL State Machine Error
Minor and Sys Res
N
8402 (33794)
Clear ISDN D Channel Establishing
Clear Informational Only**
N
8403 (33795)
Clear PPL State Machine Error
Clear Sys Res
N
EXS ExchangePlus Software Operations Guide
Overview
DSP Alarms 0x05 0x06 Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0501 (1281)
DSP SIMM Taken Out Of Service
Major and Sys Res
N
0502 (1282)
Reserved
Reserved
N
0503 (1283)
VRAS Erase Complete
Informational Only**
N
0504 (1284)
Recorded Announcement Download Inconsistency
Major and Sys Res
N
0505 (1285)
Recorded Announcement ID Inconsistency
Major and Sys Res
N
0506 (1286)
Recorded Announcement Download Ready
Informational Only**
N
0601 (1537)
DSP Taken Out Of Service
Major and Sys Res
N
8501 (34049)
Clear DSP SIMM Taken Out Of Service
Clear Sys Res
N
8503 (34051)
Clear VRAS Erase Complete
Clear Informational Only**
N
8504 (34052)
Clear Recorded Announcement Download Inconsistency
Clear Sys Res
N
8505 (34053)
Clear Recorded Announcement ID Inconsistency
Clear Sys Res
N
8506 (34504)
Clear Recorded Announcement Download Ready
Clear Informational Only**
N
8601 (34305)
Clear DSP Taken Out Of Service
Clear Sys Res
N
J-15
Overview
EXS ExchangePlus Software Operations Guide
EXS Node Alarms 0x07 Alarm Number (Decimal Number)***
J-16
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0701 (1793)
Not Using EX API
Minor and Sys Res
N
0702 (1794)
Available EXS Conference Timeslot Count Changed
Informational Only**
N
0703 (1795)
Exnet Connect SCbus Master Change
Minor and Exnet
N
0704 (1796)
Exnet Connect SCbus Fail
Major and Exnet
N
0705 (1797)
Exnet Connect Validation Enhancement
Minor and Exnet
N
0707 (1799)
Exnet Connect Not SCbus Master
Minor and Exnet
N
0708 (1800)
Remote SS7 CARD Unavailable
Major and Comm or CC Sig
N
070A (1802)
Maximum Remote Node Count Reached
Critical and Sys Res
Y
8701 (34561)
Clear Not Using EX API
Clear Sys Res
N
8702 (34562)
Clear Available EXS Conference Timeslot Count Changed
Clear Informational Only**
N
8703 (34563)
Clear Exnet Connect SCbus Master Change
Clear Exnet
N
8704 (34564)
Clear Exnet Connect SCbus Fail
Clear Exnet
N
8705 (34565)
Clear Exnet Connect Validation Enhancement
Clear Exnet
N
8707 (34567)
Clear Exnet Connect Not SCbus Master
Clear Exnet
N
8708 (34568)
Clear Remote SS7 CARD Unavailable
Clear Comm or CC Sig
N
870A (34570)
Clear Maximum Remote Node Count Reached
Clear Sys Res
N
EXS ExchangePlus Software Operations Guide
Overview
Alarm Panel Originated Alarms Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0FA1 (4001)
PDU Breaker Trip
Critical and Power
Y
0FA2 (4002)
External Fan Tray Fan Failure Or Low RPM
Critical and Fan/Temp
Y
0FA3 (4003)
External Software Alarm i.e., CDR
Critical and Ext Sw
Y
0FA4 (4004)
External Hardware Alarm i.e., Channel Bank
Critical and Ext Hw
Y
0FA5 (4005)
Loss Of Communications – Alarm Panel(s) To Host
Critical and Maint or AP Maint
Y
• •
LLC Failure, Host failure or Ethernet connection broken ANN unit failure, RS-485 connection broken
0FA6 (4006)
Temperature Out Of Range
Critical and Fan/Temp
Y
0FA7 (4007)
Voltage Out Of Range On A Or B Side
Critical and Power
Y
8FA1 (36769)
Clear PDU Breaker Trip
Clear Power
N
8FA2 (36770)
Clear External Fan Tray Fan Failure Or Low RPM
Clear Fan/Temp
N
8FA3 (36771)
Clear External Software Alarm i.e., CDR
Clear Ext Sw
N
8FA4 (36772)
Clear External Hardware Alarm i.e., Channel Bank
Clear Ext Hw
N
8FA5 (36773)
Clear Loss Of Communications – Alarm Panel(s) To Host
Clear Maint or AP Maint
N
• •
LLC Failure, Host failure or Ethernet connection broken ANN unit failure, RS-485 connection broken
8FA6 (36774)
Clear Temperature Out Of Range
Clear Fan/Temp
N
8FA7 (36775)
Clear Voltage Out Of Range On A Or B Side
Clear Power
N
J-17
Overview
EXS ExchangePlus Software Operations Guide
Watcher Alarms Alarm Number (Decimal Number)***
Switch API Message
Primary LED Indicators (Severity and Informational)
Page
0FB1 (4017)
Watcher Alarm Low Traffic Count
Major and Ext Sw
N
0FB2 (4018)
Watcher Alarm ISOS Task Died
Critical and Host
Y
0FB3 (4019)
Disk Almost Full On Host
Critical and Host
Y
0FB4 (4020)
Host Switched Sides
Major and Host
N
0FB5 (4021)
Host Lost Contact With External System
Major and Host
N
8FB1 (36785)
Clear Watcher Alarm Low Traffic Count
Clear Ext Sw
N
8FB2 (36786)
Clear Watcher Alarm ISOS Task Died
Clear Host
N
8FB3 (36787)
Clear Disk Almost Full On Host
Clear Host
N
8FB4 (36788)
Clear Host Switched Sides
Clear Host
N
8FB5 (36789)
Clear Host Lost Contact With External System
Clear Host
N
Special Alarms Alarm Number (Decimal Number)*** FF00 (65280)
J-18
Switch API Message Reset All Alarms
Primary LED Indicators (Severity and Informational) Resets All Alarms (Sets all alarms to steady green and silences the alarm buzzer)
Page N
EXS ExchangePlus Software Operations Guide
Glossary
Activated
Status of a span or channel as Inservice and available for use.
Announcement table
Used to configure the announcements loaded in the system. The first 100 entries are reserved by ExchangePlus. The rest can be defined by the user.
ANSI
American National Standards Institute. A membership organization founded in 1918 that coordinates the development of U.S. voluntary national standards in both the private and public sectors. It is a variant of SS7 used predominantly in the United States. It is derived from and nearly identical to ITU.
API
Backup
Application Programming Interface. A set of standard software interrupts, calls and data formats that application programs use to initiate contact with network services, communications software and telephone equipment. To make a copy of vital data onto a different storage medium for safety. Regular backup of databases and system logs is essential on ExchangePlus.
Backup & restore
A combination of manual and scripted procedures that restores data in the event of a hardware or software failure.
Bandwidth
Transmission capacity. Specifically, the range of frequencies that can be transmitted by a media effectively. The larger the bandwidth, the greater the capacity of voice, video, or data that the selected media can carry. Bandwidth also refers to the range of frequencies that can be sent over a channel.
Board.cfg
A file containing the setup information for each card installed in the system. The board.cfg file is used to provide ExchangePlus with the system-wide information required to initialize the system and to provide some of the information necessary to tell ExchangePlus what to do when a board is removed and reinserted. This file can either be generated by using xmenu or created manually with a text editor.
Branch
(Related to SNMP) Branches are paths off of the main tree that has a unique name and identifier.
Glossary-1
EXS ExchangePlus Software Operations Guide
Call processing
Call Statistics
CCITT CDR
Operations involved in setting up, connecting, transferring, and terminating a phone call. Provides collection and storage of call activity information. The switch will maintain separate counts of all incoming and outgoing call attempts and completions on a Per Trunk, Per Trunk Group, or Per Route basis. See ITU. Call Detail Record. An accounting record produced by the switch that tracks the type, time, duration, features used, originating party, and destination of calls. CDRs are used for customer billing, rate determination, and capacity planning.
Channel
A separate path through which signals can flow. Also, in the public switched telephone network (PSTN), a channel can be one of multiple transmission paths that exist in a single link between network points. A T-1 link, for example, provides twentyfour separate 64 Kbps channels for digital data transmission.
CIC
Circuit Identification Code used in conjunction with SS7. Synonymous with channel.
Congestion
cron.dat
cron script
A condition that occurs on the network when the load exceeds the capacity of a data communication path. The result of congestion can be bottleneck delays. A file containing a script that can be sent to the UNIX cron task to make sure ExchangePlus is automatically restarted if it stops. A list of one or more commands to a computer operating system or to a server, intended to be executed at a specified time.
crontab
A UNIX command that creates a table or list of commands. Each command is executed by the operating system at a specified time.
Curses Menu
The character-based user interface supplied with ExchangePlus (referred to as menu).
Database
Glossary-2
A database is a collection of data that is organized so that its contents can easily be accessed, managed, and updated.
EXS ExchangePlus Software Operations Guide
Database program
A software application that allows for the management of data and information structured as fields, records and files. It provides an effective and powerful query functionality, in which you can select records based on any of their content. A database program is the heart of an information system and provides mainly file creation, data entry, update, query and reporting functions.
Day of week routing
Route calls based on day of week, such as single weekday, list of week days, range of weekdays, or combination of these.
Time of Day routing
Route calls based on time of day, such as an hour, list of hours, range of hours, or a combination of these.
Dynamic routing
dbcp
Default route
DNIS Translation table
DSP Card
E1R2
A technique in which a system will automatically re-route messages across a network if a line fails or is overloaded. A program supplied with ExchangePlus that can be used two ways, to either create the ISOS database files from the data in shared memory, or to load shared memory from the database files. A routing table entry which is used to direct packets addressed to networks not explicitly listed in the routing table. The DNIS translation table used to translate the dialed number, and route calls based on the dialed number. A system card used to generate tones and receive tones, to perform conferencing, or to store recorded announcements. E1 PPL-controlled trunk.
E1 Span
An AT&T term for a digital carrier facility used to transmit a DS-1 formatted digital signal at 2.048 megabits per second. A line connection of 4 wires which carry 32 channels or trunks.
Ethernet
A 10-Mb/s or 100-Mb/s standard for LANs. All hosts are connected to a coaxial cable where they contend for network access using a Carrier Sense Multiple Access with Collision Detection (CSMA/CD) paradigm.
Exception table
Allows the user to configure the treatment associated with a particular event. The first 64 exceptions are reserved for ExchangePlus. The next 64 are user-defined. There is one exception table per partition.
Glossary-3
EXS ExchangePlus Software Operations Guide
EX/CPU-2000
A high-performance matrix card for the switch. It supports 2,048 ports on an switch and is responsible for host controller communications, system configuration control and monitoring, and the management of system resources. The EX/CPU-2000 supports both basic and extended API messages. The card contains a highperformance processor and a coprocessor with 16 MB RAM (12 on the mothercard and four on the CPU kernel). The EX/CPU-2000 comprises a mother-card with a CPU module attached.
EX/CPU I/O
Provides host communication attachment and the selection and control of switch reference timing. The EX/CPU I/O card supports the following three clock speeds: 2.048 MBPS, 1.544 MBPS, and 64 KBPS. The EX/CPU I/O interfaces with the host computer through either an RS-232 serial link or an Ethernet link.
EXNET
Lucent’s open, architecture, proprietary, 1.3 GPS fiber optic network using a packet-based protocol.
Export Tables
Used to create a switch.cfg file which contains a listing of all the config data stored in tables. This can be printed out, used to create the .dbf files using dbcp, or read into memory using a program called readcfg.
ExchangePlus
A fully-featured “out-of-the-box” tandem and international gateway switch for service providers. The architecture of ExchangePlus supports both 24- and 32channel interfaces in compliance with ANSI and ITU standards. ExchangePlus uses EXS Signaling. This software enables access of signaling from a higher level, so modifications can be made without altering internal system code. ExchangePlus provides a graphical user interface (GUI) for all system functions that are usercontrolled. Some of these include routing, reporting and operations, administration and maintenance (OA&M).
EXS
File transfer
Lucent’s programmable switch that provides a switching platform that supports from 96 to 2,048 non-blocking ports. Copying of a file from one computer to another over a computer network.
File Transfer Protocol (FTP)
A protocol which allows a user on one host to access, and transfer files to and from, another host over a network. The UNIX command is “ftp”.
Graphical User Interface(GUI)
A Windows-style graphical user interface program is included with the system. Also known as xmenu.
Hop
Glossary-4
A term used in routing. A path to a destination on a network is a series of hops, through routers, away from the origin.
EXS ExchangePlus Software Operations Guide
Host
Host interface
A computer that allows users to communicate with other host computers on a network. A computer, attached to the switch through an RS-232 or Ethernet link, from which you run the ExchangePlus system software application that controls the switch. Also, a host is a node in a network. In an EXS system, the host runs ExchangePlus, which performs call routing decisions, logging, CDR generation, and sends appropriate commands to the EX/CPU 2000. The connection between a network and a host computer.
Internet address
A unique computer (host) location on the Internet expressed either as a unique string of numbers.
Internet protocol address
IP address. A 32-bit address used in IP routing. When an IP address is established, it is stored in EPROM on the EX/CPU card. Example of an IP address expressed in dot notation: 205.245.172.72
Integrated Services Digital Network (ISDN)
Standards for transmission of simultaneous voice, data and video information over fewer number of channels than would otherwise be necessary, using out-of-band signaling. The most common ISDN system provides one data and two voice circuits over a standard copper wire pair, but it can also represent as many as 30 channels. Broadband ISDN extends the ISDN capabilities to services that reach up into the Gigabit range. The standards that define ISDN are specified by ITU.
ISOS parent directory
The ISOS parent directory where the ExchangePlus system software is installed. It is normally set to /usr/isos.
ExchangePlus User Interface ITU
Leaf Least-cost routing
Two interfaces in use. A character-based interface called menu and a Windowsâ&#x20AC;&#x2122;based interface called xmenu. International Telecommunications Union. Formerly the CCITT (Consultative Committee for International Telephony and Telegraphy). An international organization founded in 1865 and headquartered in Geneva that sets communications standards, and which has over one hundred-fifty member countries. (Related to SNMP) The leaves of the tree represent the actual MIB object. A method of automatically selecting the least costly facility for transmission of a call.
Glossary-5
EXS ExchangePlus Software Operations Guide
Line assign
A setup that allows a phone number to be attached to a specific trunk circuit which is specified by the trunk group it belongs to and the offset within the group. The line assign setup allows a phone number to be attached to a specific trunk circuit which is specified by the trunk group it belongs to and the offset within the group. When setting up the translation for line assign, a translation to narrow the call down to the trunk group must be setup, then the line assignment will determine which channel within the trunk group will be selected.
Log
The directory where all the log files for ExchangePlus are created. Log files are used to help trace calls, track problems, etc.
Manager
(Related to SNMP) A manager is an application, process, or node that executes network management operations to monitor and control agent systems. Its main role is to poll the agents for certain requested information but it can alter or set management information also on the agentâ&#x20AC;&#x2122;s system. HP OpenView is an example of a network node manager.
Master host Matrix
A switch or device, such as the EX/CPU 2000, that connects calls from one input to the desired output.
menu
Curses interface for ExchangePlus. Supplied with the system.
MIB
MIB-II
Network
Glossary-6
A host connected to the master matrix card.
Management Information Base. The information the SNMP can attain from a network is defined as a MIB (management information base). The MIB is structured like a tree. At the top of the tree is the most general information available about a network. Each branch of the tree then gets more detailed into a specific network area, with the leaves of the tree as specific as the MIB can get. For instance, devices may be a parent in the tree, its children being serial devices and parallel devices. The value of these may be 6, 2, 4 accordingly; with the numbers corresponding to the number of devices attached (4 parallel + 2 serial = 6 total devices). Each node in the MIB tree is a variable (hence in the above example, devices, serial devices, and parallel devices are all variables, their values being 6, 2, 4 accordingly). Check to see if the MIB file that you load onto the network node manager workstation is the same version being used by the SNMP agent on your network device. The Internet MIB-II is one of many standard MIBs. The purpose of the MIB-II is to define common objects for managing TCP/IP networks. The Internet MIB-II definition (RFC 1213) defines standardized objects for TCP/IP agents. An central entity comprised of more than one node. Nodes are programmed to perform custom operations on the messages that pass through them.
EXS ExchangePlus Software Operations Guide
Network address
Network Node Manager
The network portion of an IP address. For a class A network, the network address is signified by the first byte of the IP address. For a class B network, the network address is signified by the first two bytes of the IP address. For a class C network, the network address is signified by the first three bytes of the IP address. In each class, the remainder is the host address. HP OpenView is an example of a network node manager.
NMS
Network Management System. The system responsible for managing a network. The NMS talks to network management agents, which reside in the managed nodes, via a network management protocol.
NOC
Network Operations Center.
Node
In EXS, a unit that contains up to two EX/CPUs, line cards such as T1 and E1, and service cards such as SS7 and ISDN. Nodes can support up to 2048 voice channels. They may be connected together using EXNET to form a larger capacity switch in 2048 increments.
Non-Blocking
A switching system in which the total number of available transmission paths is equal to the number of ports. Therefore, all ports have simultaneous access through the network.
Object
Object Identifiers
(Related to SNMP) An object is anything that will be managed, such as a host, gateway, terminal server, hub, bridge, application, database, or MIB. (Related to SNMP) OIDs are unique identifiers for all space and time. An OID value is an ordered sequence of non-negative integers that contains at least two members with the value of the first member restricted to 0, 1, or 2, and the value of the second member restricted to 0 to 39 if the value of the first is 0 or 1. This sequence describes the only path through the object-naming hierarchy to the object. The naming hierarchy is also known as the tree. The convention for writing object identifiers is called dot notation. An OID in dot notation consists of the integers of the OID in sequence with a period (dot) between them. An example would be: 1.3.6.1.4.1.3959. The full written name of the path is iso.org.dod.internet.private.enterprise.InterCall.
Off-hook
The state of a telephone line that allows dialing and transmission but prohibits incoming calls from being answered.
On-hook
The state of a telephone line that can receive an incoming call.
Glossary-7
EXS ExchangePlus Software Operations Guide
Partition
Permissions
A subtable in the DNIS Translation table, ANI table, and Exception table that will be used for routing. There are 32 partitions in the Exception table and up to 9999 partitions in the DNIS Translation and ANI tables. A UNIX term. Permissions determine who can use which file or directory and how they can use it.
Programmable switch
A telephone switching system controlled by a host computer. The switch is typically integrated into telecom applications by system integrators, OEMs, and VARs who in turn sell complete turnkey applications. Programmable switches can be customized for use in a wide variety of applications such as enhanced service platforms, wireless applications, and service bureaus.
Protocol
Message formats and the rules two computers must follow to exchange those messages. Protocols can describe low-level details of machine-to-machine interfaces (for example, the order in which bits and bytes are sent across a transmission medium) or high-level exchanges between allocation programs (for example, the way in which two programs transfer a file across the Internet).
Protocol ID
PSTN
read.cfg Redundant host
Public Switched Telephone Network. The worldwide voice telephone network. Accessible to anyone who has a telephone and access privileges. The program used to download the switch.cfg file into shared memory. A host connected to the standby matrix card. If the master host fails, the standby host will connect to the master matrix card and take over as the new master host.
RFC
Request For Comment, which is the initial stage in the process for creating Internet standards. RFCs go through several stages of review and refinement before they are adopted as final by the Internet community.
Ring
See EXNET.
Rollover CDR
Route
Glossary-8
The ID assigned to the stack, and currently also used to specify the National/ International indicator. Even is for national and odd is for international. Numbers less than 10 indicate a customized PPL is being used for trunk groups controlled by PPL.
To save collected data into a time-stamped file and re-open it to collect more data. On ExchangePlus, CDR files are automatically rolled over on a regular basis. The path that network traffic takes from its source to its destination. Also, a possible path from a given host to another host or destination.
EXS ExchangePlus Software Operations Guide
Route list
Routing
Routing table
Server Shared memory
A set of trunk groups arranged in priority or by percentage. The switch will always choose the first available trunk group in the list which has circuits that are available when routing. The process of finding the best path to move information through a network. As more networks are interconnected, routing becomes more complex. Also, the process of selecting the correct interface and next hop for a packet being forwarded. A data matrix containing available routes and such parameters as user class of service and call destination. The table is used by the switching software to select a route for a given call. A provider of resources (e.g., file servers and name servers). A method by which program processes can exchange data more quickly than by reading and writing using the regular operating system services. Using a designated area of shared memory, the data can be made directly accessible to more than one process without having to use the system services.
SMI
Structure of Management Information. MIBs are defined using this Internet standard language of objects with a standardized notation. SNMPv1 is one of the versions of SMI.
SNMP
Simple Network Management Protocol. SNMP in general is a protocol designed to give a user the capability to remotely manage a computer network by polling and setting terminal values and monitoring network events. SNMP is composed of three elements: the MIB, the manager, and the agent.
SNMP Agent
The SNMP agent is an application that acts on behalf of an object to perform network management operations requested by the manager. It collects network and terminal information as specified in the MIB and can send unsolicited traps to alert managers of local events. If an agent detects an error condition that is defined in the agentâ&#x20AC;&#x2122;s MIB file, the agent will generate and sends SNMP traps to the network node manager. The ExchangePlus snmpd is an example of an agent.
snmpd
An SNMP agent which binds to a port and awaits requests from SNMP management software. Upon receiving a request, it processes the request(s), collects the requested information and/or performs the requested operation(s) and returns the information to the sender.
snmpdconf Span
A configuration file which defines how the SNMP agent operates. A single physical T1, E1, or J1 line connection
Glossary-9
EXS ExchangePlus Software Operations Guide
SS7
Signaling System 7. A system that puts the information required to set up and manage telephone calls in a separate network rather than within the same network that the telephone call is made on. Signaling information is in the form of digital packets. SS7 uses what is called out-of-band signaling, meaning that signaling (control) information travels on a separate, dedicated 56 or 64 Kbps channel rather than within the same channel as the telephone call. SS7 is now an international telecommunications standard.
Standby host
A host connected to the standby matrix card(s). If the master host fails, the standby host will connect to the master matrix card(s) and take over as the new master host.
Standby IO card Start Host Control
Startup routine
IO card that is associated with the standby line card. Used to restart the host controller if it has been manually stopped with the terminate application command. There are four different levels that can be used to start the host. 0 - start the host controller. 1 - start the host controller and reconfigure the slots. 2 - start the host controller and reload trunk instructions based on the configuration information for the trunk groups and circuits. 3 - restart the host controller, reconfigure the slots and reload the trunk instructions base on the configuration information. The normal startup is level 0. Level 3 is typically used if the matrix has been powered completely down. A routine that is executed when the computer is booted or when an application is loaded. It is used to customize the environment for its associated software. This script is used to start ExchangePlus from the command line.
Storage
A medium designed to hold data, such as a hard disk or CD-ROM
Subtree
(Related to SNMP) Refers to the entire group of branches and leaves under a particular intermediate branch.
Terminate Host Control Window
Uses UNIX command â&#x20AC;&#x153;stopitâ&#x20AC;? at the prompt to manually stop the host controller.
Subscriber
The customer of a local telephone company or carrier., also referred to as the end user, customer, or local user subscriber line.
Glossary-10
Switching
Refers to the process of interconnecting appropriate lines, trunks, or both.
Switch.cfg
A file that contains the initial setup information for ExchangePlus in ASCII format. It is used as a seed file for setting up the initial ExchangePlus databases.
EXS ExchangePlus Software Operations Guide
Switchover
The process in which the primary host will either be terminated or terminate itself and the secondary host will take over as the primary host. The former primary host will attempt to resume a new role as secondary host when restarted by a cron task.
Synchronization
Shows where the current span timing is being derived in ExchangePlus. The system is set up in the Initial Config file to synchronize in the following order: a. Primary Reference clock b. Secondary Reference clock c. Primary Span (1) d. Secondary Span (2) e. Free running clock.
System.log
A log of system startup information as well as a log of any errors that occurred. In addition if the “remote print” level is set to something other than 0, this file will contain call trace information. The higher the remote print level, the more detailed this information will be. This also contains any card fault messages from the switch matrix.
T1 span
An AT&T term for a digital carrier facility used to transmit a DS-1 formatted digital signal at 1.544 megabits per second. A line connection of 4 wires which carry 24 channels or trunks.
TCP/IP Protocol Suite
Transmission Control Protocol over Internet Protocol. This is a common shorthand which refers to the transport and application protocols which run over IP. Provides the ability to link dissimilar computers and to connect equipment to a variety of other systems and protocols.
Tar
Tape ARchive. A UNIX utility that is used to archive files by combining several files into one. A tar archive has the file suffix “.tar”. The files in a tar archive are not compressed, just gathered together in one file. A tar archive is perhaps more frequently used today to transfer files among UNIX systems.
Telnet
The Internet standard protocol for remote terminal connection service. It is defined in STD 8, RFC 854 and extended with options by many other RFCs. Telnet is a user command and an underlying TCP/IP protocol for accessing remote computers.
Topology
Shows the nodes in a network and the links between them. A network must be aware of the current network topology to be able to route packets to their final destination.
Traps
Traps handle special conditions such as when a router link goes down, when network performance is degrading, when a power failure has occurred, etc. You don't poll for traps - the agent just sends the traps to the specified network management station. You can program the network management station to take automatic action. It is important to poll the agents periodically just to see if they are operating correctly.
Glossary-11
EXS ExchangePlus Software Operations Guide
Tree
Trunk group
UCD User.log
An arrangement of similar types of trunk circuits, originating from the same location and terminating at the same location. A trunk group can carry multiple conversations. The voice circuits of the switch are setup as a series of trunk groups. Each trunk group typically goes to a particular switch or carrier. University of California at Davis. A log of everything that was typed or displayed on the system console (menu and xmenu). Much of this is duplicated in system.log but this also shows what was typed.
vi
A UNIX-based text editor. Like most UNIX system interfaces and other text editors, it lets you control the system by using the keyboard rather than a combination of mouse selections and keystrokes.
Watcher
A very flexible and configurable task that monitors trunk activity on the switch and sends out an E-mail or a page alert when certain thresholds are exceeded. Watcher consists of a number of processes and uses simple ASCII text files for configuration.
xmenu
Glossary-12
The naming tree has the structure of a conventional tree. The nodes are labeled with non-negative integers (each node among siblings must have a unique label). Every path through the tree ultimately terminates at a leaf node. The sequence of labels along the path (starting at the root) is the Object Identifier (OID) for the object named at the leaf.
A Windows style graphical user interface program. Supplied with the system.
EXS ExchangePlus Software Operations Guide
Index Symbols & and - 6-38 Âľ-law 6-9
A Alarm Panel clearing condition 12-21 configuration 12-16 configuring pager 12-16 hardware setup 12-9 setting up host name 12-15 switch and host alarms J-1 upgrade embedded software 12-11 upgrade EPROM 12-12 Alarms API messaging J-6 audible J-4 critical J-1 indications J-4 informational J-2 LED pairs J-3 logging J-5 major J-2 paging J-4 priority J-5 remote indications J-4 switch J-7 traps I-2 visual J-3 A-law 6-9 ANI adding or changing entries 6-26 deleting entries 6-31 on demand G-13 table 6-31 Announcements adding or changing 6-54 deleting 6-56 downloading 6-57 API Responses F-3 AppFlag 6-37 Associated Mode Signaling G-3
B B Channel
attributes window 7-41 configuring attributes 7-41 configuring groups 7-38 negotiation (ISDN) G-13 window 7-38 Backup 13-1 board.cfg 4-6 saving tables 6-67 Bouncing the channels 14-18
C Call Statistics by outbound call completion 10-6 by outbound completion by route lists 10-9 by outbound completion by trunk groups 10-8 by trunk groups 10-7 by trunks 10-5 configuring 10-2 viewing 10-4 Calls stop 14-27 Cause Codes ANSI G-10 CDE Command Shortcut Menu 2-15 CDR C-1 cannot write 14-23 cdr.cfg 3-8 file format 3-7 release 2.x format C-4 release 3.x format C-1 removing old files 14-13 rollover 3-2, 6-73 setting up parameters 3-6 time duration 3-9 timestamp 3-4 Channels bouncing 14-18 status 9-4 CICs adding or changing 7-17 configuring 7-16 deleting 7-19 group setup window 7-17 update status window 14-21 CLD 6-36 Clock Sources, Priority 3-23 Command Shortcut Menu 2-15
Index-1
EXS ExchangePlus Software Operations Guide
Configuration making changes via UNIX 6-68 printing the 6-72 saving changes via UNIX 6-71 Connections adding and modifying new 5-2 deleting 5-7 cron setting up tasks 3-2 starting job 3-5, 14-10 stopping job 14-9 Curses Interface 1-13, 2-9 Custom Application 8-1 activating 8-5 adding 8-3 deleting 8-9 reloading 8-10 table 8-3
D D Channel attributes 7-32 backup 7-29, G-12 facilities 7-35 ISDN 7-26 Database Menu A-5 Day of Week 6-62 deleting routes 6-64 DNIS Translation adding or changing 6-32 deleting 6-49 examples 6-41 matching criteria 6-39 partitions 6-33 sample entries 6-42 sorting entries 6-48 DOW 6-62 Downloading Firmware 14-28 DSP adding or changing resources 6-9 card configuration window 6-10 card status 9-6 function configuration window 6-11
E E1 Span adding or changing 6-6 deleting or reassigning 14-16 set up for E1R2 7-44
Index-2
E1R2 inseize 7-49 inseize control 7-55 menu A-8 outseize 7-52 outseize control 7-58 PPL control 7-67 PPL timer 7-64 PPL transmit sig 7-61 set up span for 7-44 stage parameters 7-45 E-mail Log 11-10 EPROM, alarm panel upgrade 12-12 Error Messages description F-1 ISDN F-2 wrong config file F-2 etc/hosts 2-3 Exceed accessing host 2-7 adding ExchangePlus host to 2-5 installing on Windows platform 2-4 terminal window 2-8 XDMCP startup modes 2-6 Exceptions adding or changing 6-50 deleting 6-53 table 6-50 ExchangePlus description 1-1 MIB H-3 saving information on host 1-9 traps I-1, I-2 Export Tables 6-66 exportcfg 6-71 External Time Standard 3-25
F Firmware, Downloading 14-28
G Group Setup Window 7-17
H Host access using Exceed 2-7 accessing from non-windows platform 2-10 accessing from Windows platform 2-2
EXS ExchangePlus Software Operations Guide
adding Exceed 2-5 Changing host name 14-11 file 12-15 forcing switchover 4-8 redundant 4-1 redundant, synchronizing clocks 3-25 restarting 14-6 saving information on 1-9 selecting master or standby 3-18 starting controller 14-2 Telnet 2-11 host.cfg 3-7 HP OpenView 12-4 basic concepts 12-5
I I/O Card card status 9-10 importcfg 6-68 Information Elements (IE) G-12 information services educational services 2 Inseize configure control 7-55 control window 7-55 E1R2 7-49 window 7-49 Interpret Digits 3-14 examples 6-43 ISDN B channel attributes 7-41 B channel groups 7-38 B channel negotiation G-13 backup D channels 7-29 card status 9-8 channels G-12 D channel attributes 7-32 D channel backup G-12 D channel facilities 7-35 D channels 7-26 description G-11 error messages F-2 information elements (IE) G-12 menu A-7 PRI capabilities 7-25 PRI software architecture G-13 redundancy G-12 setting up span 7-25 software architecture G-13
ISUP Timers 7-21
L Line Card card status 9-9 Line Card Configuration window 6-4 Link Sets configuring 7-7 information window 7-7 Links configuring 7-10 status 9-13 log directory description 6 Loop Timing 3-24
M Main Menu 2-9 Maint Menu A-4 Master Database 4-7 Master Host 3-18 Matching Criteria (DNIS) 6-39 Matrix Cards 9-5 status window 9-5 Menu database A-5 E1R2 A-8 ISDN A-7 maint A-4 SS7 A-6 status A-3 system A-2 MIB 12-5 access H-3 browsing 12-7 description H-1 ExchangePlus H-3 loading ExchangePlus 12-6 organization H-2 MTP2 Timers 7-21 MTP3 Timers 7-21
N Netra changing time zones 14-25 Network Node Manager 12-4 NMM 12-4 NOA 6-35, 6-37, 6-41
Index-3
EXS ExchangePlus Software Operations Guide
Node calls stop 14-27 status 9-14
rptmgr.cfg 10-2
O
Save Slot Configuration Window 6-67 Service State, setting span 14-14 Set Channel State Window 14-15 Signaling link sets, configuring 7-7 links, configuring 7-10 routes, configuring 7-13 stacks 7-2 stacks, deleting 7-6 SNMP 12-1 description H-1 network node manager 12-4 quick start 12-2 setting up application 12-3 snmpd.conf 12-3 SNMP and Alarm Monitoring 12-1 snmpd 12-15 Span setting service state 14-14 setting up to use ISDN 7-25 SS7 signalling 7-2 status 9-2 taking out of service 14-14 SS7 acronyms G-2 ANSI cause codes G-10 applications G-1 associated mode signaling G-3 card status 9-7 channels not processing traffic 14-21 CICs 7-16 description G-1 ITU cause codes G-6 layer 3 plus G-5 link sets 7-7 links 7-10 menu A-6 network architectures G-2 optional parameters 7-22 point codes G-3 quasi-associated mode signaling G-3 signaling routes 7-13 software architecture G-4 span 7-2 stacks 7-2 timers 7-21
OOS 14-14 Outbound Translation 3-12 examples 6-45 Outseize control 7-58 control window 7-58 E1R2 7-52 window 7-52
P Page Log 11-9 Pager, configure 12-16 Partitions, DNIS 6-33 Point Codes G-3 PPL control 7-67 Timer 7-64 transmit sig 7-61 Printing Configuration File 6-72 Priority, Clock Sources 3-23
R Redundant Hosts description 4-1 forcing switchover 4-8 saving configuration files 4-6 setting up 4-2 synchronizing 3-25 upgrading software 4-9 Reload Trunk Instructions Window 14-19 Ring(s) Status 9-15 Rollover CDR 3-2, 6-73 Route Setup Window 7-13, 7-15 Routes adding or changing 6-17 configuring 7-13 day of week 6-62 delete time of day 6-61 deleting 6-22 deleting day of week 6-64 from DNIS 6-39 route list table 6-18 time of day 6-58
Index-4
S
EXS ExchangePlus Software Operations Guide
TUP G-6 ss7optparm.cfg 7-22 Stage Parameters Window 7-45 Standby Database 4-7 Standby Host 3-18 Start Host Window 14-4 Statistics by outbound call completion 10-6 by trunk groups 10-7 by trunks 10-5 call 10-2 outbound completion by route lists 10-9 outbound completion by trunk group 10-8 viewing call 10-4 Status channel 9-4 DSP card 9-6 I/O card 9-10 ISDN card 9-8 line card 9-9 links 9-13 matrix cards 9-5 menu A-3 node 9-14 Ring(s) 9-15 span 9-2 SS7 card 9-7 synchronization 9-12 trunk 14-18 version 9-16 VRAS 9-11 Switch timing 3-22 traps I-3 switch.cfg 4-6 Switchover redundant hosts 4-8 Synchronization clocks on redundant hosts 3-25 master and standby database 4-7 reference timing, loop timing, free running 322 status 9-12 to external time standard 3-25 System Log 9-18 System Menu A-2
T T1 Span
adding or changing 6-3 deleting or reassigning 14-16 line configuration window 6-4 Table Sizes D-1 Technical Support x Telnet 2-11 Terminal Window 2-7 Time duration in CDR 3-9 synchronizing to external 3-25 Time of Day delete routes 6-61 route 6-58 table 6-58 Time Zones, Changing 14-25 Timestamp, CDR 3-4 Timing, Synchronizing Switch 3-22 to 6-66 TOD 6-58 Translate With Prefix 3-16, 3-20 examples 6-44 Traps I-1 ExchangePlus alarm specific I-2 switch I-3 Trunk flags B-3 reloading instructions 14-19 status 14-18 types B-1 Trunk Groups adding or changing 6-12 adding trunks 6-23 deleting 6-16 deleting trunks 6-25 Trunk Group Table 6-12 trunk table 6-25 Trunks adding to trunk groups 6-23 deleting from trunk groups 6-25 status 14-20 table 6-25 take out of service 14-15 TUP G-6
U UFlag 6-37 UNIX commands E-4 description E-1
Index-5
EXS ExchangePlus Software Operations Guide
making configuration changes 6-68 operation E-3 permissions E-12 saving configuration changes 6-71 vi E-10 Update CIC Status Window 14-21 Upgrade Redundant Host 4-9 User Interface curses 1-13, 2-9 Main menu 2-9 terminal window 2-7 Windows-based 1-10 User Log 9-17
V Version Status 9-16 vi E-10 VRAS adding or changing announcements 6-54 announcement table 6-56 deleting announcements 6-56 downloading announcements 6-57 status 9-11
W Watcher E-mail log 11-10 E-mailing 11-7 monitor trunk parameters 11-4 page log 11-9 paging 11-6 setting monitor levels 11-3
X XDMCP startup modes window 2-6 xmenu saving configuration changes 6-65
Index-6