BusinessPhone Communication Platform 5.1
System Description ASB 150 02

## Operation & Maintenance (O&M)

### Operational cases

Maintenance of ASB 150 02 can be performed locally or via remotely connected equipment.

All exchange parameters that are programmable can be administered from the web-based operation & maintenance system, BMS. Furthermore a limited number of parameters can be programmed from certain types of system telephones.

#### O&M from a system telephone

Certain parameters in the PBX can be programmed from arbitrary system telephones, type "EXECUTIVE", or the PBX-operator console.

Parameters that are often changed in a system can be programmed during operation such as (alteration of extension numbers, external abbreviated numbers, categories and clocks).

It is also possible to set certain I/O-parameters from these system telephones. These parameters control the possibility to connect external units, e.g. BMS.

#### O&M from a locally connected computer

A computer (PC) equipped with BMS can be connected to any V.24 port in the system. (At least one V.24 port exists on the CPU-D_ board in all PBXs).

From this computer it is possible to undertake all O&M-functions.

##### Standalone configuration

##### Network configuration (via V.24 agent)

##### Network configuration (IPU (TCP) connection)

#### O&M from remotely connected computer

A computer (PC) where the BMS program is installed can be remotely connected to the system. In principle there are two alternatives for remote connection:

With the PBX's built-in V.32bis modem:

Via the Internet

### Security

#### Passwords

Authorisation is required to permit system programming from a system telephone. There are four classes of authorisation, each with its unique 5-digit password. A higher level automatically gives authorisation to access all lower levels.

System programming from BMS is permitted only for the highest authorisation class, which permits programming of all parameters. BMS enables programming of the authorisation class.

#### Dial back

For remotely connected O&M the password security can be complemented with a dial-back procedure.

### Administration of customer data

#### On-line programming

"On-line" means that BMS is connected locally or remotely to the PBX whose data is to be programmed.

When BMS is connected to the PBX, copies of all programmable data are sent from the PBX to BMS. This data is used to be able to show the technician how the connected PBX is programmed.

When the data operator changes a certain parameter, the altered data is sent to the PBX for storage in the database (EEPROM or battery backed-up RAM) of the PBX.

It is also possible for the technician to store all data that has been copied from the PBX in the database of the BMS Server (Backup copy).

#### Off-line programming

"Off-line" means that BMS is not connected to any PBX.

In order to be able to change data a copy of all programmable data is stored in a customer PBX and is accessible in the BMS database.

This data may have been stored in conjunction with an earlier connection during on-line programming or by an earlier backup copy of the data in the customer's exchange.

The technician can alter data in the backup copy. The altered parameters are marked in the data copy and can be transferred to the customer's PBX later on.

#### New installation of a PBX

Templates with default data for all programmable parameters can be created and stored in BMS. The use of these templates considerably simplifies the adaptation of programmable data for a certain market or for a certain customer category, where several PBXs are to have the same values for certain parameters (e.g. signal interface diagrams for public telephone lines, transmission parameters, etc.).

For a new PBX installation, a set of data can be created off-line by the technician specifying the configuration of the customer's PBX for BMS.

#### Reloading of backup copy

Data stored during backup copying or in conjunction with on-line programming of a customer PBX can be reloaded into the PBX.

Before the data is reloaded, BMS verifies that the customer's PBX is configured in the same manner as the stored copy.

### Product identification

Product number and revision state on all the PBX's device boards as well as central and regional programs can be read out with the help of BMS. It is also possible to identify the revision states of the PBAs (Printed Board Assemblies).

To facilitate programming of PBXs with different software program releases or program revisions from the same BMS, the various program issues of the PBX have been furnished with a programming model number that is read out automatically from BMS when it is connected to a PBX. This model number informs BMS about the programmable data in the connected PBX so that the correct set of commands, guide texts and default values are made accessible to the data operator.

### Authority Levels and Passwords in Cordless

Security is an important issue in the Integrated Cordless. Therefore, the on-line functions have been divided into three authority levels, all protected by a password. Depending on the password entered, different authority levels may be reached providing different menus. The three authority levels are: Receptionist, System Manager and Distributor.

Access to the Off-line menus is not protected by a password as there is no connection with the Integrated Cordless system and therefore no unauthorized access to the Cordless system is possible.

- Receptionist

- The Receptionist has the lowest authority level. When you log in as Receptionist, you will only see the Receptionist menu. The Receptionist menu allows you to administer portable telephones.

- System Manager

- The next authority level is the System Manager. When you log in as System Manager, you will see both the System Manager menu and the Receptionist menu. The System Manager menu allows you to maintain the Integrated Cordless system. Also statistic functions are available when the Cordless System Statistics Software package is installed.

- Distributor

- The Distributor level is the highest authority level. When you log in as Distributor, you will see all the available menus: the Distributor menu, the System Manager menu and the Receptionist menu. The Distributor menu allows you to initialize the Central Unit.

#### Changing Passwords

The Distributor has a “default” (factory-set) password that is communicated to him when the system is delivered. After delivery he has to change the default password to the password he wants to use. Take care not to forget the Distributor's password. Only the manufacturer can change it. The manufacturer will charge you for changing the password.

Besides his own password, the Distributor may change the password of the System Manager and the Receptionist. He does not have to know the old password of the System Manager or the Receptionist. He may enter his own password and subsequently change the other password. Thus, the Distributor may give the Receptionist or the System Manager a new password if they forgot the old one.

