login | register
Tue 09 of Feb, 2010 [21:10 UTC]

voip-info.org

History

Snom Phones

Created by: admin,Last modification on Wed 03 of Feb, 2010 [01:08 UTC] by ecitelnz

Snom VoIP Phones and SIP Proxy/PBX


www.snom.com

snom_870.jpg
Snom_820.jpg
Image
Image
Image
Image
Image
snom meetingpoint.jpg
snom_expansion_module.jpg


Snom SIP based phones:

  • Snom M3: To be presented at VON autumn 2007, but sneak previewed at Astricon Phoenix 2007. DECT based (GAP compliant) cordless solution. Sold as base station with handset/charger station and single handset/charger station. Up to eight handsets can register with the base station and the base station can register up to eight SIP accounts. One base station supports a maximum of three simultaneous conversations. As with other Snoms, the base station can be provisioned via HTTP and, apparently, the individual handset menus can be configured to lock them down somewhat. Availability is quoted as 'end October 2007', but knowing Snom, the reality is to be at least the end of November 2007. UPDATE - It's January 2008 and they are now shipping!

  • snom 820: New phone launched at end of 2008.

  • snom 870: Touchscreen phone, first showcase announced for CeBIT 2009 (March 2009) in Hannover

  • snom 370: This phone was announced at CeBIT 2007 to be available April '07. High-end device, similar to 360, with higher resolution grey-scale display (240x128), a large LED-light for incoming calls and possible VPN support in future firmware versions. The phone has more RAM and CPU power than the 360; no more rubber keys.
  • snom 360: tilt-adjustable graphics display 128x64 with blue backlight, 47 keys, 13 LED (12 busy-lamps on function keys, 1 LED for message and SMS indication)
    • codecs g711a/u, g729A, g723.1 GSM-FR 6.10, g722, g726-32
    • (since firmware 4.0) supports up to 12 registration accounts instead of the 7 previously. This means that all 12 line/led keys can now be configured as a line to PBX.
    • enhanced (over snom2xx) cradel and handset for more secure fit
    • Supports 802.3af Power over Ethernet
    • TLS and SRTP support for secure voice encryption
    • significant upgrade in max volume through the handset and speaker phone
    • one touch RECORD button usuable only with special PBX support via SIP INFO method.
    • keypad buttons changed to more traditional style for faster and easier dialing
    • The 360 is the beginning of a new platform of 3xx phones from Snom, introduced in April 2005 (Cebit)
  • Snom 360 Sidecar
  • snom 320: based on the snom360 design but with smaller, two-line, tilt-adjustable LCD display without backlight. Also, the 320 supports conferences (joined at the phone) of only 3 parties (ie, the phone user and two others). The 360 will conference many parties (exact number not known). Apart from this, the 320 has features identical to the 360. Introduced in June 2005 (SuperComm).
  • snom 300 2006 model: A smaller phone, with less physical interface, but equal software feature-set to the 320.
    • Great for SOHO applications
    • Programmable function keys
    • Simpler interface
    • Downside: No Power over Ethernet
  • snom 300 2007 model: As per the 2006 model, above, but.....
    • Support for Power Over Ethernet (PoE)
    • Backlit display

New in firmware 7 (2007):
Some of the new features are
  • RTP multicast support
  • Broadsoft Busy Lamp field support (BLF)
  • Event-list subscription for dialog state monitoring
  • Presence/Buddy-list feature (snom360/snom370)
  • Caller picture display (snom370)
  • Ability to publish presence information based on the user selected status (Busy, Available, Away etc.).
  • Ability to pull the call list (missed-call-summary) from the server on startup
  • Server specific Bridged Line/Shared Call Appearance support (Asterisk, Broadsoft, Sylantro, PBXnSIP)
  • Multiple Audio Output Devices
  • New dialplan in xml (older dial plan regex support removed)
  • xml provisioning

Re-branded SNOM phones:

