OK Preston I’ll bite. I read your blog and I am trying to figure out if what you are selling is actually helpful - or is it basically nothing more than a disguised advertisement to push people into replacing phones.
If I switch over to using ClearlyIP sip trunks but I do NOT wish to replace instruments with “Brandable IP phones” or any other phones for that matter, and all my phones are fixed location phones, am I screwed or not?
Let’s play some “what do I need” games to get a handle on this:
Scenario #1: 1 dispatchable location (a small office, single floor, front and back door,) 4 extensions on a FreePBX system with 1 SIP trunk, 1 callback location because all 4 phones are programmed to ring when a call comes in the trunk.
Scenario #2 2 dispatchable locations, 1 is “first floor” 1 is “second floor” 12 extensions scattered over a group of offices on both the first floor and the second floor. Slightly larger office. 4 ClearlyIP SIP trunks. I assume that means 12 emergency callback profiles?
Scenario #3 3 physical locations, tied together via private fiber networks, 6 phones on one location that has 6 cubes in a large room, 8 phones on another location that has 6 offices scattered throughout a larger facility, 40 phones at the last location located in 35 offices that are on 3 floors. I assume this means 54 callback profiles, lets say 13 dispatchable locations. The organization has 10 ClearlyIP sip trunks.
In all 3 scenarios, NONE of the phones can move without IT help. (organizational rules)
In Scenario 2 and 3, how do you allocate Callback profiles to the sip trunks? Does the customer just say “gimmie 10 trunks and 54 callback profiles” and the profiles just float around in between the trunks? Or do you have to pay for 540 callback profiles and duplicate each 54 on each trunk because you never know when a specific extension is going to seize a specific trunk? And how does the trunking module tie into all of this?
I don’t see how this ISN’T tying up a minimum of 54 DIDs on Callback profiles. Unless you have a “pool” of DID’s that you allow to “float” around in between customers, and you have some proprietary protocol that communicates from the FreePBX module to you that passes location info, but then once a “floating” DID is assigned to a customer how long does it stay assigned? What if the 911 call center calls back 3 hours later and the DID has “floated” to another customer?
As AdHominem said, this regulation really looks to me like it’s only answerable with statically assigned DID numbers. Even if you have some super-kewel method of dynamically assigning DIDs to your SIP trunks or something, nobody else in the industry is going to do it. Not other SIP providers and definitely not other PRI providers. The telco industry is absolutely going to find some de-facto way of answering this regulation that uses standardized currently available technology, and it just seems that DIDs are the obvious choice that will just drop in. And they are also pretty cheap anyway. And it works with the current programming in existing digital PBXes. For example I have a customer with 100 Nortel digital phones and a Nortel key system that is older than dirt. I’d love to replace it. But their existing “phone guy” sells replacement extensions to them for $200 a phone. So, to them they view this system as having $200,000.00 of phones and they won’t even discuss replacing it. If I bring this law up to them as part of a pitch to dislodge their phone guy and move them off this system, their phone guy will just kick back that the system can do DIDs and it’s being fed by a PRI right now from Frontier Telephone. All that Frontier would have to do to make them compliant is setup a website where they can type in each DID and the address and location it’s in and their phone guy can get them a DID block from Frontier and badda bing. I can’t pitch them 100 “Branded IP” extensions at $200 a pop, don’t you see?
Like most government regulations dealing with technology nobody has bothered thinking about the unintended consequences. And I will point out that Greg Walden is one of my home state’s representatives and 80% of the states residents think he’s an idiot, the only ones that love him are the pro-gunner Bible-thumpers in Eastern Oregon, and that is a fact.
The unintended consequence I see is this is just going to force hundred of new prefixes into every state as each prefix exhausts DID’s, so they can open a new prefix and start assigning DIDs out of it. And when they did this in California the Telcos just loved it because they could then charge LD charges for direct dialing people who live 5 miles away. You know, I had 1 customer last year who after they moved, the NEVER BOTHERED to install deskphones - every single one of their employees had a company-paid cell phone. And the lines were cheap. I would not be surprised if the flood of demand for DIDs, the excuse of new prefixes to gouge the public, is just going to accelerate the move away from deskphones in businesses to cell phones.