On Thu, May 25, 2006 at 04:42:57PM -0600, Colin Anderson wrote:
CA> I looked long and hard at the LAN and it was basically narrowed down to the
CA> switches. In this smaller install, several cheapo Dlink ($30) switches
What switches you mean? How they named?
--
JID: [EMAIL PROTECTED]
ICQ: 58417
Hi, Ciao
I have a bunch (> 30) 320's connected to HP switches, fw version 6.0.4
They work great but occasionally they where signalling the warning "network
cable disconnected".
Monday, May 29, 2006, 10:38:09 AM, you wrote:
TC> Guido Hecken wrote:
>>> I looked long and hard at the LAN and i
Guido Hecken wrote:
I looked long and hard at the LAN and it was basically narrowed down to
the
switches. In this smaller install, several cheapo Dlink ($30) switches
de-aggregate a Cisco Catalyst switch. What I noticed was that any phone
plugged direcly into the Catalyst did *not* lock
> On Fri, 26 May 2006, Guido Hecken wrote:
> > We had the same problems with some cheap LevelOne Switches.
> > The Snoms rebooted during a call, calls dropped etc.
> > Replacing the switches was the solution.
>
> A switch should NEVER cause ANY device to lockup, ever. Period.
> If a phone locks up
On Fri, 26 May 2006, Remco Barende wrote:
There is just no valid reason why the phone would need to lockup or reboot
even if the network connection would be problematic, no matter what. That is
just poor design, not a feature.
I agree 100%. No device should ever lockup or reboot due to a margi
On Fri, 26 May 2006, Rich Adamson wrote:
Dr. Michael J. Chudobiak wrote:
Blaming the 3com switch is very likely to be the wrong root cause. High
probability the 3com was not configured properly for the phone.
Just curious - what configuration issues did you have in mind?
A partial list of issu
On Fri, 26 May 2006, Guido Hecken wrote:
We had the same problems with some cheap LevelOne Switches.
The Snoms rebooted during a call, calls dropped etc.
Replacing the switches was the solution.
A switch should NEVER cause ANY device to lockup, ever. Period.
If a phone locks up / reboots due to
Colin Anderson wrote:
More cowbell?
Shit, you owe me a new keyboard! Funniest thing I've *ever* read on the
list.
I've experienced the auto-negotiate issue with Snom's before. I forgot to
mention that we make it part of our standard install to force 100baseT-full.
I've also noticed the Catal
Remco Barende wrote:
On Fri, 26 May 2006, Rich Adamson wrote:
You mean that 3Com switches are not to be regarded as decent
switches? At least Snom could have put some remark then that you need
a certain brand of switches. If 3Com is not good enough for the
phones I would have bought differen
>From my point of view, using cheap or expensive switch is not the point.The point is "what kind of switch implementation Snom phones require ?".Up to now, it seems that problems relate to auto-negociation.
Would it be possible for anyone to check that, comparing fixed and auto-negociated behaviour
On Fri, 26 May 2006, Rich Adamson wrote:
You mean that 3Com switches are not to be regarded as decent switches? At
least Snom could have put some remark then that you need a certain brand of
switches. If 3Com is not good enough for the phones I would have bought
different phones.
Blaming th
>More cowbell?
Shit, you owe me a new keyboard! Funniest thing I've *ever* read on the
list.
I've experienced the auto-negotiate issue with Snom's before. I forgot to
mention that we make it part of our standard install to force 100baseT-full.
I've also noticed the Catalyst does the spanning-tre
Andrew D Kirch wrote:
Dr. Michael J. Chudobiak wrote:
Blaming the 3com switch is very likely to be the wrong root cause.
High probability the 3com was not configured properly for the phone.
Just curious - what configuration issues did you have in mind?
- Mike
Replacing it with a Catalyst?
Dr. Michael J. Chudobiak wrote:
Blaming the 3com switch is very likely to be the wrong root cause.
High probability the 3com was not configured properly for the phone.
Just curious - what configuration issues did you have in mind?
A partial list of issues that we've seen in the last 12 years
Dr. Michael J. Chudobiak wrote:
Blaming the 3com switch is very likely to be the wrong root cause.
High probability the 3com was not configured properly for the phone.
Just curious - what configuration issues did you have in mind?
- Mike
Replacing it with a Catalyst?
Andrew
__
Dr. Michael J. Chudobiak wrote:
I looked long and hard at the LAN and it was basically narrowed down
to the
switches. In this smaller install, several cheapo Dlink ($30) switches
de-aggregate a Cisco Catalyst switch. What I noticed was that any phone
plugged direcly into the Catalyst did *not* l
Blaming the 3com switch is very likely to be the wrong root cause. High
probability the 3com was not configured properly for the phone.
Just curious - what configuration issues did you have in mind?
- Mike
___
--Bandwidth and Colocation provided by Ea
I would like to suggest using any managed switch and hard setting the
ports to 100/full
I have found that the auto negotiation algorithm is generally to
blame on many switches.
As an example, connecting a cisco router to a netgear/dlink/3com/etc
will geneerate errors on the cisco interfac
Remco Barende wrote:
On Fri, 26 May 2006, Dave Cotton wrote:
On Fri, 2006-05-26 at 10:11 +0200, Remco Barende wrote:
Thanks for your input!
Previously I was using Nortel 10/100 switches, I replaced them some
weeks ago with 3C16479 gbit switches. The phones are connected
directly to
the gbi
I looked long and hard at the LAN and it was basically narrowed down to the
switches. In this smaller install, several cheapo Dlink ($30) switches
de-aggregate a Cisco Catalyst switch. What I noticed was that any phone
plugged direcly into the Catalyst did *not* lock up or reboot. Any phone
plugge
On Fri, 26 May 2006, Dave Cotton wrote:
On Fri, 2006-05-26 at 10:11 +0200, Remco Barende wrote:
Thanks for your input!
Previously I was using Nortel 10/100 switches, I replaced them some
weeks ago with 3C16479 gbit switches. The phones are connected directly to
the gbit switches. By coinciden
On Fri, 2006-05-26 at 10:11 +0200, Remco Barende wrote:
> Thanks for your input!
>
> Previously I was using Nortel 10/100 switches, I replaced them some
> weeks ago with 3C16479 gbit switches. The phones are connected directly to
> the gbit switches. By coincidence I dit notice on one phone tha
>
> I looked long and hard at the LAN and it was basically narrowed down to
the
> switches. In this smaller install, several cheapo Dlink ($30) switches
> de-aggregate a Cisco Catalyst switch. What I noticed was that any phone
> plugged direcly into the Catalyst did *not* lock up or reboot. Any ph
Changing firmware revs did not help, so that left the LAN.
I looked long and hard at the LAN and it was basically narrowed down to the
switches. In this smaller install, several cheapo Dlink ($30) switches
de-aggregate a Cisco Catalyst switch. What I noticed was that any phone
plugged direcly i
We have a large install of 360's running rev 4.1 with zero problems. I did
another, smaller install couple weeks ago with 40 360's running rev 5.3. In
both cases, the install was identical, same Asterisk version, same dialplan,
everything the same except the differences were:
1. Different firmware
On Wed, 24 May 2006, Tommaso Calosi wrote:
I agree... Snom firmware are buggy. You can use any version, you'll always
find a bug, expecially for 320's. I think instead of developing " the XML
minibrowser" they should make the phones to work properly.
I went around in circles with snom for a wh
I agree... Snom firmware are buggy. You can use any version, you'll
always find a bug, expecially for 320's. I think instead of developing "
the XML minibrowser" they should make the phones to work properly.
Dovid Bender wrote:
I was transporting it in my suitcase when I flew from NY to FL. When
I was transporting it in my suitcase when I flew from NY to FL. When I got there the screen was dead. I contacted snom and they were real helpfull and resolving the issue. DovidAlex Robar <[EMAIL PROTECTED]> wrote: Interesting, I've never had a screen just die on me. Are you saying that the sc
On 5/22/06, Remco Barende <[EMAIL PROTECTED]> wrote:
On Fri, 19 May 2006, Steve Davies wrote:
> I find that the snom phones can be over-sensetive to network glitches,
> which with the default configuration can cause a reboot (usually
> caused by cheap switches). Try changing the reboot on etherne
On Fri, 19 May 2006, Steve Davies wrote:
On 5/19/06, Remco Barende <[EMAIL PROTECTED]> wrote:
Most people seem quite positive about Snom phones, I cannot share this
opinion.
The displays are dying quite often, and firmware is buggy. I have tried
every firmware from 4.5 up to 5.x and 6.04 but k
I'm gonna jump in here and join Dave here.
It simply is of no value to just SPAM your opinion around without
either providing real facts or asking for assistance. We are here to
ask for or give out help. This just isn't productive.
Now, if you want a detailed, painfully so, explanation why
[EMAIL PROTECTED]
> Sent: Friday, May 19, 2006 9:21 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Asterisk-Users] Snom firmwares suck
>
> Remco Barende wrote:
> > Most people seem quite positive about Snom phones, I can
On Fri, 2006-05-19 at 10:21 -0400, Dr. Michael J. Chudobiak wrote:
> > Old English saying "A bad workman always blames his tools"
>
> I don't think that's fair... these are very complicated phones, made in
> China for very low prices. Problems do occur with them.
>
> Some Snom LCDs do have probl
Old English saying "A bad workman always blames his tools"
I don't think that's fair... these are very complicated phones, made in
China for very low prices. Problems do occur with them.
Some Snom LCDs do have problems.
There are firmware glitches, though I've only run into minor ones.
Over
On 5/19/06, Remco Barende <[EMAIL PROTECTED]> wrote:
> I find that the snom phones can be over-sensetive to network glitches,
> which with the default configuration can cause a reboot (usually
> caused by cheap switches). Try changing the reboot on ethernet unplug
> setting to "ignore".
Good ide
On Fri, 2006-05-19 at 14:19 +0100, Steve Davies wrote:
> On 5/19/06, Remco Barende <[EMAIL PROTECTED]> wrote:
> > Most people seem quite positive about Snom phones, I cannot share this
> > opinion.
> >
> > The displays are dying quite often, and firmware is buggy. I have tried
> > every firmware fr
The displays are dying quite often, and firmware is buggy. I have tried
every firmware from 4.5 up to 5.x and 6.04 but keep having problems with
phones locking up or rebooting during an ongoing conversation.
Yes, as someone asked earlier on the list the displays do die at some
random moment w
Remco Barende wrote:
Most people seem quite positive about Snom phones, I cannot share this
opinion.
The displays are dying quite often, and firmware is buggy. I have tried
every firmware from 4.5 up to 5.x and 6.04 but keep having problems with
phones locking up or rebooting during an ongoin
On 5/19/06, Remco Barende <[EMAIL PROTECTED]> wrote:
Most people seem quite positive about Snom phones, I cannot share this
opinion.
The displays are dying quite often, and firmware is buggy. I have tried
every firmware from 4.5 up to 5.x and 6.04 but keep having problems with
phones locking up
Interesting, I've never had a screen just die on me. Are you saying that the screen just stops working?As for firmware, I've always found that the best way to deal with problematic firmware is to talk to the company about it. Especially in a scenario like you're in, where everyone else seems happy
Remco Barende wrote:
Most people seem quite positive about Snom phones, I cannot share this
opinion.
The displays are dying quite often, and firmware is buggy. I have
tried every firmware from 4.5 up to 5.x and 6.04 but keep having
problems with phones locking up or rebooting during an ongoin
Most people seem quite positive about Snom phones, I cannot share this
opinion.
The displays are dying quite often, and firmware is buggy. I have tried
every firmware from 4.5 up to 5.x and 6.04 but keep having problems with
phones locking up or rebooting during an ongoing conversation.
REAL
42 matches
Mail list logo
