Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!uwm.edu!wuarchive!texbell!vector!telecom-gateway From: nastar!scott@gatech.edu (Scott Barman) Newsgroups: comp.dcom.telecom Subject: Re: Calling Number Delivery According to Bellcore Message-ID: Date: 20 Nov 89 21:51:02 GMT Sender: news@vector.Dallas.TX.US Reply-To: Scott Barman Organization: Digital Transmission Systems (NAS Development Project) Duluth, GA Lines: 42 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 525, message 8 of 11 In article nvuxr!deej@bellcore. bellcore.com (David Lewis) writes: >One thing to keep in mind is that Bellcore TRs are essentially written >to the industry to provide requirements for manufacturers; the >manufacturers are free to implement products in exact compliance to >the Bellcore TRs or not, as they see fit. In other words, the TRs >specify how Bellcore says the product/service/system *should* work, >which may or may not be the same as the way it *does* work. Caveat on the above (since we've been through these problems here): If you are with a company wanting to do business with the RBOCs, then you should really consider implementing your product/etc. to as close to exact compliance as possible. The question will come up asking if your product is not only Bellcore compliant but even certification of that compliance may be required. If you are not Bellcore compliant, then you will need to demonstrate a clear path for that compliance. I know that we lost a sale to (among a few other things) to a slight lack of Bellcore compliance. Now if you are dealing with some of the smaller carriers, this is not as much of an issue as long as you are willing to comply to their requirements and come close to the Bellcore standards. Sometimes, if you can come up with something unique and first (like a 3/1 cross-connect switch), you can get away with not being exactly Bellcore compliant (however, we still have to show a plan for future compliance). Based on things I've heard, I would suggest that if you are designing a product, the physical standards are very important--especially for the RBOCs. Standards like rack sizes and depth are very important because of the floor plans of many of the central offices already in existance. DISCLAIMER: I am not in charge of compliance here, nor do I speak for the company and I am NOT an expert on Bellcore compliance. What I present here are just impressions while working on a product to be sold to the telecom industry. scott barman {gatech, emory}!nastar!scott