SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Voice-on-the-net (VON), VoIP, Internet (IP) Telephony

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: STK1 who wrote (1441)10/4/1998 9:24:00 PM
From: Stephen B. Temple  Read Replies (3) of 3178
 
Subject: IPfication, a few steps above CT-101

This is an e-mail from Ken Persson via computertelephony.org residing in Sweden. I nice guy to e-mail if you have any questions on The European Telephony Market in general.

Ken's issue this month covers:

1. The IPfication of communication equipment

2. New Links

3. Don't forget

1) The IPfication of communication equipment

One of the clearest trends I see right now is the IPfication of
communication equipment, systems like the PBX, Access routers, faxes etc. gets IP-enabled. The early IP-telephony gateways, all were stand-alone PC-based servers. Connecting a gateway to your current communication infrastructure was an ad-hoc solution. Given that corporations often don't have telecom and datacom skills in one person or even one department made it difficult to implement stand alone gateways.

The migration from the PBX (Private Branch eXchange) to the IP- and
ATM-enabled PCX (Private Communication eXchange) with "integrated
gateways" to both ATM and IP will make it so much easier to implement
IP-telephony. IP-telephony is just another trunk on your PB(/C)X. Building networked PB(/C)X groups will be easy - you may run some systems over ATM, some over IP and others over ISDN - all trunks will give you transparent signalling which will allow you to run applications like centralised operators or virtual Call Centres. How do you network your PBX systems today? It's not easy to do if you have them spread out all over the word - why? You can't buy a VPN service that cover all your sites and you cant afford to buy leased lines between the international sites. With the IP- and ATM-enabled PBXs your networking is far less costly any much easier. No more 24 or 30 line trunk restriction, no more country specific restrictions, say no more a to a lot of things!

The multi trunk featured PBX systems are not far away - two years perhaps. "IP trunks" are here already - both in PBXs and UnPBXs.

Some IP telephony related datacom companies that aim for the corporate
market will find the multi trunk PBXs a bit less funny. They will have a very hard time selling PC- or router-based gateways if they can't offer a unique advantage. It's very hard for someone like Cisco to sell gateway ports to a customer that have to choice between having an integrated gateway on the PBX backplane offering full proprietary network signalling functionality and a router with Qsig at the most. Other advantages of
having an integrated gateway in the PBX: You don't have to buy separate UPS systems, you don't have to pull multiple trunks from the PBX to an external gateway, you don't have to buy extra trunk boards, you don't have to buy separate call accounting systems, you don't have to administrate routing in two places and so on. There are so many benefits to have it all in your PBX it's ridiculous to even suggest you should buy a separate box to handle "just another interface".

The IPfication is not discussed in the media so I really like to hear from YOU, what's your opinion? Send me an email or write a statement in the CT forum or the CT discussion list.

2) Some new interesting links:

theipsite.com - TheIPsite is great on-line resource on IP
telephony

telialight.com - The Swedish PTTs Next Gen Telco company (Swedish)

3) Don't forget

To visit the bookstore at
computertelephony.org

computertelephony.org

Regards
Ken Persson

Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext