| View previous topic :: View next topic |
| Author |
Message |
PGUser
Joined: 16 Jun 2011
Posts: 9
Location: North Carolina, US
|
 Posted: Tue Aug 02, 2011 4:27 pm Post subject: Getting Bad ID or message content on all carriers & reci |
 |
|
I have not been able to determine the problem with paging. The error I'm getting is Failed - Bad ID or message content. This, from my understanding is usually because the ID/PIN for the recipient is incorrect. I am receiving this on all carriers and all recipients. This has been set up for many years. There have been no changes to the carrier numbers or the recipients' settings. This is version 4.0.0.5.
I see the connection to the carrier but then I get this error. I am able to dial out with this modem using hyperterminal so I know the phone line and modem are good.
Below is a copy and paste of the last two successful messages sent from Global logging. Everything since has returned the error.
7/24/2011 4:02:13 PM PGSched Message scheduled. Recipient: xxxxxx from: Cad: 2011-0000000000
7/24/2011 4:02:44 PM PGDial1 SUCCESSFUL Stn:1 To:xxxxxx Frm:Cad: 2011-0000000000 File:16020387.460 Msg:xxxxxxxxxxxxxxxxxxxxxxxxxx
CALL xxxx AT HOME xxxxxxx
7/24/2011 6:29:31 PM PGSched Message scheduled. Recipient: xxxxxxx from: Cad: 2011-0000000000
7/24/2011 6:30:02 PM PGDial1 SUCCESSFUL Stn:1 To:xxxxxxx Frm:Cad: 2011-0000000000 File:18293404.462 Msg:xxxxxxxxxxxxxxxxxxxxxxxxxx
CALL xxxx xxxxxxx
7/25/2011 Unable to synchronize time with scheduler. Using local time.
7/25/2011 12:00:05 AM Modules paused
7/25/2011 12:00:05 AM Running cleanup routine
7/25/2011 12:00:19 AM Module resumed
7/25/2011 12:00:22 AM Time synchronized with scheduler
7/25/2011 8:51:04 AM PGSched Message scheduled. Recipient: xxxxxxxx from: Return Phone: xxxxxxxxxx
7/25/2011 8:56:52 AM PGDial1 FAILED Stn:1 To:xxxxxxx Frm:Return Phone: xxxxxxxxxx File:08505554.464 Msg:Cad: 2011-0000000000
xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
7/25/2011 11:20:04 AM PGSched Message scheduled. Recipient: xxxxxxxxx from: Return Phone: xxxxxxxxxx
7/25/2011 11:20:36 AM PGDial1 FAILED Stn:1 To:xxxxxxxx Frm:Return Phone: xxxxxxxxxx File:11195572.466 Msg:Cad: 2011-0000000000
xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
7/25/2011 11:51:30 AM PGSched Message scheduled. Recipient: xxxxxxxxx from: Cad: 2011-0000000000
7/25/2011 11:52:03 AM PGDial1 FAILED Stn:1 To:xxxxxxxxxx Frm:Cad: 2011-0000000000 File:11512615.468 Msg:xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
7/25/2011 1:50:55 PM PGSched Message scheduled. Recipient: xxxxxx from: Return Phone: xxxxxxxxxx
7/25/2011 1:53:55 PM PGDial1 FAILED Stn:1 To:xxxxxx Frm:Return Phone: xxxxxxxxxx File:13505016.470 Msg:Cad: 2011-0000000000
xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
7/25/2011 5:12:16 PM PGSched Message scheduled. Recipient: xxxxxxx from: Cad: 2011-0000000000
7/25/2011 5:17:21 PM PGDial1 FAILED Stn:1 To:xxxxxx Frm:Cad: 2011-0000000000 File:17121040.472 Msg:xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
7/26/2011 12:00:03 AM Unable to synchronize time with scheduler. Using local time.
7/26/2011 12:00:07 AM Modules paused
7/26/2011 12:00:07 AM Running cleanup routine
7/26/2011 12:00:21 AM Module resumed
7/26/2011 12:00:23 AM Time synchronized with scheduler
7/26/2011 10:32:47 AM PGSched Message scheduled. Recipient: xxxxxx from: Return Phone: xxxxxxxxxx
7/26/2011 10:36:54 AM PGDial1 FAILED Stn:1 To:xxxxxx Frm:Return Phone: xxxxxxxxxx File:10323939.474 Msg:Cad: 2011-0000000000
xxxxxxxxx xxxxxx xxxx
xxx xxxx xxxxxx xx xxxxx
xx xxx xx xxxxxxxxxx xx xxx
|
|
| Back to top |
|
OzCom
Joined: 22 Oct 2003
Posts: 1122
Location: US
|
| Posted: Wed Aug 03, 2011 8:52 am Post subject: |
|
|
Can you post a snippet of the pgdial1.log showing the entire session? Usually, "Failed - BAD ID" indicates that the carrier is rejecting the device identity as INVALID_________________ Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate |
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Aug 03, 2011 9:10 am Post subject: |
|
|
| Alternatively, if you're worried about potentially publishing someone's recipient information, you could email the pgdial1.log file to support at notepage dot com and I'll have a look at why the rejections are happening. |
|
| Back to top |
|
PGUser
Joined: 16 Jun 2011
Posts: 9
Location: North Carolina, US
|
| Posted: Wed Aug 03, 2011 9:49 am Post subject: |
|
|
8/2/2011 2:41:19 PM ========================================
8/2/2011 2:41:19 PM Start connection to carrier: VERIZON
8/2/2011 2:41:19 PM Connect using TAP protocol
8/2/2011 2:41:19 PM Setting communication parameters
8/2/2011 2:41:19 PM Attempting to reset modem
8/2/2011 2:41:22 PM Modem reset
8/2/2011 2:41:22 PM Attempting to send dialer init string
8/2/2011 2:41:24 PM Dialer init string sent
8/2/2011 2:41:24 PM Dialing carrier
8/2/2011 2:41:32 PM Waiting for connection
8/2/2011 2:41:36 PM Connected to carrier
8/2/2011 2:41:36 PM Waiting for protocol initialization
8/2/2011 2:41:42 PM TAP protocol detected
8/2/2011 2:41:44 PM Automatic TAP mode accepted
8/2/2011 2:41:44 PM ----------------------------------------
8/2/2011 2:41:44 PM Working on message to: xxxxxx from: Cad: 2011-0000000000
8/2/2011 2:41:44 PM Formatting message
8/2/2011 2:41:44 PM Message contained in single packet
8/2/2011 2:41:44 PM Message contained in single block
8/2/2011 2:41:44 PM Sending block
8/2/2011 2:41:45 PM Bad ID or message content. Message aborted
8/2/2011 2:41:45 PM Permanent failure. Message will not be retried
8/2/2011 2:41:45 PM FAILED Stn:1 To:xxxxxx Frm:Cad: 2011-0000000000 File:14410525.590 Msg:xxxxxxxxxx xxxxxx xxxxxx xxx
TEST PAGE PLS ADVISE IF RECEIV
ED
8/2/2011 2:41:46 PM Attempting to hang up modem
8/2/2011 2:41:49 PM Modem hung up
8/2/2011 2:55:24 PM ========================================
8/2/2011 2:55:24 PM Start connection to carrier: ALTEL
8/2/2011 2:55:24 PM Connect using TAP protocol
8/2/2011 2:55:24 PM Setting communication parameters
8/2/2011 2:55:25 PM Attempting to reset modem
8/2/2011 2:55:28 PM Modem reset
8/2/2011 2:55:28 PM Attempting to send dialer init string
8/2/2011 2:55:29 PM Dialer init string sent
8/2/2011 2:55:29 PM Dialing carrier
8/2/2011 2:55:38 PM Waiting for connection
8/2/2011 2:55:46 PM Connected to carrier
8/2/2011 2:55:46 PM Waiting for protocol initialization
8/2/2011 2:55:51 PM TAP protocol detected
8/2/2011 2:55:53 PM Automatic TAP mode accepted
8/2/2011 2:55:53 PM ----------------------------------------
8/2/2011 2:55:53 PM Working on message to: xxxxxxx from: xxxxxxxxx xxx
8/2/2011 2:55:53 PM Formatting message
8/2/2011 2:55:53 PM Message contained in single packet
8/2/2011 2:55:53 PM Message contained in single block
8/2/2011 2:55:53 PM Sending block
8/2/2011 2:55:55 PM Bad ID or message content. Message aborted
8/2/2011 2:55:55 PM Permanent failure. Message will not be retried
8/2/2011 2:55:55 PM FAILED Stn:0 To:xxxxxxx Frm:xxxxxxxxx xxx Msg:Pager test
8/2/2011 2:55:55 PM Attempting to hang up modem
8/2/2011 2:55:58 PM Modem hung up
8/2/2011 3:02:25 PM Module Stopped
8/2/2011 3:03:27 PM Module Started
8/2/2011 3:03:29 PM Time synchronized with scheduler
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Aug 03, 2011 9:52 am Post subject: |
|
|
| The problem you're running in to is that the Verizon terminal is rejecting the number you've entered in to the ID/PIN field of the recipient. Are you using the 7 or 10 digit ID in the ID/PIN field of the recipient? |
|
| Back to top |
|
PGUser
Joined: 16 Jun 2011
Posts: 9
Location: North Carolina, US
|
| Posted: Wed Aug 03, 2011 10:09 am Post subject: |
|
|
| I am using 10 digit ID/PIN. They have not changed. It was working with these previously. Now it is rejecting all IDs and all carriers. All of the carriers are dialing 800 or 866 numbers. From what I understand if using toll free numbers the area code must be included with the ID/PIN. Is this correct?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Aug 03, 2011 10:13 am Post subject: |
|
|
| Wait... no. As far as I know, all you should use in the ID/PIN field is the recipient's 10 digit cel phone number, no spaces or dashes. That's all that should go in that field. The carrier's terminal number goes in the carrier field, that's all. |
|
| Back to top |
|
PGUser
Joined: 16 Jun 2011
Posts: 9
Location: North Carolina, US
|
| Posted: Wed Aug 03, 2011 10:19 am Post subject: |
|
|
| That's what I have. Just the cell# of the recipient. No dashes or spaces 10 digits.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Aug 03, 2011 10:33 am Post subject: |
|
|
| That's... interesting. I mean, the terminal's response is that the number isn't a valid Verizon number. If this is something that's just started to happen, I can't really explain it because the responses aren't coming from PageGate. If you would, send me the pgdial1.log file so I can see the more specific commands and responses going on in the transaction. |
|
| Back to top |
|
PGUser
Joined: 16 Jun 2011
Posts: 9
Location: North Carolina, US
|
| Posted: Wed Aug 03, 2011 3:24 pm Post subject: |
|
|
Mystery solved:
As of July 24, 2011 Alltel has turned off their TAP paging. Everyone needs to be switched to snpp to use paging to Alltel phones.
snpp.alltelwireless.com
port 444
|
|
| Back to top |
|
|
