Page History

...

On the local side, the network layout displays the Sonus SBC receiving requests from SIP endpoints that are configured in the BroadSoft server. From the BroadSoft side, it shows the Sonus SBC forwarding the requests to the Broadsoft server. This diagram also displays the reverse path for the responses.

How to configure the SBC to interoperate with BroadSoft messaging

...

1. Create a new BroadSoft Signaling Group (for details on how to create a Signaling group, see Creating and Modifying SIP Signaling Groups).
2. From the SIP Mode drop down box, select Basic Call.
3. From the Agent Type drop down box, select Access Mode.
4. From the Interop Mode drop down box, select BroadSoft Extension.
5. In the Registrant TTL box, enter 3600 (default entry).
6. For all other configuration elements, see Creating and Modifying SIP Signaling Groups.

7. Save the configuration.

   Panel
   borderStyle none
   Caption 0 Figure 1 Create BroadSoft Signaling Group Image Modified

Step 2. Create Local Registrar Signaling Group

...

1. Create a new Local Registrar Signaling Group. This is the destination Registrar Signaling Group (the Registrar database is queried to find contact details of the user, since BroadSoft users are registering endpoints). For details on how to create a Signaling Group, see Creating and Modifying SIP Signaling Groups.
2. From the SIP Mode drop down box, select Local Registrar.
3. From the Agent Type drop down box, select Access Mode.
4. From the Interop Mode drop down box, select Standard.

5. For all other configuration elements, see Creating and Modifying SIP Signaling Groups.

   Panel
   borderStyle none
   Caption 0 Figure 1 Create Local Registrar Signaling Group Image Modified