Wap push SI

Wap push SI SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Wap push SI « Previous || Next »
Author Message
Anonymous
 
Posted on Saturday, May 08, 2004 - 02:10 pm:   

When I upgraded to the official nowsms 5.5 release, my nokia 6100 displayed garbled characters when getting a wap push si it was fine for the 5.5 beta release. can you help bruce?
Anonymous
 
Posted on Tuesday, May 11, 2004 - 01:40 pm:   

I think there is a bug with wap push SI in the offfical 5.5 release as I tried it with other nokia phones and got garbled message. Pls help!!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2554
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 02:03 pm:   

I'm not seeing a problem here. I don't have a Nokia 6100, but I've tried a 6600, 3650 and 6820.

However, we did change one thing, mainly related to being friendlier to CDMA ... and to address an issue where in the Americas we frequently had to have customers manually change the DCS value used for WAP push and MMS notifications.

To go back to the way it was done pre-5.5, edit SMSGW.INI, and under the [SMSGW] section header, add the statement: BinaryDCS=F5

Conventionally, a DCS value of F5 has been used for Nokia Smart Messaging binary messages.

However, a DCS value of 4 is the generic setting to indicate that a message is in binary format. And we have observed that other WAP push proxies and MMSCs seem to use the value 4.

Perhaps the SMSC to which you are connecting does not properly interpret the DCS value of "4" as indicating a binary message?

What protocol are you using for the SMSC connection?
Anonymous
 
Posted on Thursday, May 13, 2004 - 01:59 am:   

Hi Bruce,
I am just using an itegno gsm modem so I shd add the statement: BinaryDCS=F5 into the swgw.ini?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2596
Registered: 10-2002
Posted on Friday, May 14, 2004 - 02:04 am:   

Yes, edit SMSGW.INI, and under the [SMSGW] section header, add the statement: BinaryDCS=F5

Please let me know if this makes a difference for you.

Also, I am curious what mobile operator you are connected to, as this seems most unusual.
Anonymous
 
Posted on Saturday, May 15, 2004 - 02:07 am:   

Singtel mobile from Singapore
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2633
Registered: 10-2002
Posted on Wednesday, May 19, 2004 - 02:00 am:   

Did the BinaryDCS=F5 parameter make a difference?
Anonymous
 
Posted on Sunday, May 23, 2004 - 02:37 am:   

Hi Bryce,
I added BinaryDCS=F5 into smsgw.ini but it does work I got the sms as a garbled message rather than an Wap SI
Anonymous
 
Posted on Tuesday, May 25, 2004 - 01:04 pm:   

Hi Bryce,
I added BinaryDCS=F5 into smsgw.ini but it does work I got the sms as a garbled message rather than an Wap SI
Kent Williams
Moderator
Username: Kent

Post Number: 76
Registered: 10-2003
Posted on Wednesday, May 26, 2004 - 04:08 pm:   

But this definitely worked before, and nothing changed but the NowSMS version?

We haven't seen any other reports, so it is difficult to imagine what the problem could be.

I've made v5.01 available for download again under a link of http://www.nowsms.com/download/nowsms501.exe.

Please try installing that version, and see if that works properly. If it does, then we'll have to analyse the logs to see what is different.

--
Kent Williams
Now Wireless Support
Anonymous
 
Posted on Thursday, May 27, 2004 - 12:38 am:   

5.01 works fine, even the beta release of 5.5 which I am on now works fine only the official release gives me this problem
Anonymous
 
Posted on Friday, May 28, 2004 - 12:36 am:   

5.01 works fine, even the beta release of 5.5 which I am on now works fine only the official release gives me this problem. Pls help!!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2754
Registered: 10-2002
Posted on Tuesday, June 08, 2004 - 07:56 pm:   

Apologies for the delay in rejoining this thread.

We had one customer who had to implement the setting BinaryDCS=F5 under the [SMSGW] section header of SMSGW.INI in order to get OTA settings and WAP Push messages to work with v5.50.

I can't imagine any other reason why things would be different between v5.01 and v5.50.

Let's try this.

Send a WAP push message.

Install v5.50.

Send a WAP push message.

I'd like to see the SMSOUT-yyyymmdd.LOG file, so that I can see what is different about the two messages that are sent out.

-bn
Anonymous
 
Posted on Friday, June 11, 2004 - 12:44 pm:   

Hi Bryce,
Attachment pls find the 2 smsout logs
application/octet-streamNowsms 5.5 official
SMSWEB-20040611.LOG (0.2 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2816
Registered: 10-2002
Posted on Friday, June 11, 2004 - 06:11 pm:   

That was one log ... the SMSWEB log. I'd like to see the SMSOUT logs.

Thanks.
Anonymous
 
Posted on Saturday, June 12, 2004 - 06:38 am:   

sorri here it goes
application/octet-stream
SMSOUT-20040611.LOG (0.4 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2848
Registered: 10-2002
Posted on Tuesday, June 15, 2004 - 09:02 pm:   

Ok,

Edit SMSGW.INI, and under the [SMSGW] section header, add the statement: BinaryDCS=F5

From your log file, I can see that your message is going out with DCS=4. When this setting is present, you should see DCS=F5 in the log instead.

Or, download this update:

http://www.nowsms.com/download/nowsms550a.zip

We switched the default back to F5, because although the "4" value works better in North America, there were problems with some other operators.

-bn
Anonymous
 
Posted on Wednesday, June 16, 2004 - 12:24 am:   

Thanks bryce finally resolve it

Login Login / Register Logout Logout Search Last 30 Days Topics Topics