@hobbit666 said in What Are You Doing Right Now:
Backing up PC as i'm about to reinstall it. See u all after
I did that yesterday on my machine at work.
@hobbit666 said in What Are You Doing Right Now:
Backing up PC as i'm about to reinstall it. See u all after
I did that yesterday on my machine at work.
@dashrender Yep, All the apps are the same, the only difference I can tell is it doesn't include the RDS stuff.
@dashrender said in Office + RDS + Citrix + Licensing = Confused:
@brianlittlejohn said in Office + RDS + Citrix + Licensing = Confused:
It has to include Office 365 Pro applications to support RDS, I believe.
As for as I know - all O365 plans that include local install Office are Office Pro.
Business Premium is what I use for the majority of my users, It includes local install of the office programs, but their accounts will not activate on RDS. I have to use E3 for my few remote users.
It has to include Office 365 Pro applications to support RDS, I believe.
Have you had a renewal for the LE Cert since you updated to 14?
The software only license of Smartnet is usually reasonable(at least for cisco... haha). Have no idea though about this particular device.
@jaredbusch said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:
@brianlittlejohn said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:
@jaredbusch Yea, I can't think of anything else that would cause it either... I haven't upgraded any of the systems that i used LE on to 14 yet to try them.
I found a GoDaddy cert at a client that had a SAN that we were no longer using right now. SO I updated that DNS to point to my test PBX instance and loaded that cert onto my PBX. I changed the active certificate in SysAdmin and told the phone to provision to the new DNS name and it immediately provisioned.
So the problem is definitely the LE cert or cert process.
We at least know where the issue is now.
@jaredbusch Yea, I can't think of anything else that would cause it either... I haven't upgraded any of the systems that i used LE on to 14 yet to try them.
@jaredbusch yes, but this weekend since it is my production system.
@jaredbusch self signed is still installed, but GoDaddy set as default.
@jaredbusch said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:
@brianlittlejohn said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:
What information do you need?
First would be to determine how you got your SSL cert and that it is setup like mine.
Then to confirm the models and firmware levels.
Finally, the best thing would be to drop to an offline conversation and have you whitelist my IP and let me point my phone to your system to confirm your stated behavior.
I used a GoDaddy Certificate, installed through certificate manager and sysadmin module.
Phone is Yealink T46G
Firmware Version 28.81.0.110
Hardware Version 28.2.0.128.0.0.0
FreePBX Version Info
-Current PBX Version: 14.0.1.14
-Current System Version: 12.7.3-1708-1.sng7
Just upgraded my Ubuntu Unifi Beta controller to Ubuntu 17.10
What information do you need?
Listening to this guy talk makes his case worse than just reading it...
So, my T46G at my house will provision over https to FreePBX 14.
@nerdydad said in How to choose public DNS provider for an ISP:
@brianlittlejohn said in How to choose public DNS provider for an ISP:
You are going to use private IP addresses, so all of you subs will be double nat'ed ?
That's what I'm considering. What are the potential problems with this?
It will work for most things, but what if a sub wants incoming traffic?
You are going to use private IP addresses, so all of you subs will be double nat'ed ?
I use the yealink deskphones with the usb wifi in home offices where wifi traffic is minimal. No complaints so far.
I have a feeling it may be an issue with the anonymous shares since they are connecting with a different user. I would remove the anonymous shares and make them protected as a start to troubleshooting.
AOL Instant Messenger is Shutting Down, I didn't realize it still existed.
https://techcrunch.com/2017/10/06/aol-instant-messenger-shut-down/