Version Changes

PageMaster/ex 2003 Version 11:

PageMaster/ex Version 11 adds the following new features:

Stand-Alone Device Administrator - In previous version of PageMaster/ex 2003, device administration could be performed only with Active Directory Users & Computers (ADU&C).

This release adds a stand-alone administrative tool that can be deployed anywhere on the network for creation, administration, and deletion of devices. The machine on which the tool is installed need NOT have either the Exchange Remote Administration tools nor Active Directory tools. The stand-alone administration can run independently, accessing AD through LDAP calls.

Stand-Alone Connector Administrator - In previous version of PageMaster/ex 2003, connector administration could be performed only with Exchange System Manager (ESM).

This release adds a stand-alone administrative tool that can be deployed anywhere on the network for administration of PageMaster/ex connectors (both 2003 and 2007 versions). The machine on which the tool is installed need NOT have either the Exchange Remote Administration tools nor Active Directory tools. The stand-alone administration can run independently, accessing AD through LDAP calls.

This allows you to assign connector administrative tasks to users that should not have access to Exchange and/or AD tools.

Client Message Status - PageMaster/ex 2003 now supports bidirectional communication with PageMaster clients.

In prior releases, if a message were to fail, the PageMaster/ex 2003 connector would log the failure on the server end, and generate an event log error specifying the cause. However, the message originator at the client end would not be notified of the failure.

Version 11 now adds the ability for the PageMaster/ex 2003 connector to send failure notifications back to the client for display.

 

PageMaster/ex 2003 Version 10:

High-availability is the focus of the v10 release. With v10, it is possible to provide text messaging capability should Exchange, AD (Active Directory), or even the entire network, go down.

This is accomplished by establishing a chain of available text message processors; from PageMaster/ex connectors, to PageMaster/sv (a PageMaster server that is non-Exchange integrated), to a client-based processor. In such a scenario, PageMaster clients are deployed and provide a database of text message devices pulled directly from AD (Active Directory). Such clients normally send text messages through a PageMaster/ex server. Should a PageMaster/ex server go down, the client can be configured to automatically fall back to alternate PageMaster/ex servers. Should AD become unavailable, the client caches the device information to provide uninterrupted messaging.

Now, suppose that Exchange itself should go down. The PageMaster client can automatically fall back to one or more PageMaster/sv servers.

Finally should the PageMaster/sv server(s) be unavailable, or should the network itself go down, the PageMaster client can utilize its own internal text messaging engine to send messages.

At each point of processing (whether it be PageMaster/ex, PageMaster/sv, or the PageMaster client), multiple protocols can be specified for each service provider with automatic fallback should the primary protocol fail.

With this architecture, v10 provides an unprecedented level of fault-tolerance, and thus, reliability for even the most critical messages.

The new feature set for v10 includes:

  • All New PageMaster Client - PageMaster/ex 2003 now includes a client application that provides additional benefits over and above using a standard email client:

    The PageMaster client can be employed on machines that do not have an email client (i.e. Outlook) installed and connected to Exchange Server. PageMaster routes its messages to PageMaster/ex through a DCOM interface, external to mail handling, so a mail client is unnecessary. The device list is read directly from Active Directory, so no separate device database need be maintained for PageMaster clients.

    The PageMaster client also provides backup paging capability in the event of an Exchange or network outage. Automatic fallback from a primary PageMaster/ex connection will reroute messaging first to any stand-alone (non-Exchange Integrated) PageMaster/sv servers, then ultimately to the client's own internal text messaging engine.

    The PageMaster client provides additional messaging options not available when messaging through a mail clients. This includes pre-defined (or "canned") messages that can be sent quickly using a hotkey combination, scheduled and automatically recurring messages, and many formatting options for message content.

    The PageMaster/ex 2003 primary server license includes 5 PageMaster client licenses. Further details on the PageMaster client can be found by clicking here.

  • Stand-Alone Server Integration - PageMaster/ex 2003 will now operate hand-in-hand with PageMaster/sv servers (non-Exchange integrated), providing a fallback path should the PageMaster/ex 2003 server(s) or Exchange itself go down.

  • GC (Global Catalog) Switching - Previous releases of PageMaster/ex 2003 relied on a connection to a specific GC. If that GC should become unavaialble, the PageMaster/ex 2003 service would cease processing messages as it's MAPI session would no longer function. PageMaster/ex 2003 now supports the ability to switch between GCs should the GC to which it is connected go down.

  • SMTP Protocol Upgrades

    Integrated SMTP Sender - PageMaster/ex 2003 now includes its own SMTP sender. Previous versions would transmit SMTP text messages back into Exchange, and exchange would handle the SMTP connection. The deficiency in this process is that PageMaster/ex 2003 has no way of detecting errors in communication with the SMTP server. By maintaining control of text messages througout the SMTP protocol, PageMaster/ex 2003 can detect, retry on, and report any errors in SMTP communication.

    Support for alpha characters in the SMTP Device ID field - PageMaster/ex 2003 now allows more flexibility in how SMTP address templates can be specified for each service provider. This allows PageMaster/ex 2003 to be used for providers that use formats other than pin@domain.com.

 

