Duplicating and Forwarding an Incoming SIPREC INVITE

The device can duplicate and forward an incoming SIPREC INVITE request to multiple destinations (i.e., SIPREC-to-SIPREC session). These SIPREC messages are created by some other remote entity (e.g., another SBC) and the device simply duplicates them and forwards them to specified destinations. The destinations may include, for example, Session Recording Servers (SRSs) or agent-assist contact center bots like those deployed by AudioCodes Live Hub. This capability is especially useful for SIP User Agents (UAs) that don't support SIPREC INVITE message duplication.

When the device duplicates the incoming SIPREC INVITE message, it also copies the original XML metadata to each duplicated SIPREC INVITE sent to the configured destinations.

Configuration of this feature is like standard SIPREC configuration(see Configuring SIP Recording Rules). In addition, for the device to copy the original XML metadata to the duplicated SIPREC INVITE messages, you need to configure the 'Use Initial Incoming INVITE for re-INVITE' [SBCKeepInitialIncomingINVITE] parameter in the IP Profiles table to Enable:

● It is strongly recommended to configure a dummy Test Call endpoint when implementing duplication and forwarding of SIPREC INVITE requests to multiple destinations. Without this configuration, if the first destination (SRS) to which the device forwards the INVITE request doesn't respond, the device will not proceed to forward the requests to the remaining destinations. To avoid this behavior, use the Test Call Rules table to configure a dedicated Test Call endpoint (see Configuring Test Call Endpoints). Make sure to configure the Test Call with the following settings:
✔ Configure the 'Endpoint URI' parameter.
✔ Configure the 'Call Party' parameter to Called.
✔ Configure the 'Play' parameter to Disabled.

You can use Message Manipulation to manipulate the destination URI of the outgoing leg so that its routed to the Test Call's Endpoint URI.

● This feature doesn't support the active-standby SIPREC feature.
● The device duplicates and forwards the SIPREC INVITE request only after receiving a SIP 200 OK response from the specific destination. (In standard SIPREC operation, duplication occurs immediately upon receipt of the INVITE.)