bkml wrote:
> And my point was that none of this matters if you have a unified call 
> model.

Well, it kinda does matter to me, if I wanted to migrate from 
Asterisk/OpenPBX to Call Manager or something else, because the previous 
PBX could no longer meet the customer's requirements. Unicall or not, 
having PSTN access provided via industry standard SIP/H.323 from an 
external box opens up lots of doors. *That* was my point. No vendor lock-in.

> Where does it say that you have to have BRI/E1/T1 in order to use the 
> Q.931 call model?

Ok, now you're not listening to what I'm saying. That was a new 
paragraph, a new topic in the discussion. I wasn't suggesting Q.931 
could only be run over ISDN.

> Now, you seem to be saying "Don't worry, we'll soon be able to only use 
> the SIP button and simply ignore the other buttons, at least most of the 
> time".

No, I was questioning why businesses are effectively paying twice, for 
something that can these days be combined into a single, managed WAN or 
MPLS connection. And just to be clear, I'm not suggesting that SIP is 
the only thing that could run over that WAN. It's what most VoIP 
providers will want you to use, but if it's run by a conventional telco, 
they may prefer H.323. You can run IAX or MGCP over it if you really 
want. I don't care.

Maybe I should have started a new thread or changed the email subject 
line to make it clearer.

In a perfect world, maybe everybody would use Unicall or Q.931 
signalling. But we know it's not a perfect world. At the end of day, I'm 
just interested in providing a solution that works, and moving on to the 
next paying customer. That Aston Martin won't just buy itself ya' know.

To paraphrase a great American president, I'm just trying to put food on 
my family ;-)
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Reply via email to