Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Survivable Remote vs ESS
- Thread starter mgoston
- Start date
In the Avaya Aura® Communication Manager Survivability Options manual there is a table with embedded on S8300E or a Simplex Survivable Remote on Dell™ PowerEdge™ R620 / Dell™ PowerEdge™ R630 / HP ProLiant DL360p G8 / HP ProLiant DL360 G9
jimbojimbo
Vendor
There are some nuances between a survivable core and a survivable remote which you should be aware of.
A survivable remote supports a branch session manager. A survivable core does not.
A survivable core and a survivable remote can run on servers however the S8300 only supports the survivable remote embedded
profile. This may change in the next release (Aura 10) however still no feature roadmap or technical specs.
If you configure a survivable remote the link between the branch session manager and survivable remote will "standardize" the domain to a single SIP domain when failing over. When configuring a Branch Session Manager with a survivable remote you are not required to configure a link from the CM to the BSM. The configuration of the survivable remote Communication Manager will include the BSM information.
If you configure a survivable core with a session manager you will need to configure the link between the CM Core instances and the Session Manager and configure trunking/routing.
Starting with Aura 7.x all CM/SM/BSM instances are running on top of an ESXi host. ASP120/AVP is the Avaya OEM version. ASP130 is a Dell VMware image. You can also run on customer provided VMware.
A survivable remote supports a branch session manager. A survivable core does not.
A survivable core and a survivable remote can run on servers however the S8300 only supports the survivable remote embedded
profile. This may change in the next release (Aura 10) however still no feature roadmap or technical specs.
If you configure a survivable remote the link between the branch session manager and survivable remote will "standardize" the domain to a single SIP domain when failing over. When configuring a Branch Session Manager with a survivable remote you are not required to configure a link from the CM to the BSM. The configuration of the survivable remote Communication Manager will include the BSM information.
If you configure a survivable core with a session manager you will need to configure the link between the CM Core instances and the Session Manager and configure trunking/routing.
Starting with Aura 7.x all CM/SM/BSM instances are running on top of an ESXi host. ASP120/AVP is the Avaya OEM version. ASP130 is a Dell VMware image. You can also run on customer provided VMware.
- Status