Discontinued Snom phones:

  • snom 220 (Released August 2004, discontinued, no longer supported Aug-07): Top-of-the-line business phone, replaced by 360 model. codecs: g729a, GSM, G711u/a, 128 X 64 graphical back-lit display, PoE, four context sensitive soft keys, 16bit 16Khz audio, half duplex speaker, key extension module available to expand programmable keys to 60, dual 10/100mbit ethernet switch;
  • snom 200 (discontinued) codecs: g711u/a, g729a, GSM, power-over-ethernet, otherwise virtually identical to model 190, except for sound system, but no discernable difference in audio quality.
  • snom 190 (discontinued manufacturing by SNOM, but still available as ip290 by ELMEG): Successor of the discontinued snom200, Two-line LCD display, 5 Function keys with busy lamps, SRTP and SIPS encryption, max. 7 account lines configurable, 2 call appearances, no POE, Codecs: g711u/a, g729A, g722, g726-32, g723.1, GSM (since 3.56e), full duplex audio system; Snom 190 Review.
  • snom 105 (discontinued)
  • snom 100 (discontinued) the snom100 is a nice and small SIP/H323 capable IP phone with a 128x64 pixel graphical green LCD screen featuring an analog clock image, date and registration account lines. The botton line is used as labels for the 4 software programmed key on the top row of the 4x5 key pad. The phone uses a 24 or 48Volt power supply and has Power over Ethernet capability as well. It only has one Ethernet port.

Snom software:


  • snom Softphone (Windows v5.3): softphone version of the SNOM 360. Free for private use, still in beta development (with issues).

  • snom 4S based solutions: Commercial servers by SNOM
    • snom 4S Proxy: SIP Proxy and registrar (Linux or Widows).
    • snom 4S Media Server: Auto-attendent, voice-mail, annoucements (Linux or Windows).
    • snom 4S NAT Filter/Session Border Controller: RTP proxy for NAT traversal.
    • snom ITSP solution: Bundle consisting of the 4S Proxy, 4S Media Server, and 4S NAT Filter/Session Border Controller. Complete system for beginning ITSP.

    • snom 4S History: In 2000 it was very difficult to test SIP against anything else, so snom decided to build a test system and give it away for free also to customers. Over time, more and more features went into the system, and customers were accepting the software as commercial product. snom then called this system 4S for "snom small SIP system". Today, there is a broad range of SIP software available and in order to maker partnerships easier, snom moved the software into a seperate company. The 4S was moved to www.4snewcom.de which takes care about 4S for ITSP. There was a internal project called 5S which took care about the PBX, but in order to avoid confusion with the product names, the project took place in a new company with the name www.pbxnsip.com. The snom box uses the pbxnsip software now as a "third party" product.


SIP Phone Features:


The phones are based on an embedded linux kernel, source is available from the SNOM web site.

All models have good sound quality, readable displays, adjustable ring tones and work well with Asterisk and other SIP systems (supported by Asterisk). The programmable keys have LEDs and can "SIP subscribe" to other extensions. The phones support Power over Ethernet (except the 190) as well as having a seperate power supply available. The support SNOM delivers is excellent and they pay attention to the Asterisk community. All phones have native language interface, English, German, French, Dutch, Spanish,..

Custom ring tones:

The SNOM has the ability to download custom ringtones to the phone using the webinterface starting with firmware version 2.05b. The type of files that should be supplied to the phone are: "8 kHz 16 bit/sample (linear) mono WAV files". Alternatively you can instruct the Proxy or PBX (like Asterisk) to include an ALERT_INFO header in the SIP communication that carries a HTTP URI pointing at a wav file that is to be used as ringtone for this particular call.

Headset / Handset / Speaker behaviour:

SNOM released a document describing the policies regarding this issue:
http://www.snom.com/faq/FAQ-04-04-28-ut.pdf

Intercom and Auto Answer:

Phones have an Auto Answer capability as well as Intercom support.
Intercom works with special PBX support. The Request/To URI must contain intercom=true parameter.
See Asterisk Wiki or Mailing List for specifics for Asterisk users.
  • Post on Asterisk Mailing List

NAT traversal support:

Snom phones support a variety of NAT traversal options, including (depending on model and firmware version) STUN, Outbound-Proxy, UPnP, ICE, symmetric RTP. STUN support was broken for a period after the introduction of the snom190 (only snom190/firmware 3.60s works) and all versions of the 320/360 series firmware until release 4.1. UPnP support was dropped in the later releases of the 190 and in the 320/360 models.
In the newer firmware release STUN support can be configured separately for each registration account, which is a nice feature if you need to register to a local PBX (behind NAT with the phone) as well as remote networks.
The newer snom phones models also claim ICE support, but this is not widely available on PBX's and providers networks.

Web interface:

You can see a demo of the Snom phone web interface at http://www.provu.co.uk/snom_demo/

Impressions and Reviews

Read reviews of Snom phones:

Snom phones are definitely at the quality end of the market rather than cheap. The build quality is high - except that the handset of the Snom 200 feels light, and it sits rather loosely in the chassis when hung up.

Mass Deployment

Information on snom mass deployment of phones

Howtos

SNOM360:
SNOM190:
SNOM200:
Display credit at VoIP provider after call
SNOM hardware and software hacks

Pricing

  • snom 370 ~ 210 Euro
  • snom 360 ~ 170 Euro
  • snom 320 ~ 130 Euro
  • snom 300 ~ 75 Euro
  • snom Softphone 360 ~ free (no support)
  • snom Box ~ 1450 Euro

Distribution

You can purchase SNOM phones from a number of vendors, including:



















3rd party tools

Tool for editing the phone's address book and Call by PC
Update: V.1.1.2 NEW!!!
http://www.paradoxon101.de/counter_dl/count.php?id=3

Firmware

You can find firmware releases at the following sites:

Snom is pretty good at responding to bug reports and inquiries. Be clear in your wording. Follow-up may be necessary depending on your native tongue.

Firmware 5.x

  1. New firmware structure, please see Important Update description.
  2. DKEYS which mean keys which usually have a static binding (redial, transfer, etc.) and which now can be bound to different functionalities.
  3. Actions URLs for call start and call end including support for settings and macro replacement.
  4. Keyboard lock, by pressing the *-key for a few seconds the keyboard will be locked and can be unlocked by again pressing this key for a few seconds. If a PIN has been defined before (e.g. via the web interface), the phone is asking for that before unlocking.
  5. Basic LDAP support.
  6. XML idle screen description to design your own idle screen. Read about it in the FAQs.
  7. Signalling of DTMF via SIP INFO.
  8. Shared Line Appearance based on the IETF draft with sla parameter in dialog Event type.

Firmware 6.x

  1. GUI: added XML minibrowser support (snom360)
  2. GUI: fixed desktop SMS
  3. GUI: title texts configurable through mass deployment (snom360)
  4. GUI: line based ring after delay for incoming calls
  5. GUI: changed MWI led behavior to reflect latest vmail status
  6. GUI: fixed first dtmf echo on dialing
  7. GUI: deny list now works for complete uri match using identity context
  8. GUI: fixed Name+Number for numeric display names
  9. GUI: double redial key press to redial last call
  10. GUI: set led's for associated key events
  11. GUI: DND icon has high priority on status line
  12. GUI: use identity of connected call for parking/Xfer
  13. GUI: enhanced spanish language support
  14. GUI: reset to factory defaults restarts the phone, too
  15. GUI: fixed speed dial on Xfer
  16. GUI: redirection on timeout has its own target parameter now
  17. WEB: reset to factory defaults restarts the phone, too
  18. WEB: added new reboot info page
  19. WEB: clean up e164 numbers dialed through web interface
  20. WEB: added star codes based dnd/redirection
  21. WEB: directory key is programmable
  22. WEB: added control to filter out SIP tracing for REGISTER/SUBSCRIBE/NOTIFY
  23. WEB: added ACTIVE option for fkey context selection
  24. LID: adjusted knocking (call waiting) volume
  25. LID: fixed local playback of first dtmf in handsfree mode, also fixed and cleaned overall local playback of DTMF in different cases
  26. LID: fixed a conference bug (phone slowed down after a conference)
  27. SIP: intercom/Push2Talk calls send an Alert-Info header
  28. SIP: added server hosted conference feature
  29. SIP: use display name if available in 180 Ringing
  30. SIP: send NOTIFY on receiving an unsubscribe request
  31. SIP: added pnp settings retrieval

Upgrading the firmware

There are 3 pieces of software in the Snom 190, Snom 320, and Snom 360:
  1. Linux
  2. Applications
  3. jffs2 (was Ramdisk in the past)

Firmware 7.x

  1. Wannabe call manager compatible ?!?
  2. Phone looks for SIPDefault.cnf, SIP{MAC}.cnf in addition to snom3x0.htm and snom3x0-{MAC}.htm
  3. Provisioning via XML
  4. Default softkey allocation changes
  5. Labelling of certain functions (eg phone book, call history) changes
  6. 7.1.8, which ships on some units from the factory, does NOT work with Asterisk.
    • Upgrade the firmware to the latest 7.1.x or the latest 6.x and you'll be all set
  7. If supplied with 7.x from factory, and you'd rather stick with the more mature 6.x, the downgrade process is straightforward if you use Snom's method:
    • http://wiki.snom.com/Firmware/Wizard
    • Do NOT downgrade manually unless you know what you are doing. Phones that shipped with 7.x have new MAC address ranges and cannot be downgraded to firmware older than 6.5.13.
      • The flash layout changes and new MAC address ranges.
        • http://kb.snom.com/kb/index.php?View=entry&CategoryID=48&EntryID=77
  8. Snom recently elevated Firmware 7.1.x to non-beta status. 6.x is also still being maintained.

To upgrade these, you paste the URL locations into the "Software Update | Firmware" field.
Currently, there is also a "Bootloader" field on this page. DO NOT use the Bootloader Field in the procedure below.

The phone picks out the last letter before .bin in order to know what type of software is being changed:
  • -l corresponds to Linux
  • -r corresponds to jffs2 (was Ramdisk in the past)
  • -j corresponds to Applications
As of 3.60b, there is no way to tell what Linux or Ramdisk version you are using. The only way to know for sure is to upload the files.



Bugs and Issues

  • Asterisk support broken in 7.1.8, fixed in 7.1.10 and higher
  • Retarded dialplan support v7.1.x, rectified a little bit in 7.1.16 and higher
  • Phones transfer function seriously broken - see below (upto 7.1.19)

Blind Transfers

I had a problem with transfers on my Snom 190 until I made sure that the "Break Key" setting on the advanced page of the Snom web configuration was set to off. Then blind transfers started working great.

Distinctive ringing:

This only seems to work if the distinctive ringtones are selected based on "source", rather than "destination". That is, you can assign distinctive ringtones for certain callers. However, trying to assign ringtones based on the extension dialed (if you have set up multiple lines on the phone) just doesn't work (as of firmware v3.35, anyway) - the default ringtone is always used.

This problem is fixed in Snom190 3.56r, Snom200 3.56r, Snom220 3.56t.
Also makesure you have "Default Selection:" set to "source" under "Ringtone defaults:" on the preferences page.

Call Parking Orbits

I don't think the programmable function keys can be used to implement call parking on Asterisk. (Snom has their own server software - for which the call parking function keys presumably work.) Go to Asterisk bounty snom call park if you know how to fix this.

I tried the Call Park Orbit feature with Asterisk by setting the desired button to Park with a value of 700. When in a call pressing the park button immediately parks the call but I don't get the Asterisk announcement telling me what extension to pick the call up on.

UPDATE:

  • There is a patch for 1.2.9.1 available here: http://bugs.digium.com/view.php?id=5779 which will get parking working on the 3XX series*** See the last few comments on the notes.
    • Regarding the dialplan setup: the directions available are somewhat ambiguous as to one detail: DO keep your parkedcalls context, and DO include => parkedcalls in the context your user is registered to (or included in), but make sure you DO also provide a hint to local/701@parkedcalls in the SAME context your user is registered to (i.e. DO NOT put the hints in a context included from the one your user is registered to). -FG

  • Set "Transfer On Hook" to off in the Snom firmware, or attempting to connect to a parked call while your phone is ringing will transfer the incomming call to that parking spot with no way of getting it back. The two 3rd parties will be chatting on your dime. -FG

  • Users may try, and are now able, to attempt to transfer a call directly to a parking spot. The system picks up on the fact that the spot is empty, tells the incomming caller that ".. there is no call parked on that extension... ", and proceeds to hang up on them. This would be great if it worked, and somehow had a safeguard that would prevent loss of the call if two users try to park a call on the same spot at the same time (what happens to the one that came in second?). My feeling is that Asterisk 1.4 will address this. -FG

  • My users dont get audible confirmation of the parking either using Snom 360s. Everything else works, but the CLI shows that the Snom disconnects the call before Asterisk gets to the playback the second digit of the spot extension, and before the user heasrs the first one. While this is probably still ok for a small PBX, it two people park a call at the same instance, there is no way to tell who got the first available spot. -FG

These last two issues are the only serious ones I've found, but they are pretty critical. Hope this helps.

Assisted (Attendant) Transfers are broken.


Although the Snom 370 might look like a great receptionists phone it has a major problem with assisted transfers (7.1.X to 7.1.19 at least).

Basically, if there is more than one incoming call your receptionist has to answer all of them and put all of them on hold before using the phones transfer functions (this has been raised with Snom support and they confirmed this is the case). If another call comes in whilst in the transfer process you're stuffed.

Here's the failing scenario:

Snom370 gets a Call (Call A).
Snom370 answers Call A. Call A wants to be transferred to Phone C.
Snom370 has another call ringing (Call B).
Snom370 presses HOLD button gets Dialtone. Call A is on Hold, Call B still ringing.
Snom370 Dials Phone C (Call C).
Snom370 talks to Call C.
Snom370 presses TRANSFER.

The display shows:

      < CallA
      > CallB

The soft keys now show "<<" and ">>". Pressing them does nothing.

When the TRANSFER button is pressed again, CallA is connected to CallB (the original caller is now talking to the previously unanswered party) not what one wanted to happen!


Help forum


See also


Comments

Comments Filter
222

333Re: Adding A Info Message on LCD - Snom 360

by ryanwilliams, Wednesday 14 of November, 2007 [02:47:19 UTC]
Night Mode message. (Use the TrySystem command in the dialplan to execute the script)

idle.xml
< screen_description>
< DigitalClock>
< LocationX>135< /LocationX>
< LocationY>50< /LocationY>
< /DigitalClock>
< Line>
< Account>
< LocationX>40< /LocationX>
< LocationY>20< /LocationY>
< /Account>
< /Line>
< /screen_description>

night-on.sh
wget --delete-after 'http://192.168.104.121/dummy.htm?settings=save&user_xml_screen_url1=http://192.168.104.1/idle.xml&user_idle_text1=Night Mode' -o /dev/null

night-off.sh
wget --delete-after 'http://192.168.104.121/dummy.htm?settings=save&user_xml_screen_url1=&user_idle_text1=' -o /dev/null

222

333VoIP Wholesale and Distributionship needs

by jenniferhan, Wednesday 17 of October, 2007 [03:07:21 UTC]
As VoIP business users in Dubai are being blocked. Many users are turning to VPN solutions to allow the ability to use VoIP and get around the current blocking issue. This however is an expensive and unnecessary solution with SpeedVoIP Technology. To resolve this situation, SpeedVoIP has released it's new solution for Voip Blocking called VGCP (VoiceGuard Control Protocol).

In today’s market, VoIP for business has become more and more popular and necessary than ever before.

Dubai has become a big market, many big companies need to open branch offices in the UAE allowing more profit and larger market access. Technology Issues become apparent during this process that can cripple communications for that company. The primary communications issues are with VOIP blocking policies implemented in Dubai.

Now, here is the good news, A Canada based company SpeedVoIP with their integral R&D team have work out a new way to solve this VoIP blocking issue. This new system VGCP (VoiceGuard@ Control Protocol) has now laid the path to streamline low cost telephony solutions removing country limitations.

VGCP is a proprietary layer 2 link protocol working at between IP stack and NIC driver for VoIP anti-blocking. The core patent-pending VGCP is industry's most state-of-art voice service provider class security protocol whose scalability and flexibility results in not to compromise voice quality and overhead. VGCP controls and monitors full voice signalling and media flow intelligently, meanwhile disguises sip and RTP packets into normal allowed data packets such as DNS and TFTP, and makes two-way encryption and decryption driven by user-customized policy. VGCP is fully transparent to upper SIP proxy or UA which means VoiceGuard@ can work with any 3rd party soft phone/ATA/Gateway/IP Phone/IADs and SIP Proxy or Server not like some competitors which take effect on their own device and soft switch.

Korea Telecom has implemented this solution successfully for more than one year. And it has been operational within a group of Dubai companies. The trials and implementations proves that, The VGCP solution is the best solution to solve the VoIP Blocking issue and provides stable communications platforms providing an indispensable part of the business network.

