Page History

...

• Ribbon SBC SWe Lite
• SBC SWe Lite License 
  • This interop requires the acquisition and application of SIP sessions. Refer to Working with Licenses for more information.
• NICE Engage Platform
  
  • NICE Engage platform SIPREC server running on 4.1 version or above.
    
  • Licenses for the required number of recording sessions.
  • NICE Dispatch Integration Services running on the SIPREC server.

...

To install and run the SBC SWe Lite on the VMware ESXi, refer to Installing SBC SWe Lite on VMware ESXi.

SBC SWe Lite Configuration

...

For more details on Licenses, refer to Working with Licenses.

Import Trusted Root CA Certificates

...

Configure Media Profiles

...

Signaling groups allow grouping telephony channels for routing and shared configuration. They are used for routing calls and selecting Call Routes.

From the Settings tab, navigate to Signaling Groups (Add SIP SG).

...

• Attach the Sip Profile you created earlier.
  • Specifies the SIP Profile for this Signaling Group.
• Select the Agent Type as Back-to-Back User Agent.
  • The SBC maintains the state and participates in all SIP signaling between both endpoints.
• Attach the SIP Server Table "UAC". 
  • Specifies the SIP Server Table for this Signaling Group.
• Select the appropriate Media List.
  • Specifies the Media List this Signaling Group uses.

...

• Enable SIP Recording and attach the Recording Server Table created for SIP recording.

  • When the SIPREC is enabled for the specific Signaling Group, this field allows you to select an entry from a SIP Recording Table, using the drop-down list. This list is populated from the entries configured in the SIP Recording table. For details, refer to Creating and Modifying Entries in the SIP Recorder Table.

• Select Ethernet 1(IPv4) as the Signaling/Media Source IP
  • Specifies the Logical IP address for receiving SIP messages. Use this address as the source IP for all SIP messages, leaving the SBC SWe Lite or SBC 1000/2000 through this Signaling Group.

...

Transformation Tables facilitate the conversion of names, numbers, and other fields when routing a call. They can, for example, convert a public PSTN number into a private extension number or a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table and is available for user selection. Transformation tables are also configurable as a reusable pool that Action Sets can reference.

To Create a Transformation Table

...

Configure Call Routing Tables

...