I have a client that has 5 Snom 320s. 4 work great, one does not. I upgrade the firmware to the latest (6.5.2) and the problem goes away, but then comes back a couple days later. There is a slight packet loss on the phone (about 1%), though there is no packet loss on any of the other phones. I determine the packet loss by the Linux command "ping -f -c 10000 192.168.2.10". Outgoing calls are junk, incoming calls are fine. (relatively speaking) The config from one phone to the next is the same except for account and voicemail settings. sip.conf is the same except for account. okay, the phone is bad, so I order a new one. This phone, however, is reporting 4% - 30% packet loss so every call is horrible just due to the lost packets (I'd assume). I install a new cable into a different port on the switch (same port as a working phone, with the working phone going into the same port as the old cable). Same results. Take this phone elsewhere. Packet loss continues. I even try different power supplies and handsets to find SOME sort of fault other than the obvious. I take the old phone back to my office and it works flawlessly, though my client uses the phone constantly all day whereas we only did approximately a half hour of testing. I take the new phone back to my office and it now has 0% packet loss. So, do I have two broken phones or is there something else wrong? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070117/3da4b865/attachment.htm
Had this happen when I put a SNOM 360 On the Lan over Fiber. The Fiber transivers where stuck to 100tx and it was botching things. I put a 10base hub between the fiber and the phone and it worked. Disable the auto network config and I think that you can set the unplug to ignore and another setting.... logging into one..... Phone Type: snom360-SIP MAC-Address: xxxxxxxxxxxxx IP-Address: 192.168.1.79 Kernel Version: snom360 linux 3.25 Application-Version: snom360-SIP 6.5.1 Rootfs-Version: snom360 jffs2 v3.36 Firmware-URL: http://192.168.20.1/snom/firmware/snom360-3.25-l.bin Production Information: Mac:00041323195B;Version:Standard;Hardware:snom360 (Revesion B);Lot:12 (June 2005) Thats right I had to update the Linux Kernel, the firmware and the filesystem.... three updates.... give it a try On 1/17/07, Mike Hammett <asterisk-users@ics-il.net> wrote:> > > > I have a client that has 5 Snom 320s. 4 work great, one does not. I > upgrade the firmware to the latest (6.5.2) and the problem goes away, but > then comes back a couple days later. > > There is a slight packet loss on the phone (about 1%), though there is no > packet loss on any of the other phones. > > I determine the packet loss by the Linux command "ping -f -c 10000 > 192.168.2.10". > > Outgoing calls are junk, incoming calls are fine. (relatively speaking) > > The config from one phone to the next is the same except for account and > voicemail settings. > > sip.conf is the same except for account. > > okay, the phone is bad, so I order a new one. This phone, however, is > reporting 4% - 30% packet loss so every call is horrible just due to the > lost packets (I'd assume). > > I install a new cable into a different port on the switch (same port as a > working phone, with the working phone going into the same port as the old > cable). Same results. > > Take this phone elsewhere. Packet loss continues. I even try different > power supplies and handsets to find SOME sort of fault other than the > obvious. > > I take the old phone back to my office and it works flawlessly, though my > client uses the phone constantly all day whereas we only did approximately a > half hour of testing. > > I take the new phone back to my office and it now has 0% packet loss. > > So, do I have two broken phones or is there something else wrong? > > > ----- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > >-- --- Andrew Latham - AKA: LATHAMA (lay-th-ham-eh) lathama@lathama.com - lathama@gmail.com If any of the above are down we have bigger problems than my email! Hind sight is most always 20/20 or better. ---
On the voip-info.org wiki there are good tips to get snoms to play nice on lans. I personally have experienced wierdness using particular switches (cheap ones). also note that snom now has an auto-update subscription URL in their support wiki, if you use the URL it makes updating a 4.X to 6.X with the new FS, linux, etc not quite so brutal.
Note: you can also download and fine tune the php used to do it. works like a charm. On 1/17/07, Colin Anderson <ColinA@landmarkmasterbuilder.com> wrote:> On the voip-info.org wiki there are good tips to get snoms to play nice on > lans. I personally have experienced wierdness using particular switches > (cheap ones). > > also note that snom now has an auto-update subscription URL in their support > wiki, if you use the URL it makes updating a 4.X to 6.X with the new FS, > linux, etc not quite so brutal. > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- --- Andrew Latham - AKA: LATHAMA (lay-th-ham-eh) lathama@lathama.com - lathama@gmail.com If any of the above are down we have bigger problems than my email! Hind sight is most always 20/20 or better. ---