Andy Wong ~ ~
MSN: andywong-01@hotmail.com
Email: xd.wong@speed-voip.com
www.speed-voip.com

222

333Adding A Info Message on LCD - Snom 360

by mike240se, Saturday 04 of February, 2006 [22:41:05 UTC]
The LCD is so big that there is plenty of room to be able to display a message, I was hoping to be able to put "Night Mode Activated" when the phones are put into night mode.... XML Idle screen controls only where you can put things, and the xml apps need to be run i believe. And also the send text wouldnt stay on all night till the phones are switched in the morning... I was hoping i could add something to the xml idle so that it would work.

Also I use the record button by simply turning on one-touch record in features.conf and then maping the record button to *1 or whatever its set to. I havent seen any mention of this?
222

333Tweaks required to get the extension state lights to work

by adsllc, Saturday 23 of April, 2005 [14:37:35 UTC]
Note: voip-info.org won't let me put greater than/less than characters in this post (it strips them out thinking they're HTML), so greater than is shown as '}' and less than as '{'. Replace as needed.

To get the extension state lights to work, you need to do the following:

Add the following for each extension you'd like to be able to monitor:

exten =} 1010,hint,SIP/1010

This should be in extensions.conf in the same context as the extension itself is defined in. Variables and such won't work, it needs to be a simple mapping of extension to device.

On the phone, go to Setup | Function Keys and set as the following:

P5 Destination Number: 1010

After you click Save, 1010 will expand to {sip:1010@asterisk;user=phone}

Then go to Setup | Advanced and turn off "Filter Packets from Registrar" (this is the magic ingredient, the rest of these instructions apply to most any phone).

All of this should allow you to transfer/make calls to ext. 1010 with the button, and the light should show you when the phone is available.

Rumors I've heard:

You must reset this phone and the target phones after making changes due to incomplete SUBSCRIBE support in Asterisk.
Issuing a "reload" command breaks this feature. Use a "restart gracefully" instead.

Troubleshooting:

You can use the SIP trace feature to see if the phone is receiving and responding to events appropriately. When a remote extension goes into use, the phone should receive a packet something like this (1020=Snom 360, 1012=Remote extension):

Received from udp:asterisk:5060 at 23/4/2005 09:01:51:690 (618 bytes):

NOTIFY sip:1020@asterisk SIP/2.0
Via: SIP/2.0/UDP asterisk:5060;branch=z9hG4bK5d4cc481
From: {sip:1012@asterisk;user=phone};tag=as40a61412
To: {sip:1020@asterisk};tag=65yk3i8chi
Contact: {sip:1012@asterisk}
Call-ID: 3c26700d1adb-i31pkwpyd2oc@snom360
CSeq: 130 NOTIFY
User-Agent: Asterisk PBX
Event: dialog
Content-Type: application/dialog-info+xml
Content-Length: 207

{?xml version="1.0"?}
{dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="28" state="full" entity="sip:1020@asterisk"}
{dialog id="1012"}
{state}confirmed{/state}
{/dialog}
{/dialog-info}

Then the phone will reply with something like this:

Sent to udp:asterisk:5060 at 23/4/2005 09:53:16:760 (265 bytes):

SIP/2.0 200 Ok
Via: SIP/2.0/UDP asterisk:5060;branch=z9hG4bK43e8d1e3
From: {sip:1012@asterisk;user=phone};tag=as40a61412
To: {sip:1020@asterisk};tag=65yk3i8chi
Call-ID: 3c26700d1adb-i31pkwpyd2oc@snom360
CSeq: 132 NOTIFY
Content-Length: 0

If you haven't turned off "Filter Packets from Registrar" the reply will be a "xxx Access Denied" or somesuch instead of "200 Ok".

And when the call completes you should get much the same thing, except with a state of "terminated" instead of "confirmed".
222

333Update: Snom 360 trouble - seemed to be released before it was ready for prime time

by adsllc, Friday 22 of April, 2005 [11:03:13 UTC]
OK, there is a firmware update available, it's just not where you'd ever find it.

Try http://www.snom.com/download/share. The current latest (beta) is http://www.snom.com/download/share/snom360-3.60d-SIP-j.bin.

