Office 365 Phone System Deployment
-
@scottalanmiller said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
Not being a yealink reseller. How does one get themselves onto the yealink RPS system to add / remove devices from RPS,
AFAIK, you can't. It's a reseller only option.
Pretty much correct. I got a trial account because I didn’t stop pestering. I also used leads from people here.
-
@scottalanmiller said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
I can't seem to find much useful info on this.
Probably because it is horrible
It absolutely is.
-
@scottalanmiller said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
We need to be able to somehow auto provision all the template settings when the Yealink first boot up after a factory reset.
I don't think that you can do that. That's not a normal phone function.
It has been for years. But it requires the RPS.
Without that all you can do is DHCP boot options. Which is obviously local/controlled only.
-
@JaredBusch said in Office 365 Phone System Deployment:
Without that all you can do is DHCP boot options. Which is obviously local/controlled only.
Ahh. Not what I wanted to hear :frowning_face:
-
@360col said in Office 365 Phone System Deployment:
Hmm so how do I push out setting to those yealink phones that remote.
The license for the Yealink RPS is pretty damn cheap. The issue that we are having are regarding O365 SfB as a solution and everything involved with it.
I won't go down the details but it's a bit of a bear to get to do what we need it to do. A traditional PBX would've been better and much cheaper in comparison over any period of time.
-
@JaredBusch said in Office 365 Phone System Deployment:
@scottalanmiller said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
We need to be able to somehow auto provision all the template settings when the Yealink first boot up after a factory reset.
I don't think that you can do that. That's not a normal phone function.
It has been for years. But it requires the RPS.
Without that all you can do is DHCP boot options. Which is obviously local/controlled only.
Yes, that I knew. But he already knew RPS wasn't available and was responding to "need to do it without RPS". Without RPS, it's not an option unless the phones are local.
I know a provider that makes every home office "local" to deal with this. They provide a router and phone for every house to get around that.
-
@DustinB3403 said in Office 365 Phone System Deployment:
I won't go down the details but it's a bit of a bear to get to do what we need it to do. A traditional PBX would've been better and much cheaper in comparison over any period of time.
That is my current view. I would not have bother to even evaluate it with all the current issue I'm seeing. The user experience is no where near a FreePBX solution for our use case.
-
We have hundreds of sites that are remote and being able to just factory reset and it pickups the settings again (regardless of where it is) to a know state is he way to go (with our current solution). Other then the some what fixed cost monthly per user of the S4B (which is actually not fixed if you look at the details).
It will be fun times ahead with the S4B solution... It was sold as part of some other bigger stuff / package so I have to play along due to not being the decision maker.
-
@360col said in Office 365 Phone System Deployment:
We have hundreds of sites that are remote and being able to just factory reset and it pickups the settings again (regardless of where it is) to a know state is he way to go (with our current solution). Other then the some what fixed cost monthly per user of the S4B (which is actually not fixed if you look at the details).
Yeah, that's why the company in question that I dealt with sent out routers with every phone, for exactly that reason.
-
@360col said in Office 365 Phone System Deployment:
@DustinB3403 said in Office 365 Phone System Deployment:
I won't go down the details but it's a bit of a bear to get to do what we need it to do. A traditional PBX would've been better and much cheaper in comparison over any period of time.
That is my current view. I would not have bother to even evaluate it with all the current issue I'm seeing. The user experience is no where near a FreePBX solution for our use case.
It's a Microsoft product, I would not expect them to even be considering making it on par with FreePBX, that's not their style. It'll improve, but they will never attempt to be a market leader. That's not the kind of customer that they go for.
-
@360col said in Office 365 Phone System Deployment:
We have hundreds of sites that are remote and being able to just factory reset and it pickups the settings again (regardless of where it is) to a know state is he way to go (with our current solution). Other then the some what fixed cost monthly per user of the S4B (which is actually not fixed if you look at the details).
It will be fun times ahead with the S4B solution... It was sold as part of some other bigger stuff / package so I have to play along due to not being the decision maker.
You don’t need to worry about that with SfB. The user logs in and it puts their stuff on it.
-
@JaredBusch said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
We have hundreds of sites that are remote and being able to just factory reset and it pickups the settings again (regardless of where it is) to a know state is he way to go (with our current solution). Other then the some what fixed cost monthly per user of the S4B (which is actually not fixed if you look at the details).
It will be fun times ahead with the S4B solution... It was sold as part of some other bigger stuff / package so I have to play along due to not being the decision maker.
You don’t need to worry about that with SfB. The user logs in and it puts their stuff on it.
Users logging into phones can be confusing for them.
-
@scottalanmiller said in Office 365 Phone System Deployment:
@JaredBusch said in Office 365 Phone System Deployment:
@360col said in Office 365 Phone System Deployment:
We have hundreds of sites that are remote and being able to just factory reset and it pickups the settings again (regardless of where it is) to a know state is he way to go (with our current solution). Other then the some what fixed cost monthly per user of the S4B (which is actually not fixed if you look at the details).
It will be fun times ahead with the S4B solution... It was sold as part of some other bigger stuff / package so I have to play along due to not being the decision maker.
You don’t need to worry about that with SfB. The user logs in and it puts their stuff on it.
Users logging into phones can be confusing for them.
SfB should be set up with a PIN. It is really that easy. Even a lawyer can do it.
-
@JaredBusch said in Office 365 Phone System Deployment:
SfB should be set up with a PIN. It is really that easy. Even a lawyer can do it.
Now THAT'S easy!
-
I assume that that is all handled by the SfB specific firmware?
-
@scottalanmiller said in Office 365 Phone System Deployment:
I assume that that is all handled by the SfB specific firmware?
Yes.
You can log in a SfB/Teams Yealink phone with the username and pin or username and password.
-
@JaredBusch said in Office 365 Phone System Deployment:
@scottalanmiller said in Office 365 Phone System Deployment:
I assume that that is all handled by the SfB specific firmware?
Yes.
You can log in a SfB/Teams Yealink phone with the username and pin or username and password.
Okay, that's a cool feature. Kudos to them for making that easy.
-
@JaredBusch said in Office 365 Phone System Deployment:
You don’t need to worry about that with SfB. The user logs in and it puts their stuff on it.
I know about this bit as I have already tried it out on one handset. Saying that our users are not the office type and hardly know how to use a computer and some handsets are purely for making phone calls only. Current solution they don't even need to know anything. Just plug the phone in give it a couple of minutes and dial away without having to even log in.
The bit I was looking for is after loggin in how does one even mass change config of the yealink spread throughout many sites! This is my number one question. You guys already answer that question.
-
@JaredBusch said in Office 365 Phone System Deployment:
You can log in a SfB/Teams Yealink phone with the username and pin or username and password.
MY experience so far. I have managed to get the phone (with S4B firmware) logged in using the web sign in with pin thing. But I had to log in to the handset via IP then initiate the whole process. Not very automated.
Another annoyance is the handset seems to go into sleep mode after which you have to enter pin to get back in to it. I have not been able to find out how to disable it yet. Users remembering pin to the phone which they could previously just pickup and dial. That'll go well! Once again they seem to be designed for office workers who are very UC (Unifi comms) savvy.
-
@JaredBusch said in Office 365 Phone System Deployment:
You can log in a SfB/Teams Yealink phone with the username and pin or username and password.
BTW 99% of our users don't even know their login / passwords (that is not a conversation for this thread or will it ever change). Things get all pre-setup and they just use it.
