Hi Mike, in your message to ftth you noted:
"I'm assuming SBC and PacBell did not volunteer to be hooked up to the DSNET gateway. What'll be more interesting is how they got into a cableco headend. 1996 Telecom Act doesn't require an MSO to cooperate."
I realize there may have been some confusion concerning whether we are talking about CLWKs or WIN. Nevertheless, what follows addresses the use of DSET gateways, and your interpretation of why and how service providers "inter-connect" with one another.
DSET's eLoclizer gateway product is _not_ a substitution for transport and switching infrastructure. I.e., these devices do not replace, or function in lieu of, switches, servers, routers, whatever.
I attempted to clarify what they are doing in my reply to ftth's (the person) initial post on this topic. The eLocalizer ties together OSSes from competing, or partnering, service providers. The way they tie into one another could be through an IP connection, or through direct ATM/T1 links. These are "hot links", in the sense that you touch the balloon in SP #1 and a change is effected in SP #2.
From their web site:
"OSS Interconnection
dset.com
DSET electronic-bonding gateways interconnect the operations support systems (OSSs) of competitive carriers and their trading partners to automate a full spectrum of processes basic to turning on and maintaining servies for customers."
See my reply to ftth.
Message 15127836
--------
So, in retrospect, and to address your post to ftth, yes the startup provider does have a requirement to procure their own network elements, unless, of course, they fall back to one of the more traditional forms of leasing space (partitions) from a host, such as a master source of some kind (such as a blockbuster repository), or competing, carrier, as is often done. But the latter has nothing or very little to do with the use of the DSET unit. HTH.
FAC |
