readme

g-page 是一款客户端/服务器应用程序

   program. You can use wildcards for the file, for example the following are all fine:

*.mydata
mydata.*
*fubar.txt
fubar.t*

Any wildcard searches allowed by your shell should be fine.

You will then need to tell g-page what to do with the target file after it has been sent 
to the pager. You can delete the file, have it renamed or do nothing. If you rename the 
file g-page prepend the file with a r. and append a long number to the end of the file. 
(This number is the number of seconds since Jan 1 1970, it's rather long but I wanted 
something that would be unique ) For example, if I send a file named pagefile.msg and 
choose the rename option, the file will be renamed to r.pgfile.msg.1000077300. Of course 
the number at the end will be different for you.


Now you need to tell g-page who to send the page to. You can either select a name from 
the main receiver list, or you can include the name of the receiver or group as the first 
line in the target file. This name must be an exact match for one that you have setup in 
your receiver list. For example lets say you have a group called MyGroup. If you have a file 
with the contents:

MyGroup
This is a test page

g-page will send the message "This is a test page" to all the members of the group MyGroup. The 
page data cannot exceed 1000 characters or g-page will truncate the message.

SET TIME - Here is where you will define the time when g-page will attempt to send your page. 
	   You can set it to happen once or have it happen as a recurring event. If you set 
 	   the "manual" option then you can define auto page to execute every XX minutes. If
	   you leave the manual time set as zero g-page will default to executing this event every 
	   10 seconds. You can change the default value under the Pref->Auto Page from the toolbar.

PARSE OPTIONS - These settings allow you to "fine tune" the data you send to your pager. You can 
leave the default option of "send entire file" or you can choose to parse sections from the file and
only send those sections. It's important to note that the fields start at zero, so if you wish 
to send out the first 100 characters set field one to start at zero and end at 99. You can overlap
fields if you wish. A parsed field must have an ending field greater than the starting field.



                               2 WAY WCTP FEATURES
 

	
g-page supports sending canned replies to a 2 way wctp pager, as well as retrieving a reply sent 
from a two way pager.

SENDING MULTIPLE CHOICE MESSAGES 

Under the Utilities option on on the main menu you can
select Utilities->2 way response options from the main menu, or right click in the message box
and select select 2 way response from the popup menu. This should popup the 2 way message response
options dialog box. You will need to add messages to the database before you can send them. This
is done by clicking on "Add" then typing in the message followed by clicking Save to add the
message to your current list. You can also edit or delete a message using the proper buttons
from the toolbar.

If you wish to send 1 - 3 message reply options along with a wctp page you need to click on the 
message you want to send to select it, then drag and drop it into an open slot. Once you have 
your replies in the slots you will need to click on the "Activate" button on the toolbar, you 
will see the Activation Status light at the far right hand side of the toolbar turn from red
to green. At this point any wctp page you send to a 2 way pager will send your custom message
replies along with it. To de-activate your custom replies simply click on the deactivate 
button. Note - The custom replies will only be sent to a pager that has 2.0 paging selected
under WCTP Options in the Add/Edit receiver dialog box.

MANAGE 2 WAY REPLIES 

Click on Maintenance->Msg Replies on the main menu to bring up the 
Manage 2 Way Replies dialog box. From this dialog you can view all the messages which have
been sent to a 2 way WCTP pager, as well as the status of each message and replies, if 
they exist. 

When a message is sent to a 2 way wctp pager it will show up in the list of outstanding messages
in the upper list box. The message will have a "U" in the status box to signify that it has
not been confirmed yet with regards to delivery. To check for delivery status, as well as for
any replies, select the message from the list of outstanding messages and click on the "status"
button at the bottom of the dialog. You will see a message in the middle of the dialog box 
next to the Status: label which says "Connecting with wireless service - please wait" this is 
where g-page will report back status of each message. If the message delivery has not been 
confirmed you will get a notice telling you there is no data from the wireless service. If the 
message has been confirmed delivered the "U" in the status box will change to a "D" to 
signify that the delivery has been confirmed. If a reply has been sent back the message will be 
removed from the top dialog box and entered into the "Saved Replies" dialog box on the bottom, 
along with the actual reply. These messages will stay here until you manually delete them. 

Note - The time stamp that gets loaded into the saved replies is the time when you got the
reply back from the messaging service. This does not reflect the time the reply was actually
sent back from the pager.

