View previous topic :: View next topic |
Author |
Message |
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Wed Aug 10, 2011 5:19 pm Post subject: Not receiving texts messages with SUCCESFUL prompt |
|
|
We are currently attempting experiencing an issue with notepagepro Version 3.0 installed on a server 2003 r2 server.
We are using the following setup, US Robotics external modem, with the following settings applied to the carrier:
Verizon
TAP
866-337-4504
1200
Even
7
1
AT&F0Q0V1X4&D2&B1&K0&M0&N2
Max Char 240
Our issue is the following: We are able to dial out and the connection monitor displays the following:
8/10/2011 3:52:14 PM Working on message to: omar from: general
8/10/2011 3:52:14 PM Formatting message
8/10/2011 3:52:14 PM Message contained in single block
8/10/2011 3:52:14 PM Sending block
8/10/2011 3:52:14 PM Sent:<STX>XXXXXXXXXX<CR>general:Test<CR><ETX>6=9<CR>
8/10/2011 3:52:15 PM Received:<CR><ACK><CR><LF>
8/10/2011 3:52:15 PM Block sent successfully
8/10/2011 3:52:15 PM SUCCESSFUL To:omar Frm:general Msg:Test
8/10/2011 3:52:15 PM ------------------------------------------------
8/10/2011 3:52:15 PM Working on message to: omar from: general
8/10/2011 3:52:15 PM Formatting message
8/10/2011 3:52:15 PM Message contained in single block
8/10/2011 3:52:15 PM Sending block
8/10/2011 3:52:15 PM Sent:<STX>XXXXXXXXXX<CR>general:Test<CR><ETX>6=9<CR>
8/10/2011 3:52:16 PM Received:<CR><ACK><CR><LF>
8/10/2011 3:52:16 PM Block sent successfully
8/10/2011 3:52:16 PM SUCCESSFUL To:omar Frm:general Msg:Test
8/10/2011 3:52:16 PM Sent:<EOT><CR>
8/10/2011 3:52:17 PM Attempting to hang up modem
8/10/2011 3:52:19 PM Sent:AT<CR>
8/10/2011 3:52:22 PM Received:RIER<CR><LF>
8/10/2011 3:52:22 PM Attempting to hang up modem
8/10/2011 3:52:25 PM Sent:AT<CR>
8/10/2011 3:52:25 PM Received:<CR><LF>OK<CR><LF>
8/10/2011 3:52:25 PM modem hung up
8/10/2011 4:08:38 PM ====================================
It would seem that everything was “successful” but I never receive anything. I have tested the POTS line with an analog to verify that it is working and I have also attempted different carriers. Any assistance would be much appreciated.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Thu Aug 11, 2011 9:15 am Post subject: |
|
|
From the init string, I'm guessing you have a US Robotics modem. This may sound like a random question but, by chance, do you have a US Robotics 5637 modem? |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Thu Aug 11, 2011 9:32 am Post subject: |
|
|
Thanks for the reply, it is a 5686 "Sportster," I did take a gander at just about all of the FAQ and Forum pages before posting and did see a common issue with the 5637 and ceratin carriers.
I should have noted that: notepager pro and the modem were working previously. We recently had to migrate its server hardware to different hardware, aside from just the server being a slightly different model, everything has staye absolutely the same. Which is honestly the most puzzling part.
I should have also mentioned that during our trouble shooting bonanza we tested dialing out through modem via hyper terminal and we did have a dial tone and were able to dial out.
Thanks in advance for any suggestions.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Thu Aug 11, 2011 10:12 am Post subject: |
|
|
Well, the problem you're running in to isn't that the program isn't dialing out, it is. It's that the protocol negotiation with the Verizon TAP system is... odd. For example, have a look at this transaction:
8/10/2011 3:52:15 PM Working on message to: omar from: general
8/10/2011 3:52:15 PM Formatting message
8/10/2011 3:52:15 PM Message contained in single block
8/10/2011 3:52:15 PM Sending block
8/10/2011 3:52:15 PM Sent:<STX>XXXXXXXXXX<CR>general:Test<CR><ETX>6=9<CR>
8/10/2011 3:52:16 PM Received:<CR><ACK><CR><LF>
8/10/2011 3:52:16 PM Block sent successfully
8/10/2011 3:52:16 PM SUCCESSFUL To:omar Frm:general Msg:Test
8/10/2011 3:52:16 PM Sent:<EOT><CR>
8/10/2011 3:52:17 PM Attempting to hang up modem
8/10/2011 3:52:19 PM Sent:AT<CR>
8/10/2011 3:52:22 PM Received:RIER<CR><LF>
8/10/2011 3:52:22 PM Attempting to hang up modem
8/10/2011 3:52:25 PM Sent:AT<CR>
8/10/2011 3:52:25 PM Received:<CR><LF>OK<CR><LF>
8/10/2011 3:52:25 PM modem hung up
8/10/2011 4:08:38 PM ====================================
Specifically, this part:
8/10/2011 3:52:16 PM Block sent successfully
8/10/2011 3:52:16 PM SUCCESSFUL To:omar Frm:general Msg:Test
8/10/2011 3:52:16 PM Sent:<EOT><CR>
8/10/2011 3:52:17 PM Attempting to hang up modem
8/10/2011 3:52:19 PM Sent:AT<CR>
8/10/2011 3:52:22 PM Received:RIER<CR><LF>
If you'll notice, the TAP system receives the packet of data from the program but then, after the transaction is finished, we receive a broken response packet:
8/10/2011 3:52:22 PM Received:RIER<CR><LF>
The full packet would have said, "NO CARRIER"... which means that after they received the data packet from the system, they dropped the connection. This probably means that the terminal dropped the line before it could fully receive the data packet containing the message. Unfortunately, this means that NotePager Pro thinks the message went through... because as far as we can tell, it did.
Have you tried their alternate terminal number? It's 18668230501 |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Thu Aug 11, 2011 10:25 am Post subject: |
|
|
Yes, we have tried the alternate number. Could the carrier dropping the packet indicate a problem with the modem itself? Or could this indicate that the packet is not being accepted our carrier?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Thu Aug 11, 2011 10:26 am Post subject: |
|
|
If you have an alternate modem you can try, I'd recommend it. At least it would give us a baseline to say whether it was the modem or the terminal. Just based on the log file, it could be either. |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Thu Aug 11, 2011 11:50 am Post subject: |
|
|
Just attempted the same procedure utilizing a different modem and I am still experiencing the same issue. Any other step I should take?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Thu Aug 11, 2011 11:56 am Post subject: |
|
|
Did you reset the init string to (auto) in the carrier settings? The reason I ask is that unless it was another US Robotics modem, the new modem may use a new AT command set and that might cause issues. |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Thu Aug 11, 2011 1:01 pm Post subject: |
|
|
I just attempted that and I am still experiencing the same issue, I even removed the carrier information that was already in there and re-added the information.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Thu Aug 11, 2011 1:06 pm Post subject: |
|
|
I can't fully explain what you're seeing, unfortunately. I mean, we've pretty fairly determined that the problem isn't with the modem you're using... and the terminal is saying that it accepted the data packet with the message, even if it is responding weirdly after the data packet it received. Unfortunately, I don't know that there's anything you can do directly on your end short of doing a system restore to before the problem started to happen to see if maybe one of the Windows Updates modified the telephony suite in Windows and that, for whatever odd reason, caused the underlying issue? |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Thu Aug 11, 2011 4:35 pm Post subject: |
|
|
Just as an update, I have contacted our provider and they will be looking into any possible issues that could be occuringon their end. I should know something between 2-3 business days and will post a reply.
In the mean time are there any other procedures or trouble shooting steps that i can take?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4367
|
Posted: Fri Aug 12, 2011 11:50 am Post subject: |
|
|
There isn't anything else I can think of that you can really try, no. I'd be very interested to see what they have to say, though. |
|
Back to top |
|
itdepartment
Joined: 10 Aug 2011 Posts: 7
|
Posted: Mon Aug 15, 2011 4:30 pm Post subject: |
|
|
It was a carrier issue…Our carried which will remain nameless, but rhymes with horizon fireless, was having a local TAPS issue. Thank you for all of your suggestions and assistance.
|
|
Back to top |
|
|