Search found 12 matches

You need to obtain a TAP number from your paging company.

The software would then use TAP to deliver the text message. Right no, it sounds like you are dialing your pager's phone number. That is fine for numerical messages only.

Increase the Baud up to 2400 or 9600 and use "(auto)" for Init String.

GSM Carrier settings do not require a telephone number or Init String.

You do need to enter ID/Pins for Recipients (usually the phone number of the device you are sending a message to).

Looks like your modem did not receive the terminal's acknowledgement response<ACK> after NP32 sent the message block.

Try using this Init Sting:
AT&FQ0V1X4&D2N0+MS=V22

If it continues, try dropping the Baud Rate to 300 and reset the Carrier Init String to "(auto)".

Try removing the "1" from the ID/Pin. Verizon accepts 10 digit ID/Pins for SNPP.

Otherwise, contact Verizon to verify you can receive pager messages via SNPP.

Verizon does NOT support SNPP for their Cell phones.

The dialer log clearly indicates that the terminal's serial port is configured for Manual Entry Mode.

I can't help you with the actual settings for the Terminal, although I would guess that the "01" at the end of the line hex below, be changed to "00" (for the port that you are using).

0D 00 02 1E 01 ; force manual entry mode 0=no, 1=yes (8a4+)

Could be that the serial port on the Zetron is not configured for TAP, but is configured for Manual entry.

Can you post a direct connection attempt from your Dialer log (PGDial1.log)?

Looks like the Airtouch TAP termnal cannot handle 2400 Baud with your modem.

a) Drop the Carrier Baud Rate to 1200
and
b) Set the Carrier Init String to "(auto)".

Try shutting down your NotePager Pro.

If the message continues, it is not a software problem.

Try manually registering the file.
Type this on the commandline:

"regsvr32 comdlg32.ocx"

You should receive a message box that states:

"DllRegisterServer in comdlg32.ocx succeeded."

Repeat for any other "dll" or "ocx" files that you may get a similiar error on.

Was there a solution?

Author	Message
Topic: wont send message
Poncho67 Replies: 1 Views: 13776	Forum: General Questions and Announcements Posted: Wed Jul 27, 2005 9:49 am Subject: TAP
Poncho67 Replies: 1 Views: 13776	You need to obtain a TAP number from your paging company. The software would then use TAP to deliver the text message. Right no, it sounds like you are dialing your pager's phone number. That is fine for numerical messages only.
Topic: Notepager32 sends but says its bad.
Poncho67 Replies: 4 Views: 16926	Forum: NotePager Pro Support Posted: Mon Jul 25, 2005 5:03 am Subject: Notepager32 sends but says its bad.
Poncho67 Replies: 4 Views: 16926	Increase the Baud up to 2400 or 9600 and use "(auto)" for Init String.
Topic: Sending an SMS
Poncho67 Replies: 1 Views: 10343	Forum: PageGate Support Posted: Fri Jul 22, 2005 10:24 am Subject: Sending an SMS
Poncho67 Replies: 1 Views: 10343	GSM Carrier settings do not require a telephone number or Init String. You do need to enter ID/Pins for Recipients (usually the phone number of the device you are sending a message to).
Topic: Notepager32 sends but says its bad.
Poncho67 Replies: 4 Views: 16926	Forum: NotePager Pro Support Posted: Fri Jul 22, 2005 10:22 am Subject: Notepager32 sends but says its bad.
Poncho67 Replies: 4 Views: 16926	Looks like your modem did not receive the terminal's acknowledgement response<ACK> after NP32 sent the message block. Try using this Init Sting: AT&FQ0V1X4&D2N0+MS=V22 If it continues, try dropping the Baud Rate to 300 and reset the Carrier Init String to "(auto)".
Topic: ID/PIN number
Poncho67 Replies: 1 Views: 11117	Forum: NotePager Pro Support Posted: Fri Jul 22, 2005 10:18 am Subject: ID/PIN number
Poncho67 Replies: 1 Views: 11117	Try removing the "1" from the ID/Pin. Verizon accepts 10 digit ID/Pins for SNPP. Otherwise, contact Verizon to verify you can receive pager messages via SNPP. Verizon does NOT support SNPP for their Cell phones.
Topic: direct connection
Poncho67 Replies: 4 Views: 16776	Forum: PageGate Support Posted: Thu Jul 14, 2005 5:09 am Subject: direct connection
Poncho67 Replies: 4 Views: 16776	The dialer log clearly indicates that the terminal's serial port is configured for Manual Entry Mode. I can't help you with the actual settings for the Terminal, although I would guess that the "01" at the end of the line hex below, be changed to "00" (for the port that you are using). 0D 00 02 1E 01 ; force manual entry mode 0=no, 1=yes (8a4+)
Topic: direct connection
Poncho67 Replies: 4 Views: 16776	Forum: PageGate Support Posted: Wed Jul 13, 2005 2:26 pm Subject: direct connection
Poncho67 Replies: 4 Views: 16776	Could be that the serial port on the Zetron is not configured for TAP, but is configured for Manual entry.
Topic: direct connection
Poncho67 Replies: 4 Views: 16776	Forum: PageGate Support Posted: Wed Jul 13, 2005 1:11 pm Subject: direct connection
Poncho67 Replies: 4 Views: 16776	Can you post a direct connection attempt from your Dialer log (PGDial1.log)?
Topic: Trying unsuccessfully to connect to Airtouch
Poncho67 Replies: 2 Views: 13929	Forum: NotePager Pro Support Posted: Mon Jul 11, 2005 9:11 pm Subject: Trying unsuccessfully to connect to Airtouch
Poncho67 Replies: 2 Views: 13929	Looks like the Airtouch TAP termnal cannot handle 2400 Baud with your modem. a) Drop the Carrier Baud Rate to 1200 and b) Set the Carrier Init String to "(auto)".
Topic: message will not quit
Poncho67 Replies: 2 Views: 11935	Forum: NotePager Pro Support Posted: Wed Jul 06, 2005 12:57 pm Subject: message will not quit
Poncho67 Replies: 2 Views: 11935	Try shutting down your NotePager Pro. If the message continues, it is not a software problem.
Topic: Error #339Component 'comdlg32.ocx not correctly registered
Poncho67 Replies: 1 Views: 12245	Forum: PageGate Support Posted: Wed Jul 06, 2005 12:53 pm Subject: Try manually registering the file
Poncho67 Replies: 1 Views: 12245	Try manually registering the file. Type this on the commandline: "regsvr32 comdlg32.ocx" You should receive a message box that states: "DllRegisterServer in comdlg32.ocx succeeded." Repeat for any other "dll" or "ocx" files that you may get a similiar error on.
Topic: Unable to send messages from Windows 2003 server
Poncho67 Replies: 5 Views: 17643	Forum: PageGate Support Posted: Thu Jun 23, 2005 1:31 pm Subject: Solution?
Poncho67 Replies: 5 Views: 17643	Was there a solution?