|Sonus Documentation Portal|
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.
Check the currently defined metavariables 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.
Verify that the metavariables were added successfully.
Create the SIP signaling port using the newly created metavariables.
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 10.34.196.80.
Verify that the metavariable IP address is shown in the configuration for
system metaVariableDynamictable, if the entry already exists in the
metaVariableDynamictable, make sure to add an entry for each of the nodes in the cluster (active and standby).
metaVariableDynamictable are appropriately configured on the cloud hosting the SBC VM, so those addresses are reachable externally.