Polycom 3725-49106-001 Rev A User Manual

Page of 92
Web Application for Polycom Phones 
UC Software 5.0.0
 
Polycom, Inc. 
20 
The following are ways to execute an internal URI action: 
  If the file sent to the phone contains only internal URI actions, which you can send as Data Push, 
ensure the file content type is application/x-com-polycom-spipx. Each internal URI action 
must be separated by a newline and the execution is performed in order from the top down. 
  If an XHTML file includes internal URI, you need to define and execute 
the file’s anchor tags in the 
HREF attribute. For example, <a href=”Key:Setup”>Menu</a>. When you select the anchor, 
the action is processed and executed. 
  Using the PolyUri() JavaScript function, apply one of the following soft key actions in anchor tags:  
 
SoftKey:Home 
 
SoftKey:Back 
 
SoftKey:Exit 
 
SoftKey:Cancel 
 
SoftKey:Refresh 
See also 
. 
 
 
Note: Executing Internal URIs 
Internal URI actions contained in a file with content type application/x-com-polycom-spipx 
can be executed only through a URL push. 
 
Use the format ActionType:Action when configuring the internal URIs where: 
  ActionType is a type of key or action to execute: Key, Soft key, Tel, or Play. 
  Action is the name of the action to be executed. 
The supported internal URIs are described in the following table. 
Table 6: Supported Internal URIs 
Action Type 
Action 
Key 
Line1 to Number of Lines supported by the Phone 
model., DialPad0 to DialPad9, Softkey1 to Softkey5, 
DialPadStar, DialPadPound, VolDown, VolUp, Headset, 
Handsfree, MicMute, Menu, Messages, Applications, 
Directories, Setup, ArrowUp, ArrowDown, ArrowLeft, 
ArrowRight, Backspace, DoNotDisturb, Select, 
Conference, Transfer, Redial, Hold, Status, Call List 
The Key URIs send the key press event to the phone. The phone processes this event as if the button had been 
physically pressed. 
SoftKey
1
 
Back, Cancel, Exit, Home, Refresh, Reset, Submit, 
Fetch 
The Soft Key URIs send the soft key press event to the phone. The phone processes this event as if the 
associated soft key had been physically pressed. These URIs function when the interactive microbrowser is on the 
screen.