Troubleshooting the Script File
The following troubleshooting information assumes that the Async gateway functioned properly until a script was implemented. You might be facing any of the problems listed below after its inclusion.
The Gateway Is Not Dialing
The Gateway Is Not Answering
The Script Is Not Executing
The Gateway Is Not Dialing
If the Async Gateway is not dialing, verify the following:
- Modem commands are followed by "/r" in the script. Check to see if this has been appended to the dialing instructions, and ensure that it is within double quotes (""). See Sample Script for Initialization and Dialing for more information on using scripts for dialing.
- Ensure that the script has reached its dialing instructions. If necessary, use log comments to confirm the path taken in your script.
- Check the Remote Phone Number field in the Domain Connections screen. If the field is blank, the gateway cannot not dial. If you choose to embed dialing instructions within a script (to avoid putting the phone number in the Remote Phone Number field), place a space in the field.
- When dialing, if the message No Dial Tone appears in the log (you might even hear a dial tone from the modem's speaker), you might be attempting to redial while the line is still open from a previous dial attempt. Try hanging up before dialing again. You should wait for a few seconds before and after issuing a hangup command. An example of such a scenario is included in Label 4 of Sample Script for Initialization and Dialing.
The Gateway Is Not Answering
The Async Gateway might not be responding because of the following reasons:
- The modem might not be initialized. Check the status of the Auto Answer field. You might also need to define a modem for the port even if you plan to initialize and dial from a script. If the port has a modem definition, the gateway automatically initializes the port or modem on starting the gateway.
- The Async Gateway does not listen to incoming calls while executing a script. To specify the time interval between retries, we recommend that you vary the time specified in the Time Between Retries field in the Calling Schedules and Intervals dialog box. For more information, see Defining a Domain Connection.
The Script Is Not Executing
Verify the following if the script is not executing on your gateway.
- The name of your script file must be either default.scr or link.scr.
- Ensure that the script is placed in the appropriate directory. If you are utilizing a link-specific script, it must be placed in the link directory under gwout. Check the dates on those files to make sure that you are working with a current link directory. See Scripting Language for more information on using the scripting feature.