| WAP Push SI fails to send |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ Archive through September 20, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Jason Scrod New member Username: Captainscrod Post Number: 6 Registered: 06-2012 |
Hello, I am unable to send a WAP Push SI message via NowSMS Lite. I'm wondering if there is something wrong with my modem or if the network is rejecting the message. I can send SMS/MMS messages just fine. I keep getting this generic "+CMS ERROR: 111" error and the message sits in the outbox queue retrying over and over. This is the modem that I have: Option Icon322 http://www.option.com/en/support/software-download/icon322/ Recent User Activity: -------------------- 2012-09-18 18:42:47,nowuser,SMSSubmit,5555555555,192.168.1.100,4FD17AF6.req,WAPPush,DCS=F5; UDH=0605040B8423F0;Data=610601AE02056A0045C60D037961686F6F2E636F6D00070103636865 636B206F757420746869732073776565742077656273697465000101;Binary=1 Logging from SMSDEBUG.LOG: ------------------------- 18:42:47:449 [18] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm?WAPSL=&PhoneNumber=5555555555&WAPURL=http%3A%2F %2Fwww.yahoo.com&Text=check+out+this+sweet+website&WAPSIACTION=signal-medium&WAPSII D=&WAPSICREATED=&WAPSIEXPIRES= 18:42:47:449 [18] Debug: 1 recipient entries 18:42:49:165 [16] ThreadProcessModem: Processing 4FD17AF6.req... 18:42:49:180 [16] ThreadProcessModem: OUT: AT+CMGS=75 18:42:49:211 [16] ThreadProcessModem: IN: > 18:42:49:211 [16] ThreadProcessModem: OUT: 0041170A81555555555500F53F0605040B8423F0610601AE02056A0045C60D037961686F6F2E636F 6D00070103636865636B206F757420746869732073776565742077656273697465000101 18:43:18:555 [16] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 111 18:43:18:555 [16] ThreadProcessModem: OUT: 8:43:18:664 [16] ThreadProcessModem: OUT: \r 18:43:18:664 [16] ThreadProcessModem: OUT: AT 18:43:18:680 [16] ThreadProcessModem: IN: ERROR 18:43:19:210 [16] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 111 18:43:20:006 [16] ModemTest: GlobeTrotter Icon322 - Modem Interface 18:43:20:146 [16] ModemTest: OK 18:43:22:112 [16] ThreadProcessModem: Processing 4FD17AF6.req... 18:43:22:143 [16] ThreadProcessModem: OUT: AT+CMGS=75 18:43:22:159 [16] ThreadProcessModem: IN: > 18:43:22:159 [16] ThreadProcessModem: OUT: 0041180A81555555555500F53F0605040B8423F0610601AE02056A0045C60D037961686F6F2E636F 6D00070103636865636B206F757420746869732073776565742077656273697465000101 Is there any additional logging that I could enable? Thanks, Jason | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8020 Registered: 10-2002 |
Hi Jason, What mobile operator is the modem connected to? Some mobile operators, most notably AT&T, block mobile originated push requests. I seem to remember one other mobile operator that refused to accept DCS=F5 messages. If you are using a mobile operator other than AT&T, you can try editing SMSGW.INI, and under the [SMSGW] header, add BinaryDCS=4. This setting will only affect newly submitted messages, not ones pending retry in the queue. It is worth trying, but very low probability of resolving the problem. Unfortunately, if you are using AT&T, or another operator that is blocking mobile originated push messages, the only solution is using SMPP with a service provider that supports these messages. (In the US market, that is difficult. If you need a recommendation, I'd need to do some searching through other threads and e-mails to see what others are using. In general, WAP push is not a good solution for US markets as the providers that can support it only support AT&T, T-Mobile and a few GSM based regional operators.) -bn | |||
| Jason Scrod New member Username: Captainscrod Post Number: 7 Registered: 06-2012 |
Hi Bryce, Thanks for the info. I had previously messed with the BinaryDCS=4 option based on a thread that I came across in these forums. That didn't work. This confirms my suspicion that the carrier is rejecting the wap push SI. I was just trying this out of curiosity, so not a big deal that it doesn't work. Thanks again, Jason | |||
