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

Common Configuration

# P0602477 Ver: 3.1.11 Page 227

Message Format

Previously, only one message format could be specified for all connections to one

instance of VTCPD. However, VTCPD now supports different message formats for

outgoing and incoming messages. By default, the header format is the same for both

message formats as defined by the VTCPD options -f or -i. In the case of

differing formats, these options are applied to the outgoing messages only, while the

-F and -j options are applied to incoming messages. (See vtcpd on page 227 and

“Message Identification (ID)” on page 231.) The following formats are available.

The following is important information regarding the use of these options:

• In UDP mode, the entire message comes from a host in a single packet:

therefore, the -f option should not be used.

• VTCPD adds a message header or a delimiter to a string received from an

application. The application should not include a message header or a

delimiter with the message sent to the daemon.

Format Description

fixed length The message contains a fixed number of bytes.

variable length

(with delimiter)

The message is delimited by a specified character.

variable length

(with byte

specification)

The number of bytes precedes each message. The message starts

after the header. The message length does not include the size of

the header.

vtcpd -f | -F {len | d:D | l:{#|lf[:hp[:hl]]}|

L:{w|lf[:hp[:hl]]}|

a:{n|lf[:hp[:hl]]}|

A:{n|lf[:hp[:hl]]}

[{-mB | -m

h | -m t}]

The -F option applies to incoming messages only, and then only when the

format differs from outgoing messages. Otherwise, the -f option prevails.

position

length field

header

message

message body

1 2 ... 222 223 224 225 226 227 228 229 230 231 232 ... 305 306

Sin comentarios

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