BW BusinessTrunkingConfigurationGuide R140

Business Trunking Configuration Guide
Release 14.0
Document Version 1
220 Perry Parkway

Gaithersburg, MD USA 20877
Tel +1 301.977.9440
Fax +1 301.977.8846
WWW.BROADSOFT.COM
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.
BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE
2007 BROADSOFT INC.
10-BD5020-00
PAGE 2 OF 28
Document Revision History

Release
Version
Reason for Change
Date
Author
14.0
Created document.
October 29, 2007
Sam Hoffpauir
14.0
Edited and published document.
November 13, 2007
Andrea Fitzwilliam
2007 BROADSOFT INC.
10-BD5020-00
PAGE 3 OF 28
Table of Contents
1
Changes between Release 13.0 and Release 14.0.................................................................6
Purpose........................................................................................................................................7
Overview ......................................................................................................................................8
BroadWorks Business Trunking PBX Classifications..........................................................9
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
Type A - SIP Connect Registering PBX Classification...............................................................9

Type B - SIP Connect Non-registering PBX Classification ........................................................9
Type C - SIP Connect Registering PBX with Modified request-URI Header
Classification.............................................................................................................................. 10
Type D - SIP Connect Non-registering PBX with Modified request-URI Header
Classification.............................................................................................................................. 10
Type E - Device Addressing PBX Classification...................................................................... 11
Type F - Subscriber Registering PBX Classification ............................................................... 11
BroadWorks Identity/Device Profile Types for PBX Classifications .................................13
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type A - SIP Connect
Registering PBX ........................................................................................................................ 14
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type B - SIP Connect
Non-registering PBX.................................................................................................................. 15
Generic SIP IP-PBX Identity/Device Profile Type for Type C - SIP Connect
Registering PBX with Modified request-URI Header............................................................... 15
Generic SIP IP-PBX Identity/Device Profile Type for Type D - SIP Connect
Non-registering PBX with Modified request-URI Header ........................................................ 16
Generic SIP TDM-PBX Identity/Device Profile Type for Type E - Device
Addressing PBX ........................................................................................................................ 17
Generic SIP Connect IP-PBX Identity/Device Profile Type for Type F - Subscriber
Registering PBX ........................................................................................................................ 17
BroadWorks Business Trunking PBX Configuration..........................................................19
Create Identity/Device Profile for the Trunk Group.................................................................. 19
Create Trunk Group .................................................................................................................. 20
Add Users to Trunk Group........................................................................................................ 25
References........................................................................................................................................28
2007 BROADSOFT INC.
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
2007 BROADSOFT INC.
10-BD5020-00
PAGE 5 OF 28
Changes between Release 13.0 and Release 14.0

This is a new document in Release 14.0. However, this document is applicable to
Release 13.0 as well.
2007 BROADSOFT INC.
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.
2007 BROADSOFT INC.
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:
BroadWorks Application Server (Trunk Group)
Session Border Controller (optional)
IP PBX
Application Layer Gateway (optional)
BroadWorks and/or Third Party Add-On applications (link to Boulevard)
BroadSofts Key Advantage

BroadWorks is specially designed to normalize between PBX variants. Just as it does
with Hosted PBX/IP Centrex applications, BroadWorks is smart enough to differentiate
between different types of access devices. Furthermore, configuration of access device
profiles is a simple process on BroadWorks.
Therefore, to integrate a PBX with SIP Trunking, you simply select the appropriate profile
type of the PBX when configuring BroadWorks.
Finally, to make this process even simpler, BroadSoft has worked with scores of IP-PBX
vendors throughout the industry, and classified all PBX types into a limited set of six types.
This document explains these types, shows how to create these device profile types on
BroadWorks, and then provides simple instructions on how to configure SIP Trunks on
BroadWorks.
Following is the three-step process that shows how to configure BroadWorks SIP
Trunking:
1)
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.
2007 BROADSOFT INC.
10-BD5020-00
PAGE 8 OF 28
BroadWorks Business Trunking PBX Classifications

