Figured out #2 as well. Its a bit more complicated. You will need to the object id of the call handler for the user whose caller input key you want to change. Every user has a call handler, and if you are looking at the user data returned from a GET, its under the tag <CallHandlerObjectId>. This is the object id of the user's call handler.
So now you just do the following PUT...
PUT https://<server>/vmrest/handlers/callhandlers/<callhandlerobjectid>/menuentries/4
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<MenuEntry>
<Action>2</Action>
<TargetConversation>PHTransfer</TargetConversation>
<TargetHandlerObjectId>object id of target call handler goes here</TargetHandlerObjectId>
</MenuEntry>
What does all this mean? Good question.
The Action is a custom type that is set to a different value depending on what you want the caller input key to do. The Action type is used in lots of places, so its not the case that all possible values of the Action type are valid in certain areas. Here is a list of possible values and what they mean...
0: Ignore - no action taken.
1: Hangup - the call is immediately terminated.
2: Goto - go to an object such as a call handler, directory handler or interview handler.
3: Error - play the error greeting.
4: Take a message.
5: Skip greeting.
6: RestartGreeting - restart greeting on current handler
7: Transfer to Alternate Contact Number
8: Route From Next Call Routing Rule
The TargetConversation should be set to PHTransfer if you want to transfer to the call handler in question. If you just want to have the call go directly the call handlers greeting, set it to PHGreeting instead.
Then lastly, the TargetHandlerObjectId is the call handler object id of the call handler that you want the 4 key to take the caller to.
Hopefully that helps.
-kelro
CUC Forums 
