From: Chris Talbot <chris@talbothome.com>
To: ofono@ofono.org, netdev@vger.kernel.org,
debian-on-mobile-maintainers@alioth-lists.debian.net,
librem-5-dev@lists.community.puri.sm
Subject: [PATCH 3/9] Ensure Compatibility with AT&T
Date: Sat, 10 Apr 2021 10:20:50 -0400 [thread overview]
Message-ID: <178dd29027e6abb4a205e25c02f06769848cbb76.camel@talbothome.com> (raw)
In-Reply-To: <df512b811ee2df6b8f55dd2a9fb0178e6e5c490f.camel@talbothome.com>
This patch fixes two issues to ensure compatibility with AT&T:
1) Explicity close connections to the mmsc
2) Allow MMS Proxies that are domain names
---
gweb/gweb.c | 3 ++-
src/service.c | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gweb/gweb.c b/gweb/gweb.c
index f72e137..995d12f 100644
--- a/gweb/gweb.c
+++ b/gweb/gweb.c
@@ -1309,7 +1309,8 @@ static guint do_request(GWeb *web, const char
*url,
session->address = g_strdup(session->host);
memset(&hints, 0, sizeof(struct addrinfo));
- hints.ai_flags = AI_NUMERICHOST;
+ /* Comment out next line to have AT&T MMS proxy work
*/
+ //hints.ai_flags = AI_NUMERICHOST;
hints.ai_family = session->web->family;
if (session->addr != NULL) {
diff --git a/src/service.c b/src/service.c
index c7ef255..a3b90c5 100644
--- a/src/service.c
+++ b/src/service.c
@@ -2527,6 +2527,9 @@ void mms_service_bearer_notify(struct mms_service
*service, mms_bool_t active,
g_web_set_debug(service->web, (GWebDebugFunc)debug_print,
NULL);
+ /* Explicitly close connections to work with AT&T */
+ g_web_set_close_connection(service->web,TRUE);
+
/* Sometimes no proxy is reported as string instead of NULL */
if (g_strcmp0(proxy, "") != 0)
g_web_set_proxy(service->web, proxy);
--
2.30.2
next prev parent reply other threads:[~2021-04-10 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 14:13 [PATCH 0/9] Updates for mmsd Chris Talbot
2021-04-10 14:17 ` [PATCH 1/9] Fix mmsd to work with T-mobile Chris Talbot
2021-04-10 14:20 ` [PATCH 2/9] Ensure Compatibility with Telus Canada Chris Talbot
2021-04-10 14:20 ` Chris Talbot [this message]
2021-04-10 14:21 ` [PATCH 4/9] Fix issue if there is an empty string in encoded text Chris Talbot
2021-04-10 14:22 ` [PATCH 5/9] Allow for a user configurable maximum attachment size Chris Talbot
2021-04-10 14:22 ` [PATCH 6/9] Update README Chris Talbot
2021-04-10 14:23 ` [PATCH 7/9] Fix Draft and Sent Bugs Chris Talbot
2021-04-10 14:23 ` [PATCH 8/9] Allow Maintainer mode to compile without -WError Chris Talbot
2021-04-10 14:24 ` [PATCH 9/9] Enable support for Modem Manager Chris Talbot
2021-04-14 18:21 ` Forking on MMSD Chris Talbot
2021-04-14 18:30 ` [Debian-on-mobile-maintainers] " Guido Günther
2021-04-14 18:46 ` Chris Talbot
2021-04-15 9:10 ` Guido Günther
2021-04-14 18:39 ` Marius Gripsgard
2021-04-14 22:09 ` Bug#985893: " Wookey
2021-04-15 0:12 ` Chris Talbot
2021-04-14 19:29 ` Pavel Machek
2021-04-14 21:11 ` Bug#985893: " Paul Wise
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 10:50 [PATCH 3/9] Ensure Compatibility with AT&T Christopher Talbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178dd29027e6abb4a205e25c02f06769848cbb76.camel@talbothome.com \
--to=chris@talbothome.com \
--cc=debian-on-mobile-maintainers@alioth-lists.debian.net \
--cc=librem-5-dev@lists.community.puri.sm \
--cc=netdev@vger.kernel.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).