Kristian Kielhofner ha scritto:
Or you can keep using the phones with SIP and use sip_notify. I think
Ciscos support it.
In my last try it was not doing it on cisco sip phones.
Sergio
___
--Bandwidth and Colocation provided by Easynews.com --
We've currently got 4 servers, and anytime we make any major
modifications to the servers, the phones have to be rebooted. We've got
about 55 cisco 7940's (which is going to steadily increase over the next
few months), does anyone know of a way to reboot the phones without
using the telnet
On Mon, 2005-12-12 at 11:36 -0600, Aaron Daniel wrote:
We've currently got 4 servers, and anytime we make any major
modifications to the servers, the phones have to be rebooted. We've got
about 55 cisco 7940's (which is going to steadily increase over the next
few months), does anyone know
Joseph wrote:
On Mon, 2005-12-12 at 11:36 -0600, Aaron Daniel wrote:
We've currently got 4 servers, and anytime we make any major
modifications to the servers, the phones have to be rebooted. We've got
about 55 cisco 7940's (which is going to steadily increase over the next
few months),
We do currently have the cisco's on their own vlan along with the
servers, but I'm told vlan hopping is trivial so that's not considered
secure... considering all you have to do is change a route on a box to
get to the vlan. And has anyone actually got sip_notify to work for the
cisco phones?
On Mon, 2005-12-12 at 16:20 -0600, Aaron Daniel wrote:
We do currently have the cisco's on their own vlan along with the
servers, but I'm told vlan hopping is trivial so that's not considered
secure... considering all you have to do is change a route on a box to
get to the vlan.
Far from
Patrick wrote:
On Mon, 2005-12-12 at 16:20 -0600, Aaron Daniel wrote:
We do currently have the cisco's on their own vlan along with the
servers, but I'm told vlan hopping is trivial so that's not considered
secure... considering all you have to do is change a route on a box to
get to the
I'm not a VLAN expert either, but there's one switch that ties the
private vlans into the public vlan, so all you have to do is add a route
from your box to the vlan over that switch, effectively hopping you onto
the vlan. Not really sure the details on it, but that's basically the
gist of
I think what the OP's managers were suggesting is that its not all that
difficult to overflow the switch forwarding table, and cause packets to
appear on a vlan where it shouldn't be. The approach has been around for
a while, and the higher quality switches now handle the table overflow
issue in
