Appropo nothing at all - I'm just an advocate of "out of the box" thinking...

I've been looking closely at what can be achieved using Alarm Detection/Condition/Reaction within SCS/SCI and it came to me that you [i]could [/i] control certain aspects of your Genesys environment remotely - by phone (or email - or any other interaction method)...
1. There are settings you can use within [i]Alarm Detection [/i] that can detect entries in any Genesys Application Log File, including the potential to recognize a specific attached data item (KVP) in the TServer Log... [i]<can you see where this is going...?

>[/i]
2. There are [i]Alarm Conditions [/i] you can set on a particular Application instance....
3. There are [i]Alarm Reactions [/i] which can invoke all sorts of things - including Application Setting chnages, OS commands and other types of on-line and ff-line scripts (SNMP)...
So, it should be feasible to;
4. Create an IVR Script or Routing Strategy loaded on an external DN which, given the right User input(s) would create a specific User Data (KVP) entry in a TServer Log File.
5. Create an Alarm Detection based on the TServer Log File User Data (KVP) item.
6. Create an Alarm Reaction to Load and Unload various items, including Routing Strategies and changes to Sub-Routines.
7. Call the external DN an enter digits (via a Dialogic or IVR) to apply the KVP within the TServer Log File which, with [i]Alarm Detection [/i] could enable a specific [i]Alarm Reaction [/i] to stop/start/change setitngs within the Genesys environment.
Like I said - appropo nothing but the concept is quite interesting, if you need to make a remote change (frequently) on the fly and you don't have immediate access to your environment... Perhaps if you are "on-call" and it is your responsibility to invoke operational/reactive changes to your Genesys Applications or Routing on the fly, from home...

Any thoughts on this...? Or have I finally gone mad....?

Tony