FreePBX and Sangoma phones, advantages?


(Claudio Pelosi) #4

everything seems very interesting, I will propose the D65 for testing


(Itzik) #5

After installing hundreds of Sangoma Phones, I disagree with that.
Zero touch provisioning is something that wasn’t mentioned, and works wonders.

Finally, you mentioned that he should “stay away” but you didn’t mention why. So I will ask. Why is that?


(Charles Darwin) #6

I bought a 705s a year ago and was very, very disappointed. For many years I used Cisco 7975 and 8961 phones with freePBX and became tired of patching Asterisk.
Both Cisco phones have VERY good audio, when used with g722 codec (I hate alaw/ulaw) and the hardware is of highest quality.
When I first used the Sangoma s705, I thought it is a joke. The audio is like super cheap (in comparison to Cisco) and the phones required a reboot every month or so.
The Sangoma phone apps have the design of a former-East-German app and a latency which is not acceptable…whereas the Digium visual voicemail for the D65 is super cool and user friendly. That’s the reason why I deactivated Sangoma Endpoint Manager and used the Digium phone module to configure the D65.
The only downside of the Digium/Sangoma D65 is that you are supposed to use the phonebook of the Digium phones module. If you want to use the freePBX contactmanager you need a conversion script…


(Jared Busch) #7

I would not suggest stay away, but I would suggest testing it yourself.

I personally found the S-series to be slow and a bit flaky. I had no issues with sound quality.

The Phone Apps are horribly slow to use. I did not continue suing them long enough to figure out if it was the phone or the app itself that was slow. It did not matter really as whatever the cause, the end user experience was poor with it.

Regarding flaky, the BLF would not stay consistently displayed after a reload of the config. It would require a reboot for it to be brought back. It did not do it every time, but often. That is just silly. Again, I did not continue to use the device long enough to troubleshoot.

This kind of stuff should have had feedback before being released.

Maybe it is better now, I do not know. The S505 (or S500 I forget) that I have is still sitting powered off on the shelf in my office.

Compared to the Yealink T4X series that was current at the time, it simply was not worth the extra cost with those issues for the minor good features that it had over Yealink.

I get that Sangoma needs/wants a revenue stream to fund all the development for both the FOSS projects they lead as well as development of commercial solutions. I’m just not sure if their own line of phones was really the best choice. Or maybe there just was not enough R&D done to make it seem like it was a well designed device.

But it has now been 5 years since they acquired Schmoozecom and only a little more than a year since they acquired Digium. Personally, I am hoping they combine the Digium line and the Sangoma lines into a single GOOD phone line in the nearish future.


(Jared Busch) #8

This is overrated. I can do the same thing with a solid DHCP scope setup and any model of phone. No need to even deal with a remote provisioning system to point devices to my local install.

Zero touch is a super nice thing for the rare instance where you drop ship a phone from your VAR straight to a remote home user where you have no IT control.

From a reseller point of view, it can also be a super good thing if they don’t stage things first. I do get the positive use cases.


(Charles Darwin) #9

Here is a link to a video of the visual voicemail of a Sangoma/Digium D65:

Once you switch a D65 phone on, you instantaneously realize that the Digium dev team is/was superior to Sangomas previous dev team (most left Sangoma already).
That‘s the reason why I am very optimistic regarding the future of Sangoma. It seems some of the former Digium devs replaced the ones who left Sangoma last year…


(Itzik) #10

I disagree. We dropship these phones to users all over the world working from home or tiny offices with no real network management. These phones are plug and play once configured with Zero Touch Provisioning.


(Charles Darwin) #11

A Digium/Sangoma D65 discovers a freePBX/Asterisk server automatically during startup too, if one uses the Digium phones module DPMA.


(Jared Busch) #12

No, it requires a RPS, no different than Sangoma phones, or any other brand that has this feature.

The RPS has all the information that tell the devices where to go to get their provisioning information.

There is no magic. So when you have a controlled network you can already do this. Where this shines, as I clearly pointed out, is when you don’t have a controlled network.


(Brian Ladd) #13

I really want to like the S505. I ordered 20 of them. Had to pull all of them back from deployment. Within 2 weeks, 4 of them were boot looping and RMA’d (which Sangoma handled speedily, I must add). 2-3 others would just not stay registered. I 2nd the laggy interface. Audio quality is not as good as Yealink or even old Cisco SPA504’s. Customer feedback was lukewarm on the ones that did work.

