Documentation Contents

User Documentation

Administrator Documentation

Index of terms

Technical Support

On-line Search

This application gives an opportunity to a cell phone user to access some selected information and services of the mail server, to which he gets connected usually through his mail client - in this case we are talking about MS Exchange server. Access to these informations have only those users, who are registered on the mail server and have the right cell phone number set in their mailbox.

These informations and services are supported in present time:

• searching in user's contacts - samples
• searching in company's contacts - samples
• calendar + meeting arrangement - samples
• "Inbox" folder - samples
• Send - samples
• Reply - samples
• Forward - samples
• Respond (Meeting Request) - samples
• Language settings
• 'Out of office' flag settings
• brief help

User's contacts and company's contacts

• "?a" - for access to user's contacts,
• "?g" - for acces to company's contacts.

• "?xn" - searching is limited only to the "Display Name" item (very fast searching).
• "?x" - basic searching, the "Display Name", name, surname, "Nick Name", ("File As"), e-mail, e-mail2, e-mail3 a the company's name are being searched.
• "?xa" - enhanced searching, complete address and all phone numbers are being searched either.

Every contact goes back as a separate SMS, the number of returned contacts is limited with script setting (ex: 5 contacts found - see MCO installation). If more matching records are found, a special message is sent with the number of found contacts that recommends the user to give a better specification of his request.

Returned information is in format "Display Name(available informations)". Available informations are in this order:

• name and surname,
• address, ZIP, place,
• BP: + business phone (+ second phone),
• BF: + business fax,
• HP: + home phone (+ second phone),
• HF: + home fax,
• OP: + other phone no.,
• M: + cell phone,
• C: + company name,
• E: + e-mail (+ second, third e-mail),
• W: + web page.

Samples

"?g @datasys.cz" - person(s) searching due to e-mail (or its part) - all company's contacts who has an e-mail by Datasys company, s. r. o. (that could be more than 5 persons so we get summary count of Datasys employees with valid e-mail account).

"?ga 0603123456" - person searching by number - all company's contacts that contain searched phone number.

back to top of page

Calendar

