SMS Gateway not responding
pjharren01
Enthusiast - Level 2

The Verizon SMS gateway  (vtext.com) does not respond to attempts to deliver messages. This problem began around noon on 4/18/2023. We are a gated community and send text messages to residents when their visitors arrive at the gate. We send about 100 texts per day to Verizon customers.  Around 700 - 800 residents are Verizon customers who are not receiving their text messages from us.

0 Likes
Reply
1 Solution
vzw_customer_support
Customer Service Rep

Hello pjharren01,

 

Thank you for reaching out. We want to do all we can to ensure our products are meeting your needs. I want to advise that Vtext.com is intended for consumer use only.

 

The service is not intended to be used for large volumes of commercial messages or emergency messages. Due to the inherent limitations of Internet email, Verizon provides no assurance regarding the timeliness or receipt of messages sent using this service. 

 

The good news is that we do offer a service that is more closely aligned with your intended use, Enterprise Messaging, which you can learn more about here: https://www.verizon.com/business/products/voice-collaboration/workforce-productivity/business-messag...

 

I hope this information helps you reach a solution that better meets your needs!

-Colin

View solution in original post

0 Likes
Reply
4 Replies
vzw_customer_support
Customer Service Rep

Hello pjharren01,

 

Thank you for reaching out. We want to do all we can to ensure our products are meeting your needs. I want to advise that Vtext.com is intended for consumer use only.

 

The service is not intended to be used for large volumes of commercial messages or emergency messages. Due to the inherent limitations of Internet email, Verizon provides no assurance regarding the timeliness or receipt of messages sent using this service. 

 

The good news is that we do offer a service that is more closely aligned with your intended use, Enterprise Messaging, which you can learn more about here: https://www.verizon.com/business/products/voice-collaboration/workforce-productivity/business-messag...

 

I hope this information helps you reach a solution that better meets your needs!

-Colin

0 Likes
Reply
pjharren01
Enthusiast - Level 2

We are a gated community of about 2400 homes. Approximately one-third of our residents are Verizon customers.  For several years we have offering residents text notification of the arrival of their visitors at the gate. This has been very popular with residents. Verizon customers have been generally pleased except for occasional complaints of late delivery of our text messages. Subscribing to your Business Messging is not a reasonable option. Less than 100 messages a day is not a large volume. We just want to get back to the service before you made your change yesterday. 

So, what can we tell your unhappy customers other than suggest that they consider changing to a different carrier?

0 Likes
Reply
RadioJim
Newbie

I  came across this thread because I too am having SMS/MMS gateway issues. The posture of Verizon to blame the costumer and the internet is unseemly. I've been around the internet for over 30 years and I know how email works! The problem is not with "internet email" it is with Verizon's equipment. I use SMS to pass notices from my ham radio spotting system to my phone when an operator of interest comes on the air and I am away from the radio. This is a 100% non-commercial consumer use case and is time sensitive as the operator will typically be on the air for only a short time. It is not at all helpful when the SMS/MMS messages come through days later.  Based on what I have read so far I will be looking for a more reliable service.

0 Likes
Reply
pjharren01
Enthusiast - Level 2

The Verizon SMS gateway  (vtext.com) does not respond to attempts to deliver messages. This problem began around noon on 4/18/2023. We are a gated community and send text messages to residents when their visitors arrive at the gate. We send about 100 texts per day to Verizon customers.  Around 700 - 800 residents are Verizon customers who are not receiving their text messages from us. The notification from the Outlook mail server is:

 

Delivery has failed to these recipients or groups:

 

 (part of message removed per rules)

Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond.

Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their email system isn't accepting connection requests from your email system. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem.

For more information and tips to fix this issue see this article: .

Diagnostic information for administrators:

Generating server: SA1PR17MB4643.namprd17.prod.outlook.com
Receiving server: SA1PR17MB4643.namprd17.prod.outlook.com
Total retry attempts: 7

[email address removed per the Verizon Terms of Service]
5/19/2023 12:45:33 PM - Server at SA1PR17MB4643.namprd17.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
5/19/2023 12:36:28 PM - Server at vrz-sms.mx.a.cloudfilter.net (35.165.168.89) returned '421 4.4.2 Connection dropped due to SocketError'

