Some notes i took 2/16/2015
NS_CLI/SubscriberMgmt> ?
The Subscriber Management (SubscriberMgmt) level allows display, addition,
modification, and/or deletion of attributes related to administrators,
enterprises, and users.
Commands:
0) Administrator : go to level Administrator
1) DefaultSourceID : go to level DefaultSourceID
2) Devices : go to level Devices
3) Enterprise : go to level Enterprise
NS_CLI/SubscriberMgmt/Enterprise> ?
The Network Server uses the concept of an enterprise as a way to collect and
organize users who share the same provisioning and routing
characteristics.Private routing policies are assigned to enterprises using this
level. Enterprises can be assigned routing profiles to process public calls as
well as policies to process private calls. User groups allow for a further
defining of an enterprise by breaking it down into smaller groups to which
specific phone numbers and URLs can be assigned. It is also possible to
provision a routing profile for a specific user group. The public policies used
during call processing are derived from the user group's profile first and then
from the enterprise's profile. A combination of both profiles is used and
priority is given to the user group's profile.
NS_CLI/SubscriberMgmt/Enterprise/Site> ?
This level is used to view, add, modify, and delete sites specific to an
enterprise.
4) IMRN : go to level IMRN
5) MaxFailedLoginAttempts : go to level MaxFailedLoginAttempts
6) MinLoginIdLength : go to level MinLoginIdLength
7) NetworkTranslationIndex : go to level NetworkTranslationIndex
8) Numbers : go to level Numbers
9) PasswordRules : go to level PasswordRules
NS_CLI/System/CallP> ?
Configuration on the Network Server for call processing involves translations,
SIP error code treatments, call type definitions, country and national
destination codes, and dial plans. From this level, all call processing
information can be viewed and specified.
Commands:
0) CallTypes : go to level CallTypes
1) CountryCodes : go to level CountryCodes
2) DMI : go to level DMI (Digit Manipulation like REPL)
3) Options : go to level Options
4) PolicyPrecedence : go to level PolicyPrecedence
5) Translation : go to level Translation (LCA and NNACL)
6) Treatment : go to level Treatment
NS_CLI/Policy> ?
The Policy level allows you to configure routing policies and profiles.
Routing policies can be defined as having instances that are a variation of the
policy. Instances are assigned to routing profiles, and profiles are then
associated with enterprises and user groups to instruct the Network Server on
the routing rules for that enterprise or user group.
Commands:
0) CallScreening : go to level CallScreening
1) CallTyping : go to level CallTyping
2) DstSvcRtg : go to level DstSvcRtg
3) EASvcCallRtg : go to level EASvcCallRtg
4) EqualAccess : go to level EqualAccess
5) FarEndRtg : go to level FarEndRtg
6) MediaSrvSel : go to level MediaSrvSel
7) MobileNumberRtg : go to level MobileNumberRtg
8) NearEndRtg : go to level NearEndRtg
9) NumberPortability : go to level NumberPortability
10) OrigRedirect : go to level OrigRedirect
11) PhysLocation : go to level PhysLocation
12) PreCallTyping : go to level PreCallTyping
13) Profile : go to level Profile
The Network Server processes routing rules according to the call type and the
policy instance assigned to the profile for that enterprise or user group. The
following describes policies, policy instances, and profiles.Policies.
- Routing services are implemented through policies (for example, SubLocation, or
Equal Access.). Routing policies specify the routing logic. To implement
different routing applications with similar routing logic, a routing policy
will have different instances.Policy Instances.
- For some policies (for example, Call Screening), a variation can be defined
which has the major properties of the policy but some different attributes.
Not all policies, however, can have multiple instances.Profiles.
- A profile is the assignment of policy instances to enterprises and user groups.
A profile consists of one or more instances of different policies. Once a
profile is defined, it may be assigned too many enterprises and user groups.
Each enterprise and user group can only have one profile. An enterprise must
have a profile, but profiles can also be assigned at the user group level. If
a profile exists for both a user group and its enterprise, the user group
profile has precedence. A system-wide default profile also can be defined. If
a caller is unknown, the default profile is used.
14) RCBasedRtg : go to level RCBasedRtg
15) ReverseTranslation : go to level ReverseTranslation
16) SIMPLE : go to level SIMPLE
17) SMSDefaultRtg : go to level SMSDefaultRtg
18) SMSNearEndRtg : go to level SMSNearEndRtg
19) SubLocation : go to level SubLocation
20) SvcCtrRtg : go to level SvcCtrRtg
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 and originator defined by a range of valid digits to a
destination. It provides support for three types of routing results:Fully
specified directory number destination (meaning, 11 digits for North America
E.164 compliant number)Network gatewaysNetwork gateway controllers along with a
destination trunk groupIf a phone or directory number is first obtained from
the search in the service routing list, it replaces the service number as the
call destination. The call will thereafter be routed using Network Server
public routing policies.If gateways and/or gateway controllers are obtained
from the search in the service routing list, they are be added as contacts in
the SIP 302 response. The call is then routed as is and does not go through
other policies.If a trunk group is obtained from the search in the service
routing list, a valid BroadWorks contact is added in the SIP 302 response. The
user part of the contact contains the address trunkgroup@mgcpGateway (in
escaped form) and the host part contains an Application Server acting as a
gateway controller. The call is then routed as is and does not go through
other policies.For the Service Center Routing policy, a service center routing
list is entered to determine how calls are handled.
NS_CLI/Policy/SvcCtrRtg/SCRL> ?
This level allows for display, addition, modification, and deletion of service
center routing list (SCRL) attributes associated with the Service Center
Routing policy.
21) TandemOverflow : go to level TandemOverflow
22) TgrpTerm : go to level TgrpTerm
23) TrunkGroupTransl : go to level TrunkGroupTransl
24) UrlDialing : go to level UrlDialing
25) XSLocation : go to level XSLocation
No comments:
Post a Comment