NowSms OMA OTA codepage problem with Motorolas

NowSms OMA OTA codepage problem with Motorolas SearchSearch
NowSMS Support Forums ⬆
NowSMS Support - SMS Issues ⬆
Archive through October 19, 2005 ⬆
 ◄    ►
Author Message
CiaranB
Unregistered guest
Posted on Wednesday, August 24, 2005 - 06:14 pm:   
Hi Bryce,

Is it possible to tell the NowSms compiler not to use codepage 1 when compiling OMA OTA xml documents ? There are some Motorola handsets that do not support the change to codepage 1.

What I would like to do is get NowSms to encode

<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="NAME" value="xx/>
<parm name="TO-PROXY" value=xx"/>
<parm name="ADDR" value="xx" />
</characteristic>

as

C650034150504C49434154494F4E0001870503415050494400060377340001870706037878000187 0503544F2D50524F585900060378780001870503414444520006037878000101

instead of

C600015501873606037734000187390603787800018707060378780001873406037878000101

Is this possible?

Thanks!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4813
Registered: 10-2002
Posted on Monday, August 29, 2005 - 10:27 pm:   
Hi Ciaran,

That is sad.

We could easily add an INI file setting to disable any codepage switches, which would cause everything to stay in code page 0, with any settings outside of that code page being encoded as literals.

But it would be more difficult to do this "on the fly", as we would have to devise some way in the XML header to signal that only code page 0 is supported.

Thoughts?

-bn
Search Search Search Last 30 Days Login / Register Logout

NowSMS Technical Bulletins
Read more