BroadWorks supports both IP PBXs and TDM PBXs via an IAD or gateway, via a SIP
interface. BroadWorks has configurable policies to support the vast variety of addressing
models, which an IP PBX or IAD/gateway may use when interfacing with BroadWorks
Business Trunking. Additionally, BroadWorks also supports configurable policies on
handling a variety of mechanisms for call redirections within the public switched telephone
network (PSTN), including redirections to external voice mail/unified messaging from the
PBX.
To determine which policies to apply on BroadWorks to support the varying IP PBX and
TDM PBX configurations, the IP PBX or TDM PBX via an IAD or gateway are placed into
different classifications. These classifications are then mapped into configurations on
BroadWorks.
The following classifications are used to characterize the inter-working of the IP PBX or
TDM PBX via an IAD or gateway with BroadWorks:
4.1
Type A - SIP Connect Registering PBX
Type B - SIP Connect Non-registering PBX
Type D - SIP Connect Non-registering PBX with Modified request-URI Header
Type E - Device Addressing PBX
Type F - Subscriber Registering PBX
Type A - SIP Connect Registering PBX Classification

From the BroadWorks SIP Business Trunking Interworking Guide [1], a SIP Connect
Registering PBX maps to a parent registration for the IP PBX or IAD/gateway covering all
PBX subscribers.
In this classification, an IP PBX or IAD/gateway sends a single REGISTER with the
contact of the IP PBX or IAD/gateway representing all of the PBX subscribers served by
the PBX. This method is referred to as a parent registration, in which the IP PBX or
IAD/gateway is the parent registering on behalf of the children, that is, the PBX
subscribers.
The PBX routes calls from BroadWorks to the PBX subscribers using the To header of the
INVITE. The request-URI is populated with the registered contact of the PBX.
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.
4.2
Type B - SIP Connect Non-registering PBX Classification

From the BroadWorks SIP Business Trunking Interworking Guide [1], a SIP connect nonregistering PBX maps to a static parent registration for the IP PBX or IAD/gateway
covering all PBX subscribers.
2007 BROADSOFT INC.
10-BD5020-00
PAGE 9 OF 28
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 To header of the
INVITE. The request-URI is populated with the registered contact of the PBX.
the request-URI of the INVITE populated by BroadWorks to send calls to the PBX.
4.3

Classification
From the BroadWorks SIP Business Trunking Interworking Guide [1], a SIP connect
registering PBX with modified request-URI header maps to a Per-Business Trunk Group
configuration for the IP PBX or IAD/gateway covering all PBX subscribers. This
classification is identical to the Type A - SIP Connect Registering PBX classification with
the exception that the PBX routes calls from BroadWorks within the PBX using the
request-URI rather than the To header. BroadWorks must populate the user portion of the
request-URI with the identity of the PBX subscriber, and the host portion of the requestURI with the host portion from the registered contact received from the PBX.
In this classification, an IP PBX or IAD/gateway sends a single REGISTER with the
contact of the IP PBX or IAD/gateway representing all of the PBX subscribers served by
the PBX. This method is referred to as a parent registration, in which the IP PBX or
IAD/gateway is the parent registering on behalf of the children, that is, the PBX
subscribers.
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 and BroadWorks modifies the user portion to contain the Business Trunking user
identity. The PBX ignores the To header for call routing.
the Contact header of the Register.
4.4
Type D - SIP Connect Non-registering PBX with Modified request-URI

Header Classification
From the BroadWorks SIP Business Trunking Interworking Guide [1], a SIP connect nonregistering PBX with modified request-URI header maps to a Per-Business Trunk Group
configuration for the IP PBX or IAD/gateway covering all PBX subscribers. This
classification is identical to the Type B - SIP Connect Non-registering PBX classification
with the exception that the PBX routes calls from BroadWorks within the PBX using the
request-URI rather than the To header. BroadWorks must populate the user portion of the
10-BD5020-00
PAGE 10 OF 28
2007 BROADSOFT INC.
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.
or IAD/gateway. The signaling for this classification is identical to that of a SIP connect
registering PBX classification except for the register.
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.
the request-URI of the INVITE populated by BroadWorks to send calls to the PBX.
4.5
Type E - Device Addressing PBX Classification

From the BroadWorks SIP Business Trunking Interworking Guide [1], a device addressing
PBX maps to a Per-Business Trunk Group configuration for the IP PBX or IAD/gateway
covering all PBX subscribers. This classification is similar to the Type D - SIP Connect
non-Registering PBX with Modified request-URI Header classification with the exception
that the PBX uses device addressing rather than proxy addressing. Device addressing
means that the PBX populates the host portion of the addressing headers (for example,
From, To, P-Asserted-Identity, request-URI) with the IP address of the device rather than a
domain configured in BroadWorks for calls sent to BroadWorks.
or IAD/gateway.
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.
The PBX uses the addressing/domain space of the device 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 used by the
PBX in populating all of the addressing headers.
4.6
Type F - Subscriber Registering PBX Classification

From the BroadWorks SIP Business Trunking Interworking Guide [1], a subscriber
registering PBX maps to an individual child (per PBX subscriber) registration.
In this classification, an IP PBX or IAD/gateway sends a REGISTER with the contact of
the IP PBX or IAD/gateway for each PBX subscriber served by the PBX. This method is
referred to as a child registration, where the IP PBX or IAD/gateway as the parent,
registers the IP PBX or IAD/gateway contact for each of the children, that is, the PBX
10-BD5020-00
PAGE 11 OF 28
2007 BROADSOFT INC.
subscribers. The contact for each child registration may all have the same addresses or
the contact may be unique for each child registration.
header of the INVITE. The request-URI is populated with the registered contact of the
PBX subscriber.
the Contact header of the register.
10-BD5020-00
PAGE 12 OF 28
2007 BROADSOFT INC.
BroadWorks Identity/Device Profile Types for PBX Classifications

To configure a Trunk Group for a PBX in one of the defined PBX classifications, the
Identity/Profile type must either be selected or created in BroadWorks.
The following procedure can be used to determine if the Identity/Device Profile type for the
PBX classification exists in BroadWorks Release 14.0 and above. If the Identity/Device
Profile type does not exist, the system administrator can create the Identity/Device Profile
type for the PBX classification using the following the instructions for the appropriate PBX
classification.
Note, in Release 13.0, the Identity/Profile types must be provided by BroadSoft. If the
appropriate Identity/Device Profile type for the PBX classification is not available in the
drop-down list when creating a device, contact your BroadSoft support representative to
obtain the patch for the appropriate Identity/Device Profile type.
Step
Details
Purpose
Step 1
Log in to the BroadWorks web

configuration interface as a system
administrator.
You must be logged in to BroadWorks as

a system to view the attributes of an
identity/profile type in the system.
Step 2
Under the Resources tab in the left-side

navigation, select the Identity/Device
Profile Types link.
This is the search page for all of the

Identity/Device Profile types defined in
the system.
Step 3
In the search criteria, enter the name of

the Identity/Device Profile type for the
appropriate PBX classification and click
on the Search button.
Search for the Identity/Device Profile type

in the system.
Step 4
Determine if an entry is found.
Determine if the Identity/Device Profile

type exists in the system.
If an entry is found, the Identity/Device

Profile type exists for the PBX
classification.
Otherwise, an Identity/Device Profile
type must be created for the PBX
classification.
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

configuration interface as a system
administrator.

a system to view the attributes of an
identity/profile type in the system.
Step 2

Profile Types link.
This is the search page for all of the

Identity/Device Profile types defined in
the system.
Step 3
Click Add.
Add the Identity/Device Profile type.
10-BD5020-00
PAGE 13 OF 28
2007 BROADSOFT INC.
Step
Details
Purpose
Step 4
Enter the Identity/Device Profile name

for the specific PBX classification.
Create the Identity/Device Profile type in

the system.
Select the appropriate Signaling

Address type for the specific PBX
classification.
Select the appropriate policies for the
specific PBX classification.
Click OK.
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
Use Business Trunking Contact
PBX Integration
10-BD5020-00
PAGE 14 OF 28
2007 BROADSOFT INC.
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.
Static Registration Capable
Use Business Trunking Contact
PBX Integration
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
2007 BROADSOFT INC.
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:
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
The Generic SIP IP-PBX Identity/Profile type must have the following policies:
Static Registration Capable
10-BD5020-00
PAGE 16 OF 28
2007 BROADSOFT INC.
PBX Integration
Figure 2 shows the Identity/Device Profile type for the Generic SIP IP-PBX.
5.5
Generic SIP TDM-PBX Identity/Device Profile Type for Type E - Device

