Thursday, March 09, 2006

ISDN BRI & Cisco ::: Bad Combination

Well, its not a troll, nor would i like to cribb on my blog.
However ISDN & Cisco don't mate well.
We have legacy hardware which have Leased Circuit & ISDN as backup for a remote site to connect to main Site.

Recently the management decided to replace the legacy hardware with the Cisco Routers.
Well for some sites the ISDN works perfectly on a c2821, whereas for others the same config on the another c2821 with same IOS doesn't work.

I am certain , cisco would be prompt in pointing that we get the line checked.
Despite their best support & excellent documentation, We still have to suffer when it comes to ISDN.
But beleive you me, the fact that the moment we plug our ISDN lines back to the legacy equipment, the, line JUST WORKS !!!!!!!!!!!.

Whereas , on c2821 , we have to log in to the router & issue clear int bri 1/o etc to get the status on the cisco ACTIVE.
Since our migration, we have had severe heart burns, when the leased lines have failed & ISDN hasn't fired.
ON many a times, we have had to request the remote site coordinator to reboot the cisco router & then the ISDN would work. No....... we cant ask remote cooridinator to login to the router & clear the interface status.


So my question to Cisco Lovers & in general ISDN users on cisco to help me out
How do you cope with your share of problems with ISDN on cisco.

I wish to know what would you do when the remote site goes offline completely ( no ISDN, no Leased Line) to get the ISDN to ALWAYS connect to main site when Leased Line fails.

No comments: