AT&T Business Messaging

Learn how to use your AT&T Business Messaging service. Receive tips on how to log in to the AT&T Business Notification Center website to build lists and send messages, or integrate with notification applications. Use our step by step walk-throughs to learn how to create, edit, import, and export both contacts and groups.

Back to product page

AT&T Business Messaging protocols and their specifications

Simple Mail Transfer Protocol (SMTP):

 

Protocol

Address

Message Length

Delivery Receipts

Two-way

SMTP

mobilenumber@page.att.net

1000

Yes

Yes

 

 

 

SMTP Troubleshooting tips:

  1. Ensure that the receiving device is provisioned with Business Messaging.
  2. The two most common issues with SMTP delivery are: using one of the consumer e-mail gateways or issues with SMTP relays in customer and intermediate networks.
  3. Verify that the application is set to send messages to mobilenumber@page.att.net, not one of the consumer e-mail gateways (for example @txt.att.net).
  4. To test delivery receipts, send a message from the application to mobilenumber@page.att.net and request a delivery receipt.
  5. When sending messages to Public Groups created in the BNC, ensure that you are using the group name with the correct letters in lower and upper case as the address is case sensitive. Messages with the Public Group name in the wrong case will not be successful.

 

Simple Network Paging Protocol (SNPP):

Protocol

Address

Message Length

Delivery Receipts

Two-way

SNPP

http://snpp.att.net port 444

1000

Yes

Yes

 

 

 

SMTP Troubleshooting tips:

 

  1. Ensure that the receiving device is provisioned with Business Messaging.
  2. Verify network connectivity and ping snpp.att.com port444. If this is unsuccessful, configure firewalls or proxy servers to allow traffic over port 444 with the paging gateway.
  3. If successful, try to manually send a message using Telnet.
  4. Telnet to snpp.att.com port 444 (Responses from gateway in italics, your entries in bold)

Response: 220 SNPP Gateway Ready

Entry: PAGE

Response: 250 Pager ID Accepted

Entry: MESS

Response: 250 Message OK

Entry: SEND

Response: 960 OK, Message accepted for Delivery

Entry: QUIT

Response: 221 OK, Goodbye

 

Wireless Communications Transfer Protocol (WCTP):

 

Protocol

Address

Message Length

Delivery Receipts

Two-way

WCTP

http://sctp.att.net/WCTP port 80

https://wctp.att.net/WCTP port 443

1000

1000

Yes*

Yes*

 

 

 

 

 

 

Note: To retrieve delivery receipts and two-way messages via WCTP, you must obtain a senderID/pollerID and Security Code.

WCTP troubleshooting tips:

  1. Ensure that the receiving device is provisioned with Business Messaging.
  2. From the machine the paging application is running on, open a browser and go to http://wctp.att.com/WCTP or https://wctp.att.com/WCTP. “DONE” should appear in the browser if it is able to connect to the paging gateway.
  3. Some paging applications require a “pollerID” or “senderID” to retrieve delivery receipts and replies from the paging gateway. Obtain a WCTP pollerID/senderID at http://bmam-businessmessaging.att.com/wctppollerid.jsp.

 

Telelocator Alphanumeric Protocol (TAP):

 

Protocol

Address

Message Length

Delivery Receipts

Two-way

SMTP

mobilenumber@page.att.net

1000

No

No

 

 

 

Modem configuration should be set to 9600 baud and E,7,1 or N,8,1.

 

TAP troubleshooting tips:

  1. Ensure that the receiving device is provisioned with Business Messaging.
  2. Verify the correct phone number: (888) 298-3562 or (214) 452-0299.
  3. Modem configuration should be set to 9600 baud and E,7,1 or N,8,1.
  4. Try a baud rate of 9600 (if it fails, try going lower to 2400 & 1200 bps).
  5. Try E,7,1 first (Even parity, 7 bits, 1 stop bit).
  6. If it fails, try N,8,1 (No parity, 8 bits, 1 stop bit).