| |
| Search found 83 matches |
| Author | Message |
|---|---|
| jandafields Replies: 5 Views: 11662 |
|
| It looks like it gets stuck receiving after sending the data. I see in the log that it starts receiving at 12:52:11 and it stops receiving over 30 minutes later at 1:29:31.
All 16 connectors are doing that (since I'm sending more than 16 messages) Of course, AT&T has fixed their API CloudFlare issue and this is no longer happening today. |
|
| jandafields Replies: 5 Views: 11662 |
|
| Also, which version of PageGate are you using?
You can see that on the splash screen of PG Admin and in the 'Registration' section. 8.2.1 |
|
| jandafields Replies: 5 Views: 11662 |
|
|
6/5/2026 12:52:00 AM ======================================== 6/5/2026 12:52:00 AM Start connection to carrier: ATT 6/5/2026 12:52:00 AM Send using WCTP protocol 6/5/2026 12:52:00 AM ---------------------------------------- 6/5/2026 12:52:00 AM Working on message to: xxxxx from: xxxxx 6/5/2026 12:52:00 AM Formatting message 6/5/2026 12:52:00 AM Message contained in single packet 6/5/2026 12:52:00 AM Sending message to https://wctp.firstnet.com:443/WCTP 6/5/2026 12:52:01 AM Sent: 6/5/2026 12:52:01 AM <?xml version="1.0"?> 6/5/2026 12:52:02 AM <!DOCTYPE wctp-Operation SYSTEM "http://dtd.wctp.org/wctp-dtd-v1r1.dtd"> 6/5/2026 12:52:02 AM <wctp-Operation wctpVersion="wctp-dtd-v1r1"> 6/5/2026 12:52:04 AM <wctp-SubmitRequest> 6/5/2026 12:52:05 AM <wctp-SubmitHeader submitTimestamp="2026-06-05T04:52:01"> 6/5/2026 12:52:06 AM <wctp-Originator senderID="xxxxx" securityCode="xxxxx" /> 6/5/2026 12:52:06 AM <wctp-MessageControl messageID="xxxxx" preformatted="true" allowResponse="false" /> 6/5/2026 12:52:07 AM <wctp-Recipient recipientID="xxxxx" /> 6/5/2026 12:52:07 AM </wctp-SubmitHeader> 6/5/2026 12:52:08 AM <wctp-Payload> 6/5/2026 12:52:08 AM <wctp-Alphanumeric>TEST MESSAGE</wctp-Alphanumeric> 6/5/2026 12:52:08 AM </wctp-Payload> 6/5/2026 12:52:09 AM </wctp-SubmitRequest> 6/5/2026 12:52:10 AM </wctp-Operation> 6/5/2026 12:52:11 AM Received: 6/5/2026 1:29:29 AM <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" cont ... |
|
| jandafields Replies: 5 Views: 11662 |
|
| Sending WCTP messages to AT&T Firstnet causes PageGate to hang with 100% CPU usage under the following specific cirucmstances:
The remote WCTP service is down with CloudFlare's "Error 502 Bad gateway" and there are multiple PageGate connectors using that service. This is the first time that FirstNet WCTP has been down with a 502 error (at least that I have seen). This prevents PageGate from getting a connection refused like normal, because CloudFlare's proxy is still online, it's just the link from CloudFlare to FirstNet that is down. So, PageGate gets a network connection to the CloudFlare proxy but then goes crazy with 16 connectors all using significant CPU when there is no WCTP response, causing the entire server to go to 100% CPU. Bug: A remote service being down should not cause PageGate to hang with high CPU. To work around this issue, I have changed to FirstNet SNPP service instead of WCTP, as SNPP is online and working properly. |
|
| jandafields Replies: 3 Views: 13839 |
|
| Ok, I just sent the file to your email as requested. | |
| jandafields Replies: 3 Views: 13839 |
|
| Is there a way to make the smtp password show in the debug log? Currently the log just shows "<password>" instead of the actual text sent to the smtp server. | |
| jandafields Replies: 4 Views: 16415 |
|
| That really doesn't make sense.
You say that when Carrier-A fails, the message is then marked for retry. That 1 retry makes it go to Carrier-B. Okay, fine. Carrier-B fails. Why do you show it going on to Carrier-C then? Oh, maybe I misread your reply. You are showing it retrying A-A-B-B-C-C . Okay, that makes sense. I was thinking A-B-C-A-B-C. |
|
| jandafields Replies: 4 Views: 16415 |
|
| That really doesn't make sense.
You say that when Carrier-A fails, the message is then marked for retry. That 1 retry makes it go to Carrier-B. Okay, fine. Carrier-B fails. Why do you show it going on to Carrier-C then? |
|
| jandafields Replies: 4 Views: 16415 |
|
| Does a Carrier Failover count towards the Retry limit?
For example, I have retries = 1. Send a message out through Carrier-A The message follows this flow: Carrier-A Failover = Carrier-B Carrier-B Failover = Carrier-C If all 3 carriers fail, will the message go Carrier-A, Carrier-B, Carrier-C, and then retry one time and go Carrier-A, Carrier-B, Carrier-C ? Or will it stop after the first Carrier-B because of the Retry=1 limit? |
|
| jandafields Replies: 4 Views: 14740 |
|
| AH! Perfect, thank you. I had been looking in the SMTP settings under interface, where the mail server is set. | |
| jandafields Replies: 4 Views: 14740 |
|
| That won't work, I'm trying to use SMTP as the Failover. So, the auth|pass already has a value for the carrier's primary SNPP connection.
It fails over fine to SMTP if it can't connect to SNPP... but it doesn't use the value from the auth|pass for SMTP and even if it did use that value, it would be incorrect. So, knowing this, where do i enter the smtp credentials? Thank you. |
|
| jandafields Replies: 4 Views: 14740 |
|
| In PageGate 6, where do I put the SMTP user/pass?
I see where to put the smtp server in the relay field, but where do I put the username and password for the SMTP server? |
|
| jandafields Replies: 17 Views: 56638 |
|
| I talked to Verizon. They said the 777 nuumber will always be used from now on. There is no way to go back to the way it was before.
Also, they said that the free TAP service would be discontinued sometime in 2013. |
|
| jandafields Replies: 3 Views: 14512 |
|
| Actually, I just received this from Verizon:
Verizon plans to end free TAP messaging in 2013, but it will continue to be available with the paid EMAG service. |
|
| jandafields Replies: 3 Views: 14512 |
|
| Thank you for the information! | |
All times are GMT - 5 Hours |