Pure Talk MMS

[jwide]

Thanks for the reply. I did email them but that didn't produce any new information. 

I did manage to send a few mms messages on a fresh Manjaro Phosh install, but I haven't successfully received any yet. Unfortunately, sending messages is broken again also. Not sure what caused that, unless the unread messages are somehow blocking the send process.

Looking around at the mmsdtng -d output, I see the following "repeated" several times (the data change, but the pattern is consistent):

** (mmsdtng:4404): DEBUG: 00:08:07.182: ../mmsd/src/service.c:process_request_queue() service 0xaaaadcfc5ea0
** (mmsdtng:4404): DEBUG: 00:08:07.182: ../mmsd/src/service.c:process_request_queue() location http://107.227.45.165:8003/Y/0116050922423001000110000
** (mmsdtng:4404): DEBUG: 00:08:07.182: ../mmsd/src/service.c:resolve_host() There is an active proxy! Not attempting to resolve host
** (mmsdtng:4404): DEBUG: 00:08:07.182: ../mmsd/src/service.c:resolve_host() Using URI for request: http://107.227.45.165:8003/Y/0116050922423001000110000
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.185: GSocketClient: Starting new address enumeration
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.186: GSocketClient: Address enumeration succeeded
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.187: GSocketClient: Starting TCP connection attempt
** (mmsdtng:4404): DEBUG: 00:08:07.188: ../mmsd/src/service.coupmessage_network_event_cb() Socket 25 Binding to wwan0 length 5
** (mmsdtng:4404): DEBUG: 00:08:07.188: ../mmsd/src/service.coupmessage_network_event_cb() Socket is bound to wwan0
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.316: GSocketClient: TCP connection successful
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.317: GSocketClient: Starting application layer connection
(mmsdtng:4404): GLib-GIO-DEBUG: 00:08:07.317: GSocketClient: Connection successful!
> GET /Y/0116050922423001000110000 HTTP/1.1
> Soup-Debug-Timestamp: 1642313287
> Soup-Debug: SoupSession 1 (0xffff840246a0), SoupMessage 7 (0xaaaadd0580b0), SoupSocket 7 (0xaaaadcfceb90)
> Host: 107.227.45.165
> Accept-Encoding: gzip, deflate
> Connection: Keep-Alive

** (mmsdtng:4404): DEBUG: 00:08:26.256: ../mmsd/src/service.c:response_got_chunk() Got chunk: 2756
** (mmsdtng:4404): DEBUG: 00:08:26.281: ../mmsd/src/service.c:response_got_chunk() Got chunk: 238
** (mmsdtng:4404): DEBUG: 00:08:26.301: ../mmsd/src/service.c:response_got_chunk() Got chunk: 501
< HTTP/1.1 503 Service Unavailable
< Soup-Debug-Timestamp: 1642313306
< Soup-Debug: SoupMessage 7 (0xaaaadd0580b0)
< Server: HPM/14.09.0099
< Mime-Version: 1.0
< Date: Sun, 16 Jan 2022 06:08:25 GMT
< Content-Type: text/html
< Content-Length: 3495
< X-Hpm-Error: ERR_CONNECT_FAIL 113
< Via: 1.0 proxy.mobile (HPM/14.09.0099)


** (mmsdtng:4404): CRITICAL **: 00:08:26.303: Fail to get data (http status = 503)
** (mmsdtng:4404): DEBUG: 00:08:26.304: ../mmsd/src/service.c:on_message_done() status: 503
** (mmsdtng:4404): DEBUG: 00:08:26.304: ../mmsd/src/service.c:on_message_done() data size = 3495
** (mmsdtng:4404): DEBUG: 00:08:26.304: ../mmsd/src/service.c:on_message_done() request->result_cb=0xaaaabfa31274 vs. retrieve_conf=0xaaaabfa31274/send_conf=0xaaaabfa29b30/notify_resp=0xaaaabfa2d554

** (mmsdtng:4404): CRITICAL **: 00:08:26.305: Fail to get data (http status = 503)

** (mmsdtng:4404): CRITICAL **: 00:08:31.306: retry later



An http 503 error seems problematic. It seems to connect, but then the server says it is unavailable, so I don't know what to make of it. Has anyone else tackled this problem?

Thanks again.