SonyEricsson OTA

SonyEricsson OTA SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » SonyEricsson OTA « Previous || Next »
Author Message
Chris Reeves
Unregistered guest
Posted on Friday, May 14, 2004 - 12:35 pm:   

Hi,

Got some issues with OTA settings using the web interface:

We had a problems with version 4.2, many thanks this was fixed with 4.20a. Note both WAP and SyncML worked OK.

Moving to version 5.0 WAP OTA works fine but SyncML OTA does not. However the gateway has sent a message and the phones get the message but do not act on the message. The form has the OTA pin/pin (OMA) type could this be the issue?

Installing 5.5 and there are no SyncML OTA messages sent at all!

Any thoughts?

I've tested xml on 5.5 with no messages being sent out. But will test 5.0 to see is there is a xml format error in the basic SyncML OTA settings form.

Regards

Chris
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

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

Hi Chris,

I haven't had any problems sending SyncML OTA settings out to SonyEricsson phones with v5.5.

I normally send them out without a PIN (neither User PIN or Network PIN checked).

I just tried again right now, and it worked sending out to a T630. I also remember testing this with a P900 late last week.

What type of SMSC connection are you using?

I'm wondering. Another customer had a problem with WAP push messages not working after installing v5.5. We changed one default parameter in v5.5 in order to work better in many North America configurations.

Try editing SMSGW.INI, and under the [SMSGW] section header, add the parameter BinaryDCS=F5

This causes us to revert back to the way that we were sending out settings prior to v5.5.

But you say that v5.0 OTA wasn't working either?

Are there some example settings that you could give me, so that I can try sending the same settings that you are, and compare whether or not it works properly on my end? I'm just looking for any clue for why this would not be working ... like maybe some parameter combination.

Try the BinaryDCS setting first. If it doesn't make a difference, remove it so that this setting doesn't confuse anything else.

-bn
Chris Reeves
Unregistered guest
Posted on Friday, May 21, 2004 - 01:27 pm:   


Hi Bryce,

Had time to test today.

The ini setting worked.

The SMSC is a local modem (siemens).

Yep I tried on pin, and 5.0 was also not working.

Will this ini change
effect other things?

Regards

Chris
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2743
Registered: 10-2002
Posted on Tuesday, June 08, 2004 - 06:39 pm:   

Hi Chris,

I am curious what mobile operator you are using with the GSM modem. The setting that you change should not present any problems, we only made the change because we were having to frequently tell people in North America to use a setting for a different DCS value.

In previous versions of NowSMS, we used a DCS value of F5 as the default when sending out binary messages. That is a GSM specific DCS value which indicates that a message is binary, class 1.

We changed this default value to 04, which is a generic indicator of a binary message (and the default message class is 1).

So, both F5 and 04 should work exactly the same.

We found that in North America, quite a few systems could not handle the F5 value, because it was GSM specific (and even GSM carriers there often have a mix of GSM and TDMA equipment). Based upon our tests, 04 has seemed to work the same as F5 elsewhere, but apparently there is an issue with your mobile operator, that's why I'm curious who the mobile operator is.

-bn

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