WAP Push on at&t | ![]() |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
Author | Message | |||
GSM TEST New member Username: Gsmtest Post Number: 5 Registered: 04-2006 |
At&t recently made a change to their network that blocks mobile originated WAP Push messages. Any attempt to send results in an error code 38. Is there another delivery method that I could configure in NOWSMS to deliver Push messages to a device on their network? Using v2008.06.03 | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 676 Registered: 08-2008 |
Sigh ... the things that mobile operators do because they think they are protecting their subscribers. You should feel safer, not inconvenienced. ![]() You can try different DCS values. NowSMS defaults to using DCS=F5, which is a binary message with explicit message class information set. A WAP Push message is also valid if you use a generic binary DCS value of 4 (no message class information). To use this alternate value, edit SMSGW.INI, and under the [SMSGW] header, add BinaryDCS=4. Then restart the NowSMS server and see if this works. -- Des NowSMS Support | |||
GSM TEST New member Username: Gsmtest Post Number: 7 Registered: 04-2006 |
That doesn't work, but i found that i can send WAP Push messages using the binary message option in Now SMS. Are there any other changes i can make to the WAP push tab that would emulate these settings and allow the WAP push tab to be used instead? Coding each message is a real pain. This binary data sends successfully UDH - 0605040B8423F0 PID – 1 DCS – F5 Binary data - 740601AE etc......... | |||
GSM TEST New member Username: Gsmtest Post Number: 8 Registered: 04-2006 |
I figured it out. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 852 Registered: 08-2008 |
What was the resolution? |