@JaredBusch said in Yealink W52P config files:

@fuznutz04 said in Yealink W52P config files:

This was the most secure way that we could think of to securely provision remote phones. (aside from VPN that is.) I'd be interested to hear how you or others securely provision remote extensions. Is there a better way?

The answer there varies.
For most companies, I would used raw HTTP(S) with IP based whitelist as a first choice. Why? Because they have fixed IP blocks.
If you are dealing with roving users, then yeah, it is harder to decide what to do.

Yep, we use HTTPS with username/password, but not a whitelist currently. Once the phones are provisioned, the chances of them needing re-provisioned is fairly low, unless their is a configuration change that we want to push out. As of now, everyone would automatically get the new info. If I implement a whitelist, then it would become more difficult to push an update to roaming users, but certainly not a deal breaker, seeing as we could just update the whitelist as needed.

How often do you have your phones checking the provisioning server for changes?

@JaredBusch said in Yealink W52P config files:

@fuznutz04 said in Yealink W52P config files:

@JaredBusch said in Yealink W52P config files:

@fuznutz04 said in Yealink W52P config files:

Well, after hours of troubleshooting, pizza, and analyzing Wireshark packet captures, I've come to the conclusion that something with our local provisioning server is causing the Yealink phones not to get their entire configuration files, and of course, can not properly apply any parameters to the phone. Our Developer who wrote the website code is reviewing it now. The strange thing is that the provisioning server works perfect with Grandstream phones, and Polycom phones...Yealink seems to dislike it however.

Why would your provisioning server be a webserver? Most of the time this is a TFTP server. I mean HTTP and HTTPS are supported, as well as FTP and TFTP, but TFTP is standard.

The Yealink admin guide shoes the examples in the appendix. Are you sure you put the URL correctly into the phone in the first place?

Since we have cloud VPS servers, I wanted a secure way to send provisioning information to the phones. We achieve this by using HTTPS. We tried to use the build in EndPoint manager for provisiining via HTTPS, but it was lacking some features that we wanted. Plus, with a centralized provisioning server, we have a central point for the files and if we ever choose to move VPS providers, making changes to all config files and pointing to a new server would be quick and almost transparent to the client.

Yes, the URL was correct. We direct every client to the central server, and then based on thier individual login, we direct them to their specific files. The code that does this operation on the web server does not play well with the Yealink phones for some reason. We cleaned it up and think we are almost out of the woods. Probably a good thing...eyes getting heavy.

You left out some serious information in your initial post then. Notably HTTPS != "web server" as well as you are authenticating to the webserver somehow?

That is all horribly complicating things and leads me to question the over all goal that led to this design. But you apparently have the developers working around the issues already.

In the original post, I was convinced it was the configuration files. It's only after I did some packet captures that I realized that the phone wasn't getting the configuration file completely.

This was the most secure way that we could think of to securely provision remote phones. (aside from VPN that is.) I'd be interested to hear how you or others securely provision remote extensions. Is there a better way?

@JaredBusch said in Yealink W52P config files:

@fuznutz04 said in Yealink W52P config files:

Well, after hours of troubleshooting, pizza, and analyzing Wireshark packet captures, I've come to the conclusion that something with our local provisioning server is causing the Yealink phones not to get their entire configuration files, and of course, can not properly apply any parameters to the phone. Our Developer who wrote the website code is reviewing it now. The strange thing is that the provisioning server works perfect with Grandstream phones, and Polycom phones...Yealink seems to dislike it however.

Why would your provisioning server be a webserver? Most of the time this is a TFTP server. I mean HTTP and HTTPS are supported, as well as FTP and TFTP, but TFTP is standard.

The Yealink admin guide shoes the examples in the appendix. Are you sure you put the URL correctly into the phone in the first place?

Since we have cloud VPS servers, I wanted a secure way to send provisioning information to the phones. We achieve this by using HTTPS. We tried to use the build in EndPoint manager for provisiining via HTTPS, but it was lacking some features that we wanted. Plus, with a centralized provisioning server, we have a central point for the files and if we ever choose to move VPS providers, making changes to all config files and pointing to a new server would be quick and almost transparent to the client.

Yes, the URL was correct. We direct every client to the central server, and then based on thier individual login, we direct them to their specific files. The code that does this operation on the web server does not play well with the Yealink phones for some reason. We cleaned it up and think we are almost out of the woods. Probably a good thing...eyes getting heavy.

