PartnerConfigGuide - Acme - Packet - Net-Net - 3000-4000 - Series R18 BROADSOFT

BroadSoft Partner Configuration Guide
Acme Packet Net-Net 3000/4000 Series
November 2012
Document Version 5.14
9737 Washingtonian Blvd., Suite 350

Gaithersburg, MD USA 20878
Tel +1 301.977.9440
WWW.BROADSOFT.COM
BroadWorks® Guide
Copyright Notice
Copyright© 2012 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., 9737 Washingtonian Boulevard, Suite 350, Gaithersburg, MD 20878.
BroadSoft reserves the right to make changes without prior notice.
Trademarks
®
BroadWorks and BroadWorks Assistant–Enterprise™, BroadWorks Call Center™,
BroadWorks Communicator™, BroadWorks Receptionist™, and BroadWorks
Deployment Studio™ are trademarks of BroadSoft, Inc.
Microsoft, MSN, Windows, and the Windows logo are registered trademarks of Microsoft
Corporation. Other product names mentioned in this document may be trademarks or
registered trademarks of their respective companies and are hereby acknowledged.
This document is printed in the United States of America.
BROADSOFT PARTNER CONFIGURATION GUIDE – ACME PACKET NET-NET 3000/4000 SERIES 20-BD5096-00
©
2012 BROADSOFT, INC. PAGE 2
Document Revision History
Version Reason for Change
1.1 Introduced document with version sd110b19.
1.2 Updated document with comments from Acme Packet.
1.3 Updated document with version 1.3.0 B25.
1.4 Edited document.
1.5 Updated document with version 1.3.3.
1.7 Continued document version from the old to the new BroadSoft branding. Documented Acme Packet
Net-Net 3000/4000 software v2.1.1-P14.
1.9 Updated document to include Acme Packet Net-Net 3000/4000 parameters to fix and enable the (Busy
Lamp Field) BLF feature.
2.0 Updated the document’s configuration descriptions and sample configuration file based on Acme
Packet’s suggestions.
2.2 Updated BLF section to note the optional configuration of the Acme Packet Net-Net 3000/4000’s sip-
message-len parameter when the SIP NOTIFY from BroadWorks exceeds what is currently configured.
2.3 Added static (non-registering) device configuration and SIP Connect configuration.
2.4 Updated SIP registering peer configuration section and sample configuration file with Acme Packet
recommended optimizations.
2.5 Edited changes and published document.
2.6 Identified “without NAT traversal static peer config” as appropriate when there is a SIP-aware firewall.
2.8 Updated document with version C5.0.0p7. Documented configuration changes that resolved previously
existing issues (Network Conferencing & TCP (core-side) transport).
3.0 Added uaCSTA-to-CAP solution configuration, SIP trunking correlation table, SIP manipulation section.
3.2 Minor corrections.
3.4 Minor update to section 4.2.1.2.2.
3.6 Removed uaCSTA gateway config instructions.
3.8 Minor update to section 4.2.1.2.1.
4.0 Added Delay Media Update configuration.
©
Version Reason for Change
4.1 Edited and published document.
4.2 Added Step 6 in the second table of section 4.3.1.2.2. Split Step 3 of section 4.3.2.3 into two
configuration options.
4.4 Updated section 4.3.2.3, Step 3, option 2.
4.6 Renamed document from Acme Packet Session Director to Acme Packet Net-Net 3000/4000 Series.
Updated for Acme Packet C6.1.0/BroadWorks Release 16.0 test results.
4.8 Amended workaround for Acme Packet issue AP26131.
5.0 Added reference to Acme Packet BCP for basic DDoS configuration.
5.2 Minor updates.
5.4 Added section 3.2 Configure Media Manager and updated step 8 of section 3.4.1.2.1 SIP Proxy
Configuration.
5.4 Edited changes.
5.5 Updated for Acme Packet 6.3.0/BroadWorks Release 18.sp1 test results.
5.6 Made many minor updates, including removing SIP Network Peering information.
5.8 Updated Media Manager section.
5.10 Rearranged various sections.
5.12 Removed section 3.5 for SIP manipulation for special cases.
5.13 Made minor editorial changes.
©
Table of Contents
1 Overview .............................................................................................................................................7
2 Interoperability Status ......................................................................................................................8

2.1 Verified Versions...........................................................................................................................8
2.2 Interface Capabilities Supported..................................................................................................8
2.3 Known Issues ............................................................................................................................ 12
3 Net-Net 3000/4000 Configuration ................................................................................................ 14
3.1 Media Manager Configuration .................................................................................................. 15
3.2 BroadWorks-side Configuration................................................................................................ 16
3.2.1 Configure Network Interface ............................................................................................ 16
3.2.2 Configure Core Realm...................................................................................................... 18
3.2.3 Configure Session Agents ............................................................................................... 18
3.2.4 Configure Session Agent Group ...................................................................................... 21
3.2.5 Configure Local Policy...................................................................................................... 22
3.2.6 SIP Manipulation Configuration ....................................................................................... 23
3.3 Access-Side Configuration........................................................................................................ 25
3.3.1 Configure SIP Registering Peer....................................................................................... 25
3.3.2 Configure SIP Static Peer without NAT Traversal .......................................................... 32
3.3.3 Configure SIP Static Peer with NAT Traversal ............................................................... 38
3.4 Configure SIP Registering SIP Connect Peer ......................................................................... 48
3.4.1 Topology Diagram for Registering SIP Connect Peer .................................................... 48
3.4.2 SIP Connect Configuration .............................................................................................. 49
3.5 Net-Net 3000/4000 Redundancy Configuration ...................................................................... 51
3.5.1 Local Redundancy Configuration .................................................................................... 51
3.5.2 Geographic Redundancy Configuration .......................................................................... 52
3.6 Remote Survivability Configuration .......................................................................................... 52
4 Access Device Configuration ...................................................................................................... 53
4.1 SIP Access Device Configuration ............................................................................................. 53
4.1.1 SIP Registering Access Device Configuration ................................................................ 53
4.1.2 SIP Non-registering Access Device Configuration ......................................................... 53
5 SIP Trunking Configuration.......................................................................................................... 54
5.1 Correlation of BroadWorks PBX Classification to Required Acme Packet Configuration ..... 54
6 Appendix A: Sample Net-Net 3000/4000 Configuration Files................................................ 55
6.1 Standard Redundant Net-Net 3000/4000 Configuration for Registering Peers ..................... 55
6.2 Static Peer with NAT Traversal Configuration ......................................................................... 66
6.3 Static Peer without NAT Traversal Configuration .................................................................... 83
References ............................................................................................................................................. 100
©
Table of Figures
Figure 1 Typical Topology for Non-registering Access Device without Requirement for Net-Net
3000/4000 to Perform NAT Traversal ................................................................................................ 32
Figure 2 Typical Topology for a Non-registering Access Device with the Net-Net 3000/4000
Performing NAT Traversal .................................................................................................................. 39
Figure 3 Typical Topology for a Registering Access Device with SIP Connect Configuration ............ 49
Figure 4 Net-Net 3000/4000 Local Redundancy Configuration ............................................................. 51
Figure 5 Net-Net 3000/4000 Geographic Redundancy Configuration .................................................. 52
©
1 Overview
This document describes the configuration procedures required for an Acme Packet Net-
Net 3000/4000 Series to make full use of the capabilities of BroadWorks.
The Net-Net 3000/4000 is one of the many session controllers that interoperate with
BroadWorks.
This guide describes the specific configuration items that are important for use with
BroadWorks. It does not describe the purpose and use of all configuration items on the
Net-Net 3000/4000. For those details, see the Net-Net 4000 ACLI Configuration Guide [1]
supplied by Acme Packet.
©
2 Interoperability Status
This section provides the known interoperability status of the Acme Packet Net-Net
3000/4000 Series with BroadWorks. This includes the version(s) tested, the capabilities
supported, and known issues.
Interoperability testing validates that the device interfaces properly with BroadWorks via
the SIP interface. Qualitative aspects of the device or device capabilities not affecting the
SIP interface, such as performance, are not covered by interoperability testing. Requests
for information and/or issues regarding these aspects should be directed to Acme Packet.
2.1 Verified Versions

The following table identifies the verified Acme Packet Net-Net 3000/4000 Series and
BroadWorks versions and the month/year the testing occurred. If the device has
undergone more than one test cycle, versions for each test cycle are listed, with the most
recent listed first.
Compatible Versions in the following table identify specific 3000/4000 versions which the
partner has identified as compatible and should interface properly with BroadWorks.
Generally, maintenance releases of the validated version are considered compatible and
may not be specifically listed here. Contact Acme Packet for any questions concerning
maintenance and compatible releases.
NOTE: Interoperability testing is normally performed with the latest generally available (GA)
device firmware/software and the latest GA BroadWorks release and service pack at the time the
testing occurs. If there is a need to use a non-verified mix of BroadWorks and device software
versions, customers can mitigate their risk by self-testing the combination using the BroadWorks
Session Controller Interoperability Test Plan [4].
Verified Versions Table
Date BroadWorks 3000/4000 Verified 3000/4000 Compatible Versions

(mm/yyyy) Release Version
03/2012 Release 18.sp1 C6.3.0 F1P6 Any maintenance release of the

verified version.
12/2009 Release 16.0 C6.1.0 M2P4 Any maintenance release of the

verified version.
09/2007 Release 14.sp2 C5.0.0p7 Any maintenance release of the

verified version.
09/2006 Release 14.sp1 4.1.1p42
2.2 Interface Capabilities Supported

The Acme Packet Net-Net 3000/4000 Series has completed interoperability testing with
BroadWorks using the BroadWorks Session Controller Interoperability Test Plan [4]. The
results are summarized in the following table.
The BroadWorks test plan is composed of packages, each covering distinct
interoperability areas, such as “Basic” call scenarios and “Redundancy” scenarios. Each
package is composed of one or more test items which in turn are composed of one or
©
more test cases. The test plan exercises the SIP interface between the device and
BroadWorks with the intent to ensure interoperability sufficient to support the BroadWorks
feature set.
The Supported column in the following table identifies the 3000/4000’s support for each of
the items covered in the test plan packages, with the following designations:
 Yes Test item is supported.
 No Test item is not supported.
 NA Test item is not applicable to the device type.
 NT Test item was not tested.
Caveats or clarifications are identified in the Comments column.
Note that the DUT in the following table refers to the Device Under Test which in this case
is the Acme Packet Net-Net 3000/4000 Series.
BroadWorks Session Controller Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Basic Call Origination Yes
Call Termination Yes
Session Audit Yes
Session Timer Yes
Ringback Yes
Forked Dialog Yes
Early UPDATE Yes
Early-Session NT
181 Call Being Forwarded Yes
DTMF – Inband Yes
DTMF – RFC 2833 Yes
DTMF – DTMF Relay Yes
BroadWorks Services Third-Party Call Control – Basic Yes
Third-Party Call Control – Advanced Yes
Message Waiting Indicator – Yes

Unsolicited
Message Waiting Indicator - Solicited Yes
Voice Portal Outcall Yes
Advanced Alerting Yes
Calling Line ID – Non-Trusted Yes

Endpoint
Calling Line ID – Trusted Endpoint Yes
Diversion Header Yes
History-Info Header Yes
Deny Calls from Unregistered Users Yes
©
Enterprise Trunking – OTG Yes
Enterprise Trunking – DTG Yes
Enterprise Trunking – TGRP Yes
Access Device Call Waiting Yes

Services – Call
Control Services Call Hold Yes
Call Transfer Yes
Local Conference Yes
Network Conference Yes
Call Forward Yes
Access Device Registration – Register Yes

Services – Authentication
Registration and
Authentication Registration – Maximum Registration Yes
Registration – Minimum Registration Yes
Authentication – Invite Authentication Yes
Authentication – Re-Invite/Update Yes

Authentication
Authentication – Refer Authentication Yes
Authentication – Access Device Yes

Authenticating BroadWorks
PBX Trunk Registration – Trunk Yes

Register
PBX Trunk Registration – Call to PBX Yes

User
PBX Trunk Registration – Call from Yes

PBX User
Access Device G711 Fax Passthrough Yes

Services – Fax
G711 Fax Fallback Yes
T38 Fax Messaging Yes
Access Device Short Message Service Yes

Services – Short
Message Service
Advanced Phone Busy Lamp Field Yes

Services – Busy
Lamp Field
Advanced Phone Do Not Disturb Yes

Services – Feature
Key Synchronization Call Forward Yes
Call Center Agent Logon/Logoff Yes
Advanced Phone Line-Seize Events Yes

Services – Shared
Call Appearance Call-Info Events Yes
©

using Call Info Multiple Call Arrangement Yes
Bridging Yes
Advanced Phone Dialog Events NT

Services – Shared
Call Appearance Hold/Retrieve NT
using Dialog Event
Multiple Call Arrangement NT
Bridging NT
Redundancy DNS SRV Lookup Yes
Register Failover/Failback Yes
Invite Failover/Failback Yes
Bye Failover Yes
Video – Basic Video Call Origination Yes

Calls
Call Termination Yes
Call Hold Yes
Call Transfer Yes
Video – BroadWorks Auto Attendant Yes

Video Services
Auto Attendant – HD Yes
Voice Messaging Yes
Access Redirect Register Yes
Register Failover Yes
Invite Yes
Invite Failover Yes
Trunk Group Invite Using OTG Yes
Trunk Group Invite Using TGRP Yes
Remote Survivability Register NA
Local Calls – Without Subscriber NA

