Scomtois:

VTScada

2026-09-28T20:19:14Z

Scomtois:

[[File:VTScada-logo.png|right|200px]]

'''VTScada''' is an industrial automation and SCADA platform developed by Trihedral. Among its alarm notification features, VTScada can use SIP-based Voice over IP (VoIP) services to place automated voice calls and, when supported, exchange SMS messages with alarm recipients.

This article describes how to configure '''VTScada''' for use with [[VoIP.ms]].

The configuration presented in this guide uses a dedicated VoIP.ms [[Sub Accounts|Sub Account]]. Although the Main Account may also be used, a dedicated Sub Account is recommended when possible because it provides separate SIP credentials and prevents registration conflicts with other SIP devices or applications.

'''Note:''' VTScada is a third-party application and is not developed or maintained by VoIP.ms. Menu names and available options may vary between VTScada versions.

== Requirements ==

Before configuring VTScada, you should have:

:* An active [[VoIP.ms]] account with available balance.
:* A VoIP.ms SIP account or preferably a dedicated [[Sub Accounts|Sub Account]].
:* A VoIP.ms [[Choosing Server|POP server]] selected for the connection.
:* A valid outbound Caller ID.
:* A DID number if incoming calls or SMS functionality will be used.
:* VTScada installed and configured with the Alarm Notification System.
:* Internet access from the VTScada workstation to the selected VoIP.ms POP.

If SMS notifications or SMS acknowledgement will be used:

:* The DID must support SMS.
:* SMS/MMS must be enabled for the DID.
:* Incoming SMS messages must be routed to the SIP account used by VTScada.

== Creating a VoIP.ms Sub Account ==

Although VTScada can be configured with the VoIP.ms Main Account, using a dedicated Sub Account is recommended.

To create one:

:1. Log in to the VoIP.ms Customer Portal.

:2. Navigate to:

::'''Sub Accounts → Create Sub Account'''
:: [[File:VTScada-VoIP-CreateSubAccountMenu.png|none]]

:3. Configure the following basic options:

::* '''Protocol:''' SIP
::* '''Authentication Type:''' User/Password Authentication
::* '''Username:''' Enter a name that identifies the VTScada system, for example:
:::<pre>vtscada</pre>
::* '''Password:''' Enter a strong and unique SIP password.
::* '''Caller ID Number:''' Select the DID or verified Caller ID that VTScada should present for outbound calls.
::* '''Encrypted SIP Traffic:''' Yes
The resulting SIP username will use the following format:

:<pre>123456_vtscada</pre>

Where:

:* '''123456''' represents your VoIP.ms account number.
:* '''vtscada''' represents the Sub Account username.
:: [[File:VTScada-VoIP-CreateSubAccount.png|none]]
Click '''Create Account''' to save the configuration.

For additional information regarding Sub Accounts, refer to [[Sub Accounts]].

== Selecting a VoIP.ms POP Server ==

VTScada must register to one of the VoIP.ms SIP servers.

Select a server that is geographically appropriate for the VTScada installation. For example:

:<pre>montreal1.voip.ms</pre>

The same server should also be selected as the '''POP''' for any DID that will be routed directly to the VTScada SIP account.

For more information about available servers, refer to [[Choosing Server|Choosing a Server]].

'''Important:''' If the DID is configured on a different POP than the server used by VTScada, incoming calls may not reach the application correctly.

== Configuring the DID ==

A DID is not necessarily required when VTScada will only place outbound voice calls.

A DID is required when the installation will use features such as:

:* Receiving calls through the VoIP.ms number.
:* Sending SMS from a VoIP.ms number.
:* Receiving SMS messages.
:* Alarm acknowledgement through SMS.

To configure the DID:

:1. From the VoIP.ms Customer Portal, navigate to:

::'''DID Numbers → Manage DID(s)'''
:: [[File:VTScada-VoIP-ManageDID.png]]

:2. Locate the DID and click the '''Edit''' icon.
:: [[File:VTScada-VoIP-EditDID.png]]

=== DID POP ===

Ensure that the '''DID Point of Presence (POP)''' corresponds to the same VoIP.ms server configured in VTScada.

For example:

:<pre>montreal1.voip.ms</pre>
:: [[File:VTScada-VoIP-DIDPOP.png|VoIPms PoP Server]]

=== DID Routing ===

If incoming SIP calls should be delivered directly to VTScada:

:1. Locate the '''DID Routing''' section.

:2. Select the '''SIP/IAX''' routing option.

:3. Select from the drop-down menu, the Sub Account created for VTScada.

For example:
:<pre>123456_vtscada</pre>
:: [[File:VTScada-VoIPms_DIDROUTING.png]]

:4. Save the DID configuration.

== SMS Configuration ==

If VTScada will use SMS notifications or SMS acknowledgement, SMS must first be enabled on the VoIP.ms DID.

From:

:'''DID Numbers → Manage DID(s)'''
:: [[File:VTScada-VoIP-ManageDID.png]]

Edit the desired DID and locate:
:: [[File:VTScada-VoIP-EditDID.png]]

:'''Message Service (SMS/MMS)'''
Enable the SMS/MMS service.
:: [[File:VTScada-VoIP-EnableSMS.png]]

Then enable the option to route received SMS messages to a SIP Account and select the VTScada Sub Account.

For example:

:<pre>123456_vtscada</pre>

The SIP account must be successfully registered with VoIP.ms for incoming SIP MESSAGE requests to reach VTScada.

'''Important:''' Avoid registering the same SIP Sub Account simultaneously on VTScada and another SIP application. Doing so may cause calls or SMS messages to be delivered to the wrong registration.

'''Note:''' SMS functionality should be thoroughly tested before relying on SMS acknowledgement for production alarm handling.

== SIP Encryption ==

VoIP.ms supports SIP signaling encryption using TLS and media encryption using SRTP.

If encrypted SIP traffic will be used with VTScada, enable this option on the VTScada Sub Account.

