Professional Documents
Culture Documents
Release 14.0
Document Version 1
BroadWorks Guide
Copyright Notice
Copyright 2007 BroadSoft, Inc.
All rights reserved.
Any technical documentation that is made available by BroadSoft, Inc. is proprietary and
confidential and is considered the copyrighted work of BroadSoft, Inc.
This publication is for distribution under BroadSoft non-disclosure agreement only.
No part of this publication may be duplicated without the express written permission of
BroadSoft, Inc. 220 Perry Parkway, Gaithersburg, MD 20877.
BroadSoft reserves the right to make changes without prior notice.
Trademarks
BroadWorks and BroadWorks Call Center Agent/Super are trademarks of BroadSoft,
Inc.
Microsoft, MSN, Windows, and the Windows logo are registered trademarks of Microsoft
Corporation. Other product names mentioned in this manual may be trademarks or
registered trademarks of their respective companies and are hereby acknowledged.
This document is printed in the United States of America.
10-BD5020-00
PAGE 2 OF 28
Version
Date
Author
14.0
Created document.
Sam Hoffpauir
14.0
Andrea Fitzwilliam
10-BD5020-00
PAGE 3 OF 28
Table of Contents
1
Purpose........................................................................................................................................7
Overview ......................................................................................................................................8
4.1
4.2
4.3
4.4
4.5
4.6
5
5.1
5.2
5.3
5.4
5.5
5.6
6
6.1
6.2
6.3
References........................................................................................................................................28
10-BD5020-00
PAGE 4 OF 28
Table of Figures
Figure 1 Identity/Device Profile Creation for Generic SIP Connect IP-PBX Identity/Profile Type........ 15
Figure 2 Identity/Device Profile Creation for Generic SIP IP-PBX Identity/Profile Type....................... 16
Figure 3 Identity/Device Profile Creation for Generic SIP TDM-PBX Identity/Profile Type .................. 17
Figure 4 Identity/Device Profile Creation Page ....................................................................................... 20
Figure 5 Trunk Group Add Configuration................................................................................................ 22
Figure 6 Trunk Group Addressing Configuration.................................................................................... 23
Figure 7 Trunk Group Addressing Configuration with Identity/Device Profile ....................................... 25
Figure 8 Trunk Group User Addressing Page ........................................................................................ 26
Figure 9 Trunk Group Addressing Configuration with Identity/Device Profile for Type B and
Type D SIP Connect Non-registering PBX Classifications ............................................................... 27
10-BD5020-00
PAGE 5 OF 28
10-BD5020-00
PAGE 6 OF 28
Purpose
This document provides clarifications and configuration descriptions for inter-working an
Internet Protocol (IP) Private Branch Exchange (PBX) or legacy PBX with BroadWorks for
the Business Trunking solution. This document is a supplement to the BroadWorks SIP
Business Trunking Interworking Guide [1] for partners and operators who want to interface
to PBXs and other remote call control platforms with the BroadWorks Business Trunking
service.
This document is divided into four key sections. The key chapter of this document is
section 6 BroadWorks Business Trunking PBX Configuration. It provides the step-by-step
process to configure BroadWorks to connect to an IP PBX. However, before you can
execute the steps in section 6, there are certain configuration prerequisites that must be
executed. These involve pre-defining the device profiles you use in section 6.
This document contains the following sections:
Chapter 3:
Provides an executive overview of the BroadWorks Business Trunking solution, and
introduces the value of the BroadWorks device profile mechanism for normalizing between
any type of PBX.
Chapter 4:
Provides a background of the six types of device profiles you encounter when deploying
Business Trunking or SIP Trunking. You must be familiar with these devices, and you
must qualify your IP PBXs, integrated access devices (IADs), and session border controls
(SBCs) to understand which of these six profiles you should use. This is a key benefit.
Although there are literally hundreds of Session Initiation Protocol (SIP) implementations
on IP PBXs and IADs, BroadWorks allows you to simplify this space into six device profile
types. (BroadSoft instructs you on which profiles to use for different PBXs on the
BroadSoft Boulevard SIP Trunking page.)
Chapter 5:
Provides instructions on how to create the appropriate device type on BroadWorks, based
on the IP-PBXs and IADs in your service offering.
Chapter 6:
Provides the BroadWorks configuration instructions for creating the BroadWorks Trunk
Group.
10-BD5020-00
PAGE 7 OF 28
Overview
BroadSoft allows you to make SIP Trunking deployment as easy and reproducible as time
division multiplexing (TDM) primary rate interface (PRI) deployment. To achieve this goal,
it is essential to provide end-to-end system configuration guidance, and not just
BroadWorks-specific configuration instructions.
This is an important exercise because a successful SIP Trunking deployment requires the
configuration of four to five separate components:
IP PBX
Configure a Trunk Group and device types on BroadWorks (as explained in this
document).
2)
Configure your access equipment (IP-PBX, SBC, Application Layer Gateway [ALG]).
For information and an up-to-date summary of what profile types to use for each type
of access equipment, go to the BroadSoft Boulevard at
https://www.broadsoft.com/boulevard/Solutions/businesstrunking/sip-trunking.
3)
Configure and customize the SIP Trunking Add-On services (Fixed mobile
Convergence Mobility, Remote Workers, Disaster Recovery, and so on) that
differentiate your offering. For more information, go to the BroadSoft Boulevard at
https://www.broadsoft.com/boulevard/Solutions/businesstrunking/sip-trunking.
10-BD5020-00
PAGE 8 OF 28
4.1
4.2
10-BD5020-00
PAGE 9 OF 28
4.3
4.4
10-BD5020-00
PAGE 10 OF 28
request-URI with the identity of the PBX subscriber, and the host portion of the requestURI with the host portion from the statically configured contact on BroadWorks.
In this classification, an IP PBX or IAD/gateway does not register with BroadWorks.
However, the PBX is statically configured on BroadWorks with the IP address of the PBX
or IAD/gateway. The signaling for this classification is identical to that of a SIP connect
registering PBX classification except for the register.
The PBX routes calls from BroadWorks to the PBX subscribers using the request-URI
header of the INVITE. The request-URI is populated with the statically configured contact
of the PBX and BroadWorks modifies the user portion to contain the Business Trunking
user identity. The PBX ignores the To header for call routing.
For calls originated within the PBX and sent to BroadWorks, the PBX populates the calling
line identity of the PBX subscriber in the From or P-Asserted-Identity header.
The PBX uses the addressing/domain space of the Application Server for populating the
host portion of the SIP URIs in the From, To, P-Asserted-Identity, and Request-URI
headers for calls sent from the PBX to BroadWorks. The PBX or IAD/gateway IP address
is not used by the PBX in any of the addressing headers. The IP address is only used in
the request-URI of the INVITE populated by BroadWorks to send calls to the PBX.
4.5
4.6
10-BD5020-00
PAGE 11 OF 28
subscribers. The contact for each child registration may all have the same addresses or
the contact may be unique for each child registration.
The PBX routes calls from BroadWorks to the PBX subscribers using the request-URI
header of the INVITE. The request-URI is populated with the registered contact of the
PBX subscriber.
For calls originated within the PBX and sent to BroadWorks, the PBX populates the calling
line identity of the PBX subscriber in the From or P-Asserted-Identity header.
The PBX uses the addressing/domain space of the Application Server for populating the
host portion of the SIP URIs in the From, To, P-Asserted-Identity, and Request-URI
headers for calls sent from the PBX to BroadWorks. The PBX or IAD/gateway IP address
is not used by the PBX in any of the addressing headers. The IP address is only used in
the Contact header of the register.
10-BD5020-00
PAGE 12 OF 28
Details
Purpose
Step 1
Step 2
Step 3
Step 4
If the Identity/Device Profile type must be created for the PBX classification, the following
procedure can be used to create the appropriate Identity/Device Profile type for the PBX
classification.
Step
Details
Purpose
Step 1
Step 2
Step 3
Click Add.
10-BD5020-00
PAGE 13 OF 28
Step
Details
Purpose
Step 4
5.1
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type A - SIP
Connect Registering PBX
The Identity/Device Profile type for the Type A - SIP connect registering PBX classification
is Generic SIP Connect IP-PBX.
Note that this is the same Identity/Device Profile type used for the Type B - SIP connect
non-registering PBX. The profile type contains both the registration policy and static
registration policy to accommodate both PBX classifications in a single profile type.
The Generic SIP Connect IP-PBX Identity/Profile type uses the Intelligent Proxy
Addressing Signaling Address type.
The Generic SIP Connect IP-PBX Identity/Profile type must have the following policies:
Registration Capable
PBX Integration
10-BD5020-00
PAGE 14 OF 28
Figure 1 shows the Identity/Device Profile type for the Generic SIP Connect IP-PBX.
Figure 1 Identity/Device Profile Creation for Generic SIP Connect IP-PBX Identity/Profile Type
5.2
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type B - SIP
Connect Non-registering PBX
The Identity/Device Profile type for the Type B - SIP connect non-registering PBX
classification is Generic SIP Connect IP-PBX.
Note that this is the same Identity/Device Profile type used for the Type A - SIP connect
registering PBX. The profile type contains both the registration policy and static
registration policy to accommodate both PBX classifications in a single profile type.
The Generic SIP Connect IP-PBX Identity/Profile type uses the Intelligent Proxy
Addressing Signaling Address type.
The Generic SIP Connect IP-PBX Identity/Profile type must have the following policies:
PBX Integration
Figure 1 shows the Identity/Device Profile type for the Generic SIP Connect IP-PBX.
5.3
Generic SIP IP-PBX Identity/Device Profile Type for Type C - SIP Connect
Registering PBX with Modified request-URI Header
The Identity/Device Profile type for the Type C - SIP connect registering PBX with modified
request-URI header classification is Generic SIP IP-PBX.
10-BD5020-00
PAGE 15 OF 28
Note that this is the same Identity/Device Profile type used for the Type D - SIP connect
non-registering PBX with modified request-URI header. The profile type contains both the
registration policy and static registration policy to accommodate both PBX classifications in
a single profile type.
The Generic SIP IP-PBX Identity/Profile type uses the Intelligent Proxy Addressing
Signaling Address type.
The Generic SIP IP-PBX Identity/Profile type must have the following policies:
Registration Capable
PBX Integration
Figure 2 shows the Identity/Device Profile type for the Generic SIP IP-PBX.
Figure 2 Identity/Device Profile Creation for Generic SIP IP-PBX Identity/Profile Type
5.4
Generic SIP IP-PBX Identity/Device Profile Type for Type D - SIP Connect
Non-registering PBX with Modified request-URI Header
The Identity/Device Profile type for the Type D - SIP connect non-registering PBX with
modified request-URI header classification is Generic SIP IP-PBX.
Note that this is the same Identity/Device Profile type used for the Type C - SIP connect
registering PBX with modified request-URI header. The profile type contains both the
registration policy and static registration policy to accommodate both PBX classifications in
a single profile type.
The Generic SIP IP-PBX Identity/Profile type uses the Intelligent Proxy Addressing
Signaling Address type.
The Generic SIP IP-PBX Identity/Profile type must have the following policies:
10-BD5020-00
PAGE 16 OF 28
PBX Integration
Figure 2 shows the Identity/Device Profile type for the Generic SIP IP-PBX.
5.5
PBX Integration
Figure 3 shows the Identity/Device Profile type for the Generic SIP TDM-PBX.
Figure 3 Identity/Device Profile Creation for Generic SIP TDM-PBX Identity/Profile Type
5.6
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type F Subscriber Registering PBX
The Identity/Device Profile type for the Type F - Subscriber registering PBX is Generic SIP
Connect IP-PBX.
Note that this is the same Identity/Device Profile type used for the Type A - SIP connect
registering PBX and Type B - SIP connect non-registering PBX. The profile type contains
both the registration policy and static registration policy to accommodate both PBX
classifications in a single profile type.
10-BD5020-00
PAGE 17 OF 28
The Generic SIP Connect IP-PBX Identity/Profile type uses the Intelligent Proxy
Addressing Signaling Address type.
The Generic SIP Connect IP-PBX Identity/Profile type must have the following policies:
Registration Capable
PBX Integration
Figure 1 shows the Identity/Device Profile type for the Generic SIP Connect IP-PBX.
10-BD5020-00
PAGE 18 OF 28
6.1
Details
Purpose
Step 1
Step 2
Step 3
Step 4
Click Add.
Step 5
10-BD5020-00
PAGE 19 OF 28
Figure 4 shows an example Identity/Device Profile web page used to add the
Identity/Device profile for use with the trunk group configuration on BroadWorks.
6.2
Details
Purpose
Step 1
Step 2
Step 3
Step 4
Click Add.
10-BD5020-00
PAGE 20 OF 28
Step
Details
Purpose
Step 5
10-BD5020-00
PAGE 21 OF 28
Figure 5 Trunk Group Add Configuration shows the Trunk Group Add web page used for
the Trunk Group configuration.
Once the Trunk Group is created, the next step is to configure the main phone number for
the PBX in the Trunk Group. The main phone number may also be (optionally) configured
with an extension that can be reached by any user in the same group or enterprise as the
Trunk Group.
Step
Details
Purpose
Step 6
Step 7
Click Apply.
10-BD5020-00
PAGE 22 OF 28
Figure 6 Trunk Group Addressing Configuration shows the Trunk Group Addresses web
page used for the Trunk Group phone number and extension configuration.
The final step to configure the Trunk Group is to select the appropriate Identity/Device
profile from the drop-down list. The Identity/Device profile selected should be the one
created specifically for the Trunk Group.
Once the Identity/Device profile has been selected, the main Trunk Group line information
can be configured by populating the phone number of the main line of the PBX in the
line/port field.
The remainder of the Identity/Device Profile addressing configuration is dependent on the
PBX classification. For specific information on how to select and configure the correct
Identity/Device profile addressing for each PBX classification, see the classification details
that follow. The domain portion of the Identity/Device Profile addressing, when present,
should be populated with the domain used for the PBX as applicable based on the
Identity/Device profile selected. This must match the configuration of the PBX.
Step
Step 9
Details
Navigate to the newly created Trunk
Group by clicking on the group name of
the newly created Trunk Group.
Purpose
Obtain the Trunk Group profile.
10-BD5020-00
PAGE 23 OF 28
Step
Step 10
Details
Under the Profile tab in the left-side
navigation, select the Addresses link.
Purpose
Select the Identity/Device profile and
configure the line/port and host.
Click OK.
10-BD5020-00
PAGE 24 OF 28
Figure 7 Trunk Group Addressing Configuration with Identity/Device Profile shows the
Trunk Group Addresses web page used for the Trunk Group addressing configuration
including the Identity/Device profile selection.
6.3
10-BD5020-00
PAGE 25 OF 28
Figure 8 Trunk Group User Addressing Page shows the Trunk Group User Addresses
web page used for associating the user with the Trunk Group.
For Type B and Type D SIP connect non-registering PBX classifications, the contact field
must be populated with the location of the PBX. This is typically set to the PBX main
users phone number with the IP address of the PBX (for example,
sip:2407208427@168.54.23.38). It may be set with an FQDN or other information based
on the PBX configuration requirements.
10-BD5020-00
PAGE 26 OF 28
Figure 9 shows the Trunk Group Addresses web page used for associating the user with
the Trunk Group for Type B and Type D SIP connect non-registering PBX classifications.
Figure 9 Trunk Group Addressing Configuration with Identity/Device Profile for Type B and Type D SIP Connect
Non-registering PBX Classifications
This process for adding users to the Trunk Group may be repeated for each user with an
individual Direct Inward Dialing (DID) configured in the PBX.
10-BD5020-00
PAGE 27 OF 28
References
[1] BroadSoft, Inc. 2006. BroadWorks SIP Business Trunking Interworking Guide,
Release 14.0. Available from the BroadSoft Boulevard at
www.broadsoft.com/Boulevard.
[2] Sibley, C., Gatch, C., IP PBX/Service Provider Interoperability, sf-draft-twgIP_PBX_SP_Interop-sibley-sipconnect, March 2006.
10-BD5020-00
PAGE 28 OF 28