BW SANetworkServerModule5 R120

BroadWorks System Administration
Module 5: Network Server Release 12 Version 1
May 2005
70
Module 5: Agenda
BroadWorks Network Server
Brief review of Network Server
Redundancy
Overview and implementation
SIP/MGCP Overview
SIP redirect message
Enterprise and Private Policies

Concept of an enterprise Private policies and policy instances
Public Policies and Instances

Translation policies Routing policies
Network Elements
Hosting and resource network elements
Advanced Feature
Configurable policy precedence
71
2005 BroadSoft, Inc. Proprietary and Confidential; Do Not Copy, Duplicate, or Distribute
71
Module Objectives
At the end of this module, you will be able to:
Explain the Network Server SIP Redirection function Explain the Network Server Media Server Selection function Understand Policies, Policy Instances and Profiles Understand the difference between Public and Private policies Understand Network Server call processing flow Explain the function of Public and Private policies
72
72
Network Server Reference Documents

BroadWorks Network Server Product Description BroadWorks NNACL Translation File User Guide BroadWorks Dialing Plans Guide BroadWorks DNs, CCs, and NDCs Guide BroadWorks E.164 Overview Guide BroadWorks Special Call Types Routing Guide
73
73
Network Server
Network Devices
SIP
CLI
NS1
Telne t/SSH
NS2
Web Browser
HTTP
/SSL
SIP
AS1
74
SIP
AS1
Centralized Routing
E.164 and URL supported transaction-based system. Enterprise voice VPN services. Policy-based routing. Acts as SIP redirect server: 302 Moved Temporarily. Translations and routing.
Management
Multi-location enterprise portal. Self-service and private dial plan management.
Location Register
SyncAPI maps user or group addresses to owning Application Server.
Media Server Selection

Locates closest Media Server to the end user or network gateway. Uses proprietary MSS protocol to send list of Media Servers to the Application Server.
SIMPLE Support
Supports Windows Messenger communications.
74
Network Server Redundancy
DB
DB
ttR
EP ttR
ttR EP
EP ttR
EP
DB
DB
DB
75
Network Server Clustered Architecture

Network Servers are deployed in a cluster model, whereby servers providing duplicate functionality are deployed together. The cluster model has been designed to meet capacity, scalability, and redundancy requirements.
Redundancy
Network Servers are deployed in an N+1 configuration for redundancy. Network Server provides IP interface redundancy.
Scalability
Network Servers are independent of one another. Each Network Server has its own image of the data and can be used to add new data.
Data Replication
Network Server is delivered with the commercial database, TimesTen. When a change occurs in a server, data is automatically replicated to the other Network Server databases. Replication ensures consistency between servers.
Load Balancing
Load balancing ensures distributed usage of the Network Servers in a configuration and also permits Network Servers to operate in failover mode. Load balancing between Network Servers is performed through route list management; Application Servers use a pre-defined route list or a DNS-returned route list.
75
Network Server User Hierarchy

System provider
Group provisioning administrator
Enterprise administrator
76
Levels of Access
System provider Accesses and manages all Network Server information. Performs system maintenance and management, maintains system and subscriber security, and monitors system events. Sets system-wide service and interface parameters to configure public routing and translations functionality and configure network elements. Creates and manages enterprise private policies. Customizes and brands the BroadWorks interface. Group provisioning administrator Management access to subscriber management level. No access to system information and policies. Enterprise administrator Access to information related to a specific enterprise. Views enterprise and groups attributes associated with enterprise. Manages private policies. Verifies private policies.
76
Network Server Centralized Routing
Network Server Network element: Application Server Network gateway Private gateway Softswitch
INVITE (to, from)
302 Temp. Moved (destinations)
77
Network Server
Provides a centralized repository of IP telephony routing information. Maintains a topology of the network allowing flexible routing policies. Policy-driven engine to determine destinations: location register, centralized routing. Translations are DN-driven (E.164 encoding is imposed). Transaction based (stateless).
77
Network Server: SIP Redirect Server

Dialed Digits Originator
INVITE sip:2403649257@192.168.5.101;user=phone SIP/2.0 Via:SIP/2.0/UDP 192.168.5.100;branch=z9hG4bK-BroadWorks.192.168.5.100-192.168.5.101V5060-0-557386564793232821-1085594015366 From:"grp_4 Test2"<sip:+12403649253@192.168.5.100;user=phone>;tag=793232821-1085594015366 To:<sip:2403649257@192.168.5.101;user=phone> Call-ID:BW13533503652605040226336760090@192.168.5.100 CSeq:557386564 INVITE Contact:<sip:192.168.5.100:5060> Network Server
SIP/2.0 302 Moved temporarily Via:SIP/2.0/UDP 192.168.5.100;branch=z9hG4bK-BroadWorks.192.168.5.100-192.168.5.101V5060-0-557386564793232821-1085594015366 From:"grp_4 Test2"<sip:+12403649253@192.168.5.100;user=phone>;tag=793232821-1085594015366 To:<sip:2403649257@192.168.5.101;user=phone> Contact 1 Call-ID:BW13533503652605040226336760090@192.168.5.100 CSeq:557386564 INVITE Contact:<sip:2403649257@192.168.5.100:5060;user=phone>;q=0.5;ct=LO;ton=PUBLIC;cat=LOCAL,<sip:2403649257 @192.168.5.107:5060;user=phone>;q=0.25;ct=LO;ton=PUBLIC;cat=LOCAL Contact 2
78
SIP Redirect Function

Network Server receives incoming INVITE from network element (NE). Network Server processes INVITE and applies policies based on dialed digits, originator, forwarding party. Network Server returns 302 Moved Temporarily message to NE. NE creates a new INVITE with URI equal to the Contact info provided. If first Contact does not respond, NE will route advance to next contact.
78
Network Server Centralized Network Topology

Network Server
Network Elements (NEs) RoutingNEs RoutingNEs
Interconnection Interconnection to to PSTN PSTN No No User User association association Softswitch, Softswitch, Public Public Gateway Gateway (AS5350) (AS5350)
Groups/Users/Enterprises
HostingNE HostingNE Association Association Users Users (DNs, (DNs, URLs) URLs)
Group1 Group1
HostingNEs HostingNEs
Interconnection Interconnection support support for for users users AppServer, AppServer, Private Private Gateway Gateway (AS5350) (AS5350)
Enterprise 1 Manual association of groups

HostingNE HostingNE Association Association Users Users (DNs, (DNs, URLs) URLs)
Groups share same private dial plans Group2 Group2
ResourceNEs ResourceNEs
Available Available network network resources resources Media Media Server Server SIMPLE SIMPLE Proxies Proxies
79
Network Topology
Network topology must be known by the Network Server to return a contact for calls from the network elements. Users and their groups must be known to the Network Server to return a contact for their calls to proceed.
79
Translations and Routing Basics

Network Server uses policies to translate and route incoming calls Policy is a set of rules defining how to translate and route calls Two families of policies:
Public policies: Globally defined and assigned to routing profiles by
the system provider
Private policies: Assigned and configured by enterprises and are

used to provide VPN-type services
Policies are configurable by Network Server administrator
80
80
Policies and Policy Instances

Policy
Call Type Near-End Routing Far-End Routing
Policy Instance
Call Type EM
Call Type LO, TO Call Type INT
Near-End LO Far-End TO Far-End INT
Enterprise/ Group/NE
Enterprise Enterprise
NE NE
Group Group
81
Policy
Set of rules used to translate or route a call. Can be network-wide or specific to an enterprise. Usually has configuration information that customizes the policy, thereby creating a policy instance.
Policy Instance
Customization of a policy. Used to provide a specific type of processing, for example, on-net routing. Public policy instances can be grouped to create a routing profile which can be assigned to enterprises, groups, HostingNE, or RoutingNE. Private policy instances are assigned to an enterprise.
81
Public Routing Profiles

Policy
Call Type Near-End Routing Far-End Routing
Policy Instance
Call Type EM
Call Type LO, TO Call Type INT
Near-End LO Far-End TO Far-End INT
Profile
Profile 1
Profile 2
Enterprise/ Group/NE
Enterprise Enterprise
NE NE
Group Group
82
Public Routing Profile

A routing profile is a set of public policies. A routing profile can be assigned to a RoutingNE, HostingNE, enterprise, or group. Relationship between public policies, policy instances, profiles, and enterprises (consisting of groups of subscribers) A public policy can have multiple instances. A public policy instance can be assigned to more than one profile. A public routing profile can be assigned to more than one enterprise, group, HostingNE, or RoutingNE. A public policy is triggered (applied to a call) or not based on the call type returned by translations.
82
Private Policy Subscription Model
Policy
EXT Dialing
Voice
VPN
Far-End Hop Off
Policy Instance
EXT Dialing
EXT Dialing
Voice VPN
Far-End Hop Off
Far-End Hop Off
Enterprise
Enterprise Enterprise A A Enterprise Enterprise B B
83
Private Policy Subscription Model

There is no profile concept for private policies Private policies instances are directly assigned to enterprises
83
Public Profile/Private Policy Assignment

Network Server
Network Elements (NEs) RoutingNEs RoutingNEs
Public Public Routing Routing Profile Profile
Groups/Users/Enterprises
Group1 Group1
HostingNEs HostingNEs
Public Routing Profile Private Policies
Enterprise 1
ResourceNEs ResourceNEs
Not Not Applicable Applicable
Group2 Group2
84
RoutingNE Profile Selection

If the call is incoming from a RoutingNE, the RoutingNE public profile is selected.
HostingNE Profile Selection

Users belong to groups that are associated with a HostingNE. Group can belong to enterprises. Groups, enterprises, and HostingNEs can have public profiles associated to them. Network Server first selects the group profile, if available, then performs an intersection with the enterprise profile. Group profile policies have precedence over enterprise profile policies. HostingNE profile is only when the FROM: DN is not identified (not a known Network Server DN or URL).
84
Network Server: Policy Precedence

Condition
Enterprise Policies
Order
1 2
Policy
Private Extension Dialing Voice VPN Originator Redirect Pre-Call Typing Call Typing Enterprise Subscriber Location (enterprise policy) Number Portability Subscriber Location Far-End Hop-Off (enterprise policy) Call Screening Enterprise NGW Routing (enterprise policy) Service Center Routing Rate Based Routing Equal Access Far-End Routing Near-End Routing Tandem Overflow Network URL Dialing (Invite) Private SIMPLE (Subscribe and Message) SIMPLE (Subscribe and Message) Enterprise Media Server Selection Media Server Selection
Public Policies
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
URL-Dialed Calls
1 2 3
MSS Call
85
1 2
Network Server Policies

Private policies can be assigned to an enterprise. Public, URL and Media Server selection policies can be associated together in a profile and then assigned to: Network element Enterprise Group
85
Configurable Policy Precedence

NS_CLI/System/CallP/PolicyPrecedence> get Precedence Policy Default Domain ================================================= 1 ExtDialing true private 2 EntSIMPLE true private 2 voiceVPN true private 4 EntMediaSrvSel true public 4 UrlDialing true public 6 OrigRedirect true public 7 PreCallTyping true public 8 CallTyping true public 8 MediaSrvSel true public 8 SIMPLE true public 11 EntSubLocation true public 12 NumberPortability true public 13 SubLocation true public 14 FarEndHopOff true public 15 CallScreening true public 16 EntNGWRouting true public 17 SvcCtrRtg true public 18 RCBasedRtg true public 19 EqualAccess true public 20 FarEndRtg true public 21 NearEndRtg true public 22 TandemOverflow true public
86
Configurable Policy Precedence

The Network Server now supports the following ordering functions: Move policy A before policy B. Move policy C after policy D. Reset the precedence number of policy E to its original default value. The actual new position of policy E relative to the others is undetermined as the order of the other policies might have been changed by previous commands. Reset the precedence number of all policies to their original default value.
86
PolicyPrecedence
NS_CLI/System/CallP/PolicyPrecedence> set policy NearEndRtg after SvcCtrRtg [Warning 12345] This change may adversely impact call processing and could cause call failures. Please verify that the new policy precedence allows your Network Server to properly route calls. Please confirm (Yes, Y, No, N): y
87
Set
<attribute>, Choice = {defaultAll, policy} policy: <name>, Choice = {CallScreening, CallTyping, EntMediaSrvSel, EntNGWRouting, EntSIMPLE, EntSubLocation, EqualAccess, ExtDialing, FarEndHopOff, FarEndRtg, MediaSrvSel, NearEndRtg, NumberPortability, OrigRedirect, PreCallTyping, SIMPLE, SubLocation, SvcCtrRtg, TandemOverflow, UrlDialing, voiceVPN} <action>, Choice = {after, before, default} after: <name>, Choice = {CallScreening, CallTyping, EntMediaSrvSel, EntNGWRouting, EntSIMPLE, EntSubLocation, EqualAccess, ExtDialing, FarEndHopOff, FarEndRtg, MediaSrvSel, NearEndRtg, NumberPortability, OrigRedirect, PreCallTyping, SIMPLE, SubLocation, SvcCtrRtg, TandemOverflow, UrlDialing, voiceVPN} before: <name>, Choice = {CallScreening, CallTyping, EntMediaSrvSel, EntNGWRouting, EntSIMPLE, EntSubLocation, EqualAccess, ExtDialing, FarEndHopOff, FarEndRtg, MediaSrvSel, NearEndRtg, NumberPortability, OrigRedirect, PreCallTyping, SIMPLE, SubLocation, SvcCtrRtg, TandemOverflow, UrlDialing, voiceVPN}
87
Call Processing
Incoming Call Call Setup Phase Private Processing A
Private Calls
Public Calls
Call Typing Phase Screening Phase On-Net Routing A Off-Net Routing Treatment Phase
302
Response Phase
4xx or 5xx
Outgoing Call
88
The Network Server call processing model is based on a multi-stage approach; phases are mapped to one or more policies.
Call Setup
Maps incoming call to enterprise/routing element. Identifies public profile enterprise/routing element. Identifies private policies associated with enterprise.
Private Processing
Applies private policies associated with enterprise. No match, call may or may not continue to public processing depending on permissive/nonpermissive setting.
Public Processing
Applies public policies associated with selected profile.
88
Configuration Example
Cisco 53xx NGW
RoutingNE: ngw1 192.168.2.133
ResourceNe: ms1 192.168.5.181
Media Server
NGW
ResourceNe: ms2 192.168.5.185
Media Server
NetServer: ns1 192.169.5.183
Network Server
NGW
PSTN
Cisco 3600 NGW
HostingNE: PBX1 192.168.6.155
Legacy PBX
Application Server
HostingNe: as1 192.168.5.180
RoutingNE: ngw2 192.168.2.150
NGW
PSTN
NGW IAD IAD
Site=SITE1
Cisco 2600 NGW

HostingNE: PRIV_514 192.168.6.190
PBX
ENT1/GRP1
301 977-7xxx
ENT1/GRP2
240 364 4xxx
ENT1/GRP3
301 977 2xxx
89
Network Server Dial Plan: Private Policies

AS groups (GRP2/GRP3) and PBX users (GRP1) are part of the ENT1 enterprise. ENT1 has ExtDialing assigned to support redundancy. Private dialing using ENT1 VoiceVPN private policy: 4xxx/2xxx VoiceVPN dialing to groups, 7xxx VoiceVPN dialing to PBX users 9+ PSTN dialing for PSTN local/toll/international calls 911/411 calls do not require 9+ dialing Calls to 514 area code use the ENT1 FarEndHopOff private policy to route to private gateway PRIV_514 and drop off as local 10-digit calls. Site1 users use the ENT1 EntNGWRouting policy to route DA calls to private gateway PRIV_514.
Network Server Dial Plan: Public Policies

CallTyping policy for proper setting of call type. SubLocation policy- allowing on-net calling between all hosted. MediaSrvSel policy allowing for MS selection by the Network Server. Local calls from 240364xxxx users use ngw1, Local calls from 301977xxxx users use ngw2 (NearEndRtg). Toll calls for all users use ngw1, International calls for all users use ngw2 (FarEndRtg). 911 calls from 240364xxxx use ngw1, 911 calls from301977xxxx use ngw1 and prepend a 99 gateway routing prefix (SvcCtrRtg). 411 calls from all users use ngw1 or ngw2 after 411 has been replaced by 18005551234 routing number to preferred OA carrier (SvcCtrRtg).
89
Configuration Steps
Step 1: Basic Network Server Configuration
Network Server identity
Step 2:Public Policy Configuration

Public policies instances NNACL and LCA file for public routing Public profiles for enterprise and routing element assignment Equal access carriers
Step 3: Network Server Device Configuration

Hosting NE entities Public routing NE entities Media Servers
Step 4: Public Routing Configuration

Number Portability Fixed static Near/Far-End Route list Service Center Routing Route list Rate Center Based Routing
Step 5: Enterprise Private Policy Configuration

Create enterprises and assign private policies Create VoiceVPN Dial Plan Set up FarEndHopOff Set up EntNGWRouting
90
90
Basic Network Server Configuration

NS_CLI/System/Alias> add 192.169.5.183 NS_CLI/System/Alias> add ns.lab.broadsoft.com NS_CLI/System/Alias> add ns1.lab.broadsoft.com NS_CLI/System/Alias> get About to access 6 entries. Continue? Please confirm (Yes, Y, No, N): y Retrieving data... Please wait... 127.0.0.1 192.169.5.183 ns.lab.broadsoft.com ns1.lab.broadsoft.com
91
91
Public Policies
Service provider policies
Pre-Call Typing (CallTyping) Call Typing (CallTyping) Call Screening (CallScreening) Number Portability (NumberPortability) Subscriber Location (SubLocation) Originator Redirection (OrigRedirect) Service Center Routing (SvcCtrRtg) Rate Center Based Routing (RCBasedRtg) Equal Access (EqualAccess) Far-End Routing (FarEndRtg) Tandem Overflow (TandemOverflow) Near-End Routing (NearEndRtg)
92
Translations
Routing
Translation policies determine the call type and category of the call. Call types can either be system- or user-defined. System-defined call types are mandatory and are always added back, if deleted. User-defined call types are added by a system provider and can be referred to from policies with flexible call type support.
Call Categories
There are five call categories that are subsets of call types: Local Intra-LATA/National (Call within a LATA) International Inter-LATA (calls between two LATAs) Other Routing policies determine the contact(s) to return in the 302 SIP message.
92
Public Policy: CallTyping - Translations

NS_CLI/Policy/CallTyping> get Policy: CallTyping Instance: DefaultInst NS_CLI/Policy/CallTyping> get DefaultInst Policy: CallTyping Instance: DefaultInst CallTypes: Selection = {ALL} From = {CSV, SV, TRMT, CT, LPS, MS, PCS, TPS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, FGB, DA, EA, OA, POA} Enable = true
93
The Call Typing policy uses the Dial Plan of the country code set at installation. This policy then looks at the dial plan to determine the call type, if it matches the selection parameter it will continue with the call routing procedure. If not it returns a treatment.
Call Typing Policy Instance Setup

The get command with no parameter returns a list of policy instances. Using the get command with the instance name displays the policy parameters set for that instance. The set command with the instance name is used with the following fields: Selection Enable Selects the call types to trigger on. false true The instance is not active (off). The instance is active (on).
93
CallTyping: Dial Plans

