<br><font size=2 face="sans-serif">I think your redundancy assumptions
are correct. The whole setup for this multicast MOH is a little
tricky. It would be great if Cisco could make it a bit easier. I
actually came into an existing environment where they had about 8 audio
sources enabled for multicast. I created a dummy audio file for this
purpose and disabled all the others that were multicasting. Even
though all other audio sources were not multicasting and my audio file
was audio source 2 the ulaw stream was being sent from 239.1.1.5 and not
239.1.1.1 as anticipated.(base of 239.1.1.1 on MOH server). </font>
<br>
<br><font size=2 face="sans-serif">After performing some maintenance about
a week ago and resetting all the CM servers guess what?? The multicast
stream address changed to 239.1.1.1 !!!</font>
<br>
<br><font size=2 face="sans-serif">I had to go back to about 8 gateways
and change the multicast address to get them working again. I'm guessing
that the audio 1 source file was previously multicast enabled and the changes
didn't take affect until the reboot. </font>
<br>
<br><font size=2 face="sans-serif">Carlos</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Robert Kulagowski <bob@smalltime.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">06/06/2007 10:16 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Ryan Ratliff <rratliff@cisco.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">cisco-voip@puck.nether.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] Multicast SRST, branch
router, no moh for PSTN caller</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Ryan Ratliff wrote:<br>
> I'm pretty sure CM will increment the port/IP address of the MOH <br>
> stream going from ulaw to alaw. Since you can only stream to
one <br>
> multicast IP address/port from the router you need to make sure every
<br>
> endpoint that needs to listen to that MOH source is using the same
<br>
> codec.<br>
<br>
I know for a fact that it does; I just ran into this issue in Sydney, <br>
where I put a alaw file on the router and discovered that my MOH didn't
<br>
work. When I looked at sh ccm-manager music-on-hold I realized that
it <br>
was coming from 239.1.1.2 port 16384 instead of 239.1.1.1 and had to <br>
update my config.<br>
<br>
However, this configuration is brittle in that 1) I can't put 239.1.1.2
<br>
on more than one MOH source on CM because CM then complains that the IP
<br>
is already in use and/or 2) I don't think that I can wildcard the
IP <br>
address (but keep a fixed port on the router multicast moh config), so
<br>
if a CM goes bye-bye and the phones register to another CM this is going
<br>
to fail, correct?<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</tt></font>
<br>