Data
PSTN Calls – Without Subscriber NA

Data
SCA Call – Without Subscriber Data NA
Register for Subscriber Data NA
Local Calls – With Subscriber Data NA
PSTN Calls – With Subscriber Data NA
SCA Call – With Subscriber Data NA
IPV6 Call Origination NT
Call Termination NT
©
Ringback NT
Call Control NT
Registration w/ Authentication NT
T38 Fax Messaging NT
Busy Lamp Field NT
Redundancy NT
Video NT
2.3 Known Issues

This section lists the known interoperability issues between BroadWorks and specific
partner release(s). Issues identified during interoperability testing and known issues
identified in the field are listed.
The following table provides a description of each issue and, where possible, identifies a
workaround. The verified partner device versions are listed with an “X” indicating that the
issue occurs in the specific release. The issues identified are device deficiencies or bugs,
so typically not BroadWorks release dependent.
The Issue Number is a BroadSoft ExtraView partner issue number if the testing was
performed by BroadSoft. If the testing was performed by the partner or a third party, the
partner may or may not supply a tracking number.
For more information on any issues related to the particular partner device release, see
the partner release notes.
Issue Number Issue Description Partner Version
All BroadWorks Releases

6.1.0
6.3.0
EV 110951/ BYE failover fails. X

AP26232
The Net-Net 3000/4000 does not failover on BYE to the secondary
Application Server after exhausting retries to the primary Application
Server.
Workaround: None.
NOTE: This issue is fixed in Release 6.1.0M9 and 6.2.0M6 and
higher.
©
Issue Number Issue Description Partner Version
All BroadWorks Releases
6.1.0
6.3.0
AP26131 Register cache cookie placement in contact URI causes issue X
with enterprise trunking.
In cases where the access device (IP-PBX/PBX trunking gateway)
registers with tgrp/trunk-context in the CONTACT header, if the Net-
Net 3000/4000 reg-cache-mode is set to “append”, it inserts the
cookie immediately after the trunk-context parameter which corrupts
the trunk-context. The cookie should be placed directly after the user
ID.
Incorrect: Contact: < sip:2413330442;tgrp=bsoft;trunk-
context=solution.dept-
kjs6n4aufgibf@64.215.212.79:5060;transport=udp >.
Correct: Contact: < sip:2413330442-kjs6n4aufgibf;tgrp=bsoft;trunk-
context=solution.dept @64.215.212.79:5060;transport=udp >
Workaround: The following workaround is provided by Acme Packet.
Enable port mapping on the Net-Net 3000/4000:
1.) sip-interface (core)
Set the port map range. Range must not overlap steering pool
ports. Example:
set port-map-start = 45535
set port-map-end = 65535
If sip-nat is enabled, perform the next three steps.
2.) sip-config
set options-reg-cache-mode = append
3.) sip-nat (core)
set use-url-parameter = none
4.) sip-nat (peer)
set use-url-parameter = all
5.) save-config
6.) reboot activate (Activate without reboot is okay, but has adverse
effect with those ports that are already allocated.)
The port range cannot overlap with the steering-pool ports for RTP.
The new Contact-URI port takes effect upon next registration refresh
from the SD (half the registration expires value from BroadWorks).
Alternate workaround: Cookies are required for deployments in
which the user portion on the SIP contact may be duplicated (for
example: bsmith@xyz.com and bsmith@abc.com). If the
deployment is configured to ensure this does not occur, an alternate
workaround is to disable the Net-Net 3000/4000 cookies: Set reg-
cache-mode to “none”.
Note that this issue is fixed by enabling a global sip-config option set
to “process-implicit-tel-URI”. And the SW version that introduces this
fix is 6.1.0M9 and 6.2.0M5 and higher.
The workaround to set port-mapping should not be needed when reg-
cache-mode is set to append in sip-config.
©
3 Net-Net 3000/4000 Configuration
The Net-Net 3000/4000 configuration commands can be entered through the ACLI
interface, either through the console port or via telnet. For details on how to use this
configuration tool, refer to the Net-Net 4000 ACLI Configuration Guide [1].
The following subsections describe how to configure the BroadWorks Application Servers
and the Net-Net 3000/4000 to work together to allow access devices on remote networks
to work with BroadWorks.
©
3.1 Media Manager Configuration
The following tables identify media manager parameters which may require settings other
than default in some networks.
Step Command Purpose
Step 1 Enter the media-manager After logging into the Acme Packet Net-
Configuration menu. Net 3000/4000 as an administrator, enter
the “configure parameter” mode to add or
Example:
edit Net-Net 3000/4000 parameters.
# media-manager
This is located under the media-manager
(media-manager)# branch.
Step 2 Set state to enabled Enable media manager.

Example:
(media-manager)# state enabled
Step 3 Disable media latching Example: The “latching” parameter is enabled by

default. It is not recommended to set
(media-manager)# latching
“latching” to disabled for security
disabled
reasons. However, latching may need to
be disabled if T.38 issues are identified.
For T.38, some devices use a different
port in the reINIVTE SDP than the port in
the initial INVITE SDP. If latching is
enabled, the SBC will drop T.38 packets
from the new port.
Step 4 Enable RTCP support for devices Enable “hnt-rtcp” is required for video
behind NAT. end points behind NAT. Video is
susceptible to the loss of the initial video
Example:
frame which may cause no video being
(media-manager)# hnt-rtcp enabled displayed. When that happens, video
end points rely on the RTCP to recover
and display the video properly. As a
result, end-to-end RTCP flow is required.
Step 5 Disable rtcp rate cap This is a per flow configuration parameter
that allows SBC to monitor the RTCP
Example:
rate limit according to the value
(media-manager)# rtcp-rate-limit configured. It defaults to “0” which
0 means any RTCP rate is allowed.
Step 6 Enable fragment msg queue. Because untrusted and fragmented

packets share the same amount of
Example:
bandwidth for policing, any flood of
(media-manager)# fragment-msg- untrusted packets can cause the SBC to
bandwidth 96000 drop fragment packets. To prevent
fragmented packet loss, set the
“fragment-msg-bandwidth to a value
other than 0, (which disables it). The
valid value range is 2000 – 10000000.
This tells Net Net SBC to provide a
separate policing queue for fragment
packets (separate from that used for
untrusted packets) and thus prevent
fragment packet loss when there is a
flood from untrusted endpoints.
Step 7 Required options parameter This option parameter is introduced in
6.3.0 release and it is required to prevent
Example:
SBC preemptively tearing down an
(media-manager)# options dont- orphaned call leg in the hairpin scenario.
terminate-assoc-leg
©
3.2 BroadWorks-side Configuration
This section identifies the settings necessary to configure the BroadWorks (or core) side of
the Net-Net 3000/4000 for registering devices and SIP Static Peer with or without NAT
Traversal.
3.2.1 Configure Network Interface

The network-interface elements specify a logical network interface. At least one network
interface must be configured for each physical interface that already exists. Additional
network-interface configuration can be obtained within the Net-Net 4000 ACLI
Configuration Guide [1].
The following steps describe the core-side configuration setup between the Acme Packet
Net-Net 3000/4000 and the BroadWorks Application Server.
Step 1 Enter Acme Packet After logging into the Acme Packet Net-
configuration mode. Net 3000/4000 in an administrator
mode, enter the “configure parameter”
# configure terminal mode to add or edit Net-Net 3000/4000
(configure)# parameters.
Step 2 Enter the general system Select the “system” to access the
component configuration. System Level Configuration element.
(configure)# system
(system)#
Step 3 Enter the layer-3 network This sub tree enables you to access
interfaces configuration. and configure the network-interfaces
and the related parameters.
(system)# network-interface
(network-interface)#
©
Step 4 Configure Network-Interface The following parameters should be

parameters. configured for the Network Interface.
Example: name – Set name for network interface.
Must be the same name as the physical
name
interface to which it corresponds.
M10
hostname – (optional) FQDN hostname
sub-port-id
for the network-interface.
0
ip-address – Set address of the
hostname
network-interface.
ip-address
netmask – Set netmask address of the
192.168.6.90
network.
pri-utility-addr
192.168.6.91 gateway – Set the network gateway.
sec-utility-addr gw-heartbeat – Set to enable to

192.168.6.92 proactively monitor the health status of
the respective gateways of each
netmask network interface when SD is deployed
255.255.255.0 in High Availability mode.
gateway
192.168.6.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
192.168.6.22
dns-ip-backup1
dns-ip-backup2
dns-domain
intas.broadworks.net
hip-ip-list
192.168.6.90
ftp-address
192.168.6.90
icmp-address
192.168.6.90
snmp-address
telnet-address
192.168.6.90
©
3.2.2 Configure Core Realm
The following table describes the Realm Configuration on the core side of the network.
Step 1 Enter the realm-config After logging into the Acme Packet Net-
Configuration menu. Net 3000/4000 as an administrator, enter
the “configure parameter” mode to add or
Example:
edit Net-Net 3000/4000 parameters.
# realm-config
This is located under the media-manager
(realm-config)# branch.
Step 2 Enter the identifier for the Configure a unique name for the realm
realm. identification.
Example:
(realm-config)# identifier core
Step 3 Identify the network interface Configure the network interface for the
for the realm. realm. The network interface should
already have been created.
Example:
(realm-config)# network-
interfaces M10:0
Step 4 Configure the prefix address. Configure the prefix address as the static
peer IP address.
Example:
(realm-config)# addr-prefix
192.168.6.0/24
Step 5 Set the access control trust The access control always remains
level to “high”. TRUSTED.
Example:
(realm-config)# access-control-
trust-level high
Step 6 Delay-media-update. The delay-media-update parameter must

be enabled. This allows media for IVR
Example:
and ringback tone to be streamed in
(realm-config)# delay-media- cases when the call forwards or transfers
update enabled and the media originates from a different
source.
3.2.3 Configure Session Agents

One session agent should be configured for the primary Application Server, and a second
session agent should be configured for the secondary Application Server.
The following steps describe the configuration setup of a session-agent for the primary
Application Server.
Step 1 Enter the Session Agent This is located under the session-router
Configuration menu. branch.
Example:
(session-router)# session-agent
©
Step 2 Use the address of the Application Set this to the primary Application Server
Server as the Hostname. address for that session agent.
Example: This value is used in the dest field of the
(session-agent)# hostname session-group on the Net-Net 3000/4000.
192.168.6.20
Step 3 Set the IP address. Set the IP address of the primary

Application Server.
Example:
(session-agent)# ip-address
192.168.6.20
Step 4 Set the application protocol to Set the application protocol to use the
use. SIP protocol.
(session-agent)# app-protocol SIP
Step 5 Set the transport method to use Setting the transport-method parameter
for the session-agent. to UDP+TCP allows the session-agent to
accept UDP or TCP-transmitted
(session-agent)# transport-method
messages.
UDP
Step 6 Set the realm that the Application The realm-ID must be set for all session-
Server is in. agents.
Example:
(session-agent)# realm-id core
Step 7 Add a description for the session- Insert a description to identify the
agent. session-agent. Use double quotes if the
description contains spacing between
(session-agent)# description
words.
“BroadWorks Primary AS”
Step 8 Set the proxy-mode. Define the proxy mode for arriving SIP
requests.
(session-agent)# proxy-mode Proxy
Step 9 Set redirect-action. Define how to handle Redirect (3xx)

response.
(session-agent)# redirect-action
Recurse
Step 10 Enable the Ping Method. Use OPTIONS to ping the Application
Servers to test their availability.
Example:
(session-agent)# ping-method
OPTIONS;hops=0
Step 11 Set the Ping Interval. This is in seconds. Since there should
not be many Net-Net 3000/4000s
Example:
deployed for each Application Server
(session-agent)# ping-interval 60 cluster, this should not introduce extra
message traffic.
Step 12 Set the trust-me mode to be This is required for all session-agents
enabled. when privacy information is passed
between them. If a session-agent is not
Example:
trusted, privacy information is stripped.
(session-agent)# trust-me enabled
©
The following steps describe the configuration setup of a session-agent for the Secondary
Application Server.
Step 1 Enter the Session Agent This is located under the session-router
Example:
Step 2 Use the address of the Application Set this to the primary Application Server
Server as the Hostname. address for that session agent.
Example: This value is used in the dest field of the
(session-agent)# hostname session-group on the Net-Net 3000/4000.
192.168.6.21
Step 3 Set the IP address. Set the IP address of the primary

Application Server.
Example:
192.168.6.21
Step 4 Set the application protocol to Set the application protocol to use the
use. SIP protocol.
Step 5 Set the transport method to use Setting the transport-method parameter
for the session-agent. to UDP+TCP allows the session-agent to
accept UDP or TCP transmitted
messages.
UDP
Step 6 Set the realm that the Application The realm-ID must be set for all session-
Server is in. agents.
Example:
Step 7 Add a description for the session- Add a description to identify the session-
agent. agent. Use double quotes when the
description has spaces between words.
(session-agent)# description
“BroadWorks Secondary AS”
Step 8 Set the proxy-mode. Define the proxy mode for arriving SIP
requests.
(session-agent)# proxy-mode Proxy
Step 9 Set redirect-action. Define how to handle Redirect (3xx)

response.
Recurse
Example:
OPTIONS;hops=0
Step 11 Enable the Ping Method. Use OPTIONS to ping Application

