Back-to-back configuration checklist

Last Updated : Apr 25, 2023 |

In the following table, the first task refers to the configuration of Avaya SBC in the Core network. The rest of the tasks refer to the configuration of Avaya SBC in the DMZ network.

For more information, see Multiple Session Manager configuration checklist.

Note:

Remote workers must register to IP address of Avaya SBC in DMZ.

No.

Task

Notes

1.

Configure Avaya SBC in the Core network.

Use the multiple Session Manager configuration checklist.

2.

Configure Avaya SBC in the DMZ network.

For more information about configuring SBC in DMZ, see the previous section.

If there are no remote workers configured to get the service from DMZ SBC directly, the Enable heartbeat field in the Server Configuration feature corresponds to Core SBC 1 and Core SBC 2.

2a.

Configure server interworking profile.

Clone the avaya-ru server interworking profile and name it avaya-ru-multism. The server interworking profile configuration is same if you are using the same EMS to manage Avaya SBC in remote location and Avaya SBC in DMZ.

In Timers tab, set the Trans Expire field to 4 seconds. This is to support FAST RESPONSE TIMEOUT.

In Advanced tab, set Record Routes to None.

2b.

Configure server.

Server configuration corresponding to primary Session Manager and secondary Session Manager point to the corresponding external IP address of the Core Avaya SBC.

Note:

Repeat this step for each Core Avaya SBC that you deploy.

Do not configure server configuration for Presence server.

Ensure that you enable heartbeat so that Avaya SBC sends heartbeats to Session Manager. The heartbeats are used to detect whether a Session Manager is available.

2c.

Configure topology hiding profile.

2d.

Configure a reverse proxy for file download.

See Creating a reverse proxy relay service for file or firmware download.

2e.

Configure an Application Relay to support IM for remote workers.

See Configuring application relay for IM.