Installed some cheap Grandstream GXP-2135’s on the same PBX, same LAN, same WAN…and they work like a champ.

I have to say, if you put a Sangoma S505 and a Yealink T46S next to each other, I’m picking the T46 every time.

Again, I want to like the S505, but I just don’t. have confidence in them.


(Aaron) #14

The Sangoma phones are just rebranded HTEK phones. Buttons in slightly different places but the software running them is the same. Ive met the HTEK guys, drank with them etc. They did not reveal they manufactured them although I asked. Sangoma left the model number of the EHS adapter the same though which was my first clue, then I saw the software was the exact same.

http://htek.com/products/UC900_Series/index.html


(Charles Darwin) #15

You have to be specific…you are talking/writing about the inferior Sangoma S-series phones…interesting, if true.
But the Sangoma/Digium D-series phones are definitely phones designed by Digium…


(Jared Busch) #16

HTEK is the manufacturer of the S-series phones, yes.
Simply rebranded, no.


(Tom Ray) #17

It’s Sony guts.This is what you want.


#18

I have two Sangoma S500. They work and do their job, but it’s really not a phone I’ve actually liked at any time. It feels clumsy and everything is slow. Build quality is ok, but more sturdy than nice looking. The display has bad viewing angles.

Compared to a for example the Snom D765/D785 or a Mitel 6873i, they are just worlds apart (those cost more, but actually not a lot more). Sure, better FreePBX integration would be nice, but in the age of iPhone and highend Android phones, I really cannot ask anyone to live with a a desk phone which is slow, clumsy and has a display that is at best “ok”.

At least the Sangoma S705 now has Bluetooth (finally). But those phones are hard to get here in Germany and I won’t risk getting stuck with one if the Bluetooth implementation turns out to be unreliable. It’s not like they are available on Amazon and I can just send one back if it sucks.

Oh and yes, the latency of the phone apps: That feels like a 2400 baud Modem from 1990. Really really bad.


(Jared Busch) #19

I think you nailed the feel of using the phone apps quite well. Going to remember this


(D E) #20

One thing I’ve found with my Digium phones (that I’m hoping will be fixed at some point) is that call flow control based on the free/busy/away status of the phone doesn’t work as advertised. I’ve also found that a simple graphic on a D70’s display seems to have slowed down the entire menu system. Otherwise very happy, but it took a long time to get to this point. :slight_smile:
I actually enjoyed it, though!


(Mike Waldron) #21

I rolled out about 30 Sangoma S500s before moving on to Yealink T46S/G, which is what I sell now exclusively (in addition to paid EPM). My problems with Sangoma phones:

  • Sketchy firmware - Last one I tried a few weeks ago made the handset volume way too loud, had to roll it back
  • Failure rate is worse than Yealink
  • Slow interface
  • In past firmwares G722 codec created high send volumes, so I only deploy G711 on these devices.
    Send Volumes
  • Could never get a sidecar to work properly

With all that said, they are reliable enough for day to day, but not worth the cost of free phone apps and EPM. While visual voicemail is nice, my clients don’t seem to care. Most have voicemail to email which bridges the gap.


(christrati) #22

Just to add some additional feedback. I initially started with Sangoma S300, S305, S400 and S705s. The biggest complaints I had were in regards to delay when dialing and microphone volume on the handset. Based off of using them for a couple of years, they are at least holding up. The S705s have been the ones we’ve had the most issues with, mainly when performing firmware updates and issues with dialing.

In terms of the comments about the Sangoma phones being slow, make sure you changed the following setting:


It was enabled by default and always slowed down the loading of any apps. I also had to turn off BLF Alerts, as that would cause a beep and delay as well. With those two changes, the phones were much more responsive and comparable to Yealinks.

Overall, I ended up using Yealinks in a majority of our locations, as the build quality was better and the microphone picked up better. We have lots of users that tend to hold the microphone portion close to their neck, so the Sangoma’s are basically muted and the Yealinks work a little better.

In terms of failures, I purchased about 100+ Sangoma phones and haven’t had to return one yet. On the flip side, we purchased about 200+ Yealink and have had to return 4 due to failures. We’ve only been using the Yealinks for a year.

In terms of usage, I liked the S305 for a basic wall phone. The Yealink T41S is what I use for a majority of our general locations. Then we have the Yealink T46S for places that need extra BLF keys.

Hopefully this helps!

Chris


(system) closed #23

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.