<div dir="ltr"><div>Thank you for taking the time to respond Tim.<br></div><div><br></div><div>You have provided me with a clearer insight into the passage, and I am now in agreement with your explanation.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 18, 2019 at 10:29 AM Tim Smith <<a href="mailto:tim.smith@enject.com.au">tim.smith@enject.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-AU">
<div class="gmail-m_6265843994432170830WordSection1">
<p class="MsoNormal"><span>This looks to be specific to re-broadcasting (which I haven’t had the pleasure of playing with yet)<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Looking at the diagram in there. I assume you configure a new source with a multicast address on your MOH server.<u></u><u></u></span></p>
<p class="MsoNormal"><span>If it’s set to re-broadcast, it’ll be looking to capture the input stream from that address.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Is it just saying since your MOH server is receiving MMOH on say <a href="http://239.1.1.1:16384" target="_blank">239.1.1.1:16384</a><u></u><u></u></span></p>
<p class="MsoNormal"><span>(And would then re-broadcast this as Unicast where required)<u></u><u></u></span></p>
<p class="MsoNormal"><span>It won’t send any multicast on that same address<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>But you can configure a multicast address – on that source – which means it re-broadcasts the original stream as multicast on a new multicast address as well.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>MoH server for re-broadcasting + External Multicast source must be on same LAN (or at least have multicast routing connectivity between them) for the rebroadcasting – so if your server is receiving
on one address, you wouldn’t want to be sending out on the same address.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>That’s the way I read it which I think makes sense to me.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Cheers,<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Tim<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>>
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Thursday, 19 September 2019 1:00 AM<br>
<b>To:</b> Cisco VoIP Group <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> [cisco-voip] Multicast MOH (MMOH) SRND Question<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">I was helping someone troubleshoot a MMOH issue and what was happening was that CUCM audio source, MOH Server, and MRG were all setup to do MMOH. There was also a hardware MOH device on the network, which was sending MMOH on the same IP
address (239.1.1.1) as the CUCM MOH Server.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">When I pointed out that this would be a problem, I was shown the following statement from the SRND:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><i>"If the multicast MoH server and the audio source are configured with the same multicast group address, when Phone B is placed on hold, it will receive the multicast RTP audio stream (E) from the original multicast stream (B) broadcast
by the SRST router. In this case the MoH server does not send the audio because it is aware that the destination multicast IP address group is the same as the external audio source multicast stream (B) broadcast by the SRST router."</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Source: <a href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/media.html#pgfId-1393039" target="_blank">https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/media.html#pgfId-1393039</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Now, a TAC case was opened, and TAC said it should have done what the SRND is stating, but I am doubtful. I think the wording in the SRND is poor, and that perhaps it only pertains to the Fixed source of 51, and not just any source you
create.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">So, I'm asking for your understanding and knowledge of how this works, to clarify this aspect of MMOH for me. Please read the entire section of the SRND linked, because context is important here. I only provided a snippet.<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote></div>