NS_CLI/System/CallP/CountryCodes/DialPlan/Entry> get 1 NADP About to access 126 entries. Continue?
Please confirm (Yes, Y, No, N): y Retrieving data... Please wait... CC Dial Plan From To Match Min Max Call Type Prefix Action Description ================================================================================================================ = 1 NADP 0 0 exact 1 1 OA 0 Operator Assisted 1 NADP 00 00 exact 2 2 POA 0 PIC1 Operator Assisted 1 NADP 001 010 prefix 3 30 TRMT 0 TRMT=invld 1 NADP 011 011 prefix 4 30 IN 3 International 1 NADP 012 019 prefix 3 30 IN 2 Intl Operator Assisted (so IN, not OA) 1 NADP 02 0310 prefix 8 11 OAP 1 Operator Assisted Long-Distance 1 NADP 0311 0311 prefix 3 30 EM 0 REPLACE(311) Emergency police 1 NADP 0312 0910 prefix 8 11 OAP 1 Operator Assisted Long-Distance 1 NADP 0911 0911 prefix 4 30 EM 0 REPLACE(911) Emergency 1 NADP 0912 099 prefix 11 11 OAP 1 Operator Assisted Long-Distance 1 NADP 101 101 prefix 8 25 DP 7 CAC=[4-7],DP=NADPCAC Equal Access 1 NADP 102 109 prefix 3 30 TRMT 0 TRMT=invld 1 NADP 11 11 prefix 2 30 TRMT 0 TRMT=invld 1 NADP 1200 1200 prefix 8 11 TO 1 Service Access Code (???) 1 NADP 1201 1210 prefix 8 11 TO 1 Toll - Validated by Call Screening
NS_CLI/System/CallP/CountryCodes/DialPlan/Entry>> add 1 NADP 18009999999 18009999999 TF 11 11 TRMT Block Toll Free to 18009999999"
94
Dial Plans
The Network Server is delivered with default public dial plans and provides support for the public North American Dial Plan (all NA call types). System providers can build their own public dial plan or customize an existing one using the CLI. Dial plans are applied based on the country code of NE that originated the INVITE. When the INVITE terminating DN is a global E.164 number (starts with a +), this policy causes the call processing to jump from the current instance to another specified Call Typing instance which handles E.164 DNs with no prefix. The add command and the following fields are used to add an entry to the dial plan: Field DialPlanID *From/*To Match Description A dial plan name used to assemble a collection of from-to digit ranges. Digit sequence defining the beginning/end of a range of digits. CountryCode Specifies the country code for which a dial plan entry applies.
Defines the scope of from-to range. Prefix means that this entry applies if the called party number starts with digits matching from-to range. Suffix means that this entry applies if the called party number ends with digits matching from-to range. Exact means that this entry applies if the called party number is identical from-to number. CallType Prefix Call type to be set if the incoming digit sequence is included in the range defined by from-to, and has a length between Min and Max. The prefix to be set, if the incoming digit sequence is included in the range defined by the from-to, and has a length between Min and Max. The prefix indicates the number of prefix digits to ignore. Minimum/maximum length of a digit sequence for the rule to apply. Describes: Actions to be taken by the translation (run-time). Extra conditions on digit pattern matching. Short description of the expected behavior for the given digit range.
to
Min/Max Action Description
94
Public Policy: CallScreening -Translations

NS_CLI/Policy/CallScreening> get DefaultInst Policy: CallScreening Instance: DefaultInst Disallow 1+ local calls LocalPfx = false TollNoPfx = false Disallow 10 digit toll calls, Network Server will prefix 1 CallTypes: if set to true Selection = {TPS, PCS, OAP, TO, LO} From = {SV, CSV, TRMT, CT, MS, LPS, TPS, PCS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, EA, DA, POA, OA} Enable = true
95
The Call Screening Policy has been designed to work with the North American Numbering Plan. It validates that the call type found by the Call Typing policy is coherent with NPA/NXXs implied in the call. Knowing the NPANXX of the originator and at least the NXX of the terminator, the Call Screening policy searches the NNACL (NPA/NXX Active Code List) and LCA (Local Calling Area file) database to determine the category of the call (local, intra-LATA toll, and interLATA). It then checks if the call type found by the Call Typing Policy is valid based on the dialed digits.
Call Screening Policy Instance Setup

The get command with no parameter returns a list of policy instances. Using the get command with the instance name displays the policy parameters set for that instance. The set command with the instance name is used with the following fields: Selection Enable LocalPfx TollNoPfx Selects the call types to trigger on. false true true false true false The instance is not active (off). The instance is active (on). Allows 1+ local calls. Disallows 1+ local calls. Allows 10-digit toll calls (NS prefixes 1 to calls). Disallows 10-digit toll calls.
95
CallScreening NNACL and LCA files

NS_CLI/System/CallP/Translation> set NNACL dir /var/broadworks/translations/nnacl/ NS_CLI/System/CallP/Translation> set LCA dir /var/broadworks/translations/lca/ NS_CLI/System/CallP/Translation> set NNACL File 3Q01nnacl NS_CLI/System/CallP/Translation> set LCA File GBURG.lca NS_CLI/System/CallP/Translation> set active NS_CLI/System/CallP/Translation> get Sending the request NNACL(1) LCA(1) ------------Name: Name: Status: No File Loaded Status: No File Loaded Row(s): 0 Row(s): 0 Date: Date: NNACL(2) *Active* -------Name: 1Q03nnacl Status: File Loaded Row(s): 144262 Date: Sep 1, '04 at 10:48 AM
96
LCA(2) *Active* -----Name: GBURG.lca Status: File Loaded Row(s): 256 Date: Sep 1, '04 at 10:42 AM
Call Screening Policy

Determines the category of the call: Local Intra-LATA toll Inter-LATA toll Works in conjunction with the North American Numbering Plan (NANP). Uses the NPA-NXX Active Code List (NNACL) file provided by Telcordia for North America. Uses the Local Calling Area (LCA) file, a file customized by the system provider that specifies a list of originating rate centers and their related terminating rate centers/NPA-NXX codes for which the call will be categorized as local.
NNACL and LCA File for Public Routing

Create directories /nnacl and /lca under /var/broadworks/translations/. FTP Telcordia-provided NNACL file to /nnacl directory. FTP operator-provided LCA file to /lca directory. Set translations directory path and file name.
96
Public Policy: NumberPortability - Routing

NS_CLI/Policy/NumberPortability> get DefaultInst Policy: NumberPortability Instance: DefaultInst CallTypes: Selection = {ALL} From = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, CSV, PCS, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} Enable = true
NS_CLI/Policy/NumberPortability> ? 1) add : add a new NumberPortability instance 2) set : modify NumberPortability instance-related attributes 3) delete : delete an existing NumberPortability instance 4) portedOutNumbers : go to level portedOutNumbers 5) portedInNumbers : go to level portedInNumbers h (help), e (exit), q (quit), r (read), w (write), t (tree), c (config), cd (cd), a (alias), hi (history), p (pause), re (repeat)
97
Number Portability Policy

Supports users ported on to BroadWorks and users ported out of BroadWorks. The external number of the ported users remains the same and an internal routing number or route is used to port the users from one system to another. NS_CLI/Policy/NumberPortability/portedOutNumbers> get DefaultInst Policy: NumberPortability Instance: DefaultInst Table: PortedOutNumbers portedOutNumber 15145550000 15145550011 15145550011 internalNumber routingNe cost weight dmi +1555559999 1555559988 1555559988 ngw1 ngw2 1 1 - -1 99 -1 99 -1 ==================================================================
NS_CLI/Policy/NumberPortability/portedInNumbers> get DefaultInst Policy: NumberPortability Instance: DefaultInst Table: PortedInNumbers PortedInNumber 15145552222 PublicNumber 1555553333 ====================================
97
Public Policy: SubLocation - Routing

NS_CLI/Policy/SubLocation> get DefaultInst Policy: SubLocation Instance: DefaultInst CallTypes: Selection = {ALL} From = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, PCS, CSV, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} Enable = true
If the call type of the call matches the selection call type and the terminating number is known by the Network Server it returns its hosting NE as the contact.
98
Subscriber Location Policy

Applies to on-net routing. Identifies the dialed digits as a subscriber on the Network Server and allows incoming calls to terminate to end user in a given IP network. Used to allow on-net calling between users in different groups (and/or different Application Servers) by returning the terminators HostingNE in the contact list. Used for calls from the PSTN (RoutingNE) to terminate a call to a known user on the IP network. Without SubLocation, public calls between Network Server users always route to PSTN through off-net routing.
98
Public Policy: SvcCtrRtg - Routing

Call Type Matches Selection Call Type Service Center RouteList Match Originator E.164 DN and Redirection SIP RoutingNE, MGCP trunk group on RoutingNE, or public DN
NS_CLI/Policy/SvcCtrRtg> add Inst_1 true CallTypes EM DA NS_CLI/Policy/SvcCtrRtg> get Inst_1 Policy: SvcCtrRtg Instance: Inst_1 CallTypes: Selection = {EM, DA} From = {CSV, SV, TRMT, CT, LPS, MS, PCS, TPS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, FGB, DA, EA, OA, POA} Enable = true
99
Service Center Routing Policy

The Service Center Routing Policy (SvcCtrRtg) is an origination-based routing policy. It allows a Network Server administrator to route incoming calls to specific destinations based on the call originator and on the Network Server identified call type. This policy uses service routing entries to map incoming call types, call attributes, and originator defined by a range of valid digits to a destination. It provides support for three types of routing results: Fully-specified DN destination A destination network gateway A destination MGCP gateway with and a specific trunk group name Users can access unique SCRLs through application of different SvcCtrRtg policies and instances to public policies. Supports multiple routes with different results cost and weighting (multiple contacts returned). Supports full digit manipulation of dialed digits.
99
Public Policy: SvcCtrRtg Route List (SCRL)

NS_CLI/Policy/SvcCtrRtg/SCRL> add Inst_1 EM 1240364 1240364 1 99 gateway ngw1 NS_CLI/Policy/SvcCtrRtg/SCRL> add Inst_1 EM 1301977 1301977 1 99 gateway ngw1 dmi 21 NS_CLI/Policy/SvcCtrRtg/SCRL> add Inst_1 DA 1 1 1 99 address 18005551234 NS_CLI/Policy/SvcCtrRtg/SCRL> get Inst_1 Policy: SvcCtrRtg Instance: Inst_1 Table: SCRL id callType from to callSelector address gateway trunkgroupID cost weight dmi ===================================================================== 1 {EM} 1240364 1240364 {All} ngw1 1 99 -1 2 {EM} 1301977 1301977 {All} ngw1 1 99 21 3 {DA} 1 1 {All} 18005551234 1 99 -1
100
Service Center Routing List

CallType From/To Call type to which this entry applies. Digit sequence defining the beginning/end of a range of digits. All: Route applies to any call. Redirect: Route only applies to calls received with a Diversion indicator. NoRedirect: Route only applies to calls received without a Diversion indicator. Cost Weight DMI Address Gateway TrunkGrpID Route selection cost. Route selection weight. Digit manipulation index to the list of service provider-defined digit manipulation algorithm. (DN) Route to a specific address. Route to a specific routing NE. Destination gateway. Route to a trunk group. The trunk groups unique ID consists of: Protocol: The protocol of the trunk group (MGCP). TrunkGroup: A string that represents the trunk group name that is used when returned in a contact. Channel: The channel that can be used on the specified trunk group. Gateway: The MGCP device that owns the trunk group. GatewayControllerGroupID: (Optional) The group ID for gateway controllers (hosting NEs). A list of controllers, for example Application Servers used to interface with the MGCP device.
CallSelector A call attribute used to discriminate if the route applies or not:
100
Digit Manipulation Index (DMI)

NS_CLI/System/CallP/DMI> add 21 pre(99) "prepend 99 to 911 call" NS_CLI/System/CallP/DMI> get Index Digit Manipulation Description ====================================================== 21 PRE(99) prepend 99 to 911 call
101
Digit Manipulation Index

The DMI add command has the following fields: Index dmStr desc The index number. The digit manipulation string or algorithm The description of the digit manipulation string.
The DMI can be used in other policy instances.
101
Public Policy: RCBasedRtg - Routing

Call Type Matches Selection Call Type Rate Center RouteList Match Originating Rate Center and Redirection SIP RoutingNE or public DN
NS_CLI/Policy/RCBasedRtg> add DefaultInst true CallTypes EM NS_CLI/Policy/RCBasedRtg> get Policy: RCBasedRtg Instance: DefaultInst
NS_CLI/Policy/RCBasedRtg> get DefaultInst Policy: RCBasedRtg Instance: DefaultInst CallTypes: Selection = {ALL} From = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, CSV, PCS, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} Enable = true
102
Rate Center Routing Policy

The Rate Center Routing Policy (RCBasedRtg) is an origination-based routing policy. This policy allows a system provider to select a destination based on the call originators Rate Center and call type. The rate center identification can be based on one of the following: Telcordia NNACL file (also referred as LATA-based rate centers) ZONEs assigned directly against NDCs
102
Public Policy: RCBasedRtg - LataRoute

NS_CLI/Policy/RCBasedRtg/LataRouteList> add DefaultInst EM 850 MONTREAL 1 99 address 2002002001 NS_CLI/Policy/RCBasedRtg/LataRouteList> add DefaultInst EM 850 MONTREAL 1 99 routingNe NGW1 dmi 123 NS_CLI/Policy/RCBasedRtg/LataRouteList> get DefaultInst Policy: RCBasedRtg Instance: DefaultInst Table: LataRoutingList id callType lata rateCenter address routingNE cost weight dmi ====================================================================== 1 EM 850 MONTREAL 2002002001 - 1 99 NIL_DMI 2 EM 850 MONTREAL NGW1 1 99 123
103
Rate Center LATA Route List

This command is used to add a new rate center routing rule. Entries can either be used to set a new destination address or a routingNe but not both at the same time. A DMI entry can optionally be specified for both address and RoutingNe results. add <instance>, String {1 to 12 characters} <callType>, Choice = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, CSV, PCS, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} <lata>, Integer {100 to 9999} <rateCenter>, String {3 to 25 characters} [<attribute>, Multiple Choice = {cost, weight, address, routingNe, dmi}] <cost>, Integer {1 to 9} <weight>, Integer {0 to 99} <address>, String {1 to 15 characters} <routingNe>, String {1 to 40 characters} <dmi>, Integer {-1 to 32767}
103
Public Policy: RCBasedRtg - ZoneRoute

NS_CLI/Policy/RCBasedRtg/ZoneRouteList> add DefaultInst EM 1 Zone1 cityXYZ 1 99 address 8678899089 NS_CLI/Policy/RCBasedRtg/ZoneRouteList> add DefaultInst EM 1 850 Montreal 1 99 routingNe NGW1 dmi 123 NS_CLI/Policy/RCBasedRtg/ZoneRouteList> get DefaultInst Policy: RCBasedRtg Instance: DefaultInst Table: ZoneRoutingList id callType cc zone rateCenter address routingNE cost weight dmi ====================================================================== 1 EM 1 1 MONTREAL 2002002001 1 99 NIL_DMI 2 EM 1 1 MONTREAL NGW1 1 99 123
104
Rate Center Zone Route List

This command is used to add a new rate center routing rule. Entries can either be used to set a new destination address or a routingNe but not both at the same time. A DMI entry can optionally be specified for both address and RoutingNe results. add <instance>, String {1 to 12 characters} <callType>, Choice = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, CSV, PCS, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} <cc>, String {1 to 3 characters} <zone>, String {1 to 32 characters} <rateCenter>, String {3 to 25 characters} [<attribute>, Multiple Choice = {cost, weight, address, routingNe, dmi}] <cost>, Integer {1 to 9} <weight>, Integer {0 to 99} <address>, String {1 to 15 characters} <routingNe>, String {1 to 40 characters} <dmi>, Integer {-1 to 32767}
104
Public Policy: EqualAccess - Routing
Call type, Originator E.164 DN
Equal Access Call Category
DN@NGW with CIC
NS_CLI/Policy/EqualAccess> get DefaultInst Policy: EqualAccess Instance: DefaultInst addCICasCAC = false CallTypes: Selection = {TO, CT, OA, CSV, OAP, IN, POA} From = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, PCS, CSV, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} CicAlways = false Enable = true BlockUnknownCac = false
105
Equal Access Policy

The Equal Access policy allows for selection of pre-defined carriers for off-net routing. Origination-based routing policy triggered on call type toll or international calls. Uses preferred inter-exchange carriers (PICs). PICs can be assigned to an enterprise or group. Each enterprise/group has three PICs provisioned: Intra-LATA Inter-LATA International System default PICs are configurable.
Equal Access Functionality

Can associate a carrier with a list of RoutingNEs. When a list is not provided, the preferred inter-exchange carrier or carrier access code is prefixed to the outgoing call and routed to the POP device closest to the call originator (selected from the POP devices configured on the Network Server). Carrier Identification Code (CIC) is passed back to the requesting Network Element (NE) as part of the 302 Temporarily Moved Contact list. Receiving RoutingNE (SS7 or PRI-based) maps CIC to Transit Network Selector (TNS) parameter in outgoing IAM or SETUP message.
105
Equal Access Carriers

AS_CLI/System/Carrier> get Carrier Country Code CIC IntraLata InterLata International ======================================================================= Bell Deutsche Telekom 2 entries found. 1 49 1234 334455 true false false true true false
106
Add an Equal Access Carrier

The add command and the following fields are used to add an Equal Access carrier: carrier CAC intraLata interLata intl The name of the carrier. The carrier access code. no yes no yes no yes This carrier does not support intra-LATA toll call routing. This carrier does support intra-LATA toll call routing. This carrier does not support inter-LATA toll call routing. This carrier does support inter-LATA toll call routing. This carrier does not support international toll call routing. This carrier does support international toll call routing.
106
Public Policy: Far-End Near-End Routing

Call Type Destination E.164 DN Far-End Routing Routelist Match DN at NGW closest to destination
NS_CLI/Policy/FarEndRtg> get DefaultInst Policy: FarEndRtg Instance: DefaultInst Overflow = false LocationRouting = false CallTypes: Selection = {TO, IN} From = {CSV, SV, TRMT, CT, LPS, MS, PCS, TPS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, FGB, DA, EA, OA, POA} Enable = true
Call Type Origination E.164 DN
Near-End Routing Routelist Match
DN at NGW closest to origination
NS_CLI/Policy/NearEndRtg> get DefaultInst Policy: NearEndRtg Instance: DefaultInst LocationRouting = false CallTypes: Selection = {ALL} From = {CSV, SV, TRMT, CT, LPS, MS, PCS, TPS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, FGB, DA, EA, OA, POA} Enable = true
107
Far-End Routing Policy

This policy is used for off-network routing. Selects a routing path using rules ensuring the least cost. Identifies the POP device closest to the call destination, for example, between an IP network and the PSTN. The system provider is the default carrier for the call.
Near-End Routing Policy

This policy is used for off-network routing. Terminates a call to the network element (point-of-presence [POP] device, such as a network gateway or a softswitch) closest to the call originator. Uses the network route selector framework to route a call. Typically the default Network Server policy. The add command and following fields are used to add an instance: instance Enable CallTypes LocationRouting The name of the instance for this policy. false true false true The instance is not active (off). The instance is active (on). Indicates only routing entries are used and that locationbased search is not used. Indicates that the policy tries to find contacts from routing entries and location-based search.
The type of call this policy instance can process.
107
Near-End and Far-End Route Lists

NE From To Cost Weight Tags Far-end Category Far-end DMI Near-end DMI ================================================================================ ngw1 10 1240363 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw1 1240364 1240364 1 99 {} OTHER -1 (NO_DMI) -1 (NO_DMI) ngw1 1240365 1301976 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw1 1301978 19 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw2 2 9 1 99 {} INTERNAT -1 (NO_DMI) -1 (NO_DMI) ngw2 1301977 1301977 1 99 {} OTHER -1 (NO_DMI) -1 (NO_DMI)
Network elements must first be provisioned on the Network Server before the route list can be built.
108
Fixed Route Assignment

Selection based on ranges of originating/terminating E.164 DNs. Cost to determine route ordering. Weight to distribute traffic load. Near-End and Far-End Routing share common route list.
Dynamic Route Selection by Geographic Location of Routing Element

Routing element assigned location (NPA/NXX). Uses vertical and horizontal (V&H) to find closest routing element. Used as a backup when no or only one route is identified. Also used for geographic Media Server Selection.
Telcordia Vertical and Horizontal (V&H)

North America overlaid with vertical and horizontal coordinates grid. NNACL file provided V&H location for every NPA/NXX. Example: 202822 EOCN WASHDCMTDS15E 9211236 WASHGTN ZONE 1 05622 01583 DCY Originator/Terminating NPA/NXX and all routing elements plotted on V&H grid. Routing elements closest to originator/terminator makes up contact list.
108
Other Network Server Policies

URL policies
Network URL Dialing (UrlDialing) Public MSN SIMPLE (SIMPLE) Enterprise MSN SIMPLE (EntSIMPLE)
Media Server policy

Media Server Selection (MediaSrvSel)
109
109
URL Dialing Policy

URL alias URL Dialing URL@host address
NS_CLI/Policy/UrlDialing> get DefaultInst Policy: UrlDialing Instance: DefaultInst CallTypes: Selection = {ALL} From = {MS, TO, LPS, LO, NIL, CT, DP, TF, OA, TPS, PCS, CSV, ZD, ALL, EA, OAP, TRMT, DA, EM, SV, FGB, IN, POA} Enable = true
110
Network URL Dialing

URL calls are distinguished from DN-based calls. Performs subscriber location for URL-dialed calls, allowing calls to terminate to any end user in a given IP network. This is a SIP-based policy.
Call Routing
Upon URL dialing call origination, the Application Server sends the call with an unknown alias to the Network Server. The Network Server then looks up in its table of URLs to identify the subscriber location. If the subscriber is found, a 302 (moved temporarily) is returned to the originating Application Server with the new destination attached using the maddr parameter. If the subscriber is not found, a 302 is still sent but with the original targeted domain as the new destination. The add command and the following fields are used to add an instance: instance Enable CallTypes The name of the instance for this policy. false true The instance is not active (off). The instance is active (on).
The type of call this policy instance can process.
110
SIMPLE Policy (Public)

This policy routes Windows Messenger SIMPLE (Session Initiation Messaging and Presence Leveraging Enhancements) messages between end users Triggers on SIP Message and Subscribe messages Policy uses the provisioned end-user URLs to route SIP Subscribe and Message messages If the Request URI indicates that the message is for a URL provisioned in the Network Server, the policy redirects this message to the Hosting NE on which the URL is hosted If the URL is not known in the Network Server, the policy redirects the message to the SIMPLE proxy server capable of handling traffic for the domain specified in the URL
111
111

PROTOCOL: MSSelection TRANSACTIONID: 2410@12.39.208.194 TYPE: REQUEST SOURCE: 12.39.208.194 COMMAND: SelectMS DN: +12292442099 IPADDRESS: NGW1
Incoming
Network Server
Outgoing
PROTOCOL:MSSelection TRANSACTIONID:2410@12.39.208.194 TYPE:RESPONSE COMMAND:SelectMS SELECTEDMS:12.39.208.195:5679 SELECTEDMS:66.201.233.59:5679 112

Uses proprietary the MSS protocol. The Network Server receives an incoming MSS Request from an Application Server. The Network Server processes an MSS Request by looking at the DN of the requestor or the IP address of the NE that requires a Media Server. The Network Server returns an MSS Response message to the Application Server with list of Media Servers to try. If the first Media Server does not respond, the Application Server tries the next Media Server in the returned list.
112

Origination DN/ IP address Media Server Selection Media Server list
NS_CLI/Policy/MediaSrvSel> get DefaultInst Policy: MediaSrvSel Instance: DefaultInst CallTypes: Selection = {ALL} From = {CSV, SV, TRMT, CT, LPS, MS, PCS, TPS, DP, OAP, TO, LO, IN, EM, NIL, ALL, TF, FGB, DA, EA, OA, POA} Enable = true
113
Media Server Selection Routing Policy

Locates the Media Server which is physically closest to a RoutingNE or to an end-user DN on an IP network. This policy allows Media Servers to be decoupled from Application Servers so they do not have to be collocated; an operating company can locate Media Servers close to network gateways.
113
Public Profiles
NS_CLI/Policy/Profile> add Hosting NS_CLI/Policy/Profile> add Hosting CallTyping DefaultInst NS_CLI/Policy/Profile> add Hosting CallScreening DefaultInst NS_CLI/Policy/Profile> add Hosting SubLocation DefaultInst NS_CLI/Policy/Profile> add Hosting SvcCtrRtg Inst_1 NS_CLI/Policy/Profile> add Hosting MediaSrvSel DefaultInst NS_CLI/Policy/Profile> add Hosting NearEndRtg DefaultInst NS_CLI/Policy/Profile> add Hosting EqualAccess DefaultInst NS_CLI/Policy/Profile> get profile Hosting Profile: Hosting Policy Instance ========================================== SvcCtrRtg Inst_1 MediaSrvSel DefaultInst CallTyping DefaultInst CallScreening DefaultInst SubLocation DefaultInst NearEndRtg DefaultInst EqualAccess DefaultInst
114
Public Profiles
Profiles can be assigned to network elements, enterprises, and groups. Policy instances are grouped together in a profile to be assigned. The add command and the following fields are used to add an instance: profile policy instance The name of the profile. The name of the new policy. The name of the profile policy instance.
114
Lab 1 Step 1: Public Policy Profile Configuration
115
Public Policy and Profile Creation

Public call routing is driven by public policies. Public policies are grouped into profiles and can be assigned to hosting network elements, routing network elements, enterprises, or groups. Each team will create two public profiles (one associated with the enterprise and the associated with the RoutingNE). For the enterprise profile: The CallTyping policy is used to set call types. CallScreening policy used to validate call types. MediaSrvSel policy used by the Network Server for Media Server selection. A combination of the FarEndRtg, NearEndRtg, and SvcCtrRtg policies, which are assigned to support the following routing.
All calls from 240364xxxx users use a static route list of ngw1(NearEndRtg) with the exception of Teams 1,2,3 and 4 who set toll calls for all users to use ngw1 (FarEndRtg). Teams 5, 6, 7,8 and 9 set International calls for all users to use ngw1 (FarEndRtg). For all teams, 911 calls from 240364xxxx use a SCRL for each teams DUMMY<Team#> routingNE after prepending 99 to the dialed digits (SvcCtrRtg). For all teams, 411 calls from all users use ngw1 after 411 has been replaced by 18005551234 routing number to the preferred OA carrier (SvcCtrRtg).
For the RoutingNE profile: The CallTyping policy is used to set the call type. The SubLocation policy is used to allow incoming PSTN calls to terminate to hosted users. The MediaSrvSel policy is used by the Network Server for Media Server selection.
115
1. Log in to the Network Server as bwadmin. 2. Log in to the BroadWorks command line interface level as admin. 3. Teams 1, 2, 3, and 4, create the following team-specific policy instances under the corresponding NS_CLI/Policy level. 4. Teams 5, 6, 7, 8, and 9 create the following team-specific policy instances under the corresponding NS_CLI/Policy level.
Policy Name SvcCtrRtg FarEndRtg Instance Name INST_<Team#> INST_<Team#> Applicable Call Types EM, DA TO
5. Under NS_CLI/Policy/FarEndRtg level, ensure that location routing is disabled for your FarEndRtg policy instance. 6. Under NS_CLI/Policy/Profile level, each team creates a public profile called HOST_<Team#> and assigns the following policies and policy instances. Under NS_CLI/Policy/Profile level, each team creates a Routing NE public profile called ROUTE_<Team#> and assigns the following policies and policy instances.
Policy Name SvcCtrRtg FarEndRtg Instance Name INST_<Team#> INST_<Team#> Applicable Call Types EM, DA IN
7. Under NS_CLI/Policy/Profile level, each team creates a Routing NE public profile called ROUTE_<Team#> and assigns the following policies and policy instances.
Policies CallTyping CallScreening MediaSrvSel NearEndRtg SvcCtrRtg FarEndRtg
Policy Instance DefaultInst DefaultInst DefaultInst DefaultInst INST_<Team#> INST_<Team#>
116
Build Network Elements

Network Server must know the network element (NE) to route calls to and from the NE
117
117
Network Server HostingNE Configuration

NS_CLI/System/Device/HostingNE> add bwas HOST_9 Def_Ent NIL_ENTERPRISE DFLT_SITE DFLT_SITE 1 false OnLine PhoneContext broadworks CLI/Network/Device/HostingNE> get Hosting Network Element bwas Type = broadworks Profile = HOST_9 Default Enterprise = Def_Ent Default Routing Enterprise = NIL_ENTERPRISE Default Site = DFLT_SITE Default Routing Site= DFLT_SITE Poll = false OpState = enabled State = OnLine Signaling Attributes= PhoneContext Country Code = 1
118
The add command and the following fields are used to add a hosting network element: hostNe The network element name. profile The profile to be used for this hosting NE. dfltEnterprise Used to temporarily map a default enterprise name on the Network Server when user data is uploaded from the Application Server. dfltRoutingEnterprise Used to temporarily map a default routing enterprise name on the Network Server when user data is uploaded from the Application Server. dfltSite Used to temporarily map a default site on the Network Server when user data is uploaded from the Application Server. dfltRoutingSite Used to temporarily map a default routing site on the Network Server when user data is uploaded from the Application Server. countryCode The country code. signaling One of the following: NONE: No signaling defined. E164Compliant: The NE supports E.164. PhoneContext: The NE supports phone-context. Forking: The NE supports forking. CallTypeInfoRequired: The NE requires the call type info to be sent back as part of the 302 contacts returned by the NS. sourceId: The NE supports Originating Trunk Groups. poll True or false: Allows the Network Server to poll another device. state Offline or online: Sets the state of the device. type BroadWorks or other: Indicates the type of device.
118

NS_CLI/System/Device/HostingNE/Address> add PRIV_18 0 192.168.2.133 signaling 1 99 5060 NS_CLI/System/Device/HostingNE/Address> get About to access 12 entries. Continue? Please confirm (Yes, Y, No, N): y Retrieving data... Please wait... HostingNE NodeID Address type cost weight port ====================================================================== PRIV_18 0 192.168.2.133 Signaling 1 50 5060 bwas 0 192.168.5.100 Signaling 1 1 5060 bwas 0 as1 Alias bwas 0 as1.lab.broadsoft.com Access 1 1 5060 bwas 1 192.168.5.107 Signaling 1 1 5060 bwas 1 as2 Alias bwas 1 as2.lab.broadsoft.com Access 1 1 5060
Ensure that all hosting network elements are provisioned for the network
119
Once the network element is provisioned on the network it must have an address provisioned for it. The add command and the following fields are used to add a network element: hostNE nodeID address type The name of the network element. Cluster member ID. Default is 0. The corresponding IP address, or host name, or domain name for the network element. One of the following: DualRouting: The address is a SIP signaling address. It can be added to the contact list from a returned 302 following a SIP request. Access: The address is a public address used for Location API. Signaling: This address is public and also a SIP signaling address at the same time. It will be returned for SIP and location API requests. Alias: Alias of hosting NE used for the Sync API. cost weight The associated cost code for the network element Given the same cost, network elements will be randomly listed according to weight with a higher weight appearing more often at the top. The port number.
port
119

NS_CLI/System/Device/HostingNE/Node> add asqtsc 1 default false NS_CLI/System/Device/HostingNE/Node> get About to access 5 entries. Continue? HostingNe NodeID default description ========================================================== PRIV_1 0 true Node 0 (automatically added) PRIV_3 0 true Node 0 (automatically added) PRIV_2 0 true Node 0 (automatically added) asqtsc 0 true Node 0 (automatically added) asqtsc 1 false
120
120
Network Server RoutingNE Configuration

NS_CLI/System/Device/RoutingNE> add RoutingNE 1240364 1 99 routing false OnLine NS_CLI/System/Device/RoutingNE> get Retrieving data... Please wait... Network Element NGW1 Location = 1240364 Static Cost = 1 Static Weight = 50 Poll = false OpState = enabled State = OnLine Profile = routing Signaling Attributes= Network Element RoutingNE Location = 1240364 Static Cost = 1 Static Weight = 99 Poll = false OpState = enabled State = OnLine Profile = routing Signaling Attributes=
NS_CLI/System/Device/RoutingNE/Address> add RoutingNE 192.168.5.133 1 50 5060
121
The add command and the following fields are used go add a routing network element: ne location cost weight profile poll state signaling The network element name. The physical location of the network element in the network. The associated cost code for the network element. Given the same cost, network elements will be randomly listed according to the weight with a higher weight appearing more often at the top. The profile to be used for this routing network element having precedence over the system profile. True: Allows the Network Server to poll another device. False: Polling is turned off. Offline: When set to offline, no calls are routed to this NE Online: When set to online, calls will be routed to this NE. One of the following: NONE: No signaling defined. E164Compliant: The target device supports E.164 encoded PhoneContext: The target device supports phone-context. Forking: Target device supports forking. InboundOnly: The device is only used for sending calls in the in bound directory. UseOrigBasedScreening: Use the call category from call screening (Caller to Called number) instead of the call category from the RoutingNE to the called number. information.
121
Network Server ResourceNE Configuration

NS_CLI/System/Device/ResourceNE> add ms1 ms all 1240364 1 99 false Online default 1 99 NS_CLI/System/Device/ResourceNE> add ms2 ms all 1301977 1 99 false Online NS_CLI/System/Device/ResourceNE> get Resource Type Location NE MS1 ms 1240364 MS2 ms 1240364 Stat Cost 2 2 Stat Weight 50 50 Poll OpState State false enabled OnLine false enabled OnLine Dflt Dflt Services Cost Weight true 1 99 all false all Dflt
NS_CLI/System/Device/ResourceNE/Address> add ms1 192.168.5.180 1 99 5060 NS_CLI/System/Device/ResourceNE/Address> add ms2 192.168.5.185 1 99 5060
122
The add command and the following fields are used to add a new resource network element: neName neType location The resource network element name. ms: The device is a Media Server. SIMPLE: The device is a SIMPLE-based messaging server. The physical location of the resource network element in the network. processing staticCost The static cost for the resource network element used in the postfor a V&H lookup. staticWeight The static weight for the resource network element used in the post-processing for a V&H lookup. poll state default True or false: Allows the Network Server to poll another device. OffLine: The resource network element is off line and not available. OnLine: The resource network element is on line and is available. defaultCost: The default cost used in the post-processing of the default resource network element list. defaultWeight: The default weight used in the post-processing of the default resource network element list. To add network element address attributes, enter: add neName, address, cost, weight, port. neName address cost weight port The name of the resource network element. The corresponding IP address, or host name, or domain for the resource NE. The associated cost code for the resource network element. The weight assigned to the The resource network element port number.
122
Network Server ResourceNE Configuration

NS_CLI/Policy/MediaSrvSel/RouteList> add DefaultInst ms1 1240364 1240364 all 1 50 NS_CLI/Policy/MediaSrvSel/RouteList> add DefaultInst ms2 1240364 1240364 all 2 50 NS_CLI/Policy/MediaSrvSel/RouteList> add DefaultInst ms2 1301977 1301977 all 1 50 NS_CLI/Policy/MediaSrvSel/RouteList> add DefaultInst ms1 1301977 1301977 all 2 50 NS_CLI/Policy/MediaSrvSel/RouteList> get DefaultInst Policy: MediaSrvSel Instance: DefaultInst Table: RouteList mss from to service cost weight ============================================== MS1 1240364 1240364 {all} 1 50 MS2 1240364 1240364 {all} 2 50 NS_CLI/System/Device/ResourceNE/MSSelect> add ms1 ngw1 all 1 50 NS_CLI/System/Device/ResourceNE/MSSelect> add ms2 ngw1 all 2 50
123
The add command and the following fields are used to add a new routing list: instance ms from/to service The name of the instance for this policy. The name of the Media Server to which this instance applies. Digit sequence defining the beginning/end of a range of digits. One of the following: ivr: This is interactive voice response. conf: This is a conference repeater. fax: This is a fax. liveAudio: This is a live audio source. all: The routing entry applies to all possible media services. cost weight The associated cost code for the route. The relative value (user defined) to randomize distribution of traffic along this route.
The add command and the following fields are used to add a new Media Server network element: ms service cost weight The Media Server name. See service description listed above. The associated cost code for the Media Server. Given the same cost, Media Servers are randomly listed according to the weight with a higher weight appearing more often at the top. routingNE The name of the routing network element.
123
Public Routing Configuration

NS_CLI/System/Device/RoutingNE/Routing> add ngw1 10 1240363 1 99 {} NATIONAL -1 -1 NS_CLI/System/Device/RoutingNE/Routing> add ngw1 1240364 1240364 1 99 {} OTHER -1 -1 NS_CLI/System/Device/RoutingNE/Routing> add ngw1 1240365 1301976 1 99 {} NATIONAL -1 -1 NS_CLI/System/Device/RoutingNE/Routing> add ngw2 1301977 1301977 1 99 {} OTHER -1 1 NS_CLI/System/Device/RoutingNE/Routing> add ngw1 1301978 19 1 99 {} NATIONAL -1 1 NS_CLI/System/Device/RoutingNE/Routing> add ngw2 2 9 1 99 {} INTERNAT -1 -1
NS_CLI/System/Device/RoutingNE/Routing> get Retrieving data... Please wait... NE From To Cost Weight Tags Far-end Category Far-end DMI Near-end DMI =============================================================================== ngw1 10 1240363 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw1 1240364 1240364 1 99 {} OTHER -1 (NO_DMI) -1 (NO_DMI) ngw1 1240365 1301976 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw1 1301978 19 1 99 {} NATIONAL -1 (NO_DMI) -1 (NO_DMI) ngw2 2 9 1 99 {} INTERNAT -1 (NO_DMI) -1 (NO_DMI) ngw2 1301977 1301977 1 99 {} OTHER -1 (NO_DMI) -1 (NO_DMI)
124
The add command and the following fields are used to add a network element route: neString from to cost weight tag The network element name. The starting phone number of the range. The ending phone number of the range. The associated cost code for the phone number range. The relative value to randomize distribution of traffic. For future use. LOCAL NATIONAL INTERLAT INTRALAT INTERNAT PRIVATE OTHER farendDMI nearendDMI This allows a route to be flagged as local. This allows a route to be flagged as national. This allows a route to be flagged as inter-LATA. This allows a route to be flagged as intra-LATA. This allows a route to be flagged as international. This allows a route to be flagged as private. This allows a route to be flagged as other.
farendCategory One of the following:
EMERGENCY This allows a route to be flagged as emergency. The digit manipulation index allowing digit manipulation on the routing entry. The digit manipulation index allowing digit manipulation on the routing entry.
124
End-User Management
NS_CLI/SubscriberMgmt/Enterprise/UserGroup> add Grp1 PBX1 enterprise Ent1 User Group Grp1 Hosting NE PBX1 Description Enterprise Profile Intra-LATA PIC Inter-LATA PIC International PIC InDM
= = = = = = =
Ent1 NIL_PROFILE NILCAC NILCAC NILCAC
Can set group EA carriers to be used for various call categories
Can set incoming dialed digit manipulation that will be applied to the entire group
NS_CLI/SubscriberMgmt/Enterprise/DnUrl> add Grp1 PBX1 dn {1301977700013019777010}
125
The add command and the following fields are used to add a group. groupId hostNE attribute The ID of the user group. The network element hosting the user group. enterprise profile lcaid intraPic interPic intlPic InDM sourceId The enterprise to which the user group belongs. The routing profile to be used by the user group. The LCA name. The carrier to be used for intra-LATA calls. The carrier to be used for inter-LATA calls. The carrier to be used for international calls. The digit manipulation algorithm for incoming calls to the user group. The originating trunk group (OTG). This is another means of identifying an enterprise, user group or site in the system. The same sourceID can be used to identify many enterprises, groups, or sites. groupName The name of the user group.
The add command and the following fields are used to add directory numbers: group hostNE address The name of the user group. The network element hosting the group. dn ext url The site where these numbers are used and DNs belonging to this user group site. The site where these extensions are used and the extensions belonging to this user group site. The site where these URLs are used and the URLs belonging to this user group site.
125
Lab 2 Step 2: Network Elements Configuration
126
Step 2: Create Network Elements

The Network Server has a network topology view of the entire BroadWorks network. There are three categories of NEs: Resource NE, Routing NE, and Hosting NE. Media Servers MS0 has been added and configured as the default Media Server by your instructor. Each team will add a dummy Media Server that will be returned as part of the Media Server Selection return contact list. 1. Under NS_CLI/System/Device/ResourceNE, each team creates a Media Server resource with the following parameters:
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9 MS Name DUMMYMS1 DUMMYMS2 DUMMYMS3 DUMMYMS4 DUMMYMS5 DUMMYMS6 DUMMYMS7 DUMMYMS8 DUMMYMS9 IP Address 192.168.7.103 192.168.7.104 192.168.7.105 192.168.7.106 192.168.7.107 192.168.7.108 192.168.7.109 192.168.7.110 192.168.7.111 Location 1240364 1240364 1240364 1240364 1240364 1240364 1240364 1240364 1240364 Polling false false false false false false false false false Static Cost 2 2 3 3 4 4 5 6 7 Weight 50 50 99 1 50 50 50 50 50
126
Routing Network Elements NGW1 has been added by the instructor and has PSTN connectivity. Each team will add a dummy Routing NE that will be returned in the contact list depending on the dial plan. For all teams, 911 calls from 240364xxxx use a SCRL for each teams DUMMY<Team#> routingNE after prepending 99 to the dialed digits (SvcCtrRtg). 1. Under NS_CLI/System/Device/RoutingNE, each team creates a network gateway resource with the following parameters:
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9
NGW Name DUMMY1 DUMMY2 DUMMY3 DUMMY4 DUMMY5 DUMMY6 DUMMY7 DUMMY8 DUMMY9
IP Address 192.168.7.121 192.168.7.122 192.168.7.123 192.168.7.124 192.168.7.125 192.168.7.126 192.168.7.127 192.168.7.128 192.168.7.129
Location 1240364 1240364 1240364 1240364 1240364 1240364 1240364 1240364 1240364
Profile ROUTE_1 ROUTE_2 ROUTE_3 ROUTE_4 ROUTE_5 ROUTE_6 ROUTE_7 ROUTE_8 ROUTE_9
Static Cost 1 1 1 1 1 1 1 1 1
Weight 50 50 50 50 50 50 50 50 50
Polling false false false false false false false false false
Status Online Online Online Online Online Online Online Online Online
Private Network Gateways Private network gateways are used by private policies, such as FarEndHopOff, to route calls to a customer-owned CPE gateway. Private network gateways are defined as Hosting NEs on the Network Server. FarEndHopOff to support routing calls to the 514 NPA through private gateway (PRIV_1 to PRIV_9) 1. Under NS_CLI/System/Device/HostingNE, each team creates a private network gateway resource with the parameters shown in the following table. Each gateway overlays on the same IP address (using the same IP address as NGW1).
Team
NGW Name PRIV_1 PRIV_2 PRIV_3 PRIV_4 PRIV_5 PRIV_6 PRIV_7 PRIV_8 PRIV_9
IP Address
Profile
Polling
Status
Type
CC
Default Enterprise/ Routing NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE NIL_ENTERPRISE
Default Site/ Routing DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE DFLT_ SITE
Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9
192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133 192.168.2.133
HOST_1 HOST_2 HOST_3 HOST_4 HOST_5 HOST_6 HOST_7 HOST_8 HOST_9
false false false false false false false false false
Online Online Online Online Online Online Online Online Online
other other other other other other other other other
1 1 1 1 1 1 1 1 1
127
Create Enterprise
Enterprises must be created to associate subscribers and groups to routing profiles
128
128
Enterprise Private Policy Configuration

NS_CLI/SubscriberMgmt/Enterprise> add Ent1 profile Hosting NS_CLI/SubscriberMgmt/Enterprise> get Enterprise Ent1 Call Logging = Disabled Description = Intra-LATA PIC = NILCAC Can set enterprise EA carriers to be used for various call categories Inter-LATA PIC = NILCAC International PIC = NILCAC Routing profile = Hosting Private policies = {}
129
The add command and the following fields are used to add an enterprise: enterprise attribute The name of the new enterprise. intraPic interPic intlPic profile lcaid desc callLog sourceId The carrier to be used for intra-LATA calls. The carrier to be used for inter-LATA calls. The carrier to be used for international calls. The routing profile for this enterprise. The LCA name. Descriptive information about the enterprise. disabled enabled Call logging is turned off. Call logging feature is on.
The originating trunk group (OTG).
129
Private Policy: ExtDialing

ExtDialing: Required for the Application Server redundancy solution
NS_CLI/SubscriberMgmt/Enterprise/Policy/ExtDialing> add Ent1 true NS_CLI/SubscriberMgmt/Enterprise/Policy/ExtDialing> get Policy: ExtDialing Enterprise: Ent1
Bytes IN from AS1 INVITE sip:2001;phone-context=/bw/igc/GRP4_1@192.168.5.101;user=phone SIP/2.0
130
Private Extension Dialing Policy

Provides support for intra-group extension dialing for the Application Server redundancy solution. Uses a proprietary extension to the SIP phone-context to exchange intra-group calls between Application Servers. The add command and the following fields are used to add an instance of the policy: enterprise Enable The enterprise name. false true The instance is not active (off). The instance is active (on).
130
Private Policy: VoiceVPN

Location code + min/max digits Private Dial Plan Match User@host, public DN, Treatment
NS_CLI/SubscriberMgmt/Enterprise/Policy/voiceVPN> add Def_Ent true PUBLIC true NS_CLI/SubscriberMgmt/Enterprise/Policy/voiceVPN> get Def_Ent Policy: voiceVPN Enterprise: Def_Ent processE164AsPublic = true Enable = true dfltSel: Selection = {PUBLIC} From = {PUBLIC, PRIVATE}
131
The add command and the following fields are used to add a policy instance: enterprise The enterprise name. Enable false The instance is not active (off). true The instance is active (on). The add command and the following fields are used to a dial plan: enterprise The enterprise name. locCode The code for the site location. extMin The minimum number of digits for an extension. extMax The maximum number of digits for an extension. selector PRIVATE Use only private policies to process calls. PUBLIC Continue through all available policies starting with private policies first, then public ones. ROUTE Route calls with redirect. TRMT Treat calls using the corresponding treatment (trmtID). attribute dm The digit manipulation string. hostId The hosting network element. (Can only be changed when the selector is ROUTE and is mandatory.) grpId The group ID. (Can only be changed when the selector is ROUTE and is mandatory.) trmtId Dynamically generated: tmpun, bdreq, or frbdn. The error code of the treatment to be used. desc The description of the dial plan entry. Use to enclose text.
131
Private Policy: VoiceVPN Dial Plan

NS_CLI/SubscriberMgmt/Enterprise/Policy/voiceVPN/DialPlan> add Ent1 2 3 3 route hostId IHApp grpId Grp3 desc "4 digit extn to grp2 locCode extMin extMax selector dm hostId grpId trmtId desc ===================================================================== 2 3 3 {ROUTE} IHApp Grp3 {} 4 digit extn to grp3 4 3 3 {ROUTE} IHApp Grp2 {} 4 digit extn to grp2 411 0 0 {PUBLIC} {} 7 3 3 {PUBLIC} INS(301977) {} 4 digit extn to grp1 9 7 20 {PUBLIC} DEL(1) {} 911 0 0 {PUBLIC} {}
132
132
Private Policy: EntSubLocation

Originator DN and Terminating DN Both DNs in same Enterprise
HostingNE of dstn user is returned in contact
NS_CLI/SubscriberMgmt/Enterprise/Policy/EntSubLocation> add Def_Ent true
133
Enterprise Subscriber Location Routing Policy

Performs intra-enterprise subscriber location routing (that is, on-net dialing). Routes calls within the same enterprise using the hosting network element as the destination. Bypasses public translations when both the call originator and destination are in user groups part of the same enterprise. Using the enterprise of the caller, this policy searches through the DNs and URLs defined for the enterprise (in its user groups) and tries to find a match with the called DN or URL. If a match is found, the HostingNE of the destination user is returned in the contact list. The add command and the following fields are used to add a policy instance: enterprise Enable The enterprise name. false true The instance is not active (off). The instance is active (on).
133
Private Policy: FarEndHopOff

FarEndHopOff RouteList Match
E.164 Dialed Digits
DialedDigits@PrivateNGW
SubscriberMgmt/Enterprise/Policy/FarEndHopOff> add Ent1 true
Private gateway PRIV_514 must be authorized for use by Ent1 E.164 route list must be created
134
Far-End Hop-Off Routing Policy

Allows an enterprise to route public calls through private gateways using their own facilities. Private gateways are defined as HostingNEs and then authorized for use by a specific enterprise. An enterprise can use their own facilities to perform toll bypass based on the E.164 representation of the dialed digits. For example, company with offices in the US and UK wants all UK traffic (country code 44) to be sent on-net to a private NGW located in the UK. All other PSTN calls will use public routing. Digit manipulation operations can be performed on the dialed digits. If a permissive Voice VPN dial plan is enabled, routing will continue to public policies and append PSTN routes. The add command and the following fields are used to add a policy instance: enterprise Enable The enterprise name. false true The instance is not active (off). The instance is active (on).
134
FarEndHopOff Private Policy Configuration

Authorize Ent1 to use the Priv_514 gateway
NS_CLI/SubscriberMgmt/Enterprise/Policy/FarEndHopOff/AuthHost> add Ent1 PRIV_514
Add E164 route list

NS_CLI/SubscriberMgmt/Enterprise/Policy/FarEndHopOff/RoutingList> add Ent1 PRIV_514 1514 1514 OutDM "del(1)"
135
The add command and the following fields are used to authorize an enterprise to use a gateway: enterprise AuthHost The enterprise name. The network element name.
The add command and the following fields are used to add a routing list: enterprise AuthHost From To attribute The enterprise name. The network element name of a pre-authorized host. Digit sequence defining the beginning of a range of digits. Digit sequence defining the end of a range of digits. OutDM The digit manipulation algorithm to be applied against the requested digits.
135
Private Policy: Enterprise NGW Routing

SITE/Call Type EntNGWRouting RoutiList Match DialedDigits@CPE_NGW
Enterprise NGW Routing policy

Route specific call types from specified subsets of users (defined by site) through CPE-based network gateways Create Site1 Set up PRIV_514 as authorized EntNGWRouting host Create Ent1 Site1 routing to PRIV_514 for DA calls
136
Enterprise NGW Routing Policy

Route specific call types from specified subsets of users (defined by site) through CPEbased network gateways. Users are associated with a site. CPE gateways are defined as HostingNEs and then authorized for use by a specific site. NGW Routing policy allows for routing specific call types through the CPE gateways, while other call types continue to use public routing policies. Digit manipulation operations can be performed on the dialed digits.
136
Enterprise Private Policy Configuration

NS_CLI/SubscriberMgmt/Enterprise/Site> add Ent1 Site1 profile Hosting NS_CLI/SubscriberMgmt/Enterprise/Policy/EntNGWRouting/AuthHost> add Ent1 PRIV_514 NS_CLI/SubscriberMgmt/Enterprise/Policy/EntNGWRouting/Properties> add DA NS_CLI/SubscriberMgmt/Enterprise/Policy/EntNGWRouting/RoutingList> add Ent1 Site1 DA PRIV_514 1 99 "
137
The add command and the following fields are used to authorize an enterprise to use a specific gateway: enterprise authHost The enterprise name. The network element name.
The add command and the following fields are used to add call types: callType desc The type of call. Description of the new call type property.
The add command and the following fields are used to add a routing list: enterprise site callType authHost cost weight outDM The enterprise name. The enterprise site name. The type of call. The network element name of a pre-authorized host. The associated cost code for the gateway. The relative value to randomize distribution of traffic along this route. The digit manipulation algorithm to be applied against the requested digits.
137
Lab 3 Step 3: Enterprise Configuration
138
Enterprise Creation and Private Policy Association

Network Server enterprises allow private policies to be shared by groups. Groups can be assigned to different enterprises and have unique private dial plans. Each teams enterprise will have the following private policies: ExtDialing assigned to support redundancyVoiceVPN, which supports the following private dial plan:
5XXX/9XXX extension dialing between 240364xxxx users in groups belonging to
the enterprise 01144 international calls will be blocked FarEndHopOff to support routing calls to the 514 NPA through private gateway (PRIV_1 to PRIV_9) EntSubLocation to support on-net calling between users in the same enterprise Enterprise Creation 1. Under NS_CLI/SubscriberMgmt/Enterprise, using the add command, each team creates an enterprise with the following parameters:
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9 Enterprise Name ENT_1 ENT_2 ENT_3 ENT_4 ENT_5 ENT_6 ENT_7 ENT_8 ENT_9 Public Profile HOST_1 HOST_2 HOST_3 HOST_4 HOST_5 HOST_6 HOST_7 HOST_8 HOST_9 Call Logging Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled EA PICs NILCAC NILCAC NILCAC NILCAC NILCAC NILCAC NILCAC NILCAC NILCAC
138
Private Policy Association 1. Under the corresponding NS_CLI/SubscriberMgmt/Enterprise/Policy level, each team associates EntSubLocation, voiceVPN (dfltSel is set to PUBLIC and processE164AsPublic is set to true), FarEndHopOff, and ExtDialing private policies to their enterprise. 2. Example: NS_CLI/SubscriberMgmt/Enterprise/Policy/ExtDialing> add ENT_# true FarEndHopOff Configuration 1. Under the NS_CLI/SubscriberMgmt/Enterprise/Policy/ FarEndHopOff/ AuthHost level, each team adds their PRIV_<Team#> private NGW as a valid host for their enterprise. 2. Example: NS_CLI/SubscriberMgmt/Enterprise/Policy/FarEndHopOff/AuthHost> add ENT_# PRIV_# 3. Under the NS_CLI/SubscriberMgmt/Enterprise/Policy/ FarEndHopOff/ RoutingList level, each team creates a route list entry to return their PRIV_<Team#> gateway in the contact list for calls to the 514 area code. (NOTE: The From/To range is E.164-based.) 4. Example: NS_CLI/SubscriberMgmt/Enterprise/Policy/FarEndHopOff/ RoutingList add ENT_2 PRIV_3 1514 1514 OutDM DEL(1) VoiceVPN Configuration 1. Under the NS_CLI/SubscriberMgmt/Enterprise/Policy/voiceVPN/ DialPlan level, each team creates the enterprise dial plan to match the private dial plan described in section 2.1.1.1.1 Private Policies. Use the following table:
LocCode 5 91 92 01144
ExtMin 3 2 2 8
ExtMax 3 2 2 8
Selector Private Public Private trmt
DM INS(240364) INS(240364) INS(240364) -
HostId -
GrpId -
TRMT -
frbdn
Public Static Route List Creation

1. The Network Server supports both dynamic public route selection (through location routing and the NNACL file) and static public routes. The FarEndRtg, NearEndRtg policies share a common system-wide route list. The SvcCtrRtg policy is used to apply instance-specific route lists to a call. Near-End and Far-End Static Routing 1. All calls from 240364xxxx users use a static route list of ngw1(NearEndRtg) with the exception of Teams 1,2,3 and 4 who set toll calls for all users to use ngw1 (FarEndRtg). Teams 5, 6, 7,8 and 9 set International calls for all users to use ngw1 (FarEndRtg). 2. Under NS_CLI/System/Device/RoutingNE/Routing, add the following far-end routing static routes. Enter the tags {} and cost and weight of 1 and 99. Your instructor added the default near-end routing route for all calls from 1240364 users.
139
TEAM TEAM 1 TEAM 2 TEAM 3 TEAM 4 TEAM 5 TEAM 6 TEAM 7 TEAM 8 TEAM 9
NE NGW1 NGW1 NGW1 NGW1 NGW1 NGW1 NGW1 NGW1 NGW1
FROM 1978 1201 1212 1202 1819 1613 1514 2 1301
TO 1978 1201 1212 1202 1819 1613 1514 9 1301
farendCategory NATIONAL NATIONAL NATIONAL NATIONAL NATIONAL LOCAL LOCAL INTERNATIONAL NATIONAL
farendDMIs -1 -1 -1 -1 -1 -1 -1 -1 -1
nearendDMI -1 -1 -1 -1 -1 -1 -1 -1 -1
Service Center Routing Static Route List For all teams, 911 calls from 240364xxxx use a SCRL for each teams DUMMY<Team#> routingNE after prepending 99 to the dialed digits (SvcCtrRtg). For all teams, 411 calls from all users use ngw1 after 411 has been replaced by 18005551234 routing number to the preferred OA carrier (SvcCtrRtg). 1. Under the NS NS_CLI/System/CallP/DMI level, each team creates a DMI entry to prepend 99 to the dialed digits (each team should use their team number as the DM index number). 2. Under the NS_CLI/Policy/SvcCtrRtg/SCRL level, each team creates the following SCRL entries for their teams SvcCtrRtg instance to support the public dial plan.
CallType EM DA
FROM 1240364 1240364
TO 1240364 1240364
callSelector ALL ALL
Address 18005551234
RoutingNE DUMMY<Team#> -
DMI <Team#> -
140
Questions
141
141

BW SANetworkServerModule5 R120

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BW SANetworkServerModule5 R120

Загружено:

Авторское право:

Доступные форматы

BroadWorks System Administration

Module 5: Network Server Release 12 Version 1

Enterprise and Private Policies

Public Policies and Instances

Network Server Reference Documents

Media Server Selection

Network Server Redundancy

Network Server Clustered Architecture

Network Server User Hierarchy

Group provisioning administrator

Network Server Centralized Routing

302 Temp. Moved (destinations)

Network Server: SIP Redirect Server

SIP Redirect Function

Network Server Centralized Network Topology

Enterprise 1 Manual association of groups

Groups share same private dial plans Group2 Group2

Translations and Routing Basics

Private policies: Assigned and configured by enterprises and are

Policies are configurable by Network Server administrator

Policies and Policy Instances

Call Type LO, TO Call Type INT

Near-End LO Far-End TO Far-End INT

Public Routing Profiles

Call Type LO, TO Call Type INT

Near-End LO Far-End TO Far-End INT

Public Routing Profile

Private Policy Subscription Model

Far-End Hop Off

Far-End Hop Off

Far-End Hop Off

Private Policy Subscription Model

Public Profile/Private Policy Assignment

Public Public Routing Routing Profile Profile

Public Routing Profile Private Policies

Public Public Routing Routing Profile Profile

RoutingNE Profile Selection

HostingNE Profile Selection

Network Server: Policy Precedence

Network Server Policies

Configurable Policy Precedence

Configurable Policy Precedence

ResourceNe: ms1 192.168.5.181

ResourceNe: ms2 192.168.5.185

NetServer: ns1 192.169.5.183

Cisco 3600 NGW

HostingNE: PBX1 192.168.6.155

RoutingNE: ngw2 192.168.2.150

Cisco 2600 NGW

Network Server Dial Plan: Private Policies

Network Server Dial Plan: Public Policies

Step 2:Public Policy Configuration

Step 3: Network Server Device Configuration

Step 4: Public Routing Configuration

Step 5: Enterprise Private Policy Configuration

Basic Network Server Configuration

Public Policy: CallTyping - Translations

Call Typing Policy Instance Setup

CallTyping: Dial Plans

Min/Max Action Description

Public Policy: CallScreening -Translations

Call Screening Policy Instance Setup

CallScreening NNACL and LCA files