Note - g-page will only allow you to query for status and replies from pagers which have
2.0 paging selected under WCTP Options in the Add/Edit receiver dialog.



                        CLIENT DATABASE FILES

	There are 12 files that the gpage client uses:

RECEIVER.dat:
	This contains all of the info for the wireless receivers/pages/phones.

SERVICE.dat:
	This contains all of the data for the paging services you have stored.

CONFIG.dat:
	This holds your user preferences as well as your tcp/ip settings along 
	with your email settings. This file MUST reside in ~/.gpage

GROUP.dat:
	This holds all the information for your pre-defined groups

MSG.dat
	This file holds all of the pre-defined messages you have created

IDS.dat:
	This file keeps track of the id's the software uses to associate
a pager with a service. It stores the next available id and keeps track
of id's that get recycled when a pager or service is deleted.

SCHED_DB.dat:
	This file contains information about any scheduled pages you might have.

log.gpage:
	This file holds all the stored logs from pages sent.

2way_log_gpage:
	This file holds all the two way messages sent to a 2 way wctp pager
which have not been replied to.

AUTO_SCRIPT:
	This file holds the info from your last autopage settings. 

reply.gpage:
	This file holds the replies sent to a 2 way wctp pager

TWO_WAY_RESPONSE.dat:
	This file holds all the canned message replies you have stored.

All of these files are comma delimited plain text and can be edited by hand, 
but be warned, at this time g-page is not very forgiving and if you munge one 
it will cause the software to not work properly, if at all. It's best to 
use gpage to add/edit/delete things unless you have a good reason. All 
these files can be found in your ~/.gpage directory


                        SERVER DATABASE FILES

	There are 5 files that the gpage server uses:

SCHED_ID.dat:
	This is the file where all the id numbers for scheduled pages are kept 
	and recycled.

gsched_id.dat:
	This is the data file for pages that are scheduled and when they need to 
	go out.

gsched.dat:
	This is the file that contains the actual scheduled pages and all of the
	information needed to send it.

gpage_sched_log.dat:
	This is the log file for scheduled pages which have been sent but have
	not been queried by the client.

server_log.dat:
	This file holds all the auditing data from the server when it's run in
	auditing mode. This includes the ip address from which the message originated
	and the message info.

These files will reside in the ~/.gpage directory of the server.

                       WHAT ELSE DO I NEED TO KNOW

1) The client logs status updates from the server in a file
called g-page.log which is stored in your ~/.gpage directory. This file is used 
for debugging and can contain useful information if things are not working for 
you. 

2) The client creates a FIFO pipe for talking to the status line 
in the directory you run it in. If gpage should die for some reason
you might see a file named pcclient_xxx in your /tmp directory. 
(xxx is the process id for gpage.) You can delete that file. If gpage 
exists normally the file gets deleted automatically.

3) The CONFIG.dat file must reside in your ~/.gpage directory. All other
database files can reside anywhere on your computer. If CONFIG.dat is not
in the ~/.gpage directory then g-page will think you are running the software
for the first time and it will create a new CONFIG.dat with the default values.


                                 HACKERS

	The code for the interface was all generated by Glade and is not the
prettiest thing to slog through. Glade does a great job of building an
interface, but it's totally void of comments. It's really rather straight 
forward though and once you dive into it you can find stuff rather easily.

If anyone wishes to help I would be happy to have it. One of the biggest needs 
right now is for someone to do the documentation properly. I would like to have a 
nice html help file done by someone with some proper writing skills (which I am 
lacking :) as well as some html talent. I promise to let you put your name all 
over the place if you want to help. 


SNPP INFORMATION

Here are some addresses and port numbers of some of the service providers
who support snpp. I can't promise you this information is correct but I believe
it is.

Company:          SNPP ADDRESS          PORT

AirTouch/Verizon  snpp.airtouch.com     444
Nextel   	  pecos.nextel.com   	444
Pagemart:  	  pagemart.net 		444
Skytel            snpp.skytel.com	7777
Metrocall         snpp.metrocall.com    444
Propage           page.propage.net      444

WCTP INFORMATION

Contact your paging carrier to see if they provide support for the 
WCTP protocol. At this time I believe that Arch Wireless, Skytel, 
Metrocall and Weblink Wireless do.