(05-18-2022, 03:06 PM)treebeard Wrote: I've got an PinePhone (Evergreen) running Mobian Bookworm.  I got MMS messaging working in February after installing chatty v0.6.0-1 and it was fine until on or shortly before March 12 2022.  The messages seem to be retrieved and queued in ~/.mms/modemmanager/ but they don't get processed further and make their way into chatty anymore.

I've also got a Ting SIM with service via T-Mobile/Dish and MMS works fine with that.  I've switched SIMS back-and forth several times and the symptoms are persistent - Verizon always fails now and Ting works.

Here is the log for a 2nd attempt at processing a message:

Code:

May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:process_request_queue() service 0x55ab13be70
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:process_request_queue() location http://63.55.64.151/servlets/mms?message-id=2105824508BB00007650000201
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host() No active proxy
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host_systemd() resolve_host_systemd
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host_systemd() systemd-resolved host ip: 63.55.64.151
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host() Using URI for request: http://63.55.64.151/servlets/mms?message-id=2105824508BB00007650000201
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:create_new_web_message() host: 63.55.64.151, port: -1
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Starting new address enumeration
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Address enumeration succeeded
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Starting TCP connection attempt
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:soupmessage_network_event_cb() Socket 11 Binding to wwx0225d3683889 length 15
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:soupmessage_network_event_cb() Socket is bound to wwx0225d3683889
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: TCP connection successful
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: Starting application layer connection
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: Connection successful!
May 18 15:10:10 pine mmsdtng[5933]: Fail to get data (http status = 007)
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() status: 007
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() data size = 0
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() request->result_cb=0x557625fdc0 vs. retrieve_conf=0x557625fdc0/send_conf=0x557625a180/notify_resp=0x557625cf64
May 18 15:10:10 pine mmsdtng[5933]: Fail to get data (http status = 007)
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() On attempt 2
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() Requeued Message
May 18 15:10:14 pine mmsdtng[5933]: ../src/service.c:service_retry_process_request_queue() Retrying Queue

   
After the "Connection successful!" message there should be some communication happening but instead I seem to get a timeout after one minute.  My MMS config has CarrierMMSC=http://mms.vtext.com/servlets/mms  and  MMS_APN=vzwinternet.

I've tried a varety of config changes in case this had something to do with DNS, and cleared nftables rules in case the firewall was interfering.  No joy.

Does anyone have a clue what's going on here?  Is there anyone for whom MMS & Verizon is working?

Edit 1: I have done regular dist-upgrades, including a couple days ago, and the symptoms don't seem to change.

(05-20-2022, 10:34 AM)cjhead Wrote: It looks like Verizon changed their MMS apn. I don't think it's vzwinternet anymore.

Read the comments here