Skip to end of metadata
Go to start of metadata


The SBC SWe Cloud provides a system table that you can populate with additional metavariables to add to the metadata in an existing SBC deployment. The metavariable values in the table become available to the SBC instance without having to rebuild it. For example, you can add the metavariable values needed to configure an additional SIP signaling port in a deployed SBC instance using the following set of commands. The configuration needs to be done on the Headend SBC in the SBC SWE cluster.

  1. Check the currently defined metavariables in the metaVariable table.

    > show table system metaVariable 
    CE NAME                NAME          VALUE         
    isbctest-  IF0.DHCP      False         
    isbctest-  IF0.GWV4   
    isbctest-  IF0.IPV4  
    isbctest-  IF0.Port      Mgt0          
    isbctest-  IF1.DHCP      False         
    isbctest-  IF1.GWV4   
    isbctest-  IF1.IPV4  
    isbctest-  IF1.Port      Ha0           
    isbctest-  IF2.GWV4   
    isbctest-  IF2.IPV4  
    isbctest-  IF2.Port      Pkt0          
    isbctest-  IF3.GWV4   
    isbctest-  IF3.IPV4  
    isbctest-  IF3.Port      Pkt1          
    isbctest-  IF0.PrefixV4  24           
    isbctest-  IF1.PrefixV4  24           
    isbctest-  IF2.PrefixV4  24           
    isbctest-  IF3.PrefixV4  24           
  2. In the metaVariableDynamic table, add new metavariables to define the interfaces you plan to use for the additional SIP signaling port. You must run the commands twice to create the variables on both the active and standby nodes.

    % set system metaVariableDynamic isbctest- name IF4.IPV4 value
    % commit
    Commit complete.
    % set system metaVariableDynamic isbctest- name IF4.IPV4 value
    % commit
    Commit complete.
  3. Verify that the metavariables were added successfully.

    > show table system metaVariableDynamic
    CE NAME                NAME      VALUE
    isbctest- IF4.IPV4
    isbctest- IF4.IPV4
  4. Create the SIP signaling port using the newly created metavariables.

    % set addresscontext default zone ZONE1 sipSigPort 3 state enabled portNumber 5060 transportProtocolsAllowed sip-udp ipInterfaceGroup LIG1 ipVarV4 IF4.IPV4

    sipSigPort "3" refers to the index number of the SIP signaling port. In the example, the command creates SIP signaling port 3 with a port number of 5060. The SIP signaling port supports UDP transport and is added to the LIG1 IP interface group. The previously added metavariable IF4.IPV4 specifies that the IP address for the SIP signaling port is

  5. Verify that the metavariable IP address is shown in the configuration for sipSigPort 3.

    > show addressContext default zone ZONE1 sipSigPort 
    sipSigPort 3 {
        ipInterfaceGroupName      LIG1;
        portNumber                5060;
        state                     enabled;
        transportProtocolsAllowed sip-udp;
        ipVarV4                   IF4.IPV4;


    • You cannot add an entry to the system metaVariableDynamic table, if the entry already exists in the system metaVariable table.
    • When you add an entry in the metaVariableDynamictable, make sure to add an entry for each of the nodes in the cluster (active and standby).
    • Ensure the IP addresses you configure in the metaVariableDynamic table are appropriately configured on the cloud hosting the SBC VM, so those addresses are reachable externally.