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 softkey tags must exist inside the
<form>
tag that
they are to act upon.
•Indexes need not be sequential. A missing index will result in an empty
space, no soft key displayed.
•An index greater than eight is ignored.
•By default, a Back soft key is placed on the graphic display (even if one is
not defined).
For example, to create a simple page:
<html>
<p> Hello World! </p><br/>
<softkey index="1" label="Home" action="SoftKey:Home" />
<softkey index="2" label="Refresh" action="SoftKey:Refresh" />
<softkey index="4" label="Exit" action="SoftKey:Exit" />
<softkey index="3" label="Back" action="SoftKey:Back" />
</html>
Telephone Integration URIs
Internal URIs provide the interface to execute predefined actions on the phone.
These actions are similar to the manual execution of key presses by the user.
There are three ways to execute an internal URI action:
•If the file sent to the phone contains only internal URI actions, the file
content type must be “
application/x-com-polycom-spipx
”. The
internal URIs are executed in ascending order.
•If an XHTML file will include internal URI, they must be defined in (and
executed from) anchor tags, in the
href
attribute (for example,
<a
hef=”Key:Setup”>Menu</a>
). When the user selects the anchor, the
action is processed and executed.
•Refer to Programmable Soft Keys on page 2-14.
Note The soft keys from the “Browser Active” and “Edit Active” soft key groups override
any custom soft keys defined in the current XHTML.
The soft keys from the “Browser Stop” soft key group appear if no custom soft keys
are defined.
The exact soft keys that appear vary between the SoundPoint IP and SoundStation
IP phones.