Using Dynamic Metavariables to Add a SIP Signaling Port

Related articles:

SBC SWe N:1 and SWe cloud-based systems provide 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.

Check the currently defined metavariables in the metaVariable table.

> show table system metaVariable 
CE NAME                NAME          VALUE         
---------------------------------------------------
isbctest-10.34.195.79  IF0.DHCP      False         
isbctest-10.34.195.79  IF0.GWV4      10.34.194.1   
isbctest-10.34.195.79  IF0.IPV4      10.34.194.79  
isbctest-10.34.195.79  IF0.Port      Mgt0          
isbctest-10.34.195.79  IF1.DHCP      False         
isbctest-10.34.195.79  IF1.GWV4      10.34.195.1   
isbctest-10.34.195.79  IF1.IPV4      10.34.195.79  
isbctest-10.34.195.79  IF1.Port      Ha0           
isbctest-10.34.195.79  IF2.GWV4      10.34.196.1   
isbctest-10.34.195.79  IF2.IPV4      10.34.196.79  
isbctest-10.34.195.79  IF2.Port      Pkt0          
isbctest-10.34.195.79  IF3.GWV4      10.34.197.1   
isbctest-10.34.195.79  IF3.IPV4      10.34.197.79  
isbctest-10.34.195.79  IF3.Port      Pkt1          
isbctest-10.34.195.79  IF0.PrefixV4  24           
isbctest-10.34.195.79  IF1.PrefixV4  24           
isbctest-10.34.195.79  IF2.PrefixV4  24           
isbctest-10.34.195.79  IF3.PrefixV4  24           
[ok]

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-10.34.195.79 name IF4.IPV4 value 10.34.196.80
[ok]
% commit
[ok]
Commit complete.
% set system metaVariableDynamic isbctest-10.34.195.80 name IF4.IPV4 value 10.34.196.80
[ok]
% commit
[ok]
Commit complete.

Verify that the metavariables were added successfully.

> show table system metaVariableDynamic
CE NAME                NAME      VALUE
-----------------------------------------------
isbctest-10.34.195.79 IF4.IPV4  10.34.196.80
isbctest-10.34.195.80 IF4.IPV4  10.34.196.80
 [ok]

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
```
Where:
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 10.34.196.80.
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;
}
```
Note
- 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.
- It is not recommended to delete a dynamic metavariable that is in use as it can cause issues with configuration. Before deleting, ensure that the dynamic metavariable is not in use by any configuration in the system.

Space shortcuts

Page tree