OTA provision an Alcatel OT557 handset

OTA provision an Alcatel OT557 handset SearchSearch
Author Message
Stephen McMullan
New member
Username: Smcmullan

Post Number: 1
Registered: 09-2005
Posted on Friday, September 23, 2005 - 03:44 pm:   

Hi,

I was wondering if anyone could help me. I've been attempting to OTA provision an Alcatel OT557 handset for WAP browsing and MMS services using the OMA 1.1 format (ref OMA-WAP-ProvCont-v1_1) provisioning document shown below.

<wap-provisioningdoc>
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="PLATEAU" />
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="NAME" value="PLAT-OTA-MMS" />
<parm name="PROXY-ID" value="MMS" />
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PH-MMS" />
<parm name="PXADDR" value="208.254.124.011" />
<parm name="PXADDRTYPE" value="IPV4" />
<parm name="TO-NAPID" value="NAP-MMS" />
<characteristic type="PORT">
<parm name="PORTNBR" value="9201" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="NAME" value="PLAT-OTA-WAP" />
<parm name="PROXY-ID" value="WAP" />
<parm name="STARTPAGE" value="http://wap.yahoo.com" />
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PH-WAP" />
<parm name="PXADDR" value="208.254.124.011" />
<parm name="PXADDRTYPE" value="IPV4" />
<parm name="TO-NAPID" value="NAP-WAP" />
<characteristic type="PORT">
<parm name="PORTNBR" value="9201" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAME" value="PLAT-OTA-MMS" />
<parm name="NAPID" value="NAP-MMS" />
<parm name="BEARER" value="GSM-GPRS" />
<parm name="NAP-ADDRESS" value="plateaumms" />
<parm name="NAP-ADDRTYPE" value="APN" />
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP" />
<parm name="AUTHNAME" value="mms@plateaugsm.com" />
<parm name="AUTHSECRET" value="plateau" />
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAME" value="PLAT-OTA-WAP" />
<parm name="NAPID" value="NAP-WAP" />
<parm name="BEARER" value="GSM-GPRS" />
<parm name="NAP-ADDRESS" value="plateaumms" />
<parm name="NAP-ADDRTYPE" value="APN" />
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP" />
<parm name="AUTHNAME" value="mms@plateaugsm.com" />
<parm name="AUTHSECRET" value="plateau" />
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w2" />
<parm name="TO-PROXY" value="WAP" />
<parm name="NAME" value="Browser" />
<characteristic type="RESOURCE">
<parm name="URI" value="http://wap.yahoo.com" />
<parm name="STARTPAGE" />
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w4" />
<parm name="TO-PROXY" value="MMS" />
<parm name="ADDR" value="http://208.254.124.011:8514" />
</characteristic>
</wap-provisioningdoc>

The WAP browser settings and MMS profile settings are stored with the exception of the MMS Service Centre which is not populated. I'm assuming that the Service Centre setting should be populated from the ADDR parameter of the Application characteristic.

However I notice from the Alcatel OTA OMA 1.1 supported parameters document (from their OneTouch developers site http://www.my-onetouch.com/onetouch/ahead/wap/) that the ADDR parameter is "not stored".

Is that what is responsible for the fact that the Service Centre configuration item of the WAP Connection Profile for MMS is not set after the handset is provisioned?

Is there a work around solution for this? Has anyone managed to sucessfully OTA provision this handset?

Many thanks for your assistance.

Regards,

Stephen McMullan
ANAM Mobile Ltd.
http://www.anam.com