The Polycom model 600, 601, and 650 phones have a feature called Microbrowser that allows browsing of simple XHTML web pages on the phone's LCD screen. In addition the microbrowser can also be used to display information on the phone's idle screen, however in this mode navigation is not possible.

There is very limited information about this feature in the Polycom documentation.

To use this feature, you set a starting URL in the configuration file that gets loaded when the phone boots, or you can set it using the phone's web configuration page. The option is called: Main Browser Home.

Hit the Services key on the phone to acces this URL.

---

The idle display can also be configured to access a URL, and automatically refresh on a periodic basis. The provisioning variables are mb.idleDisplay.home="(url)" and mb.idleDisplay.refresh="(seconds").

The following tags are the only tags known to be supported. Unknown (but properly formatted) tags are ignored by the microbrowser:

  html, head, title, body, img, b, u, a, br, hr, img, form, input

tables are not supported at all.

---

David Gomillion dgomillion at eyecarenow.com posted on the Asterisk Users Mailing List his experiences implementing a timeclock system using the Polycom Microbrowser.

Here are David's hints for using the Microbrowser

All HTML tags including single element tags must be closed as the browser is very strict on XHTML syntax.

The BR tag for instance should be written as <BR/>, <BR /> or even could be <BR></BR> but <BR> by itself is not valid in XHTML.

XHTML Syntax errors will cause the browser to return an error. No portion of the page will be rendered.

This will not work:
  <input type="text" name="myfield">
This will
  <input type="text" name="myfield" />

This will not work:
   <p>....<p>...
This will:
   <p>...</p><p>....</p>

Tags which are specifically not supported

The following are not supported:

• <b>...</b>
• <i>...</i>
• <small>...</small>
• <select>...</select>
• <table>...</table> (And associated element tags)

Image support

• Inline images are supported by the microbrowser. Only 1bpp and 4bpp windows byte order .bmp's seem to be supported. .GIF, .JPG, .PNG and other common web image formats do not work. Make sure to close the IMG tag (ex: <img src="image.bmp" height="20" width="40"/>)
• If you don't include image dimensions in the IMG tag, the page will render but will take a much longer time to draw as it has to reformat the layout both before and after it loads EACH IMAGE on the page!
• If you specify a width other than the width and height of the image it will be scaled to the dimensions you specify using a crude nearest neighbor algorithm. This is useful for drawing <hr> equivalents with a 1x1 pixel black bmp or aligning text with a 1x1 pixel white .bmp (which is invisible on the screen.)

Special character and international character support

• Special characters used in HTML with a character code, &quot; for instance, are not supported by the microbrowser. For the purposes of it being a very strict XHTML parser, I suppose it throws the proper "Entity Not Defined" error, but using correct DTD's doesn't seem to make it work either. You should either avoid special characters entirely or simply use them in binary form and see if the phone will tolerate it. Further documentation would be required from Polycom in order to know for sure why this is the case.

Hints

• Page titles are prominently displayed, so choose your titles appropiately.
• Session management should be tested carefully, otherwise hitting the back key on the phone may re-submit old data.
• It is possible to simulate tables or align text or images to columns in the microbrowser through the use of the old HTML trick of using invisible images to pad whitespace. However since the browser uses a proportional font you have to know the widths of each character in order to do accurately pad text. The width of each character in the microbrowser's font is provided here along with a short description of how to use the technique: Polycom Microbrowser Character Widths

Another person's experiences

anishp anishp is is at at win-ent dot dot com com

• the polycom does not respect the maxlength or size variables for an input box
• improper pages will cause the phone to reboot or lockup
• input type of checkbox does not render
• ! in text fields will apparently cause the phone to reboot on random.
• <select name="stuff[]" multiple> does not work
• nor does a drop down select
• radio buttons do work, but when used in conjuction with PHP, some pretty funky stuff happens

---

Although specific technical information is not published by polycom, as a sidenote, the microbrowser running on the SoundPoint IP 650 renders pages much more quickly than on the 600/601, most likely due to the phone containing a more powerful CPU.

See Also

• Polycom Phones
• Polycom Soundpoint IP 600
• Polycom XML browser scripts for asterisk