GPRS setting via OTA have a problem with Samsung?

GPRS setting via OTA have a problem with Samsung? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » GPRS setting via OTA have a problem with Samsung? « Previous || Next »
Author Message
ehsan alizadeh
New member
Username: Ehsan123

Post Number: 1
Registered: 09-2005
Posted on Sunday, September 11, 2005 - 06:05 am:   

I have sent GPRS setting OTA for Nokia and SonyEricsson and Siemens. All of them know and accept it as a GPRS setting but Samsung X600 hadn't recieved it. I want to know if it has a problem with some brands of phones. or some phones doesn't support OTA setting. Please tell me which brands or which models are supported.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4887
Registered: 10-2002
Posted on Tuesday, September 13, 2005 - 07:39 pm:   

Hi,

There are so many different models of mobile phones around the world that it is not possible to identify which phones support OTA and which do not.

Generally speaking, you need to refer to the specifications from the manufacturer to determine whether or not this is supported.

Based upon what I see on the web, the Samsung X600 should support OMA OTA.

Have you tried it with an without a PIN? Some devices require that you set a USERPIN.

Are you using the web form in NowSMS or custom settings?
ehsan alizadeh
New member
Username: Ehsan123

Post Number: 3
Registered: 09-2005
Posted on Saturday, September 17, 2005 - 12:34 pm:   

I use web form in NowSMS and tried with and without a PIN but the X600 did not recieve anything.
I want to know if NowSMS has a problem with this model or with all models of samsung or this problem maybe happen in other barnds too?
Imate has the same problem and hadn't recieve the setting.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4953
Registered: 10-2002
Posted on Monday, September 19, 2005 - 07:50 pm:   

There are issues with Microsoft Smartphone devices (of which iMate is a major manufacturer). Basically, the Microsoft Smartphone platform supposedly supports OMA OTA ... however, this support is disabled by default by Microsoft for security reasons. (I've tried various tests attempting to enable that support, but I'm not enough of an expert on the Pocket PC or Smartphone platform to succeed. You can search this forum using a keyword of Smartphone to read about some of these attempts.)

But I don't have any information on the Samsung X600. And Samsung (to the best of my knowledge), does not publish details for which of their phones support which OTA standards, with what restrictions.

I do know that some Samsung models, which use the Teleca browser, support the Nokia/SonyEricsson OTA Provisioning standard (which we refer to as "WAP OTA" in our menus).

But the X600 uses the Openwave 6.1 browser, which should suppport OMA Provisioning Content ("OMA OTA" in our menus), although this ability may be blocked if the phone is locked.

Can you send WAP Push messages to the phone ok?

How about sending a WAP Push message with extra long text in the "text:" field (over 140 characters). Is that received ok?

I want to make sure that there is no problem in your setup with delivering binary messages and multipart binary messages.

-bn

ehsan alizadeh
New member
Username: Ehsan123

Post Number: 4
Registered: 09-2005
Posted on Saturday, September 24, 2005 - 12:07 pm:   

I had sent WAP push messages to X600 but it didn't recieve it either.
I sent a long text and it recieved the text in 2 messages so it can deliver multipart binary messages.
Do you support all brands? if yes then is there any standard that you use it to producing these OTAs? Please tell the standards number?
If you understand X600 problem please tell it too.
Thanks a lot
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5050
Registered: 10-2002
Posted on Wednesday, October 05, 2005 - 03:27 pm:   

The fact that the phone is not receiving WAP Push message is a cause for concern.

OMA Provisioning Content is sent via WAP Push.

Check the phone's settings to see if there are settings for WAP Push which have been disabled. According to the manual, there is an option in the browser menu under Push Messages/Setting, which controls this.

It is also possible that this particular phone has been locked.

So my primary concern here would not be that OTA doesn't work ... but that a simple WAP Push doesn't work, because OMA OTA (which the phone supposedly supports) delivers via WAP Push.

Here are a few things to try ... concentrating on simple WAP Push messages first.

This thread describes two SMSGW.INI settings that can add additional fields to the WAP Push message. Try the settings described in the following thread:

http://support.nowsms.com/discus/messages/485/5910.html

Also, try this setting under [SMSGW] in SMSGW.INI, available in v5.51a or later:

WAPPushIncludeDate=Yes

Some Samsung phones display a date/time associated with received WAP Push messages, where the date/time displayed is inaccurate. This setting forces NowSMS to insert a date/time stamp into WAP Push messages. Note that this setting was implemented to resolve a specific incident report, and has not been tested against a wide range of other phones.

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