Hi, I have a question, which is not really operational but rather technological one. It concerns the Internet dial-in access. I hope there are several dial-in ISPs, not only transit ones, among you. Let me explain the situation. We are a "emerging" LEC in Czech Republic. Our aim is to build a wireless access network for data and telephony services. The wireless base stations will be connected to the voice and data switches, which will be interconnected via SDH network together. The problem is following: We expect a huge amount of Internet dial-in users, which will connect to the ISPs via our regular telephony service. We need to find a device, which will be placed between the base station and voice switch and capable to detect (based on the called number) the call to the ISPs, terminated it (e.g. completely bypass the voice switch) and provide some data interface, which will be connected to the ISP on the ordinary IP level.We know, in US you are facing the same problems with this kind of un-needed voice switches overload, your help will be very usefull for us. My question is: Do somebody of you use some kind of this rerouting or DXCs bypass and with which devices or is this functionality included directly in the voice switch ??? Only pointers to vendors are quite sufficient - Nortel´s "Internet Thruway" can be a example. Thanks very much.
At 12:12 PM 13-08-97 +-200, Jan Novak wrote:
Do somebody of you use some kind of this rerouting or DXCs bypass and with
which devices or is this functionality included directly in the voice switch ???
Only pointers to vendors are quite sufficient - Nortel´s "Internet Thruway" can be a example.
If you are dealing with an existing voice switch, I don't think you have much choice but to handle it with that voice switch vendor's product. Third party solutions seem to have too much to do with handling call recognition to be cost effective. Both Nortel and Lucent have announced plans to deal with data calls by off-loading from the first voice switch onto a packet network. Frankly, I don't understand enough about voice switch architecture to know how well that deals with first-switch overloading, but it will certainly deal well with the inter-office trunk overloading that is prevalent in the US architecture. Another idea that you should seriously consider is "always on ISDN". The concept is to use all three BRI ISDN channels as a dedicated link to a single ISP. It may be possible to set things up in the voice switch to allow more than one ISP to play in this game, but the idea is to use the D signaling channel as a dedicated low speed link between the premise and the selected ISP. The two B channels are brought on as data is presented for transport. The idea is to make the circuit switching happen on the time scale of Internet connection association (ie, TCP setup and teardown). This gives the data user the same or better call characteristics as the voice caller, thereby easing the load on the switch and allowing it to multiplex more efficiently than it does when the data circuits stay nailed up almost continuously. I would suggest that you talk to your switch vendors about how to implement "always on ISDN" on their switches and then think carefully about how to price this service. (In other words, you had better not keep the same pricing as current per-call tariffs, but come up with either a flat rate or a usage based on traffic measure so that users don't have to worry about the cost of thousands of calls per month.) You can compare this to the front-end offloading approach and pick the one that seems most cost effective and scalable. In fact, why not do both? If Czechoslovakian phone companies aren't totally focused on preserving a monopoly of obsolescent phone services as here in the US, then perhaps innovative circuit switched data services are feasible? If not, you could always swim uphill with xDSL or cable modems. :-) Hope this helps. --Kent Kent W. England Direct: 650.596.6321 VP of Technology Company: 650.596.1700 GeoNet Communications, Inc. Fax: 650.596.1701 555 Twin Dolphin Drive mailto:kwe@geo.net Redwood City, CA 94065 http://www.geo.net --- note area code change from 415 to new 650 ---
Dans son message, Kent W. England ecrivait:
If you are dealing with an existing voice switch, I don't think you have much choice but to handle it with that voice switch vendor's product. Third party solutions seem to have too much to do with handling call recognition to be cost effective. Both Nortel and Lucent have announced plans to deal with data calls by off-loading from the first voice switch onto a packet network. Frankly, I don't understand enough about voice switch architecture to know how well that deals with first-switch overloading, but it will certainly deal well with the inter-office trunk overloading that is prevalent in the US architecture.
I recommend exploring TR-303 technology based on Bellcore's TR-NWT-000303 specification. Everybody can do tandem trunk relief and far-end office relief now. It is the near-end office relief that is being tackled now.
data services are feasible? If not, you could always swim uphill with xDSL or cable modems. :-)
I won't get into that here ... ;-) -- Sharif Torpis (storpis@pbi.net) Network Engineering Pacific Bell Internet PGP Key at http://www-swiss.ai.mit.edu/~bal/pks-toplev.html
participants (3)
-
jan.novak＠aliatel.cz -
Kent W. England -
storpis＠pbi.net