Original message headers:

Received: from PH0PR17MB5913.namprd17.prod.outlook.com (2603:10b6:510:164::12)
 by SA1PR17MB4643.namprd17.prod.outlook.com (2603:10b6:806:196::7) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.19; Fri, 19 May
 2023 09:23:00 +0000
Received: from MW4PR17MB5500.namprd17.prod.outlook.com (2603:10b6:303:127::12)
 by PH0PR17MB5913.namprd17.prod.outlook.com (2603:10b6:510:164::12) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.17; Fri, 19 May
 2023 00:48:24 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=CqaCSABVYf7FIzVPV9dI/onioCODhPJiLq7Kq6bWGXquiG0EHbpgCwrWuAzcxx0nxI7IjD9lJJuJF7ZxYzRoAlkIuLStrStOR6v1+73C3IdezQQkGn8sJYObLPKJ369vo9s5/X1S+Cfhy0zG8WEYxxwSxI5wAeeFwuHtxpFRdgRudRPOgVppSCd4eh5UZJufEaoGhJBsBomEhxObazQ0nwFbDZfDZEjuG9WfWjTfF0tDzN2OIJMuS6DaJVnQnW1nLOxKieIxDPdleDvA43zn6jCPaj6BAdmK7qjTRVXHkVcxibLr3o2MhBlKTe3ySBi4wF8a6O+QJQ5XGF2mavObnA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=8Xo2FdLbfiHDr1Ew0ZzhhZ2brA6G1yJpZMvOgiVw6us=;
 b=DC0GoPlE/Zgp+RblYqkLXV1B9hiLhdfkEkPSgoaV0iwUHT4kaE/LTQ6b1YuhDlK+De58NZA8ZA9xDdZZJzRt84DTJtOFUkobqmOkLHlIKcBnP0RmPbhGOyHAY6pKS1KWxEy5iJwNlPM/B2U/hRo7cXXznPhE8GK8Mdm2Zh7fFhmMbejAd6rzWYBXBeulHg2jkMAhjyGsMEmtz3LoXnw1dl5zHgCr34XeAmVf/x/tl4loxEh72d3+zkKpdiVQYnmGK9ZrrrhAffQdGBb8XX7XOQUCVHoThY+4ExIDZ5aOTyTmkSjyBLbTkL4KwXswR8UmfRNZBHR7NRPuN9NFHE4zXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=bentwaterpoa.com; dmarc=pass action=none
 header.from=bentwaterpoa.com; dkim=pass header.d=bentwaterpoa.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BWpoa.onmicrosoft.com;
 s=selector2-BWpoa-onmicrosoft-com;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=8Xo2FdLbfiHDr1Ew0ZzhhZ2brA6G1yJpZMvOgiVw6us=;
 b=m5+GMofC8d+iF8kTtN7rs02fUN/JvmExP8LtZ2TIMPnlLoI96cgMuSeFnM/SPrR8I/zdc48xmSkXdi1OH0JgXpG5t8p8/FdbauTF2PP8C/Mp299MwLwV7OWt+JcN1pSXAzOgAmPLo8as58BcB0UgkPl+6zoV79DNK/nQAwFEmMQ=
Authentication-Results: dkim=none (message not signed)
 header.d=none;dmarc=none action=none header.from=bentwaterpoa.com;
Received: from MW4PR17MB4732.namprd17.prod.outlook.com (2603:10b6:303:109::14)
 by MW4PR17MB5500.namprd17.prod.outlook.com (2603:10b6:303:127::12) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.19; Thu, 18 May
 2023 12:45:33 +0000
Received: from MW4PR17MB4732.namprd17.prod.outlook.com
 ([fe80::e89b:bb63:99f8:39a]) by MW4PR17MB4732.namprd17.prod.outlook.com
 ([fe80::e89b:bb63:99f8:39a%5]) with mapi id 15.20.6411.019; Thu, 18 May 2023
 12:45:33 +0000

 

0 Likes
Reply