Paste the full URL into the Firmware field (not the bootloader field) on the phone's software udpate page. The phone may reboot automatically, if not you'll have to reboot it manually. It will prompt to download/install the update as it's coming back up. You have to be in front of the phone to accept the update, don't try it remotely...

Firmware descriptions are available from http://www.snom.com/snom360_release_notes.html?&L=1. You can't find this information under Support | Firmware download, only the release notes. The link for downloads given in the release notes is currently incorrect, use the one given above.

I upgraded from 3.57t to 3.60d, and I'm cautiously optimistic that it will fix the issues I've been having. I haven't been able to get the extension state lights to work with a hint for each extension yet, but I'm working on it.

Additional hard to find info that's mostly accurate can be found at
http://www.abptech.com/mainpages/support/faq_index.html, near the bottom.
222

333Snom 360 trouble - seemed to be released before it was ready for prime time

by adsllc, Thursday 21 of April, 2005 [18:03:12 UTC]
1. There is no manual available for this phone.
2. The firmware stinks, and no updates are available.

This phone has potential to be a decent phone, but I would call it alpha quality and nowhere near ready for release as of April 2005.

Firmware problems include dead-end links in the HTTP based config, garbling and dropping calls (particularly if you mix multi-line usage, call transfers, and using the hold feature), and over a dozen button presses required to forward calls.

I tried to love this phone for two weeks, but it's just not up to snuff. It seems like they discontinued their Snom 220, then needed to push this out the door to fill the void.

I literally gave the receptionist two phones - the Snom 360 and a Uniden UIP-220 because I was so concerned with the 360's stability. After a week, she pretty much only uses the Uniden...

I certainly will not buy nor recommend this phone again until the firmware is tightened up and a manual is available.
222

333This Phone Kicks ass (LINUX)

by , Thursday 30 of December, 2004 [19:07:16 UTC]
This is a truly linux solution. Now I would stop buying othere ata's if I knew you people built one.

I recommend the snom phone above all othere phones on the market. I would rate the 190 up agaist a good lot of the cisco, and othere big wigs. this company is worth your monies. they care. They concentrate on makeing the hardware better and are open with its software.

That to me is a company to support!
222

333Snom190 tips

by , Sunday 12 of December, 2004 [04:41:40 UTC]
Some tips:
- As with any SIP phone, you should upgrade the firmware as soon as you get it. Initially we found the phone would reboot every time it tried to register with our internal SIP registrar (Asterisk server). It turned out that disabling the UPnP feature on the ADSL router which was on the same subnet helped, and a firmware upgrade resolved the problem completely. At http://fox.snomag.de/download/share/ you can see evidence of an active unofficial/beta firmware development by Snom AG. You'll need to use an "alpha" v3 firmware release to get a GMT+10/Brisbane timezone which isn't available in the latest v2 (stable) release.
- Wondering why it takes two button presses to get hands-free mode? The phone seems to assume you have a head-set plugged in, and will try to use it by default. Pressing the speakerphone button will cycle between the head-set and internal speaker. Tell the phone you don't have a head-set and you'll then be able to get the internal speaker the first time.
- There are two ways to dial: 1) Pickup, dial, press OK - OR - 2) Dial, then pickup.
- Ring tone 6 seems to be closest thing to a "normal" ring sound we could find.
- The transfer button seems to behave in an "odd" way. Not sure if this was fixed in the v3.x firmware. I've instructed our users to use the '#' key to initiate a transfer via Asterisk instead - besides, it's one less key to press since 'OK' is unnecessary this way.

A legitimate aesthetic complaint against the Snom 190 would be that the handset is light and sometimes awkward to sit back in its cradle properly. Apart from that, the only complaint from our users I've had is that it has no cool blue backlight like the Grandstream BudgeTone 100s :-)

The speakerphone works very well, supports the voicemail in Asterisk with MWI and the two line display makes it easy to perform certain actions (DND, Voicemail, call log, etc) and also to see what's going on (date/time, CLID, current extn., call timer). We use the five programmable buttons to switch between calls and for speed dial. In case you're wondering, yes, you can use '#' followed by a programmed speed dial button with Asterisk.

The web interface is great - a demo can be seen here.