Manuale d’uso / di manutenzione del prodotto SIP 3.1 del fabbricante Polycom
Vai alla pagina of 71
August, 2008 Edition 1725-17693-310 Rev. A SIP 3.1 W eb Application Developer’ s Guide for the Polycom ® SoundPoint ® IP/SoundStation ® IP Family SIP 3.
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.
iii About This Guide The Developer’s Guide for the SoundPoint IP / SoundStation IP family is for developers of applications which use the Web Server and the Microbrowser on SoundPoint IP / SoundStation IP phones.
Developer’ s Guide SoundPoint IP / SoundStation IP iv.
v Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 What is the Microbrowser . . . . . . . . . . . . . . . . . . .
Developer’ s Guide SoundPoint IP / SoundStation IP vi 3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 XML Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 - 1 1 Over view This chapter provides an overview of the Web Serv er and the Microbrowser available on SoundPoint IP 330/32 0, 430, 501, 550 , 560, 60 0, 601, 650, and 67 0 desktop phones and SoundStation IP 4000, 6000, and 7000 co nference phones. It also provides an introduction to XHTML and guidelines for the application development.
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.
Over view 1 - 3 beyond a skeleton set were gro uped into individual modules . User agent (UA) developers could then d ecide which extensions to support.
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.
Over view 1 - 5 New Features in SIP 3.1 The following new features were introduced in SIP 3.1: • SoundPoint IP/SoundStatio n IP XML API Application Interface —Expanded support in the Microb rowser.
Developer’ s Guide SoundPoint IP / SoundStation IP 1 - 6.
2 - 1 2 Application Development This chapter presents step-by-step in structions on how to develop an XHTML application that can be run on the We b Server and Microbrowser of certain SoundPoint IP and SoundStation IP phones. It also describes the configuration parameters that can be found in the sip.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 2 • 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 • <!--.
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.
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.
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.
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 .
Application Development 2 - 7 Ta b l e Ta g s The following tabl e tags are supported: • <table> —Defines a table • <caption> —Defines a table caption • <th> —Defines a t.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 8 <caption> This element defines a table caption. The <caption> tag must be inserted immediately after the <table> tag. You can specify only one caption per table. Usually the caption will be centered above the table.
Application Development 2 - 9 bgcolor rgb(x,x,x) #xxxxxx colorname S pecifie s the background co lor of the table cell. Deprecated. Use styles instead.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 10 <tr> This tag defines a row in a table. The following attributes are supported: <td> This tag defines a cell in a table.
Application Development 2 - 11 <thead> This tag defines a table header. The thea d, tfoot and tbody elements enable you to group rows in a table. When you create a table, you might want to have a header row, some rows wi th data, and a row with totals at bottom.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 12 <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: <tfoot> This tag defines a table footer.
Application Development 2 - 13 Meta Information T ags The following meta information tags are supported: • <head> —Defines information about the document <head> The head element can contain informat ion about the document. The browser does not display the “head information” to the user.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 14 The SoundPoint IP/Sound Station IP XML API is intended to provide developers wit h flexibilit y in developi ng applications on SoundPoint IP and SoundStation IP phones, while tightly in tegrating into the phone’s telephony capabilities and functions.
Application Development 2 - 15 The supported actions are de scribed in the following table: Depending on the browser state, a number of predefined soft keys exist: Action Default Action Name Descripti.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 16 The following should be noted with respect to softkey tags: • All actions are case insensitive. • If the soft key action name is empty, the soft key tag is ignored. • The Reset and Submit so ftkey tags must exis t inside the <form> tag that they are to act upon.
Application Development 2 - 17 The following format is supported: ActionType:Action where: • ActionType is a type of key or action to execute (Key, Softkey, Tel, or Play) • Action is the name of the action to be executed.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 18 The following should be noted with respect to internal URIs: • The action name and key type are case insensitive. • For non-XHTML content containing only internal URIs, the internal URIs are executed in ascending order without any delay.
Application Development 2 - 19 For example, to create a link th at behaves as if you pressed the Do Not Disturb key: <html> <body> <br/> Click on the link to engage the DND feature &.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 20 The following table describes when to use a specific priorit y: The following should be noted with respect to HTTP URI push: • By default, a Back soft key is placed on the graphic display. • The phone can hold a maximum of 10 push requests at any time.
Application Development 2 - 21 Data Push The data push allows you to send messages in XHTML format to a specific phone. The following format is supported: <Data priority=”X” >Y</Data> .
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 22 • Set apps.push.password to the appropriate password. For example, apps.push.password =1234 T elephony Notification Events The phone can b.
Application Development 2 - 23 CallingPartyName name The name displayed in phon e's "From" label in screen. • If the line is registered and the call is initiated from that line, then the registered l ine display name of the calling party is shown.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 24 When the telephone notification URI is set and the incoming call event is enabled to gather information, the following example shows the transmitted data for a call between two registered lines: <PolycomIPPhone> <IncomingCallEvent> <PhoneIP>172.
Application Development 2 - 25 Offhook Event The following format is supported: <OffHookEvent> <PhoneIP> </PhoneIP> <MACAddress> </MACAddress> <TimeStamp> </Time.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 26 The following attributes are supported: Onhook Event The following format is supported: <OnHookEvent> <PhoneIP> </PhoneIP>.
Application Development 2 - 27 • Set apps.telNotification.incomingE vent to 1 or 0 (for Enable or Disable respectively). For example, apps.telNotification.incomi ngEvent =1 • Set apps.telNotification.outgoingE vent to 1 or 0 (for Enable or Disable respectively).
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 28 Call Line Information The following format is supported: <CallLineInfo> <LineKeyNum> </LineKeyNum> <LineDirNum> <.
Application Development 2 - 29 When the phone state polling URL is set and the phone receives a Call Processing Request, the following example shows the transmitted data: <PolycomIPPhone> <Ca.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 30 <LineState>NotConnected</Line State> </CallLineInfo> <CallLineInfo> <LineKeyNum>3</LineKeyNum> <LineD.
Application Development 2 - 31 Network Configuration The following format is supported: <NetworkConfiguration> <DHCPServer></DHCPServer> <MACAddress>0004f214b8e7</MACAdd ress> <DNSSuffix></DNSSuffix> <IPAddress>172.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 32 Phone State Polling Configuration Parameters The phone state polling conf iguration parameters in sip.cfg must be set as followed: • Set apps.statePolling.URL to the location where requested information should be sent.
Application Development 2 - 33 HTTP Suppor t The Microbrowser is a fully compliant HTTP/1.1 user agent: • It supports: — Cookies — Refresh headers — HTTP proxies — HTTP over SSL/TLS — Self-signed or custom CA certificates • There are the following exception s: — There is no sophisticated caching.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 34 • 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.
Application Development 2 - 35 Whenever there is an event in the telephony application that requires the user's attention, the telephony applic ation is brought to the foreground automatically. The Microbrowser can be displaye d again by simply pushing the Applications key.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 36 Developing an XHTML Application Changing Configuration Parameters Create a new configuration file in the style of sip.cfg so that users will connect to your application when they press the App licatio n key (or select the Application feature item).
Application Development 2 - 37 a Set apps.push.messageType to the appropriate display priority. For example, apps.push.messageType =3 b Set apps.push.serverRootURL to the application server root URL. For example, apps.push.serverRootURL =http://172.24.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 38 b Set apps.statePolling.username to the appropriate username. For example, apps.statePolling.username =bob The username and password are requ ired to a uthentica te incoming polling requests to the phone.
Application Development 2 - 39 2. Configure the Web server to serve the above XHTML file. For example, if you are using Apache To mcat to try this example, then put this file into the webappsPLCM folder of Tomcat. 3. Configure SoundPoint IP and SoundStation IP phones to point to the XHTML file in the sip.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 40 3. Write an application that is going to retrieve the stock informa tion from a data service provider. For this example, this a pplication will be retrieving stock information from Yahoo and will send it to the Microb rowser.
Application Development 2 - 41 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 webappsPLCM folder of Tomcat. 5. Configure SoundPoint IP and SoundStation IP phones to point to the XHTML file in the sip.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 42 • After the customer clicks Send Requ est , the page shown belo w is pushed to the customer support agent’s phone. The customer support agent can call the customer by just pressing the Select key, because the highlighted link contai ns a Tel URI with the customer’s phone number.
Application Development 2 - 43 </body> </html> 2. Using Microsoft Vi sual Studio, create a file cal led webcallback.aspx.cs . using System; using System.IO; using System.Text; using System.Data; using System.Configuration; using System.Net; using System.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 44 string result = ""; // Create the web re quest HttpWebRequest reque st = (HttpWebRequest)WebRequest.C reate(strLoc); WebRequestState myRe questState = new WebRequestState (); myRequestState.
Application Development 2 - 45 // Write the data to the stream. streamResponse.Write (byteArray, 0, byteArray.Length) ; streamResponse.Close (); allDone.
Developer’ s Guide SoundPoint IP / SoundStation IP 2 - 46.
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.
Developer’ s Guide SoundPoint IP / SoundStation IP 3 - 2.
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 a g Description Basic T ags <html>—Defines HTML document. <body>—Defines docu me nts’ body .
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.
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 .
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. <col>—Defines attributes for table columns.
Index – 1 Index A application development process 2–36 B basic tags supported 2–2 unsupported A–1 block tags unsupported A–2 C character format tags unsupported A–1 configuration parameter.
Developer’ s Guide SoundPoint IP / SoundStation IP Index – 2 U unsupporte d attributes A–1 unsupported elements A–1 X XHTML, definition 1–2.
POLYCOM, INC. APPLICATION PROGRAMMING INTERF ACE LICENSE (“API”) FOR SOUNDPOINT IP AND SOUNDSTATION IP PRODUCTS (“Product” or “Products”). 1.
By downloading the following Sample Applic ations, you agree to the below end user license agreement. LICENSE AGREEMENT FOR DEVELOPMENT P URPOSES This License Agreement for Development Purposes (the "A greement") is a legal agreement between you and Polycom, Inc.
2.3. Reservation. Polycom reserves all rights in the Software not expressly granted to you in this Agreement. 3. SUPPORT SERVICES. 3.1. No Support Services.
for certain products supplied to consumers or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in thei r application to you.
agreement shall be construed to limit eithe r party's right to inde pendently develop or distribute software that is f unctionally similar to the other party's products, so long as proprietary information of the other part y is not included in such software.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Polycom SIP 3.1 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Polycom SIP 3.1 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Polycom SIP 3.1 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Polycom SIP 3.1 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Polycom SIP 3.1, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Polycom SIP 3.1.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Polycom SIP 3.1. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Polycom SIP 3.1 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
