Ask a question
Search in Wireless Forums

Wireless Forum

Reply
Posted Aug 4, 2010
10:14:11 AM
View profile
Text reports sent from an emergency application to AT&T Users are not being delivered

We are sending reports as text to customer with critical information about fire alarms, these reports are not being received by AT&T carrier users, please review the heather bellow to see if there is something we can change to process these reports properly thru AT&T.

Please advise.

 

Delivered-To: sundain@gmail.com

Received: by 10.151.148.13 with SMTP id a13cs359275ybo;

        Tue, 27 Jul 2010 11:42:57 -0700 (PDT)

Received: by 10.142.144.16 with SMTP id r16mr10858176wfd.135.1280256177031;

        Tue, 27 Jul 2010 11:42:57 -0700 (PDT)

Return-Path: <NoReply@centraldispatchcenter.com>

Received: from Mail.moonsecurity.com (mail.moonsecurity.com [64.185.101.232])

        by mx.google.com with ESMTP id 8si11047115wfb.94.2010.07.27.11.42.56;

        Tue, 27 Jul 2010 11:42:56 -0700 (PDT)

Received-SPF: pass (google.com: domain of NoReply@centraldispatchcenter.com designates 64.185.101.232 as permitted sender) client-ip=64.185.101.232;

Authentication-Results: mx.google.com; spf=pass (google.com: domain of NoReply@centraldispatchcenter.com designates 64.185.101.232 as permitted sender) smtp.mail=NoReply@centraldispatchcenter.com

Received: from manatou ([10.0.1.45]) by Mail.moonsecurity.com with Microsoft SMTPSVC(6.0.3790.4675);

         Tue, 27 Jul 2010 11:42:55 -0700

From: "Alarm Report" <noreply@centraldispatchcenter.com>

To: sundain@gmail.com

Subject: Notification

X-Mailer: CSMTPConnection v2.38

Content-Type: text/plain;

        charset=utf-8

Date: Tue, 27 Jul 2010 11:42:55 -0700

Return-Path: noreply@centraldispatchcenter.com

Message-ID: <X-FACTORsDSzhxRz3s200000f35@Mail.moonsecurity.com>

X-OriginalArrivalTime: 27 Jul 2010 18:42:55.0915 (UTC) FILETIME=[871CFFB0:01CB2DBB]

 

Trouble Report: 07/27/2010 11:42

TRAINING - Margo Polo

Signal: PA Panic Alarm

Zone: 3

Descr: Entry Motion

We are sending reports as text to customer with critical information about fire alarms, these reports are not being received by AT&T carrier users, please review the heather bellow to see if there is something we can change to process these reports properly thru AT&T.

Please advise.

 

Delivered-To: sundain@gmail.com

Received: by 10.151.148.13 with SMTP id a13cs359275ybo;

        Tue, 27 Jul 2010 11:42:57 -0700 (PDT)

Received: by 10.142.144.16 with SMTP id r16mr10858176wfd.135.1280256177031;

        Tue, 27 Jul 2010 11:42:57 -0700 (PDT)

Return-Path: <NoReply@centraldispatchcenter.com>

Received: from Mail.moonsecurity.com (mail.moonsecurity.com [64.185.101.232])

        by mx.google.com with ESMTP id 8si11047115wfb.94.2010.07.27.11.42.56;

        Tue, 27 Jul 2010 11:42:56 -0700 (PDT)

Received-SPF: pass (google.com: domain of NoReply@centraldispatchcenter.com designates 64.185.101.232 as permitted sender) client-ip=64.185.101.232;

Authentication-Results: mx.google.com; spf=pass (google.com: domain of NoReply@centraldispatchcenter.com designates 64.185.101.232 as permitted sender) smtp.mail=NoReply@centraldispatchcenter.com

Received: from manatou ([10.0.1.45]) by Mail.moonsecurity.com with Microsoft SMTPSVC(6.0.3790.4675);

         Tue, 27 Jul 2010 11:42:55 -0700

From: "Alarm Report" <noreply@centraldispatchcenter.com>

To: sundain@gmail.com

Subject: Notification

X-Mailer: CSMTPConnection v2.38

Content-Type: text/plain;

        charset=utf-8

Date: Tue, 27 Jul 2010 11:42:55 -0700

Return-Path: noreply@centraldispatchcenter.com

Message-ID: <X-FACTORsDSzhxRz3s200000f35@Mail.moonsecurity.com>

X-OriginalArrivalTime: 27 Jul 2010 18:42:55.0915 (UTC) FILETIME=[871CFFB0:01CB2DBB]

 

Trouble Report: 07/27/2010 11:42

TRAINING - Margo Polo

Signal: PA Panic Alarm

Zone: 3

Descr: Entry Motion

Text reports sent from an emergency application to AT&T Users are not being delivered

803 views
3 replies
(0) Me too
(0) Me too
Reply
View all replies
(3)
0
(0)
  • Rate this reply
View profile
Aug 5, 2010 1:26:03 PM
0
(0)
Expert

this is a peer to peer forum, att only supplies moderation. Best bet is to call them

this is a peer to peer forum, att only supplies moderation. Best bet is to call them

Re: Text reports sent from an emergency application to AT&T Users are not being delivered

2 of 4 (767 Views)
0
(0)
  • Rate this reply
View profile
Dec 20, 2010 1:08:21 PM
0
(0)
Tutor

Did you ever get a response to this? I'm having this issue as well. AT&T support has been useless.  I don't receive my alerts from my alarm company to txt.att.net, but I do get them to my email addresses.

Did you ever get a response to this? I'm having this issue as well. AT&T support has been useless.  I don't receive my alerts from my alarm company to txt.att.net, but I do get them to my email addresses.

Re: Text reports sent from an emergency application to AT&T Users are not being delivered

3 of 4 (509 Views)
Highlighted
0
(0)
  • Rate this reply
View profile
Dec 21, 2010 11:10:22 AM
0
(0)
Tutor

Resolved:  So after speaking to 9, that's correct NINE!! AT&T people, I asked my alarm company to change the txt.att.net to mms.att.net and it somehow magically resolved it.   I got quite the run around from AT&T and not ONE of their techs or agents recommended this.  I just happend to read it somewhere on here about the mms.att.net and decided to try it.

 

Once my contract is up, i'm out.  "Can you hear me now" Man Wink

Resolved:  So after speaking to 9, that's correct NINE!! AT&T people, I asked my alarm company to change the txt.att.net to mms.att.net and it somehow magically resolved it.   I got quite the run around from AT&T and not ONE of their techs or agents recommended this.  I just happend to read it somewhere on here about the mms.att.net and decided to try it.

 

Once my contract is up, i'm out.  "Can you hear me now" Man Wink

Re: Text reports sent from an emergency application to AT&T Users are not being delivered

4 of 4 (478 Views)
Share this post
Share this post