Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleEngineering | Voiceware | TCP/IP Psip-PMS Setup

Voiceware blocks all TCP/IP connections including any made from Psip-PMS.

This results in no PMS being able to use TCP/IP to connect to any Voiceware system.

You’ll want to first confirm who is the client and who is the server. There’s a known bug in Voiceware version (needToFIndVersion) where Voiceware can only operate as (client or server, need to confirm).

For Voiceware 1.X, 2.X, 3.X run these commands:

iptables -I INPUT -p tcp --dport -j ACCEPT
iptables -I trusted -s -j ACCEPT
service iptables save
or
/etc/init.d/iptables save

For Voiceware 4.X run these commands:

firewall-cmd --permanent --new-zone=pms
firewall-cmd --permanent --zone=pms --add-port /tcp
firewall-cmd --permanent --zone=pms --add-source=
firewall-cmd --reload

To test you can also run these commands:

firewall-cmd --get-active-zones
firewall-cmd --list-all
firewall-cmd --list-all-zones

To test the ports locally on Voiceware you can run these commands:

[root@vw-00301802af83 ~]# netstat -tuwln | grep -i
tcp 0 0 0.0.0.0:5555 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5556 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3551 0.0.0.0:* LISTEN
[root@vw-00301802af83 ~]#

[root@vw-00301802af83 ~]# telnet 127.0.0.1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@vw-00301802af83 ~]#

Troubleshooting with tcpdump and wireshark:

tcpdump -envi port

or

tshark -i -f 'tcp port '

(If you want to use tshark you will have to install tshark it does not come pre-installed like tcpdump does)

Here is an example of a capture from a site where the issue was the connection was closing and reopening again multiple times in the same second.

We can see the TCP/IP flow and where the PMS vendor was sending us a FIN to end communication.

SYN TO

09:36:57.406927 50:6b:8d:8c:35:65 > c4:24:56:c7:a3:10, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 22567, offset 0, flags [DF], proto TCP (6), length 60)10.0.90.60.35194 > 208.98.218.10.telelpathstart: Flags [S], cksum 0x0ed8 (incorrect -> 0xea4d), seq 129419826, win 29200, options [mss 1460,sackOK,TS val 43740008 ecr 0,nop,wscale 7], length 0

SYN-ACK FROM

09:36:57.408496 c4:24:56:c7:a3:10 > 50:6b:8d:8c:35:65, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 122, id 35166, offset 0, flags [DF], proto TCP (6), length 52)208.98.218.10.telelpathstart > 10.0.90.60.35194: Flags [S.], cksum 0xd474 (correct), seq 1528152534, ack 129419827, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

ACK TO

09:36:57.408533 50:6b:8d:8c:35:65 > c4:24:56:c7:a3:10, ethertype IPv4 (0x0800), length 54: (tos 0x0, ttl 64, id 22568, offset 0, flags [DF], proto TCP (6), length 40)10.0.90.60.35194 > 208.98.218.10.telelpathstart: Flags [.], cksum 0x0ec4 (incorrect -> 0x1463), ack 1, win 229, length 0

FIN-ACK FROM

09:36:57.410130 c4:24:56:c7:a3:10 > 50:6b:8d:8c:35:65, ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 122, id 35167, offset 0, flags [DF], proto TCP (6), length 40)208.98.218.10.telelpathstart > 10.0.90.60.35194: Flags [F.], cksum 0x1145 (correct), seq 1, ack 1, win 1026, length 0

ACK TO

09:36:57.410595 50:6b:8d:8c:35:65 > c4:24:56:c7:a3:10, ethertype IPv4 (0x0800), length 54: (tos 0x0, ttl 64, id 22569, offset 0, flags [DF], proto TCP (6), length 40)10.0.90.60.35194 > 208.98.218.10.telelpathstart: Flags [.], cksum 0x0ec4 (incorrect -> 0x1462), ack 2, win 229, length 0

FIN-ACK TO

09:36:57.428685 50:6b:8d:8c:35:65 > c4:24:56:c7:a3:10, ethertype IPv4 (0x0800), length 54: (tos 0x0, ttl 64, id 22570, offset 0, flags [DF], proto TCP (6), length 40)10.0.90.60.35194 > 208.98.218.10.telelpathstart: Flags [F.], cksum 0x0ec4 (incorrect -> 0x1461), seq 1, ack 2, win 229, length 0

ACK FROM

09:36:57.430077 c4:24:56:c7:a3:10 > 50:6b:8d:8c:35:65, ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 122, id 35168, offset 0, flags [DF], proto TCP (6), length 40)208.98.218.10.telelpathstart > 10.0.90.60.35194: Flags [.], cksum 0x1144 (correct), ack 2, win 1026, length 0

Expand
titleSet NAT and Qualify

From the command line issue the command

psql -Upostgres asgi_cc -c"UPDATE devices SET nat=true, qualify='yes';"

If it works you should see a number of devices updated.

image-20240530-170126.pngImage Added
Expand
titleHunter | Network Metrics | Bandwidth

Bandwidth is the amount of information that can be transmitted, measured in bits per second (bps), or some multiple thereof. When monitoring, you need to distinguish between the nominal data link/Ethernet bit rate, the throughput of a link at Layer 3, and the throughput available to an application.

Bandwidth for audio depends on the sampling frequency (Hertz) and bit depth of each sample. For example, telecommunications links are based on 64 Kbps channels. This was derived through the following calculation:

The voice frequency range is 4000 Hz. This must be sampled at twice the rate to ensure an accurate representation of the original analog waveform.
The sample size is 1 byte (or 8 bits). Therefore, 8 KHz x 8 bits = 64 Kbps.
For VoIP, bandwidth requirements for voice calling can vary, but allowing 100 Kbps per call upstream and downstream should be sufficient in most cases.

Bandwidth required for video is determined by image resolution (number of pixels), color depth, and the frame rate, measured in frames per second (fps).

...