
VTCPD Messages
P0602483 Ver: 03.41 Page 51
All messages must include a Message ID field. The length and location of the ID field
is specified by:
-i N:M
Message ID Options
vtcpd {-i|I} {<len>:<pos>|<len>@<str>} [-m i] [{-a <#>|-A <#>}]
Args: -i The Message ID is assigned by applications.
-I The Message ID is assigned by VTCPD.
<len> Specifies the length in bytes for the message ID field.
<pos> Specifies the starting position of the ID field (i.e., the offset).
<str> Specifies a string within the message that identifies the
Message ID field by directly preceding it. The string can be any
set of ASCII characters except 0x00. Unprintable characters
are represented in hexadecimal as 0xXX.
-a <#> Specifies the line number of an administrative application that
receives any unidentifiable messages.
-A <#> Specifies the line number of an administrative application that
sends all messages from the host. In this case, the Message ID
fields from application GET and SEND requests are ignored.
-m i Specifies that VTCPD is to run in inverted mode. This is
intended for messages that cannot be correlated by means of
the Message ID field. Use this option if the message IDs are set
by the host.
Examples: vtcpd -i 48:1
The Message ID is supplied by the application. The Message ID field is 48
bytes in length and starts from the beginning of the message.
vtcpd -I 2:1
The Message ID is supplied by VTCPD and consists of binary
representations of the phone line and MPS numbers.
vtcpd -I 6:24
The Message ID is supplied by VTCPD. The Message ID consists of ASCII
representations of the phone line and MPS numbers.
vtcpd -i 4@abc0x0A0x0B
The Message ID is supplied by the application. The Message ID field is four
bytes in length, and is located directly after the string abcXY, where X and Y
are binary values representing 1 and 2.
Komentarze do niniejszej Instrukcji