Remote router phone

Status
Not open for further replies.

goinghosted79

Silver Partner
Basic Certified
Joined
May 3, 2022
Messages
81
Reaction score
7
Looking at setting up a new customer on 3cx but they have a main office and one remote user. Can I put in a raspberry pi for the office sbc then ship the remote worker a t53 setup as a router phone? Is this a straightforward process
 
In my mind, a pi is just another device to manage and another expense. I do not know what phones you have now, but I would use a router phone rather than a pi. The only advantage to a pi is that nobody is likely to unplug it and move it to another cubicle forgetting that other users are dependent on it working. Even better than a router phone is the option of making all the phones router phones -- then there are no dependencies on anything other than the user's own phone.

I'm getting older (65), yet this old dog has learned that a physical phone is rarely better than a soft phone (at least for people who spend most of their day at their desk). I understand that some customers/users just want a physical phone. But as a business person, YOU do not want them to use a physical phone. A physical phone requires more work to setup, it's another point of failure, there is almost no margin (profit), and you have to deal with RMAs (returns). One RMA costs more than you make on the sale of 10 phones. Why would you want to do that? The only reason to put in physical phones is if you WANT the extra billable labor. That's a horrible reason.

Can you pre-prevision a router phone? Sure. Try it. Configure it, and take it home and plug it in. It's an easy thing to test.

Maybe I'm unrealistic, but I think physical phones should be replaced with soft phones in every place where there is a computer/laptop/cell phone/tablet. MAYBE in a manufacturing facility, warehouse, or lobby where there is not a computer available, a physical phone makes sense, but for an office worker, physical phones are an antiquated technology hanging on for just a little longer until all the luddites are all gone.

As an implementer of technology, you want your staff to scale. After all, LABOR is likely your biggest single expense. That means putting in technology that never fails (unless the whole phone system fails). That's why the industry has moved to hosted servers. You set it up and don't really have to worry much about the infrastructure (blades, SANs, power, cooling, wiring, insurance, etc.). Not to mention the expense of all the training and certifications that go with managing that infrastructure. You want to focus on solutions rather than running around hassling with phone issues IMO.

I do not want to sell, implement, or manage physical phones ever again. Back in the day we used to make $400 per phone. Now we make $5 per phone if we are lucky. Screw that. If your customer/user wants a physical phone, they better have a REALLY good reason for it.
 
Last edited:
lol love it! And I understand where you are coming from. This is for a small law firm with about 20 or so users, not sure if you deal with a lot of lawyers but they are very picky in my experience and this firm wants a phone on every desk. We lease the phones to them so we can make a little money after the first year on a new device
 
Oh dear. You are a brave soul if you work with law firms. I am painting with a broad brush when I say there is no more difficult client than a law firm. I have learned to run the opposite direction when they approach us. It is just too easy for them to play the "lawsuit" card every time anything does not go the way they demand. Heaven help you.

If they want a phone at every desk, and the PBX is hosted, then make them all router phones.
 
@goinghosted79 Also consider a Linux VM in the office…no worries about Pi/Arm support or hardware. But yes a router phone is fine. Note a given extension can have only one router phone.
 
Is there an issue doing what VoIP tools suggested and making them all router phones?
 
No issue at all. Every phone being a router phone is great
 
  • Like
Reactions: goinghosted79
Is there an issue doing what VoIP tools suggested and making them all router phones?
Two I can think of which may or may not be an issue:
If you enable trunk outage notifications and the office drops you'll get an email for every phone.
Normally audio for internal calls stays behind the SBC but with each phone separate, internal calls go to the 3CX server and back.
 
Is there an issue doing what VoIP tools suggested and making them all router phones?
An issue I can think of, would be if any phones are required to be Hotdesking Phones. Hotdesking Phones cannot be setup as a router phone.
 
  • Like
Reactions: Evolute IT
Two I can think of which may or may not be an issue:
If you enable trunk outage notifications and the office drops you'll get an email for every phone.
Normally audio for internal calls stays behind the SBC but with each phone separate, internal calls go to the 3CX server and back.
isn’t that how a hosted company like ring central or nextiva would work too, minus the notifications.

Just trying to see if there is a down side, I don’t mind putting in a sbc and just having the one remote phone set as a router phone. I could use T46u phones that way
 
isn’t that how a hosted company like ring central or nextiva would work too, minus the notifications.
Yes essentially. Probably immaterial for a small company and notable for a large one or slow Internet.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet