Problem with SNPP to AT&T

[lnoland]

We are using pagegate version 4 and trying to send pages to AT&T Wireless at snpp.attws.net port 444

The pages are being sent but the log shows "Message not accepted"

Pagegate keeps trying to send the page over and over again and we receive it OK over and over again. Pagegate finally quits trying after 10 times and moves the page to the BAD directory.

What can we do to correct this?

Thanks

Enterprise Paging Gateway Addresses:

Protocol Address
TAP: (408)961-2819
SNPP: snpp.attws.net port 444
WCTP: http://wctp.attws.net/wctp
SMTP: <10 digit mobile number>@page.attws.net

[Tech Support]

Although there are servers at those WCTP and SNPP addresses, they do not appear to accept all AT&T ID/Pins.

You may want to consult with AT&T to determine if those servers are configured for general use, or if there are specific account options required.

Please keep us informed, so that we can update the information on our Protocol information pages.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[lnoland]

In speaking with AT&T the ID/PIN is not the problem. My phone number has been provisioned for use with AT&T Enterprise Paging
http://www.enterprisepaging.com

The problem with the SNPP interface is that they(ATT) ONLY support SNPP level 1 SNPP. That is using the MESS command.

Pagegate is using Level 2, using the DATA command. Their SNPP server will not support level 2 / DATA at this time.

How do we get pagegate to use level 1 / mess command instead of level 2 / data command?

Thanks

[Tech Support]

Would it be possible for you to turn on debugging in PageGate, send several test messages, then send a copy of the dialer log "PGDial1.log" to forumsupport@notepage.com?


Please do the following so that you will have detailed connection (debugging) information in the dialer log(s):

1.) Create a empty text file in the folder "C:\Program Files\PageGate\".
2.) Rename the file to "modem.dbg".

When you change the file name and extension, Windows should warn you about making the file unusable.

3.) Select "Yes".
4.) Stop PageGate's Dialer(s)
5.) Restart PageGate's Dialer(s)

Your modules will see the file (which acts as a flag) and the dialers will now write detailed debugging information to the logs.

I would suggest increasing the log size ('Logging' - 'Settings' - 'Max Log Length') to accommodate the increase in information being written to your logs.

After stopping and restarting the dialers, attempt to send several messages.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[lnoland]

========================================
8/10/2004 4:13:56 PM Start connection to carrier: ATT
8/10/2004 4:13:56 PM Connect using TAP protocol
8/10/2004 4:13:56 PM Setting communication parameters
8/10/2004 4:13:56 PM Attempting to reset modem
8/10/2004 4:13:58 PM Sent:AT<CR>
8/10/2004 4:13:59 PM Received:<CR><LF>OK<CR><LF>
8/10/2004 4:13:59 PM Modem reset
8/10/2004 4:13:59 PM Attempting to send dialer init string
8/10/2004 4:14:00 PM Sent:AT&FQ0V1X4&D2N0S37=5\N0%C0<CR>
8/10/2004 4:14:00 PM Received:<CR><LF>OK<CR><LF>
8/10/2004 4:14:01 PM Dialer init string sent
8/10/2004 4:14:01 PM Auto detecting carrier init string
8/10/2004 4:14:01 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2<CR>
8/10/2004 4:14:01 PM Received:<CR><LF>OK<CR><LF>
8/10/2004 4:14:01 PM Attempting to send carrier init string
8/10/2004 4:14:02 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2<CR>
8/10/2004 4:14:02 PM Received:<CR><LF>OK<CR><LF>
8/10/2004 4:14:03 PM Carrier init string sent
8/10/2004 4:14:03 PM Dialing carrier
8/10/2004 4:14:03 PM Sent:ATDT9,1408961281942433<CR>
8/10/2004 4:14:11 PM Waiting for connection
8/10/2004 4:14:37 PM Received:<CR><LF>CONNECT 1200<CR><LF>
8/10/2004 4:14:37 PM Connected to carrier
8/10/2004 4:14:37 PM Waiting for protocol initialization
8/10/2004 4:14:41 PM Sent:<CR>
8/10/2004 4:14:45 PM Received:?D?<0>
8/10/2004 4:14:45 PM Sent:<CR>
8/10/2004 4:14:49 PM Received:?D?<0>
8/10/2004 4:14:49 PM Sent:<CR>
8/10/2004 4:14:55 PM Received:?D?<0>
8/10/2004 4:14:55 PM Sent:<CR>
8/10/2004 4:15:01 PM Received:?D?<0>
8/10/2004 4:15:01 PM Attempting to hang up modem
8/10/2004 4:15:03 PM Sent:AT<CR>
8/10/2004 4:15:04 PM Received:<CR><LF>OK<CR><LF>
8/10/2004 4:15:04 PM Modem hung up
8/10/2004 4:15:41 PM ========================================

