Document #350, Setup and Troubleshooting of GoldMine 95 & Alpha-Numeric Paging
Covers all versions of GoldMine
For GoldMine to send a message to an alpha-numeric pager, you must know the terminal telephone number (usually an 800 number) and the terminal PIN number for your pager. Most, but not all, pager companies provide this dial-in capability. Please contact your pager company to determine if they offer this service and what terminal telephone number and terminal PIN number should be used. GoldMine can also send an E-Mail to the pagers E-mail address.
GoldMine has a profile named "Pager PIN" which can be used to store a pager PIN number for a contact records pager. In the notes of this profile, the terminal phone number should be entered.
To aid in troubleshooting, you can keep the pager status window from minimizing you can add the following line to the [GoldPage] section of the username.ini file (i.e. - Mark.ini):
ShowStatus=1
Setup
1. Select E-mail|Send Pager Message|Pager Info. Enter the Pager PIN and Terminal telephone number and "80" for Terminal's maximum character width.
2. Click the Modem Setup Tab. While GoldMine 95 uses 32 bit TAPI to dial for autodial and synchronization, it accesses the modem directly to send pager messages. Select the COM port where your modem resides and “300,e,7,1” for Modem Settings. Leave Modem Initialization blank.
3. Try sending a page. If the page is sent successfully, then the settings are correct, otherwise proceed to step 4.
4. If the modem dialed using pulse dial rather than touch-tone dialing, Click on the Pager Info. Tab and place a T in front of the terminal telephone number.
5. If the operation fails, click the Modem Setup Tab. Enter the following for Modem Initialization
"S37=3-J0\Q0\N0\V1B0&C1&D2" (note all 0's are zeros). Attempt to send a page again.
6. If the operation fails, click the Modem Setup Tab. Enter the following for Modem Initialization
"S37=3-J0\Q0\N0\V1B1&C1&D2" (note all 0's are zeros). Attempt to send a page again.
7. If the operation fails, consult your modem documentation on what initialization string should be used to set the following parameters:
In the GoldMine directory, there are two log files that can help you to troubleshoot some of the errors you may be encountering when paging, GoldPage.log or GoldPage.ta. The GoldPage.log might look similar to this one:
PageMart Wireless Services Nationwide. Wireless Services SDK.
19951103. 09:23:34:33 - Log Opened. Transaction 0x11c70000
19951103. 09:23:34:33 - SDK module name I:\LIVE\PMSDK16.DLL
19951103. 09:23:34:33 - SDK file date Wed Aug 30 23:24:20 1995. Size 77131
19951103. 09:23:34:38 - Port opened: Speed 300, Parity: EVEN, Data bits 7, Stop bits 1
19951103. 09:23:34:44 - Port 'COM3'. Terminal no. '9,9,1-800-555-1212'. Pager ID '12345678'.
19951103. 09:23:34:44 - Message text follows
19951103. 09:23:34:44 - Hi! This is a page from Mark!
19951103. 09:23:34:44 - Sending preinit: 'Z'
19951103. 09:23:35:81 - Dialing: '9,9,1-800-555-1212'
19951103. 09:24:00:20 - Connection found
19951103. 09:24:00:20 - Sending parameter 1
19951103. 09:24:08:65 - Parameter 1 acknowledged
19951103. 09:24:08:65 - Sending parameter 2
19951103. 09:24:09:31 - Parameter 2 acknowledged
19951103. 09:24:09:37 - Sending packets
19951103. 09:24:09:48 - Transmitting packet 0
19951103. 09:24:12:06 - Parameter 3 (ACK) received for packet 0
19951103. 09:24:12:06 - Message was successfully sent
19951103. 09:24:12:11 - Hanging up
19951103. 09:24:14:64 - Log Closed. Transaction 0x11c70000
Explanations of Parameter Errors To Aid In Debugging
Error regarding Param 1:
(common error)
Could not log into terminal correctly. Did not receive proper acknowledgment from terminal. Check modem initialization string, try another modem. Almost all paging services use Comm settings of 7,e,1. This parameter will be returned if they are using 8,n,1 with such a service.
Error regarding Param 2:
(rare)
Connected and started login procedure but did not complete process. Check and double check password, other settings, and check modem initialization string. Rare possibility, terminal system is being worked on, (i.e. PageNet has well over 200 lines coming into paging equipment and technicians are there all day working on the equipment). Might have hit a bad trunk.
Error regarding Param 3:
(common)
Connected and logged in, SENT MESSAGE, no acknowledgment from terminal. Common reasons for error:
Wrong PIN. Check again.
Right PIN but user prepended area code. Service may not need area code in front of PIN. Right PIN but dialing wrong terminal. (i.e. PageNet has ~600 terminals, PIN will work on one only) Slow/busy terminal, time-out before receiving response. Line noise interrupted before receiving acknowledgment from terminal.
PageMart SDK Errors and Result Codes
Result Description
SUCCESSFUL = 0 The result of the transaction was successful
UNSUCCESSFUL = 1 General no-success code
UNSENT = 2 Message not sent
NO_PORT = 3 Communications port not found
NO_MODEM = 4 Modem not found on communications port
NO_DIALTONE = 5 Dial tone not found
NO_CONNECT = 6 No connect response received from the modem.
BUSY = 7 Busy signal received from the modem.
NO_IDEQUAL = 8 No Parameter 1 (ID=)
NO_BRACKP = 9 No Parameter 2 (ESC ]p)
NO_ACK = 10 No Parameter 3 (ACK)
CANCELED = 11 Transmission Canceled
Diagnostic Procedures for Result Codes
This section is designed for troubleshooting unsuccessfully sent messages. Errors and solutions are straightforward and should greatly assist you in diagnosing and correcting the problem.
Result 00 Successful
This is the result assigned to message that were successfully sent. This Result code will only be found in the Log File Management Window. This is an informative message, not an error code.
Result 01 Unsuccessful
Result one is a generic error code that is currently unused.
Result 02 Message Unsent
Result 2 is automatically assigned to messages that have been placed in the Queue but have not been sent. This is an informative message, not an error code.
Result 03 Port Not Found
Result 3 occurs when the wrong COM Port has been selected or the COM Port is being used by another communications program.
Result 04 Modem Not Found
Result 4 occurs when your modem is either:
1) Not connected to your computer
2) Not receiving power
3) A wrong COM Port has been selected
4) or the COM Port is being used by another communications program
Check the connections between the computer and the modem. If they are loose or disconnected, firmly reconnect them. Check to see of the modem is receiving power. If the modem is not receiving power, check the connection at the modem and at the plug. Reconnect them if they are unplugged or loose.
Result 05 No Dial Tone
Result 5 occurs when the modem is not detecting a dial tone.
1) Check the connection of the phone line at the modem and at the phone jack. If they are disconnected, reconnect them.
2) Check to see if the phone line is currently working. If it is not, contact your local telecommunications expert to repair your phone line.
Result 06 No Connect
Result 6 occurs when the following is detected:
1) Your terminal is busy and can not connect at this time.
2) Your modem is not plugged into the phone line (See: Result 5).
3) Your modem is having trouble connecting at 300 Baud. This can occur on 9600 and 14,400 baud modems.
4) This can be corrected by entering the correct initialization string for your modem. These initialization strings can be found by:
· Looking for it in your modem documentation
· Calling your modem manufacturer
5) The Terminal may be inactive. Messaging companies incur occasional down time as they make upgrades and repairs to their Terminals.
6) You may have selected the wrong number for your Terminal Access Number. This number will not be the same as your pager number and should sound like a fax machine connecting.
7) Retries = 0. Increase retry limit to 1 or greater.
Result 07 Miscellaneous Error
Result 7 is reserved as a miscellaneous error code, you should not get this error.
Result 08 Parameter 1 Not Found
Result 8 occurs when the terminal is not allowing the SDK to log on to the terminal system.
1) The most common cause is that your modem is having trouble connecting at 300 baud. This can occur on 9600 and 14,400 baud modems and can be corrected by entering the correct initialization string for your modem. These initialization strings can be found by:
· Looking for it in your modem documentation
· Calling your modem manufacturer
2) It is also possible that you are not dialing the modem access number. Check to see if the number you are dialing sounds like a fax machine connecting. If you hear a voice asking for you ID number, this is not the correct number. Call your service provider and ask for the modem access number to their terminal.
Result 09 Parameter 2 Not Found
Result 9 occurs when the Terminal Logon was not accepted. This indicates that:
1) Your Terminal is requiring more information than the SDK is sending.
2) Your messaging service provider is not completely adhering to the alphanumeric messaging protocols. (Please call PageMart Technical Support Services)
3) It is also possible that you are not dialing the modem access number. Check to see if the number you are dialing sounds like a fax machine connecting. If you hear a voice asking for you ID number, this is not the correct number. Call your service provider and ask for the modem access number to their terminal.
Result 10 Parameter 3 Not Found
Result 10 occurs when a message is not being accepted by the Terminal.
Your message may be exceeding the length (number of characters per message) of the service provider's limits. Make sure that you have selected the correct maximum length your service provider allows.
1) Your PIN Number was invalid. If you use multiple service providers, make sure you have selected the correct service provider for the PIN number.
2) The Terminal is currently not accepting messages. Try to send your message later.
3) Call your service provider and ask them to send you a test message. This will help determine if the problem lies with your service provider or with having an invalid PIN Number.
Result 11 Transmission Canceled
Result 11 occurs when you manually cancel a transmission of a message while the message is in progress.
Copyright (c) 2002 FrontRange Solutions Inc.
All rights reserved. You may use this document for personal and informational (non-commercial) purposes, provided that the copyright notice and all other notices and permissions appear in all copies, the document is not copied or posted on any network computer or broadcast in any media and modifications are not made to the document. Use for any other purpose is expressly prohibited by law, and may result in civil or criminal penalties.
The information contained in this document is provided “as is” without warranty of any kind. To the maximum extent permitted by applicable law, FrontRange Solutions disclaims all warranties, either express or implied, including warranties for quality, accuracy, merchantability, fitness for a particular purpose, title and non-infringement; and in no event shall FrontRange Solutions or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of profits or data or special damages, even if FrontRange Solutions or its suppliers have been advised of the possibility of such damages.