On Aug 6, 2006, at 7:52 PM, Daniel Swarbrick wrote:
the point I was trying to make is that once you have an
external box handling your PSTN, with H.323/SIP trunk to your PBX,
it's
very easy to migrate away from PSTN in future, and run your H.323/SIP
trunk over some kind of WAN.
And my point was that none of this matters if you have a unified call
model.
Why do businesses pay for a high speed internet feed, which can easily
have QoS implemented on it in the case of "corporate" WAN options (as
opposed to consumer ADSL), then pay for multiple BRI or channelised
E1/T1?
Where does it say that you have to have BRI/E1/T1 in order to use the
Q.931 call model?
Let me give you an example.
Asterisk shouldn't have any such thing as chan_foo, chan_bar,
chan_baz and the Dial command shouldn't be Dial(FOO/xyz), Dial(BAR/
xyz), Dial(BAZ/xyz). Those are implementation details that should be
hidden in the lower layers of a library.
Imagine somebody was trying to sell you a telephone set which has a
POTS button, an ISDN FLAVOUR 1 button, and ISDN FLAVOUR 2 button, and
ISDN FLAVOUR 3 button, a VOIP SIP button, an H323 FLAVOUR 1 button,
an H323 FLAVOUR 2 button, an IAX button etc etc etc and if you want
to make a call, you first have to know which of those buttons to
press before you can start dialing someone.
That's the Asterisk model and unfortunately, Freeswitch is heading
there, too.
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".
I am saying "We shouldn't have any of those buttons in the first
place, none of them, not even the <insert your favourite> one".
That's what Unicall is about.
It has nothing to do with whether or not you have physical ISDN
circuits, nor even if any of your calls are handed off to any ISDN
circuit.
rgds
benjk
___________________________________________________________
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal
http://uk.docs.yahoo.com/nowyoucan.html
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
