Geo redundant srg

[harps08]

Assume Rls 6.0

If I were to deploy the primary cs,ss at site A, with a secondary call server, ss at site B. Would it then be possible to add an additional gateway at Site C and configure it to be a Geographically redundant Survivable remote gateway?

Perhaps there is a better solution? Site A, Site B, and Site C are all using 39xx series digital telephones and the customer is looking to have a redundant solution where all locations could survive on there own if their connection to the WAN was lost.

 

[biv343]

Site C could be a survivable media gateway (SMG) which replicates the database from one of the main sites. A SMG is tied to it's "host" call server. When the WAN link goes down, the local call server will go into active mode and the MGC in that SMG will register locally, and they will have access to whatever resources live in that media gateway or gateways as the case may be.

If site B was a media gateway off site A, and site A fails, then the MGC in site B can also register to the call server in site C, assuming the WAN connectivity is still there. If site B also needs to survive on it's own in the event of a WAN failure, then it would need to be a SMG off of site A as well. When the system is running normally, then the call server at site A controls all call processing for all three sites. The call servers/sig servers at the remote sites only go into an active state in the event of WAN failure or a failure of the primary call server.

A survivable remote gateway is based off the BCM platform and only supports IP sets or analog sets at the remote facility. A SMG is based off the CS1000 platform.

 

[harps08]

The only problem is that the customer is looking to re-use their digital telephones and they would not be supported on an srg right?

 

[biv343]

Exactly. If they replace them with IP phones, they can go with a SRG. If they want to keep the digital sets, then the system needs to become a SMG. This assumes that you want one database across all the systems. If you don't mind maintaining three different databases, you could tie all three sites together via IP trunks.