Navigate to:

:'''Sub Accounts → Manage Sub Accounts'''

Edit the VTScada Sub Account, and set:

:* '''Encrypted SIP Traffic:''' Yes
:: [[File:VTScada-VoIP-SIPEncryption.png]]

Save the configuration.

'''Important:''' Once '''Encrypted SIP Traffic''' is enabled for the Sub Account, the SIP client must also be configured to use TLS/SRTP. Standard unencrypted SIP registrations for that Sub Account will no longer be accepted.

For additional information, refer to [[Call Encryption - TLS/SRTP]].

== Configuring VTScada ==

Once the VoIP.ms SIP account has been prepared, VTScada can be configured.

From the VTScada application:

:1. Open the '''Application Configuration''' dialog.

:2. Select '''Edit Properties'''.

:3. Make sure the configuration is displayed in '''Basic Mode'''.

:4. Select the '''Alarms''' tab.

:5. Scroll to the '''VOIP Settings''' section.

:: [[File:VTScada-VoIP-Settings.png|VTScada VoIP Settings]]

=== Enable VoIP Calls ===

Enable:

:'''Enable VOIP Calls'''

This allows the Alarm Notification System to place voice calls using the configured VoIP.ms SIP account.

If SMS functionality will also be used, enable:

:'''Enable VOIP SMS'''

=== Workstation ===

Select the workstation that will act as the Alarm Notification Server.

When multiple VTScada workstations are present, it is recommended to explicitly select the appropriate workstation rather than leaving the option set to '''Default'''.

=== SIP Identity ===

Enter the SIP identity using the VoIP.ms Sub Account and selected POP.

The general format is:

:<pre>VTScada <sip:ACCOUNT_SUBACCOUNT@SERVER.voip.ms></pre>

For example:

:<pre>VTScada <sip:123456_vtscada@montreal1.voip.ms></pre>

If the VoIP.ms Main Account is used instead, the format would be similar to:

:<pre>VTScada <sip:123456@montreal1.voip.ms></pre>

=== SIP Server ===

Enter the selected VoIP.ms POP as a SIP URI.

For example:

:<pre>sip:montreal1.voip.ms</pre>

=== SIP Proxy ===

When required by the VTScada configuration, use the same VoIP.ms POP server.

For example:

:<pre>sip:montreal1.voip.ms</pre>

=== SIP Domain ===

Enter the hostname of the selected VoIP.ms server without the ''sip:'' prefix.

For example:

:<pre>montreal1.voip.ms</pre>

VTScada uses the SIP Domain when constructing SIP URIs for destinations stored as regular telephone numbers.

=== SIP Login User ID ===

Enter the complete VoIP.ms SIP username.

For a Sub Account:

:<pre>123456_vtscada</pre>

For the Main Account:

:<pre>123456</pre>

=== SIP Password ===

Enter the SIP password associated with the account being used.

When using a Sub Account, this is the password configured when the Sub Account was created.

Do not enter the VoIP.ms Customer Portal password when using a Sub Account.

== Example Configuration ==

A typical VTScada configuration using a VoIP.ms Sub Account might therefore appear as follows:

:'''Enable VOIP Calls:'''
::Enabled

:'''Enable VOIP SMS:'''
::Enabled, if required

:'''Workstation:'''
::The workstation hosting the Alarm Notification System

:'''SIP Identity:'''
::<pre>VTScada <sip:123456_vtscada@montreal1.voip.ms></pre>

:'''SIP Server:'''
::<pre>sip:montreal1.voip.ms</pre>

:'''SIP Proxy:'''
::<pre>sip:montreal1.voip.ms</pre>

:'''SIP Domain:'''
::<pre>montreal1.voip.ms</pre>

:'''SIP Login User ID:'''
::<pre>123456_vtscada</pre>

:'''SIP Password:'''
::The password configured for the VTScada Sub Account.

Replace the example account number, username and server with the information from your own VoIP.ms account.

== Telephone Number Format ==

When telephone numbers are entered directly into a VTScada roster, use complete telephone numbers.

For calls within the North American Numbering Plan (NANPA), using the complete 11-digit number is recommended.

For example:

:<pre>15145551234</pre>

Avoid spaces, parentheses and hyphens.

For example, instead of:

:<pre>(514) 555-1234</pre>

use:

:<pre>15145551234</pre>

VTScada combines the destination with the configured SIP Domain when creating the SIP URI used to place the call.

== Configuring a Roster Tag ==

After the SIP connection has been configured, create or modify a VTScada '''Roster Tag''' to define which users will receive alarm notifications.

In VTScada:

:1. Create or edit the desired Roster Tag.

:2. Under the '''ID''' tab, configure the identifying information for the roster.

:3. Open the '''Contacts''' tab.

:4. Select:

::'''+ Add Contact'''

:5. Add the telephone number or SMS destination for each alarm recipient.

:6. Open the '''Settings''' tab.

:7. Configure the trigger conditions that will activate the roster.

During initial testing, it may be useful to configure only one recipient and a short notification delay.

Once the configuration has been validated, configure the final notification sequence required by the installation.

== User Identification Codes ==

VTScada can require users receiving voice alarm notifications to authenticate before acknowledging an alarm.

For each applicable VTScada user:

:1. Open '''Accounts'''.

:2. Select the user.

:3. Locate '''Alternate Identification'''.

:4. Configure a numerical identification code or PIN.

:5. Apply the changes.

Provide the appropriate identification code to the corresponding alarm recipient.

== Testing the Configuration ==

Before placing the configuration into production, verify both the VoIP.ms SIP registration and the VTScada alarm notification process.

=== Verify SIP Registration ===

Log in to the VoIP.ms Customer Portal and navigate to the Portal Home.

Locate the '''Sub Account Registration Status''' section.

The VTScada Sub Account should appear as registered.

For example:

:<pre>123456_vtscada Registered</pre>

If the Sub Account does not appear as registered, verify:

:* SIP username.
:* SIP password.
:* VoIP.ms server hostname.
:* Network or firewall configuration.
:* TLS configuration, if encryption is enabled.

=== Test Outbound Calls ===

Configure a temporary Roster contact using a telephone number that can be answered during testing.

Generate a test alarm and verify that:

:* VTScada initiates the call.
:* The destination telephone rings.
:* The alarm announcement can be heard.
:* DTMF input is recognized.
:* The alarm can be acknowledged successfully.

=== Test SMS ===

If SMS is enabled:

:* Send an alarm notification by SMS.
:* Confirm that the message is received.
:* Send the required acknowledgement response.
:* Confirm that VTScada receives and processes the response.

Do not rely on SMS acknowledgement in production until the complete send-and-response process has been successfully tested.

== Testing with a Softphone ==

When troubleshooting, a SIP softphone such as MicroSIP can be temporarily configured with the same VoIP.ms credentials to verify that the account itself is operating correctly.

This can help distinguish between:

:* A VoIP.ms account configuration problem.
:* Incorrect SIP credentials.
:* A network or firewall issue.
:* A VTScada configuration issue.

'''Important:''' Disconnect the softphone before starting VTScada again.

Using the same SIP account simultaneously in both applications can cause registration and routing conflicts.

Whenever possible, separate VoIP.ms Sub Accounts should be used when multiple SIP applications must remain registered at the same time.

== Advanced VTScada Settings ==

=== VOIPPickUpDelay ===

VTScada includes the advanced property:

:<pre>VOIPPickUpDelay</pre>

This value determines the interval between the start of a VoIP call and the beginning of the voice announcement.

The VTScada default is normally 10 seconds.

Depending on the telephone network and destination, a shorter value may provide faster alarm announcements.

For example:

:<pre>VOIPPickUpDelay = 2</pre>

This setting should be tested carefully since beginning playback too quickly may cause the beginning of the alarm message to be missed.

=== VOIPPort ===

VTScada normally uses the standard SIP port configured by the application.

If another SIP application on the same workstation is already using the local SIP port, VTScada allows its local VoIP port to be changed through its Setup.INI configuration.

For example:

:<pre>VOIPPort = 5062</pre>

After modifying Setup.INI, restart VTScada.

Changing the local VTScada SIP port normally does not require changing the VoIP.ms server hostname.

== Troubleshooting ==

=== Registration Fails ===

If VTScada cannot register with VoIP.ms:

:* Confirm that the SIP Login User ID contains the complete Sub Account username.
::* Example:
:::<pre>123456_vtscada</pre>

:* Confirm the SIP password.
:* Confirm that the correct VoIP.ms POP hostname is being used.
:* Check the registration status from the VoIP.ms Customer Portal.
:* Confirm that TLS/SRTP settings match the '''Encrypted SIP Traffic''' setting of the Sub Account.
:* Confirm that a firewall is not blocking SIP or RTP traffic.

=== SIP 401 or 403 Errors ===

VTScada's communication logs may contain SIP response codes such as:

:<pre>401 Unauthorized</pre>

or:

:<pre>403 Forbidden</pre>

These generally indicate that authentication was unsuccessful.

Verify:

:* SIP Login User ID.
:* SIP password.
:* SIP server.
:* Encryption configuration.
:* That another application is not simultaneously using the same SIP credentials.

=== Outbound Calls Work but Incoming Calls Do Not ===

Verify:

:* The DID is routed to the correct SIP Account.
:* VTScada is successfully registered.
:* The DID POP matches the VoIP.ms server used by VTScada.

For example, if VTScada registers to:

:<pre>montreal1.voip.ms</pre>

the DID should normally also use:

:<pre>montreal1.voip.ms</pre>

=== Calls Connect but There Is No Audio ===

If a call connects but audio is missing in one or both directions:

:* Verify the firewall configuration.
:* Verify that RTP traffic is permitted between the VTScada workstation and VoIP.ms.
:* Check for SIP ALG on the router and disable it when it interferes with SIP communication.
:* Review the VTScada VoIP communication logs.

=== SMS Can Be Sent but Replies Are Not Received ===

Verify:

:* SMS/MMS is enabled on the DID.
:* The DID is configured to route received SMS messages to the VTScada SIP Account.
:* The VTScada SIP Account is registered.
:* The same SIP account is not registered simultaneously on another application.
:* TLS settings are consistent between VTScada and VoIP.ms.

=== Viewing VTScada VoIP Logs ===

VTScada can generate VoIP communication logs for troubleshooting.

These logs are normally stored under:

:<pre>VTScada\TraceFiles\VOIPLogs</pre>

Review the logs for SIP registration errors, rejected requests and authentication responses.

The logs can be particularly useful when determining whether a problem occurs before or after communication reaches the VoIP.ms server.

== Security Recommendations ==

Because VTScada may be responsible for critical alarm notifications, additional security measures are recommended.

:* Use a dedicated VoIP.ms Sub Account for VTScada.
:* Use a strong and unique SIP password.
:* Do not expose the VTScada management interface directly to the public Internet.
:* Consider enabling [[Call Encryption - TLS/SRTP|TLS/SRTP]].
:* Consider using VoIP.ms POP and IP restrictions where appropriate.
:* Disable international calling on the Sub Account if it is not required.
:* Restrict outbound calling capabilities to only those services required by the installation.
:* Regularly verify that alarm notifications are operating correctly.

Refer to [[General Security]] for additional VoIP.ms security recommendations.

== See Also ==

:* [[Sub Accounts]]
:* [[Manage DID]]
:* [[SMS]]
:* [[Choosing Server|Choosing a Server]]
:* [[Call Encryption - TLS/SRTP]]
:* [[General Security]]
:* [[DID Troubleshooting]]

== VTScada Documentation ==

The following VTScada documentation provides additional information about
the Alarm Notification System and VoIP configuration:

