Super Pager Version 1.8 - Download Current Version
[Top][Introduction][Installing][Setting Up][Description][Features][Network][Register][Future]
This is a ShareWare product. The ShareWare version is limited to 30 characters. Please support the shareware concept and register. Registration fee for Super Pager: $25 - For Standalone OS/2 PM Pager (pmpage.exe) (OS2) $25 - For Standalone Windows pager only. (winpage.exe). (Win) Registration fee for Super Pager Network: $100 - Support for 15 pagers. Advance 32 bit Network Paging Server with LAN Server support(Windows NT, OS/2) E-Mail Gateway (Windows NT, OS/2) TCP/IP SNPP Gateway (Windows NT, OS/2) TCP/IP SNPP clients (Windows, OS/2). Lan Server clients for (Windows, OS/2) Web Server Paging for (Windows NT, OS/2 - Web Server Needed) Site license for all Network Clients (1 building) $200 - Super Pager Network with Support for a total of 40 Pagers. $300 - Super Pager Network with Support for a total of 100 Pagers. $400 - Super Pager Network with Support for unlimited Pagers. When you register; you will receive a activation key that will unlock the super pager software and lift the 30 character limit.
If you wish to pay by charge card look at the ORDER.TXT file for more information or use BMT's secure order form. If you wish to pay by check send it to the address below. Borghese Software Engineering 981 Hillsdale Dr. Columbus, OH 43224 Please make check Payable to: Brent K. Borghese All questions and technical support is through e-mail. I would like to here your comments. Please send them to: "Brent K. Borghese" SuperPager@bmtmicro.com Super Pagers Home Page: http://www.bmtmicro.com/catalog/superpager/ or http://brent.dispatch.com/sw/sp/ (Beta Version availible)
You are free to distribute this shareware version of Super Pager as long as the following conditions are met: o The distributed archive must contain ALL the files listed above, and no others. o The contents of this archive are NOT MODIFIED in any way. o This version is not to be sold. However, a reasonable disk copying fee is permitted. o This version is not to be bundled with a commercially sold package without permission from the authors.
Radio paging is somewhat taken for granted, because of the wide availability and wide use of paging products. However, the actual delivery of the page, and the process used (especially in wider area paging) is somewhat complicated. When a user initiates a page, by dialing a number on a telephone, or entering an alphanumeric page through some input device, the page must ultimately be delivered to some paging terminal, somewhere. In most cases, this delivery is made using TAP (Telocator Alphanumeric input Protocol, also known as IXO). This protocol can be a somewhat convoluted, and complicated protocol using older style ASCII control characters and a non-standard checksumming routine to assist in validating the data. Even though TAP is widely used throughout the industry, there are plans on the table to move to a more flexible "standard" protocol referred to as TME (Telocator Message Entry Protocol).
The recently-added level three enhancements have been engineered for use, specifically, with acknowledgment-based paging. With the recent advances in wireless technology, two-way paging is fast approaching reality--therefore creating a need for a workable end-to-end acknowledged protocol. Two-way messaging, however, opens up several new areas of unpredictability. The most pronounced is the subscriber response time. Although deliveries from host to subscriber, and subsequent receipt-acknowledgments happen in a rather predictable manner, it is impossible to know when the subscriber will physically pull the unit out, read the message and respond to it. Therefore, it could well be cost prohibitive to conduct such transactions online using a phone line as medium--especially an 800-number. This makes the Internet an extremely attractive alternative because of its (generally) usage insensitive nature.
However, acknowledging the complexity of task, and flexibility of the current protocols (or the lack thereof), the final user function is quite simple: to deliver a page from point-of-origin to someone's beeper. That is the simple, real-time function that Super Pager addresses.
[Top]
Features:
Features
Unzip the zip file to a directory called \TMP From a command prompt run SETUP2.EXE
Unzip the zip file to a directory called \TMP From Windows program mamager do a File->Run.. and type \TMP\SETUP.EXE
[Top]
The first section of the file is the globle section. All items in the globle section are optional and are not required. The first line of this section has the keyword GlobalSection.
GlobalSection LogFileName = "X:\LogFileName.TXT" - If you wish to override the default log file(LOG.TXT), this line can be added with the new directory and file name. MapCodePage = CP437|CP850 - This will get the character translation CP437 is for the USA, and CP850 is for multilingual. In OS/2 super pager will set this for you, so it is not needed. In windows you have to set the manualy. The code page will translat character like "ea","EA", A with a dot on top and more. LogMessages = Enabled|Disabled - This will let you log the messages that are sent to the pagers. MaxReTrys = 10 - The number of times super pager will try to send the page to the paging system. 0 Will try forever. The default is 10 DialingPrefix = "9" - The dialing prefix is add to the begining of all phone numbers dialed. QueueSize = 100 - The max number of pages that can be queued at one time. If there are a large number of people in a group(>90) the QueueSize can be increased to meet the need.
TcpPort = 5100 - This is the default TCP/IP port. If the pager system does not have a port number this number will be used. The SNPP Client is being used the TCP/IP port number. This number can be anything from 2000 to 30000. We picked 5100. HostName = "SnppServerHostName" - This is the default TCP/IP host name If the pager system does not have a host name this name will be used. This host name is the node name of the computer running the SNPP Gateway(SNPPD.EXE or SNPPD32.EXE) LanServerName = "ServerName" - This is the default Lan server host name. Name of the node that has the Lan server network running on it and its should also be running the PAGED.EXE program. ReadNamesFromServer = Enabled|Disabled - This option is for Super Pager Network. The default is enabled. If more then one paging server is being used this options needs to be desabled. If this is not disabled the list of names read in from the INI file will be overwiten. ClientType = Slim|Full - By default the Lan Server Clients can page now, delay in min or delay till a certain time, this is ClientType = Full, If you only want people to be able to page now set this to Slim. DisplayGroupName = "Group Name" - This is one of the Group names below. If there is a large number of pager, they can be grouped and a smaler list of names displayed in the web, PM and windows clients.
The next section of the file is PagerSystemsSection it will be used to setup each person's pager system and type. The first line of this section has the keyword PagerSystemsSection. Next, if you are using a numeric pager you must have a setup for the numeric pagers. Here are the commands needed(The | separates possible options): [Numeric] - If there will be numeric pager being paged, there must be a [Numberic] section to setup the comm port. ModemInitString = Auto|"AT Z" - For most modems this can be set to Auto. If Super Pager can not detect the modem setup a manual init string can be entered here. tones to send the page. Port = "COM1" - The Comm port your modem is on. Port = "COM2" - If using the paging server more than one Port line can be used to handle more pages. There is a max of 20 modems Baud = 1200 - The baud rate the modem will be using. Parity = None|Odd|Even|Space|Mark - Parity to set the comm port to. On a numeric page this should be set to None DataBits = 8|7|6|5 - Data bits to set the comm port to. On a numeric page this should be set at 8. StopBits = 1|2 - The number of Stop bits to set the port to. This should be set to 1. Next setup each pager system you will use. There can be a total of 50 different paging system. Here are the commands needed. [Name of System 1] - This is the name of the pager system. For each pager system there will be a header. ModemInitString = Auto|"AT Z" - The init string for your modem. On a alpha pager the modem will need to be setup to hangup when DTR is droped(&D2) and the host baud rate to match connect speed(S37=0). For a direct line to a TAP device set this to "" Port = "COM1" - The Comm port your modem is on. Port = "COM2" - If using the paging server more than one Port line can be used to handle more pages. There is a max of 20 modems Baud = 1200 - The baud rate the modem will be using. Parity = None|Odd|Even|Space|Mark - Parity to set the comm port to. On a pager system that uses TAP it should be set to Ever. UCP should be set to None. Please note your pager system might be different. DataBits = 8|7|6|5 - Data bits to set the comm port to. On a numeric page this should be set at 7. TAP it should be set to 7. UCP should be set to 8. StopBits = 1|2 - The number of Stop bits to set the port to. This should be set to 1. MaxMessageLength = 230 - The maximin size of the message that the pager system can take in at one time. SystemPhoneNumber = "690-1234" - The phone number of the pager system. For a direct line to a TAP device set this to "" SystemType = Tap|TapM|Script|UCP - The type of pager system. If the pager system support TAP. Set the SystemType to Tap. There is also manual mode TAP avalible(TapM), this does not need to be used every. If the pager system does not suport TAP a script can be used. UCP (Universal Computer Protocol) format is also a valid system type. You must ask you pager system what they support. TapPassWord = "PASSWORD" - If SystemType = Tap you can add a TAP password. In the USA most of the time this is not needed and can be left out. ScriptFileName = "c:\pageos2\systema.src" - If SystemType = Script then a script file is needed. Refere to the Non-TAP paging systems for more information. MultipleMessageMode = Enabled|Disabled - If your TAP paging system support multiple pages per call set this to Enabled. Most pager systems do. MaxMessageLength = 230 - The maximin size of the message that the pager system can take in at one time. On the Numeric it is not used MaxPagesPerConnection = 20 - Maximin number of pages sent to a paging system before hanging up and redialing to send more. NOTE: If the paging system is setup using a script the PagerType must be to Alphanumberic.
A list of Typical modem Init Strings
These next options are for super pager network and are not required. If there are more then one paging servers in use, each user's pager can point to a different paging server. OverrideTcpPort = 5100 - This option overrides the TcpPort option in the global section. And If the SNPP Client is being used the TCP/IP port must be entered. This number can be anything from 2000 to 30000. We picked 5100. OverrideHostName = "SnppServerHostName" - This option overrides the HostName option in the global section. And If the SNPP Client is being used the TCP/IP host name must be entered. This host name is the node name of the computer running the SNPP Gateway(SNPPD.EXE or SNPPD32.EXE) OverrideLanServerName = "ServerName" - This option overrides the LanServerName option in the global section. And the server with this node name has the paging server running on it. The next section of the file is the Name Section it will be used to setup the people with the pagers. In this version there can be a total of 1000 names. The first line of this section has the keyword NameSection. Next setup each person's pager system and type. Here are the commands needed. [Bob Smith] - The name of the user PageID = "630-2222" - The ID of the pager or the Pagers phone number PagerType = Numeric|Alphanumeric - What type of pager SystemName = "Name of System" - The name of the paging system, these are the same names you setup in the PagerSystemsSection A optional item is: Group = "EveryBody" - If this uses is to be in a group you can add this line. If the uses is in more than one group create a line for each group. SuppressNameDisplay = Enabled|Disabled - The default is Disabled. If there is a persons names that you do not want to show up automatically in the paging list box add this line and set it to Enabled. A example of its use might be, a high up person in the company has a pager and you do not want just any body paging him/her. So you Enabled this and made special version of the page.ini file for one of the pager clients you will then only have a few person be able to page them. The next section of the file is the Group Section will be used to setup groups of people that you can page all at once. The first line of this section has the keyword GroupSection. Next setup each group. Here are the commands needed. [Group Name 1] Name = "Bob Smit" Name = "Mr. Bill"
If your system does not support the TAP(System Type) protocol you can setup a script configuration file. It is used to send the pages to your pager system. Not all pager systems are the same so some tuneing might need to be done. The file is in the format of Send String, Expect String. There are some esc sequences in the send string, they are shown below: \r - Sends a return(0x0D) \n - Sends a return and a line feed(0x0D,0x0A) %i - Sends the persons pager ID %m - Sends the message %p - Sends the systems phone number %d - Two second pause ^a - Sends a control charature, the charature can be form a-z There is one esc sequences in the expect string, it is shown below: \r - Expect a return(0x0D)(^m does same thing) ^a - Expect a control charature, the charature can be form a-z Sample Script file
By default all pages are loged to: LOG.TXT it can be changed by using the LogFileName = "X:\LogFileName.TXT" command in the Global Section.
Run pmpage.exe from the pager directory. Select name from the list, enter the message and click page button. If the pager server is running the PM pager will send a message to the server and the server will page the person.
Run paged.exe from the pager directory. Once the pager server is running the pager clients can be run to submit pages to the server. There are two clients included a command line version and a pm version.
Once the paging server is running the command line client can be run. The format of the command is as follows: doscli [-nadils args] [@filename.txt] id Message or page [-nadils args] [@filename.txt] id Message n Page now - Default page -n "Bill" "My message" page "Bill" "My message" a Page at a date(MM-DD-YY) and time(HH:MM) page -a 08-12-95 15:55 "Bill" "My message" d Delete a page at date(MM-DD-YY), time(HH:MM) and ID page -d 08-12-95 15:55 "Bill" page -d 00-00-00 00:00 "" - Deletes all pages i Page in xxx minutes page -i 10 "Bill" "My message" l List page log file: page -l index index: 0: Show last 1K of log file - Default 1: Show 1K of log file, starting at EOF-2K s List # of pages in Now queue and # of pages in At queue page -s type type: 0: Short list - Default 1: Full list c Lan Server name page -c PageServer "Bill" "My message" A file can be passed to the command line client. The format of the command is as follows: page @filename.txt page id @filename.txt There are two file formats one with the id and one with out. The file format with the id has two parts, the first line has the id and the message is on the following lines. The file format with out the id has one part the message. NOTE: The dos version was made to run under Windows NT, Windows 95, Windows 3.1 and WinOS2.
The WINPAGE.EXE and WPAGEIP.EXE have optional arguments. There are 2 arguments the first is the name of the person to page and the second is the message. On Windows NT you can page by the command line, no window is displayed. example: winpage "Brent Borghese" "This is my message" Other window programs have the ability to run programs, this give you the ability to add paging to them.
Run pmpage.exe from the pager directory. Select time for page to occur and select name from the list, enter the message and click page button.
[Top]
For OS/2 run paged.exe and snppd.exe from the pager directory. For Windows NT run paged32.exe and snppd32.exe from the pager directory. Once the programs are running the SNPP clients can be run to submit pages to the server. There are two clients included a pm version and a windows version. You will need tcpip installed on all computer used. The windows version is winsock V1.1 compatible program. When setting up the program you will need to select a TCP port to use and a host name or IP address. The setup file for snppd.exe is named SNPP.INI it has the format of: TcpPort = PortNumber Example:
TcpPort = 5100 The files needed to run the OS/2 SNPP Gateway are: PAGED.EXE PAGE.INI SNPPD.EXE SNPP.INI The files needed to run the Windows NT SNPP Gateway are: PAGED32.EXE PAGE.INI SNPPD32.EXE SNPP.INI
The setup the clients you will add two lines to the PAGE.INI. These lines are added after the GlobalSection line, the lines are: TcpPort = PortNumber HostName = "SnppServerHostName" And optionly: DisplayGroupName = "Group Name" Example GlobalSection TcpPort = 5100 HostName = "pagesrv"
Once the paging server and the SNPP Gateway are running the system is ready to receive page message over the network. The supported SNPP clients are OS/2 PM (PMPAGEIP.EXE), Windows (WPAGEIP.EXE), OS/2 command line (PAGEIP.EXE) and a Windows NT/95 command line version (PAGEIP32.EXE). The Windows and PM versions a very simple and need no explanation. Files needed: PMPAGEIP.EXE PAGEIP.EXE PAGEIP32.EXE WPAGEIP.EXE PAGE.INI
The format of the command is as follows: pageip [@msgfile.txt] id Message examples: pageip32 "Bill" "My message" pageip32 @filename.txt pageip32 id @filename.txt A file can be passed to the command line client. The format of the command is as follows: pageip32 @filename.txt pageip32 id @filename.txt There are two file formats one with the id and one with out. The file format with the id has two parts, the first line has the id and the message is on the following lines. The file format with out the id has one part the message. Files needed: PAGEIP.EXE or PAGEIP32.EXE PAGE.INI
Copy wwwpage.exe to your web server CGI-BIN directory, And copy page.htm file to your web server's DOCS directory. The web client will get the list of names from the paging server. From you web browser: http://www.yourserver.com/cig-bin/wwwpage.exe/page.htm Files needed: PAGED.EXE PAGE.INI WWWPAGE.EXE NOTE: IBM's web server
Copy wwwpgnt.exe to your web server \InetPub\SCRIPTS\TOOLS directory, And copy page.htm file to your web server's DOCS(\InetPub\wwwroot) directory. The web client will get the list of names from the paging server. From you web browser: http://www.yourserver.com/scripts/tools/wwwpgnt.exe/page.htm Files needed: PAGED32.EXE PAGE.INI WWWPGNT.EXE NOTE: Microsoft's web server
This is done by adding ?group=DisplayGroupName to the URL. Like: http://www.server.com/cgi-bin/wwwpage/page.htm?group=DisplayGroup Note: The goup name must not have any spaces in it!!!! or If you do not want to use the URL to display a group, you can edit the page.htm file and add %g and then the group name. The %g should be at the beginig of the file. Here is a sample: %gMyGroupName Note: The goup name must not have any spaces in it!!!!
To make your own list of names in the web pager find %p in the page.htm file, the %p can be replaced with: < OPTION > Mr. Bill < OPTION > John Smith Add a < OPTION > line for every name you wish to add.
Inaddition to the other files copyed, copy wwwpage.ini to your web server CGI-BIN directory. And copy pgstart.htm, pgok.htm, pgbad.htm and pgend.htm files to your web server's DOCS directory or to any other directory you want. Edit the wwwpage.ini file it will have the format:
LanServerName = "PagingNode" - If the paging server and the web server are not on the same computer, the web client can send the page over your LAN server network to the paging server. StartingHtmlFile = "c:\www\docs\pgstart.htm" - If you want a custom response after you page OkHtmlFile = "c:\www\docs\pgok.htm" - there are 4 html files you can setup to generate BadHtmlFile = "c:\www\docs\pgbad.htm" - the page. OkHtemlFile is sent if the page was OK. EndingHtmlFile = "c:\www\docs\pgend.htm" - and BadHtmlFile is the file sent if there was a error sending the page to the paging server. HostName = "TcpIPHostName" - If the paging server and the web server are not on the same computer, the web client can send the page over TCP/IP to your paging server. TcpPort = SnppPort - The TCP/IP port that the web client will use to contacted the SNPPD Gateway. Please note that the file names are full path name of the files on the web server. They are not based on your web servers root document directory. If you are running the web server and the paging server on the same computer the LanServerName line can be left out. NOTE: On NT the WWWPAGE.INI is in the InetPub\scrips directory not the InetPub\scrips\tools directory (This is back on directory) NOTE: On OS/2 the WWWPAGE.INI is in the same direcory as the wwwpage.exe file.
The page.htm file is used for basic paging. The pageadv.htm file is used for advanced paging, this being: Page in X minutes, Page at MM-DD-YY HH:MM time and deleting pages.
In the form section of the page.htm add: The Ip address is only added if the host name is not sent.
Run the paged.exe from the pager directory and your OS/2 web server software. To then call up, run your favorite web browser. The URL you will enter will look something like this: http://www.yourserver.com/cig-bin/wwwpage.exe/page.htm Select a name and press the page button.
If your web server is not running on the paging server(paged.exe) the web pager can use your network to send the paging infomation to the paging server. Run the paged.exe from the pager directory on your paging server, and on the OS/2 web server load the wwwpage.exe and the htm files. To change the lan server node name to your paging server's name edit wwwpage.ini and add a line into with the format like this: LanServerName = "PagingNode" To then call up, run your favorite web browser. The URL you will enter will look something like this: http://www.yourserver.com/cig-bin/wwwpage.exe/page.htm Select a name and press the page button.
If your web server is not running on the paging server(PAGED.EXE and SNPPD.EXE, PAGED32.EXE and SNPPD32.EXE) the web pager can use your network to send the paging infomation to the snpp paging gateway. Run the paged.exe and snppd.exe from the pager directory on your paging server, and on the Web server load the htm files and one of the cgi programs wwwpage.exe(OS/2) or wwwpgnt.exe(NT). To change the Host name to your paging server's name edit wwwpage.ini and add a line into with the format like this: HostName = "HostNameOfPagingServerOrAddress" TcpPort = 5100 To then call up, run your favorite web browser. The URL you will enter will look something like this: http://www.yourserver.com/cig-bin/wwwpage.exe/page.htm Select a name and press the page button. NOTE: On NT the WWWPAGE.INI is in the InetPub\scrips directory not the InetPub\scrips\tools directory (This is back on directory) NOTE: On OS/2 the WWWPAGE.INI is in the same direcory as the wwwpage.exe file.
Lan server networks include: Warp Server, IBM Lan Server, Win NT Server, Windows for workgroups and Warp connect peer to peer. To page over your Lan Server network you must have two computers setup and running the network software. A user also must be login to the network to run the paging client.
Run paged.exe(OS/2) or paged32.exe(Windows NT) from the pager directory. Once the program is running. The Lan Server clients can be run to submit pages to the server. Files needed on the server: PAGED.EXE or PAGED32.EXE PAGE.INI
Once the paging server is running on the server the system is ready to receive page message over the network. There are 4 Lan Server clients, a OS/2 PM version PMPAGELS.EXE, a Windows version WPAGELS.EXE, a OS/2 command line version PAGE.EXE and a DOS command line DOSCLI.EXE. The PM and windows versions a very simple and need no explanation. The PAGE.INI file must have the lan server node name in it, The format of the PAGE.INI is very simple it is shown below: LanServerName = "ServerName" - Name of the node that has the Lan server network running on it and its should also be running the PAGED.EXE program. And optionly: DisplayGroupName = "Group Name" Files needed: PMPAGELS.EXE - OS/2 PM Lan server network client PAGE.EXE - OS/2 Command line pager DOSCLI.EXE - DOS Command line pager(Will run on: OS/2 VDM, NT VDM, WFW DOS window, Win 95 DOS window) WPAGELS.EXE - Windows lan server network client. (Will run on: Windows For Workgroups, Win 95, Win NT, WIN-OS/2) PAGE.INI - The setup file Please note that the client will get a list of names and groups from the paging server.
Setup each of the paging server as if you were using one paging server. Next, we must setup the client PAGE.INI file. The first section must look like: GlobalSection ReadNamesFromServer = Disabled Next, we must setup pager systems one for each paging server on your network. Here is a sample of what the PagerSystemsSection should look like: PagerSystemsSection [City 1 Pager Server] OverrideTcpPort = 5100 OverrideHostName = "city1.mydomain.com" OverrideLanServerName = "PG1SRV" [City 2 Pager Server] OverrideTcpPort = 5100 OverrideHostName = "city2.mydomain.com" OverrideLanServerName = "PG2SRV" NOTE: For TCP/IP the options OverrideTcpPort and OverrideHostName are the only ones needed. For Lan server the only option needed is OverrideLanServerName. Next we must setup the users. There must be a entry for all uses on all the paging servers. Here is a sample of what the NameSection should look like: NameSection [Bob in City 1] SystemName = "City 1 Pager Server" [Mike in City 2] SystemName = "City 2 Pager Server"
All technical support is through e-mail. I would like to here your comments. Please send them to: "Brent K. Borghese" brent@dispatch.com Super Pagers Home Page: http://www.bmtmicro.com/catalog/superpager/ or http://brent.dispatch.com/sw/sp/ Borghese Software Engineering 981 Hillsdale Dr. Columbus, OH 43224
Run paged.exe and poppaged.exe(paged32.exe and ppaged32.exe for NT), configure the poppage.ini file with the mail account and send the account a E-Mail. The format of the E-Mail is very simple, in the Subject field put the pager ID or Users name(The names that are in the page.ini file), then enter the message in the body of the E-Mail.
Files needed: PAGED.EXE POPPAGED.EXE PAGE.INI POPPAGE.INI Sample poppage.ini file: [Name of the gateway] - The name of this E-Mail gateway, every gateway has a different name. PollTime = 30 - This is how frequent we will check for new mail(seconds) PopPort = 110 - TCP/IP port number for the POP server. PopHostName = "mail.mydomain.com" - Host name or IP address of POP server. PopUser = "pagersystem" - Mail account user login PopPassword = "PagerPassword" - Mail account passwordNOTE: If the text %%EndPage%% is in the body of the message, no text after the %%EndPage%% will be sent to the pager.
A direct line is a dedicated connection to your paging provider that is connected 24 hours a day. With this type of connection there is no need for modems or dialing up the provider because it is always available.
To setup a direct connection, setup a pager provider and leave the ModemInitString and the SystemPhoneNumber blank. Here is a example:
ModemInitString = "" SystemPhoneNumber = ""
pmpage.exe - Standalone OS/2 PM Pager, Also will acts as a local client to the paging server. pmpagels.exe - OS/2 PM Lan Server Pager client winpage.exe - Standalone Windows pager wpagels.exe - Windows Lan Server client. (Windows for workgroup type network needed for Lan Server) pmreg.exe - OS/2 Registration program(Enters registration info in to INI file) winreg.exe - Windows Registration program(Enters registration info in to INI file) paged.exe - OS/2 Pager server poppaged.exe - OS/2 E-Mail Gateway. Works with any POP3 Mail server. paged32.exe - Windows NT Pager Server. (Does not work on Windows 95) ppaged32.exe - Windows NT E-Mail Gateway. Works with any POP3 Mail server. page.exe - OS/2 Command line client for pager server and lan server. doscli.exe - DOS Command line client for pager server and lan server. wwwpage.exe - OS/2 Web server pager client. (Web server needed) wwwpgnt.exe - NT Web server pager client. (Web server needed) wwwpage.ini - Sample ini file for web paging. page.htm - Sample html file of paging. pageadv.htm - Sample html file of paging with delayed paging. pgstart.htm - Sample html file of the Header for the returned page screen pgok.htm - Sample html file if page was sent correctly pgbad.htm - Sample html file if there was a error sending the page pgend.htm - Sample html file of the footer for the returned page screen snppd.exe - OS/2 SNPP Gateway. (TCP/IP needed) Simple network paging protocol gateway, PAGED.EXE needed snppd32.exe - Windows NT SNPP Gateway. (TCP/IP needed) Simple network paging protocol gateway, PAGED32.EXE needed pmpageip.exe - OS/2 PM SNPP Pager client. (TCP/IP needed) pageip.exe - OS/2 Command line SNPP Pager client. (TCP/IP needed) pageip32.exe - Windows NT/95 Command line SNPP Pager client. (TCP/IP needed) wpageip.exe - Windows SNPP client. (TCP/IP needed with Winsock V1.1) snpp.ini - Sample setup file for SNPP Gateway page.ini - Sample setup file for pager system poppage.ini - Sample setup file for E-Mail gateway. file_id.diz - Description file history.txt - History of modification to Super Pager page.cpp - C Source for client interface page.h - C header file for client interface paged.scr - Sample modem script file for non TAP pager systems readme.txt - Brief info about Super Pager readme.htm - Documentation. This file bg.jpg - Image file pg.gif - Image file pg1.gif - Image file page.ico - Image file paged.ico - Image file poppage.ico - Image file snppd.ico - Image file paged32.ico - Image file ppaged32.ico - Image file snppd32.ico - Image file feedback.txt - Customer Feedback form order.txt - Order form for paying by charge card.
The paging server has a debug option. To enable the option run the program with the debug flag. The line you would enter is show below: paged debug or paged32 debug
If you page by calling a 800 number then entering in a PIN number then the digit message. A script needs to be setup. Set the type script. Try makeing a script with this in it: AT DT 1-800-555-1212,,,%i#,,,%m# NO CARRIER NOTE: If the paging system is setup using a script the PagerType must be to Alphanumberic.
A Typical Init String - ATV1X4
Hayes Compatible 1 - AT&F&Q0&C1&D2M1V1 Adtech Hi-Per 96/96 - AT&F&Q0&C1&D2M1V1 Adtech Hi-Per 96/144 - AT&F&Q0&C1&D2M1V1 Boca Research PM1440 - AT&F&Q6&C1&D2M1V1 Hayes Optima - AT&F&Q0&C1&D2M1V1 Hayes Optima 28.8 V.34 - AT&Q0S36=1S37=0S48=128N0B1&D2 Hayes Ultra - AT&F&Q0&C1&D2M1V1 Intel 9600ex - AT&F\N0\Q0&C1&D2M1V1 Intel 14400 ex - AT&F\N0\Q0&C1&D2M1V1 Practical Peripherals 2400 - AT&F&Q0&C1&D2M1V1 Practical Peripherals 2 - AT&F&Q0&C1&D2M1V1S46=0 Racal-Datacom RMD 3221 - AT&F*Q0&C1&D2M1V1 UDS FastTalk Fax 32 Bx - AT&F&Q0&C1&D2M1V1 Zyxel 1 - AT&F&Q0&C1&D2M1V1 Hayes Compatible - AT&Q0Q0V1X4S7=60&C1&D2S0=0 ATI 2400 ETC - AT&FQ0V1X4S7=60&C1&D2S0=0 AT&T Paradyne - AT%C0\N0Q0V1X4S7=60&C1&D2S0=0 Cardinal 9600 - AT%C0\N0&Q6Q0V1X4S7=60&C1&D2S0=0 Cardinal MVP 144DSP - AT\N0Q0V1X4S7=60&C1&D2S0=0 Intel - AT\N0Q0V1X4S7=60&C1&D2S0=0 Motorola Generic - ATZQ0V1E1%C0\N0&D2 Motorola Lifestyle Modems - ATZQ0V1E1%C0\N0&D2 Motorola Power Modems - ATZQ0V1E1%C0\N0&D2 Motorola Power Cellular Operation AT&F1Q0V1E1%C0\N0&D2 Multitech - AT&E0Q0V1X4S7=60&C1&D2S0=0 Practical Peripherals - AT&Q0Q0V1X4S7=60&C1&D2S0=0 Telebit - ATS180=0Q0V1X4S7=60&C1&D2S0=0 Telebit TrailBlazer Plus - ATS95=0S97=0S106=0Q0V1X4S7=60&C1&D2S0=0 UDS V.3225 - AT\NQ0V1X4S7=60&C1&D2S0=0 US Robotics - AT&K0&M0Q0V1X4S7=60&C1&D2S0=0 Zoom - AT&Q6Q0V1X4S7=60&C1&D2S0=0 Zoltrex - AT%C0Q0V1X4S7=60&C1&D2S0=0 Zyxel 2 - AT&K0Q0V1X4S7=60&C1&D2S0=0 Example for Hayes 28.8 V.34 ModemInitString = "AT&Q0S36=1S37=0S48=128N0B1&D2" Example for US Robotics ModemInitString = "AT&K0&M0Q0V1X4S7=60&C1&D2S0=0"
GlobalSection PagerSystemsSection [Numeric] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = None DataBits = 8 [USA Mobil] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = Even DataBits = 7 StopBits = 1 MaxMessageLength = 230 SystemPhoneNumber = "842-6252" SystemType = Tap MultipleMessageMode = Enabled [SkyTel] ModemInitString = Auto Port = "COM1" Baud = 2400 Parity = Even DataBits = 7 StopBits = 1 SystemPhoneNumber = "1-800-759-6366" SystemType = Tap MultipleMessageMode = Enabled [A Script for USA Mobil] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = Even DataBits = 7 StopBits = 1 SystemPhoneNumber = "842-6252" SystemType = Script ScriptFileName = "page.scr" NameSection [Brent Borghese] PageID = "555-1212" PagerType = Alphanumeric SystemName = "USA Mobil" [Mr. Bill] PageID = "555-1234" PagerType = Numeric SystemName = "Numeric" [Brent with a Script] PageID = "555-1212" PagerType = Alphanumeric SystemName = "A Script for USA Mobil" GroupSection [Page Brent 3 Times] Name = "Brent Borghese" Name = "Brent Borghese" Name = "Brent Borghese" [Page everybody] Name = "Brent Borghese" Name = "Mr. Bill" Name = "Brent with a Script"
GlobalSection TcpPort = 5100 LanServerName = "ServerName" ReadNamesFromServer = Enabled PagerSystemsSection [Numeric] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = None DataBits = 8 [USA Mobil] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = Even DataBits = 7 StopBits = 1 MaxMessageLength = 230 SystemPhoneNumber = "842-6252" SystemType = Tap MultipleMessageMode = Enabled NameSection [Brent Borghese] PageID = "555-1212" PagerType = Alphanumeric SystemName = "USA Mobil" [Mr. Bill] PageID = "555-1234" PagerType = Numeric SystemName = "Numeric" GroupSection [Page Brent 3 Times] Name = "Brent Borghese" Name = "Brent Borghese" Name = "Brent Borghese" [Page everybody] Name = "Brent Borghese" Name = "Mr. Bill"
GlobalSection LanServerName = "ServerName"
GlobalSection PagerSystemsSection [USA Mobil] ModemInitString = Auto Port = "COM1" Baud = 1200 Parity = Even DataBits = 7 StopBits = 1 MaxMessageLength = 230 SystemPhoneNumber = "842-6252" SystemType = Tap MultipleMessageMode = Enabled NameSection [Brent Borghese] PageID = "555-1212" PagerType = Alphanumeric SystemName = "USA Mobil" GroupSection
GlobalSection TcpPort = 5100 HostName = "pagesrv"
TcpPort = 5100
LanServerName = "PagingNode" StartingHtmlFile = "c:\www\docs\pgstart.htm" OkHtmlFile = "c:\www\docs\pgok.htm" BadHtmlFile = "c:\www\docs\pgbad.htm" EndingHtmlFile = "c:\www\docs\pgend.htm"
NOTE: This file is not needed to use the web paging system
GlobalSection ReadNamesFromServer = Disabled PagerSystemsSection [City 1 Pager Server] OverrideTcpPort = 5100 OverrideHostName = "city1.mydomain.com" [City 2 Pager Server] OverrideTcpPort = 5100 OverrideHostName = "city2.mydomain.com" NameSection [Bob in City 1] SystemName = "City 1 Pager Server" [Mike in City 2] SystemName = "City 2 Pager Server"
AT DT %p\r CONNECT \r \r M\r RETURN. %i\r Message, then RETURN. %m\r then RETURN.
Planned enhancements to Super Pager include:
Last Updated: 5-25-1998