PBX Info :: Your Free PBX, PABX and Telephone Information Resource - View Single Post - CS2000 Geo Redundant
View Single Post
Old 03-28-2008, 03:30 PM   #2 (permalink)
rhack
Junior Member

Activity Longevity
2/20 20/20
Today Posts
0/0 ssssss170
Location: Chlt-NC
Rep Power: 6rhack is on a distinguished road
Country:
Not sure what you mean by CVM. I have worked on a geo CS2100, and in the last 4 months have worked thru the process of converting a SL100 SuperNode and an SL100 SNSE to CS2100 systems (non-geo).

1.) I believe geo systems are now configured with 4 ERS8600's. There were issues with the ability of IP phones, and gateways losing connectivity to the core under some types of failure conditions. I think by going to a 4-8600 configuration it prevents outage conditions.

2.) In a geo split, only the core that is located where the MS resides connects to the MS. The geo site with the MS is equipped with two SAM21 shelfs. One shelf only contains an MC card. The MC (Message Controller) has two ports on it. One port goes to MS0 the other to MS1. The "primary" SAM with the Call Agent also has an MC connected in the same manner. Per the geo planning guide, if you lose your core at the host/tdm site the core at the remote/geo site won't do much for you. Personally, I think geo split is best when you are either all IP, or you have MG9K's in front of your LGC's/LTC's, and you are using IP trunk gateways. This way, the whole backbone is IP and the components can talk to either core. No more ENET or MS.
rhack is offline   sendpm.gif Reply With Quote