Well, after hours of troubleshooting, pizza, and analyzing Wireshark packet captures, I've come to the conclusion that something with our local provisioning server is causing the Yealink phones not to get their entire configuration files, and of course, can not properly apply any parameters to the phone. Our Developer who wrote the website code is reviewing it now. The strange thing is that the provisioning server works perfect with Grandstream phones, and Polycom phones...Yealink seems to dislike it however.

Does anyone have a working copy of the configuration files needed to provision a Yealink W52P DECT phone. I'm having issues with provisioning the phone. I have my own provisioning server, and I can see the phone requesting the files. (both the y000000025.cfg file, as well as the MAC.cfg file.) The server responds and serves them to the phone, but none of config parameters are applying to the phone. I have a feeling the config files are messed up somehow, and not applying any of the parameters. I downloaded the blank templates from Yealink, so I wouldn't think there would be any issues, but in any case, it's not working.

Does anyone have a copy of a working config ?

@JaredBusch said in EdgeMAX Alpha release v1.8.5alpha1:

@fuznutz04 said:

@JaredBusch said:

@fuznutz04 said:

@JaredBusch said:

@fuznutz04 what type of OpenVPN? Site to site? I have wrote up that process before back when I was learning EdgeOS originally. I can update it and make it clean.

No, I was looking to set it up as a server so I can remote in via the OpenVPN client. Basically, secure access to my home network when I need it. Right now, my experience with Open VPN is limited to the package available for PFSense. I'd like to do the same on my ERX.

I have that setup also. both as a certificate based and as a password based. at different sites. I really need to make new documentation anyway.

You would be hailed as "the man" if you produce that content and share it.

It is already on the ubnt forum. buried somewhere in posts I made 2 years ago there.

Just needs updated and reposted.

Hey Jared,

Any update on this new guide? I'm getting ready to replace a PFSense router with an ERX and the only thing holding me back is a working OpenVPN solution for the ERX.

@LAH3385 said in Voice/Greeting recording for generic holidays and other messages...Where do you get them from?:

@fuznutz04
I want him!!!! I neeeeeeed John Bailey!!!! I say he's probably my second best voice next to Morgan Freeman.

Yeah, either of those two guys would work. Really, I would settle for either of them on my personal voicemail greeting.

It needs to be John Bailey...

Youtube Video

@scottalanmiller said in VoIP - Location & latency:

@fuznutz04 said in VoIP - Location & latency:

@scottalanmiller said in VoIP - Location & latency:

@fuznutz04 said in VoIP - Location & latency:

3. Hardware - Memory and storage-
   I typically like to see 2 GB of RAM on a FreePBX box for example. What about storage? Does a VPS with an HDD have a greater chance of call quality issues VS a VPS with SSDs

SSDs serve no purpose unless you are dealing with some insane load of voicemails. Calls do not go through the disk in any way so the disk is not important.

2GB of RAM is excessive unless you have tons of callers or are running lots of extra stuff. We normally use 512MB - 1024MB and have systems that have run for a long time on 256MB without issue. 2GB is just wasteful.

That's my experience as well with HDDs. I've always ran my PBX on HDDs and haven't had any issues. Some VPS providers that offer "VoIP" servers, have both HDD options as well as SSD options. Is this purely a marketing thing to get more money? Like you said, unless the disk is being pounded by call recordings or voicemails, most people wouldn't even notice anything.

With the latest distro of FreePBX, they are adding new things all the time that we don't use, but eat up memory. When we were running with 1 GB, we were approaching the limit and swapping to disk. We've since disabled many un-used modules, but still use a bit of memory. For example, i just spun up a fresh FreePBX box, and without doing anything else besides update, it is already using 366 MB of RAM.

What is the output of free -m ?

total used free shared buffers cached
Mem: 1877 572 1305 0 52 153
-/+ buffers/cache: 366 1510
Swap: 2047 0 2047

@scottalanmiller said in VoIP - Location & latency:

@fuznutz04 said in VoIP - Location & latency:

3. Hardware - Memory and storage-
   I typically like to see 2 GB of RAM on a FreePBX box for example. What about storage? Does a VPS with an HDD have a greater chance of call quality issues VS a VPS with SSDs

SSDs serve no purpose unless you are dealing with some insane load of voicemails. Calls do not go through the disk in any way so the disk is not important.

2GB of RAM is excessive unless you have tons of callers or are running lots of extra stuff. We normally use 512MB - 1024MB and have systems that have run for a long time on 256MB without issue. 2GB is just wasteful.