Example:
options
Step 12 Set the Ping Interval. Set the ping interval (in seconds). Since
there should not be many Net-Net
Example:
3000/4000s deployed for each
(session-agent)# ping-interval 60 Application Server cluster, this should not
introduce extra message traffic.
©
Step 13 Set the trust-me mode to be This is required for all session-agents
enabled. when privacy information is passed
between them. If a session-agent is not
Example:
trusted, privacy information is stripped.
(session-agent)# trust-me enabled
3.2.4 Configure Session Agent Group

This section describes how to configure the Net-Net 3000/4000 session agents for
redundancy.
Step 1 Enter the Session Group This is located under the session-router
Example:
(session-router)# session-group
Step 2 Give the group a name. This name is used in the local-policy
configuration as SAG: Application
Example:
Server, which means Session-Agent-
(session-agent-group)# group-name Group: Application Server.
BROADWORKS
Step 3 Set a description. Enter a description for the session-group.

(session-agent-group)#
description “BroadWorks Hunt
Group”
Step 4 Set application protocol. Set the session-group to use the SIP
signaling protocol.
(session-agent-group)# app-
protocol SIP
Step 5 Set the Routing Strategy. BroadWorks requires that the primary
Application Server always has priority
Example:
over the secondary Application Server.
(session-agent-group)# strategy (The Hunt strategy behaves this way.)
Hunt
Step 6 Enter the destinations. List the primary Application Server first,
then the secondary Application Server.
Example:
(session-agent-group)# dest
192.168.6.20
192.168.6.21
Step 7 Enable the Session Agent Group. Enable the Session Agent Group.
Example:
(session-agent-group)# state
enabled
Step 8 Disable the recursion. Session Agent Group recursion should

be disabled.
Example:
(session-agent-group)# sag-
recursion disabled
©
3.2.5 Configure Local Policy
Step 1 Enter the local-policy This is located under the session-router

Example:
# local-policy
Step 2 Enter the matching criteria. These parameters match the incoming
SIP message.
Example:
(local-policy)# from-address *
(local-policy)# to-address
as.broadworks.net
(local-policy)# source-realm
access
Step 3 Enter the policy-attributes. Option 1 routes the SIP messages to the
(Option1) BroadWorks Network Server which is
Example:
fronting multiple BroadWorks Application
(local-policy-attributes)# next- Server Clusters. Each Application Server
hop 192.168.6.22 should be already configured with a
session-agent in the core realm.
(local-policy-attributes)# realm
core  “next-hop” – This is the address or
(local-policy-attributes)# app- the cluster address of the
protocol SIP BroadWorks Network Server. The
Network Server address is required
here to support the BroadSoft
Originator Redirect feature. Note
that the BroadWorks Network
Server must be configured with
Originator Redirect for the Acme
Packet Net-Net 3000/4000. For
detailed explanation of the
BroadWorks Originator Redirect
feature, refer to the BroadWorks
Network Server Product Description
[6].
 “realm” – core
 “app-protocol” – SIP
Step 3 Enter the policy-attributes. Option 2 routes the SIP messages to the
(Option 2) BroadWorks Application Server.
Example:
(local-policy-attributes)# next-  “next-hop” – This is the
hop SAG:BROADWORKS BroadWorks redundant Application
Server cluster (session-group)
(local-policy-attributes)# realm defined as the next hop for routing
core traffic.
(local-policy-attributes)# app-  “realm” – Realm where BroadWorks
protocol SIP resides.
 “app-protocol” – The protocol to be
used.
©
3.2.6 SIP Manipulation Configuration
SIP headers’ manipulation may be required when devices statically peering with
BroadWorks. The following is an example configuration for change the Request–URI in
the outgoing request messages:
Step 1 Enter the sip-manipulation This is located under the session-

Configuration menu. router branch.
Example:
# sip-manipulation
(sip-manipulation)#
Step 2 Configure the sip manipulation list Set the SIP-manipulation list name to
name. the out-manipulation ID in the
session-agent configuration.
Example:
(sip-manipulation)# name “ippbx-1- Configure a suitable description for
change-ruri” the manipulation.
(sip-manipulation)# description
“change RURI”
Step 3 Enter the header-rules configuration This is located under the SIP-
menu. manipulation menu.
Example:
# header-rules
(sip-header-rules)#
Step 4 Configure the header-rule name. Configure a unique name for the
header rule.
Example:
(sip-header-rules)# name “Change-
RURI”
Step 5 Configure the header-name for the Configure the header-name as

header rule. Request-uri since the SIP
manipulation is for the request-URI
Example:
header.
(sip-header-rules)# header-name
“Request-uri”
Step 6 Configure the action parameter for This is to manipulate the request-uri
the header rule. header in the INVITE.
Example:
(sip-header-rules)# action manipulate
Step 7 Configure the message type. Configure the message type as

“request”.
Example:
(sip-header-rules)# msg-type request
Step 8 Enter the element-rules configuration This is located under the header-
menu. rules menu.
Example:
# element-rules
(sip-element-rules)#
©
Step 9 Configure the element-rule name. Configure a unique name for the
element rule.
Example:
(sip-element-rules)# name “Change-
Host”
Step 10 Configure the element type. Configure the element type for which
rule needs to be applied.
Example:
(sip-element-rules)# type uri-host
Step 11 Configure the action parameter for This manipulation is to replace a

the header rule. matched value in the REQUEST-URI
with a new value.
Example:
(sip-element-rules)# action replace In this case, the value
“adtran.broadworks.net” (the FQDN
of the static peer defined on
BroadWorks), is replaced by
“192.168.242.41” (the IP address of
the static peer). This is because the
static peer (Adtran) does not support
FQDN as hostname.
Step 12 Configure the match-value. Configure the value to be matched in

the REQUEST-URI.
Example:
(sip-element-rules)# match-value
adtran.broadworks.net
Step 13 Configure the new value to be Configure the value to be replaced

replaced. with the matched value in the
REQUEST-URI.
Example:
(sip-element-rules)# new-value
192.168.242.41
©
3.3 Access-Side Configuration
This section identifies the settings necessary to configure the access side of the Net-net
3000/4000 for registering devices and SIP Static Peer with or without NAT Traversal.
3.3.1 Configure SIP Registering Peer

This section describes how to configure the Net-Net 3000/4000 for registering devices.
Most SIP access devices provide registration capability. This configuration usually needs
to be completed only once to service all registering devices. However, if the Net-Net
3000/4000 is serving multiple Application Server clusters or there are differences required
for some access devices, additional configuration may be required. For registering
devices supporting SIP Connect registration, see section 3.4 Configure SIP Registering
SIP Connect Peer.
3.3.1.1 Network Interface Configuration

The following steps describe the access-side configuration setup between the Acme
Packet Net-Net 3000/4000 and the access network.
Step 1 Enter Acme Packet configuration After logging into the Acme Packet Net-
mode. Net 3000/4000 in an administrator mode,
enter the “configure parameter” mode to
# configure terminal add or edit Net-Net 3000/4000
(configure)# parameters.
Step 2 Enter the general system Select the “system” to access the System
component configuration. Level Configuration element.
(configure)# system
(system)#
Step 3 Enter the layer-3 network This sub-tree enables you to access and
interfaces configuration. configure the network-interfaces and the
related parameters.
(system)# network-interface
(network-interface)#
©
Step 4 Configure Network-Interface The following parameters should be

parameters. configured for the Network Interface.
Example: name – Set name for network interface.
Must be the same name as the physical
name
interface to which it corresponds.
M00
hostname – (optional) FQDN hostname
sub-port-id 0
for the network-interface.
hostname
ip-address – Set address of the network-
ip-address interface.
192.168.242.110
netmask – Set netmask address of the
pri-utility-addr network.
192.168.242.111
gateway – Set the network gateway.
sec-utility-addr
192.168.242.112
netmask
255.255.255.0
gateway
192.168.242.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
192.168.6.22
dns-ip-backup1
dns-ip-backup2
dns-domain
intas.broadworks.net
hip-ip-list
192.168.242.110
ftp-address
icmp-address
192.168.242.110
snmp-address
telnet-address
3.3.1.2 SIP Configuration

Step 1 Enter Acme Packet configuration After logging into the Acme Packet Net-
mode. Net 3000/4000 in an administrator more,
enter the “configure parameter” mode to
# configure terminal add or edit Net-Net 3000/4000
(configure)# session-router parameters.
(session-router)# sip-config Go to the sip-configuration level under

session-router.
©
Step 2 Set the home realm id. Set the realm ID that will be defined as
the “home” realm for the Net-Net
Example: 3000/4000. This is defined for a SIP-
(sip-config)# home-realm-id home NAT bridge environment.
Step 3 Set the egress realm id. Setting the egress realm ID defines the
default route for SIP requests addressed
Example: to destinations outside the home realms
(sip-config)# egress-realm-id address prefix. This corresponds to
core routed messages from BroadWorks.
Step 4 Set operation mode. Setting the “operation-mode” to “dialog”

allows for a B2BUA state session.
Example:
(sip-config)# operation-mode
dialog
Step 5 Set the NAT mode. This indicates that the subnet defined in
the addr-prefix-ID of the home-realm is
Example: “public” and the subnet defined in the
(sip-config)# nat-mode Public addr-prefix-ID field of all other external
realms identified in the SIPNAT are
private networks. Thus IPv4 address are
encoded and decoded as messages are
received and sent respectively by realms
defined by the SIPNAT.
Step 6 Set registrar parameters. Set “registrar-domain” to define the

domain to match against the host part of
Example: a URI to determine if a request is
(sip-config)# registrar-domain * addressed to the registrar. If there is a
match, the registration caching, NAT
(sip-config)# registrar-host * traversal, and route to registrar
parameter values for the SIP interface
(sip-config)# registrar-port
are applied to the request. Setting (*)
5060
specifies that the values apply to all
requests.
Set “registrar-host” to define the address
of the registrar for which requests for
registration caching, NAT traversal, and
router to register options apply. Setting
(*) indicates that normal routing is used
to determine the registrar’s address.
Set “registrar-port” port number.
Step 7 Set Maximum UDP Length option. This is an options parameter that
overrides the default value of the
(sip-config)# options +max-udp- maximum UDP datagram size of 1500
length=0 bytes (as the SIP processor required
anything >1300 bytes to be sent as SIP
/TCP). By setting this = 0 forces these
packets to be fragmented but sent over
UDP.
This is important for interworking with the
BroadWorks BLF feature.
©
Step 8 Set Registration Grace Timer. This is options parameter tells the SBC
to keep the registration cached for a
Example: specific number of seconds event if the
(sip-config)# options +register- SIP endpoint does not refresh its
grace-timer = 20 registration when it supposed to.
When to enable this parameter:
In a non geo-redundant SBC
deployment, some Cisco phones that de-
register prematurely before the minimum
60-second NAT-interval. The buffer is
required so that it prevents deregistration
of the phone from the registration cache.
When NOT to enable this parameter:
In a geo-redundant SBC deployment,
enabling this parameter causes issues
For an example; a short network issue
caused a short duration transition to an
alternate SBC pair and then resumed
using the primary target pair. Failover
works fine with devices registering
through the alternate SBC. But since
there is no synchronization between
separate HA SBC pairs, registration
caching on the primary pair still exists
until its timer expires. As a result, on a
quick fail-back, the primary SBC sees
cache entry and does not pass Register
through and BroadWorks still thinks the
phone is registered from the secondary
SBC.
Step 9 Set Refer-to URI for BroadWorks This is an options parameter that must
Network Conferencing. be set to the user portion of the
configured BroadWorks Network
Example: Conference URI to enable Three-Way
(sip-config)# options +refer-to- and N-Way network conferencing for
uri-prefix=”conf” phones behind the Net-Net 3000/4000.
3.3.1.3 SIP Interface Configuration

The sip-interface element defines the transport addresses (IP address and port) that the
Net-Net 3000/4000 uses for receiving and sending SIP messages. The sip-interface
defines the signaling interface. The SIP interface is defined for each realm.
The following steps outline the configuration for the SIP interface between the Acme
Packet Net-Net 3000/4000 and the access network.
Step 1 Enter the SIP Configuration menu. Sip-interface is located under the
session-router branch.
Example:
# sip-interface
(sip-interface)#
Step 2 Enable the SIP interface. Set to enable the SIP interface.
Example:
(sip-interface)# state enable
©
Step 3 Set realm-id. Set the realm-ID to which the SIP

interface is connected. This will either be
Example:
set to the access (public) or core (private)
(sip-interface)# realm-id access realms. The realms should already exist
or be created.
Step 4 Set the sip port. Configure the sip-port interface to specify
the address, port, transport type, and
Example:
allow anonymous criteria.
(sip-interface)#sip-port  “address” – IP address on which to
(sip-port)# address listen.
192.168.242.110  “port” – Port number to use.
 “transport-protocol” – Associates
(sip-port)# port 5060 transport protocol with the SIP port
(sip-port)# transport-protocol UDP (UDP or TCP).
Note that up to the current version
(sip-port)# allow-anonymous
C5.0.0p7, the Net-Net 3000/4000 does
registered
not support DNS lookup to resolve a
NOTE: To allow the “sip- preferred transport. For this reason,
interface” for the specified realm when both UDP and TCP are configured
to support the TCP transport, on the core (private) realm, UDP is
repeat Step 4 and define the selected as the default transport.
“transport-protocol” parameter as Therefore, if TCP is the intended
TCP. transport, only TCP should be
configured.
 “allow-anonymous” – Sets the criteria for
