(01-08-2021, 12:10 PM)kent Wrote: Quick update. Think I've figured it out. The fix ends up requiring adding a line of code and commenting out another.
There were 2 issues.
1. The host name / ip address issue in gweb->do_request() I've already touched on. On that, I'm now 99% sure there will be no negative impacts from just commenting out the AI_NUMERICHOST flag and allowing the existing code to resolve the proxy host name. The explicit proxy host -> ip address conversion block is commented out and available if I'm wrong about that. It looks like this might come up again on sending messages, but I'm not there yet.
2. Requests to AT&T need to explicitly tell AT&T's servers to close connections. As a result, I was seeing absurdly long time-outs for every request. Fortunately mmsd has a parameter for that and the functionality is already there. I've added a line in service.c->mms_service_bearer_notify() to set the parameter. I am not sure if this will impact other carriers negatively.
Those two little tweaks has mmsd working quite well across AT&T's proxy now. If anyone wants to try out these changes on different carriers, I'd love to know if they break anything for anyone else.
My working repo is: https://source.puri.sm/Kent/mmsd
That's great!
If you could, could you do a MR with my repo so I can test the changes on T-Mobile? I don't expect that to affect T-mobile (since they don't use a proxy). You may want to also test it against my modem manager plugin as well (this is a lot more stable with Modem Manager):
https://source.puri.sm/kop316/mmsd/-/tree/ModemManager
EDIT: Or if I am understanding you right, I just need to add these two lines here:
https://source.puri.sm/Kent/mmsd/-/blob/...ce.c#L2531
and comment out this line:
https://source.puri.sm/Kent/mmsd/-/blob/...eb.c#L1336
And it is done to support AT&T right? If so, I will add it to the modem manager plugin.
Hey All,
I think I have a "0.1" release of the modem manager plugin! It is located here:
https://source.puri.sm/kop316/mmsd/-/tree/ModemManager
EDIT: Ok I got a bit excited, I now added a few things to ensure that you can understand the API and make sure the plugin is resiliant. Also as soon as I confirm the AT&T fixes, those will be added.
