10-17-2022, 04:08 PM
Have you reviewed log messages from modemmanager and mmsd-tng when they're initializing for any obvious signs of trouble?
Somewhere in the middle of it you should see something like this:
Somewhere in the middle of it you should see something like this:
Code:
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Setting Context...
mmsdtng[889]: ../src/service.c:mms_service_set_mmsc() service 0x55880a3e70 mmsc http://mms.vtext.com/servlets/mms
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Current Context APN: vzwapp, mmsd-tng settings MMS APN: vzwapp
mmsdtng[889]: ../plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context...
mmsdtng[889]: ../src/service.c:mms_service_set_apn() Service APN Set to vzwapp
mmsdtng[889]: ../src/service.c:mms_service_set_resolvers() service 0x55880a3e70 resolvers: ipv4: 198.224.177.135,198.224.176.135, ipv6: 2001:4888:45:ff00:432:d::,2001:4888:46:ff00:430:d::
mmsdtng[889]: ../plugins/modemmanager.c:set_context() DNS from modemmanager IPv6: 2001:4888:45:ff00:432:d::,2001:4888:46:ff00:430:d::, IPv4: 198.224.177.135,198.224.176.135