Question: can a CopperRocket bridge (an unhacked one, not a Hack-o-Rocket) work with a non-CM SDSL or IDSL line?

Answer: absolutely not.

Question: why not?

Answer: in the case of SDSL it should be fairly obvious, as the SDSL flavor is quite different at the physical layer. The CM flavor is Flavor B, most others are ATM. Even if some other DSLAM also uses Flavor B, the data rates will probably be different, and there will be no CM pulse train to indicate which one it is.

But even if the physical layer happens to be compatible (which will be more likely with IDSL), there would still be virtually no chance of the CopperRocket working with any other DSLAM. The rocket encapsulates all bridged Ethernet packets in CM 1483, and like all CM CPE, it relies heavily on CMCP.

The last point needs to be re-emphasized: the CopperRocket needs not just a Copper Mountain line, but one using the CM 1483 bridged encapsulation. What would happen if you connect it to a CM SDSL line configured for the routed RFC 1490 encapsulation? I don't recommend that you try: it might complain loudly via CMCP packets, the ISP would see them and might switch your line from the elite RFC 1490 routed encapsulation to the CM 1483 bridged one, reducing you to a regular user.

Again all of the above assumes a standard unhacked CopperRocket. Our Hack-o-Rocket is a whole different story.