O2 cannot receive WAP PUSH

O2 cannot receive WAP PUSH SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » O2 cannot receive WAP PUSH « Previous || Next »
Author Message
Anonymous
 
Posted on Thursday, March 31, 2005 - 06:00 am:   

seems like the new O2 XDA IIs, Mini and Xphone II all cannot receive wap push from nowsms, any way to solve it?

Thanks.
Anonymous
 
Posted on Wednesday, April 06, 2005 - 10:17 pm:   

what are u trying to push ?
Anonymous
 
Posted on Thursday, April 07, 2005 - 03:27 pm:   

wap push for user to download content.
Anonymous
 
Posted on Friday, April 08, 2005 - 07:39 pm:   

I'm pretty certain that SI and SL are not available on PPC .. ( not on my PPC 2003 anyway ).
Why ? MS think they are a security issue so have not enabled them since PPC has no security model. Only available on Smartphone, which has, where it works ! I have not tried or looked into this, and u will need dev environment and a smartphone to get details from registry ect, but it might be possible to enable it. Look in PushRouter regsitration section and where wap encoding types are supported in the registry. MS tends to use the same app to do many things and simply pass in command line params to invoke different behaviour..
Anonymous
 
Posted on Tuesday, April 12, 2005 - 05:29 pm:   

PPC phone edition might work? Bryce?
Anonymous
 
Posted on Wednesday, April 13, 2005 - 09:01 pm:   

No sorry .. have a look in registry under PushRouter registrations .. vnd.wap.sic and slc are defined but are not linked to an application .. i.e. there is nothing to handle them .. u could always handle yourself see the SDK which has example of how to register a handler with the pushRouter ..(have done it and it works fine) u need however to run at highest priveledge level..
ashot shahbazian
New member
Username: Animatele

Post Number: 32
Registered: 06-2004
Posted on Thursday, April 14, 2005 - 06:20 am:   

If the device is sold by O2 (not SIM-free) there may be a lock in the phone or PDA, which would prevent it from receiving WAP push messages from third parties.

If you can receive Wap push and download content if subscribed off O2's own Web site but cannot do it from elsewhere that is most likely the case. Depending on the phone/PDA model, you may or may not be able to disable the lock through the menu; usually you would have to dig very well to find it. If not, flashing the firmware ("Unlocking" the device) may be the only option.
Anonymous
 
Posted on Tuesday, April 19, 2005 - 11:35 am:   

i test with my device o2s (sim-free), not able to receive it. Might be bug in nowsms.
Anonymous
 
Posted on Wednesday, April 20, 2005 - 10:52 am:   

Get the smartphone and PPCPE SDK and have a read things will become clearer then. SI/SL not on PPCPE but is on Smartphone. wbxml-connectivity is on both ! U just have to enable in the registry since some service providers disable WAP messaging on the device.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4374
Registered: 10-2002
Posted on Monday, April 25, 2005 - 07:12 pm:   

It is a policy issue.

By default, a Windows Smartphone device will not accept service indication push messages unless they are from a trusted push proxy gateway.

What is a trusted push proxy gateway? Well, if you have a device that was provisioned for a particular mobile operator, then they might have one or more push proxies for that operator pre-configured in the trusted list.

Or if you bought an unlocked device, it may have an empty trusted proxy list, which means that you're not going to receive any service indication WAP push messages.

I've been experimenting with a device this evening, and have managed to unlock it so that it will receive service indication messages. Service indication messages will then appear in the Inbox for text messages, where you'll see the message text and the URL link. Also, they'll pop up on screen when we received.

I managed to unlock mine using some tools from the Smartphone SDK (change the Service Indication policy) ... so I need to spend a little more time on this to figure out how to do it without the SDK, so that mere mortals can make a simple tweak.

To be continued ...
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4378
Registered: 10-2002
Posted on Tuesday, April 26, 2005 - 02:00 pm:   

Follow-up ...

I used RAPICONFIG from the Smartphone SDK to send the following XML to my phone while connected in the cradle:

<wap-provisioningdoc>
<characteristic type="SecurityPolicy">
<parm name="4109" value="4095"/>
</characteristic>
</wap-provisioningdoc>

This changes the security policy for receiving "service indication" WAP push messages. And after I did this, I was able to send WAP Push messages to the device as expected.

If you want to check the current value for this setting before sending it, use the following XML:

<wap-provisioningdoc>
<characteristic type="SecurityPolicy">
<parm-query name="4109"/>
</characteristic>
</wap-provisioningdoc>

And you'll get back an XML response that reports the current value.

The challenge is how to do this without the SDK. I'm not a Pocket PC/Smartphone expert, so I could use some help there.

I tried creating a CPF file containing the XML, and running that on the Smartphone, but that resulted in an error, presumably because running on the Smartphone itself, I didn't have security privileges to modify the setting.

The SDK says that you should be able to call DMProcessConfigXML to send configuration XML to a device that is in the cradle. And I've seen various links on the web that mention that RAPICONFIG.EXE from the SDK is merely a wrapper around DMProcessConfigXML.

However, I don't believe this to be true ... at least not with SmartPhone 2003.

I tried creating a simple application that calls DMProcessConfigXML. However, the SDK libraries resolve this function call to AYGSHELL.DLL ... and I don't have that DLL anywhere in my system. It doesn't seem to be included in the Smartphone 2003 SDK.

So I took a closer look at RAPICONFIG.EXE. And I don't see any evidence that RAPICONFIG calls this DMProcessConfigXML function. Instead, I see that RAPICONFIG calls the following functions in RAPI.DLL: CeRapiInit, CeRapiFreeBuffer, CeRapiUninit ... and a mysterious unnamed function at ordinal 25.

So I'm not sure what to make of this. Ideally, I'd like to see a program like RAPICONFIG that can send this type of configuration XML to a Smartphone without requiring that the SDK be installed.

Any thoughts?

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4485
Registered: 10-2002
Posted on Monday, May 09, 2005 - 05:11 pm:   

Just posting a cross-link to related discussions:

http://support.nowsms.com/discus/messages/1/7837.html
HM
Unregistered guest
Posted on Saturday, May 28, 2005 - 09:46 pm:   

Thanks guys. I don't know how to send XML to my phone (PPC phone edition) but there was enough information in this thread to figure out how to get WAP Pushes working.

Just ran a registry editor on the phone, went to HKLM\security\policies\policies and changed the key 100D to value 4095.

Works like a charm now.
NZ
Unregistered guest
Posted on Tuesday, June 14, 2005 - 02:14 pm:   

I used RAPICONFIG from the Smartphone SDK to send the following XML to my phone while connected in the cradle:

<wap-provisioningdoc>
<characteristic type="SecurityPolicy">
<parm name="4109" value="4095"/>
</characteristic>
</wap-provisioningdoc>


Is it necessary to do this operation to enable OMA client provisioning as well (for gprs/wap/mms) ?

Because I've tried to send OMA Settings and the device (an O2 Xda II) do not react at all...

I've also tried with the microsoft "mwid" parameter (like on this page http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mobilesdk5/html /wce51samaddingmodifyinglogicalphysicalproxydevicetechnique.asp ) but nothing either...

Did somebody already managed to send OMA Settings to a PPC 2003 Smartphone ?

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