Aura Messaging 6.3

[TN94z]

We are implementing Aura Messaging 6.3 and also use Session Manager and System Manager. With CallPilot, we sent out remote notification to alphanumeric pagers to alert of new messages. Has anyone used this within Aura Messaging on pagers other than the pre-defined ATT, Verizon, etc...? We cannot seem to get this to work. Thanks

 

[KenMeans]

AAM only supports SMTP pagers so if you are using something else you need to play with the call me feature to see if it will work with the older type pagers

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[TN94z]

I never got it to work but did find out the pagers are smtp as well. I am just waiting on the customer to give our AAM permission to send emails outside their domain since we point everything to their exchange server.

 

[KenMeans]

If they don't it will never work unless they move the pagers in house.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[TN94z]

So the customer gave AAM permission to send the emails and that resolved the pager issue. My last problem is getting AAM to send a test to cell phones. That doesn't seem to work no matter how I configure the mobile operators. I am going to play around with it some more today.

 

[KenMeans]

When you say "send a test to cell phones" do you mean a call or a SMS ?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[TN94z]

I'm sorry, I mean SMS. The calls work fine. Using this mobile operator definition for example:

{10}@txt.att.net

I can send an email using that the 10 digit number@txt.att.net. But notification from AAM is not successful

 

[TN94z]

I can put cell number@txt.att.net into the email notification and it sends the text just fine.

 

[KenMeans]

Updated:
  
17 Aug 2016
Author:
  
Charles Christner
 
Details
AAM Notify Me cannot send text messages to AT&T mobile phones.
Notify Me text notifications work to Verizon Mobile phones.
On initial configuration Text Notify Me worked to all carriers used.
The site has advised no known changes.
Problem Clarification
Text messages from AAM Notify Me are not received by the AT&T users.
IMAP/SMTP Messaging Log shows the text is delivered to the Mailbox Gateway Machine Name configured on the Storage Server found under Administration>Messaging>IMAP/SMTP Settings>Mail Options.
 
SMTP log:
Mar 11 14:57:18 voicemail postfix/smtp[24902]: 03936110051: to=<818xx@txt.att.net>, relay=xx[xx]:25, delay=30, delays=0.03/0.01/0/29, dsn=2.6.0, status=sent (250 2.6.0 <14887873.610.1457737006527.xx@xx.com> [InternalId=72315228] Queued mail for delivery)
Mar 11 14:57:18 voicemail postfix/qmgr[25911]: 03936110051: removed
Cause
The logs show the Text message from the AAM are being successfully sent to the Mailbox Gateway Machine (SMTP Proxy Server).
This means the Mailbox Gateway Machine is not forwarding the text messaging or the Carrier is not accepting it.
Solution
1. Verify the users Notify Me text configuration has a 10 digit number and that the Mobile Operator is correct.
2. Verify the Mobile Operators for the vender are correct:
Storage Server Administrator>Messaging>Messaging System (Storage) >Class of Server>Notification>(See Mobile Operators) link.  The configuration can be compared with the Mobile carrier's website for the correct format.
3. Verify the IMAP/SMTP Messaging log for delivery failures.
   a. If failures are found with communication to the Mailbox Gateway Name test communication via  nslookup -type=mx port25.com and make corrections as needed.
   b. If failures are not found then advise the Mailbox Gateway administrator to verify communication to the mobile carrier.
Note: Changes to the Mailbox Gateway Name under Trusted Hosts are not service affecting to AAM call answering.  Changes to the trusted hosts name or IP may affect communication network communication with that server.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[TN94z]

That looks identical to my log. I have sent an email to the administrator at the customer site to verify whether or not it was successfully sent to the carrier.

 

[TN94z]

So after further conversations, it looks like AT&T is bouncing it back because the return address is postmaster@xx.com. So I am going to try to assign the voicemailnoreply@xx.com as the return address on these and see if that resolves the issue. I will update