| View previous topic :: View next topic |
| Author |
Message |
Eric
Guest
|
 Posted: Wed Apr 28, 2004 1:52 pm Post subject: "Waiting for protocol initialization" |
 |
|
Hello,
After I connect to the carrier, the log tells me that it's waiting for protocol initialization. After about 10 or 15 seconds, it then moves on to hanging up the modem and disconnecting.
I am using the TAP protocol.
Does this mean that for some reason the TAP initialization is failing? What could cause such an error?
Thanks
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4354
|
| Posted: Wed Apr 28, 2004 5:30 pm Post subject: |
|
|
Eric,
This issue usually occurs when the modem cannot handshake with the TAP terminal PRIOR to detecting and initializing TAP.
It sounds like you may have to adjust some of the Carrier's settings.
I would try dropping the Carrier's Baud Rate to "300" and selecting "(auto)" for the Initialization String
You should also do the following so that you will have detailed connection (debugging) information into the dialer log (npp.log):
1.) Create a empty text file in the folder "C:\Program Files\NotePager Pro".
2.) Rename the file to "modem.dbg".
When you change the file name and extension, Windows should warn you about making the file unusable.
3.) Select "Yes".
4.) Send another message.
If the messages go through - GREAT!
If not, attach the dialer log file (npp.log) to an e-mail and send it to forumsupport@notepage.com .
Please include the following information in the e-mail:
Carrier
Phone Number
Baud Rate
Data Bits
Parity
Stop Bits |
|
| Back to top |
|
Eric
Guest
|
| Posted: Wed Apr 28, 2004 9:23 pm Post subject: Tap connection |
|
|
| I'll give this a try in the morning...thanks
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4354
|
| Posted: Thu Apr 29, 2004 2:26 pm Post subject: |
|
|
Follow-up:
The customer's Carrier is using 8 Data Bits, No(ne) Parity, and 1 Stop Bit (8,N,1).
This is somewhat unique in the US and Canada. Generally 7 Data Bits, Even Parity and 1 Stop Bit (7,E,1) is used.
Once the Carrier settings were adjusted in the software, the customer was able to initialize TAP correctly. |
|
| Back to top |
|
Guest
|
| Posted: Fri Apr 30, 2004 1:46 pm Post subject: |
|
|
Yes, that is correct. Thanks again for your help.
Also, I needed to change the modem init string to AT&FQ0V1X4&D2 to get it fully work (but I was able to get past the initial problem I was having by changing the settings to 8N1).
|
|
| Back to top |
|
|
