Oracle SBC Notes

Learning Notes

#

This section is meant to cover notes about Oracle SBC’s and related information.

Oracle SBC’s are meant to act as a B2BUA. This means that it will re-originate traffic and rewrite fields such as the request-uri, via, contact, call-id, etc for topology hiding.

Ideal first time setup configuration items

#

Set the VM RAM to a required level then change the HDD to be (RAM*2) + 12Gb.

prompt-enable enable
format hard-disk

Terms

#

• realm: is a container of resources, this must contain a sip-interface and a steering-pool. A realm can also be configured in a parent child manor.
  • address-prefix can be used as a form of CAC to whitelist networks so that a realm will only send / receive traffic to networks defined in the prefix.
• steering-pool: using for binding media and signaling to a interface. When configuring a steering-pool the network interface parameter is left blank unless you are going to use a separate interface for media from your signaling.
• sip-config: global config, it is needed for the SBC to handle SIP traffic.
  • operation-mode: should be “dialog” for the SBC to act as a B2BUA
  • dialog-transparency: Control topology hiding for call ID’s. defaults to enable and does not change Call ID’s.
• local-policy: Call routing polices are defined with this element. use the to-address to route calls based of the request uri.
• session-agent: A more privileged endpoint from the SBC point of view.
  • constraints: Set to enabled to be able to configure items like max-sessions, like max-inbound-sessions, like max-outbound-sessions, etc.. Constraints can be used un conjunction with a session-group to trigger the next routing choice when a session-group is set to hunt.

Saving and Reverting configs

#

Taking a backup from the CLI.

backup-config <name-of-backup> [running | editing]

Arguments

• Enter the name of the backup configuration file.
• running- Backup the configuration from the running configuration cache. This is an optional argument.
• editing- Backup the configuration from the editing configuration cache. This is an optional argument.

Restoring a backup from the CLI.

restore-backup-config running

verify-config

save-config

activate-config

Monitor and Trace

#

The trace menu is limited to 50 messages per session. If a call has more than 50 messages the oldest message is over written.

Interfaces

#

when deploying a VM these interfaces will not be a 1:1 match on the vmware NIC order. From the CLI you will have to run int interface-swap command in order to fix the order.

• wancom0 - Used for management
• wancom1 - Used for HA
• wancom2 - Used for HA
• S0P0 - Used for calling
• S0P1 - Used for calling
• S1P0 - Used for calling
• S1P1 - Used for calling

Network-interface

#

system interfaces such as wancom are meant for management, not voip traffic. Media interfaces by default will only allow VoIP traffic. Traffic such as ICMP has to be permitted. usable names are as follows.

• S0P0
• S0P1
• S1P0
• S1P1

hip-ip-list is needed to be configured as well as icmp-address to be able to ping the media interfaces, multiple addresses can be configured as well.

Order of operations for first time setup

#

1. system-config
2. filter-config
3. sip-monitoring
4. enable media-manager
5. sip-config
6. phy-interface

Order of operations for a basic call flow

#

1. network-interface
2. sip-manipulation
3. realm
4. sip-interface
5. steering-pool
6. session-agent
7. session-group(optional)
8. local-policy

Routing Logic

#

• the SBC will look at the ingress realm.
• then look at all the local polices that are configured.
• it will ignore the policies that do not match the from and to params.
• Then it will look at all routes remaining, the SBC will then select the route.
  • next it will pick lowest cost
  • then media codec
  • then the most specific to address
  • then the most specific from address
  • then the smallest day in week range
  • then the smallest time of day range.
  • lastly it will choose a policy with the to and from set to “*”.

HA Considerations

#

• If you are setting up HA for an existing device make sure you have a backup.
• Passwords and features should match
  • Features must have HA enabled.
• Make sure you have the targetname set in you bootparams.
• Define your phy-interface virtual MAC
• Configure NTP and cable the wancom ports.
• Configure wancom port on the primary then secondary nodes.
  • wancom1 health score should be a 8.
  • wancom2 health score should be a 9.
  • Addressing should be in the RFC 3330 range.
  • wancom ports will only use the primary and secondary utility address fields.
• Configure HA redundancy on the primary then secondary nodes.
  • health-threshold is the value that causes a graceful switch over.
  • emergency-threshold causes a immediate switch over.
  • percent-drift * advertisement-time will determine the amount of time the SBC will wait for a response.
• Reboot the primary node.
• Once the secondary node acquires the config reboot it.
  • acquire-config 192.0.2.1
  • reboot force activate
• run show health to make sure that the cluster health is 100