It is recommended to plan the SLS coverage and gather information from CM before creating the SLS administration data set at the Branch Gateway command line. Strategic selection of the stations and trunks that participate in SLS can ensure that vital communications are spared interruptions caused by network outages.
Important:
Since you can administer your system for SLS either from the SAT or from the Branch Gateway CLI, the two administration tasks must be synchronized with common data and port usage as well as system-defined capacities. For example, if a physical DCP station port number 10 is not administered on the CM server, even though the Branch Gateway’s SLS engine has that port administered, the port is unusable during SLS operation on the Branch Gateway. This is because the hardware port configuration on the media modules is initially configured by CM in subtending gateway mode, by using the H.248 control channel to push information down to the Branch Gateway.
