[Index]

Model: relation/HcsSipGwREL

SIP Local Gateways

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

This topic outlines a possible workflow for setting up Local Break Out using a SIP Local Gateway. This workflow copies IOS commands to the IOS device CLI after each step. Alternatively, you can use the consolidate commands tool to create one set of IOS commands to run all at once.

Perform these steps:

  1. Create customized Command Builders for events. Either add new ones, or clone the default ones and update the clones. See Set up a Command Builder or Clone a Command Builder.
  2. Add an IOS device at customer hierarchy level. See Set up an IOS Device.
  3. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  4. Add SIP Local Gateways at customer hierarchy level. See Set up SIP Local Gateway.
  5. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  6. Perform manual configuration on the SIP Local Gateway. See IOS Gateway Manual Configuration.
  7. Associate SIP Local Gateways to sites. See Associate a SIP Local Gateway to a Site.
  8. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  9. Create E.164 Associations. See Associate a Set of E.164 Numbers to One Directory Number or Associate a Range of E.164 Numbers to a Range of Directory Numbers.
  10. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.

IOS Devices

Full HTML Help

In VOSS Automate, you can set up IOS devices such as SIP Local Gateways and Analog Gateways. And you can set up Command Builders to generate the appropriate IOS commands, which allow you to copy to the IOS device CLI.

Related Topics

Command Builders in the Core Feature Guide

IOS Device Management Workflow

This section outlines a possible workflow for setting up Local Break Out (LBO) using a SIP Local Gateway. This workflow copies IOS commands to the IOS device CLI after each step. Alternatively, you can use the consolidate commands tool to create one set of IOS commands to run all at once.

Perform these steps:

  1. Create customized Command Builders for events. Either add new ones, or clone the default ones and update the clones. See Set up a Command Builder or Clone a Command Builder.
  2. Add an IOS device at customer hierarchy level. See Set up an IOS Device.
  3. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  4. Add SIP Local Gateways at customer hierarchy level. See:

Set up SIP Local Gateway in the Core Feature Guide

  1. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  2. Perform manual configuration on the SIP Local Gateway. See IOS Gateway Manual Configuration.
  3. Associate SIP Local Gateways to sites. See:

Associate / Disassociate SIP Local Gateway to a Site in the Core Feature Guide

  1. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.
  2. Create E.164 Associations. See:

Associate a Set of E164 Numbers to One Internal Number in the Core Feature Guide

Associate a Range of E164 Numbers to a Range of Internal Numbers in the Core Feature Guide

  1. View the IOS Commands log and copy commands to the IOS device CLI. See View IOS Commands Log.

Set up SIP Local Gateway

Full HTML Help

Before You Begin

A SIP Local Gateway is a logical gateway running on a physical IOS device.

Procedure

  1. Log in as provider, reseller, or customer administrator.

  2. Set the hierarchy path to the customer for which you are setting up the SIP Local Gateway.

  3. Choose Apps Management > IOS > SIP Local Gateways.

  4. Click Add.

  5. On the SIP Local Gateways screen, complete at minimum, the mandatory SIP Local Gateways Fields.

  6. Click Save.

    View transaction progress and details in the Transaction Logs.

Related Topics

Transaction Logging and Audit in the Core Feature Guide.

SIP Local Gateways Fields

Field Description
Name * Enter a name for the SIP Local Gateway. This field is mandatory.
Description Enter a description for the SIP Local Gateway.
IOS Device *

Choose the IOS Device on which the SIP Local Gateway is located. This field is mandatory. Note:

An IOS Device can have only one SIP Local Gateway.

Once selected, the IOS Device cannot be changed.
Country *

Choose the country where the SIP Local Gateway is. This field is mandatory.

The country selected must be the same country as the Site to which the SIP local gateway will be associated.
CUCM Publisher *

Choose the CUCM Publisher. All CUCM Publishers that are in the customer's NDL are displayed. This field is mandatory.

The chosen CUCM Publisher must be the same as the CUCM Publisher in the NDL for the Site to which the SIP local gateway will be associated.
SIP Trunk *

Choose the SIP Trunk from the ones available on the CUCM Publisher. This field is mandatory. Note:

Only SIP Trunks configured at the customer hierarchy are available. If the customer uses a shared CUCM, then SIP Trunks must be manually configured at the customer level in VOSS Automate to be selectable here.
Gateway Address

Gateway Address. This field is read-only and is derived from the selected SIP Trunk.

Note:

