/mcpOn the Search Custom Recording page, select the custom recording that you want to delete. Select Delete Selected and OK to confirm deletion. Default Automated Attendant Behavior The following example uses the default Unity Connection automated attendant configuration to illustrate a call flow through various call management elements. It illustrates some of the default behavior that you can expect if you have not changed the call management configuration after installing Unity Connection. Consider an outside caller that does not have a Unity Connection mailbox dials the main phone number in Unity Connection at 9:00 a.m. on a Monday morning. The following steps describes the call flow: 1. Information from the phone system indicates that the call is a direct call from an outside caller. Unity Connection checks the call routing rules for a rule that matches the call. The Direct routing rules table contains two entries: Attempt Sign In and Opening Greeting. For the Attempt Sign-In rule, Unity Connection attempts to match the caller phone number with the extension or alternate extension of a Unity Connection user. When this fails, Unity Connection tries the next routing rule, the Opening Greeting rule. 2. The Opening Greeting call routing rule matches any incoming call at any time of day. It is configured to attempt to route the call to the Opening Greeting call handler. 3. Unity Connection checks the transfer option settings for the Opening Greeting call handler. Because the call came in during the Weekdays active schedule, the standard transfer options apply. These specify to send the call to the greeting for this call handler. (Note that if the Opening Greeting call routing rule had been configured to send the call to the greeting for the Opening Greeting call handler rather than attempting to transfer to it, this step would be skipped). 4. Because the call came in during the Weekdays active schedule from a phone number that did not match an internal Unity Connection user, Unity Connection plays the standard greeting for the call handler: “Hello: Cisco Unity Connection Messaging System. From a touchtone phone you may dial an extension at any time. For a directory of extensions, press 4. Otherwise, please hold for an operator.” 5. While the greeting plays, as the greeting indicates, the caller can enter digits to reach a user extension. The caller input settings on the Opening Greeting call handler also define several one-key dialing actions that can be taken—for example, when the caller presses key 4, Unity Connection is configured to send the call to the System Directory Handler if no other keys are pressed within the time configured to wait for additional digits. 6. If no digits are entered, Unity Connection proceeds with the after greeting action for the Standard greeting on this call handler, which is configured to attempt to transfer the call to the Operator call handler. 7. The Operator call handler is also configured for the Weekdays active schedule, and once again, Unity Connection checks the standard transfer options for the call handler, which specify to transfer to the call handler greeting. The greeting plays: “Sorry, the operator is not available.” 8. The after greeting action for this greeting directs Unity Connection to take a message. The message settings for this call handler specify that the Operator user receives the message, and that after the caller leaves the message, Unity Connection should hang up. System Administration Guide 112 Call Management Default Automated Attendant Behavior