[Tech Support]

It looks like there is a TAP "parity" issue. The dialer is receiving question marks "?" as part of the response to our "Carriage Returns" when attempting to Initialize TAP.

We have confirmed that the TAP terminal at that number is capable of various Baud Rates up to 9600 and the following settings:

8 Data Bits, No(ne) Parity, 1 Stop Bit

AND

7 Data Bits, Even Parity, 1 Stop Bit

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[Tech Support]

Update:

SNPP is working with AT&T. PageGate does support both "DATA" and "MESS" commands.

The current issue is related strictly to TAP.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[lnoland]

Thanks, changing the parity to 8,none,1 worked for us.

Everything is working for us now in PageGate for AT&T Paging.

If people want to use paging (SMS) to their AT&T Wireless phones they will need to provision their wireless number to enable SMS paging to it via these interfaces.

http://www.enterprisepaging.com

Here are the settings that work for us right now.

Enterprise Paging Gateway Addresses:

TAP: (408) 961-2819 or (866) 833-7243 8,none,1
SNPP: snpp.attws.net port 444
WCTP: http://wctp.attws.net/wctp
SMTP: <10 digit mobile number>@page.attws.net

[lnoland]

Pagegate to SNPP for AT&T broke today.

It looks like AT&T started accepting the DATA command, but Pagegate is not recognizing that the page was dropped off at AT&T and thinks it failed, trying to send the page over and over. We get all of the retries.
Previously AT&T rejected the DATA command, and pagegate then switched to the MESS command, and the page worked ok. Here is the log for this:

9/2/2004 10:36:43 AM ----------------------------------------
9/2/2004 10:36:43 AM Working on message to: lnolan from: salive
9/2/2004 10:36:43 AM Formatting message
9/2/2004 10:36:43 AM Message contained in single packet
9/2/2004 10:36:43 AM Carrier message limit reached, Reconnecting...
9/2/2004 10:36:43 AM Sent:QUIT

9/2/2004 10:36:43 AM Disconnected
9/2/2004 10:36:43 AM Disconnected from server
9/2/2004 10:36:44 AM Connected to Host
9/2/2004 10:36:45 AM Received:220 SNPP Gateway Ready,UEG 1.0

9/2/2004 10:36:45 AM SNPP Session Started
9/2/2004 10:36:45 AM Sending message
9/2/2004 10:36:45 AM Sent:PAGE 5014990384

9/2/2004 10:36:45 AM Received:250 Pager Id 15014990384 Accepted

9/2/2004 10:36:45 AM Sent:DATA

9/2/2004 10:36:45 AM Received:354 Enter mail, end with . on a line by itself

9/2/2004 10:36:45 AM Sent:salive:CTS6-ETHER is DOWN
9/2/2004 10:36:45 AM Sent:
.

9/2/2004 10:36:46 AM Received:250 Message OK

9/2/2004 10:36:46 AM Sent:SEND

9/2/2004 10:36:47 AM Received:960 5014990384 13510 OK, Message accepted for Delivery

9/2/2004 10:36:47 AM Message not accepted
9/2/2004 10:36:47 AM Failed Attempt Stn:1 To:lnolan Frm:salive File:CTS6-ETHER.324 Msg:CTS6-ETHER is DOWN

9/2/2004 10:36:47 AM Sent:RESE

9/2/2004 10:36:47 AM Received:250 Reset OK

9/2/2004 10:36:47 AM ----------------------------------------

[lnoland]

There are two ways to send to AT&T Wireless Phones (SMS):

<10 digit mobile number>@page.attws.net is better for pages (cleaner)

<10 digit mobile number>@mobile.att.net is better for email

Try both and see what works best for you