
XML Profile for Configuration 7 - 15
<Menu ID="14" name="DeskCallOnHold" title="Options">
<entry ID="1" value="HangUp:S:L:PhoneHangUp"/>
<entry ID="2" value="Transfer:M:L:TransferPhoneBook"/>
<entry ID="3" value="UnHold:S:L:PhoneResume"/>
<entry ID="4" value="Applications:M:L:Applications"/>
</Menu>
<Menu ID="15" name="AppCallOnHold" title="Options">
<entry ID="1" value="HangUp:S:L:PhoneHangUp"/>
<entry ID="2" value="Transfer:M:L:TransferPhoneBook"/>
<entry ID="3" value="UnHold:S:L:PhoneResume"/>
</Menu>
<Menu ID="16" name="AECForHeadset" title="AEC HS">
<entry ID="1" value="Enable:S:L:SetAEC:1"/>
<entry ID="2" value="Disable:S:L:SetAEC:0"/>
</Menu>
</Menus>
Menu Elements
There can be any number of <Menu> elements contained in the <Menus> element. Each <Menu> can contain any
number of <entry> elements. Each <Menu> element should be assigned sequential IDs. The <Menu> element
name is the term by which the menu is referred to from another menu entry. The title is the display name in the title
bar at the top of the CA50 display.
Menu entries should be listed in the order they are to display; their IDs should also be sequential. The value is
interpreted as follows: 'Entry Text:Opt1:Opt2:data'
where:
'Entry Text' - is what gets displayed as the menu item to be selected
Opt1 - is M or S meaning (M)enu or (S)pecial option
Opt2 - is S or L meaning (S)erver or (L)ocal
data depends upon Opt1 and Opt2 as follows:
M:L:Menu Name - Specifies name of another locally stored static menu.
M:S:Menu.xml:URI - specifies name of dynamic menu and Web service URI to retrieve this dynamic
menu which is cached locally.
S:L:Command[:options] - specifies an agent recognized action with possible options.
S:S:URL - URL to open with the UCA client application browser.
NOTE
URIs or URLs with GET parameters need to use the "&" instead of just the "&" due to XML
processing.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......