BusinessPhone Communication Platform 6.0
BMS Script Programmers Reference

## General

### Document overview

The script documentation consists of the following parts:

- Script programmers guide
- Script programmers MO reference
- trm28pa3.emf
- iwd-tonescheme-21-N.emf

The basic structures are described, which are necessary for understanding, writing and debugging BMS scripts.

This document gives you an overview about the structure and all types of BMS managed objects (later used "MO" only). The structure is defined through the chapter’s structure itself. Therefore, please regard the chapter hierarchy as a kind of tree directory.

##### MO’s chapter title: syntax description

Each chapter title consists of the following components:

[ProgramminModel:] MOType "( " Identifier " )"

Whereas:

ProgramminModel = { R12, R13 }

MOType = { MO, TrunkMO, ExtensionMO }

Identifier = { Hotel, Systemdata... }

##### MO description

You can handle a MO as only one object, which has some attributes and methods that allow reading, writing and modification.

##### Script data types

The following script data types are supported:

- String, MO, ExtensionMO, TrunkMO

There are two different types of MO’s:

- Static MO – unique and always available
- Dynamic MO – not required, more than one instance possible

BMS knows two dynamic MO’s: ExtensionMOs and TrunkMOs. There are two ways to identify the different dynamic MOs:

- by directory number identifier
- by card, and individual number definition

For a detailed definition of the directory number, card position number and the individual number, please refer to the BSM help or the BSM documentation.

##### MO methods

MO types and list of their methods:

MO:

set("attname","attValue" … );

TrunkMO:

set("attname","attValue");

userDIRentry();

userLINKentry();

findLink("dirno"); // dirno must be a valid directory number

linkparam2copy("attname"…);

mark2copy("attname"…);

setSTSN("cardnumber","individuumnumber");

ExtensionMO:

set("attname","attValue");

userDIRentry();

mark2copy("attname"…);

setSTSN("cardnumber","individuumnumber");

##### Relation Command – Attribute

Sometimes you will have to deal with commands that have more than one value (e.g. any kind of table). Therefore, the command number differs from the attribute identifier. This difference is marked through following syntax:

- Command/Attribute: command identifier is identical with the attribute identifier.
- Command: command number only
- Attribute: attribute identifier only

##### Value description

Each value will be defined as a string in quotation marks " ".

The value range or the value enumeration will be defined in lists or optional in tables.

##### Abbreviations

BP |  | BusinessPhone |
BMS |  | BusinessPhone Management Suite |
OAM |  | Operation Administration and Maintenance |
RASC |  | Remote Access Supervision and Configuration |

Revision: A © Ericsson Enterprise 2004