PageMaster/ex 2003 Version 9 adds the following new features:

  • Calendar Reminder Messaging - PageMaster/ex 2003 now includes the ability to forward Outlook calendar reminders to devices. Using WEBdav, the PageMaster/ex service will actively monitor calendars reminders for selected users. Reminders will then be forwarded automatically to the user's text message device (i.e. pager, cellular phone, Blackberry). On a per-user basis, the reminder messaging may be configured to either always send, or only send when the user's out-of-office flag is set.

    Configuration of Reminder Messaging is quick and simple. It is necessary only to specify an account that the PageMaster/ex service can use to access the calendar folders for the selected users. This account need only have "Receive As" and "Send As" rights on the mailbox store(s) associated with the users.

    The content and format of the reminder messages is completely configurable. Elements of the reminders that can be sent as text messages include:
    • Start Time
    • End Time
    • Subject
    • Location
    • Description
  • Export to PageMaster Client - PageMaster/ex 2003 now supports conversion of Text Messaging Devices from AD (Active Directory) to a PageMaster client device file. This allows a stand-alone PageMaster client to be used for an emergency backup paging console should the network or Exchange experience a downtime.
  • Support for Customized Message Format per Device - PageMaster/ex 2003 now allows the message template format to be customized down to the device level. This means that for each device, you can customize which fields of the message (From, Subject, Message Body) are delivered to the device.

TAP Protocol Upgrades

  • Support for Protocol Specific Message Length Settings. PageMaster/ex 2003 now supports specification of maximum message length for each protocol definition, instead of a single setting for all protocols.
  • Enhanced Security - The TAP engine in PageMaster/ex 2003 has been rewritten in accordance with Microsoft's security initiative. This insures that TAP engine code does not use any legacy APIs or deprecated function calls known to be security concerns.

SNPP Protocol Upgrades

  • Support for SNPP UserID and Password parameters - Many providers are now requiring usage credentials when accessing their SNPP server. Support for these parameters allows PageMaster/ex 2003 to provide these credentials when sending messages.
  • Support for SSL (Secure Socket Layer) connections - Many SNPP providers are now supporting the transmission of text messages encrypted using SSL. This new feature allows PageMaster/ex 2003 to negotiate an SSL connection in order to transmit the message data in this encrypted format.
  • Support for Protocol Specific Message Length Settings - PageMaster/ex 2003 now supports specification of maximum message length for each protocol definition, instead of a single setting for all protocols.
  • Support for the SNPP Level 3 protocol specification - Changes to the SNPP engine in PageMaster/ex 2003 bring it into compliance with SNPP servers supporting Level 3 functionality.
  • Enhanced Security - The SNPP engine in PageMaster/ex 2003 has been rewritten in accordance with Microsoft's security initiative. This insures that SNPP engine code does not use any legacy APIs or deprecated function calls known to be security concerns.
  • Support for Limiting Number of Messages Sent per Connection - In order to reduce spam, many providers are now limiting the number of text messages that can be sent in each connection to their SNPP server. PageMaster/ex 2003 now supports a property that limits the number of messages it will send in each connection session. PageMaster/ex will automatically reconnect as necessary in order to transmit all messages queued.

