|
|
In the NotePager Net Admin program, select the 'Settings' object found underneath the 'Logging' object. Make sure 'Log to Disk' and 'Detailed Log' are both checked. Apply your changes. You can view the dialer's log file by selecting the 'Log' object from under the 'Dialer1' object, which is found under the 'Connectors' object. Next, send a test message and then review the dialer log. Here are failure messages for the dialers and their possible causes:
Unable to send dialer init string - the dialer init string was sent to the modem, but not accepted. Verify the syntax of the init string, or try a new one.
Unable to send carrier init string - the carrier init string was sent to the modem, but not accepted. Verify the syntax of the init string, or try a new one.
Unable to connect to carrier - the dialer didn't receive a 'CONNECT' message from the modem. This is usually caused by a wrong phone number, incorrect modem settings, or improper init string.
Checksum error - your message was transmitted to the carrier, but the data received didn't match the data you sent. This can be caused by a bad connection or improper init string.
Bad message content - your message was received by the carrier without any errors. However, the carrier rejected the message due to invalid data in it. This is almost always caused by an incorrect ID/PIN number, or by sending a message that is longer than what the carrier will accept in a single message (try lowering the 'maxchars' setting for the carrier).
Disconnect requested by carrier - this message could mean a number of different things. It is sometimes simply given because the carrier has a limit to the number of messages it will accept in a single session, and wants you to hang up. In most other cases, the terminal has detected a condition which prohibits it from continuing to accept messages, and wants to terminate the session.
No response from carrier - somewhere in the middle of transmitting messages, contact was lost with the carrier. This is usually caused by a bad phone connection, or the need for a better init string.
Message retry limit reached - the message has been retried the number of times specified in the global dialer settings, without being sent successfully. The message at this point is marked as bad, and not retried again. Please check the error message previous to this one in the log for causes.
Carrier retry limit reached - This means that a specific carrier has been unable to be reached after being retried for the number of times set in the global dialer settings. Check the log for failure messages prior to this one for more information on how the connection failed. This message is usually due to an outage of service at the carrier or a modem/phoneline/hardware failure. All pending messages currently queued for this carrier are marked as bad, so as not to delay the delivery of message to other carriers that are still accessible.