accepting and processing a SIP request
from another SIP element. Setting to
“all” allows requests from any SIP
element. For the core (private) realm,
the value “agents-only” should be set.
The “agents-only” value allows
connections only from configured
session agents.
Step 6 Set use minimum registration. Generally, the Net-Net 3000/4000’s
Registration Throttling is achieved
Example:
through the “registration-interval” on the
(sip-interface)#min-reg-expire access side of the sip-interface and the
7200 expiration time is provided in the 200 OK
response to the Net-Net 3000/4000’s
registration.
However, if the BroadWorks Application
Server’s minimum registration is not
enabled or enforced, the expiration time
on the core side is same as the
expiration time on the access side,
(which increases the number of
registration messages on the core side of
network).
By default, the Net-Net 3000/4000
refreshes registration at the halfway point
of the expiration time. Therefore, setting
“min-reg-expire” to 7200 seconds
achieves Net-Net 3000/4000 re-register
itself with BroadWorks at the 3600-
second interval.
Note that the BroadWorks recommended
registration interval is 3600 seconds.
©
Packet Net-Net 3000/4000 and BroadWorks Application Server.
Example:
# sip-interface
(sip-interface)#
Example:
Step 3 Set realm-id. Set the realm-ID to where the SIP

interface is connected. This is either set
Example:
to the access (public) or core (private)
(sip-interface)# realm-id core realm. The realm should already exist or
must be created.
Step 4 Set the sip port. Configure the sip-port interface to specify
the address, port, transport type, and
Example:
allow anonymous criteria.
(sip-interface)#sip-port
 “address” – IP address on which to
(sip-port)# address 192.168.6.90 listen.
(sip-port)# port 5060  “port” – Port number to use.
(sip-port)# transport-protocol UDP  “transport-protocol” – Associates the
(sip-port)# allow-anonymous transport protocol with the SIP port
agents-only (UDP or TCP).
NOTE: To allow the “sip-  “allow-anonymous” – Sets criteria for
interface” for the specified realm accepting and processing a SIP
to support the TCP transport, request from another SIP element.
repeat Step 4 and define the Setting to “all” allows requests from
“transport-protocol” parameter as any SIP element.
TCP.
Step 5 Set stop-recurse on 4xx. Enter a list of the returned response

codes that this SIP interface will watch
Example:
for to stop recursion. The listed settings
(sip-interface)# stop-recurse are recommended and may be expended
“400,401,403,407,480,486” to include other response codes, such as
408, depending on the implementation.
©
3.3.1.4 SIP Feature
For support of the BroadWorks Busy Lamp Field (BLF) feature, the following SIP feature
must be defined.
Step 1 Set sip-feature parameter. This sip-feature parameter must be

configured to handle BLF SIP NOTIFY
Example
message from BroadWorks.
sip-feature
name
eventlist
realm
support-mode-inbound
Pass
require-mode-inbound
Pass
proxy-require-mode-inbound
Pass
support-mode-outbound
Pass
require-mode-outbound
Pass
proxy-require-mode-outbound
Pass
Step 2 Set the following parameter in Change the current transport

session-agent. configuration within the session-agent
section from “UDP+TCP” to “UDP”.
session-agent
transport-method UDP This change should be made for both the
session-agents for the primary
Application Server and secondary
Application Server.
Step 3 Remove the following parameters Remove the sip-port parameter that is
for sip-interface. assigned the TCP transport protocol with
the “core” realm-ID.
sip-interface
sip-port
address 192.168.6.90
port 5060
transport-protocol TCP
allow-anonymous all
Step 4 Adjust sip-message-len parameter The sip-message-len parameter must be

under sip-config. adjusted to handle the large message
size of the SIP NOTIFY received from
sip-config
BroadWorks.
sip-message-len 32768
If the Net-Net 3000/4000 returns a “513
Message Size Too Large” in response to
a SIP message from BroadWorks, then
sip-message-len needs to be increased.
The sip-message-len parameter has a
maximum size of 65535(bytes).
©
3.3.2 Configure SIP Static Peer without NAT Traversal
This section describes how to configure the Net-Net 3000/4000 for a static or non-
registering SIP device without the requirement for the Net-Net 3000/4000 to perform NAT
traversal.
NOTE: This configuration also applies for deployments in which the static peer is behind a SIP-
aware firewall.
This configuration needs to be completed for each non-registering peer in this category.
3.3.2.1 Topology Diagram for SIP Static Peer without NAT Traversal
Figure 1 identifies a typical topology for a non-registering access device without the
requirement for the Net-Net 3000/4000 to perform NAT traversal. The IP addresses in
Figure 1 are used in the following configuration sections for this peer type.
Primary AS(192.168.6.20) Secondary AS(192.168.6.21)
Redundant AS pair
AS1 AS2
Private subnet
192.168.6.0/24
192.168.6.90
AcmePacket SD
192.168.242.110
Access Network:
Public IP Network
192.168.242.0
IP PBX(192.168.242.41)
2403330053 2403330052
Figure 1 Typical Topology for Non-registering Access Device without Requirement for Net-Net 3000/4000 to
Perform NAT Traversal
©
3.3.2.3 Realm Configuration

The following table describes the realm configuration of the Net-Net 3000/4000 for the
static peer:
Step 1 Enter the realm-config Configuration After logging into the Acme Packet
menu. Net-Net 3000/4000 as an
administrator, enter the “configure
Example:
parameter” mode to add or edit Net-
# realm-config Net 3000/4000 parameters.
(realm-config)# This is located under the media-
manager branch.
Step 2 Enter the identifier for the realm. Configure a unique name for the
realm identification.
Example:
(realm-config)# identifier peer-1
Step 3 Identify the network interface for Configure the network interface for
the realm. the realm. The network interface
should already have been created.
Example:
(realm-config)# network-interfaces
M00:0
Step 4 Configure the prefix address. Configure the prefix address as the
static peer IP address.
Example:
192.168.242.41
Step 5 Set the access control trust level Setting access-control-trust-level to

to “medium”. “medium” allows SD to promote the
access hosts to a trusted list or
Example:
demote to an untrusted list depending
(realm-config)# access-control- on the invalid signaling thresholds
trust-level medium configured. The invalid signaling
thresholds parameters will vary by
customer.
3.3.2.4 Access Control Configuration

The following describes the access control configuration of the Net-Net 3000/4000 for the
static peer:
Step 1 Enter the SIP Configuration menu. Access-control is located under the
Example:
# access-control
(access-control)#
©
Step 2 Configure the realm id. Set the realm ID for the access control.
This should already be configured on
Example:
the realm-config.
(access-control)# realm-id peer-1
Step 3 Configure the source address. The source address is the static IP
address of the non-registering peer.
Example:
(access-control)# source-address
192.168.242.41
Step 4 Configure the destination address. The destination address is the public
side IP address of the Net-Net
Example:
3000/4000.
(access-control)# destination-
address 192.168.242.110:5060
Step 5 Configure the transport protocol. Set the transport protocol to “all”, which
includes TCP and UDP.
Example:
(access-control)# transport-
protocol all
Step 6 Configure the trust-level. The access-control can be set to

medium or low to match the realm
Example:
configuration.
(access-control)# trust-level
medium
Step 7 Configure the invalid signal This value is the acceptable invalid
threshold value. signaling message rate within a
tolerance window.
Example:
(access-control)# invalid-signal- It has been noted that some Polycom
threshold 1 phones need this parameter to set to
“2”. However, the value of the “invalid-
signal-threshold depends on what type
of device the remote endpoint is and
whether NAT is employed on the
remote endpoint.
Step 8 Configure the maximum signal This value is the allowed maximum
threshold value. number of signaling messages within a
tolerance window. This is an example
Example:
value only.
(access-control)# maximum-signal-
threshold 15000
3.3.2.5 Host Route Configuration

The following table describes the access control configuration of the Net-Net 3000/4000
for the static peer:
Step 1 Enter the host-route Configuration This is located under the system
menu. branch.
Example:
# host-route
(host-route)#
©
Step 2 Enter the destination network. Configure the destination network as

the static IP address of the non-
Example:
registering peer.
(host-route)# dest-network
192.168.242.41
Step 3 Enter the destination subnet mask. Configure the destination subnet
mask.
Example:
(host-route)# netmask 255.255.255.0
Step 4 Enter the gateway ip address. Configure the gateway IP address for
the network.
Example:
(host-route)# gateway 192.168.242.1

Step 1 Enter Acme Packet configuration Go to the sip-configuration level under

mode. session-router.
# configure terminal
(configure)# session-router
(session-router)# sip-config
Step 2 Set the egress realm id. Setting the egress realm ID defines the
default route for SIP requests
Example: addressed to destinations outside the
(sip-config)# egress-realm-id home realms address prefix. This
peer-1 corresponds to routed messages from
BroadWorks.

defines the signaling interface. The SIP interface is defined for each realm that is defined.
Packet Net-Net 3000/4000 and the non-registering static peer:
Example:
# sip-interface
(sip-interface)#
Example:
Step 3 Set realm-id. Set the realm ID so that the SIP

interface is connected. This will be
Example:
set to the static realm. The realms
(sip-interface)# realm-id peer-1 should already be created.
©
Step 4 Set the sip port. Configure the sip-port interface to

specify the address, port, transport
Example:
type, and allow anonymous criteria.
“address” – IP address on which to
(sip-port)# port 5060 “port” – Port number to use.
(sip-port)# transport-protocol UDP “transport-protocol” – Associate
(sip-port)# allow-anonymous agents- transport protocol with SIP port (UDP
only or TCP).
NOTE: To allow the “sip-interface” “allow-anonymous” – Set criteria for
for the specified realm to support accepting and processing a SIP
the TCP transport, repeat Step 4 and request from another SIP element.
define the “transport-protocol” Setting to “agents-only” to only allows
parameter as TCP. the traffic from the configured agents.
3.3.2.8 Configure Session Agents

The following steps describe the configuration setup of a session-agent for the static peer:
Step 1 Enter the Session Agent Configuration This is located under the session-
menu. router branch.
Example:
Step 2 Configure the hostname. Configure the hostname as the IP

address the static peer.
Example:
(session-agent)# hostname
192.168.6.20
Step 3 Set the IP address. Configure the IP address as the IP

address used for the static peer.
Example:
192.168.6.20
Step 4 Set the application protocol to use. Set the application protocol to use the
SIP protocol.
Step 5 Set the transport method to use for Setting the transport-method
the session-agent. parameter to UDP+TCP allows the
session-agent to accept UDP or TCP
transmitted messages.
UDP+TCP
Step 6 Set the realm that the Application The realm ID must be set for all
Server is in. session-agents.
Example:
agent. session-agent. Use double quotes if
the description contains spacing
(session-agent)# description “Non-
between words.
registering peer”
©
Example:
(session-agent)# ping-method options Ping method should be disabled if the
end device does not respond to
pings. Otherwise, Net-Net 3000/4000
thinks the device is out of service.
Step 9 Set the Ping Interval. This is in seconds. Since there

should not be many Net-Net
Example:
3000/4000’s deployed for each
(session-agent)# ping-interval 60 Application Server cluster, this should
not introduce extra message traffic.
This is not required when the ping
method is disabled.
Step 10 Configure the proxy mode. The requests are forwarded in the
proxy mode.
Example:
(session-agent)# proxy-mode proxy
Step 11 Configure the redirect mode. The redirect responses are sent back
to the previous hop.
Example:
proxy
Step 12 Set the outbound manipulation id. Configure the outbound manipulation
ID name. This manipulation will be
Example:
configured under sip-manipulation
(session-agent)# out-manipulationid menu.
“ippbx-1-change-ruri”
3.3.2.9 Configure Local Policy

This section describes the local policy to be used for outgoing calls from the static peer:
Step 1 Enter the local-policy Configuration This is located under the session-
Example:
# local-policy
Step 2 Enter the matching criteria. These parameters match the

incoming SIP message.
Example:
(local-policy)# to-address *
(local-policy)# source-realm peer-1
Step 3 Enter the policy-attributes. This determines how to route these

SIP messages.
Example:
(local-policy-attributes)# next-hop next-hop – This is the BroadWorks
SAG:BROADWORKS redundant Application Server cluster
(session-group) and is defined as the
(local-policy-attributes)# realm core next hop for routing traffic.
(local-policy-attributes)# app- realm – Realm in which BroadWorks
protocol SIP resides.
(local-policy-attributes)# done app-protocol – Protocol to be used.
©
This section describes the local policy to be used for incoming calls to the static peer:
Example:
# local-policy

Example:
(local-policy)# from-address * 240333005 is the prefix of the DNs
configured on the static peer.
(local-policy)# to-address 240333005
(local-policy)# source-realm peer-1

SIP messages.
Example:
(local-policy-attributes)# next-hop next-hop – The IP address of the
192.168.242.41 static peer is defined as the next hop
for routing traffic.
peer-1 realm – Realm in which static peer
resides.
(local-policy-attributes)# app-
protocol SIP app-protocol – Protocol to be used.
(local-policy-attributes)# done
3.3.3 Configure SIP Static Peer with NAT Traversal

