HowTo: Session Manager Trunking
From Jaymzworld
Contents |
Introduction
Communication Manager
Texas
IP NODE NAMES
Name IP Address
asm-sm100 10.0.24.9
default 0.0.0.0
procr 10.0.24.20
In the Authoritative Domain field, enter the SIP domain name for which this network region applies. This same SIP domain name is used in the Session Manager interface.
IP NETWORK REGION
Region: 1
Location: 1 Authoritative Domain: asmlab.com
Name: local region 1
MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes
Codec Set: 1 Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048 IP Audio Hairpinning? n
UDP Port Max: 3329
DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y
Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46 Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 6
Audio 802.1p Priority: 6
Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
Go to the IP Codec Set screen. Check that you have the right media compression for your SIP endpoint types and other constraints.
IP Codec Set
Codec Set: 1
Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711MU n 2 20
2:
SIGNALING GROUP
Group Number: 20 Group Type: sip
Transport Method: tls
IMS Enabled? n
Near-end Node Name: procr Far-end Node Name: asm-sm100
Near-end Listen Port: 5061 Far-end Listen Port: 5061
Far-end Network Region: 1
Far-end Domain: iptlab.com
Bypass If IP Threshold Exceeded? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y
Session Establishment Timer(min): 3 IP Audio Hairpinning? n
Enable Layer 3 Test? n Direct IP-IP Early Media? n
H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6
display trunk-group 20 Page 1 of 21
TRUNK GROUP
Group Number: 20 Group Type: sip CDR Reports: y
Group Name: SIP to ASM COR: 95 TN: 1 TAC: 120
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Signaling Group: 20
Number of Members: 10
display trunk-group 20 Page 3 of 21
TRUNK FEATURES
ACA Assignment? n Measured: none
Maintenance Tests? y
Numbering Format: public
UUI Treatment: service-provider
Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Show ANSWERED BY on Display? y
display trunk-group 20 Page 4 of 21
PROTOCOL VARIATIONS
Mark Users as Phone? n
Prepend '+' to Calling Number? n
Send Transferring Party Information? n
Send Diversion Header? n
Support Request History? y
Telephone Event Payload Type: 101
NUMBERING - PUBLIC/UNKNOWN FORMAT
Total
Ext Ext Trk CPN CPN
Len Code Grp(s) Prefix Len
Total Administered: 1
5 705 20 5 Maximum Entries: 9999
DIAL PLAN ANALYSIS TABLE
Location: all Percent Full: 1
Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
1 3 dac
3 4 aar
7 5 ext
8 1 fac
9 1 fac
* 3 fac
# 3 fac
AAR DIGIT ANALYSIS TABLE
Location: all Percent Full: 1
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
3 7 7 999 aar n
30 4 4 20 aar n
Pattern Number: 20 Pattern Name: SIP to ASM
Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 20 0 n user
2: n user
3: n user
4: n user
5: n user
6: n user
BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 M 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none
Maine
Session Manager
The steps below show how to administer Session Manager (SM) enterprise routing using the System Manager (IMSM) Network Routing Policy screens.
Commit and Save to Pending modes
There are two modes of operation when adding, editing or deleting elements via the NRP screens. They are:
- Use the Commit button to immediately save the associated screen data to the database and distribute it to the SM instances. A successful Commit operation transitions the state of the associated element to the Sync state.
- Use the Save to Pending button to temporarily store the proposed changes but not save them to the database or distribute them to the SM instances. A successful Save to Pending operation transitions the state of the associated element to the Saved state. A subsequent Commit operation on an element in the Saved state will save the associated screen data into the database and distribute it to the SM instances. Save to Pending can be used to build up a set of changes that need to be all in place before committing them.
Administration
Connect to the System Manager management interface at http://ip-addr-of-server/SMGR. Log into the system and from the left menu choose Network Routing Policy.
The images used here have been scaled down. Click on the respective image to see a full resolution version.
SIP Domains
The NRP SIP Domain screen is used to administer the set of SIP domains and sub-domains for which the SM enterprise is authoritative for routing. This information is used to determine if a SIP user is part of the SIP network.
Administer a SIP Domain or set of SIP Domains if you plan to use domain based routing. You will be able to select one of the administered SIP Domains on the Dial Pattern screen.
Locations
The NRP Locations screen is used to administer Routing Origination Locations. Locations are call origination locations that are used by call processing to determine the originating location of the caller. This call originating information will be evaluated when SM calculates the destination where the call has to go (may be the final destination or the next hop). The current physical location of the caller will be determined by the IP address of the device the caller uses. The Location associates an IP address pattern with a name to be used in the Routing Policy to determine the originating location of a call.
The basic idea is that the IP address pattern defines a location (similar to an IP network region) to be able to perform originating location-based routing. The Locations screen is also used for the establishment of emergency calls.
The Locations screen can contain one or several IP addresses. Each SIP Entity has a particular IP address. Depending on the physical and geographic location of each SIP entity, some of the SIP Entities may be grouped into a single Location. If there are for example, two CMs located at Denver, they can form one Location named Denver.
Adaptations
The NRP Adaptations screen is used to administer adaptations.
Adaptations can be optionally used to modify SIP messages that are leaving an SM instance (egress adaptation) and that are entering an SM instance (ingress adaptation). This adaptation function is mainly needed when Service Provider trunks (SIP Trunks) have to be used that require special SIP protocol conventions. Adaptation modules are not configured and defined by NRP but adaptation modules can be loaded into SMs and can be assigned to SIP entities. Adaptations can include digit conversions for incoming and outgoing traffic. Digit conversion can be configured by NRP for both directions incoming and outgoing. Adaptation modules can also be used to modify host name values.
Available adaptations (case sensitive):
- DigitConversionAdapter
- CiscoAdapter
- VerizonAdapter
- AttAdapter
SIP Entities
Use the NRP SIP Entities screen to administer SIP Entities. SIP Entities are all the network elements that act as the SIP System. SIP Entities include SM instances, CMs, SBCs, etc. To administer minimal routing via SM, you will need to configure a SIP Entity of type CM and a second SIP Entity of type ASM.
- If you need to specify an Adaptation Module for the SIP Entity, click the drop down selector for the Adaptation field.
- If you need to specify the Location for the SIP Entity, click the drop down selector for the Location field.
- If the SIP Entity Type is ASM and you need to specify an Outbound Proxy for the SIP Entity, click the drop down selector for the Outbound Proxy field.
- If you need to specify the Port parameters, click the Add button under Port. Then supply the necessary Port and Protocol parameters.
Entity Links
The general configuration of connections between SIP entities enables NRP and SM to identify specific connection configurations (e.g. Trusted Hosts, outbound proxy) between SIP Entities.
- Entity Links are configured to connect two SIP Entities
- Support of Trusted Hosts: Trusted Hosts will be indicated by assigning the Trust State to the link that connects the entities.
Time Ranges
The NRP Time Ranges screen is used to administer time ranges with start and end times. Time ranges will be used for time-based routing configuration. Time ranges are:
- Used for time based routing
- Used to specify a start time and end time
Eventually, every Routing Policy will require at least one time range and will also require that all the hours in a week are covered by one of the specified time ranges.
Routing Policies
All Routing Policies together form the enterprise wide dial plan. *Routing Policies can include the Origination of the caller, the dialed digits of the called party, the SIP domain of the called party and the actual time the call occurs.
Optionally, instead of dialed digits of the called party and the SIP domain of the called party a regular expression can be defined. Depending on one or multiple of the inputs mentioned above a destination where the call should be routed is determined.
Optionally, the destination can be qualified by deny which means that the call will not be routed.
SM uses the data configured in the Routing Policy to find the best match against the number (or address) of the called party.
- If you need to associate Time of Day routing parameters with this Routing Policy, Click the Add button for the Time of Day section.
- Fill in the relative Rankings that you would like associated with each Time Range. Remember that lower Ranking values indicate higher priority.
- Associate Dial Patterns and Regular Expressions with Routing Policies via the Dial Pattern and Regular Expression sections. Note that the Dial Patterns and Regular Expressions must have been previously administered before they can be associated with the Routing Policy on this screen.
Dial Patterns
The NRP Dial Patterns screen is used to assign Locations and Routing Policies to dial patterns.
- Enter the Dial Pattern General information in the General section. Note that a SIP Domain can be provided to restrict the Dial Pattern to the specified SIP Domain.
- Click the Add button under the Locations and Routing Policies section. Select all the desired Locations and Routing Policies that you want to be associated with the Dial Pattern by clicking the checkbox in from of each item.
- If you need to specify Deny Locations, which indicate that calls from the specified Locations will be denied, click the Add button under the Denied Locations section.
Regular Expressions
The NRP Regular Expressions screen is used to associate Regular Expressions with Routing Policies.
Generally speaking, you would Enter the Pattern in the General section. Then select the Rank Order to specify the relative ranking that this regular expression should be given. Lower Rank Order numbers have higher priority. Also, check the Deny checkbox if calls that have the specified regular expression are to be denied.
- Select all the desired Routing Policies that you want to be associated with the Regular Expression by clicking the check box in from of each listed Routing Policy.
Regular expressions were not used in this configuration, but an example is included below.
References
- Avaya "Installing and Administering Avaya Aura Session Manager". Avaya, June 9, 2009
