General |
| Name: |
PageMaster |
| Version: |
5.0 |
| Released: |
2009 |
System Requirements |
| Processor: |
Intel 32-bit |
| Operating
System: |
Windows XP,
Windows Vista, WIndows 7, Windows 2003 Server, or Windows 2008 Server |
| Internet Connectivity: |
A WinSock-compatible Internet
connection is required for the SNPP, SMPP, SMTP, and WCTP protocols |
| Modem: |
Hayes-compatible
2400 baud or faster is required if using the TAP or DTMF protocols) |
| Network: |
Supports any
network topology. Allows sharing of device, group, and service provider databases. Allows sending text messages from a central server through
PageMaster/sv or
PageMaster/ex) |
Devices |
| Number
of Devices: |
Unlimited,
with full search capability |
| Grouping: |
Devices may
be grouped with no limitations on the number of groups that may be defined. Devices may be assigned to multiple groups |
| Device
Types: |
Alphanumeric Pagers (1 and
2-Way), Cellular Phones (SMS 1 and 2-Way), Numeric Pagers |
| Additional
Fields: |
Three user-defined data fields maintained for each device |
Message Handing |
| Batch Sending: |
Alphanumeric messages sent
to devices sharing a common access method are issued in a single session |
| Message Length: |
Unlimited. Messages are automatically
split and delivered to a device in separate messages according to a maximum
message length (user definable) |
| Error Correction: |
Full error detection and recovery
on all protocols. Includes dial-tone detection and busy signal redial for
TAP |
| Confirmation: |
If desired, a confirmation dialog box will be displayed once
the message is transmitted successfully |
| Error Notification: |
If an error is encountered
sending a message, an failure dialog box will be displayed. Full error details are logged
in the application event log |
| Backup Protocols: |
Multiple protocols may be specified
for each service provider. Automatic fallback to alternate protocols upon
failure |
| Logging: |
All text messages sent and
failed are logged. Log files are user configurable as to content and organization. |
Messaging Methods |
| Manual: |
Text messages
entered and issued manually |
| DDE: |
Text messages
issued from applications via DDE (Dynamic Data Exchange) commands |
| Command
Line: |
Text messages
issued by providing, on the command line, a name of a file that contains
device names and messages |
| Scheduled: |
Text messages
may be scheduled for delivery at a specific date and time |
Additional Features |
| Logging: |
All text messages sent and
failed are logged. Log files are user configurable as to content and organization. |
| Import/Export: |
Device database
may be imported from or exported to text files in comma-delimited format. |
| |