This section describes how to configure the Net-Net 3000/4000 for a static or non-
registering device with the Net-Net 3000/4000 performing Network Address Translation
(NAT) traversal.
This configuration needs to be completed for each non-registering peer in this category.
3.3.3.1 Topology Diagram for SIP Static Peer with NAT Traversal
Figure 2 identifies a typical topology for a non-registering access device with the Net-Net
3000/4000 performing NAT traversal. The IP addresses in Figure 1 are used in the
following configuration sections for this peer type.
©
Redundant AS pair
AS1 AS2
Private subnet
192.168.6.0/24
192.168.6.90
AcmePacket SD
192.168.242.110
Access Network:
Public IP Network
192.168.242.0
Public side of IP PBX

Router with NAT (192.168.242.107)
Private subnet
10.10.1.0
IP PBX(10.10.1.60)
2403330053 2403330052
Figure 2 Typical Topology for a Non-registering Access Device with the Net-Net 3000/4000 Performing NAT
Traversal

Configuration Guide [1] and Acme Packet’s Best Currently Practice [7].
©
3.3.3.3 Realm Configuration
The following table describes the realm configuration of the Net-Net 3000/4000 for the
static peer:
Step 1 Enter the realm-config Configuration After logging into the Acme Packet
menu. Net-Net 3000/4000 as an
administrator, enter the “configure
Example:
parameter” mode to add or edit Net-
# realm-config Net 3000/4000 parameters.
(realm-config)# This is located under the media-
manager branch.
Step 2 Enter the identifier for the realm. Configure a unique name for the
realm identification.
Example:
(realm-config)# identifier peer-
1_nat
Step 3 Identify the network interface for Configure the network interface for
the realm. the realm. The network interface
should already have been created.
Example:
(realm-config)# network-interfaces
M00:0
Step 4 Configure the prefix address. Configure the prefix address as the
static peer IP address.
Example:
10.10.1.60
Step 5 Set the access control trust level The access control always remains
to “high”. TRUSTED.
Example:
(realm-config)# access-control-
trust-level high
3.3.3.4 Access Control Configuration

static peer:
Step 1 Enter the SIP Configuration menu. Access control is located under the
Example:
# access-control
(access-control)#
Step 2 Configure the realm id. Set the realm ID for the access
control. This should already be
Example:
configured on the realm-
(access-control)# realm-id peer- configuration.
1_nat
Step 3 Configure the source address. The source address is the static IP
address of the non-registering peer.
Example:
(access-control)# source-address
10.10.1.60
©
Step 4 Configure the destination address. The destination address is the

public-side IP address of the Net-
Example:
Net 3000/4000.
(access-control)# destination-
address 192.168.242.110:5060
Step 5 Configure the transport protocol. Set the transport protocol to “all”,
which includes TCP and UDP.
Example:
(access-control)# transport-protocol
all
Step 6 Configure the trust-level. This ensures that the access control
always remains TRUSTED.
Example:
(access-control)# trust-level high
Step 7 Configure the invalid signal This value is the acceptable invalid
threshold value. signaling messages rate within a
tolerance window.
Example:
(access-control)# invalid-signal-
threshold 1
Step 8 Configure the maximum signal This value is the allowed maximum
threshold value. number of signaling messages
within a tolerance window.
Example:
(access-control)# maximum-signal-
threshold 15000
3.3.3.5 Host Route Configuration

static peer:
Step 1 Enter the host-route Configuration This is located under the system
menu. branch.
Example:
# host-route
(host-route)#
Step 2 Enter the destination network. Configure the destination network as

the static IP address of the non-
Example:
registering peer.
(host-route)# dest-network
10.10.1.60
Step 3 Enter the destination subnet mask. Configure the destination subnet
mask.
Example:
(host-route)# netmask 255.255.255.0
Step 4 Enter the gateway ip address. Configure the gateway IP address as

the public NAT address of the static
Example:
peer.
(host-route)# gateway
192.168.242.107
©
Step 1 Enter Acme Packet configuration Go to the SIP-configuration level

mode. under session-router.
# configure terminal
(configure)# session-router
(session-router)# sip-config
Step 2 Set the egress realm id. Setting the egress realm ID defines
the default route for SIP requests
Example: addressed to destinations outside the
(sip-config)# egress-realm-id home realms address prefix. This
peer-1_nat corresponds to routed messages from
BroadWorks.

defines the signaling interface. The SIP interface is defined for each realm that is defined.
Packet Net-Net 3000/4000 and the non-registering static peer:
Example:
# sip-interface
(sip-interface)#
Example:
Step 3 Set realm-id. Set the realm-ID to which the SIP

interface is connected. This is set to
Example:
the static realm. The realms should
(sip-interface)# realm-id peer-1_nat already be created.
Step 4 Set the sip port. Configure the sip-port interface to

specify the address, port, transport
Example:
type, and allow anonymous criteria.
“address” – IP address on which to
(sip-port)# port 5060 “port” – Port number to use.
(sip-port)# transport-protocol UDP “transport-protocol” – Associate
(sip-port)# allow-anonymous agents- transport protocol with SIP port (UDP
only or TCP).
NOTE: To allow the “sip-interface” “allow-anonymous” – Set criteria for
for the specified realm to support accepting and processing a SIP
the TCP transport, repeat Step 4 and request from another SIP element.
define the “transport-protocol” Setting to “ agents-only” to only
parameter as TCP. allows the traffic from the configured
agents.
©
Step 5 Set the NAT-traversal to “always”. NAT-traversal should be set to

“always” when the SIP-Via and
Example:
transport addresses do not match.
(sip-interface)#nat-traversal always
3.3.3.8 Configure Session Agents

The following steps describe the configuration setup of a session-agent for the static peer:
Step 1 Enter the Session Agent Configuration This is located under the session-
Example:
Step 2 Configure the hostname. Configure the hostname as the IP

address of the public NAT address
Example:
used for the static device IP.
(session-agent)# hostname
192.168.242.107
Step 3 Set the IP address. Configure the IP address as the

public NAT address used for the
Example:
static device IP.
192.168.242.107
Step 4 Set the application protocol to use. Set the application protocol to use the
SIP protocol.
Step 5 Set the transport method to use for Setting the transport-method
the session-agent. parameter to UDP+TCP allows the
session-agent to accept UDP or TCP
transmitted messages.
UDP+TCP
Step 6 Set the realm that the Application The realm-ID must be set for all
Server is in. session-agents.
Example:
(session-agent)# realm-id peer-1_nat
agent. session-agent. Use double quotes if
the description contains spacing
(session-agent)# description “Non-
between words.
registering peer”
Example:
(session-agent)# ping-method options Ping method should be disabled if the
end device does not respond to
pings. Otherwise, Net-Net 3000/4000
thinks the device is out of service.
Step 9 Set the Ping Interval. This is in seconds. Since there

should not be many Net-Net
Example:
3000/4000’s deployed for each
(session-agent)# ping-interval 60 Application Server cluster, this should
not introduce extra message traffic.
This is not required when the ping
method is disabled.
©
Step 10 Configure the proxy mode. The requests are forwarded in the
proxy mode.
Example:
(session-agent)# proxy-mode proxy
Step 11 Configure the redirect mode. The redirect responses are sent back
to the previous hop.
Example:
proxy
Step 12 Set the inbound manipulation id. Configure the inbound manipulation
ID name. This manipulation is
Example:
configured under SIP-manipulation
(session-agent)# in-manipulationid menu.
“ippbx-1-add-record-route”
Step 13 Set the outbound manipulation id. Configure the outbound manipulation
ID name. This manipulation is
Example:
configured under SIP-manipulation
(session-agent)# out-manipulationid menu.
“ippbx-1-strip-route-change-ruri”
3.3.3.9 Configure Local Policy

This table describes the local policy to be used for outgoing calls from the static peer:
Example:
# local-policy

Example:
(local-policy)# to-address *
(local-policy)# source-realm peer-
1_nat

SIP messages.
Example:
(local-policy-attributes)# next-hop next-hop – This is the BroadWorks
SAG:BROADWORKS redundant Application Server cluster
(session-group) defined as the next
(local-policy-attributes)# realm hop for routing traffic.
core
realm – This is the realm in which
(local-policy-attributes)# app- BroadWorks resides.
protocol SIP
app-protocol – This is the protocol to
(local-policy-attributes)# done be used.
©
This table describes the local policy to be used for incoming calls to the static peer:
Example:
# local-policy

Example:
(local-policy)# from-address * 240333005 is the prefix of the DNs
configured on the static peer.
(local-policy)# to-address 240333005
(local-policy)# source-realm peer-
1_nat

SIP messages.
Example:
(local-policy-attributes)# next-hop next-hop – The public NAT address
192.168.242.107 of the static peer is defined as the
next hop for routing traffic.
peer-1_nat realm – This is the realm in which the
static peer resides.
(local-policy-attributes)# app-
protocol SIP app-protocol – This is the protocol to
be used.
(local-policy-attributes)# done
3.3.3.10 SIP Manipulation Configuration

The following configuration is for adding the Record-Route header to the incoming reply or
response messages.

Example:
# sip-manipulation
(sip-manipulation)#
Step 2 Configure the sip manipulation list Set the SIP manipulation list name to
name. the in-manipulation ID in the session
agent configuration.
Example:
add-record-route” the manipulation.
“Adds record route for non-reg
behind NAT”
Example:
# header-rules
(sip-header-rules)#
©
Step 4 Configure the header-rule name. Set a unique header-rule name.

Example:
(sip-header-rules)# name “Add-
Record-Route”
Step 5 Configure the header-name for the Configure the header-name as

header rule. Record-Route since the SIP
manipulation is for the record-route
Example:
headers.
“Record-Route”
Step 6 Configure the action parameter for This manipulation ID is used to add
the header rule. "Record-Route: <sip:
192.168.242.107:5060;lr>" header in
Example:
incoming reply or response
(sip-header-rules)# action add messages, such as 100 Trying.
Therefore, when Net-Net 3000/4000
receives 100 Trying from IP-PBX
through NAT, it then adds Record-
Route header before passing forward
to Net-Net 3000/4000 internal “sipd”.

“reply”.
Example:
(sip-header-rules)# msg-type reply
The following configuration is for deleting the Record-Route header and changing the
Request–URI in the outgoing request messages:

Example:
# sip-manipulation
(sip-manipulation)#
Step 2 Configure the sip manipulation list Set the SIP manipulation list name to
name. the out-manipulation ID in the session
agent configuration.
Example:
strip-route-change-ruri” the manipulation.
“Strip Route and change RURI”
Example:
# header-rules
(sip-header-rules)#
Step 4 Configure the header-rule name. Set a unique header-rule name.

Example:
(sip-header-rules)# name “Delete-
Route”
©
Step 5 Configure the header-name for the Configure the header name as Route
header rule. since the SIP manipulation is for the
Route header.
Example:
“Route”
Step 6 Configure the action parameter for This manipulation is used to strip out
the header rule. the Route headers in the outgoing
request, such as ACK and BYE. This
Example:
is because the NAT device used
(sip-header-rules)# action delete does not strip out the Route header.

“request”.
Example:
Step 8 Enter the header-rule configuration This is located under the SIP-
menu for creating Change-RURI header manipulation menu.
rule.
Example:
# header-rules
(sip-header-rules)#
Step 9 Configure the header-rule name. Configure a unique name for the
header rule.
Example:
(sip-header-rules)# name “Change-
RURI”
Step 10 Configure the header-name for the Configure the header name as
header rule. request-URI since the SIP
manipulation is for the request-URI
Example:
header.
“Request-uri”
Step 11 Configure the action parameter for This is for manipulating the request-
the header rule. uri header in the INVITE.
Example:
(sip-header-rules)# action
manipulate

“request”.
Example:
Step 13 Enter the element-rules This is located under the header-

configuration menu. rules menu.
Example:
# element-rules
(sip-element-rules)#
Step 14 Configure the element-rule name. Configure a unique name for the
element rule.
Example:
(sip-element-rules)# name “Change-
Host”
©
Step 15 Configure the element type. Configure the element type for which
rule needs to be applied.
Example:
(sip-element-rules)# type uri-host
Step 16 Configure the action parameter for This manipulation is to replace a

the header rule. matched value in the request-URI
with a new value.
Example:
(sip-element-rules)# action replace In this case, the value
“adtran.broadworks.net” (the FQDN
of the static peer defined on
BroadWorks), is replaced by
“10.10.1.60” (the IP address of the
static peer). This is because the
static peer (Adtran) does not support
FQDN as hostname.
Step 17 Configure the match-value. Configure the value to be matched in

the request-URI.
Example:
(sip-element-rules)# match-value
Step 18 Configure the new value to be Configure the value to be replaced

replaced. with the matched value in the
request-URI.
Example:
(sip-element-rules)# new-value
10.10.1.60
3.4 Configure SIP Registering SIP Connect Peer

This section identifies additional settings required to support SIP Connect peers. SIP
Connect peers are IP-PBX or PBX trunking gateways that register a single “main” line to a
BroadWorks trunk group. Users behind the PBX device are implicitly registered on the
trunk group via the main line registration.
With this configuration, INVITEs to the device from BroadWorks contain the registered
contact in the request-URI and the user number in the “TO”. The Net-Net 3000/4000 must
be configured (as follows) to support this scenario. This is identified in the Net-Net
3000/4000 documentation as SIP Connect configuration. For more information, see the
Net-Net 4000 ACLI Configuration Guide [1].
This configuration must be added to the Registering Peer configuration described in
section 3.3.1 Configure SIP Registering Peer.
3.4.1 Topology Diagram for Registering SIP Connect Peer

Figure 3 identifies a typical topology for a registering access device with SIP Connect
configuration.
©
Redundant AS pair
AS1 AS2
Private subnet
192.168.6.0/24
192.168.6.90
AcmePacket SD
192.168.242.110
Access Network:
Public IP Network
192.168.242.0
2403330051(registered
main line)
IP PBX(192.168.242.41)
2403330053(PBX User1) 2403330052(PBX User2)
Figure 3 Typical Topology for a Registering Access Device with SIP Connect Configuration
3.4.2 SIP Connect Configuration

The following table identifies the configuration to set the SIP connect option for a realm
configuration:
Step 1 Enter the access side realm-config This is located under the media-
Configuration menu. manager branch.
Example:
# realm-config
©
Step 2 Configure the options parameter. Set the options parameter name sip-
connect-pbx-reg with a “plus” sign in
Example:
front of it. If you type the option
(realm-config)# options +sip- without the “plus” sign, you overwrite
connect-pbx-reg any previously configured options.
When it receives an INVITE request,
the Net-Net 3000/4000 checks the
incoming realm for the sip-connect-
pbx-reg option. If it is configured, the
Net-Net 3000/4000 uses the INVITEs
source address (instead of the AoR
and Contact-URI) to search the
registration cache for a matched
registration entry.
This table identifies the configuration to be set for the SIP interface that accepts
registrations:
Step 1 Enter the access side sip interface This is located under the session-
Example:
# sip-interface
Step 2 Configure the options parameter. This setting allows the Net-Net
3000/4000 to use the source address
Example:
of an INVITE as the key to find a
(sip-interface)# options reg-via- registration entry in the registration
key cache.
When the INVITEs Contact header
matches the registered contact in the
registration entry, the Net-Net
3000/4000 accepts the INVITE
request.
©
3.5 Net-Net 3000/4000 Redundancy Configuration
3.5.1 Local Redundancy Configuration

The Acme Packet Net-Net 3000/4000 provides local redundancy via the virtual IP address
shown in Figure 4 Net-Net 3000/4000 Local Redundancy Configuration. If the active Net-
Net 3000/4000 becomes inactive due to fault or maintenance, the alternate Net-Net
3000/4000 becomes the active Net-Net 3000/4000.
A failover does not impact the access device since it uses a virtual IP address for the Net-
Net 3000/4000 cluster and does not know which Net-Net 3000/4000 unit it is talking to at
any one time.
Instructions for configuring the Net-Net 3000/4000 for local redundancy are not provided
here. For more information, see the Net-Net 4000 ACLI Configuration Guide [1] and/or
consult Acme Packet.
Figure 4 Net-Net 3000/4000 Local Redundancy Configuration
©
3.5.2 Geographic Redundancy Configuration
To support Net-Net 3000/4000 geographic redundancy, the access device must support a
failover mechanism to an alternate address. This is typically handled via prioritized
domain name system (DNS) service locator (SRV) entries but may also be handled by the
static configuration of two or more outbound proxy addresses on the access device. For
the preferred configuration, see the access device manufacturer’s administration guide.
Instructions for configuring the Net-Net 3000/4000 for geographic redundancy are not
provided in this document. For more information, see the Net-Net 4000 ACLI
Configuration Guide [1] and/or consult Acme Packet.
Figure 5 Net-Net 3000/4000 Geographic Redundancy Configuration
3.6 Remote Survivability Configuration

The Acme Packet Net-Net 3000/4000 does not currently support remote survivability.
©
4 Access Device Configuration
This section identifies guidelines for configuration of access devices for use with the Acme
Packet Net-Net 3000/4000.
4.1 SIP Access Device Configuration

This section provides guidelines for configuring SIP access devices for use with the Acme
Packet Net-Net 3000/4000 and BroadWorks.
Most access devices provide the capability to configure an outbound proxy. When an
outbound proxy is configured, all SIP messages are sent to the outbound proxy. The
content of the SIP message does not change – it still contains the configured SIP
proxy/domain.
4.1.1 SIP Registering Access Device Configuration

The Net-Net 3000/4000 requires that SIP access devices be registered to use an
outbound proxy configuration. With this configuration, the access device sends SIP
messages to the Net-Net 3000/4000, but the content of the SIP message contains the
BroadWorks user’s domain, as configured on BroadWorks.
This configuration also applies when registering devices using SIP Connect.
For information on how to configure the outbound proxy, see the BroadWorks Partner
Configuration Guide for the access device or the access device manufacturer’s
administration guide.
Step 1 Configure the SIP Proxy field with Some devices refer to this value as
the domain assigned to the user on something other than “SIP Proxy”.
the Application Server. To find the name of this field, refer to
the device manufacturer’s manual.
Step 2 Configure the Outbound Proxy field Set the Outbound Proxy according to
with the IP address and port the device Partner Configuration
configured in the Net-Net 3000/4000 Guide or manufacturer’s
under the access side sip-interface. administration guide.
4.1.2 SIP Non-registering Access Device Configuration

Non-registering SIP devices often do not provide the capability of configuring an outbound
proxy. In this case, the access device must be configured with the Acme Packet Net-Net
3000/4000 address as the SIP proxy/domain. The Net-Net 3000/4000 must be configured
for routing calls from each non-registering access device. For more information see
sections 3.3.2.Configure SIP Static Peer without NAT Traversal and 3.3.3 Configure SIP
Static Peer with NAT Traversal.
Step 1 Configure the SIP Proxy field with Some devices refer to this value as
the IP address and port configured something other than “SIP Proxy”.
in the Net-Net 3000/4000 under the To find the name of this field, refer to
access side sip-interface. the device manufacturer’s manual.
©
5 SIP Trunking Configuration
This section identifies Acme Packet guidelines for configuration in association with IP-
PBX’s and PBX-Trunking devices used for SIP trunking with BroadWorks.
5.1 Correlation of BroadWorks PBX Classification to Required Acme Packet

Configuration
The BroadWorks Business Trunking Configuration Guide identifies the classification types
for IP-PBX’s and PBX trunking devices. The following table lists the classification types
and identifies the Acme Packet configuration section applicable to each type. Refer to the
BroadWorks Business Trunking Configuration Guide for detailed descriptions for each
PBX classification type.
BroadWorks PBX Classification Acme Packet Configuration
Type Description Section Notes
3.4 Configure SIP Registering

Type A SIP Connect Registering
SIP Connect Peer
Type B devices must be

SIP Connect Non- configured as Type D devices
Type B Not Applicable
Registering on BroadWorks, when behind
Acme Packet.
Type C devices must be

SIP Connect Registering configured as Type A devices
Type C Not Applicable
with Modified Request-URI on BroadWorks, when behind
Acme Packet.
SIP Connect Non- Select configuration section

3.3.3 Configure SIP Static Peer
Type D Registering with Modified based on NAT traversal
with NAT Traversal
Request-URI requirements.
Select configuration section

3.3.3 Configure SIP Static Peer
Type E Device Addressing based on NAT traversal
with NAT Traversal
requirements.
3.3.1 Configure SIP

Type F Subscriber Registering
Registering Peer
©
6 Appendix A: Sample Net-Net 3000/4000 Configuration Files
NOTE: These sample files are examples and should be used for reference only.
6.1 Standard Redundant Net-Net 3000/4000 Configuration for Registering Peers

