Using the Transportable

How to make full use of your phone in transportable mode....55

Accessories

Details the accessories available for use with your phone....61

What To Do If.

Helps you to solve any problems that may occur....63
A comprehensive index......67
The Manufacturer reserves the right to make changes in technical and product specifications without prior notice.
IMPORTANT READ THIS INFORMATION BEFORE USING YOUR TRANSPORTABLE CELLULAR TELEPHONE
The cellular telephone is one of the most exciting and innovative electronic products ever developed. With it you can stay in contact with your office, your home, emergency services, and others. Over 120 scientists, engineers, and physicians from universities, government health agencies, and industry, after reviewing the available body of research, developed this updated standard. In March, 1993 the Federal Communications Commission (FCC) of N. America proposed the adoption of this updated standard. To operate within this updated ANSI standard, use your phone as described under "Efficient Phone Operation".
Efficient Phone Operation
Do not operate your transportable cellular telephone when holding the antenna, or when any person is within 10 centimetres (4 inches) of the antenna. Of course, if you want to limit RF exposure even further than the updated ANSI standard, you may chose to control the duration of your calls or maintain a distance from the antenna of more than 10 centimetres (4 inches). For best call quality, keep the antenna free from obstructions and point it straight up.

General

For the safe and efficient operation of your phone, observe these guidelines. Your transportable cellular telephone is a radio transmitter and receiver. When the phone is ON, it sends out and receives radio frequency (RF) energy. The phone operates in the GSM frequency range of 890MHz to 960MHz (or DCS 1800 frequency range of 1710MHz and 1880MHz) and employs commonly used Time Division Multiple Access (TDMA) digital modulation techniques. When you use your phone, the cellular system handling your call controls the power level at which your phone transmits. The pulsed power level can range from 0.02 of a watt to 8 watts.

To avoid interfering with blasting operations, turn your unit OFF when in a "blasting area" or in areas posted: "turn off two-way radio". Construction crews often use remote control RF devices to set off explosives.
Medical Electronic Equipment
Consult the manufacturer of any personal medical devices (such as pacemakers, hearing aids, etc.) to determine if they are adequately shielded from external RF energy. Turn your phone OFF in health care facilities when any regulations posted in the area instruct you to do so. Hospitals or health care facilities may be using RF monitoring equipment.
Potentially Explosive Atmospheres
Turn your phone OFF when in any area with a potentially explosive atmosphere. It is rare, but your phone or its accessories could generate sparks. Sparks in such areas could cause an explosion or fire resulting in bodily injury or even death. Areas with a potentially explosive atmosphere are often, but not always, clearly marked. They include fuelling areas such as petrol stations; below decks on boats; fuel or chemical transfer or storage facilities; and areas where the air contains chemicals or particles, such as grain, dust, or metal powders. Do not transport or store flammable gas, liquid, or explosives, in the compartment of your vehicle which contains your phone or accessories. Before using your phone in a vehicle powered by liquefied petroleum gas (such as propane or butane) ensure that the vehicle complies with the relevant fire and safety regulations of the country in which the vehicle is to be used.

Safety Standards

This Cellular Telephone complies with all applicable RF safety standards.
This cellular telephone meets the standards and recommendations for the protection of public exposure to RF electromagnetic energy established by governmental bodies and other qualified organisations, such as the following:

Battery Safety

To prevent injury or burns, do not allow metal objects to contact or short circuit the battery terminals. Make sure that the battery terminals do not touch greasy objects. Do not immerse the battery in water, or dispose of in a fire. Ensure that the battery is disposed of using the proper facilities. If you need to replace the battery, make sure that you use only the approved battery type. The use of other types of batteries might affect your phone and in such cases the manufacturer assumes no liability.
Verband Deutscher Elektroingenieure (VDE) DIN-0848 Directives of the European Community, Directorate General V in Matters of Radio Frequency Electromagnetic Energy National Radiological Protection Board of the United Kingdom. GS-11, 1988. American National Standards Institute (ANSI)/IEEE. C95. 1-1992 National Council on Radiation Protection and Measurements (NCRP). Report 86 Department of Health and Welfare Canada, Safety Code 6.
European Union Directives Conformance Statement

You do not need to press O to call the number.
ODialling Phone Book Numbers L G#O Alternatively you can: 1 Press QG. For example Q23 will retrieve the phone number stored in location 23 of your Phone Book. If you dont know the exact location, you can enter a random location and then use the < and > keys to scroll to the number you want. 2 Press O to call the number. Calling an Embedded Number in a Message Details on how to call a number embedded in a message are given in the Messages Menu section.
1. The Phone Book entries that you are able to access will depend on the One-Touch Dial Setting option in the Phone Book menu.
Pause - A Working Example. If, for example, you have a tone-based voicemail system on 555-6911, with a mailbox number 1066 and password 2001. Then you may dial the following number: 555691110662001O. The first part of the number would be used to call the voicemail system. When the call is answered the first pause will produce a delay of three seconds before the tones for 1066 are sent to select the mailbox. There will be a second pause of three seconds before the tones for 2001 are sent as the password.

GSM Emergency Calls

The worldwide GSM network provides a standard number, 112, to dial in cases of emergency. Provided that your phone has found a network, you will be able to make an emergency call. The call can be made regardless of any security codes and, depending on the network, with or without a SIM card inserted. The emergency call will be directed to a central emergency operator. To dial the GSM emergency number, press 112O. While the emergency call is being made and connected, the display will show Emergency.

Receiving a Phone Call

To receive a phone call: Your phone must be switched on and unlocked. You must be in an area where there is GSM service. Your Call Diversion and Call Barring settings should not be set to divert or bar incoming calls. When your phone receives a call, it will ring and the display will show the Call message (if you have Caller Line Identification, the callers number will be displayed instead). To answer the call, pick up the handset or press O. If you do not wish to answer a call you can either: Press and release the C key. If you have enabled the 'Detailed Diverting - If Busy' option in the Options Menu, the caller will be diverted to the forwarding number, otherwise the caller will hear the busy tone. or Press and hold the C key. This will reject the incoming call. No call divert option will be offered. If your phone rings and you do not answer it, the message Unanswered Call will be displayed to show you that a call attempt was received.

Postscripting

This allows you to make use of area codes and other prefixes previously stored in your Phone Book when making a call. To use postscripting, select the Phone Book entry containing the prefix and then simply enter the rest of the number and press O to make the call. You can also use postscripting if you want to call a number similar to one you have stored in your Phone Book. Retrieve the number from the Phone Book, delete the relevant digits and then enter the new number.
Postscripting a number does not overwrite the entry in the Phone Book.
1. Availability of the Fixed Dialling feature depends on the type of SIM card you have.
How to Enter Alphabetic Characters
The 0, 1,..,8 and 9 keys are used to enter alphabetic characters, for example when storing names in the Phone Book or when creating messages. For example, if you press the 5 key, the first displayed character will be J. If this is not the required character, then you can press the same key again to show K. Another press will display L, another..will display 5. Your phone will continue to scroll through the characters available on the selected key with each new key press. A long press of any of the keys will switch all the characters to lower case, a second long press will switch back to upper case. To enter the next character press the appropriate key. If, however, the next character is on the same key as the previous character you will first need to press the # key. Pressing the # key a second time will produce a space. If a mistake has been made, you can go back to the incorrect character by pressing *. Characters can be removed from the display by pressing the C key. The character before the cursor () is the character which will be deleted. Press the O key to store the information.
Available Characters Press the appropriate keys to get the following characters: Space. ? ! , & : " ( ) ' ` @ % 1 Space. ? ! , & : " ( ) ' ` @ % 1 A B C [ 2 a b c { 2 D E F 3 d e f 3 G H I 4 g h i 4 J K L 5 j k l 5 M N O ] \ 6 m n o } | 6 P Q R S 7 p q r s 7 T U V ^ 8 t u v ~ 8 W X Y Z 9 w x y z 9 + - x * / = > < # 0 + - x * / = > < # 0

The top line(s) for each key show the upper case characters, the lower line(s) show the lower case.

Personal Numbers

The Personal Numbers sub-menu is used for creating and managing your list of personal numbers. Find Entry By Name L Press I1. This option is used to select a telephone number from a list of alphabetically sorted Phone Book names. Once selected, this option will display the message Enter Name. You can enter the first three characters of a name. You do not need to enter all three characters, but a longer entry will result in a more accurate search. The Phone Book entries will be searched and the first matching entry will be displayed. If there isnt a name matching your entry, the nearest matching entry will be displayed. If you do not enter any name information, the first alphabetical entry will be displayed. If there are no names stored, No Names Stored will be displayed. To display adjacent Phone Book entries use the * and # keys. When the desired name is displayed press the O key to select it. The phone will now enter the 'Call Number', 'Modify Name Or Number' or 'Erase Name And Number' options sub-menu.
Find Entry By Location L Press QG. This option is used to select a telephone number from a list of numerically sorted Phone Book locations. Once selected, this option will display the message Enter Location. You can now enter a location number. If the entered location is not valid, a timed message Range 1-XXX will be displayed and the phone will return to the Enter Location menu item. The Phone Book entries will be searched and an entry will be displayed. If you enter a location number for which there is no entry, Location Empty will be displayed and the nearest non-empty location will be selected instead. If you did not enter a location, the first numerical entry will be displayed. If there are no numbers stored, No Numbers Stored will be displayed. To display adjacent Phone Book entries use the * and # keys. When the desired name is displayed press the O key to select it. The phone will now enter the 'Call Number', 'Modify Name Or Number' or 'Erase Name And Number' options sub-menu.

You can use postscripting to modify a number once you have retrieved it from either of the Last Ten Calls lists.
Last Calls Made This option can be used to redial the phone number of any one of the last ten calls made. Last Calls Received This option can be used to redial the phone number of any one of the last ten calls received.
You will only see numbers in the Last Calls Received list if you have Caller Line Identification.
Erase All Numbers This option erases all the numbers stored in your Last Ten Calls Made and Last Ten Calls Received lists.

My Phone Number(s)

This option allows you to access your cellular phone, fax and data numbers so that you can retrieve or modify them when required. For example, if you have difficulty remembering your cellular phone number, store it with the name My Phone and then you will be able to retrieve the number as required. The My Phone Number(s) list is stored on your SIM card. When you select this item, the first location will be displayed. Use the < and > keys to scroll through the phone numbers stored. To enter or change a number, scroll to the location and press O. You will be prompted to enter a phone number and then a name. Press O to store the information.

Fixed Dialling

Availability of the Fixed Dialling menu depends on the type of SIM card.
This feature allows you to limit use (typically third-party use) of your phone to a predefined list of telephone numbers or, if you wish, to a list of country codes, area codes, or other prefixes of your choosing. When Fixed Dialling is switched on, the only numbers that can be dialled from your phone are those stored (or whose prefix is stored) in the Fixed Dial list. If you attempt to dial any other number (apart from an emergency number), the message Restricted will be displayed. You will not be able to make fax or data calls. To make a call when Fixed Dialling is switched on, either dial the number manually, or select it from the Fixed Dial list and press O. Up to 20 entries can be stored in the Fixed Dial list. The list is stored on your SIM card. ! This option may be affected by the Call Barring setting. View Fixed Dial List This option allows you to scroll through the numbers in the Fixed Dial list. When you find the number you want, press O to make the call.
Depending on your Cellular Service Provider, you may find that one or more of the entries in the My Phone Number(s) list will have been defined. You may not be able to change these predefined entries.
Phone Book Menu Setup Fixed Dialling This option allows you to switch Fixed Dialling on or off and to enter or change entries in the Fixed Dial list. You will be prompted to enter your PIN2 security code when you select this option. On Switches fixed dialling on. Off Switches fixed dialling off. Edit Entry Modifies or clears an entry in the Fixed Dial list. When you select this option, the first non-empty location in the list will be displayed. Scroll to the entry you want to change and press O. You will be prompted to edit the phone number and the name. To erase the entry, press C. Add Entry Adds a phone number and name to the Fixed Dial list. When you select this option you will be prompted to enter the phone number, name and a location number. If you do not specify a location number, it will be stored in the next available location.

Message Editor

The Message Editor is used to edit the currently selected message and then to either send the modified message or store it in your Outgoing Messages list. See How to Create and Edit SMS Messages for more information on using the Message Editor.

Outgoing Messages

This option is used to view and manage any outgoing messages. These messages will be stored on your SIM card. When you select this option, the total number of messages will be displayed followed by the first message in the list.

Cell Broadcast

This option is used to set the cell broadcast settings. The option has two settings On or Off. If you change the setting to On, you will be asked to enter the channel you wish to receive information from. Please contact your Cellular Service Provider for a list of available channels and the information they provide. While a broadcast message is scrolling across the display you can stop and start it by pressing *. Press # to restart the message from the beginning. If you want to remove the message from the display, press C followed by O.
You cannot send an outgoing message until the Message Service Centre number has been set. See Message Settings.
Press the O key, when viewing any message, to enter the Go to Next Message, Send Message, Edit Message and Delete Message sub-menu. See How to Read SMS Messages for more information on navigating through the messages. Go to Next Message This option will display the next outgoing message. Send Message If you select this option you will be prompted for a phone number, enter the number and then press O to send the message.
If you need to use the * and # keys for their normal functions while you are receiving a cell broadcast message, you must first remove the message.

Message Settings

Voicemail Number This option is used to enter a phone number which will be used by the Call Voicemail option. If there is already a Voicemail Number, this will be shown in the display. This can be used, modified or deleted as desired. Service Centre Before you can send any messages you must use this option to enter your Message Service Centre number. This number is obtained from your Cellular Service Provider. Expiry Period You can use this option to specify the maximum time, in hours, that your unforwarded messages are to remain with the Message Service Centre before being deleted. When you select this option, the current expiry period will be displayed (the default is 24 hours). The maximum value you can enter is 10584, though the real limit will depend on your Message Service Centre. Outgoing Message Type This option is network dependent and can be used to specify the format of your outgoing messages. You can select from the following message types: Text (default), Fax, X400, Paging, E-Mail, ERMES or Voice.

When On, Divert When Unavailable takes priority over detailed diversion settings.
Divert All Calls L I6 This option will enable you to unconditionally divert all incoming calls to a single number. The option has two settings, On or Off. If you change the setting to On, you will be asked to enter a diversion phone number using the digit keys.
When On, Divert All Calls takes priority over all other diversion settings.
Detailed Diverting These options will enable you to divert calls to different numbers, depending upon the call type and the current status of your phone. Each of the following detailed diverting options operate in the same way. Each option has two settings, On or Off.

Talk and Fax

This is a network feature that allows you to speak and then send or receive a fax during the course of a single call.
On Switches Talk and Fax mode on for the next and all subsequent calls. Off Switches Talk and Fax mode off for the next and all subsequent calls.
Your phone supports a data and fax transmission speed of up to 9600 bps.
Before making a Talk and Fax call, ensure that: Your phone is fax-ready (it has been switched off, connected to the fax, then switched back on). Connecting your phone to the fax in the middle of the call will not work. The Talk and Fax mode is set to On. A Talk and Fax call automatically switches to fax mode when you start sending the fax. While the fax is being transmitted, the message Fax in progress will be displayed. The call automatically ends when the fax transmission is complete. You cannot switch back to voice mode in the same call.
OCall Holding and Call Waiting
Your phone supports the GSM network options of Call Holding and Call Waiting. Using these options you can place a current phone call on hold and accept an incoming call or start a second call. The Call Waiting menu item has two settings On or Off. If you select Off, you will be not be notified of waiting calls. The person trying to contact you will either receive the busy tone, or be diverted by the Detailed Diverting - If Busy option. If Call Waiting is On, you will be notified of a waiting call by an audible alert and by the message Call Waiting - Answer?. You can press the O key to accept the waiting call, or use the M key to scroll to an alternative option and then press O.
While a Talk and Fax call is active, incoming call services like Call Waiting and Call Holding are suspended.
If you receive a Talk and Fax call when: Your phone is not fax-ready - you can only talk. Your phone is fax-ready but Talk and Fax mode is off - the call is automatically routed to your fax (you cannot talk).
If you have Caller Line Identification, the callers number is displayed instead of the Call Waiting message.
Call Related Features Menu Call Holding and Call Waiting Scenarios The display will automatically change according to the status of your current call (or calls) and will propose the option that you are most likely to want. Press O to accept this option or press M to scroll through the alternative options. By following this procedure you will find that even the triple combination of an active call, a held call, and a call waiting is easy to manage. The following points summarise the more common situations: To end the active call, press O. If you have a call on hold it is automatically connected. To put the active call on hold and make another call, press M and select the Hold Call option, then press M again and select the Make New Call option1. To put the active call on hold and reconnect a held call, press M and then select the Switch Calls option. To accept a waiting call, press O. The active call will be placed on hold. If you prefer to end the active call before accepting the waiting call, press M and select the End Active Call option, or End Held Call option as appropriate. To reject a waiting call, press M and select the Reject Call Waiting option (or simply press the C key).

If you have an active call, a call on hold and a call waiting, you cannot accept the waiting call until you end either the active call or the held call.
Call Holding and Call Waiting Messages During Call Holding and/or Call Waiting operations, your phone may display one or more of the following messages: Trying A request to hold the active call, or swap the active call with a held call, has been made. or A request to reconnect the held call has been made. Hold Failed The request to hold a call has been unsuccessful. Cannot Hold Second Call A call is already on hold, you cannot place two calls on hold at the same time. Reconnect Failed The held call could not be made active again. Busy Try Later Your phone is still working on a previous command. Wait a short time before repeating the command. Anonymous The person who is calling you has blocked their number from appearing on your phone.
1. A quicker method of making another call is to enter the number to be called directly. As soon as you press the first digit, the display will change to Call?. This will disappear three seconds after the last key press, but if you press O before then, your phone will place the current call on hold and attempt to call the number entered.
Unavailable The network is unable to provide the callers number.

OCall Barring

Call barring is a network feature which can be used to selectively bar outgoing and incoming calls. If you change the barring setting, you may be asked to enter your barring password. There will be a short delay while the phone notifies the network of the new setting. When the change has been made by the network, the phone will display a confirmation message. The initial password will be supplied to you by your Cellular Service Provider when you subscribe to this service.
Bar Incoming Calls After selecting this option, there will be a short delay while the phone asks the network for the current setting. When Roaming When selected, this option will bar incoming calls when you are roaming. You may wish to select this option, as some Cellular Service Providers charge an additional fee for receiving calls when you are roaming. All Calls When selected, this option will bar all incoming calls. Off When selected, this option will disable all call barring for incoming calls. Change Bar Password This option can be used to change the call barring password. After selecting this option, you will be asked to enter the current password. You will then be asked to enter, and then re-enter, your new, 4 digit, barring password. When the change has been made by the network, the phone will display a confirmation message.

Network Selection Menu

Network Selection
In order for the phone to make and receive phone calls, it must register with one of the available networks. Your phone automatically searches for the last network used. If, for any reason, this network is unavailable, your phone will attempt to register with a new network. When your phone needs to register with a new network, it will generate a sorted list of networks.The network list is sorted in the following order: The Home network. Networks from a preferred list. A random list of other networks found above a certain signal strength. All remaining networks in descending order of signal strength. Any forbidden networks, stored in the SIM card, will not be included in the sorted list. Register Now Once selected, your phone will try to register with the selected network. If the registration fails, your phone will try to register in the normal way. Make Preferred Once selected, you will be asked where the selected network is to be located in the preferred list.

Network Search

These options determine how often your phone tries to register with a network and how the attempt is made. Registration Preferences This option determines how the phone tries to register with a network. The option has two settings, Automatic Search or Manual Search. Automatic Search Mode In the automatic mode, the phone will try to register with the first network in the sorted list. If this is successful, your phone will display the network name and then enter the standby mode. If registration is unsuccessful with one network in the list, your phone will try the next listed network. If your phone fails to register with any of the listed networks, it will start at the beginning of the list after a preset period. The preset period is determined by the 'Frequency Of Search' option.

Available Networks

When selected, this option will scan to see which networks are operating in your current location. When the scan is complete, press the M key to scroll through the list. When you see a network you wish to register with or store in your preferred list, press the O key. You will now enter the 'Register Now' and 'Make Preferred' sub-menu.

OPreferred Networks

Add Network To List This option enables you to add networks to your preferred list. When selected, the 'Choose From Available' option will scan to see which networks are operating in your current location. When the scan is complete, press the M key to scroll through the list. When you see a network you wish to store in your preferred list,

Call Meters Menu

Call Metering
Your phone has an internal metering system which can be used to provide you with individual and total call times or costs.
Total For All Calls Displays the cost of all your chargeable calls since the charge meters were reset to zero using the Reset Call Charges option. Credit Remaining Displays the difference between your total call costs and the limit specified by the Set Total Charge Limit option. If there is no limit, No Charge Limit Set will be displayed.
Call cost information is only available if you receive the Advice of Charge service. If you do not receive this service, then only time meters are available.
The meter can be displayed during a phone call and audible tones can be generated to indicate the passage of call time. Your phone can handle values up to 21 digits long, although during calls it can only display the last 12 digits. If the value exceeds 21 digits, then Too Large is displayed. In addition, you can set a maximum charge limit so that your phone will monitor either the number of units used or the call cost, and then not allow the limit to be exceeded.

Show Call Timers

This feature allows you to display the duration of your calls and to reset your time meters to zero. If you receive the Advice of Charge service then all calls are timed. If you do not receive the Advice of Charge service then, depending on the model, either all calls or only outgoing calls are timed. Show Last Call Displays the duration of your last call. Total For All Calls Displays the duration of all your calls since the time meter was reset to zero using the Reset All Timers option. Reset All Timers Sets the resettable time meters to zero. The Lifetime Meter is not resettable.

Show Call Charges

This feature allows you to display the cost of your calls or the amount of credit remaining. The figures are in phone units or currency depending on the setting of the Set Charge Type option.
Show Call Charges is only available if you receive the Advice of Charge service.
Show Last Call Displays the cost of your last chargeable call.

OSet Audible Call Timers

Your phone provides two programmable audible call timers: The 'Single Alert Timer' will sound a beep just once during a call, after a preset time has elapsed. The 'Repetitive Timer' will sound regular beeps during a call, at preset intervals. In both cases, the timers will sound their beeps ten seconds before the end of the programmed time.

The Battery Level Meter on the display indicates the level of the battery. When the battery needs to be charged a warning tone is heard and the display shows Low Battery. When the battery strength drops below the lowest level for normal function, the telephone is switched off automatically.
If powered via the Cigarette Lighter Adapter, the display will not show the battery strength indicator, since the transportable is powered from the vehicle's battery.
The following accessories have been designed to work with your cellular phone. Additional accessories may be available and are packaged separately. Please refer to your local service provider or retail outlet for more information.
Quick Release Mounting Bracket (CCLN4128)
The Quick Release Mounting Bracket holds the transceiver when it is mounted in the vehicle.

Battery 2.2 Ah (SNN4139)

The Battery is for use with the carrying cassette in transportable mode. It provides up to 12 hours standby time and up to 90 minutes talk time. The battery will take approximately 9 hours to fully recharge.
Replacement Handset (SCN2706)
A Replacement Handset is available should the existing one become damaged or stolen.
Replacement Hang Up Cup With Card Reader (SLN3194)
For use in a vehicle a Hang Up Cup with integral Card Reader is available.
Rapid Charger (SPN4064 - Euro/SPN4063 - UK)
The Rapid Charger connects to a spare battery and allows you to charge it in approximately four hours.

Carry Strap (SLN7340)

A Carry Strap is available so that your hands are free when carrying the phone in the carrying cassette.
Power Supply (CCPN4013 - Euro/CCPN4000 UK)
When in transportable mode, the Power Supply connects directly to the battery in the carrying cassette and allows you to use the phone at the same time as charging the battery. Depending on usage, the battery will take around four hours to charge.
Cigarette Lighter Adaptor (CCLN4208)
The Cigarette Lighter Adaptor supplies power to the carrying cassette from the vehicle's cigarette lighter socket, saving the battery for portable use.

What to do if.

You cant switch your phone on You cant make calls Carkit: Have a qualified technician check the installation. Transportable: Check the battery. Is it charged, properly fitted and are the contacts clean and dry? Check the signal strength meter in the display. If the signal is weak, move to an open space. Check the Network Selection settings. Try Manual Selection, or try another network. See Network Search. Check your Operator coverage map. Is Restricted displayed? Check the Call Barring and Fixed Dialling. Has the call charge limit been reached? Use your PIN2 code to reset the limit or contact your Service Provider. See Set Total Charge Limit. Has a new SIM card been inserted? Check that no new restrictions have been imposed. You cant receive calls Check the signal strength meter in the display. If the signal is weak, move to an open space. Check the Call Diversion and Call Barring settings. Check the Ringer settings. If off, there is no audible alert. See Ringer On or Off. Your phone wont unlock Have you inserted a new SIM card? Enter the new PIN code. See Entering Your SIM Card PIN Code. Do you have a replacement phone? Enter the default phone unlock code - 1234. Have you forgotten the unlock code? Press M to change the unlock code (you will need your security code). Your PIN is blocked Your PIN2 is blocked Your SIM card wont work Enter the PIN unblocking code supplied with your SIM card (see Unblocking Your Phone). Enter the PIN2 unblocking code supplied with your SIM card (see Change SIM PIN2 Code). Is the card inserted the right way round? See SIM Card Insertion. Is the gold chip visibly damaged or scratched? Return the card to your Service Provider. Check the SIM and phone contacts. If they are dirty, clean them with an antistatic cloth.

Call barring..40 Call charge settings..49 Call diverting.. 36, 52 Call holding...38 Call metering..48 Call meters menu..48 Call related features menu.36 Call timers..49 Call voicemail.. 33, 52 Call waiting..38 Calling a number..14 Calling an embedded number.34 Cancel all diverting. 37, 52 Capacity Checking battery capacity.36 Checking Phone Book capacity.29 Carrying cassette Cigarette lighter adaptor..58 Insertion and removal of battery.56 Insertion of transceiver..56 Mains operation..58 Overnight charger..58 Removal from the vehicle.55 Spare battery charger..58 Cell broadcast..34 Messages..32 Change bar password.40 Change greeting..44 Change SIM PIN2 code..43 Change unlock code..42 Characters..26
Charge meters Resetting... 49 Check capacity (of the Phone Book)..29
Data calls Diverting... 37 Delete Last ten calls. 29 Message.. 33, 34 Phone book entries.28 Detailed diverting.. 37 Dialling phone book numbers.15 Display.. 10 Display characters.. 26 Displaying your own phone number..30 Divert All calls.. 37 Cancelling.. 37 Data calls... 37 Fax calls.. 37 Voice calls.. 37 When unavailable.. 37 DTX... 44
Bar incoming calls..40 Bar outgoing calls..40 Batteries Charging...57 Maintaining..57 Removal..56 Battery charge indicator..10 Battery meter.. 36, 53 Battery saving mode..44 Blocked message.. 13, 43 Buttons volume...9
Editing messages.. 33 Emergency calls.. 16 Ending a phone call.. 17 Entering characters.. 26 Erase name and number..28 Extended menus.. 21, 43
Fault finding.. 63 Fax calls Diverting... 37 Find entry by location..27, 52 Find entry by name.27, 52 Find new network. 47 Fixed dialling.. 30 Calling numbers.. 30 Setting.. 31
Making a phone call..14 Master clear...45 Master reset...44 Menu navigation.. 19, 23 Menus Accessory setup menu.51 Call meters menu..48 Call related features menu..36 Extended menu.21 Messages menu.32 Network selection menu.46 Personalised menus..21 Phone book menu..25 Phone setup menu..41 Quick Access menu.52 Short menu..21 Message editor..34 Message settings..35 Messages..32 Call holding/call waiting messages.39 Calling an embedded number..34 Cell broadcast messages.32 Creating and editing.33 Reading SMS messages..32 Sending SMS messages..34 Messages menu..32 Mute car radio..51 My phone number(s)..30
Names Entering..26 Network search.46 Network selection menu..46 Networks Automatic search..46 Finding new networks.47 Manual search..47 New security code..43

Handset... 55

One-touch dial setting.31 One-touch dialling.15 Outgoing messages..34
In use symbol.. 10 International country codes.. 65 International phone calls. 15
Pauses Inserting into phone numbers..15 Personal numbers..27 Personalised menu.21 Phone book Call number.28 Capacity..25 Deleting/erasing entries.28 Dialling phone book numbers..15 Modify name or number.28 Preventing access to.29 Storing numbers - see Add Entry.28 Phone book menu..25

Funambol DM Server

Developers Guide

Version 3.0 September 2006

Important Information

Copyright Funambol, Inc. 2006. All rights reserved. The information contained in this publication is subject to US and international copyright laws and treaties. Except as permitted by law, no part of this document may be reproduced or transmitted by any process or means without the prior written consent of Funambol, Inc. Funambol, Inc. has taken care in preparation of this publication, but makes no expressed or implied warranty of any kind. Funambol, Inc. does not guarantee that any information contained herein is and will remain accurate or that use of the information will ensure correct and faultless operation of the relevant software, service or equipment. Funambol, Inc., its agents and employees shall not be held liable for any loss or damage whatsoever resulting from reliance on the information contained herein. Funambol and Sync4j are trademarks and registered trademarks of Funambol, Inc. All other products mentioned herein may be trademarks of their respective companies. Published by Funambol, Inc., 643 Bair Island Road, Suite 305, Redwood City, CA 94063
DM SERVER DEVELOPERS GUIDE

Contents

Chapter 1
SyncML Device Management. 1
Introduction. 2 Purpose. 2 SyncML DM Protocol Message Sequence Overview. 3 SyncML Device Management Tree Overview. 6 The./DevInfo Node. 6 Management Object Manipulation. 8 Management Object Security. 8 SyncML Security and Initial Provisioning (Bootstrap). 9 Security. 9 Bootstrap Provisioning. 9 Bootstrap Methods. 10

Chapter 2

Developer Overview. 11
System Architecture. 12 Funambol DM Server Architecture. 12 Execution Flow. 14 Database Schema. 16 Device Management State. 18

Chapter 3

Server Configuration. 21
Overview. 22 Funambol.properties. 22 Server JavaBeans. 23 Lazy Initialization. 25 Configuring a Standard Component. 26 Configuring a Custom Component. 27 Getting a Configured Instance. 29 Tips and Tricks. 29 Logging. 30 Adding Logging for Custom Components. 31

Chapter 4

Customizing Message Processing. 33
Overview. 34 Preprocessing an Incoming Message. 37 Creating an Input Synclet. 37
Configuring an Input Synclet. 38 Postprocessing an Outgoing Message. 39 Creating an Output Synclet. 39 Configuring an Output Synclet. 40

Chapter 5

Implementing Management Operations. 41
Overview. 42 Creating a Processor Selector. 43 DeviceIdProcessorSelector. 43 Configuring the Management Engine. 48 Creating a Management Processor. 49 ManagementOperation. 50 ManagementOperationResult. 51 Using Scripting Management Processors. 53 Scripting Variables. 53

Chapter 6

External Applications. 59
External Application Interfaces. 60 The EJB Layer. 60 Implementing the Sender Component. 62 Sender Interface. 62 Sender Component Configuration. 64

Chapter 7

Bootstrapping Devices. 65
Bootstrap Overview. 66 WAP Provisioning Profile. 69 Plain Profile. 70

Appendix A

Appendix. 71
Resources. 72 Related Documentation. 72 Other Resources. 73 Bootstrap XML Message Examples. 74 WAP Profile. 74 Plain Profile. 75 WAP Headers for Bootstrap Message. 80 PLAIN Profile. 80 WAP Profile. 80 Notification Message Using WAP Push. 82 Notification Message Created by the DM Server. 82 Complete SMS (WDP + WSP + Notification Message). 82

SyncML Device Management

Topics
Introduction, page 2 SyncML DM Protocol Message Sequence Overview, page 3 SyncML Device Management Tree Overview, page 6 SyncML Security and Initial Provisioning (Bootstrap), page 9

Introduction

The Open Mobile Alliance Device Management (OMA DM) protocol, formerly known as the SyncML DM protocol, specifies the message sequence and behaviors that will allow device management commands to be executed against management objects on a SyncML DM compliant device. Management objects might include configuration parameters that enable Internet connectivity, e-mail connectivity, WAP connectivity, MMS settings, and basic network configuration options allowing voice access to an operator network. Other management objects may include the Java Runtime Environment on J2ME enabled devices or any other applicable software environment where extensions of features and functionality can be added via an Over The Air (OTA) upgrade to those environments. SyncML DM protocol is not limited to any particular set of management objects that can be modified via OTA, although the protocol does define a specific methodology and object management tree structure that serves as a profile on how a DM server accesses specific management objects on a particular device. The Funambol DM Server is a server side implementation of the OMA DM protocol and an extensible framework for the development of device management based applications. The Funambol DM Server architecture and implementation derives from the Funambol OMA DS platform.

Purpose

This document provides developers with basic concepts and guidance for extending the functionality of the Funambol DM Server. Using this document, a developer will acquire the following skills: An understanding of the OMA DM protocol An understanding of the Funambol DM Server architecture The ability to integrate the Funambol DM Server with external applications The ability to pre- and post-process incoming and outgoing OMA DM messages The ability to implement new management operations

SyncML DM Protocol Message Sequence Overview
The SyncML DM protocol is relatively simple from a messaging sequence standpoint. The message sequence consists of three parts: Alert phase used only for unsolicited management initiation from the server to the client. Set up phase (authentication and device information exchange) Management phase
Transaction 1: Alert Phase Server to Client Only Not required if the client is contacting server. SyncML DM supports the concept of unsolicited alerts via a notification initiation alert mechanism. This mechanism allows a management server to initiate a management session with a device, rather than solely relying on a client device to initiate a session. Some devices may be capable of listening on a particular port for alert messages; other devices may not be capable of this paradigm and need an alternate method to trigger a management session. SyncML will rely on two primary methods for delivery of unsolicited alerts: WAP Push This method will deliver the alert via a Push Initiator through a Push Proxy Gateway as defined by the WAP protocol. The SyncML server will act as a Push Initiator in this example, and will deliver the message via an SMS message. The message will have a unique application ID and the message will be routed to the device management user agent per the WAP Specification. OBEX The OBEX protocol can be used to deliver unsolicited alerts to a device via the PUT command as defined by the protocol.
Transaction 2: Set Up Phase Client to Server Always required. The set up phase consists of a request from the client and the response from the server. The initial client request of the set up phase will contain three primary pieces of information. The information contained in the DevInfo (Device Information) object, as follows: Ext - An optional, internal object, marking up the single branch of the DevInfo sub tree into which extensions can be added, permanently or dynamically. Bearer - An optional, internal object, marking up a branch of the DevInfo sub tree into which items related to the bearer (CDMA, etc.) are stored. Use of this sub tree can be mandated by other standards. DevId - A unique identifier for the device. SHOULD be globally unique. Man - The manufacturer identifier. Mod - A model identifier (manufacturer specified string).

Bootstrap Provisioning

SyncML DM defines two different use cases of bootstrapping a device and two methods for initial bootstrapping. Bootstrap Use Cases Factory Bootstrap: Devices are loaded with SyncML DM bootstrap information at the time of manufacture or initial distribution. Server Initiated Bootstrap: Server initiated bootstrap is intended for devices that do not have the necessary configuration parameters set to establish a SyncML DM session.

Bootstrap Methods

WAP Profile Provisioning Other aspects of server initiated bootstrap are very similar if not identical to WAP bootstrap provisioning. If the device supports WAP provisioning, extensions to the WAP profile that define how SyncML parameters are mapped into the SyncML DM management object are defined in the SyncML specifications, and can be used to configure the device for SyncML DM via WAP bootstrap provisioning. Plain Profile Bootstrap Provisioning Plain profile is currently defined for devices that do not support WAP bootstrap provisioning. This method utilizes the SyncML DM format for the bootstrap message, and uses the same bootstrap method for security as WAP bootstrap provisioning. WAP defines several methods for authenticating a bootstrap session and these methods are utilized by the SyncML DM protocol: NETWPIN a shared secret is known by the device and server i.e. an IMSI or ESN. No user intervention is required, and is the simplest yet least secure method of authenticating a bootstrap message. USERPIN where the user enters a PIN code delivered out of band i.e. through customer care who will initiates the bootstrap after confirming the identity of the user. A Plain Profile can use any method capable of sending unprompted requests to a device, i.e. OBEX, SMS, and WAP Push. USERNETWPIN a combination of the NETWPIN and USERPIN methods, requiring the use of a shared secret and a user PIN. USERPINMAC the PIN is delivered out of band to the user. This method calculates the PIN based on the actual bootstrap method using a hashing function. When the bootstrap message arrives, the user is prompted to enter the PIN. If the PIN matches the re-hash of the bootstrap message on the device then the message is accepted.

Developer Overview

5. The device receives the notification message; it starts a new OMA DM session sending the
OMA DM PKG 1 to the server; the DM message is first received by the HTTP listener and processed by the Funambol DM Server's HTTP handler.
6. The HTTP handler is now ready to open the DM session on the Funambol DM Server and
start the real message processing; as show in the figure, the incoming message passes through the input pipeline before getting to the management engine.
7. The management engine processes the request, including authentication and session

management.

8. To build the management commands to send to the client, the management engine selects
and calls the appropriate management processor for the management operation requested in Step 1.
9. The management actions to be performed are ready to be sent to the client; the outgoing
message passes through the output pipeline for post-processing.
10. The return message is translated into an OMA DM message. 11. The return message is returned to the device.
The processing now starts again at Step 5 with a new message from the client; in this case, all commands and results exchanged between client and server belong to the same session until the server stops sending commands. Note that in the case of an unsolicited new DM session, the client starts at Step 5 without receiving a notification message.

Database Schema

The internal database schema used by the Funambol DM Server is shown below.

Table Name fnbl_user

Description Stores basic user information, such as username, first and last name, and email. The internal_user field represents an applicative user, not a real person, but an application. This field is currently not used, but it was added for future use. Stores the list of the available roles (for future use) Stores the associations between the users and the roles (for future use).

fnbl_role fnbl_user_role

Table Name fnbl_device
Description Stores basic information about a device: device id description device type (e.g., Nokia 7650) digest (the MD5(user:password)) of the user this device will be associated with client_nonce (the nonce that the client will use to calculate the next session's digest) server_nonce (the nonce that the server will use to calculate the next session's digest) server_password (the server password)

fnbl_principal

Java's String class is treated specially and is written <string>Hello, world</string> where the characters of the string are converted to bytes using the UTF-8 character encoding.
Although all object graphs may be written using just these three tags, the following definitions are included so that common data structures can be expressed more concisely: The default method name is "new". A reference to a java class is written in the form <class>javax.swing.JButton</class>. Instances of the wrapper classes for Java's primitive types are written using the name of the primitive type as the tag. For example, an instance of the Integer class could be written: <int>123</int>. Java's reflection is internally used for the conversion between Java's primitive types and their associated "wrapper classes". In an element representing a nullary method whose name starts with "get", the "method" attribute is replaced with a "property" attribute whose value is given by removing the "get" prefix and decapitalizing the result. In an element representing a monadic method whose name starts with "set", the "method" attribute is replaced with a "property" attribute whose value is given by removing the "set" prefix and decapitalizing the result. In an element representing a method named "get" taking one integer argument, the "method" attribute is replaced with an "index" attribute whose value the value of the first argument. In an element representing a method named "set" taking two arguments, the first of which is an integer, the "method" attribute is replaced with an "index" attribute whose value the value of the first argument. A reference to an array is written using the "array" tag. The "class" and "length" attributes specify the sub-type of the array and its length respectively.

Lazy Initialization

When a bean is deserialized from its XML form, the classloader that loads the serialization file first calls the bean class's empty constructor, then it sets the values of the bean properties using the setXXX() methods. However, some classes need additional work to properly initialize; that work has to be done with meaningful properties values (in other words, after the setXXX() methods are called). To support this lazy initialization approach, those classes can implement com.funambol.framework.tools.beans.LayInitBean, which defines a separate init() method. When the DM Server loads a LazyInitBean, after the bean instantiation (or deserialization), it calls its init() method, giving the bean the opportunity to complete its initialization.

</Meta> <Data>c3luYzRqOnN5bmM0ag==</Data> </Cred> <Meta> <MaxMsgSize xmlns='syncml:metinf'>20000</MaxMsgSize> </Meta> </SyncHdr> <SyncBody> <Alert> <CmdID>1</CmdID> <Data>1201</Data> </Alert> <Replace> <CmdID>2</CmdID> <Item> <Source> <LocURI>./DevInfo/Lang</LocURI> </Source> <Data>en-us</Data> </Item> [.] <Item> <Source> <LocURI>./DevInfo/DevId</LocURI> </Source> <Data>Funambol</Data> </Item> </Replace> <Final/> </SyncBody> </SyncML>
This message will be translated into the object hierarchy shown below.
After being translated into an object tree, an incoming message passes through the input message processing pipeline, before getting to the Management Engine. This gives the opportunity to further processing the message when it is in a manageable representation. In a similar way, a response message going out from the Management Engine, passes through the output message processing pipeline before getting translated to its XML (and then WBXML) representation. The input and the output pipelines are completely customizable, so that custom message preand postprocessing can be easily added to the system. Input and output message processing components are also referred to as synclets.
Preprocessing an Incoming Message
To preprocess an incoming message, you create and input processor component and configure the Pipeline Manger accordingly.
Creating an Input Synclet
An input synclet is a class that implements the
com.funambol.framework.engine.pipeline.InputMessageProcessor interface. This
interface defines a single method,
void preProcessMessage(MessageProcessingContext context, SyncML msg)
where context is a request-scoped parameter that is shared by all synclets (both input and output) involved in the message processing, and msg is the object tree representing the DM message. The following is an example of an input synclet.
Example: public class MotorolaV500 implements InputMessageProcessor { // ------------------------------------------------ InputMessageProcessor public void preProcessMessage(MessageProcessingContext processingContext, SyncML message) throws Sync4jException { List items, validItems; List results = message.getSyncBody().getCommands(); Item item; AbstractCommand c; Results r; Iterator i = results.iterator(); while (i.hasNext()) { c = (AbstractCommand)i.next(); if (c instanceof Results) { r = (Results)c; validItems = new ArrayList(); items = r.getItems(); Iterator j = items.iterator(); while (j.hasNext()) { item = (Item)j.next(); if (item.getSource() != null) { validItems.add(item); } } List oldItems = r.getItems(); oldItems.clear(); oldItems.addAll(validItems); } }

Configuring an Output Synclet
You configure the output synclet by telling the Pipeline Manager to insert the new synclet in the output pipeline, as shown in the following server-side JavaBean (using the same configuration for the input pipeline as in the preceding section on the input synclet).
Example: <?xml version="1.0" encoding="UTF-8"?> <java version="1.4.0" class="java.beans.XMLDecoder"> <object class="com.funambol.framework.engine.pipeline.PipelineManager"> <void property="inputProcessors"> <array class= "com.funambol.framework.engine.pipeline.InputMessageProcessor" length="1"> <void index="0"> <object class="com.funambol.dm.synclet.MotorolaV500"/> </void> </array> </void> <void property="outputProcessors"> <array class= "com.funambol.framework.engine.pipeline.OutputMessageProcessor" length="1"> <void index="0"> <object class="com.funambol.server.engine.RespURISynclet"/> </void> </array> </void> </object> </java>
Implementing Management Operations
This chapter describes extending the Funambol DM Server by developing custom management operations.
Overview, page 42 Creating a Processor Selector, page 43 Creating a Management Processor, page 49 Using Scripting Management Processors, page 53
A management operation is a sequence of management commands that the server sends to the device in order to perform a higher level task. For example, in the case of the client settings provisioning, a setBrowserSettings operation is translated into a sequence of Get/Replace commands that will result in setting the phone browser configuration. The Management Engine is the core component that handles device management sessions and then operations. It implements the protocol requirements but delegates to external management processors the accomplishment of the management actions to perform during a management session. When a client starts a new management session, the Management Engine selects the Management Processor to use by the means of the Manager Selector. The selector will make its choice based on the content of the first device information sent by the client in the SyncML DM PKG 1. The architecture of the management engine is shown below.

Example: <?xml version="1.0" encoding="UTF-8"?> <java version="1.4.2" class="java.beans.XMLDecoder"> <object class="com.funambol.server.dm.OperationProcessorSelector"> <void property="defaultProcessor"> <string>com/funambol/server/dm/processor/DefaultProcessor.xml</string> </void> <void property="errorProcessor"> <string>com/funambol/server/dm/processor/ErrorProcessor.xml</string> </void> <void property="namePrefix"> <string>com/funambol/server/dm/processor/</string> </void> <void property="namePostfix"> <string>.xml</string> </void> </object> </java>
Configuring the Management Engine
To configure the management engine in order to use a specific processor selector, set the server.dm.selector property in Funambol.properties.
Example: server.dm.selector=com/funambol/server/dm/OperationProcessorSelector.xml
Creating a Management Processor
A Management Processor is represented by the interface
com.funambol.framework.engine.dm.ManagementProcessor, which defines the following
methods: Method void beginSession( String sessionId, Principal principal, int type, DevInfo info, DeviceDMState dmstate ) void endSession(int completionCode) Description Called when a management session is started for the given principal. SessionId is the content of the SessionID element of the OTA DM message; type is the management session type (as specified in the message Alert); info is the device info of the device under management; dmstate is the device management state, which represents a row of the fnbl_dm_state table. Called when the management session is closed. CompletionCode can be one of the following: STATE_COMPLETED STATE_ABORTED STATE_ERROR These constants are defined in com.funambol. framework.engine.dm.DeviceDMState. ManagementOperation[] getNextOperations() void setOperationResults (ManagementOperationResult[] results) String getName() Called to retrieve the next management operations to be performed. Called to set the results of a set of management operations. Name to uniquely identify the management processor instance (each installed management processor should have a different name in its configuration file).

ManagementOperation

This class represents an action that can be performed on a client management tree, such as a Get, Replace, Exec and so on. It belongs to the com.funambol.framework.engine.dm package.
ManagementOperation can represent one of the following actions (for additional information, see the SyncML Device Management Representation Protocol, version 1.1.2): Add Atomic Copy Delete Exec Get Replace Sequence

if (log.isLoggable(Level.FINE)) { log.fine("Device detail: " + details); } // // Reset the operation so that GetDeviceDetails won't be erroneously // called again // dmstate.operation = null; dmstate.state = DeviceDMState.STATE_COMPLETED; } void endSession(int code) { log.info("endSession with code: " + (char)code); } // ------------------------------------------------------------------------log.info("Global script!"); importCommands("com/funambol/server/dm/processor/bsh/command"); cont = true; status = new StringBuffer();
The script looks very similar to a Java class without main(). As said before, when the interpreter is first created, this script is evaluated; this makes the global part of the script (the statements in the outermost scope) to be interpreted and executed. In the case above, the utility commands are imported and some variables are initialized. Plus, remember that ScriptManagementProcessor will have set the scripting variables in the table above. Before calling any other method of the script, ScripManagementProcessor calls init(); this is a good point where to put initialization code. Note that in our example there is only the initialization of the cont variable. It is done again for two reasons: The global cont=true is done so that the variable cont will be created in the interpreter global scope (it is like a declaration) The init() method could be called more then once (but always once per management session) for example when initialization is retried in the case of a failed authentication.
The management processor asks the script processors which commands to send to the client calling getNextOperation(). In our case, we have to send a Get command for the three parameters./DevDetail/FwV,./DevDetail/SwV,./DevDetail/HwV; therefore, the needed parameters are set in the nodes map and a new GetManagementOperation is created. Note that a simplified syntax is used to set the operation's nodes. The management operation so created is returned to the management processor as an array of ManagementOperation objects setting the output variable operations. cont is then set to false to remember that the Get command has already been returned to the processor. The processor will then processes all the returned commands and will collect the results from the device. Those results are translated to ManagementOperationsResult objects and setOperationResults() is called. Again, note that the ManagementOperationResult[] array is passed to the script in the input scripting variable results.

<void property="nap"> <object class="com.funambol.framework.core.dm.ddf.NAP"> <void property="address"> <string>address</string> </void> <void property="addressType"> <string>5</string> </void> <void property="auths"> <object class="org.apache.commons.collections.map.ListOrderedMap"> <void method="put"> <string>PAP</string> <object class="com.funambol.framework.core.dm.ddf.Auth"> <void property="id"> <string>username</string> </void> <void property="secret"> <string>password</string> </void> </object> </void> </object> </void> <void property="bearer"> <string>11</string> </void> </object> </void> </object> </void> </void> </object> </void> </object> </java>

WAP Provisioning Profile

The content of the bootstrap message is based on the OMA Provisioning Content Specification using the registered document 'w7' that specifies how the APPLICATION characteristic should be used to bootstrap a DM device. For an example, see Bootstrap XML Message Examples on page 74. An external application can start a bootstrap process with this profile using the bootstrap() method of the external application API, with the following message type:
com.funambol.framework.notification.NotificationConstants. MESSAGE_TYPE_BOOTSTRAP_WAP.
For details on the external application API, see External Application Interfaces on page 60. The process of generating and sending a bootstrap message by the server consists of the following steps:
1. Update the database with the information of the device to be bootstrapped. 2. Read the SyncMLboostrapMessage.xml file and create a new SyncMLDM object. 3. Update the object created at the previous step with the server information. 4. Convert the SyncMLDM object in a WBXML WAP message and send it using the
configured BootStrap sender.

Plain Profile

The content of the bootstrap message is a SyncML DM message containing the nodes to be added to the device. For an example, see Bootstrap XML Message Examples on page 74. An external application can start a bootstrap process with this profile using the bootstrap() method of the external application API, with the following message type:

</characteristic> </characteristic> </characteristic> </wap-provisioningdoc>
Example <?xml version="1.0" encoding="UTF-8"?> <SyncML> <SyncHdr> <VerDTD>1.1</VerDTD> <VerProto>DM/1.1</VerProto> <SessionID>0</SessionID> <MsgID>0</MsgID> <Target> <LocURI>1</LocURI> </Target> <Source> <LocURI>http://localhost:8080/funambol/dm</LocURI> </Source> </SyncHdr> <SyncBody> <Add> <CmdID>1</CmdID> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol</LocURI> </Target> <Meta> <Format xmlns='syncml:metinf'>node</Format> </Meta> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/Addr</LocURI> </Target> <Data>http://localhost/funambol/dm</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/AddrType</LocURI> </Target> <Data>1</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/PortNbr</LocURI> </Target> <Data>8080</Data>
</Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ConRef</LocURI> </Target> <Data>test</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ServerId</LocURI> </Target> <Data>funambol</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ServerPW</LocURI> </Target> <Data>PkFcRTVRLzc1dUd1Qns1JA==</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ServerNonce</LocURI> </Target> <Data>Q3lHUkRRKUEhMlQnSH88Tg==</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/UserName</LocURI> </Target> <Data>1</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ClientPW</LocURI> </Target> <Data>1</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/ClientNonce</LocURI> </Target> <Data>TzpNeD5FWSctMGRHPCdOMg==</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/AuthPref</LocURI> </Target> <Data>syncml:auth-md5</Data> </Item> <Item> <Target> <LocURI>./SyncML/DMAcc/funambol/Name</LocURI> </Target> <Data>1</Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test</LocURI> </Target>
<Meta> <Format xmlns='syncml:metinf'>node</Format> </Meta> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP</LocURI> </Target> <Meta> <Format xmlns='syncml:metinf'>node</Format> </Meta> <Data></Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Bearer</LocURI> </Target> <Data>11</Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/AddrType</LocURI> </Target> <Data>5</Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Addr</LocURI> </Target> <Data>address</Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Auth</LocURI> </Target> <Meta> <Format xmlns='syncml:metinf'>node</Format> </Meta> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Auth/PAP</LocURI> </Target> <Meta> <Format xmlns='syncml:metinf'>node</Format> </Meta> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Auth/PAP/Id</LocURI> </Target> <Data>username</Data> </Item> <Item> <Target> <LocURI>./SyncML/Con/test/NAP/Auth/PAP/Secret</LocURI> </Target> <Data>password</Data> </Item>

04 0B 84 C03 C4 AF E3 FC D5 CAF 01 4F E7 9C 1C AD FC79 6E 6A

Example 3

04 0B 84 C03 C4 AF 87 A3B 47 B8 D0 B3 D7 4C 45 9F BBC79 6E 6A
Explanation of Example 3: WDP Header:
06: User-Data-Header(UDHL) Length = 6 bytes 05: UDH IE Identifier Port Number 04: UDH port number IE length 0B: Destination port (high) 84: Destination port (low) C0: Origination port (high) 02: Origination port (low)

WSP Header:

01: Transaction ID / Push ID 06: PDU Type(push) 03: Headers length (content type + headers) C4: Content type AF: X-WAP-Application-ID 87: Id for urn: x-wap-application:syncml.dm

Digest:

A3B 47 B8 D0 B3 D7 4C 45 9F BB1

Notification Message:

02 C79 6E 6A