Windows Vista Tips

Windows Vista Tips > Newsgroups > ActiveSync > Direct Push on Treo 700w (WM5.0)

Reply
Thread Tools Display Modes

Direct Push on Treo 700w (WM5.0)

 
 
edsiri
Guest
Posts: n/a

 
      01-06-2006
Greetings, (and apologies for a long post)

I am having problems getting "direct push" to work with my new Treo 700w
from Verizon. Our Exchange server (SP2) is behind ISA, but before we get
into how the network is setup, I'd like to verify my understanding of Windows
Mobile 5.0 and how it integrates with "direct push" and AUTD.

First, AUTD...

AUTD uses SMS messaging OR SMTP to notify the device (Windows Mobile 5.0)
that it needs to sync with Exchange. Most providers provide some sort of
SMTP email address (i.e. ). So when Exchange sends
the notification, the provider converts it to SMS and sends it to the device.
The divice, receives the SMS, and syncs with Exchange.

The Treo 700w will ask for the device email address when setting the sync
schedule to sync "as items arive".

Under Exchange System Manager, AUTD is enabled by going to Exchange System
Manager -> Global Settings -> Mobile Services and checking "Enable up-to-date
notifications via SMTP and Text Messaging" and (in my Treo's case) "Enable
notifications to user specified SMTP addresses".

I've been able to confirm that this works and notifcations are within a few
seconds. Via network monitor, I can see the SMTP message being sent to my
device email address. The only problem is that I will be get charged 10
cents for each message Exchange sends when something in my inbox changes.


Next, "Direct Push"

My understanding of Direct Push is that it has absolutely nothing to do with
SMS or SMTP. Once the device syncs with Exchange, it maintains an HTTP(s)
session with IIS (on the Exchange server) via a heartbeat which can occur up
to every 15 minutes. This "request" allows the device to listen to a
"response". In between heartbeats, if something changes on my Inbox in
Exchange, it sends (pushes) an HTTP "response" to the device - thus telling
it to sync with Exchange.

Therefore, since it's stated all over the Internet that Windows Mobile 5.0
supports Direct Push.. there shouldn't be a need to have to turn the AUTD
features on in Exchange (assuming all devices run WM5.0). I've done this by
going to Exchange System Manager -> Global Settings -> Mobile Services and
ONLY enabling "Enable user initiated syncronization" and "Enable Direct Push
over HTTP(s)". The other two options for AUTD have been disabled.

However, doing so - it seems that Direct Push is not working. Using Network
Monitor (on both ISA and Exchange servers) and reading through ISA logs, no
heartbeats are being sent between the device and Exchange. I've also
verified that my device has access to the internet with valid IP. The two
simply aren't talking.

I've also increased the HTTP(s) connection timeout on both ISA and Exchange
servers to 15 minutes.

So that we can dig further into the problem, could somebody please first
verify my understanding of AUTD and Direct Push, and that the two
technologies are completely separate from one another?

Thanks in advance,

Ed
 
Reply With Quote
 
 
 
 
Chris De Herrera
Guest
Posts: n/a

 
      01-08-2006
Hi,
First, your Treo 700w must have AKU2 installed on it to use direct push with
Windows Mobile 5.0. It does not exist in prior versions.

Also, beyond Exchange Server 2003 SP2, you may want to install Microsoft
Exchange Server ActiveSync Web Administration Tool -
http://www.microsoft.com/downloads/d...DisplayLang=en
which allows you to remote wipe Windows Mobile 5.0 devices.

Finally Microsoft has a series of web pages on the push technology at
http://www.microsoft.com/technet/pro...2003/autd.mspx,
http://www.microsoft.com/windowsmobi...5/default.mspx and
http://www.microsoft.com/technet/pro...2mobility.mspx


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/acti...shoot-as4x.htm

"edsiri" <> wrote in message
news:31EF356D-62A6-4872-8E06-...
> Greetings, (and apologies for a long post)
>
> I am having problems getting "direct push" to work with my new Treo 700w
> from Verizon. Our Exchange server (SP2) is behind ISA, but before we get
> into how the network is setup, I'd like to verify my understanding of
> Windows
> Mobile 5.0 and how it integrates with "direct push" and AUTD.
>
> First, AUTD...
>
> AUTD uses SMS messaging OR SMTP to notify the device (Windows Mobile 5.0)
> that it needs to sync with Exchange. Most providers provide some sort of
> SMTP email address (i.e. ). So when Exchange sends
> the notification, the provider converts it to SMS and sends it to the
> device.
> The divice, receives the SMS, and syncs with Exchange.
>
> The Treo 700w will ask for the device email address when setting the sync
> schedule to sync "as items arive".
>
> Under Exchange System Manager, AUTD is enabled by going to Exchange System
> Manager -> Global Settings -> Mobile Services and checking "Enable
> up-to-date
> notifications via SMTP and Text Messaging" and (in my Treo's case) "Enable
> notifications to user specified SMTP addresses".
>
> I've been able to confirm that this works and notifcations are within a
> few
> seconds. Via network monitor, I can see the SMTP message being sent to my
> device email address. The only problem is that I will be get charged 10
> cents for each message Exchange sends when something in my inbox changes.
>
>
> Next, "Direct Push"
>
> My understanding of Direct Push is that it has absolutely nothing to do
> with
> SMS or SMTP. Once the device syncs with Exchange, it maintains an HTTP(s)
> session with IIS (on the Exchange server) via a heartbeat which can occur
> up
> to every 15 minutes. This "request" allows the device to listen to a
> "response". In between heartbeats, if something changes on my Inbox in
> Exchange, it sends (pushes) an HTTP "response" to the device - thus
> telling
> it to sync with Exchange.
>
> Therefore, since it's stated all over the Internet that Windows Mobile 5.0
> supports Direct Push.. there shouldn't be a need to have to turn the AUTD
> features on in Exchange (assuming all devices run WM5.0). I've done this
> by
> going to Exchange System Manager -> Global Settings -> Mobile Services and
> ONLY enabling "Enable user initiated syncronization" and "Enable Direct
> Push
> over HTTP(s)". The other two options for AUTD have been disabled.
>
> However, doing so - it seems that Direct Push is not working. Using
> Network
> Monitor (on both ISA and Exchange servers) and reading through ISA logs,
> no
> heartbeats are being sent between the device and Exchange. I've also
> verified that my device has access to the internet with valid IP. The two
> simply aren't talking.
>
> I've also increased the HTTP(s) connection timeout on both ISA and
> Exchange
> servers to 15 minutes.
>
> So that we can dig further into the problem, could somebody please first
> verify my understanding of AUTD and Direct Push, and that the two
> technologies are completely separate from one another?
>
> Thanks in advance,
>
> Ed



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Palm Treo 700W slickaapd Windows Vista Hardware 1 08-17-2007 03:25 PM
Treo 700w won't show up in WMDC Althas Windows Vista Hardware 3 03-07-2007 02:26 AM
Palm Treo 700w & Vista Ultimate Mobile Device Center scsa20 Windows Vista Hardware 6 02-02-2007 05:01 PM
Treo 700w DM Nelson Windows Vista Hardware 0 10-01-2006 12:55 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59