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.
Tones:
DTMF Transmit Level - Sets the volume of outgoing DTMF tones. Range between -100 - 0dB. Default -6.
Call Features:
SIP:
Session Refresher in a SIP session that utilizes a session timer, the Session Refresher is the device that will send the periodic Session Refresh requests to refresh the session.
Refresher Options:
Auto - This (Default ) setting allows both ends of the call to negotiate who will be the refresher. Typically this leaves the decision to the device receiving the SIP packets. This setting should be used unless specified otherwise by the network administrator.
UAS - The User Agent Server (UAS) is the VoIP device that responds to the SIP Request. In the case of a phone call it would be considered the “called” device. Engaging this setting will ensure that the SVC-2 card will only negotiate to a Session Timer where the UAS is nominated the refresher.
UAC - The User Agent Client (UAC) is the VoIP device that send the SIP Request. In the case of a phone call it would be considered the “calling” device. Engaging this setting will ensure that the SVC-2 card will only negotiate to a Session Timer where the UAC is nominated the refresher.
Local - This setting will ensure that the SVC-2 card will always be the refresher of a Session Refresh.
Peer - This setting will ensure that the SVC-2 card will never be the refresher of a Session Refresh.
RTP/SRTP:
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.
Layer 2:
RTP Priority, Call Control Priority and Other Traffic Priority Quality of Service (QoS) may be set if VLAN is enabled. Numerical priorities 0-3 are low priority; 4-7 are high priority.
Layer 3 DiffServ:
RTP Traffic, Call Control Priority and Other Traffic levels may be set when Layer 3 Mode is set to DiffServ (Differentiated Services).
Layer 3 TOS:
Keep Alive
This feature sends a packet at defined intervals to keep a firewall port open. Mode defines the type of packet sent, and may be set to None, Options, Register or CRLF. If set to anything other than "None," Interval may be set to 20 to 30 seconds; default is 20.
NAT Static and STUN
When NAT Static is enabled, a network admin may allow the VoIP endpoint to use a static port assignment through a firewall. A public address can be entered and an RTP Port and Signaling Port specified. When STUN is enabled, a VoIP endpoint can use an external STUN server to keep firewall ports open. The Server Address and Server Port can be entered in the VoIP configuration. Enabling one of these options disables the other.
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
Substitution:
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.
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 |