[cisco-voip] Multicast SRST, branch router, no moh for PSTN caller

[CarlosOrtiz at bayviewfinancial.com]

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). 

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 
!!!

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. 

Carlos



Robert Kulagowski <bob at smalltime.com> 
Sent by: cisco-voip-bounces at puck.nether.net
06/06/2007 10:16 AM

To
Ryan Ratliff <rratliff at cisco.com>
cc
cisco-voip at puck.nether.net
Subject
Re: [cisco-voip] Multicast SRST, branch router, no moh for PSTN caller






Ryan Ratliff wrote:
> I'm pretty sure CM will increment the port/IP address of the MOH 
> stream going from ulaw to alaw.   Since you can only stream to one 
> multicast IP address/port from the router you need to make sure every 
> endpoint that needs to listen to that MOH source is using the same 
> codec.

I know for a fact that it does; I just ran into this issue in Sydney, 
where I put a alaw file on the router and discovered that my MOH didn't 
work.  When I looked at sh ccm-manager music-on-hold I realized that it 
was coming from 239.1.1.2 port 16384 instead of 239.1.1.1 and had to 
update my config.

However, this configuration is brittle in that 1)  I can't put 239.1.1.2 
on more than one MOH source on CM because CM then complains that the IP 
is already in use and/or 2)  I don't think that I can wildcard the IP 
address (but keep a fixed port on the router multicast moh config), so 
if a CM goes bye-bye and the phones register to another CM this is going 
to fail, correct?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070606/47f7a753/attachment-0001.html