That's my experience as well with HDDs. I've always ran my PBX on HDDs and haven't had any issues. Some VPS providers that offer "VoIP" servers, have both HDD options as well as SSD options. Is this purely a marketing thing to get more money? Like you said, unless the disk is being pounded by call recordings or voicemails, most people wouldn't even notice anything.

With the latest distro of FreePBX, they are adding new things all the time that we don't use, but eat up memory. When we were running with 1 GB, we were approaching the limit and swapping to disk. We've since disabled many un-used modules, but still use a bit of memory. For example, i just spun up a fresh FreePBX box, and without doing anything else besides update, it is already using 366 MB of RAM.

@scottalanmiller said in VoIP - Location & latency:

Latency: 200ms is the line. Pretty much anything under 200ms you can't hear. Of course you don't want to go for 190ms and then get hit with spikes or find that you have sensitive users. You want the best latency that you can get within reason. But we don't worry about 20-40ms at all. That's so fast that no one cases.

You only care about staying below 200ms and you only care about total time, not just one component of the path. It's end to end that matters. So if moving the VPS causes more delay between extensions but less delay to the trunk it might be break even. You have to look at the whole thing.

In 1 example, I have a total of about 75 MS from office to PBX to trunk.

Since the board seems to be on a VoIP trend lately, (which I 100% approve of ) I'd like to get some discussion regarding hosted servers, physical location, and latency.

Let's assume you are using a VPS server.

1. Latency & physical location -
   What is considered to be an acceptable latency from your office, to the hosted VPS? 40 ms works, but 20 ms is better. How much of a difference does that 20 ms make in regards to call quality?

2. Physical location -
   This goes hand in hand with the entire latency chain, (Office, to PBX, to SIP provider to PSTN) It goes without saying, that the closer the PBX is to you, the better it is due to latency. Also, the closer the SIP provider is to your PBX, the better, for the same reason. I'd like to see some real world examples of what other IP pros are doing/seeing in this area. For example: Where is your office located, where is your VPS located, what is the latency in-between. Same goes for your PBX to SIP provider. Where is the SIP provider physically, and what is the latency in-between? Perhaps we could start a list where everyone could add to?

EDIT:
3. Hardware - Memory and storage-
I typically like to see 2 GB of RAM on a FreePBX box for example. What about storage? Does a VPS with an HDD have a greater chance of call quality issues VS a VPS with SSDs

Awesome! Can't wait to get this installed.

VoiceBunny.com has a lot of different talent on their site. Haven't used them yet, but keep them in my back pocket in case a client wants some professional voice.

@JaredBusch said in DECT base stations & Additional handsets:

@fuznutz04 said in DECT base stations & Additional handsets:

So the YeaLink phones are the better route? The W52P model? Grandstream also makes a few wireless DECT phones as well.

IMO, Grandstream is the bottom of the barrel on quality in the VOIP world. They are super cheap and often the quality suffers because of it. I know tons of hobby VoIP people love them because of the cost.

I love Yealink because of the combination of their price and quality.

There are certainly cheaper phones and there are certainly higher quality phones.

But Yealink hits that sweet spot of solid quality for reasonable cost.

That's good info, thanks. I've been working with Grandstream for a little while now and they just came out with a new firmware that revamped their interface and seemed to improve the UI a lot. However, I have no complaints about Yealink either. I haven't used their DECT phones yet, but their price is very similar compared to the VTech phones. I believe a vendor recommended this VTech phone a few months ago, but I haven't really done any research on it. Glad I asked.

So the YeaLink phones are the better route? The W52P model? Grandstream also makes a few wireless DECT phones as well.

@scottalanmiller said in MangoCon Is official!:

@fuznutz04 said in MangoCon Is official!:

Really want to go to this.

Wife already has a work conference that weekend.

(......goes quietly and sulks in corner.)

Doesn't that make it the perfect time to sneak away for a conference of your own?

Yes, it would be perfect...but 2 little kids at home say otherwise. It's not over yet...just have to see if I can recruit some grandparents for babysitting.

@MattSpeller said in MangoCon Is official!:

@fuznutz04 said in MangoCon Is official!:

Really want to go to this.

Wife already has a work conference that weekend.

(......goes quietly and sulks in corner.)

Lets have our own conference! With Liquor! and Blackjack!

I'm in!

@Minion-Queen said in DECT base stations & Additional handsets:

We have done up to 5 extensions with only one base station, using the Yealink YEA-W52P Business IP HD DECT Cordless Phones. These are really easy to setup and really easy to use. No issues at all that we have come across.

Any experience with the VTech VSP600s?

Really want to go to this.

Wife already has a work conference that weekend.

(......goes quietly and sulks in corner.)