WCTP Protocol Upgrades

  • Support for WCTP UserID (senderID) and Password (securityCode) parameters - Many providers are now requiring usage credentials when accessing their WCTP server. Support for these parameters allows PageMaster/ex 2003 to provide these credentials when sending messages.
  • Support for SSL (Secure Socket Layer) connections - Many WCTP providers are now supporting the transmission of text messages encrypted using SSL. This new feature allows PageMaster/ex 2003 to negotiate an SSL connection in order to transmit the message data in this encrypted format.
  • Support for Protocol Specific Message Length Settings - PageMaster/ex 2003 now supports specification of maximum message length for each protocol definition, instead of a single setting for all protocols.
  • Support for the WCTP 1.3 protocol specification - Changes to the WCTP engine in PageMaster/ex 2003 bring it into compliance with the 1.3 specification.
  • Enhanced Security - The WCTP engine in PageMaster/ex 2003 has been rewritten in accordance with Microsoft's security initiative. This insures that WCTP engine code does not use any legacy APIs or deprecated function calls known to be security concerns.
  • Improved Proxy Support - The WCTP engine in PageMaster/ex 2003 has been change from use of the WinInet API to the more advanced and robust WinHttp API. This means improvements in throughput, as well as more flexibility in configuring PageMaster/ex 2003 in proxy serviced environments.

SMTP Protocol Upgrades

  • Added flexibility in SMTP address specifications - PageMaster/ex 2003 now allows more flexibility in how SMTP address templates can be specified for each service provider. This allows PageMaster/ex 2003 to be used for providers that use formats other than pin@domain.com.
  • Support for Protocol Specific Message Length Settings - PageMaster/ex 2003 now supports specification of maximum message length for each protocol definition, instead of a single setting for all protocols.
  • Enhanced Security - The SMTP engine in PageMaster/ex 2003 has been rewritten in accordance with Microsoft's security initiative. This insures that SMTP engine code does not use any legacy APIs or deprecated function calls known to be security concerns.

PageMaster/ex 2003 Version 8 adds the following new features:

  • Exchange 2003 Support - This all-new release has been rewritten to support both Exchange 2003 and Exchange 2000 platforms. All permutations of environments are supported, including native and mixed mode, Windows 2003 and Windows 2000 AD, and connector installation on Exchange 2000 and Exchange 2003 servers. Previous version do not run properly on Exchange 2003 and are not supported.
  • Command Line Import/Export - PageMaster/ex 2003 now includes a command line utility for importing and exporting text messaging devices to and from active directory.

The following features were added in PageMaster/ex 2000 Version 7:

  • SMPP Support - (PRO+SMPP Version Only) PageMaster/ex 2000 now supports SMPP (Short Message Peer to Peer Protocol) for sending SMS text messages.
  • SMTP Support - (PRO Version Only) PageMaster/ex 2000 now supports SMTP as a "last resort" fallback protocol for sending text messages to email addresses should all available text messaging protocols fail.
  • COM Interface - Now includes a COM (component object model) interface for sending text messages from another application. Includes a type library file for easy integration into COM compliant applications.
  • 2-Way Internet Support - (PRO Version Only) PageMaster/ex 2000 now supports the ability for 2-way devices to send replies for text messages that originate from internet mail routed through Exchange Server.
  • Enhanced Direct Connect Capability - Now supports failover from one PageMaster/ex server to another for text messages sent via direct connections to text messaging terminals.
  • Message Progress Logging - Individual log files can be generated for each text message request received by the connector. This file will be appended with data detailing the progress and status of the message as it is transmitted to the service provider.
  • Configurable NDR Messages - Text of NDR (Non-delivery reports) for failed messages may now be customized.
  • Automatic Export of Device Lists - All text messaging devices that have been configured within AD may now be automatically exported and backed-up daily at a designated time.
  • Enhanced Monitoring of Service Status - The PageMaster/ex service will now generate a "heartbeat" event at a regular interval. The service can be confirmed as operational by monitoring for the presence of this event.

The following features were added in PageMaster/ex 2000 Version 6:

  • WCTP Support - (PRO Version Only) PageMaster/ex 2000 now supports WCTP (Wireless Communication Transfer Protocol) for sending text messages via an Internet connection.
  • Improved Fault-Tolerance - Additional text messaging engine improvements increase the engine's ability to detect send failures and resubmit failed messages.
  • User Configurable Message Format - The format of the text messages are now entirely user configurable.
  • Queue Viewer (PRO Version Only) - A viewer is now included for the connection queue, the queue of pending and active connections to messaging service providers and terminals.
  • Addressing Improvements - Additional options permit more granular adjustment of routing of message requests to multiple PageMaster/ex 2000 connectors based on parameters in a device's email address.
  • Unique PINs for Each Protocol - PageMaster/ex 2000 now supports the ability to use different PIN numbers for the same device depending on the protocol used.
Latest News

PageMaster/ex 2019 v1 now supporting Exchange 2019 has been released and is available for download. Please contact sales for further information or to obtain an evaluation.