• "?c" - sends all meetings valid for today from now one hour minus (now -1) (covers presently running meetings that don't have duration longer than 1 hour) till today's midnight.

• "?c offset" - offset tells the day due to today:
  • "?c 0" - all today's meetings (from the beginning of the day),
  • "?c 1" - all tomorrow's meetings,
  • "?c 2" - all meetings for after-tomorrow, etc.

• "?c date" - access to meetings for entered day. The date can be entered in various formats, ex: appointments from 31st December 2000 can be requested like these:
  • "?c 2000 12 31"
  • "?c 00 12 31"
  • "?c 12 31"

Each meeting returns as a separated SMS. The count of returned meetings is not restricted.

Returned information is in format "1/3 #id# 31.12.00 15:30-16:00 L:where S:what F:from T:text".
The meaning of each item is as follows:

• "1/3" - "the number of meeting in the time of the day" divide "summary count of found meetings,
• "#id#" - unique identification of meeting, which can be used if we want to receive more detailed info (it is generated by every request to the particular day so it can be used only to the next request for this day and in the time of few following days),
• "31.12.00 15:30-16:00" - the time range of planned meeting,
• "where" - place of appointment,
• "what" - subject of appointment,
• "from" - SMTP address of the meeting creator,
• "text" - meeting description limited with one SMS length (including previous informations).

• "?c id(or #id#)" or "?c any_text #id# any_text".

"ID" parameter is being proccessed as a text so it must be enterd completelly, including zeros at the beginning.

Samples

"?c 4 22" - all meetings from 22nd April actual year.

"1/3 #0003# 22.4.00 15:00-16:00 L:Albertov S:Tenis F:Ivan Lendl T:..." - sample message (or the first of three messages), that we could receive as a response to the previous request and which we can use as base for request for detailed informations about this meeting. "ID" parameter is in this case "0003".

If the cell phone doesn't allow to use the received SMS, it is possible to enter a new (equivalent) command "?c #0003#" or "?c 0003" only.

Meeting creation

• "?cn hour[:minute] [year[month[day]]] [D[separator]duration] R[separator]partners [S[separator]subject]
  [L[separator]place] [T[separator]description]"
  • "hour" - time of meeting, hour (one- or two ciphered).
  • "minute" - time of meeting, minute (always two-ciphered), default value ":00"
  • "year" - date of meeting, year (one- or four-ciphered). If not four-ciphered, value of 2000 is counted in. Optional, current year as default.
  • "month" - date of meeting, month (one- or two ciphered). If a year is entered, the month is always two-ciphered. Optional (if year is not entered), current month as default.
  • "day" - date of meeting, day (one- or two ciphered). In month is entered, the day is always two-ciphered. Optional (if month is not entered), current day as default.
  • "duration" - meeting duration in minutes. Optional, 30 minutes as default.
  • "partners" - the list of partners (postal addresses separated with ";" or comma) which are to be invited.
  • "subject" - meeting subject.
  • "place" - place of meeting.
  • "description" - meeting description.

[separator] - one of the characters ".", ":" or "*". Optional but if used, it has to be unique in the whole message, (so if I use a ":" at first, I have to use it always further). Allows to enter a text with spaces not containing selected separator as an argument. If not used, only one word without any space is taken as an argument. If entered, the argument is the whole text next to following separator (except the letter in front of following separator).

Samples

"?cn 15:30 4 ..." - meeting at 15.30, current month 4th.

"?cn 8 701" - meeting at 8 am, July 1st this year.

"?cn 9:30 10401" - meeting at 9.30 am, April 1st 2001.

"?cn 11:00 19991224" - meeting at 11 am, 24th December 1999.

Samples - arguments

"?cn ... Ragassi@tenis.com;lendl@tenis.com..." - to the meeting will be invited partners agassi@tenis.com a lendl@tenis.com.

"?cn ... R:Agassi Andre;Lendl Ivan S: ..." - to the meeting will be invited partners Agassi Andre and Lendl Ivan. Behind the type of argument was now used a separator, so it is possible to use spaces in the name of partners. To recognize partners in this format they must be stored in Exchange Global Address List (not in Contacts!). Further it is shown that in the next argument (and all following) must be used the same separator.

"?cn ...L1.floor .." - behind the type of argument (place of meeting) isn't a separator used, so it's not possible to use space, but you can use a dot though because the word till the first space behaves itself as an argument. We suppose that in none of previous arguments wasn't used a separator. (Similar for "S ...".)

"?cn ...L:1. floor T: ..." - in the place of meeting is used a space, so it's necessary to use a separator and next is used a dot so it's not possible to use it as a separator, resp. as a separator is used ":" so this mark cannot be used in the place of meeting. But in the following arguments must be used separator either (Similar for "S: ...".).

"?cn ... T:meeting description" - a separator was used so it's possible to use a spaces.

"?cn ... Tmeeting description" - a separator is not used but spaces are though. This is possible in the case, when in the whole message was not a separator used and the argument of meeting description is the last (no further are not to be detected).

Samples - complete meeting creation

"?cn 17:30 1224 R:Santa;Claus S:Xmas L:Prague T:Bring something!" - 24th December, 17:30, 30 minutes (default), separator by partners, so necessary at following arguments.

back to top of page

Inbox

• "?m" - sends the information about unread messages (incoming after last usage of this command). The age of messages is limited to 14 days, which is the default value and can be modified by an administrator. Next, the number of messages is limited to 16, which is again the default value and can be modified by an administrator. More unread messages is possible to get by repeating a question.

Enhanced command form is: "?m offset [r|u|a] [h|n|l|a]". All items are optional (default values are listed further), but if any is entered, must be entered all previous. Meaning of each item is as follows:

• "offset" - sets the day depending to today - goes like this:
  • "?m 0" - today's messages,
  • "?m 1" - yesterday's messages,
  • "?m 2" - before yesterday's messages etc.
• "[r|u|a]" - type of message:
  • "r" - read messages only,
  • "u" - unread messages only (default),
  • "a" - all messages.
• [h|n|l|a] - message priority:
  • "h" - high priority messages only,
  • "n" - normal priority messages only,
  • "l" - low priority messages only,
  • "a" - all messages without regarding to their priority (default).

• "2/5" - "message number in the meaning of matching messages" slash "summary count of messages matching the request",
• "#id#" - unique identification of message which can be used if we want to receive more detailed informations (it is being generated again by every request containing the concrete messages, so it can be used only to the next request for this message even for several days ),
• "from" - e-mail address of the sender,
• "subject" - subject of message.

• "?m id(or #id#)"

"ID" parameter is being handled as text so it must be entered complete with the zeros at the beginning.

Samples

"?m 0 u h" - today's unread messages with a high priority.

"1/1 #0004# F:lendl@tenis.com S:Today on Albertov" - sample of message that we could receive as a response to the previous request which contains informations about only one e-mail and which can be used as base for request for more detailed info about this e-mail. "ID" parameter is in this case "0004". If the message contained informations about more e-mails and we would have used it as a request we would have received informations about one e-mail (from the listed) only.

If the cell phone doesn't allow to re-use received SMS, or if the incoming message contains informations about more e-mails, it is possible to enter a new, equal, command "?m #0004#" or only "?m 0004", where we enter only suitable "ID".

back to top of page

Send message

• "?e recipients subject text" - "recipients" and "subject" have to be one word (without spaces) or:
• "?e R[separator]recipients [S[separator]subject] [T[separator]text]
  • "recipients" - required, list of mail addresses (instead of '@' you can use '*') separated with semicolon or comma to which should the message be sent
  • "subject" - optional, message subject.
  • "text" - optional, message text.

[separator] - one of the characters ".", ":" or "*". Optional but if used, it has to be unique in the whole message, (so if I use a ":" at first, I have to use it always further). Allows to enter a text with spaces not containing selected separator as an argument. If not used, only one word without any space is taken as an argument. If entered, the argument is the whole text next to following separator (except the letter in front of following separator).

Samples

back to top of page

Reply

• "?r id(or #id#) reply_text"
  • "id" or "#id#" - sets the only one message we are answering to. We can get it via "?m" command which grants access to incoming messages including their identificators.
  • "reply_text" - required value, if it is not entered, no action will be processed.

Samples

back to top of page

Forward

• "?f id(or #id#) recipient_list reply_text"
  • "id" or "#id#" - sets the only one message which is being forwarded. We can get it via the "?m" command, which grants access to incoming message uncluding their identificators.
  • "recipient_list" - list of mail addresses (instead of '@' you can use '*') separated with semicolon or comma to which should the message be forwarded.
  • "reply_text" - optional value

In the case that one or more recipients won't be recognized, the message of non-recognized recipients will be sent as a SMS to the cell phone.

Samples

back to top of page

Respond (Meeting Request)

• "?m[a|d|t] id(or #id#) respond_text"
  • ?ma - accept meeting; ?md - decline meeting; ?mt - tentative meeting
  • "id" or "#id#" - sets the only one message we are answering to. We can get it via "?m" command which grants access to incoming messages including their identificators.
  • "respond_text" - optional value.

Samples

back to top of page

Language settings

• "??lng" - send current settings of language.
• "??lng language" - set selected language.

back to top of page

'Out of office' flag settings

• "??out" - send an information about current 'Out of office' flag settings.
• "??out 0" - disable flag 'Out of office' (an alternative text: "0", "off", "n", "no").
• "??out 1 text" - enable flag 'Out of office' (an alternative text: "1", "on", "y", "yes") and if text is entered, set a text of an automatically reply.

back to top of page

Brief help

• "??" - sends text file with help.
• "??name of request" - sends text file with the request syntax.

Samples

• "??a" - sends syntax for local contacts searching request.
• "??c" - sends syntax for calendar searching request.
• "??cn" - sends syntax for a new meeting creation command.

back to top of page