/mcpgo directly to the call handler's greeting, bypassing transfer). If you want to go to a different call handler's greeting, set RouteTargetCallHandlerObjectId to it. <RoutingRule> <RouteAction>2</RouteAction> <RouteTargetConversation>PHGreeting</RouteTargetConversation> <RouteTargetHandlerObjectId>aab5eab2-38f7-4231-a3be-bf2a8fde820c</RouteTargetHandlerObjectId> </RoutingRule> Go to an Interview Handler PUT https://<server>/vmrest/handlers/callhandlers/<callhandlerobjectid>/menuentries/<key> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <MenuEntry> <Action>2</Action> <TargetConversation>PHInterview</TargetConversation> <TargetHandlerObjectId>interview handler object id</TargetHandlerObjectId> </MenuEntry> The TargetConversation should be set to PHInterview and the TargetHandlerObjectId is the object ID of the interview handler that you want to the caller input key to go to. Go to a Directory Handler PUT https://<server>/vmrest/handlers/callhandlers/<callhandlerobjectid>/menuentries/<key> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <MenuEntry> <Action>2</Action> <TargetConversation>AD</TargetConversation> <TargetHandlerObjectId>object id of directory handler</TargetHandlerObjectId> </MenuEntry> The TargetConversation should be set to AD and the TargetHandlerObjectId is the object ID of the directory handler you want to the caller input key to go to. Go to a Specific Conversation The following Routing Rule will go to (Action=2) the BroadcastMessageAdministrator Conversation. Note that RouteTargetHandlerObjectId is ignored if the RouteTargetConversation is anything other than PHTransfer, PHGreeting, PHInterview, or AD. <RoutingRule> <RouteAction>2</RouteAction> <RouteTargetConversation>BroadcastMessageAdministrator</RouteTargetConversation> </RoutingRule> Routing Rule Condition Examples Routing Rule Conditions are not as complicated as Routing Rules, but care should still be taken when creating or modifying them. The fields Parameter, Operator, and OperandValue are used to specify the conditions. This list of examples covers all of the Routing Rule Conditions that can be configured by using Cisco Unity Connection Administration (CUCA). Creating a different type of Routing Rule Condition by using CUPI is likely to yield a Routing Rule Condition that will not display properly in CUCA, and it also may not operate as expected when Connection tries to match a call. Cisco Unity Connection Provisioning Interface (CUPI) API 575 Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing Go to an Interview Handler