Survivable remote servers configuration

Last Updated : Oct 07, 2026 |
Prolog information
Metadata
Keywords:
An Avaya Solutions Platform S8300 or an Avaya Solutions Platform 130 can either be configured as a primary call-processing controller or as a survivable remote server, which is also called a Local Survivable Processor (LSP). The survivable remote server can take over call processing if the primary call-processing system, such as another Avaya server, is unavailable for any reason. Such reasons include network failure or server problems. The Avaya Solutions Platform S8300 or Avaya Solutions Platform 130 can either be the primary or the survivable remote server. This server is set up to operate as a primary or a standby survivable remote server during the configuration process using a web server interface. The license file determines the mode in which the server operates, and the Configure Server web page provides supplementary instruction.
If the Avaya Solutions Platform S8300 or Avaya Solutions Platform 130 loses contact with its gateway, the gateway retains its last status until Link Loss Delay Timer (LLDT) expires. The default for LLDT is five minutes, however, this interval is administrable using the Link Loss Delay Timer (minutes) field on the IP-Options System Parameters screen. After LLDT expires, the system removes all boards and deletes all the call-processing information. However, if the gateway loses contact with the Avaya Solutions Platform S8300 or Avaya Solutions Platform 130, the gateway tries to reconnect for a period of one minute. If reconnection fails, the gateway then tries to connect with another server in its controller list. If the primary server is a survivable remote server, it starts looking at the top of its MGC list to reconnect to the primary server. Otherwise, it starts down the list of alternative servers. When a functional Avaya Solutions Platform S8300 or Avaya Solutions Platform 130 is located, the gateway indicates the server of its current call state, and the server maintains the connections until the users disconnect.
If the primary call-processing server goes offline and a survivable remote server is available as a standby unit, call processing happens as follows:
  • IP telephones and gateways that were previously using the primary server try to register with the standby server for call processing, provided that they have been administered to do so in the controller list by using the set mgc list command.
  • The standby server, which is the survivable remote server, goes into license error mode, and then starts call processing. The standby server cannot preserve any calls set up by the primary server. IP telephone connections can stay up until the call is completed if they are shuffled, however, no features are supported on the call.
    Note:
    The license error mode runs for up to 30 days, and if the problem is unresolved, the system goes into No License Mode and administration and some commands are restricted.
  • If the standby server is rebooted, all devices return to using the primary server for call-processing service. Any calls in progress on the standby survivable remote server are dropped when the reboot occurs as the change back to the primary server is not call preserving.
The survivable remote server provides full functionality and feature.
For more information about Avaya servers, see Avaya Aura® Communication Manager Hardware Description and Reference.