| WAP PUSH not working with Wavecom Wismo |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Brian McSheehy New member Username: Brian947 Post Number: 1 Registered: 04-2006 |
Hi, I recently downloaded Now SMS to be used with a Wavecom Wismo WMOD2 GSM 1900 modem. I have Now SMS installed on a WinXP system with the modem attached via serial port and I am able to send regular SMS message with no problem via your included HTTP interface. However, I would like to be able to send a WAP Push message and have no been successful thus far. The message seems to be processed okay, however nothing is delivered to the phone. Regular Text SMS messages go through just fine. Here is the output of the SMSDEBUG Log when I attempt to send a WAP Push Message: 19:40:31:705 [6] ThreadProcessConnection: Processing connection from 192.168.1.101... 19:40:31:705 [6] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm 19:40:31:705 [6] ThreadProcessConnection: Request processing complete 19:40:47:627 [6] ThreadProcessConnection: Processing connection from 192.168.1.101... 19:40:47:627 [6] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm?WAPSL=&PhoneNumber=8082236470&WAPURL=http%3 A%2F%2Fwww.zingnow.com&Text=testing...&WAPSIACTION=signal-medium&WAPSIID=&WA PSICREATED=&WAPSIEXPIRES= 19:40:47:627 [6] Debug: 1 recipient entries 19:40:47:627 [6] Debug: 8082236470 19:40:47:627 [6] ThreadProcessConnection: Request processing complete 19:40:48:721 [2] ThreadProcessModem: Processing 442F6378.req... 19:40:48:721 [2] ThreadProcessModem: OUT: AT+CMGS=59 19:40:48:814 [2] ThreadProcessModem: IN: > 19:40:48:814 [2] ThreadProcessModem: OUT: 0041020A81082832460700042F0605040B8423F0780601AE02056A0045C60D037A696E676E6F 772E636F6D0007010374657374696E672E2E2E000101 19:40:52:111 [2] ThreadProcessModem: +CMGS: 71 OK ------ Here is an excerpt from SMSOUT-20060401 for the same message. 2006-04-01 19:40:52,442F6378.req,192.168.1.101,8082236470,OK -- COM1:,Binary=1;DCS=4;UDH=0605040B8423F0;Data=780601AE02056A0045C60D037A696E6 76E6F772E636F6D0007010374657374696E672E2E2E000101 ----------- Here is the contents of SMSGW.ini [Modem - COM1:] UseDial=No PhoneNumber=8086364504 ReceiveSMS=Yes ReceiveMMS=Yes ReceiveTo=SM [SMSGW] BinaryDCS=4 Debug=Yes Modem1=COM1: WebAuth=No WebMenu=Yes WebPort=8800 ReceiveSMS=No ReceiveMMS=No ReceiveSMSCharset=utf-8 ------ Could you please provide some assistance in helping me to get the WAP Push feature working? BTW, the GSM SIM card is using the T-Mobile North America Network. Thank You, Brian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5763 Registered: 10-2002 |
Hi Brian, We have a T-Mobile US SIM in a modem sitting in our US office, and I was just able to send a WAP Push out with it just fine. The one big problem that you have using modems in the US is that there is no cross-operator support for binary message types (including WAP Push). So with a T-Mobile SIM, you can send a WAP Push to another T-Mobile subscriber. But you can't send a WAP push to anyone on another network. (Sometimes the messages go through garbled, sometimes they are just lost.) It has to do with the way that they do SMS interoperability between the GSM and CDMA operators in the US ... where they just can't handle binary messages. (A few years ago, it used to be that you could send binary messages ok between the GSM carriers in the US, but that doesn't seem to be the case any more.) You can send MMS cross-operator in the US with a GSM/GPRS modem, as long as you configure NowSMS to route via the operator MMSC over GPRS instead of acting as a direct delivery MMSC. Which operators are reachable is dependent on the inter-operator agreements of the operator whose SIM you are using. (Last I checked, Cingular had a few more agreements than T-Mobile.) So ... getting back to your issue. As long as you are sending the push to another T-Mobile subscriber, it should work. I don't see anything that looks like an error in the message being generated for being sent out. The only thing unusual is the BinaryDCS=4 setting. But based on a quick test here, I can see that setting is fine with a modem on that network, so it shouldn't make a difference. What is the receiving phone? Maybe there is an issue with the phone. (For example, on SonyEricsson P800/P900/P910, push messages aren't received until you open the browser application. Or, on Windows Mobile devices, by default they are locked down so that they can't receive push messages.) -bn | |||
