<HTML>
<HEAD>
<TITLE>Re: [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>You should be able to upload any file to the TFTP server on a CUCM from the OS Admin pages. Just make sure you restart the TFTP service after doing so. Not sure if that actually helps or hinders your current dilemma. <BR>
<BR>
Chris Ward <BR>
<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"><B>From: </B>Lelio Fulgenzi <<a href="lelio@uoguelph.ca">lelio@uoguelph.ca</a>><BR>
<B>Date: </B>Tue, 16 Sep 2008 15:52:04 -0400<BR>
<B>To: </B>Scott Voll <<a href="svoll.voip@gmail.com">svoll.voip@gmail.com</a>>, "<a href="cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><BR>
<B>Subject: </B>Re: [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'><FONT FACE="Arial">I would go with a special VLAN for the berbee speakers. Especially, from what I remember, they can't do CDP and/or negotiate a voice vlan, so those network ports can easily be used by a PC (if they can reach) and hack your system. hack! hack.<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
<BR>
Lelio<BR>
--------------------------------------------------------------------------------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <BR>
...seen on a Geek Squad patch cord: "While it is the same length, this 7' crossover cable<BR>
is not regulation issue for most competitive Manhattan double dutch leagues.<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE='font-size:11pt'><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
----- Original Message ----- <BR>
<BR>
<B>From:</B> Scott Voll <<a href="mailto:svoll.voip@gmail.com">mailto:svoll.voip@gmail.com</a>> <BR>
<BR>
<B>To:</B> <a href="cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a> <BR>
<BR>
<B>Sent:</B> Tuesday, September 16, 2008 3:48 PM<BR>
<BR>
<B>Subject:</B> [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan<BR>
<BR>
<BR>
<BR>
<BR>
Is anyone out in internet land using Berbee IP speakers?<BR>
<BR>
<BR>
<BR>
are you also running CM 6.x?<BR>
<BR>
<BR>
<BR>
did you upgrade to SLP?<BR>
<BR>
<BR>
<BR>
Is it going across the WAN?<BR>
<BR>
<BR>
<BR>
Does it work?<BR>
<BR>
<BR>
<BR>
I have CM 6.1 and have upgraded the IP speakers to SLP since you can no longer put non-cisco files on the CM TFTP (thanks cisco). So to get around this Berbee has you upgrade to SLP (which is a Multicast 239.255.255.253 <<a href="http://239.255.255.253">http://239.255.255.253</a>> ). So it tries TFTP fails and goes to SLP. Problem I'm having is that both the IP Speaker and IC both use the SLP Multicast address so my Cat 6509 doesn't want to multicast back to an address that is sourcing it. I'm just curious if I'm the only one?<BR>
<BR>
<BR>
<BR>
I think I'm about to setup a new vlan just for IP speakers with it's own TFTP (IC) and get it working this way. I can use SSMulticast but also an admin issue.<BR>
<BR>
<BR>
<BR>
TIA<BR>
<BR>
<BR>
<BR>
Scott<BR>
<BR>
<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="100%"> <BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
<a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><BR>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></FONT></SPAN></BLOCKQUOTE><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
cisco-voip mailing list<BR>
<a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><BR>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>