Noprint | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
Panel | |
---|---|
In this section:
|
This section describes the high-level
Spacevars | ||
---|---|---|
|
This diagram depicts the high-level
Spacevars | ||
---|---|---|
|
Caption | ||||
---|---|---|---|---|
| ||||
This topic describes the basic
Spacevars | ||
---|---|---|
|
Note |
---|
For a complete listing of configuration objects, please see CLI |
...
Reference Guide or EMA User Guide. |
An address context includes all objects associated with a particular IP address space. This includes IP packet interface groups, zones, as well as the contents of each of these objects. In a "flat" IP address space such as the public IP address space, only the single "default" address context is necessary. Additional address contexts are only needed when overlapping local IP addresses (e.g., same IP addresses used in multiple networks connected to the same
Spacevars | ||
---|---|---|
|
A default address context implicitly includes the management interface group and its contained management interfaces. These interfaces are considered "trusted" network interfaces.
Command Syntax
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext name>
diamNode
dnsGroup
intercept
ipAccessControlList
ipInterfaceGroup
ipsec
linkDetectionGroup
natDirectMediaGroup
rtpServerTable
staticRoute
zone |
Example
The below rule blocks all traffic that is not explicitly allowed:
Code Block | ||
---|---|---|
| ||
% set addressContext default ipAccessControlList rule DENYALL_UNTRUST precedence 65015 ipInterfaceGroup EXTERNAL.IPIG action discard |
An IP Interface represents an IP address assigned to a physical port in the system. An IP Interface is associated with an IP Interface Group, and may contain a VLAN tag. VLAN tags are required if more than one IP Interface is associated with a single physical port on the
Spacevars | ||
---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
An IP Interface Group is a named object and contains one or more IP interfaces (IP addresses). An IP Interface Group is Address Context specific, and is permanently bound to a particular Address Context.The service section of an IP trunk group, and a Signaling Port will reference an IP Interface Group typically for purpose of restricting some sort of activity to that IP Interface Group (signaling and media respectively).
A Physical Port (
...
four ports
...
for
Spacevars | ||
---|---|---|
|
Spacevars | |
---|---|
|
...
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
...
; two ports for
...
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The first IP Interface assigned to a port determines if VLAN tagging is used or not. If a VLAN tag is used on the first IP Interface associated with a port, all IP Interfaces for that port must have VLAN tags.
A Zone groups a set of objects (for signaling and call routing information) for a particular Address Context (customer environment). A zone is permanently bound to a particular Address Context, and is normally allocated per customer, per carrier, per organization or per service level associated with one of the above groups. When configuring a zone, include zone name and ID as indicated below.
Zone objects include:
Up to 2,048 zones (
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The zone may also reference global objects such as call routing labels and call routes. Again, even though some global objects may only apply to one customer, the
Spacevars | ||
---|---|---|
|
...
Info |
---|
For comprehensive provisioning limits, see SBC Provisioning Limits. |
Example
The following example sets an Address Context "default" to Zone "peer" with an ID of "2".
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext_name> zone <zone_name>
cac
dnsGroup
gwSigPort
gwTrunkGroup
h323SigPort
h323TrunkGroup
id
ipPeer
messageManipulation
remoteDeviceType
sipSigPort
sipTrunkGroup |
Code Block | ||
---|---|---|
| ||
% set addressContext default zone peer id 2 |
Div | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
Command Syntax
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext_name> zone <zone_name> sipSigPort <sipSigPort index>
dscpValue
ipAddressV4
ipAddressV6
ipInterfaceGroupName
mode
portNumber
recorder
sctpProfileName
state
tcpConnectTimeout
tlsProfileName
transportProtocolsAllowed |
Example
This example sets address context "default" to zone "core" with an ID of 3 and SIP signaling port to 2 for IP interface group "IPIG1" at IP address.
Code Block | ||
---|---|---|
| ||
% set addressContext default zone core id 3 sipSigPort 2 ipInterfaceGroupName IPIG1 ipAddressV4 100.110.11.10 state enabled |
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Trunk groups are also used for call management between
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
Note |
---|
As a best practice, always use UPPERCASE for trunk group names. |
Include Page UniqueTGName UniqueTGName
Command Syntax
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <TG_NAME>
action
cac
callReservation
callRouting
congestionHandling
downstreamForkingSupport
dryUpTimeout
ingressIpPrefix
media
mode
packetOutage
parentSharedCacLimitsPoolName
policy
qoe
services
recordingDNpreference
signaling
state
ucidSupport |
Example
This example creates a core SIP trunk group:
Code Block | ||
---|---|---|
| ||
% set addressContext default zone core sipTrunkGroup CORE media mediaIpInterfaceGroupName IPIG1 |
A Packet Service Profile (PSP) contains a list of up to four codec entries using ERE, and defines various parameters associated with voice packet traffic between
Spacevars | ||
---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
The SBC makes appropriate negotiations and transcoding decisions based on PSP information. PSPs for voice packet traffic between a
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
IP trunk groups are each assigned a PSP used for all calls (in or out) on that trunk group. The default PSP is G711 only (no transcoding).
Packet Service Profiles control the following trunk group media settings:
Command Syntax
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile <packetServiceProfile name>
aal1PayloadSize
codec
dataCalls
flags
honorRemotePrecedence
mediaPacketCos
packetToPacketControl
peerAbsenceAction
preferredRtpPayloadTypeForDtmfRelay
rtcpOptions
secureRtpRtcp
sendRoutePSPPrecedence
silenceFactor
silenceInsertionDescriptor
t38
typeOfService
videoCalls
voiceInitialPlayoutBufferDelay |
Example
This example sets a media profile with a Packet Service Profile named "PSP" that uses a Silence Factor of "40", Type of Service "0", Voice Initial Playout Buffer Delay of "10", Aal1 Payload Size of "47", Preferred RTP Payload Type for DTMF Relay of 128, Media Packet COS of 0 and Honor Remote Precedence disabled.
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile PSP silenceFactor 40 typeOfService 0 voiceInitialPlayoutBufferDelay 10 aal1PayloadSize 47 preferredRtpPayloadTypeForDtmfRelay 128 mediaPacketCos 0 honorRemotePrecedence disable |
A Codec Entry object describes a specific codec that can be offered as part of the Packet Service Profile. Several default Codec entries are pre-configured on the system, and are a good starting point when creating your own. It is recommended to name your Codec Entries in a descriptive manner for easy selection during PSP creation or modification.
Codec Entry key fields:
Command Syntax
Code Block | ||
---|---|---|
| ||
% set profiles media codecEntry <codecEntry_name>
codec
codingRate
dtmf
fax
law
modem
packetSize
preferredRtpPayloadType
sendSid |
Note |
---|
For complete command syntax, please refer to CLI |
...
Reference Guide |
Example
...
This example creates G711u_20ms_2833_T38 a G.711u entry for internal side that uses 20 ms and 2833 only.
Code Block | ||
---|---|---|
| ||
% set profiles media codecEntry G711u_20ms_2833_T38 codec g711 packetSize 20 law ULaw
% set profiles media codecEntry G711u_20ms_2833_T38 dtmf relay rfc2833 removeDigits enable |
IP Signaling Profiles control how various SIP egress and ingress parameters are set and processed by specifying the parameters associated with H.323, SIP, and SIP-I communication sent as part of the outgoing signaling messages after applying standard protocol rules.
You may associate IP signaling profiles with IP trunk groups and virtual trunk groups. A unique profile must be used for each type of destination. A default IP Signaling Profile, "DEFAULT_SIP", is available for use. If changes are required, rather than modifying the default profile, create a new IP Signaling Profile.
Note |
---|
A trunk group has both an IP Signaling Profile and an Egress IP Signaling profile. The Egress IP Signaling profile is used for outgoing signaling (sent from the trunk group). |
Command Syntax
Code Block | ||
---|---|---|
| ||
% set profiles signaling ipSignalingProfile <unique_identifier>
commonIpAttributes
egressIpAttributes
ingressIpAttributes
ipProtocolType |
Example
Code Block | ||
---|---|---|
| ||
% set profiles signaling ipSignalingProfile DEFAULT_SIP commonIpAttributes callTransferFlags forceReRouteViaPsxQuery enable |
IP Peer is the IP address of the far-end device, and is permanently bound to a particular Zone. The primary purpose of this object is to facilitate outbound call routing. An IP Peer is referenced in the routing label, and is used for outgoing calls for a particular trunk group. For inbound calls, the set of IP Peers associated with the give Zone is searched using the peer IP address as the key.
For access configurations, one IP Peer is assigned to the feature server, not for each individual phone. If you define an IP Signaling Profile in the IP Peer (policy subsection), it overrides the profile defined in the trunk group.
Command Syntax
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext> zone <zone> ipPeer <ipPeer_name>
defaultForIp
ipAddress
ipPort
pathCheck
policy
sip
surrogateRegistration |
Example
This example binds IP Peer "core_peer" to zone "core" and assigns IP address 111.100.11.1 to it with port 5060.
Code Block | ||
---|---|---|
| ||
% set addressContext default zone core ipPeer core_peer ipAddress 111.100.11.1 ipPort 5060 |
A Routing Label consists of a set of routes and gateway/trunk group pairs. The Routing Label sends traffic between two trunk groups. One Routing Label is created for each trunk group, and is used to send calls to that trunk group.
Command Syntax
Code Block | ||
---|---|---|
| ||
% set global callRouting routingLabel <routingLabel_name>
action
overflowNOA
overflowNPI
overflowNumber
routePrioritizationType
routingLabelRoute
script |
Example
This example sets routing label "TO_PEER" to send calls to trunk group "PEER".
Code Block | ||
---|---|---|
| ||
% set global callRouting routingLabel TO_PEER routingLabelRoute 1 trunkGroup PEER ipPeer PEER inService inService |
A Route is used to determine how call routing on
Spacevars | ||
---|---|---|
|
Command Syntax
Code Block | ||
---|---|---|
| ||
% set global callRouting route <routingType> |
Example
In this example, a trunk group route is set to send calls arriving on trunk group "PEER" to Routing Label "TO_CORE" which routes call to "CORE" trunk group.
Code Block |
---|
% set global callRouting route trunkGroup PEER DALNBS01 standard Sonus_NULL 1 nationalType nationalType ALL none Sonus_NULL routingLabel TO_CORE |
Pagebreak |
---|