The following sample configuration file contains a set up for a redundant Acme Packet
Net-Net 3000/4000 which interfaces with the BroadWorks Application Server. The sample
configuration also contains the setup for support of the TCP and UDP transport, and
network-peering between separate non-routing networks.
account-config
hostname localhost
port 1813
strategy Hunt
state enabled
max-msg-delay 60
max-wait-failover 100
trans-at-close disabled
file-output disabled
max-file-size 1000000
max-files 5
file-rotate-time 60
ftp-push disabled
ftp-address 192.168.242.110
ftp-port 21
ftp-user bwftp
ftp-password bwftp
ftp-remote-path
generate-start OK
generate-interim
Reinvite-Response
last-modified-date 2006-04-19 10:43:09
host-routes
dest-network 216.61.24.0
netmask 255.255.255.0
gateway 192.168.242.1
host-routes
netmask 255.255.255.0
gateway 192.168.242.1
local-policy
from-address
*
to-address
*
source-realm
access
activate-time N/A
deactivate-time N/A
state enabled
policy-attribute
next-hop SAG:BROADWORKS
realm core
©
action none
terminate-recursion disabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol
state enabled
media-profiles
media-manager
state enabled
latching enabled
flow-time-limit 86400
initial-guard-timer 300
subsq-guard-timer 300
hnt-rtcp disabled
algd-log-level NOTICE
mbcd-log-level NOTICE
home-realm-id core
red-flow-port 1985
red-mgcp-port 1986
red-max-trans 10000
red-sync-start-time 5000
red-sync-comp-time 1000
max-signaling-bandwidth 775880
max-untrusted-signaling 5
min-untrusted-signaling 4
tolerance-window 30
rtcp-rate-limit 0
network-interface
name M00
sub-port-id 0
hostname
ip-address 192.168.242.110
pri-utility-addr 192.168.242.111
sec-utility-addr 192.168.242.112
netmask 255.255.255.0
gateway 192.168.242.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary 192.168.6.22
dns-ip-backup1
dns-ip-backup2
dns-domain intas.broadworks.net
hip-ip-list 192.168.242.110
ftp-address
icmp-address 192.168.242.110
snmp-address
telnet-address
network-interface
name M10
sub-port-id 0
hostname
ip-address 192.168.6.90
©
netmask 255.255.255.0
gateway 192.168.6.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-backup1
dns-ip-backup2
hip-ip-list 192.168.6.90
ftp-address 192.168.6.90
icmp-address 192.168.6.90
snmp-address
telnet-address 192.168.6.90
network-interface
name wancom1
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
network-interface
name wancom2
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
©
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
phy-interface
name M00
operation-type Media
port 0
slot 0
virtual-mac 00:08:25:01:cd:8e
admin-state enabled
auto-negotiation enabled
duplex-mode FULL
speed 100
phy-interface
name M10
port 0
slot 1
virtual-mac 00:08:25:01:cd:8f
admin-state enabled
duplex-mode FULL
speed 100
phy-interface
name wancom1
operation-type Control
port 1
slot 0
virtual-mac
wancom-health-score 5
phy-interface
name wancom2
port 2
slot 0
virtual-mac
realm-config
identifier access
addr-prefix 0.0.0.0
network-interfaces
M00:0
mm-in-realm disabled
mm-in-network enabled
msm-release disabled
qos-enable disabled
max-bandwidth 0
max-latency 0
max-jitter 0
max-packet-loss 0
©
observ-window-size 0
parent-realm
dns-realm core
media-policy
in-translationid
out-translationid
class-profile
average-rate-limit 1600
access-control-trust-level low
invalid-signal-threshold 1
maximum-signal-threshold 25
untrusted-signal-threshold 4
deny-period 60
symmetric-latching disabled
pai-strip disabled
mm-in-system enabled
restricted-latching None
restriction-mask 32
realm-config
identifier core
addr-prefix 0.0.0.0
network-interfaces
M10:0
qos-enable disabled
max-bandwidth 0
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
dns-realm
media-policy
in-translationid
out-translationid
class-profile
access-control-trust-level high
deny-period 30
pai-strip disabled
restricted-latching None
restriction-mask 32
redundancy-config
state enabled
log-level INFO
health-threshold 75
emergency-threshold 50
port 9090
advertisement-time 500
percent-drift 210
initial-time 1250
becoming-standby-time 45000
becoming-active-time 100
©
cfg-port 1987
cfg-max-trans 10000
cfg-sync-start-time 5000
cfg-sync-comp-time 1000
gateway-heartbeat-interval 0
gateway-heartbeat-retry 0
gateway-heartbeat-timeout 1
gateway-heartbeat-health 0
peer
name ACME1
state enabled
type Primary
destination
address
169.254.1.1:9090
network-interface
wancom1:0
destination
address
169.254.2.1:9090
network-interface
wancom2:0
peer
name ACME2
state enabled
type Secondary
destination
address
169.254.1.2:9090
network-interface
wancom1:0
destination
address
169.254.2.2:9090
network-interface
wancom2:0
session-agent
hostname 192.168.6.20
ip-address 192.168.6.20
port 5060
state enabled
app-protocol SIP
app-type
transport-method UDP+TCP
realm-id core
description BroadWorks Primary AS
carriers
allow-next-hop-lp enabled
constraints disabled
max-sessions 0
max-outbound-sessions 0
max-burst-rate 0
max-sustain-rate 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
sustain-rate-window 0
req-uri-carrier-mode None
proxy-mode Proxy
redirect-action Recurse
©
loose-routing enabled
send-media-session enabled
response-map
ping-method OPTIONS;hops=0
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
ping-from-user-part
session-agent
hostname 192.168.6.21
ip-address 192.168.6.21
port 5060
state enabled
app-protocol SIP
app-type
realm-id core
description BroadWorks Secondary AS
carriers
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
ping-from-user-part
session-group
group-name BROADWORKS
description BroadWorks Hunt Group
state enabled
app-protocol SIP
strategy Hunt
dest
©
192.168.6.20
192.168.6.21
sip-config
state enabled
operation-mode dialog
dialog-transparency enabled
home-realm-id core
egress-realm-id
nat-mode None
registrar-domain *
registrar-host *
registrar-port 5060
init-timer 500
max-timer 4000
trans-expire 4
invite-expire 180
inactive-dynamic-conn 32
pac-method
pac-interval 10
pac-strategy PropDist
pac-load-weight 1
pac-session-weight 1
pac-route-weight 1
pac-callid-lifetime 600
pac-user-lifetime 3600
red-sip-port 1988
red-max-trans 10000
options max-udp-length=0
refer-to-uri-prefix="conf"
register-grace-timer=20
last-modified-date 2007-09-26 11:40:19sip-
feature
name eventlist
realm
support-mode-inbound Pass
require-mode-inbound Pass
proxy-require-mode-inbound Pass
support-mode-outbound Pass
require-mode-outbound Pass
proxy-require-mode-outbound Pass
sip-interface
state enabled
realm-id access
sip-port
address 192.168.242.110
port 5060
allow-anonymous registered
sip-port
address 192.168.242.110
port 5060
transport-protocol UDP
carriers
proxy-mode
redirect-action
contact-mode none
nat-traversal always
©
nat-interval 45
tcp-nat-interval 45
registration-caching enabled
min-reg-expire 7200
registration-interval 120
route-to-registrar enabled
secured-network disabled
teluri-scheme disabled
uri-fqdn-domain
trust-mode all
max-nat-interval 3600
nat-int-increment 10
nat-test-increment 30
sip-dynamic-hnt disabled
stop-recurse 401,407
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid
sip-ims-feature disabled
operator-identifier
anonymous-priority none
max-incoming-conns 0
per-src-ip-max-incoming-conns 0
inactive-conn-timeout 0
network-id
ext-policy-server
default-location-string
charging-vector-mode none
charging-function-address-mode none
ccf-address
ecf-address
term-tgrp-mode none
implicit-service-route disabled
rfc2833-payload 101
rfc2833-mode transparent
sip-interface
state enabled
realm-id core
sip-port
address 192.168.6.90
port 5060
tls-profile
allow-anonymous agents-only
sip-port
address 192.168.6.90
port 5060
tls-profile
carriers
proxy-mode
redirect-action
contact-mode none
nat-traversal none
nat-interval 30
tcp-nat-interval 30
registration-caching disabled
min-reg-expire 7200
©
route-to-registrar disabled
uri-fqdn-domain
trust-mode all
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid sip-ims-feature
disabled
operator-identifier
network-id
ext-policy-server
ccf-address
ecf-address
term-tgrp-mode none
rfc2833-payload 101
steering-pool
ip-address 192.168.242.110
start-port 49152
end-port 65535
realm-id access
network-interface
steering-pool
ip-address 192.168.6.90
start-port 49152
end-port 65535
realm-id core
network-interface
system-config
hostname BroadSoftInterop
description Acme Packet Inc
location
mib-system-contact
mib-system-name
mib-system-location
snmp-enabled enabled
enable-snmp-auth-traps disabled
enable-snmp-syslog-notify disabled
enable-snmp-monitor-traps disabled
enable-env-monitor-traps disabled
snmp-syslog-his-table-length 1
snmp-syslog-level WARNING
system-log-level WARNING
process-log-level NOTICE
©
process-log-ip-address 0.0.0.0
process-log-port 0
call-trace disabled
internal-trace disabled
log-filter all
default-gateway 192.168.242.1
restart enabled
exceptions
telnet-timeout 0
console-timeout 0
©
6.2 Static Peer with NAT Traversal Configuration
The following Net-Net 3000/4000 configuration contains configuration for a static peer with
NAT traversal (see configuration in bold) in addition to the standard configuration.
For the topology represented by this configuration, see section 3.3.3.1 Topology Diagram
for SIP Static Peer with NAT Traversal.
ACME1# show run
access-control
realm-id peer-1
source-address 10.10.1.60
destination-address 192.168.242.110:5060
application-protocol
transport-protocol ALL
access permit
trust-level high
deny-period 30
account-config
hostname localhost
port 1813
strategy Hunt
state enabled
max-msg-delay 60
max-files 5
file-path
file-rotate-time 60
ftp-push disabled
ftp-address 192.168.242.110
ftp-port 21
ftp-user bwftp
ftp-password bwftp
ftp-remote-path
cdr-output-redundancy disabled
generate-start OK
generate-interim
Reinvite-Response
intermediate-period 0
prevent-duplicate-attrs disabled
vsa-id-range
host-routes
netmask 255.255.255.0
gateway 192.168.242.1
host-routes
netmask 255.255.255.0
gateway 192.168.242.1
host-routes
©
netmask 255.255.255.0
gateway 192.168.242.107
local-policy
from-address
*
to-address
*
source-realm
access
activate-time N/A
deactivate-time N/A
state enabled
policy-priority none
policy-attribute
realm core
action none
terminate-recursion enabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
local-policy
from-address
*
to-address
*
source-realm
peer-1
activate-time N/A
deactivate-time N/A
state enabled
policy-attribute
realm core
action none
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
local-policy
from-address
*
to-address
240333005
source-realm
core
activate-time N/A
©
deactivate-time N/A
state enabled
policy-attribute
next-hop 192.168.242.107
realm peer-1
action none
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
media-manager
state enabled
latching enabled
tcp-flow-time-limit 86400
tcp-initial-guard-timer 300
tcp-subsq-guard-timer 300
tcp-number-of-ports-per-flow 2
hnt-rtcp disabled
home-realm-id core
red-flow-port 1985
red-mgcp-port 1986
red-max-trans 10000
app-signaling-bandwidth 0
tolerance-window 30
rtcp-rate-limit 0
min-media-allocation 32000
min-trusted-allocation 1000
deny-allocation 1000
anonymous-sdp disabled
arp-msg-bandwidth 32000
fragment-msg-bandwidth 96000
network-interface
name M00
sub-port-id 0
hostname
ip-address 192.168.242.110
netmask 255.255.255.0
gateway 192.168.242.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
©
retry-count 0
retry-timeout 1
health-score 0
dns-ip-backup1
dns-ip-backup2
dns-timeout 11
hip-ip-list 192.168.242.110
ftp-address
icmp-address 192.168.242.110
snmp-address
telnet-address
network-interface
name M10
sub-port-id 0
hostname
ip-address 192.168.6.90
netmask 255.255.255.0
gateway 192.168.6.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-backup1
dns-ip-backup2
dns-timeout 11
hip-ip-list 192.168.6.90
snmp-address
network-interface
name wancom1
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
©
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
network-interface
name wancom2
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
phy-interface
name M00
port 0
slot 0
admin-state enabled
duplex-mode FULL
speed 100
phy-interface
name M10
port 0
slot 1
admin-state enabled
duplex-mode FULL
speed 100
phy-interface
name wancom1
port 1
slot 0
virtual-mac
©
phy-interface
name wancom2
port 2
slot 0
virtual-mac
realm-config
identifier access
addr-prefix 0.0.0.0
network-interfaces
M00:0
mm-same-ip enabled
bw-cac-non-mm disabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
dns-realm core
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 60
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restricted-latching none
restriction-mask 32
accounting-enable enabled
user-cac-mode none
user-cac-bandwidth 0
user-cac-sessions 0
net-management-control disabled
delay-media-update disabled
codec-policy
codec-manip-in-realm disabled
realm-config
identifier core
addr-prefix 192.168.6.0/24
network-interfaces
M10:0
©
mm-same-ip enabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 30
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restriction-mask 32
user-cac-mode none
user-cac-sessions 0
codec-policy
realm-config
identifier peer-1
addr-prefix 10.10.1.60
network-interfaces
M00:0
mm-same-ip enabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
©
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 60
symmetric-latching enabled
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restriction-mask 32
user-cac-mode none
user-cac-sessions 0
codec-policy
redundancy-config
state enabled
log-level INFO
health-threshold 75
port 9090
percent-drift 210
initial-time 1250
cfg-port 1987
cfg-max-trans 10000
peer
name ACME1
state enabled
type Primary
destination
address
169.254.1.1:9090
network-interface
wancom1:0
destination
address
169.254.2.1:9090
network-interface
wancom2:0
©
peer
name ACME2
state enabled
type Secondary
destination
address
169.254.1.2:9090
network-interface
wancom1:0
destination
address
169.254.2.2:9090
network-interface
wancom2:0
session-agent
hostname
intasprimary.broadworks.net
ip-address
port 5060
state enabled
app-protocol SIP
app-type
transport-method UDP
realm-id core
carriers
max-sessions 0
max-inbound-sessions 0
max-burst-rate 0
max-inbound-burst-rate 0
max-outbound-burst-rate 0
max-sustain-rate 0
max-inbound-sustain-rate 0
max-outbound-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-interval 60
ping-in-service-response-codes
out-service-response-codes
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
©
ping-to-user-part
ping-from-user-part
li-trust-me disabled
in-manipulationid
out-manipulationid
p-asserted-id
trunk-group
max-register-sustain-rate 0
early-media-allow
invalidate-registrations disabled
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-agent
hostname
intassecondary.broadworks.net
ip-address
port 5060
state enabled
app-protocol SIP
app-type
realm-id core
carriers
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
©
ping-from-user-part
in-manipulationid
out-manipulationid
p-asserted-id
trunk-group
early-media-allow
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-agent
hostname 192.168.242.107
ip-address 192.168.242.107
port 5060
state enabled
app-protocol SIP
app-type
realm-id peer-1
description Non-registering peer
carriers
constraints enabled
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
redirect-action Proxy
response-map
ping-method
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
ping-from-user-part
©
in-manipulationid ippbx-1-add-record-
route
out-manipulationid ippbx-1-strip-route-
change-ruri
p-asserted-id
trunk-group
early-media-allow
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-group
state enabled
app-protocol SIP
strategy Hunt
dest
trunk-group
sag-recursion disabled
stop-sag-recurse 401,407
sip-config
state enabled
home-realm-id core
egress-realm-id peer-1
nat-mode none
registrar-domain *
registrar-host *
registrar-port 5060
init-timer 500
max-timer 4000
trans-expire 4
invite-expire 180
pac-method
pac-interval 10
pac-load-weight 1
pac-route-weight 1
red-sip-port 1988
red-max-trans 10000
add-reason-header disabled
enum-sag-match disabled
extra-method-stats disabled
©
sip-feature
name eventlist
realm
sip-interface
state enabled
realm-id access
sip-port
address 192.168.242.110
port 5060
tls-profile
sip-port
address 192.168.242.110
port 5060
tls-profile
carriers
trans-expire 0
invite-expire 0
max-redirect-contacts 0
proxy-mode
contact-mode none
nat-interval 3600
tcp-nat-interval 3600
min-reg-expire 30
uri-fqdn-domain
trust-mode all
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid NAT-IP
operator-identifier
network-id
ext-policy-server
©
ccf-address
ecf-address
term-tgrp-mode none
rfc2833-payload 101
constraint-name
response-map
local-response-map
sip-interface
state enabled
realm-id core
sip-port
address 192.168.6.90
port 5060
tls-profile
carriers
trans-expire 0
invite-expire 0
proxy-mode
redirect-action
contact-mode none
nat-traversal none
nat-interval 30
tcp-nat-interval 30
min-reg-expire 300
uri-fqdn-domain
trust-mode all
port-map-start 0
port-map-end 0
in-manipulationid
operator-identifier
network-id
ext-policy-server
ccf-address
ecf-address
term-tgrp-mode none
©
rfc2833-payload 101
constraint-name
response-map
local-response-map
sip-interface
state enabled
realm-id peer-1
sip-port
address 192.168.242.110
port 5060
tls-profile
allow-anonymous all
carriers
trans-expire 0
invite-expire 0
proxy-mode
redirect-action
contact-mode none
nat-interval 30
tcp-nat-interval 90
min-reg-expire 300
uri-fqdn-domain
trust-mode agents-only
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid
operator-identifier
network-id
ext-policy-server
charging-vector-mode pass
charging-function-address-mode pass
ccf-address
ecf-address
term-tgrp-mode none
rfc2833-payload 101
constraint-name
response-map
local-response-map
©
sip-manipulation
name ippbx-1-add-record-route
description Adds record route for non-reg behind NAT
header-rule
name Add-Record-Route
header-name Record-Route
action add
comparison-type case-sensitive
match-value
msg-type reply
new-value
methods
element-rule
name add-record-route
parameter-name
type header-value
action add
match-val-type any
match-value
new-value <sip:192.168.242.107:5060;lr>
sip-manipulation
name ippbx-1-strip-route-change-ruri
description Strip Route and change RURI
header-rule
name Delete-Route
header-name Route
action delete
match-value
msg-type request
new-value
methods
header-rule
name Change-RURI
header-name request-uri
action manipulate
match-value
msg-type request
new-value
methods
element-rule
name Change-Host
parameter-name
type uri-host
action replace
match-val-type any
match-value adtran.broadworks.net
new-value 10.10.1.60
steering-pool
ip-address 192.168.242.110
start-port 49152
end-port 65535
realm-id access
network-interface
steering-pool
©
ip-address 192.168.6.90
start-port 49152
end-port 65535
realm-id core
network-interface
steering-pool
ip-address 192.168.242.110
start-port 49152
end-port 65535
realm-id peer-1
network-interface M00:0
system-config
location
mib-system-contact
mib-system-name
mib-system-location
process-log-port 0
call-trace disabled
log-filter all
restart enabled
exceptions
telnet-timeout 0
console-timeout 0
remote-control enabled
link-redundancy-state disabled
task done
ACME1#
©
6.3 Static Peer without NAT Traversal Configuration
The following Net-Net 3000/4000 configuration contains configuration for a static peer
without NAT traversal (see configuration in bold) in addition to the standard configuration.
For the topology represented by this configuration, see section 3.3.3.1 Topology Diagram
for SIP Static Peer with NAT Traversal.
ACME1# show run
access-control
realm-id peer-1
source-address 192.168.242.41
destination-address 192.168.242.110:5060
application-protocol
transport-protocol ALL
access permit
trust-level high
deny-period 30
account-config
hostname localhost
port 1813
strategy Hunt
state enabled
max-msg-delay 60
max-files 5
file-path
file-rotate-time 60
ftp-push disabled
ftp-address 192.168.242.110
ftp-port 21
ftp-user bwftp
ftp-password bwftp
ftp-remote-path
cdr-output-redundancy disabled
generate-start OK
generate-interim
Reinvite-Response
intermediate-period 0
prevent-duplicate-attrs disabled
vsa-id-range
host-routes
netmask 255.255.255.0
gateway 192.168.242.1
host-routes
netmask 255.255.255.0
gateway 192.168.242.1
host-routes
©
netmask 255.255.255.0
gateway 192.168.242.71
local-policy
from-address
*
to-address
*
source-realm
access
activate-time N/A
deactivate-time N/A
state enabled
policy-attribute
realm core
action none
terminate-recursion enabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
local-policy
from-address
*
to-address
240333005
source-realm
core
activate-time N/A
deactivate-time N/A
state enabled
policy-attribute
next-hop 192.168.242.41
realm peer-1
action none
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
local-policy
from-address
*
to-address
*
source-realm
peer-1
activate-time N/A
©
deactivate-time N/A
state enabled
policy-attribute
realm core
action none
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
media-manager
state enabled
latching enabled
tcp-flow-time-limit 86400
tcp-initial-guard-timer 300
tcp-subsq-guard-timer 300
tcp-number-of-ports-per-flow 2
hnt-rtcp disabled
home-realm-id core
red-flow-port 1985
red-mgcp-port 1986
red-max-trans 10000
app-signaling-bandwidth 0
tolerance-window 30
rtcp-rate-limit 0
min-media-allocation 32000
min-trusted-allocation 1000
deny-allocation 1000
anonymous-sdp disabled
arp-msg-bandwidth 32000
fragment-msg-bandwidth 0
network-interface
name M00
sub-port-id 0
hostname
ip-address 192.168.242.110
netmask 255.255.255.0
gateway 192.168.242.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
©
retry-count 0
retry-timeout 1
health-score 0
dns-ip-backup1
dns-ip-backup2
dns-timeout 11
hip-ip-list 192.168.242.110
ftp-address
icmp-address 192.168.242.110
snmp-address
telnet-address
network-interface
name M10
sub-port-id 0
hostname
ip-address 192.168.6.90
netmask 255.255.255.0
gateway 192.168.6.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-backup1
dns-ip-backup2
dns-timeout 11
hip-ip-list 192.168.6.90
snmp-address
network-interface
name wancom1
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
©
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
network-interface
name wancom2
sub-port-id 0
hostname
ip-address
netmask 255.255.255.0
gateway
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address
phy-interface
name M00
port 0
slot 0
admin-state enabled
duplex-mode FULL
speed 100
phy-interface
name M10
port 0
slot 1
admin-state enabled
duplex-mode FULL
speed 100
phy-interface
name wancom1
port 1
slot 0
virtual-mac
©
phy-interface
name wancom2
port 2
slot 0
virtual-mac
realm-config
identifier access
addr-prefix 0.0.0.0
network-interfaces
M00:0
mm-same-ip enabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
dns-realm core
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 60
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restriction-mask 32
user-cac-mode none
user-cac-sessions 0
codec-policy
realm-config
identifier core
addr-prefix 192.168.6.0/24
network-interfaces
M10:0
©
mm-same-ip enabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 30
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restriction-mask 32
user-cac-mode none
user-cac-sessions 0
codec-policy
realm-config
identifier peer-1
addr-prefix 192.168.242.41
network-interfaces
M00:0
mm-same-ip enabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
parent-realm
©
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
deny-period 60
symmetric-latching enabled
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restriction-mask 32
user-cac-mode none
user-cac-sessions 0
codec-policy
redundancy-config
state enabled
log-level INFO
health-threshold 75
port 9090
percent-drift 210
initial-time 1250
cfg-port 1987
cfg-max-trans 10000
peer
name ACME1
state enabled
type Primary
destination
address
169.254.1.1:9090
network-interface
wancom1:0
destination
address
169.254.2.1:9090
network-interface
wancom2:0
©
peer
name ACME2
state enabled
type Secondary
destination
address
169.254.1.2:9090
network-interface
wancom1:0
destination
address
169.254.2.2:9090
network-interface
wancom2:0
session-agent
hostname
ip-address
port 5060
state enabled
app-protocol SIP
app-type
realm-id core
carriers
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
©
ping-to-user-part
ping-from-user-part
in-manipulationid
out-manipulationid
p-asserted-id
trunk-group
early-media-allow
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-agent
hostname
ip-address
port 5060
state enabled
app-protocol SIP
app-type
realm-id core
carriers
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-interval 60
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
©
ping-from-user-part
in-manipulationid
out-manipulationid
p-asserted-id
trunk-group
early-media-allow
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-agent
hostname 192.168.242.41
ip-address 192.168.242.41
port 5060
state enabled
app-protocol SIP
app-type
realm-id peer-1
description Non-registering peer
carriers
constraints enabled
max-sessions 0
max-burst-rate 0
max-sustain-rate 0
min-seizures 5
min-asr 0
time-to-resume 0
ttr-no-response 0
in-service-period 0
burst-rate-window 0
proxy-mode Proxy
response-map
ping-method
ping-interval 0
media-profiles
in-translationid
out-translationid
trust-me disabled
request-uri-headers
stop-recurse
local-response-map
ping-to-user-part
ping-from-user-part
©
in-manipulationid
out-manipulationid ippbx-1-change-ruri
p-asserted-id
trunk-group
early-media-allow
rfc2833-mode none
rfc2833-payload 0
codec-policy
session-group
state enabled
app-protocol SIP
strategy Hunt
dest
trunk-group
sag-recursion disabled
stop-sag-recurse 401,407
sip-config
state enabled
home-realm-id core
egress-realm-id peer-1
nat-mode none
registrar-domain *
registrar-host *
registrar-port 5060
init-timer 500
max-timer 4000
trans-expire 4
invite-expire 180
pac-method
pac-interval 10
pac-load-weight 1
pac-route-weight 1
red-sip-port 1988
red-max-trans 10000
add-reason-header disabled
enum-sag-match disabled
extra-method-stats disabled
sip-feature
name eventlist
©
realm
sip-interface
state enabled
realm-id access
sip-port
address 192.168.242.110
port 5060
tls-profile
sip-port
address 192.168.242.110
port 5060
tls-profile
carriers
trans-expire 0
invite-expire 0
proxy-mode
contact-mode none
nat-interval 3600
tcp-nat-interval 3600
min-reg-expire 30
uri-fqdn-domain
trust-mode all
port-map-start 0
port-map-end 0
in-manipulationid
disabled
operator-identifier
network-id
ext-policy-server
ccf-address
©
ecf-address
term-tgrp-mode none
rfc2833-payload 101
constraint-name
response-map
local-response-map
sip-interface
state enabled
realm-id core
sip-port
address 192.168.6.90
port 5060
tls-profile
carriers
trans-expire 0
invite-expire 0
proxy-mode
redirect-action
contact-mode none
nat-traversal none
nat-interval 30
tcp-nat-interval 30
min-reg-expire 300
uri-fqdn-domain
trust-mode all
port-map-start 0
port-map-end 0
in-manipulationid
operator-identifier
network-id
ext-policy-server
ccf-address
ecf-address
term-tgrp-mode none
rfc2833-payload 101
©
constraint-name
response-map
local-response-map
sip-interface
state enabled
realm-id peer-1
sip-port
address 192.168.242.110
port 5060
tls-profile
allow-anonymous all
carriers
trans-expire 0
invite-expire 0
proxy-mode
redirect-action
contact-mode none
nat-traversal none
nat-interval 30
tcp-nat-interval 90
min-reg-expire 300
uri-fqdn-domain
trust-mode agents-only
port-map-start 0
port-map-end 0
in-manipulationid
disabled
operator-identifier
network-id
ext-policy-server
charging-vector-mode pass
charging-function-address-mode pass
ccf-address
ecf-address
term-tgrp-mode none
rfc2833-payload 101
constraint-name
response-map
local-response-map
sip-manipulation
©
name ippbx-1-change-ruri
description Change ruri
header-rule
name change-RURI
header-name request-uri
action manipulate
match-value
msg-type request
new-value
methods
element-rule
name Change-
Host
parameter-name
type uri-
host
action replace
match-val-type any
comparison-type case-
sensitive
match-value
new-value
192.168.242.41
steering-pool
ip-address 192.168.242.110
start-port 49152
end-port 65535
realm-id access
network-interface
steering-pool
ip-address 192.168.6.90
start-port 49152
end-port 65535
realm-id core
network-interface
system-config
location
mib-system-contact
mib-system-name
mib-system-location
process-log-port 0
call-trace disabled
log-filter all
©
restart enabled
exceptions
telnet-timeout 0
console-timeout 0
remote-control enabled
link-redundancy-state disabled
task done
©
References
[1] Acme Packet. 2009. Net-Net 4000 ACLI Configuration Guide. Available from Acme
Packet at http://support.acmepacket.com.
[2] BroadSoft, Inc. 2012. BroadWorks Device Management Configuration Guide,

