My understanding is that Twilio for Alarm Notification and the VTScada Thin Client are part of the same server so having both configured should still show up as on service. You'll want to make sure that VTScada is the only service listening on the port you are using.
On my PC Running Command Prompt as an Admin:
C:\Windows\System32>netstat -ano
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 31064
TCP [::]:80 [::]:0 LISTENING 31064
C:\Windows\System32>tasklist /FI "PID eq 31064"
Image Name PID Session Name Session
========================= ======== ================ =========== ============
VTS.exe 31064 Console 5 273,928 K
My understanding is that Twilio for Alarm Notification and the VTScada Thin Client are part of the same server so having both configured should still show up as on service. You'll want to make sure that VTScada is the only service listening on the port you are using.
On my PC Running Command Prompt as an Admin:
````
C:\Windows\System32>netstat -ano
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 31064
TCP [::]:80 [::]:0 LISTENING 31064
````
````
C:\Windows\System32>tasklist /FI "PID eq 31064"
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
VTS.exe 31064 Console 5 273,928 K
````
Trihedral Engineering Ltd.