SNOM M3 issues - HELP!

I only have one of these at home, and mine did it after updating the firmware. It must have cycled at least 10 times or so, but it eventually quit and has been working fine since.

Hey all,

Snom sent me to the beta firmware, 1.15, site for this phone. I have asked to release it here and will do so as soon as I hear back from them. I finished the update about 20 minutes ago and all seems well. I will leave it on overnight and by then, I hope to have heard from Snom.

nzkef, if you need it before Snom responds, send me an email. My email is on my website.

Thanks for doing the hard yards John. I've been in contact with our reseller in Australia and am waiting on a response from them as well.

I've just updated the firmware on my 2 handsets at the office to the beta. Might also try this version at one of the customer's sites and see how we go.

I had a look on the Snom support website and didn't see any contact details for Dan Fitzgearld. There is a generic support email address, not sure if that's the best way to get a hold of him though?

Thanks again.

Kevin.

I received my first (and last) snom m3 last night.

This is a huge disappointment. I have been able to get it to make and receive calls, but nothing else works. Transfer fails. Errors. Etc.

You can't update the contact list via the web interface. That REALLY sucks.

I tried to update the firmware, after spending 2.5 hours googling to try and find out how. The firmware update function on the handset just returns "server timeout".

I had to run Wireshark to trace the packets and see what it's doing. Great documentation. Anyway, it is trying to download "dirlist.txt" from snom's tftp server, and that file does not exist at the location they say it should.

The phone came with firmware 1.07. Snom's website says 1.16 is current. The closest thing I've been able to find by crawling around their ftp server is /m3/v116/Fileformat3. This is version 1.16, I suppose, but the only language is French.

Ummmm. This is ridiculous. can anyone suggest a way to make this phone work (minimum to support attended call transfer and DTMF RFC2833). I speak english, russian and spanish. But not french.

I guess I have 30 days before I have to try and get a refund. Thanks in advance for any help. I don't mind doing the hard work if it will in fact work.

Why so hard - details on their wiki to update to 1.16

http://wiki.snom.com/Snom_m3/Firmware/Update

I just found out that the phone doesn't display caller id text.

That is the final blow. This just cannot be used for any purpose, business or home use.

It's really strange because if you look in the "call log", the caller's name is there. But it doesn't display on the screen when the phone rings. The display just says "Speakerphone: Off".

Other reviewers said this phone is great... But I don't get it.
My $30 Uniden from Best Buy blows the doors off it. And my old Uniden get's 4 times the range.

I have a Snom m3 gateway with 4 handsets hooked up to trixbox 2.6 and cannot reproduce any of the issues you mention.
Transferring calls works, even repeatedly. caller ID text is displayed. I have everything updated to firmware 1.16
Snom confirmed that they will release an update to the firmware sometime in September which will create the possibility of centrally provided common directory.
As far as range goes, it is fine for me. Of course as with anything RF, your location may be completely different. You can always try to relocate the gateway and get additional Snom DECT repeaters.
For what it does, I think the Snom m3 has no competitor in its price range.

As I do not have any other hardware SIP phone, it will have to be a softphone registered via SIP. Is that OK? I have Zoiper and Nokia N800 with SIP client.

It works for me, no problem with the music on hold nor audio both ways.
Tested with BOL Sip Phone and Zoiper, the Nokia N800 client does not have hold function.
I hear music on the Snom handset when the softphone end placed the call on hold and when taken off hold there is audio both ways. Loud and clear.
I would be more than happy to try other setups, or share with you my provisioning file privately.

My 100 M3's seem to be behaving as of late. Only slight occurrence they get is some echo problems. And 1 (yes just 1) has the reboot handset on incoming call problem. But I think it must be an environmental issue at the customer site as I replaced the handset & gateway and the same thing happened with the new one. Yet the original one works fine in my test lab.

Can't say I have the one way audio problem though. I'm on 1.16, which seems to have resolved my handset losing registration with gateway issue.

I recently set up an M3 with five handsets and have had no trouble out of the box with call quality and normal call features etc. That was until I tried to individually name the handsets and found that two out of the five persistently try to be a clone of each other changing the name on either handset causes the other handset to change a few seconds later.

I don't know what firmware they are running because they have not been updated since purchase. A firmware update is the next thing I'm going to try to resolve this naming issue seeing as most of you are reporting good results with the latest version.

Thanks to all for the useful information

Good to see some more M3 users out there.

Chrism2: Regarding DTMF tones, have you gone in via the web browser interface and changed each handsets DTMF singnalling from 'inband' to 'SIP INFO'. This resolved the DTMF issue I was experiencing. Make sure you reset the gateway after making the change.

Kbedford: Try and update to the latest firmware (1.16). This makes naming individual handsets a whole lot easier.

Iverona: I was getting pretty frustrated with the handsets losing registration for a period of several months as well. But since going to 1.16 I've only had 2 go down and that was awhile ago now. Maybe I'm just unaware of the issue because my customers know to reset the gateway when it happens, but I haven't had any calls from them about it for at least a month.

For the record, I have 17 sites out there with Snom M3's, 16 of them with 6 handsets connecting to 1 gateway. I love how easy the M3's are to configure. But had you asked me 2 months ago would I deploy them again the answer would have been a resounding NO! I'll wait a couple more months monitoring my existing sites and if the registration issue is finally dead and buried then I'll think about deploying them again.

Good luck all.