Release 18.0. Available from BroadSoft at xchange.broadsoft.com.
[3] BroadSoft, Inc. 2012. BroadWorks Redundancy Guide, Release 18.0. Available
from BroadSoft at xchange.broadsoft.com.
[4] BroadSoft, Inc. 2012. BroadWorks Session Controller Interoperability Test Plan,
Release 18.0. Available from BroadSoft at xchange.broadsoft.com.
[5] BroadSoft, Inc. 2012. BroadWorks Business Trunking Configuration Guide, Release
18.0. Available from BroadSoft at xchange.broadsoft.com.
[6] BroadSoft, Inc. 2012. BroadWorks Network Server Product Description, Release
18.0. Available from BroadSoft at xchange.broadsoft.com.
[7] Acme Packet. 2012. BCP – Basic DDoS Configuration for SIP Access
Environments. Available from Acme Packet at http://support.acmepacket.com.
©

PartnerConfigGuide - Acme - Packet - Net-Net - 3000-4000 - Series R18 BROADSOFT

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

PartnerConfigGuide - Acme - Packet - Net-Net - 3000-4000 - Series R18 BROADSOFT

Uploaded by

Copyright:

Available Formats

BroadSoft Partner Configuration Guide

Acme Packet Net-Net 3000/4000 Series

9737 Washingtonian Blvd., Suite 350

Version Reason for Change

1.1 Introduced document with version sd110b19.

1.2 Updated document with comments from Acme Packet.

1.3 Updated document with version 1.3.0 B25.

1.4 Edited document.

1.5 Updated document with version 1.3.3.

1.6 Edited document.

1.8 Edited document.

2.1 Edited document.

2.5 Edited changes and published document.

2.7 Edited changes and published document.

2.9 Edited changes and published document.

3.1 Edited changes and published document.

3.2 Minor corrections.

3.3 Edited changes and published document.

3.4 Minor update to section 4.2.1.2.2.

3.5 Edited changes and published document.

3.6 Removed uaCSTA gateway config instructions.

3.7 Edited changes and published document.

3.8 Minor update to section 4.2.1.2.1.

3.9 Edited changes and published document.

4.0 Added Delay Media Update configuration.

4.1 Edited and published document.

4.3 Edited and published document.

4.4 Updated section 4.3.2.3, Step 3, option 2.

4.5 Edited and published document.

4.7 Edited and published document.

4.8 Amended workaround for Acme Packet issue AP26131.

4.9 Edited and published document.

5.1 Edited changes and published document.

5.2 Minor updates.

5.3 Edited changes and published document.

5.4 Edited changes.

5.5 Edited changes and published document.

5.7 Edited changes and published document.

5.8 Updated Media Manager section.

5.9 Edited changes and published document.

5.10 Rearranged various sections.

5.11 Edited changes and published document.

5.13 Made minor editorial changes.

5.14 Edited changes and published document.

2 Interoperability Status ......................................................................................................................8

2.1 Verified Versions

Verified Versions Table

Date BroadWorks 3000/4000 Verified 3000/4000 Compatible Versions

03/2012 Release 18.sp1 C6.3.0 F1P6 Any maintenance release of the

12/2009 Release 16.0 C6.1.0 M2P4 Any maintenance release of the

09/2007 Release 14.sp2 C5.0.0p7 Any maintenance release of the

09/2006 Release 14.sp1 4.1.1p42

2.2 Interface Capabilities Supported

Test Plan Package Test Plan Package Items Supported Comments

Basic Call Origination Yes

Call Termination Yes

Session Audit Yes

Session Timer Yes

Forked Dialog Yes

Early UPDATE Yes

181 Call Being Forwarded Yes

DTMF – Inband Yes

DTMF – RFC 2833 Yes