Customer Variables

Custom variables can be defined either in the template scenario scripts or in custom scripts. They must be configured in the Custom/Variables column for the script in the dbo.SbcScriptTemplate table. Its recommended to define them with proper names such as “localhostname” and not simply variable1, variable2 etc.

In the script itself, the custom variable must be defined with the notation "{{CustomVar.xxx}}. In the script example below, the defined customer variables are local host name=variable1 and tenant ID-variable2. These variables then appear as fields in the Onboarding wizard when the script is selected.

In the screen below, custom variables are defined for the IP-PBX.

The Custom Variables defined above appear in the wizard when the IP PBX Onboarding script is selected in the wizard.

In cases where it’s not clear which type of value must be entered for the custom variable, then this must be verified with the SBC INI file. For example, for the Custom Variable shown below “IP‑PBX‑proxy address”, it’s not clear whether to enter an FQDN or IP address. In this case, the Message Manipulation User-defined string defined in the Outbound Message Manipulation rule must be verified on the SBC.

In a similar way, the custom variable SIP-Hostname is configured on the SBC as the sip-group-name. It’s necessary to verify on the SBC whether the value for this parameter is an IP-address or FQDN and whether its configured for a gateway or SBC call.