VoIP Line Properties

Configuring a VoIP Phone Line

In addition to configuring the line properties for a VoIP phone in the Control/Status dialog, configuring the line can also be accomplished by clicking the Line Properties entry under the General section of the Properties sheet. This will open a dialog window where the Line Select buttons can be used to edit the properties of each line.

General Tab


Call Features:

Protocol Tab



SIPS Protocol:

SIPS Keyword - This field is used to enter the keyword used for secure SIP on a per-Line basis. To enable Secure SIP, go To VoIP Control/ Status Block, open the property sheet DSP properties, Set Protocol SIP-Transport to TLS.

Quality of Service (QoS)

Layer 2:

Layer 3 DiffServ:

Layer 3 TOS:



Keep Alive

NAT Static and STUN


Local Dial Plan is a regular expression which determines dialing behavior according to the method specified in RFC 3435. Use the default Local Dial Plan string unless an alternate one has been provided for you. Default Local Dial Plan: [2-9]11|0T|011xxx.T|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxT


Microsoft Lync/Skype for Business uses .NET Framework regular expressions to specify numeric match patterns that the server uses to translate dial strings to E.164 format for the purpose of performing reverse number lookup. The substitution dialog allows the definition of similar normalization rules to allow the Tesira VoIP card to automatically translate the dialed digits to E.164 format. Multiple rules can be defined. Each rule includes a label, a matching pattern, and a translation pattern. The rules are based upon lines.

Once substitutions have been added, a right click context menu is available allowing the option to Copy all rows, Copy selected rows or a Paste to bottom function.

Useful normalization rules

Tesira VoIP follows .Net framework regular expression to create matching rules and is a subset of .Net framework regular expression.  Multiple number pattern and translation rules can be created. The number pattern and translation rule must be present as a pair. More details on Normalization can be found here, or by visiting https://support.biamp.com/ and searching normalization.

 The below gives some basic information:

The table below gives some examples and explanations about the rules.

Use case Number pattern Translation Example
Translates 4-digit extensions ^(\d{4})$ +1503718$1 1234 is translated to +15037181234
Translates 5-digit extensions starting 5 ^5(\d{4})$ +1503718$1 51234 is translated to +15037181234
Translates 7-digit numbers ^(\d{7})$ +1503$1 7189238 is translated to +15037189238
Translates 10-digit numbers ^(\d{10})$ +1$1 5037189238 is translated to +15037189238
Translates numbers with long distance prefixes ^1(\d{10})$ +$1 15037189238 is translated to +5037189238
Translates numbers with international prefixes ^011(\d*)$ +$1 011915037189238 is translated to +915037189238
Translates 0 to an operator ^0$ +15037180100 0 is translated to +15037180100
Translates numbers with prefixes ^5678(\d{4})$ +1503718$1 56781234 is translated to +15037181234