Callmanager Express > B-ACD and Tcl Call-Handling Applications > Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant Service (B-ACD)
Copy and paste code into notepad from approximately 3/4 the way down the page. This will configure the “aa” service as well as the “queue”. Include the voip dial-peer for local dialing from CME phones, otherwise reference the pots dial-peer for inbound PSTN call handling.
I sometimes get confused as to which order to have the channel selection when configuring a PRI, be it MGCP 6608 or otherwise.
TOP_DOWN (first to last) or BOTTOM_UP (last to first). If you are not sure which port order to use, choose TOP_DOWN.
ASCENDING order (channel 1 to channel 23) or DESCENDING order (channel 23 to channel 1).
TOP_DOWN = ASCENDING
BOTTOM_UP = DESCENDING
To minimize glare conditions on the Telco circuit it is almost always recommended to configure the gateway opposite of what the telco is passing.
To control multicast MoH, be sure on what is required. Determine whether multicast MoH is required from the Callmanager MoH servers to a remote branch or instead multicast MoH from the remote branch’s flash. This will determine what number you set the “hops” setting to under the MoH server definition under Callmanager. For streaming locally from remote branch flash, the hop count should be set to 1. If streaming from Callmanager in the HQ, the hop count should be set higher, such as 4.
Additionally, use separate regions/device pools to control what codec is used for the MoH if streaming from Callmanager. If streaming locally using say G.729, ensure that the correct multicast IP address or port is specified in the local “call-manager-fallback” configuration.
Ie. If using G.729 for mcast MoH from the remote branch’s flash, the IP address would be 239.1.1.3 port 16384, or if using Port increments, 239.1.1.1 port 16386.
When integrating Unity with both Callmanager and Callmanager Express (Two Clusters under one Callmanager Configuration in the UTIM), it is known that MWI broadcasts go out on both clusters, however it is undetermined on how you can control regular outdial and avoid outdial to the wrong cluster.