| 504 Gateway Timeout |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Mike Glancy New member Username: Web9 Post Number: 30 Registered: 05-2013 |
We recently purchased the NowSMS Modem version and are trying to send MMS messages over wifi (local network) via a Google Pixel 1 phone. A few messages go out, but most of them fail with the following - Is there a setting on the application or phone we need to change? Thanks. <html><head></head><body><p>MMS Connection Failure</p> <p>Debug Info: Lookup failed for mms.vtext.com; Exception null Unable to resolve host "mms.vtext.com": No address associated with hostname [Ljava.lang.StackTraceElement;@96c6fab</p> </body></html> 15:37:52:496 [16] WaitForSocketClose: WinSock reported ioctlsocket complete 15:37:52:497 [16] ThreadProcessVASPQ: Outbound route 10.100.2.76: setting retry for 607F8795.MMS 15:37:52:497 [16] SaveIniData: [Routing] MessageID=20211019-15-180DAFD6@nowsms SenderAddress=PassTime/TYPE=PLMN [Recipients] Recip1=12108544415/TYPE=VASP:10.100.2.76 [RetryInfo] RetryCount=1 LastRetryTime=20211019153752 FirstAttemptTime=20211019153752 LastErrorInfo=MM1 - got unknown response - HTTP Status: 504 Gateway Timeout | |||
| Mike Glancy New member Username: Web9 Post Number: 31 Registered: 05-2013 |
Also, how do you view the MMS queue. We used this on the lite version, but I don't see a button for it, only for the SMS queue. Thx. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6311 Registered: 08-2008 |
Hi Mike, This was all working before with NowSMS Lite? Is this Pixel the same device that you were using before? I ask because there's no difference in how this is handled on the NowSMS server side of things. The server is asking the app on the phone to send an MMS message, but the app on the phone cannot connect to the MMSC. The error indicates that the IP address for the MMSC, mms.vtext.com, cannot be found. I recognize that MMSC name as being correct for Verizon. It is normal that this host would not be found in DNS if searching over WiFi, bt the app directs this search to be over the data network. The only idea that comes to my mind is to reboot the phone. And ensure the its data connectivity is working...maybe the data connection is not working well. Is the device configured to use WiFi calling? That can help in some situations where data connectivity to the operator network is poor.
I believe the only UI for this is in the web admin interface, where the outbound queue displays a mix of both SMS and MMS. These MMS messages are queued in the VASPQ directory, where each message has an .INI and .MMS file. Regards, Des NowSMS Support | |||
| Mike Glancy New member Username: Web9 Post Number: 32 Registered: 05-2013 |
So it is a new Pixel 1 to replace an existing Pixel 1 where the battery has swelled. I repointed the new application at the existing phone and so far, no gateway errors. There must be some setting difference between the new Pixel 1 and the current phone. I've gone over everything and they look the same except the original phone has the 2017 android NowSMS app and the new phone has the 2018 version. Regarding the MMS message queue, it was quite handy to see the pending messages and how long they have been waiting. When I log into the web interface, I only see the totals. Is there a different page for web admin? Thanks again. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6312 Registered: 08-2008 |
If you want to try the 2017 version of the app, it is accessible here: https://nowsms.com/download/NowSMSModem.20170410.apk You've confirmed that the standard messages app has no problem sending MMS, correct? Are you using the same SIM for these tests? Regarding the message queue, the Admin dropdown menu has a link for "Outbound Message Queue", which should list the queued messages. | |||
| Mike Glancy New member Username: Web9 Post Number: 33 Registered: 05-2013 |
Yes. Even if I send a test MMS via the NowSMS interface it goes out. They are using different SIM cards, but same carrier, plan, etc. Is there something with the SIM that might affect this or something we need to set on the account with Verizon? I see the message queue now. I didn't have the login set for admin access. Thx. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6313 Registered: 08-2008 |
SIM card behavior is just an idea. It's worth determining whether the problem follows the device or the SIM. I'm assuming the problem would follow the device, but maybe not? When you say that "Even if I send a test MMS via the NowSMS interface it goes out" ... what do you mean? Do you mean the problem is inconsistent ... that sometime messages go out and sometimes this 504 error is encountered? | |||
| Mike Glancy New member Username: Web9 Post Number: 36 Registered: 05-2013 |
So I wanted to revisit this issue as we attempted to swap to a new phone again. This time we used the exact same SIM card and the phone types and carriers are all the same. Again on most of the outbound MMS messages we received the same error (sample below), but some do go out. Any ideas on what we can try to troubleshoot this? Thanks. 16:18:11:991 [17] ThreadProcessVASPQ: MM1 - got unknown response - HTTP Status: 504 Gateway Timeout 16:18:11:991 [17] ThreadProcessVASPQ: HTTP/1.1 504 Gateway Timeout Content-Type: text/html Date: Thu, 13 Jan 2022 23:18:11 GMT Content-Length: 257 <html><head></head><body><p>MMS Connection Failure</p> <p>Debug Info: Lookup failed for mms.vtext.com; Exception null Unable to resolve host "mms.vtext.com": No address associated with hostname [Ljava.lang.StackTraceElement;@e2b36c5</p> </body></html> 16:18:11:991 [17] WaitForSocketClose: WinSock reported ioctlsocket complete 16:18:11:991 [17] ThreadProcessVASPQ: Outbound route 10.100.2.76: setting retry for BD4F9458.MMS 16:18:11:991 [17] SaveIniData: [Routing] MessageID=20220113-16-FA3D6CD9@ SenderAddress=PassTime/TYPE=PLMN | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8473 Registered: 10-2002 |
Hi Mike, It is very strange that this error is sporadic. Des' previous explanation is accurate. mms.vtext.com would be the host name of the Verizon MMSC, which is configured in the phone's settings. What is supposed to happen is that the app makes sure that a mobile data connection is active with the APN configured for MMS (to my knowledge, Verizon uses the same APN for internet and MMS, so there should be no confusion there), then it performs a DNS lookup for the MMS host name. It's difficult to imagine why this would be failing. I'm wondering if maybe there is an issue where the mobile data connection only gets allocated an IPv6 address. If you can access the APN settings in the phone, it might be useful to set the MMS APN settings for IPv4 only. (All this said, to the best of my knowledge, the app does support IPv6 only connections on the mobile operator side. So, this theory is more of a guess.) My best idea for how to work-around what issue is occurring would be to turn off WiFi, and configure the modem as "Remote" or "Remote vis Cloud". In the "Remote" mode, you need a public IP over which the phone can connect to the NowSMS server (by default, the app is going to try to connect to port 8990), In the "Remote via Cloud", the app and server transparently connect to each other via an encrypted proxy. Obviously, either of these work-arounds introduce security concerns. But my thought is that if WiFi is disabled and the device only has a mobile data connection, that would ensure that the DNS lookup for the MMSC host name is sent via the proper route. Out of curiously, what is the version shown on the Android app? Regards, Bryce NowSMS Support | |||