:* [https://www.vtscada.com/help/Content/D_AlarmSystem/Dev_VoIPSetup.htm Setting Up a Specific VoIP Connection]
:* [https://www.vtscada.com/help/Content/D_AlarmSystem/Dev_VOIP.htm Using VoIP for Alarm Notification]
:* [https://www.vtscada.com/help/Content/D_Tags/Dev_RosterTags.htm Roster Tags]
:* [https://www.vtscada.com/help/Content/D_Customize/dev_AccountsAndRoles.htm Accounts and Roles]
:* [https://www.vtscada.com/help/Content/D_Widgets/Dev_RosterAlarmTestWidget.htm Roster Alarm Test Widget]
:* [https://www.vtscada.com/help/Content/D_Widgets/D_ExportCommLog.htm Export Comm Log Widget]
:* [https://www.vtscada.com/help/Content/D_AlarmSystem/Dev_AlarmList.htm Alarm List]
:* [https://www.vtscada.com/help/Content/D_Widgets/D_CallManagerStatus.htm Call Manager Status Widget]

[[Category:PBX]]
[[Category:VoIP Software]]

VTScada

2026-09-28T19:19:03Z

Scomtois: Created page with "200px '''VTScada''' is an industrial automation and SCADA platform developed by Trihedral. Among its alarm notification features, VTScada can use..."

[[File:VTScada-logo.png|right|200px]]

'''VTScada''' is an industrial automation and SCADA platform developed by Trihedral. Among its alarm notification features, VTScada can use SIP-based Voice over IP (VoIP) services to place automated voice calls and, when supported, exchange SMS messages with alarm recipients.

This article describes how to configure '''VTScada''' for use with [[VoIP.ms]].

The configuration presented in this guide uses a dedicated VoIP.ms [[Sub Accounts|Sub Account]]. Although the Main Account may also be used, a dedicated Sub Account is recommended when possible because it provides separate SIP credentials and prevents registration conflicts with other SIP devices or applications.

'''Note:''' VTScada is a third-party application and is not developed or maintained by VoIP.ms. Menu names and available options may vary between VTScada versions.

== Requirements ==

Before configuring VTScada, you should have:

:* An active [[VoIP.ms]] account with available balance.
:* A VoIP.ms SIP account or preferably a dedicated [[Sub Accounts|Sub Account]].
:* A VoIP.ms [[Choosing Server|POP server]] selected for the connection.
:* A valid outbound Caller ID.
:* A DID number if incoming calls or SMS functionality will be used.
:* VTScada installed and configured with the Alarm Notification System.
:* Internet access from the VTScada workstation to the selected VoIP.ms POP.

If SMS notifications or SMS acknowledgement will be used:

:* The DID must support SMS.
:* SMS/MMS must be enabled for the DID.
:* Incoming SMS messages must be routed to the SIP account used by VTScada.

== Creating a VoIP.ms Sub Account ==

Although VTScada can be configured with the VoIP.ms Main Account, using a dedicated Sub Account is recommended.

To create one:

:1. Log in to the VoIP.ms Customer Portal.

:2. Navigate to:

::'''Sub Accounts → Create Sub Account'''

:3. Configure the following basic options:

::* '''Protocol:''' SIP
::* '''Authentication Type:''' User/Password Authentication
::* '''Username:''' Enter a name that identifies the VTScada system, for example:
:::<pre>vtscada</pre>
::* '''Password:''' Enter a strong and unique SIP password.
::* '''Caller ID Number:''' Select the DID or verified Caller ID that VTScada should present for outbound calls.

The resulting SIP username will use the following format:

:<pre>123456_vtscada</pre>

Where:

:* '''123456''' represents your VoIP.ms account number.
:* '''vtscada''' represents the Sub Account username.

Click '''Create Account''' to save the configuration.

For additional information regarding Sub Accounts, refer to [[Sub Accounts]].

== Selecting a VoIP.ms POP Server ==

VTScada must register to one of the VoIP.ms SIP servers.

Select a server that is geographically appropriate for the VTScada installation. For example:

:<pre>montreal1.voip.ms</pre>

The same server should also be selected as the '''POP''' for any DID that will be routed directly to the VTScada SIP account.

For more information about available servers, refer to [[Choosing Server|Choosing a Server]].

'''Important:''' If the DID is configured on a different POP than the server used by VTScada, incoming calls may not reach the application correctly.

== Configuring the DID ==

A DID is not necessarily required when VTScada will only place outbound voice calls.

A DID is required when the installation will use features such as:

:* Receiving calls through the VoIP.ms number.
:* Sending SMS from a VoIP.ms number.
:* Receiving SMS messages.
:* Alarm acknowledgement through SMS.

To configure the DID:

:1. From the VoIP.ms Customer Portal, navigate to:

::'''DID Numbers → Manage DID(s)'''

:2. Locate the DID and click the '''Edit''' icon.

=== DID POP ===

Ensure that the '''DID Point of Presence (POP)''' corresponds to the same VoIP.ms server configured in VTScada.

For example:

:<pre>montreal1.voip.ms</pre>

=== DID Routing ===

If incoming SIP calls should be delivered directly to VTScada:

:1. Locate the '''DID Routing''' section.

:2. Select the SIP Account routing option.

:3. Select the Sub Account created for VTScada.

For example:

:<pre>123456_vtscada</pre>

:4. Save the DID configuration.

== SMS Configuration ==

If VTScada will use SMS notifications or SMS acknowledgement, SMS must first be enabled on the VoIP.ms DID.

From:

:'''DID Numbers → Manage DID(s)'''

Edit the desired DID and locate:

:'''Message Service (SMS/MMS)'''

Enable the SMS/MMS service.

Then enable the option to route received SMS messages to a SIP Account and select the VTScada Sub Account.

For example:

:<pre>123456_vtscada</pre>

The SIP account must be successfully registered with VoIP.ms for incoming SIP MESSAGE requests to reach VTScada.

'''Important:''' Avoid registering the same SIP Sub Account simultaneously on VTScada and another SIP application. Doing so may cause calls or SMS messages to be delivered to the wrong registration.

'''Note:''' SMS functionality should be thoroughly tested before relying on SMS acknowledgement for production alarm handling.

== SIP Encryption ==

VoIP.ms supports SIP signaling encryption using TLS and media encryption using SRTP.

If encrypted SIP traffic will be used with VTScada, enable this option on the VTScada Sub Account.

Navigate to:

:'''Sub Accounts → Manage Sub Accounts'''

Edit the VTScada Sub Account, display the '''Advanced Options''' and set:

:* '''Encrypted SIP Traffic:''' Yes

Save the configuration.

'''Important:''' Once '''Encrypted SIP Traffic''' is enabled for the Sub Account, the SIP client must also be configured to use TLS/SRTP. Standard unencrypted SIP registrations for that Sub Account will no longer be accepted.

For additional information, refer to [[Call Encryption - TLS/SRTP]].

== Configuring VTScada ==

Once the VoIP.ms SIP account has been prepared, VTScada can be configured.

From the VTScada application:

:1. Open the '''Application Configuration''' dialog.

:2. Select '''Edit Properties'''.

:3. Make sure the configuration is displayed in '''Basic Mode'''.

:4. Select the '''Alarms''' tab.

:5. Scroll to the '''VOIP Settings''' section.


[[File:VTScada-VoIP-Settings.png|center|800px|thumb|VTScada VoIP Settings]]

=== Enable VoIP Calls ===

Enable:

:'''Enable VOIP Calls'''

This allows the Alarm Notification System to place voice calls using the configured VoIP.ms SIP account.

If SMS functionality will also be used, enable:

:'''Enable VOIP SMS'''

=== Workstation ===

Select the workstation that will act as the Alarm Notification Server.

When multiple VTScada workstations are present, it is recommended to explicitly select the appropriate workstation rather than leaving the option set to '''Default'''.

=== SIP Identity ===

Enter the SIP identity using the VoIP.ms Sub Account and selected POP.

The general format is:

:<pre>VTScada <sip:ACCOUNT_SUBACCOUNT@SERVER.voip.ms></pre>

For example:

:<pre>VTScada <sip:123456_vtscada@montreal1.voip.ms></pre>

If the VoIP.ms Main Account is used instead, the format would be similar to:

:<pre>VTScada <sip:123456@montreal1.voip.ms></pre>

=== SIP Server ===

Enter the selected VoIP.ms POP as a SIP URI.

For example:

:<pre>sip:montreal1.voip.ms</pre>

=== SIP Proxy ===

When required by the VTScada configuration, use the same VoIP.ms POP server.

For example:

:<pre>sip:montreal1.voip.ms</pre>

=== SIP Domain ===

Enter the hostname of the selected VoIP.ms server without the ''sip:'' prefix.

For example:

:<pre>montreal1.voip.ms</pre>

VTScada uses the SIP Domain when constructing SIP URIs for destinations stored as regular telephone numbers.

=== SIP Login User ID ===

Enter the complete VoIP.ms SIP username.

For a Sub Account:

:<pre>123456_vtscada</pre>

For the Main Account:

:<pre>123456</pre>

=== SIP Password ===

Enter the SIP password associated with the account being used.

When using a Sub Account, this is the password configured when the Sub Account was created.

Do not enter the VoIP.ms Customer Portal password when using a Sub Account.

== Example Configuration ==

A typical VTScada configuration using a VoIP.ms Sub Account might therefore appear as follows:

:'''Enable VOIP Calls:'''
::Enabled

:'''Enable VOIP SMS:'''
::Enabled, if required

:'''Workstation:'''
::The workstation hosting the Alarm Notification System

:'''SIP Identity:'''
::<pre>VTScada <sip:123456_vtscada@montreal1.voip.ms></pre>

:'''SIP Server:'''
::<pre>sip:montreal1.voip.ms</pre>

:'''SIP Proxy:'''
::<pre>sip:montreal1.voip.ms</pre>

:'''SIP Domain:'''
::<pre>montreal1.voip.ms</pre>

:'''SIP Login User ID:'''
::<pre>123456_vtscada</pre>

:'''SIP Password:'''
::The password configured for the VTScada Sub Account.

Replace the example account number, username and server with the information from your own VoIP.ms account.

== Telephone Number Format ==

When telephone numbers are entered directly into a VTScada roster, use complete telephone numbers.

For calls within the North American Numbering Plan (NANPA), using the complete 11-digit number is recommended.

For example:

:<pre>15145551234</pre>

Avoid spaces, parentheses and hyphens.

For example, instead of:

:<pre>(514) 555-1234</pre>

use:

:<pre>15145551234</pre>

VTScada combines the destination with the configured SIP Domain when creating the SIP URI used to place the call.

== Configuring a Roster Tag ==

After the SIP connection has been configured, create or modify a VTScada '''Roster Tag''' to define which users will receive alarm notifications.

In VTScada:

:1. Create or edit the desired Roster Tag.

:2. Under the '''ID''' tab, configure the identifying information for the roster.

:3. Open the '''Contacts''' tab.

:4. Select:

::'''+ Add Contact'''

:5. Add the telephone number or SMS destination for each alarm recipient.

:6. Open the '''Settings''' tab.

:7. Configure the trigger conditions that will activate the roster.

During initial testing, it may be useful to configure only one recipient and a short notification delay.

Once the configuration has been validated, configure the final notification sequence required by the installation.

== User Identification Codes ==

VTScada can require users receiving voice alarm notifications to authenticate before acknowledging an alarm.

For each applicable VTScada user:

:1. Open '''Accounts'''.

:2. Select the user.

:3. Locate '''Alternate Identification'''.

:4. Configure a numerical identification code or PIN.

:5. Apply the changes.

Provide the appropriate identification code to the corresponding alarm recipient.

== Testing the Configuration ==

Before placing the configuration into production, verify both the VoIP.ms SIP registration and the VTScada alarm notification process.

=== Verify SIP Registration ===

Log in to the VoIP.ms Customer Portal and navigate to the Portal Home.

Locate the '''Sub Account Registration Status''' section.

The VTScada Sub Account should appear as registered.

For example:

:<pre>123456_vtscada Registered</pre>

If the Sub Account does not appear as registered, verify:

:* SIP username.
:* SIP password.
:* VoIP.ms server hostname.
:* Network or firewall configuration.
:* TLS configuration, if encryption is enabled.

=== Test Outbound Calls ===

Configure a temporary Roster contact using a telephone number that can be answered during testing.

Generate a test alarm and verify that:

:* VTScada initiates the call.
:* The destination telephone rings.
:* The alarm announcement can be heard.
:* DTMF input is recognized.
:* The alarm can be acknowledged successfully.

=== Test SMS ===

If SMS is enabled:

:* Send an alarm notification by SMS.
:* Confirm that the message is received.
:* Send the required acknowledgement response.
:* Confirm that VTScada receives and processes the response.

Do not rely on SMS acknowledgement in production until the complete send-and-response process has been successfully tested.

== Testing with a Softphone ==

When troubleshooting, a SIP softphone such as MicroSIP can be temporarily configured with the same VoIP.ms credentials to verify that the account itself is operating correctly.

This can help distinguish between:

:* A VoIP.ms account configuration problem.
:* Incorrect SIP credentials.
:* A network or firewall issue.
:* A VTScada configuration issue.

'''Important:''' Disconnect the softphone before starting VTScada again.

Using the same SIP account simultaneously in both applications can cause registration and routing conflicts.

Whenever possible, separate VoIP.ms Sub Accounts should be used when multiple SIP applications must remain registered at the same time.

== Advanced VTScada Settings ==

=== VOIPPickUpDelay ===

VTScada includes the advanced property:

:<pre>VOIPPickUpDelay</pre>

This value determines the interval between the start of a VoIP call and the beginning of the voice announcement.

The VTScada default is normally 10 seconds.

Depending on the telephone network and destination, a shorter value may provide faster alarm announcements.

For example:

:<pre>VOIPPickUpDelay = 2</pre>

This setting should be tested carefully since beginning playback too quickly may cause the beginning of the alarm message to be missed.

=== VOIPPort ===

VTScada normally uses the standard SIP port configured by the application.

If another SIP application on the same workstation is already using the local SIP port, VTScada allows its local VoIP port to be changed through its Setup.INI configuration.

For example:

:<pre>VOIPPort = 5062</pre>

After modifying Setup.INI, restart VTScada.

Changing the local VTScada SIP port normally does not require changing the VoIP.ms server hostname.

== Troubleshooting ==

=== Registration Fails ===

If VTScada cannot register with VoIP.ms:

:* Confirm that the SIP Login User ID contains the complete Sub Account username.
::* Example:
:::<pre>123456_vtscada</pre>

:* Confirm the SIP password.
:* Confirm that the correct VoIP.ms POP hostname is being used.
:* Check the registration status from the VoIP.ms Customer Portal.
:* Confirm that TLS/SRTP settings match the '''Encrypted SIP Traffic''' setting of the Sub Account.
:* Confirm that a firewall is not blocking SIP or RTP traffic.

=== SIP 401 or 403 Errors ===

VTScada's communication logs may contain SIP response codes such as:

:<pre>401 Unauthorized</pre>

or:

:<pre>403 Forbidden</pre>

These generally indicate that authentication was unsuccessful.

Verify:

:* SIP Login User ID.
:* SIP password.
:* SIP server.
:* Encryption configuration.
:* That another application is not simultaneously using the same SIP credentials.

=== Outbound Calls Work but Incoming Calls Do Not ===

Verify:

:* The DID is routed to the correct SIP Account.
:* VTScada is successfully registered.
:* The DID POP matches the VoIP.ms server used by VTScada.

For example, if VTScada registers to:

:<pre>montreal1.voip.ms</pre>

the DID should normally also use:

:<pre>montreal1.voip.ms</pre>

=== Calls Connect but There Is No Audio ===

If a call connects but audio is missing in one or both directions:

:* Verify the firewall configuration.
:* Verify that RTP traffic is permitted between the VTScada workstation and VoIP.ms.
:* Check for SIP ALG on the router and disable it when it interferes with SIP communication.
:* Review the VTScada VoIP communication logs.

=== SMS Can Be Sent but Replies Are Not Received ===

Verify:

:* SMS/MMS is enabled on the DID.
:* The DID is configured to route received SMS messages to the VTScada SIP Account.
:* The VTScada SIP Account is registered.
:* The same SIP account is not registered simultaneously on another application.
:* TLS settings are consistent between VTScada and VoIP.ms.

=== Viewing VTScada VoIP Logs ===

VTScada can generate VoIP communication logs for troubleshooting.

These logs are normally stored under:

:<pre>VTScada\TraceFiles\VOIPLogs</pre>

Review the logs for SIP registration errors, rejected requests and authentication responses.

The logs can be particularly useful when determining whether a problem occurs before or after communication reaches the VoIP.ms server.

== Security Recommendations ==

Because VTScada may be responsible for critical alarm notifications, additional security measures are recommended.

:* Use a dedicated VoIP.ms Sub Account for VTScada.
:* Use a strong and unique SIP password.
:* Do not expose the VTScada management interface directly to the public Internet.
:* Consider enabling [[Call Encryption - TLS/SRTP|TLS/SRTP]].
:* Consider using VoIP.ms POP and IP restrictions where appropriate.
:* Disable international calling on the Sub Account if it is not required.
:* Restrict outbound calling capabilities to only those services required by the installation.
:* Regularly verify that alarm notifications are operating correctly.

Refer to [[General Security]] for additional VoIP.ms security recommendations.

== See Also ==

:* [[Sub Accounts]]
:* [[Manage DID]]
:* [[SMS]]
:* [[Choosing Server|Choosing a Server]]
:* [[Call Encryption - TLS/SRTP]]
:* [[General Security]]
:* [[DID Troubleshooting]]

== External Documentation ==

:* VTScada — ''Using VoIP for Alarm Notification''
:* VTScada — ''Setting Up a Specific VoIP Connection''

[[Category:PBX]]
[[Category:VoIP Software]]

Incredible PBX 2027

2026-09-22T18:15:31Z

Scomtois:

[[File:IncrediblePBX-VoIPms.jpg|300px|right|link=https://incrediblepbx.com/|IncrediblePBX]]

Incredible PBX is an open source, GPL aggregation which bundles industry-leading components to provide a production-ready, turnkey unified communications VoIP platform with support for SIP and IAX. IncrediblePBX® includes a choice of CentOS®, Rocky®, Debian®, Ubuntu®, or Raspbian® operating systems coupled with the Apache® web server, PHP®, MariaDB®/MySQL® DBMS, SendMail® or Exim® mail server, HylaFax®/AvantFax®, WebMin®, OpenVPN®, NeoRouter® VPN, IPtables firewall plus Fail2Ban® and PortKnocker®, and the latest releases of Asterisk® and FreePBX®. It is the only aggregation offering the ability to customize and recompile Asterisk from source code with your choice of Asterisk versions. Versions of Incredible PBX can be deployed with on-premise hardware including the Raspberry Pi®, in the cloud on a variety of platforms, or on virtual machine platforms: VirtualBox®, VMware®. Proxmox®, Windows 11 WSL, Mac UTM, and Linux LXC Containers.

== Pre-requisites ==
Before proceeding, a sub-account is required. This will be your SIP trunk.
You can create one under your VoIP.ms client portal, under '''Sub Account''' > '''Create Sub-Account'''. Be sure you have those following setting in it.
:- '''Authentication type''': (x) User/Password Authentication
:- '''Device type''': (x) Asterisk, IP PBX, Gateway or VoIP Switch
:- '''CallerID Number''': (x) I use a system capable of passing its own CallerID
:- '''Allowed Codecs''': Select '''[x] G711u''' ''Default codec'' and '''[x] G722''' for HD voice

= Trunk Configuration =

When you install IncrediblePBX, it comes with multiple trunk preset that helps you to get up and running faster. VoIP.ms is present in the list.

We will reuse the one that is already present and adapt the configuration.

: '''[1]''': Log into your IncrediblePBX admin.
: '''[2]''': Go under '''"Connectivity"''' tab then '''"Trunk"'''.
: '''[3]''': Search for the trunk '''"VoIPms-Registered"''' and click on '''"Edit"'''

== General tab ==

: '''[1]''': '''Trunk Name''': You can change the name of the trunk. Must be in lowercases. Hyphen is accepted.
: '''[2]''': '''Outbound CallerID''': (Optional, you can leave it empty and define the caller ID on your outbound route instead.
:: If you want to define a specific outbound caller ID Name and Number for all outbound calls that will use this trunk.
:: If you do so, after setting the caller ID, you will need to select '''Force Trunk CID''' on the ''CID Option''. The format whould be:

:: Enter your CallerID Name and Number in the following format:
<div style="margin-left:50px;
padding:5px;
font-family: Consolas, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace;
color: silver;
border-left: 6px solid rgb(208, 56, 45, 0.8);
box-shadow: 8px 6px 9px -2px #f2f2f2;
background-color: black;
width:70%;">

 "CALLERID NAME" <##########>
</div>
<div style="margin-left:50px;
padding:8px;
border-left: 6px solid rgb(73, 111, 199, 0.8);
box-shadow: 5px 4px 4px 4px #f5f5f5;
background-color: rgba(73, 111, 199, 0.08);
width:70%;">

'''⚠️ IMPORTANT - Outbound CallerID''' 
* Entering outbound Caller ID Name, it must be in '''CAPITAL LETTERS'''. ''This will appears more clearly/visible on some devices.'' 
* You must '''NOT use any special characters'''. ''They will not be displayed and it prevents potential outbound call issues.'' 
* Do '''NOT exceed 15 characters'''. ''Traditional canadian providers will '''not show more than 15 characters'''. We suggest shrinking or adapt the name.'' 
* Spaces are allowed in a caller ID name but count as a characters. ''(do not exceed 15 chars. in total)''.
</div>
:
: '''[3]''': '''Disable Trunk''': Set it to '''No'''

== Dial Number Manipulation Rules Tab ==
: Leave this section empty.

== sip Settings Tab ==
=== Outgoing tab ===
You will need to adapt the '''PEER Details'''
: '''Trunk Name''': You can change the name of the trunk. Must be in lowercases. Hyphen is accepted.
: '''PEER Details''': Change the '''username''', '''secret''', '''host''', '''fromuser''', '''allow'''

<div style="margin-left:50px;
padding:5px;
font-family: Consolas, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace;
color: silver;
border-left: 6px solid rgb(208, 56, 45, 0.8);
box-shadow: 8px 6px 9px -2px #f2f2f2;
background-color: black;
width:58%;">

: username=######_SubAccount
: type=friend
: trustrpid=yes
: sendrpid=yes
: secret=YourSubaccountPasswordHere
: qualify=yes
: nat=yes
: insecure=port,invite
: host=atlanta.voip.ms   ;This is the pop server that matches your DID.
: fromuser=######_SubAccount
: disallow=all
: context=from-trunk
: canreinvite=nonat
: allow=g722&ulaw
</div>

=== Incoming tab ===

Adjust the '''register String''' with your sub-account credentials. It must be formated this way.

::'''Sub-account username''' : '''Sub-account Password''' @ '''VoIPmsPOP.voip.ms''' / '''Sub account username'''
<div style="margin-left:50px;
padding:5px;
font-family: Consolas, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace;
color: silver;
border-left: 6px solid rgb(208, 56, 45, 0.8);
box-shadow: 8px 6px 9px -2px #f2f2f2;
background-color: black;
width:58%;">

 ######_SubAccount:YourSubAccountPassword@montreal1.voip.ms/######_SubAccount
</div>

== Inbound Route ==
=== General tab ===
:'''[1]''': Go under '''Connectivity''' then '''Inbound Routes'''
:'''[2]''': Click on '''+ Add Inbound Route'''
::'''-''' '''Description''': Enter a description for this inbound route.
::'''-''' '''DID Number''': Enter your DID Number. ''(Without Hyphen, dot or parentheses)''
::'''-''' '''Set destination''': Choose the destination where you want to route the incoming call.
:'''[3]''': Click '''Save'''
:'''[4]''': Click '''Reload''' on the corner Right of the window.

== Outbound Routes ==
If you just install IncrediblePBX, you will find an outbound route named "default". You can adapt it to use the VoIP.ms route you have created.

:'''[1]''': Go under '''Connectivity''' then '''Outbound Routes'''
:'''[2]''': Where the outbound route named '''Default''', click on the '''Edit''' button. ''(Or you can create a new Outbound route by clicking on "+ Add Outbound Route")''

=== Route settings tab===
:'''[1]''': '''Route Name''': You can change the name of your default route if you need.
:'''[2]''': '''Route CID''': (Optional, you can leave it empty if you defined the caller ID directly in the trunk settings.
:: If you want to define a specific outbound caller ID Name and Number for all outbound calls that will use this outbound route.
:: Enter your CallerID Name and Number in the following format:
<div style="margin-left:50px;
padding:5px;
font-family: Consolas, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace;
color: silver;
border-left: 6px solid rgb(208, 56, 45, 0.8);
box-shadow: 8px 6px 9px -2px #f2f2f2;
background-color: black;
width:70%;">

 "CALLERID NAME" <##########>
</div>
<div style="margin-left:50px;
padding:8px;
border-left: 6px solid rgb(73, 111, 199, 0.8);
box-shadow: 5px 4px 4px 4px #f5f5f5;
background-color: rgba(73, 111, 199, 0.08);
width:70%;">

'''⚠️ IMPORTANT - Outbound CallerID''' 
* Entering outbound Caller ID Name, it must be in '''CAPITAL LETTERS'''. ''This will appears more clearly/visible on some devices.'' 
* You must '''NOT use any special characters'''. ''They will not be displayed and it prevents potential outbound call issues.'' 
* Do '''NOT exceed 15 characters'''. ''Traditional canadian providers will '''not show more than 15 characters'''. We suggest shrinking or adapt the name.'' 
* Spaces are allowed in a caller ID name but count as a characters. ''(do not exceed 15 chars. in total)''.
</div>

:'''[3]''': '''Trunk Sequence for Matched Routes''': Replace the current Trunk to the one we have edited. Eg: VoIPms-Registered. (Or then name you have entered.) Then delete the other trunks below by pressing the trash icon.

=== Dial Pattern tab ===

You can customize this section if you need specific rules matching your needs, such as a '''"prefix"''' to dial out through the trunk you have selected.
:''Eg: if you enter '''9''' on prefix section'', you will need to dial 9 following the matching pattern to make the call. The prefix will be removed when it will be send to the trunk.

::'''You can use the following patterns compatible for VoIPms in the colomn "[Match Pattern]"'''.

<div style="margin-left:50px;
padding:5px;
font-family: Consolas, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace;
color: silver;
border-left: 6px solid rgb(208, 56, 45, 0.8);
box-shadow: 8px 6px 9px -2px #f2f2f2;
background-color: black;
width:70%;">

{| style="background: inherit; color: silver;"
! scope=col style="text-align:left; width:25%;" | '''MATCH PATTERN COL'''
----
! scope=col style="text-align:left;" | ''Description''
----
|-
|NXXNXXXXXX || ''(North American phone number)''
|-
|1NXXNXXXXXX ||''(North American phone number with country code 1)''
|-
|4443 || ''(Echo test)''
|-
|4747 || ''(DTMF test)''
|-
|988 || ''(Health line)''
|-
|911 || ''(Emergency)''
|-
|822 || ''(CallerID playback)''
|-
|511 || ''(Weather service)''
|-
|411 || ''(Directory assistance)''
|-
|311 || ''(Non-emergency)''
|-
|211 || ''(Municipality line)''
|-
|00XX. || ''(Int. prefix, that uses the route set under the sub-account)''
|-
|011XX. || '' (Int. prefix, that uses the route set under the sub-account)''
|-
|033XX. || '' (Int. prefix, that will force using the '''Value''' route only for the call)
|-
|044XX. || '' (Int. prefix, that will force using the '''Premium''' route only for the call)
|}
</div>

:'''[4]''': Click '''Save'''

== Outbound SMS ==
An outbound SMS module can be added to Incredible PBX 2027 using the '''smsrouting FreePBX module''' and a PJSIP trunk.

The module adds a Connectivity → VoIP.ms SMS option to the FreePBX interface and allows outbound SMS messages to be sent through a VoIP.ms DID.

The installation instructions and configuration details, including the required Asterisk dialplan and the smsrouting FreePBX module, are available in the following VoIP-info.org forum thread: [https://www.voip-info.org/forum/threads/outbound-sms-freepbx-module.28789/#post-183772 Here]

File:VTScada-VoIP-EditDID.png

2026-09-15T23:11:29Z

Scomtois:

File:VTScada-VoIP-CreateSubAccountMenu.png

2026-09-15T22:55:17Z

Scomtois:

File:VTScada-VoIP-ManageDID.png

2026-09-15T22:20:41Z

Scomtois:

File:VTScada-VoIPms DIDROUTING.png

2026-09-15T22:19:15Z

Scomtois: