You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

The 

Unable to show "metadata-from": No such page "_space_variables"
now supports SUBSCRIBE/NOTIFY requests for BroadSoft compatibility (SIP endpoints use the SUBSCRIBE/NOTIFY mechanism to get notifications about a specific resource from other endpoints). The Interop Mode option in the SBC Signaling Group configuration enables the SBC to passthrough SIP messages such as NOTIFY, SUBSCRIBE, and REGISTER. These messages are also forwarded to the BroadSoft server.

Through configuration (detailed below), the SBC uses the SUBSCRIBE/NOTIFY mechanism to support the following Advanced Phone Services and Access Device Services (Call Control) features:

Advanced Phone Services

  • Busy Lamp Field
  • Feature Key Synchronization
  • Shared Call Appearance

Access Device Services (Call Control)

  • Call Waiting
  • Call Hold
  • Blind Transfer
  • Attendant Transfer
  • Local Conference
  • Network Conference
  • Call Forwarding

For specific configuration of the Access Device Services (Call Control) features, please refer to BroadSoft and/or the endpoint configuration documentation.

Network View

A BroadSoft (BroadWorks) server maintains voice mail information for all of its registered users. When a user receives a voice message, the BroadSoft server communicates this information in a NOTIFY request  to users. These messages then pass through the Sonus SBC as shown below in the network layout.

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

In order for the SBC to pass through BroadSoft NOTIFY/SUBSCRIBE messages, you must create two Signaling Groups (Phone-side and BroadSoft-side) within the SBC. These Signaling Groups receive, respond, and forward requests from SIP endpoints that are configured in the BroadSoft server. The information below details how to configure these Signaling Groups.

Step 1. Create Broadsoft Signaling Group to receive Message status

The BroadSoft Signaling Group in the SBC is configured to receive message notifications from the BroadSoft server. Create this Signaling Group as follows: 

  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.

Step 2. Create Local Registrar Signaling Group

The Local Registrar Signaling group in the SBC is configured to accept NOTIFY/SUBSCRIBE messages from SIP endpoints. Create this Signaling Group as follows: 

  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.

 

 

  • No labels