1、 Printed on 22 October, 2009 IceWarp Unified Communications SyncML Push Guide Version 10 i Contents SyncML Push 1 What is SyncML Push? 1 What is Push email? . 2 How does SyncML Push work? . 3 SMS Push . 3 Server TCP/IP Push . 3 Client TCP/IP Push 3 Scheduled Polling . 4 IceWarp Server capabilities 5
2、 Client device support . 5 Feature overview . 6 Architecture overview . 7 Prerequisites 9 Server . 9 Clients 9 SMS Service Configuration . 11 Server configuration . 12 Quick guide 12 Setup SyncML 14 Settings and User Accounts . 15 Advanced options 20 Account configuration file . 20 Disabled devices
3、list 21 ii Contents Settings file 21 Client configuration 23 Enabling Push on the device 23 Enabling Push for multiple devices per one account . 24 Temporarily disabling Push from the device 24 Re-activation of Push on the device 25 Resolving a number mismatch with multiple devices 25 Troubleshootin
4、g . 26 1 In This Chapter What is SyncML Push? . 1 What is Push email? . 2 How does SyncML Push work? . 3 IceWarp Server capabilities 5 Prerequisites 9 SMS Service Configuration . 11 Server configuration 12 Client configuration . 23 Troubleshooting . 26 What is SyncML Push? SyncML Push technology, ba
5、sed on drafts created by the Open Mobile Alliance, extends the existing SyncML protocol specification by offering a method of server-initiated synchronization, i.e. the server alerts the device that new data is available so that the device can immediately synchronize. An alert, known as a SAN (Serve
6、r Alerted Notification), is sent to the device containing information about which server and database has changed, and which type of synchronization should be initiated by the client. The SAN can travel by various communication channels, dependent on the capabilities of both the server and the clien
7、t device. C HAPTER 1 SyncML Push 2 What is Push email? Push email is a completely distinct technology (where it designates the opposite of polling the server for new messages) based on other protocol stacks, such as IMAP. It is used to deliver email (and only email) in real time to the client device
8、, which must have a constant connection to the server. Push email is supported in IceWarp Server since version 8.5, using the IDLE command of the IMAP protocol. The client device should have an email client that supports IMAP and the IDLE command. This is available by default on most Windows Mobile
9、and Symbian devices, and on a number of recent feature phones and consumer mobile phones. Many devices can also download compatible email clients. The client should have the email account set up as an IMAP account and a polling interval should be set so that the connection to the server remains open
10、, and is automatically re-opened if it is lost for some reason. Push email can be freely combined with SyncML Push, but remember: they have nothing in common and have to be configured separately. Inbox synchronization should be set to use Push email or SyncML Push. C HAPTER 2 3 How does SyncML Push
11、work? There are multiple technologies and methods used to push the notification (SAN) to the client device, each with pros and cons. In This Chapter SMS Push 3 Server TCP/IP Push . 3 Client TCP/IP Push 3 Scheduled Polling . 4 SMS Push Sometimes referred to as WAP-PUSH, SMS Push is fairly universal,
12、using SMS to deliver the notification to the device, making it available on all networks and most client devices. There is an added cost to send the SMS(s) required to trigger the synchronization(s), plus any cost for data transferred over HSCSD, GPRS, EDGE, 3G or Wifi to complete the synchronizatio
13、n but there are facilities available which can help eliminate any overhead and minimize the amount of SMS messages to be sent. SMS notification is also more resistant to network connectivity loss as most service providers will hold an SMS for re-delivery if it cant be delivered immediately. Server T
14、CP/IP Push Server TCP/IP Push is designed for 3G networks where devices are available on a static, public, IP address which is directly reachable from the server. This method is therefore only suitable for carrier networks without NAT, and with simple routing. Client TCP/IP Push Client TCP/IP Push a
15、ttempts to work around the network restrictions of Server TCP/IP Push by having the client establish the connection to the server. The Client keeps the session alive and the Server sends notifications through the open connection when a change occurs. This relies on the ability to run an compatible S
16、yncML application on the client device that listens on a defined TCP port for incoming connections, limiting its use to devices equipped with an operating system. C HAPTER 3 4 SyncML Push Guide IceWarp Unified Communications Scheduled Polling Scheduled Polling is a variation of the Client TCP/IP Pus
17、h method, but clients only stay connected for a specified period of time. This methods gives the server better scalability since only a percentage of clients will be connected at any one time, allowing the server to effectively support a higher number of client devices. 5 IceWarp Server capabilities
18、 IceWarp Server 9.2 and higher SyncML Push technology primer implements: SMS Push Client TCP/IP Push (ready for the future) IceWarp Servers SMS Service is used to deliver the server alert through the wireless network, utilizing either: a remote third-party offering (if available via HTTP). another i
19、nstance of IceWarp Server (via HTTP) an instance of IceWarp Server with any AT command compatible GSM modem. A single instance of IceWarp Server can have multiple SMS Services defined, and you can mix and match HTTP and GSM modems on the instance. These multiple gateways will be used to effectively
20、load-balance the delivery of SMSs. Multiple instances of IceWarp Server can all point to the same instance of IceWarp Server as their gateway for SMSs, allowing multi-national corporations with multiple server to utilize a single sending point for all SMSs and possibly benefit from a low-cost bulk S
21、MS plan. Future plans for IceWarp Server include the ability to intelligently route an SMS to an appropriate Gateway for the destination. This would allow you take advantage of some countrys free SMS sending plan. In This Chapter Client device support . 5 Feature overview . 6 Architecture overview 7
22、 Client device support Client devices need to support SMS over GSM to receive the notification, and have to be able to establish a connection to the Internet using HSCSD, GPRS, EDGE, 3G (UMTS, CDMA) or Wifi. IceWarp Server 9.2 technology primer initially only offered the full scope of features with
23、Windows Mobile devices equipped with the latest Funambol client. Version 9.3 adds support for Nokia phones (certified for handhelds running Symbian), Sony-Ericsson and Synthesis. Continuing development is to be expected in future versions, including TCP/IP Push, a dedicated SyncML client, semi-autom
24、atic sign-up, over-the-air provisioning and remote device wipe. C HAPTER 4 6 SyncML Push Guide IceWarp Unified Communications Feature overview IceWarp SyncML SMS Push ensures up-to-the-minute information on the client device at all times delivers the latest changes to the device in real-time (with a
25、t most a 30 second delay) as opposed to scheduled synchronizations fully automates the synchronization process - no user intervention supports all types of data types available on the device including, but not limited to, Contacts, Calendar, Tasks, Notes, Inbox and Briefcase enables multiple devices
26、 to reflect the same data from a single account via automatically propagated synchronization intelligently handles events received from the server API in order to minimize the number of notifications sent to a device when multiple resources are to be synchronized is resource-aware thanks to multi-th
27、readed processing and multiple message queues gives the server administrator complete control over accounts, devices and data types to be alerted comes complete with an SMS service for small office, with the option of multiple GSM modems for corporate and support for carrier-class SMS gateways acces
28、sible through HTTP request for enterprise applications New features in 9.3 support for Symbian-based Nokia and SE handsets support for Synthesis client for Windows Mobile remote provisioning via Configuration SMS (using OMA/OTA standards) SSL encrypted connection support customizable synchronization
29、 URL with auto-correction performance optimizations Error! No text of specified style in document. 7 Architecture overview The UDP Notification Engine notifies the SyncML Push engine of any data changes on the Server. These changes may be made by a user interface (IceWarp WebClient, Outlook, CalDAV
30、client) or upon receipt of a message to the users mailbox. The SyncML Push engine issues a sync alert to the relevant device by sending a specially formatted SMS. The device, upon receipt of the alert, automatically initiates a two-way synchronization with the server. All this is done with no user i
31、ntervention. 8 SyncML Push Guide IceWarp Unified Communications 9 Prerequisites In This Chapter Server 9 Clients 9 Server 1. A valid SyncML Server license - full or trial. 2. A working SMS Service: A subscription to an SMS service over HTTP from a carrier or a 3rd party (or your own remote SMS servi
32、ce). You will also need to know the exact URL format to pass the server variables to it: %number%, %data%, %udh%, %binary%, %pid%, %dcs%, for detailed explanation refer to SMS Service Guide. Make sure that the remote service is capable of passing all of these variables, especially %udh% (Universal D
33、ata Header). - or - Any AT command compatible GSM modem connected to the server via a physical or driver-based COM port, set so that it is able to communicate with the OS (e.g. via Hyperterminal), and equipped with an active SIM card. 3. A calling plan or service optimized for sending bulk SMS messa
34、ges, depending on the number of users enabled for SyncML Push, data types they will synchronize and their general usage patterns. Clients 1. Compatible client device, such as Windows Mobile device with Funambol client installed. The latest version of the client for Windows Mobile can be downloaded h
35、ere: http:/ 2. Set the device to process server requests without requiring confirmation by the user. E.g. on Nokia, navigate to Menu - Tools - Sync select IceWarp profile press Options - Edit Sync Profile - Connection Settings set Allow sync requests to Yes and Accept all sync requests to Yes. 3. A
36、data plan and working Internet connection are required for the synchronization with the server to complete successfully. NOTE - a test should be performed to check that the synchronization process is working correctly via client request (i.e. starting the synchronization manually from the device). C
37、 HAPTER 5 10 SyncML Push Guide IceWarp Unified Communications 11 SMS Service Configuration Configure at least one SMS service, either on local COM port or on remote URL supplied by the service provider. Refer to the SMS Service Guide for more details on the available options. User authentication is
38、not required as messages sent from the SyncML Push engine will automatically bypass the authentication policy settings of SMS Service. An example configuration of a locally connected Siemens modem is shown below. C HAPTER 6 12 Server configuration In This Chapter Quick guide 12 Setup SyncML 14 Setti
39、ngs and User Accounts . 15 Advanced options 20 Quick guide Follow this guide if you are already using SyncML synchronization and want to quickly enable a device for SyncML Push. 1. Under SyncML Push, activate the engine by checking the Active box. 2. Add a user account that you wish to synchronize a
40、gainst, type its full email address or add it through the account selection dialog. 3. Make sure the account has SyncML Access Mode enabled, i.e. either: SyncML General Access Mode is set to All accounts (of the domain) the account is SyncML enabled in account properties Options - Access Mode. 4. Ad
41、d at least one device for the account. 5. Fill in the device properties accordingly, refer to the screenshot for an example and to the table further below for description of available options. 6. Tick the data types you wish to be synchronized (pushed, see note below). The dialog automatically offer
42、s folders supported by selected device. Predefined folder names will work out of the box, but can be renamed with the Edit dialog, where you can also change the synchronization type. Folder Type hints help you to identify resource types that have been previously renamed or customized. C HAPTER 7 Err
43、or! No text of specified style in document. 13 NOTE- that resource names are case-sensitive for Push and have to match on the device and in this dialog. The device matches the folder name exactly as included in the notification to its locally entered database name. To quickly enable a device for Syn
44、cML Push that is not yet configured for SyncML, you can use the Over-The-Air (OTA) SMS configuration: 1. Follow the same steps as above. 2. When you select the Client, the Send Config SMS button will become available if the device supports OTA configuration (Nokia, Sony-Ericsson, Synthesis). Otherwi
45、se the button will be greyed out. 3. Click Send Configuration SMS button. The button will become greyed out until you leave this dialog, to prevent the settings being sent multiple times. 4. On the client device: open the received SMS. confirm that its from a trusted server save the settings. 5. Sti
46、ll on the client device: navigate to Sync settings (e.g. on Nokia, go to menu - Tools - Sync - IceWarp - Edit Sync Profile - Connection Settings) and provide the password to the users account. This is a security measure preventing remote exploit of the server data. 14 SyncML Push Guide IceWarp Unifi
47、ed Communications 6. Finally, on a Nokia Client Device: 7. set the option Allow sync requests to Yes 8. set the option Accept all sync requests to Yes 9. this allows synchronization to occur without user confirmation each time. NOTE - that although you can use this dialog also for over-the-air confi
48、guration of Sony-Ericsson mobile phones SyncML Push is currently NOT supported on Sony-Ericsson devices, and you should press “Cancel“ before leaving this dialog. The Active checkbox will be disabled automatically. To enable a new device for SyncML Push which doesnt support OTA configuration, please
49、 refer to the example in the Client configuration (on page 23) section and the step-by-step guides in the SyncML Guide, these will help you to configure the device manually. Then follow the steps outlined at the beginning of this Quick guide. Setup SyncML First you should activate the SyncML engine and grant access to all the accounts/domains that require it. Select the SyncML tab in the IceWarp Server Administration GUI. Selecting the SyncML tab shows the following screen: Field Description Active
