All of the elements are using the same Exit softkey. The difference is how they are used in an application, specifically with regards to the content expiration header.
The phone will push each page onto it's history stack, similar to how browsers work, except that the phone does not expire pages, it only considers the expiration date of a page when it was initially requested.
If you include something like the following:
Response.Expires = -1;
on each page, then any time the Exit softkey is pressed, the user will be returned to the Services menu (if the Service was called from the Services menu).
Excellent, thanks for that. The thought never even crossed my mind. Must admit, I don't remember seeing that document you linked too. Perhaps I did, but forgot... I always try and read all the documentation three times before posting :).
Anyway, I should get time to try this on Thursday, but looks like it should work fine.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...