If a SIP Trunk has multiple destination addresses, only the first one is used.
Gateway Port Gateway Port. This field is read-only and is derived from the selected SIP Trunk.
Run on Every Node Indicates whether call processing is distributed across all CUCM subscriber nodes. This field is read-only and is derived from the selected SIP Trunk.
Dial Peer Info

If the Run on Every Node is cleared then the Call Manager Group members are displayed in priority order.

If the Run on Every Node check box is selected, then all CUCM nodes in the cluster are displayed, but without priority.
Enable Command Builder *

Select this check box to have Command Builder generate commands when SIP Local Gateway is added, deleted, or modified. Default = Selected.

If this is checked and the Override below is also checked, then E164-to-DN disassociation will fail if it exceeds the default limit. This setting should therefore be un-selected for disassociation to succeed in this case.
Override Voice Translation Limit ** Warning may invalidate Command Builder Configuration** Select this check box to override Voice Translation Limit if E164 associations exceed 80. Default = Cleared. Note that once checked and saved, then un-checking will not reset the limit to 80. Contact VOSS support or a high level admin to reset it to 80.

Delete a SIP Local Gateway

Full HTML Help

  1. Log in as provider, reseller, or customer administrator.

  2. Choose Apps Management > IOS > SIP Local Gateways.

  3. Select the SIP Local Gateway that you want to delete, then click the Delete icon on the details page.

    View transaction progress and details in the Transaction Logs. See Transaction Logging and Audit

Related Topics

Transaction Logging and Audit in the Core Feature Guide.

Update a SIP Local Gateway

Full HTML Help

This procedure updates a SIP Local Gateway. You can also perform this task if you have updated the SIP Trunk associated with the SIP Local Gateway.

  1. Log in as provider, reseller, or customer administrator.

  2. Set the hierarchy path to the customer whose SIP Local Gateway you are updating.

  3. Choose Apps Managment > IOS > SIP Local Gateways.

  4. Click the SIP Local Gateway to update.

  5. On the SIP Local Gateways screen you can update only the following fields:

    Field Description
    Name Enter a name for the SIP Local Gateway. This field is mandatory.
    Description Enter a description for the SIP Local Gateway.
    Enable Command Builder Select this check box to have Command Builder generate commands when SIP Local Gateway is added, deleted, or modified.

    However, you can update the SIP Trunk in Apps Management > CUCM > SIP Trunks.

  6. Click Save.

    View transaction progress and details in the Transaction Logs.

Related Topics

Transaction Logging and Audit in the Core Feature Guide.

Allow an admin to manage a SIP Local GW instance.

Model Details: relation/HcsSipGwREL

Title Description Details
Name * The name of the SIP local gateway
  • Field Name: name
  • Type: String
  • MaxLength: 1024
Description Description for the SIP local gateway
  • Field Name: description
  • Type: String
  • MaxLength: 1024
IOS Device * IOS Device the gateway runs on
  • Field Name: iosDevice
  • Type: String
  • Target: data/HcsIOSDeviceDAT
  • Target attr: name
  • MaxLength: 1024
  • Format: uri
Country * Country where the gateway is
  • Field Name: country
  • Type: String
  • Target: data/Countries
  • Target attr: country_name
  • MaxLength: 256
  • Format: uri
CUCM Publisher * Select CUCM from the customer's NDLs
  • Field Name: cucmPublisher
  • Type: String
  • Target: data/CallManager
  • MaxLength: 1024
  • Format: uri
Sip Trunk * Sip Trunk destined to the gateway
  • Field Name: sipTrunkName
  • Type: String
  • MaxLength: 1024
Gateway Address IP address of the gateway
  • Field Name: gatewayAddressIpv4
  • Type: String
  • MaxLength: 1024
Gateway Port Port of the gateway
  • Field Name: gatewayPort
  • Type: Integer
Run On Every Node Indicate whether call processing is distributed across all CUCM nodes
  • Field Name: runOnEveryNode
  • Type: Boolean
Dial Peer Info Dial peer info used for gateway configuration. If Run on Every Node is not enabled, then the Call Manager Group members are displayed in priority order. If Run on Every Node is enabled, then all CUCM nodes are displayed, but without priority
  • Field Name: dialPeerInfo
  • Type: String
  • MaxLength: 1024
Enable Command Builder Whether or not to generate IOS commands for the gateway Default: true
  • Field Name: enableCommandBuilder
  • Type: Boolean
  • Default: true
Override Voice Translation Limit - ** Warning may invalidate Command Builder Configuration ** Override Voice Translation Limit if E164 associations exceed 80 Default: false
  • Field Name: overrideVTGWLimit
  • Type: Boolean
  • Default: false
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024