|
|
|
|
|
|
| Drop
File Feature |
- Drop Files allow any application to use the fail-safe output
system of Rio Desktop Paging to deliver messages to pagers or
Mobile Phones.
- Copy files to be transmitted to the Drop File Folder. They
will be collected for transmission within a second or two.
- The Drop File folder can be private or public.
- A full audit trail of all dropped files is maintained.
- The format of a drop file is simple and can be generated by
many other programs.
|
| Drop
File Format |
- Several fields are empty for possible future expansion. Note
that the format of log files is similar.
- Each message must be placed in a separate file. Each file
can contain only one message on a single line.
- The file extension must be .DRP
- Here is a sample drop file entry.
|
| 19990129|000000||scott|839437|1|1|0|Page
Accepted|||||||This is a test page|Fred Smith |
| Field
Number |
Contents |
Explanation |
| 1 |
YYYYMMDD |
The date of
the attempted connection |
| 2 |
HHMMSS |
The time of
the attempted connection |
| 3 |
|
Name of the
Server that made the connection (currently blank) |
| 4 |
From |
The login
name of the person the Page is from |
| 5 |
To |
The
Subscriber Number of the person to whom the Page is to be
sent: 6 to 11 digits |
| 6 |
Service
Provider Number |
e.g. 1=PageOne
Communications. These are allocated sequentially by the
Server |
| 7 |
Transport
code |
e.g.
1=dial-up. These are allocated sequentially by the Server |
| 8 |
Protocol
code |
e.g. 1=TAP.
These are allocated sequentially by the Server |
| 9 |
Success /
failure code |
e.g. 0 |
| 10 |
Success /
failure message |
e.g. Page
Accepted |
| 11 |
|
Unused |
| 12 |
|
Unused |
| 13 |
|
Unused |
| 14 |
|
Unused |
| 15 |
|
Unused |
| 16 |
Page Message |
The text or
numeric Page that was sent |
| 17 |
User
Signature |
The user
signature to be attached to the page |
|
|
|
- "Reply Requested" allows the sender of a message
to specify to the recipient that he must acknowledge receipt
of the page
- The distinctive appearance of a Reply Requested message on a
pager is set by the Administrator and ensures that the
recipient will know that a reply has been requested.
- The recipient replies to the sender of the message by making
a phone call and entering a numeric message via the keypad of
the phone. This process should not take more than 20-30
seconds.
- When a reply has been made, confirmation appears in the form
of a pop-up on the screen of the sender of the message.
- If the time period set for the reply to the page (e.g. 5
minutes) expires, the message is automatically re-sent up to a
maximum number of times set by the Administrator
- The Reply Requested functionality requires an Infolink Data
Receiver. which must be purchased in addition to the
PageLinkII software.
- Reply Requested works with individual, group and Rota
messaging from PageLinkII
|
| Reply
Requested in Pratice |
- The sender enters the message. "Reply Requested"
is checked and the message is sent.
|
 |
- A pop-up on the senders' screen confirms that the message
has been sent.
|
 |
- The recipient receives the message on the pager
|
 |
- As soon as the recipient telephones 015234 123456 and enters
1234, the Rio system will inform the sender that the message
has been acknowledged and will not send the message again.
|
 |
|
|
| Log
Files Format |
Log files are
displayed, and will be saved, in the following format. Note that
the format of drop files is essentially the same with certain
fields left blank.
Each attempted connection to a Paging Service Provider is recorded
as a single line of text consisting of 17 fields each separated by
a "|" symbol. Several of the fields are currently unused
and are left for future expansion.
19990129|000000||scott|839437|1|1|0|Page Accepted|||||||This is a
test page|Fred Smith |
| Field
Number |
Contents |
Explanation |
| 1 |
YYYYMMDD |
The date of
the attempted connection |
| 2 |
HHMMSS |
The time of
the attempted connection |
| 3 |
|
Name of the
Server that made the connection (currently blank) |
| 4 |
From |
The login
name of the person the Page is from |
| 5 |
To |
The
Subscriber Number of the person to whom the Page is to be
sent: 6 to 11 digits |
| 6 |
Service
Provider Number |
e.g. 1=PageOne
Communications. These are allocated sequentially by the
Server |
| 7 |
Transport
code |
e.g.
1=dial-up. These are allocated sequentially by the Server |
| 8 |
Protocol
code |
e.g. 1=TAP.
These are allocated sequentially by the Server |
| 9 |
Success /
failure code |
e.g. 0 |
| 10 |
Success /
failure message |
e.g. Page
Accepted |
| 11 |
|
Unused |
| 12 |
|
Unused |
| 13 |
|
Unused |
| 14 |
|
Unused |
| 15 |
|
Unused |
| 16 |
Page Message |
The text or
numeric Page that was sent |
| 17 |
User
Signature |
The user
signature to be attached to the page |
|
| |