ryanwhite
Joined: 01 Jul 2025
Posts: 1
|
 Posted: Tue Jul 01, 2025 9:21 pm Post subject: Messages Not Sending or Delayed |
 |
|
Hi NotePage Team,
We're running PageGate v10.3 with a multi-carrier setup using a GSM modem connected via COM3 (direct serial, https://slopeonlinegame.github.io no USB adapter) on a Windows Server 2019 instance. We're using the GetASCII interface for integration with our NOC monitoring system, which generates anywhere from 30–150 alerts/hour depending on network state.
Lately, we’re seeing intermittent gateway failures, specifically:
Messages will queue but not transmit for up to 20 minutes, then send in bursts.
The PGDialer logs occasionally show incomplete AT command responses (e.g., AT+CMGS echo received without matching > prompt).
Occasionally we receive +CMS ERROR: 500 or CMS ERROR: 512 from the modem during heavy message traffic.
Flow control is set to hardware, and we’re using a Sierra Wireless modem (latest firmware), but I'm wondering:
Could this be a result of serial port buffer overruns or AT command queueing issues in the gateway's modem handler?
Does PageGate support any command pacing or adaptive throttling for GSM devices that aren’t handling AT+CMGS loads well under volume?
Should we consider implementing custom CTS/RTS handling via modem init strings, or is that managed internally by PageGate?
Would switching to a GSM-over-IP provider (via SMPP) give us better throughput and diagnostic control under load, and does PageGate’s gateway module support DLRs (Delivery Receipts) in that context?
We've ruled out antivirus, COM port contention, and NOC alert duplication. The modem logs (outside of PageGate) do confirm that messages are being sent, but the delayed batching behavior suggests something may be queuing internally or hanging on state transitions.
Any guidance on tuning the gateway layer or modem I/O buffering would be greatly appreciated.
Last edited by ryanwhite on Sat Jul 05, 2025 5:32 am; edited 1 time in total |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4395
|
| Posted: Wed Jul 02, 2025 7:31 am Post subject: |
|
|
Those CMS Errors indicate that the modem is experiencing a SIM card or an account issue during heavy traffic.
You may want to insert a greater pause between messages with the InterMessageDelay = X variable, where X is the number of milliseconds of delay.
For most cellular hardware, you'll need at least InterMessageDelay = 1500 to make sure the cellular radio doesn't get overloaded.
|
|