Addressing PBX
The Identity/Device Profile type for the Type E - Device Addressing PBX is Generic SIP
TDM-PBX.
The Generic SIP TDM-PBX Identity/Profile type uses the Intelligent Device Addressing
The Generic SIP TDM-PBX Identity/Profile type must have the following policies:
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
2007 BROADSOFT INC.
PBX Integration
10-BD5020-00
PAGE 18 OF 28
2007 BROADSOFT INC.
BroadWorks Business Trunking PBX Configuration

This section provides the BroadWorks Trunk Group configuration details for each PBX
classification. With these details, a PBX can easily be configured in BroadWorks after it is
mapped to one of the PBX classifications defined in this document.
The Trunk Group configuration for each of the classifications is very similar and all follow
the same configuration steps.
6.1
Create Identity/Device Profile for the Trunk Group

The first step to configure the Trunk Group on BroadWorks is to identify the appropriate
Identity/Device Profile type for the specific PBX classification.
Once the Identity/Device Profile type is identified, an Identity/Device profile is created of
the Identity/Device Profile type for the specific PBX classification. The Identity/Device
profile is typically created at the group to remain in scope with the Trunk Group.
The following procedure shows how to create an Identity/Device profile at the group to use
for the Trunk Group.
Step
Details
Purpose
Step 1

configuration interface as an
administrator.

a system, service provider, enterprise, or
group administrator to create a Trunk
Group.
Step 2
Navigate to the Group page where the

trunk group is added.
This is the default page for all of the

group services assigned to the group.
Step 3

Profiles link.
List all the Identity/Device profiles defined

in the group.
Step 4
Click Add.
Add the Identity/Device profile to the

group.
Step 5
Enter a unique Identity/Device profile

name (for example, TrunkGroup PBX1).
Configure the Identity/Device profile.
Select the appropriate Identity/Device

profile type from the drop-down list for
the PBX classification.
Optionally, configure the IP
address/hostname for the device.
Note that this only applies to the Type
E- Device addressing PBX
classification.
Click OK.
10-BD5020-00
PAGE 19 OF 28
2007 BROADSOFT INC.
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.
Figure 4 Identity/Device Profile Creation Page
6.2
Create Trunk Group

After the Identity/Device profile is created, the Trunk Group configuration can be started.
The following procedure shows how to provision the Trunk Group on BroadWorks.
Step
Details
Purpose
Step 1

configuration interface as an
administrator.

a system, service provider, enterprise, or
group administrator to create a Trunk
Group.
Step 2
Navigate to the Group page where the

Trunk Group is to be added.
This is the default page for all of the

group services assigned to the group.
Step 3
Under the Services tab in the left-side

navigation, select the Trunk Group link.
List all the Trunk Groups defined in the

group.
Step 4
Click Add.
Add the Trunk Group to the group
10-BD5020-00
PAGE 20 OF 28
2007 BROADSOFT INC.
Step
Details
Purpose
Step 5
Enter a unique Trunk Group ID for the

Trunk Group (for example,
PBX_1@broadsoft.com).
Set up the Trunk Group profile of the

Trunk Group.
Enter a unique Trunk Group name for

the Trunk Group (for example, PBX).
Enter the calling line identity name for
the Trunk Group. This is the name that
is used as the calling name for the main
Trunk Group phone number.
Enter the maximum number of active
simultaneous calls allowed in the Trunk
Group.
Optionally, specify the maximum
number of active incoming and/or
outgoing calls allowed.
Optionally, configure the authentication
credentials based on the PBX
classification. All registering PBXs
should have authentication enabled. To
determine which classifications require
the authentication credentials, see the
classification details that follow.
Click OK.
10-BD5020-00
PAGE 21 OF 28
2007 BROADSOFT INC.
Figure 5 Trunk Group Add Configuration shows the Trunk Group Add web page used for
the Trunk Group configuration.
Figure 5 Trunk Group Add 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
Navigate to the newly created Trunk

Group by clicking on the Group Name of
the newly created Trunk Group.
Obtain the Trunk Group profile.
Step 7
Under the Profile tab in the left-side

navigation, select the Addresses link.
Assign the phone number and/or

extension to the Trunk Group.
Select the phone number for the Trunk

Group from the drop-down list and/or
configure the extension for the Trunk
Group.
Step 8
Click Apply.
Save the phone number and/or extension

of the Trunk Group.
10-BD5020-00
PAGE 22 OF 28
2007 BROADSOFT INC.
Figure 6 Trunk Group Addressing Configuration shows the Trunk Group Addresses web
page used for the Trunk Group phone number and extension configuration.
Figure 6 Trunk Group Addressing 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
2007 BROADSOFT INC.
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.
Select the Identity/Device profile button.

Select the previously created
Identity/Device profile in the Identity
Device Profile Name drop-down list.
Configure the main line phone number of
the PBX in the line/port field.
Optionally, configure the host portion
with the domain used for the PBX as
applicable based on the Identity/Device
profile selected.
Optionally, configure the contact based
on the Identity/Device profile selected
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 a Fully Qualified Domain
Name (FQDN) or other information
based on the PBX configuration
requirements.
Step 11
Click OK.
Save the Identity/Device profile and

addressing information for the Trunk
Group.
10-BD5020-00
PAGE 24 OF 28
2007 BROADSOFT INC.
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.
Figure 7 Trunk Group Addressing Configuration with Identity/Device Profile
This step completes the Trunk Group configuration.
6.3
Add Users to Trunk Group

Additional users may be added to the Trunk Group either via the Trunk Group User
Creation tool or by manually adding users.
A user can be manually added to the Trunk Group by first adding a new user using the
usual procedures to create a user. Once the user is created, the user can be included in
the Trunk Group by navigating to the Addressing link on the user page.
Then, the phone number and (optionally) extension should be configured for the user.
The Trunk Group option should then be selected. Selecting this option provides a dropdown list of all the defined Trunk Groups within the group. The appropriate Trunk Group
should be selected and the users phone number should be populated in the line/port field.
The domain portion of the Identity/Device profile addressing, when present, should be
populated with the domain of the Trunk Group main user, which is configured to match the
domain configuration of the PBX as applicable based on the Identity/Device profile
selected.
10-BD5020-00
PAGE 25 OF 28
2007 BROADSOFT INC.
Figure 8 Trunk Group User Addressing Page shows the Trunk Group User Addresses
web page used for associating the user with the Trunk Group.
Figure 8 Trunk Group User Addressing Page
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
2007 BROADSOFT INC.
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
2007 BROADSOFT INC.
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
2007 BROADSOFT INC.

BW BusinessTrunkingConfigurationGuide R140

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BW BusinessTrunkingConfigurationGuide R140

Uploaded by

Copyright:

Available Formats

Business Trunking Configuration Guide

220 Perry Parkway

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

Document Revision History

Reason for Change

October 29, 2007

Edited and published document.

November 13, 2007

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

Changes between Release 13.0 and Release 14.0.................................................................6

BroadWorks Business Trunking PBX Classifications..........................................................9

Type A - SIP Connect Registering PBX Classification...............................................................9

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

Changes between Release 13.0 and Release 14.0

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BroadWorks Application Server (Trunk Group)

Session Border Controller (optional)

Application Layer Gateway (optional)

BroadWorks and/or Third Party Add-On applications (link to Boulevard)

BroadSofts Key Advantage

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BroadWorks Business Trunking PBX Classifications

Type A - SIP Connect Registering PBX

Type B - SIP Connect Non-registering PBX

Type C - SIP Connect Registering PBX with Modified request-URI Header

Type D - SIP Connect Non-registering PBX with Modified request-URI Header

Type E - Device Addressing PBX

Type F - Subscriber Registering PBX

Type A - SIP Connect Registering PBX Classification

Type B - SIP Connect Non-registering PBX Classification

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

In this classification, an IP PBX or IAD/gateway does not register with BroadWorks.

Type C - SIP Connect Registering PBX with Modified request-URI Header

Type D - SIP Connect Non-registering PBX with Modified request-URI

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

Type E - Device Addressing PBX Classification

Type F - Subscriber Registering PBX Classification

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BROADWORKS BUSINESS TRUNKING CONFIGURATION GUIDE

2007 BROADSOFT INC.

BroadWorks Identity/Device Profile Types for PBX Classifications

Log in to the BroadWorks web

You must be logged in to BroadWorks as

Under the Resources tab in the left-side

This is the search page for all of the

In the search criteria, enter the name of

Search for the Identity/Device Profile type

Determine if an entry is found.

Determine if the Identity/Device Profile

If an entry is found, the Identity/Device

Log in to the BroadWorks web