Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 -- Ignore unavailable to you. Want to Upgrade?

To: Stephen B. Temple who wrote (2054)	12/3/1998 1:59:00 AM
From: Frank A. Coluccio	Read Replies (1) \| Respond to of 3178

Stephen, just getting around to reading some of your posts. Your question: >> why would telco-negotiations be involved in the first place? << After reading this article, I was left wondering myself what exactly was on the author's mind. He wasn't too clear, IMO, about the dilemma, nor was he clear on the space that he was trying to satisfy. I suspect that there are a number of restrictions and negotiating points that he could be referring to that we can speculate about. I'll offer some, but would prefer to hear from some of the CTI developers who I know are looking in here, who might offer some corrections and clarifications. CTI apps that require access to advanced information network, or AIN, features, such as those which permit "follow-me" capabilities, need to have access to multiple carriers' data bases. These databases are often associated with switching control points (SCPs), and each time one of these databases is accessed (or "dipped" into) for a pointer or a file on a customer's whereabouts, say, or even for an 800 re-direct in the case of a virtual call center operation (remote or "work-at-home" attendants), there is an associated charge on a per dip basis. And some calls may require multiple dips per session. These per dip charges can be quite sizable when low volumes are involved, and they are invariably negotiable with SS7- and carrier-type providers. Similar considerations exist for SLDB, or subscriber line data base, information at the end office level, when the incumbents will make this information available. Then there are other directory services and discrete carrier code considerations that are more esoteric to the craft, such as those which are used for least cost routing (not necessarily for the PBX, rather, at the central office machine level). There can be huge deltas between the costs of one supplier's dip and the next's. The difference of a cent or so, per call lookup, can make or break the ROIs that developers have to prove in, when extended over time. Other things that occur to me off the top of my head that could be a problem for a CTI developer might have to do with calling pattern limitations, and the fact that in order to route or re-route certain types of calls, it is still a requirement that the switching or routing entity be a licensed carrier. There can be fuzzy lines distinguishing these, however. I'm sure if you use your imagination, you will come up with some scenarios that fit this bill... [g]