Go to page of
Similar user manuals
-
IP Phone
Polycom 3726-17861-001
2 pages 0.53 mb -
IP Phone
Polycom SIP 3.0.2
288 pages 4.29 mb -
IP Phone
Polycom 1725-44328-001
22 pages 1.19 mb -
IP Phone
Polycom 5000
76 pages 4.86 mb -
IP Phone
Polycom CX3000
22 pages 1.81 mb -
IP Phone
Polycom 1725-31424-001
56 pages 1.56 mb -
IP Phone
Polycom SOUNDPOINT IP 33X
96 pages 2.5 mb -
IP Phone
Polycom VVX400
95 pages 2.76 mb
A good user manual
The rules should oblige the seller to give the purchaser an operating instrucion of Polycom VR-6000, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.
What is an instruction?
The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Polycom VR-6000 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.
Unfortunately, only a few customers devote their time to read an instruction of Polycom VR-6000. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.
What should a perfect user manual contain?
First and foremost, an user manual of Polycom VR-6000 should contain:
- informations concerning technical data of Polycom VR-6000
- name of the manufacturer and a year of construction of the Polycom VR-6000 item
- rules of operation, control and maintenance of the Polycom VR-6000 item
- safety signs and mark certificates which confirm compatibility with appropriate standards
Why don't we read the manuals?
Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Polycom VR-6000 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Polycom VR-6000, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Polycom service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Polycom VR-6000.
Why one should read the manuals?
It is mostly in the manuals where we will find the details concerning construction and possibility of the Polycom VR-6000 item, and its use of respective accessory, as well as information concerning all the functions and facilities.
After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.
Table of contents for the manual
-
Page 1
April, 2008 Edition 1725-17693-300 Rev. A SIP 3.0.2 W eb Application Developer’ s Guide for the SoundPoint ® IP/SoundStation ® IP Family SIP 3.0.2[...]
-
Page 2
Polycom Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduce d or transmitted in any form or by any means, el ectronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reprod ucing includ es translating into another language or format. As between the part[...]
-
Page 3
iii About This Guide The Developer’s Guide for the SoundPoint IP / SoundStation IP family is for developers of applications which use the Microbrowser on Soun dPoint IP / SoundStation IP phones. The following relat ed documents for Soun dPoint IP / SoundStation IP family are available: • Quick Start Guides, which describe how to assemble the ph[...]
-
Page 4
Developer’ s Guide SoundPoint IP / SoundStation IP iv[...]
-
Page 5
v Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 What is the Microbrowser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 What is XHTML . . . . . . . . . . . . . . . . . . . [...]
-
Page 6
Developer’ s Guide SoundPoint IP / SoundStation IP vi[...]
-
Page 7
1 - 1 1 Over view This chapter provides an overview of the Microbrowser available on SoundPoint IP 330/320 , 430, 501, 550, 560, 6 00, 601, 650, and 670 desktop phones and SoundStation IP 4000, 6000, and 7000 conference phones. It also provides an introduction to XHTML and guidelines for the application development. This chapter contains informatio[...]
-
Page 8
Developer’ s Guide SoundPoint IP / SoundStation IP 1 - 2 The XHTML pages displayed on the Micr obrowser can contain static or dynamic information. Static XHTML. These pages are created us ing XHTML editors and hoste d by the Web server. These pages are accessed from the Microbrowser (usin g HTTP protocol) by entering the URL to a ccess the page. [...]
-
Page 9
Over view 1 - 3 where XHTML was divided up into ‘mod ules’, where any features abo ve and beyond a skeleton set were gro uped into individual modules . User agent (UA) developers could then d ecide which extensions to support. A s imple user agent can be considered a fully compli ant user agent by supporting only the Basic module, whereas a mor[...]
-
Page 10
Developer’ s Guide SoundPoint IP / SoundStation IP 1 - 4 • Company directory • Stock ticker Dependin g on the type and complexity of the application, you might use one of the following tools for creation: • Text editor • XML editor • Microsoft Word When designing applicati ons, you migh t want to consider the following guidelines: 1. Sp[...]
-
Page 11
2 - 1 2 Application Development This chapter provides informati on on supported XHTML elements. It describes HTTP support and the Microbrows er user interface. It also describes the configuration parameters that can be found in sip.cfg . This chapter presents step-by-step in structions on how to develop an XHTML application that can be run on the M[...]
-
Page 12
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 2 • Table Tags • Meta Information Tags Unsupported elements and attributes are de scribed in Unsupported XHTML Elements on page A-1 . Basic T ags The following basic tags are supported: • <!DOCTYPE> —Defines the document type • <!--...--> —Defines a comment <!DOCTYP[...]
-
Page 13
Application Development 2 - 3 <!--...--> The comment tag is used to insert a comment in the source code. A comment will be ignored by the browser. You can use comments to explain your code , which can help you when you edit the source code at a later date. This tag does not have any attributes. Link T ags The following link tag is supported: [...]
-
Page 14
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 4 <form> The form element creates a form for user input. A form can contain text fields, check boxes, radio buttons and more. Forms are used to pass user d ata to a specified URL. The following attributes are supported: Note The Microbrowser supports both the GET and POST methods for su[...]
-
Page 15
Application Development 2 - 5 <input> The <input> tag defines the start of an input field where the user can enter data. In XHTML the <input> tag must be properly closed. The following attributes are supported: Attribute Va l ue / s Description checked checked Indicates that the input elem ent should be checked when it first loads[...]
-
Page 16
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 6 Image T ags The following image t ag is supported: • <img> —Defines an image The Microbrowser supports imag es stored in uncompressed .bmp format. While all BMP bit depths will be displayed to the best of the phone’s ability, it is recommended that the image format most suitable[...]
-
Page 17
Application Development 2 - 7 Ta b l e Ta g s The following tabl e tags are supported: • <table> —Defines a table • <tr> —Defines a table row • <td> —Defines a table cell • <tbody> —Defines a table body <table> The <table> tag defines a table. Inside a <table> tag you can put table headers, [...]
-
Page 18
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 8 <tr> This tag defines a row in a table. The following attributes are supported: <td> This tag defines a cell in a table. The following attributes are supported: Attribute Va l ue / s Description align right left center justify char Defines the text alignment in cells. Attribute [...]
-
Page 19
Application Development 2 - 9 <tbody> This tag defines a table body. The thead, tfoot and tbody elements enable you to group rows in a tabl e. The following attributes are supported: Meta Information T ags The following meta information tags are supported: • <head> —Defines information about the document <head> The head elemen[...]
-
Page 20
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 10 — HTTP over SSL/TLS — Self-signed or custom CA certificates • There are the following exception s: — There is no sophisticated caching. The HTML cache refresh META tag is not supported. — Any images in the body of a document with the same URL are assumed to be the same image. Th [...]
-
Page 21
Application Development 2 - 11 • A n i n s t a n c e t h a t d o e s n o t s u p p o r t u s er input, but appears in a window on the idle display Launching the Microbrowser The first time the Applications ke y is press ed, the main Mic robrowser loads the home page specified in the mb.main.home configuration parameter. Subsequent presses of the [...]
-
Page 22
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 12 When the user has focused on a link that they would like to follow, or a form element they would like to toggle, they press the Select key. This will either generate a request for the linke d page or toggle the selection of an element in the form. When the focus moves to fields which are e[...]
-
Page 23
Application Development 2 - 13 T o allow an application to be r un from the Microbrowser: 1. Open a new configuration file in an XML editor. 2. Add the Microbrowser <mb> parameter. 3. Set mb.proxy to the address of the desired HTTP proxy to be used by the Microbrowser. For example, mb.proxy=10.11.32.103:8080 where 10.11.32.103 is proxy server[...]
-
Page 24
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 14 T o develop a static XHTML application: 1. Create a Sample.xhtml page with static information to be displayed. In this case, the static information will be "Hello World!". <html> <head> <title>Sample Application</t itle> </head> <body> <p>[...]
-
Page 25
Application Development 2 - 15 <!- - BODY END - -> </html> 2. Configure the Web server to serve the above XHTML file. For example, if you are using Apache To mcat to try this example, put this file into the webappsPLCM folder of Tomcat. 3. Write an application that is going to retrieve the stock informa tion from a data service provide[...]
-
Page 26
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 16 <!-- START DISPLAY BMP FILE --> <img src="quote.bmp"/> <!-- END DISPLAY BMP FILE -- > </body> </html> 4. Configure the Web server to deploy the above JSP file. For example, if you are using Apache To mcat to try this example, put this file into the w[...]
-
Page 27
3 - 1 3 T roubleshooting This chapter presents problems, li kely causes, and corrective actions. Problems are grouped as follows: • XML Errors If you still need as sistance, c ontact your system administrator. XML Errors Symptom Problem Corrective Action Improperly formatted tables could cause the phone to stop and restart or display the error ?[...]
-
Page 28
Developer’ s Guide SoundPoint IP / SoundStation IP 3 - 2[...]
-
Page 29
A - 1 A Appendix This appendix provides information on unsupported XHTML elements. Unsuppor ted XHTML Elements The unsupported elements and attributes are: Ta g Ty p e T ag Description Basic T ags <html>—Defines HTML document. <body>—Defines docu ments’ body . <h1> to <h6>—Defines header 1 to header 6. <p>—De[...]
-
Page 30
Developer’ s Guide SoundPoint IP / SoundStation IP A - 2 Output T ags <pre>—Defines preformatted text. <code>—Defines computer code text. <tt>—Defines teletype text. <kbd>—Defines keyboard text. <var>—Defin es a va ri ab l e. <dfn>—De fi ne s a de fi n i ti on te rm. <samp>—Defines sample co[...]
-
Page 31
Appendix A - 3 Input T ags <form>—Defines a form. The following attributes ar e not supp orte d: accept, accept charset, enctype, target, class, id, style, title, dir , lang, and accesskey . <input>—Defines an input field. The following attributes are not su pported: accept, align, alt, disabled, maxlength , readonly , size, arc, ty[...]
-
Page 32
Developer’ s Guide SoundPoint IP / SoundStation IP A - 4 Ta b l e Ta g s <table>—Defines a table. The following atrribu te s are not supported: bgcolo r , frame, rules, summary , id, cla ss, title, style, dir , lang, and xml:lang. <caption>—Defines a table caption. <col>—Defines attributes for table columns. <th>—D[...]
-
Page 33
Appendix A - 5 Programming T ags <script>—Defines a script <noscript>—Defines a noscript section <applet>—Deprec ate d. Defines an applet <object>—Defi nes an embe dded object <param>—Defines a parameter for an object Ta g Ty p e T ag Description[...]
-
Page 34
Developer’ s Guide SoundPoint IP / SoundStation IP A - 6[...]
-
Page 35
Index – 1 Index A application development process 2–12 B basic tags supported 2–2 unsupported A–1 block tags unsupported A–2 C character format tags unsupported A–1 configuration parameters, changes t o 2–12 F frame tags unsupported A–2 H HTTP support 2–9 I image tags supported 2–6 unsupported A–3 input tags supported 2–3 un[...]
-
Page 36
Developer’ s Guide SoundPoint IP / SoundStation IP Index – 2 X XHTML, definition 1–2[...]