The System Manager may change his own password and the password of the Receptionist. To change the Receptionist's password, he does not have to know the old password of the Receptionist. He may enter his own password and subsequently change the Receptionist's password. Thus, the System Manager may give the Receptionist a new password if he has forgotten the old one.

The Receptionist may change only his own password. To change the password, the old password must be entered first, and then the new password.

#### Stand-by Protection

To protect the system against misuse after a correct password is entered, a Stand-by mode is used. The program switches to the Stand-by mode when, during a 5 minute period, the keyboard of the PC has been left untouched. After entering a correct password the corresponding authority level is selected.

### Administration of faults

#### Fault detection

##### Method

All abnormal situations that are detected by central and regional programs are reported to the central operating system via a warning mechanism.

The warning mechanism is used for all types of faults (errors), e.g. defective hardware, incorrect behaviour by connected devices, reporting of certain "lack of resources" situations and pure program faults. To differentiate between the different cases each type of warning has been assigned a number (1-255).

This warning number, together with an identity, program unit or board (ST/CARD), and up to four other parameters that describe the fault is stored centrally in the system. The time when the event occurred is stored as well.

##### Monitoring of operation

The central processor is monitored by a watchdog that restarts the entire system if CP or SP malfunctions for some reason or other.

A voltage monitor on CPU-D_ locks memory access and restarts the whole system if the 5V voltage used for the processes drops too low. Certain device boards also possess local voltage monitors where incorrect voltages are reported to CP.

A program in the central processor monitors all regional processors periodically (every minute), so that the system can restart a single board, if one of the RPs malfunctions.

All common resources such as PCM-channels, dynamically allocated memory and non-volatile memory (E2 and battery backed-up RAM) are monitored periodically every 24 hours. Faults (if any) are reported with the help of the warning mechanism.

Certain peripheral units can also be monitored, e.g. when the mains voltage fails and the system switches to battery operation or when connected units for call logging malfunction (e.g. no paper left in a printer).

#### Fault recording

The warning mechanism comprises several parts, namely:

- The central operating system that receives fault reports from central and regional software
- An O&M-block in the central software that deals with the storage of data related to warnings
- A maintenance part in BMS that can be read out and show all stored data.

There are three classes of warnings:

- STOP: When the warning is generated the PBX is restarted.
- ALARM: Serious fault that requires action.
- WARNING: Other faults.

The classification determines in which fault log the warning data shall be stored. For most warnings the classification can be altered. A warning can also be deactivated so that it is not stored in the system's logs at all.

An attribute is supplied with each warning:

- ACTIVE: The warning is indicated in an external O&M-centre (via modem).
- INFO: A programmable text can be associated with the warning. The text can be read off from a system telephone with display.
- TRIG: Generates a TRACE-log, that is a set of data from the activity that generated the warning, is stored in CP's memory.

#### Fault reporting

The warnings can be reported to the data operator(s) in different ways:

- A programmable key indicator on a system telephone can be lit upon a specific occurrence
- Via a modem the warning can be sent to an external O&M-centre
- The warning is indicated on a LED on the front of the CPU-D_ board

It is also possible to connect BMS, locally or remotely, in order to read out all fault- and TRACE-logs that have been stored in the PBX.

There is also an inverted form of fault reporting. The PBX can be programmed to call an O&M-centre regularly using a "heartbeat" procedure. A missed call then indicates that there is something wrong with the PBX.

#### Fault locating

In principle fault locating takes place via those fault- and TRACE-logs that can be read out from BMS, Available resources, data related to power supply and temperatures can also be read out via BMS.

For fault locating at local level see Fault Tracing Description (1545-ASB 150 02 Uen), containing directions for localisation of faults.

Furthermore, the LEDs on each device board can provide certain information regarding board status.

### Traffic measurement

No traditional traffic measurement functions implemented. However, certain facilities send information about traffic to external units, e.g. ACD (Automatic Call Distribution) and CIL (Call Information Logging).

There are also certain meters in the PBX that can be read out by BMS, e.g. the number of times that calls could not be set up due to lack of capacity in the switch.

### Call metering

#### Logging of calls

An external computer can be connected to the system for registration of calls (CIL, Call Information Logging).

#### Accumulation of call costs

Reception of metering information from connected public exchanges takes place on the BTU-A, BTU-C, BTU‑D, BTU-B2 and MFU boards.

With exchanges connected in analogue fashion (BTU‑A, ‑C) special hardware is required to detect call metering pulses. Add-on boards for different metering systems are mounted as daughter boards directly on the BTU‑A, ‑C boards.

These boards (CM) exist for 50 Hz pulses (CM50) or for 12/16 KHz pulses (CM12/16).

With exchanges connected in digital fashion, CAS or ISDN (BTU-D,-B and MFU), the metering information is received directly in the digital signal channel without any extra equipment.

The metering information is then stored in the battery backed-up memory on the CPU-D_ board.

#### Read out of metering information

Read out of accumulated metering information can take place via a system telephone with display or via a printout on a locally connected printer.

The information can be obtained in the form of metering pulses or converted into local currency.

Using a system telephone with display it is also possible to obtain metering information for an individual call while the call is ongoing or after the call has ended.

Revision: M © Ericsson Enterprise 2003