Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 231)

Common Configuration

# P0602477 Ver: 3.1.11 Page 231

Message Identification (ID)

Messages are identified by a unique combination of consecutive bytes called the

message ID. Unless a host connection is exclusively dedicated for a single phone line

(see below), all messages must include an ID field. A request from an application and

the corresponding reply from the host will have the matching message ID fields.

Identification fields for requests can either be assigned by applications (specified by

the -i or -j option) or by VTCPD (specified by the -I option), but not both. If

the daemon assigns the ID, it uses one of the following methods:

If it is specified that the ID is to be assigned by applications, they are responsible for

ensuring that no two outstanding requests have the same ID. The daemon doesn't

check the validity of the ID field. It only matches it byte for byte with the ID in the

host responses. If two requests with the same ID are pending, applications may be

given unrelated responses to their requests.

If host data contains an ID that cannot be associated with any phone line, it is normally

discarded. However, it is possible to pre-assign an administrative phone line that

receives all unidentified messages. The messages are sent to the line as the data

portion of the condition unexdata.

Bytes Message ID Contents Digits

one Phone line of the application sending the request. binary

two Phone line and MPS number of the requesting application. binary

three Phone line number of the requesting application in the

format 999.

ASCII

six Phone line and MPS number of the requesting application. ASCII

1 2 ... 226 227 228 229 230 231 232 233 234 235 236 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 231