[cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan
Chris Ward
chrward at cisco.com
Tue Sep 16 16:31:14 EDT 2008
An issue like that would need a TAC case for troubleshooting. But we use the
upload feature for uploading background images and ringtones, so we know
that non-cisco files can be posted there.
What method are you using to upload TFTP files?
Chris Ward
Cisco Systems Inc.
Customer Support Engineer
Unified Communication Infrastructure
Boxborough, MA
9:00am - 6:00pm Eastern
978-936-0217
chrward at cisco.com
From: Scott Voll <svoll.voip at gmail.com>
Date: Tue, 16 Sep 2008 13:27:53 -0700
To: Chris Ward <chrward at cisco.com>
Cc: Lelio Fulgenzi <lelio at uoguelph.ca>, "cisco-voip at puck-nether.net"
<cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan
This would work great if it actually worked. I upload the file to the CM
and then restart the TFTP service go back and search for the file and it's
gone.
Berbee said that's the reason they went to SLP is because Cisco does NOT
allow none cisco files on the TFTP server.
if I'm doing something wrong....... PLEASE give me instructions on how to do
it.
Thanks
Scott
On Tue, Sep 16, 2008 at 1:02 PM, Chris Ward <chrward at cisco.com> wrote:
> 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.
>
> Chris Ward
>
>
>
> From: Lelio Fulgenzi <lelio at uoguelph.ca <http://lelio@uoguelph.ca> >
> Date: Tue, 16 Sep 2008 15:52:04 -0400
> To: Scott Voll <svoll.voip at gmail.com <http://svoll.voip@gmail.com> >,
> "cisco-voip at puck-nether.net <http://cisco-voip@puck-nether.net> "
> <cisco-voip at puck.nether.net <http://cisco-voip@puck.nether.net> >
> Subject: Re: [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan
>
> 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.
>
>
> Lelio
> ------------------------------------------------------------------------------
> --
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ...seen on a Geek Squad patch cord: "While it is the same length, this 7'
> crossover cable
> is not regulation issue for most competitive Manhattan double dutch leagues.
>>
>> ----- Original Message -----
>>
>> From: Scott Voll <mailto:svoll.voip at gmail.com>
>>
>> To: cisco-voip at puck-nether.net <http://cisco-voip@puck-nether.net>
>>
>> Sent: Tuesday, September 16, 2008 3:48 PM
>>
>> Subject: [cisco-voip] SLP -- Multicast? Berbee IP Speakers across wan
>>
>>
>>
>>
>> Is anyone out in internet land using Berbee IP speakers?
>>
>>
>>
>> are you also running CM 6.x?
>>
>>
>>
>> did you upgrade to SLP?
>>
>>
>>
>> Is it going across the WAN?
>>
>>
>>
>> Does it work?
>>
>>
>>
>> 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
>> <http://239.255.255.253/> <http://239.255.255.253 <http://239.255.255.253/>
>> > ). 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?
>>
>>
>>
>>
>> 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.
>>
>>
>>
>> TIA
>>
>>
>>
>> Scott
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net <http://cisco-voip@puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <http://cisco-voip@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/20080916/80f1004b/attachment.html>
More information about the cisco-voip
mailing list