You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In this section:

 

All

Unable to show "metadata-from": No such page "_space_variables"
 signaling and routing (both Trunking and Access) are based upon trunk group configurations defined within zones. A zone can contain multiple trunk groups.

CLI commands are case-sensitive and must be entered exactly as shown in this guide. Objects and profiles with names that differ only in case are considered distinct objects.

For example, the following trunk groups are three distinct trunk group entities: trunkgroup1, TRUNKGROUP1, TrunkGroup1. It is strongly recommended to avoid such naming conventions, and to also adopt a standard naming convention when initially defining your configuration.

Note

Trunk group names must be unique across all address contexts, zones, and trunk group types. 

Note

IP peer names must be unique across all address contexts, and zones.

As a best practice, always use UPPERCASE for trunk group names.

Configure Trunk Groups

To configure a SIP trunk group for an Address Context, use commands similar to the example below:

% set addressContext default zone peer sipTrunkGroup PEERTG state enabled mode inService  
% set addressContext default zone peer sipTrunkGroup PEERTG media mediaIpInterfaceGroupName IPIG0

To view the trunk group configuration data, execute the following:

> show table addressContext default zone zonePublicTrunking

To view the status of trunk groups in a particular zone, execute the following command:

> show table addressContext default zone MYZONE trunkGroupStatus
                                                TOTAL                                              TOTAL
                                     TOTAL      CALLS     INBOUND  OUTBOUND  TOTAL       PRIORITY  OUTBOUND  BW                  BW       BW
                                     CALLS      INBOUND   CALLS    CALLS     CALLS       CALL      CALLS     CURRENT  BW         INBOUND  OU
NAME                      STATE      AVAILABLE  RESERVED  USAGE    USAGE     CONFIGURED  USAGE     RESERVED  LIMIT    AVAILABLE  USAGE    US
--------------------------------------------------------------------------------------------------------------------------------------------
CANARY                    inService  -1         0         0        0         -1          0         0         -1       -1         0        0
HORNET                    inService  -1         0         0        0         -1          0         0         -1       -1         0        0
GRIZZLY                   inService  -1         0         0        0         -1          0         0         -1       -1         0        0
DESKPHONE                 inService  -1         0         0        0         -1          0         0         -1       -1         0        0
PRONGHORN                 inService  -1         0         0        0         -1          0         0         -1       -1         0        0
PRONGHORNB                inService  -1         0         0        0         -1          0         0         -1       -1         0        0
[ok][2013-06-20 11:12:40]

Delete Trunk Groups

To delete a trunk group, execute commands similar to the example below. This involves disabling the trunk group and it putting it out of service before deleting it.

% set addressContext default zone zonePublicTrunking sipTrunkGroup MYTRUNKGROUP state disabled mode outOfService

% delete addressContext default zone zonePublicTrunking sipTrunkGroup MYTRUNKGROUP

  • No labels