|
|
Table Of Contents
URIs for Pressing Buttons on the Phone
URIs for Invoking Softkey Functionality
Internal URI Features
Internal uniform resource identifiers (URIs) provide access to embedded phone features such as placing calls, playing audio files, and invoking built-in object features. These sections provide details about the available internal URIs:
•
Supported URIs by Phone Model
•
•
•
Supported URIs by Phone Model
Table 3-1 lists the URIs that are supported for this release.
1. Does not support the Volume parameter for RTP Receive streams.
2. Cisco Unified IP Phone 7920 only supports one incoming and one outgoing unicast stream.
URIs for Pressing Buttons on the Phone
The Key URI allows a programmer to send an event that a key has been pressed. The system initiates the event as if the button was physically pressed.
Note that when buttons are pressed with this method, if the button is not present on the phone (hard button) or not available (softkey) when the URI is processed, the event is discarded.
Example 3-1 Key:Soft1
If the softkey set is changing and disabled while the event is being processed, the request is discarded.
Verify available softkeys by using the QA web pages that the phones web server provides to indicate the active softkey set.
Key
URI Format:
Key:nWhere
n = a Key name.
The following is a complete listing of the Key URIs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
URIs for Invoking Softkey Functionality
You can execute native softkey functionality when the phone executes a Softkey URI. The SoftKey URI allows developers to customize softkey names and layout in the Services and Directories windows while retaining the functionality that the softkeys provide.
Softkey URIs work in menu items and in softkey items in the XML objects for which they natively occur on the phone.
SoftKey
URI Format:
SoftKey:nWhere
n = one of the following softkey names:
•
•
•
•
•
•
•
•
•
•
•
Table 3-2 contains valid softkey actions for each XSI object type follow. The URI invokes the native functionality that each key possesses in the given object context.
Table 3-2 Valid Softkey Actions for CiscoIPPhoneObject Types
CiscoIPPhoneMenu
X
X
CiscoIPPhoneIconMenu
X
X
CiscoIPPhoneText
X
X
CiscoIPPhoneImage
X
X
CiscoIPPhoneGraphicMenu
X
X
CiscoIPPhoneInput
X
X1
X
X
CiscoIPPhoneDirectory
X
X
X2
X 2
1 Only when used under the Directories button.
2 The SoftKey:Dial and SoftKey:EditDial URIs can be used only for Directory objects, but the Dial:xxx and EditDial:xxx URIs can be used as the URL of any SoftKeyItem or MenuItem. For more details, see the "Miscellaneous URIs" section.
QueryStringParam URI
The QueryStringParam URI allows an application developer to collect more information from the user with less interaction. When the user performs an action with a softkey, you can either append a query string parameter to the URL of the highlighted MenuItem or append the query string parameter from the MenuItem to the URL of the softkey.
URI Format:
QueryStringParam:dWhere
d = the data to be appended to a corresponding URL.
Example 3-2 QueryStringParam URI in a CiscoIPPhoneMenu object
<CiscoIPPhoneMenu><Title>Message List</Title><Prompt>Two Messages</Prompt><MenuItem><Name>Message One</Name><URL>QueryStringParam:message=1</URL></MenuItem><MenuItem><Name>Message Two</Name><URL>queryStringParam:message=2</URL></MenuItem><SoftKeyItem><Name>Read</Name><URL>http://server/read.asp</URL></SoftkeyItem><SoftKeyItem><Name>Delete</Name><URL>http://server/delete.asp</URL></SoftkeyItem></CiscoIPPhoneMenu>Example 3-2 shows how to use the QueryStringParam URI in a
CiscoIPPhoneMenuobject. TheCiscoIPPhoneMenuobject includes two MenuItems with QueryStringParam URIs. If the user chooses the MenuItem(s) with the numeric keypad, the cursor moves to that entry, but nothing executes because the values are QueryStringParam URIs.If the user presses either custom softkey, the currently highlighted MenuItem URI value gets appended to the softkey URL that was pressed and requested from the web server.
If you highlight the first MenuItem and press the Read softkey, the phone generates the following URL:
http://server//read.asp?message=1
Example 3-3 Selecting an Item with Numeric Keypad Calls the URL
<CiscoIPPhoneMenu><Title>Message List</Title><Prompt>Two Messages</Prompt><MenuItem><Name>Messae One</Name><URL>http://server/messages.asp?message=1</URL></MenuItem><MenuItem><Name>Messae Two</Name><URL>http://server/messages.asp?message=2</URL></MenuItem><SoftKeyItem><Name>Read</Name><Position>1</Position><URL>QueryStringParam:action=read</URL></SoftKeyItem><SoftKeyItem><Name>Delete</Name><Position>2</Position><URL>QueryStringParam:action=delete</URL></SoftKeyItem></CiscoIPPhoneMenu>The Cisco Unified IP Phones allow you to implement the QueryStringParam URI in either manner although Example 3-3 is not as efficient as Example 3-2. Choose the best way to perform the action based on your applications needs.
Example 3-3 does have a slight advantage in that if the user chooses an item with the numeric keypad, the URL gets called. This would allow you to invoke some default behavior such as to read the message in the example. By highlighting the first message and pressing the Read softkey, the phone creates the following URL:
http://server/messages.asp?message=1&action=read
Using the QueryStringParam URI reduces the size of the XML objects that you generate by not having to repeat redundant portions of a URL in every MenuItem.
URIs to Control RTP Streaming
You can invoke RTP streaming via URIs in services. You can instruct the phone to transmit or receive an RTP stream with the following specifications:
•
•
•
•
The supported format of the RTP stream follows:
•
•
RTPRx
The RTPRx URI instructs the phone to receive a Unicast RTP stream or to stop receiving Unicast or Multicast RTP streams.
URI Formats:
RTPRx:i:p:vRTPRx:StopWhere
i = the IP Address from which the stream is coming.
p = the UDP port on which to receive the RTP stream. Ensure that this is an even port number within the decimal range of 20480 to 32768. If no port is specified, the phone chooses a port and returns it when initiated by a push request.
Stop = the parameter that will stop any active RTP stream from being received on channel one
v = the optional volume setting that controls the volume of stream playout. The supplied value is a percentage of the maximum volume level of the device and must be in the range 0-100. The phone converts the specified percentage into the closest device-supported volume level setting and uses it. After the initial volume level gets set and the stream starts, you can manually change the volume level as needed. If the optional volume parameter does not get included, the current volume setting on the phone gets used as the default.
RTPTx
Use the RTPTx URI to instruct the phone to transmit a Unicast RTP stream or to stop transmitting Unicast or Multicast RTP streams.
URI Formats:
RTPTx:i:pRTPTx:StopWhere
i = the IP Address to which an RTP stream is transmit ed.
p = the UDP port on which to transmit the RTP stream. Ensure that this is an even port number within the decimal range of 20480 to 32768.
Stop = the parameter that will stop any active RTP stream from being transmitted on channel one.
RTPMRx
The RTPMRx URI instructs the phone to receive a Multicast RTP
URI Format:
RTPMRx:i:p:vWhere
i = the Multicast IP Address from which to receive an RTP stream.
p = the Multicast UDP port from which to receive the RTP stream. Ensure that this is an even port number within the decimal range of 20480 to 32768.
v = the optional volume setting that controls the volume of stream playout. The supplied value is a percentage of the maximum volume level of the device and must be in the range 0-100. The phone converts the specified percentage into the closest device-supported volume level setting and uses it. After the initial volume level gets set and the stream starts, you can manually change the volume level as needed. If the optional volume parameter does not get included, the current volume setting on the phone gets used as the default.
RTPMTx
The RTPMTx URI instructs the phone to transmit a Multicast RTP stream.
URI Formats:
RTPTx:i:pWhere
i = the Multicast IP Address to which an RTP stream is transmitted.
p = the Multicast UDP port on which to transmit the RTP stream. Ensure that this is an even port number within the decimal range of 20480 to 32768.
Miscellaneous URIs
This section describes the following miscellaneous URIs:
•
•
•
•
Init
The Init URI allows an application to initialize a feature or data with the argument that is passed with the URI.
URI Format:
Init:oWhere
o = the Object name.
Valid object name:
CallHistory—When the phone encounters an Init:CallHistory URI, it clears the internal call history logs that are stored in the phone. This action initializes Missed Calls, Received Calls, and Placed Calls.
Dial
The Dial URI initiates a new call to a specified number. The Dial URI invokes when it is contained in a menu item, the menu item is highlighted, and the device is taken off hook.
Activate the Dial URI by one of the following:
•
•
•
•
•
•
URI Format:
Dial:nWhere
n = the number dialed (such as Dial:1000).
EditDial
The EditDial URI initiates a new call to a specified number. The EditDial URI invokes when it is contained in a menu item, the menu item is highlighted, and the device is taken off hook.
Activate the EditDial URI by one of the following:
•
•
•
•
•
•
URI Format:
EditDial:nWhere
n = the number dialed (such as EditDial:1000).
Play
The Play URI downloads an audio file from the TFTP server and plays through the phone speaker. This same mechanism also plays ring files, and the format of the files is the same. You could use the Play URI to play files that are in the Ringlist.xml or those that are not. If the phone is equipped with an MWI light, it will be flashing while the audio file is playing, providing a visual alert as well.
If you want to achieve a unique audible notification, use a file that is not available from the Ringlist.xml.
URI Format:
Play:fWhere
f = the filename of a raw audio file in the TFTP path (such as Play:Classic2.raw).
Posted: Wed Jul 26 09:51:29 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.