configure Multicast MOH from the Branch Router Flash.

Multicast MOH from the branch router flash is a feature for multisite deployment
s that
use centralized call processing.
The feature works only with multicast MOH and is based on MOH capabilities of Ci
sco
Unified SRST. The Cisco IOS SRST gateway is configured for multicast MOH and
continuously sends a MOH stream, regardless of its SRST mode (standby or fallbac
k
mode).
Neither CUCM nor the remote IP Phones are aware that the SRST gateway is involve
d.
To them it appears as though a multicast MOH stream has been generated by the
CUCM MOH server and received by the remote IP Phones.
Therefore, the remote Cisco IP Phones are configured to use the centralized CUCM
MOH server as their MOH source. The CUCM MOH server is configured for multicast
MOH (mandatory), and the max-hops value in the MOH server configuration is set t
o 1
for the affected audio sources. The max-hops parameter specifies the Time to Liv
e
(TTL) value that is used in the IP header of the RTP packets. The CUCM MOH serve
r
and the Cisco IOS SRST gateway located at the remote site have to use the same
multicast address and port number for their streams. This way, MOH packets gener
ated
by the CUCM MOH server at the central site are dropped by the central-site route
r
because the TTL has been exceeded. As a consequence, the MOH packets do not cros
s
the IP WAN. The SRST gateway permanently generates a multicast MOH stream with
an identical multicast IP address and port number so that the Cisco IP Phones si
mply
listen to this stream as it appears to be coming from the CUCM MOH server.
Instead of setting the max-hops parameter for MOH packets to 1, you can use one
of the
following methods:
* Configure an access control list (ACL) on the WAN interface at the central sit
e: This
prevents packets that are destined for the multicast group address or addresses
from
being sent out the interface.
* Disable multicast routing on the WAN interface: Do not configure multicast rou
ting
on the WAN interface to ensure that multicast streams are not forwarded into the
WAN.
When using multicast MOH from branch router flash, G.711 has to be enabled betwe
en
the CUCM MOH server and the remote Cisco IP Phones. This is necessary because th
e
branch SRST MOH feature supports only G.711. Therefore, the stream that is set u
p by
CUCM in the signaling messages also has to be G.711. Because the packets are not
sent
across the WAN, configuring the high-bandwidth G.711 codec is no problem as long
as

it is enabled only for MOH. All other audio streams (such as calls between phone
s) that
are sent over the WAN should use the low-bandwidth G.729 codec.
A Cisco Unified SRST license is required regardless of whether the SRST function
ality
will actually be used. The license is required because the configuration for str
eaming
multicast MOH from branch router flash is done in SRST configuration mode. Also,
even if SRST functionality will not be used, at least one max-ephones for every
Cisco
IP Phone supported and at least one max-dn for every directory number (dn) on al
l
phones must be configured.
I hope this information helps clarify how this works and as explained before to
get this
configured
It will be necessary to open a new case with our gateway team (multi services).

Really this needs to be setup across the WAN or on a network topology

where the multicast stream from the CallManager cannot possibly reach
the router.
The router's configuration is missing:
1. ip multicast-routing
2. ip pim statements under the interfaces, I typically used "ip pim
sparse-dense" but what you select ultimately depends on your network and
multicast configuration.
3. A loopback interface. This is required in order for multicast moh
audio to be heard on the gateway during regular operation. For example:
interface loopback 0
no shutdown
ip address 1.1.1.1 255.255.255.0 <---this doesn't have to be a valid
or routable address
ip pim sparse-dense
!
4. The route statement on the multicast command under
call-manager-fallback:
call-manager-fallback
multicast moh 239.1.1.1 port 16384 route 10.128.51.5 1.1.1.1
!
Note, I've included the fastethernet's IP address and also the address
from the loopback interface.