<br><font size=2 face="sans-serif">Thanks for the tips!</font>
<br>
<br><font size=2 face="sans-serif">I can see that the phone is sending
the correct 239.1.1.1 address and port. The internal phones are now
hearing the music but the quality is beyond bad. I see on the same
page that the sender codec is g.722 and the recr codec is g.711u. Could
this be the issue?</font>
<br><font size=2 face="sans-serif"><br>
Steve Siltman<br>
Assurant Corporate Technology<br>
Senior Network Engineer - Cisco CCVP<br>
Work: 651-361-4752<br>
Cell: 651-336-5563<br>
steve.siltman@assurant.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Ryan Ratliff <rratliff@cisco.com></b>
</font>
<p><font size=1 face="sans-serif">2009-12-08 20:11</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">steve.siltman@assurant.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] MOH from Router Flash
between internal callers</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>I don't recall this ever not being supported, in fact
the whole point of using the router flash for MOH was to get it working
to phones and PSTN gateways at the remote site.</font>
<br>
<br><font size=3>It is most definitely supported and there are quite a
few people that use it with no issues. The reason you were asked
for traces is because if the configuration looks good, then the traces
are the best way to confirm what MOH audio source/server CUCM is selecting
and why the multicast address the phone is told to listen to doesn't line
up with what the router is sending.</font>
<br>
<br><font size=3>You are correct and it is fairly straight forward. One
slight correction is that it is not the phone initiating the hold but rather
the CUCM server that instructs the held party to listen to the MOH stream.
The address used will be a combination of the user hold audio source
configured on the holding phone and the MRGL of the held phone.</font>
<br>
<br><font size=3>You can also find out the address the phone is being told
to listen to by putting the phone on hold, and then pointing a web browser
at the held phone's IP address. Click on the Streaming Statistics
links until you see the multicast address. If everything is configured
correctly then this address and port will match that configured on the
SRST router. If it doesn't match, then your CUCM configuration is
not correct. If it does match and the phone is still hearing silence
on hold then you need to troubleshoot the layer 2 and 3 multicast between
the SRST router and the IP phone.</font>
<br>
<br><font size=3>-Ryan</font>
<br>
<br><font size=3>On Dec 8, 2009, at 4:22 PM, </font><a href=mailto:steve.siltman@assurant.com><font size=3 color=blue><u>steve.siltman@assurant.com</u></font></a><font size=3>
wrote:</font>
<br><font size=3><br>
</font><font size=2 face="sans-serif"><br>
Has anyone been able to get this too work? I turned on Multicast
within the internal network at this remote site and I'm unable to get the
phones to hear the MOH between two internal Cisco IP Phones. Years
ago, I read that this wasn't possible but was hoping this was resolved
in later versions. We are running v7 Call Manager with 12.4.24 router
code. MOH works fine to external customers. It seems fairly
straight forward as the one Cisco IP phone issues the Hold and sends the
multicast ip address to the other phone. I'm not sure why the other
phone doesn't pick up on the stream. Grr</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
If this isn't supported then I'll have to allow MOH across the WAN and
forget about using the routers flash outside of SRST.</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
I've got a ticket open with Cisco and they verified the configuration and
have asked for trace files. Either this TAC person doesn't know it
isn't supported or something has changed since my Cisco Voice Gateways
book was printed in 2006.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Thanks,</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
-Steve</font><font size=3> <br>
This e-mail message and all attachments transmitted with it may contain
legally privileged and/or confidential information intended solely for
the use of the addressee(s). If the reader of this message is not the intended
recipient, you are hereby notified that any reading, dissemination, distribution,
copying, forwarding or other use of this message or its attachments is
strictly prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all copies and
backups thereof. Thank you._______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net"><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3><br>
https://puck.nether.net/mailman/listinfo/cisco-voip</font>
<br>
<br>
This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.