- Joined
- Oct 18, 2018
- Messages
- 5
- Reaction score
- 0
We are adding satellite office on existing 3cx hosted on AWS. Log files have this info:
ERR | 20190131-172550.047 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.85:10010
ERR | 20190131-173251.670 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-173251.701 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-182048.308 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-183359.983 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10092
ERR | 20190131-203423.475 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10094
ERR | 20190131-203505.213 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10096
192.168.1.xx are phone IP. On firewall i have created a policy where traffic from SBC IP to AWS public IP is allowed for any port and on AWS i have opened ports mentioned on documentation.
Can somebody explain why is this happening and what might be the solution?
SBC is installed on Hyper-V dedicated Windows 10 computer. No joined to domain or anything. No other functions in it.
ERR | 20190131-172550.047 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.85:10010
ERR | 20190131-173251.670 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-173251.701 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-182048.308 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10090
ERR | 20190131-183359.983 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10092
ERR | 20190131-203423.475 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10094
ERR | 20190131-203505.213 | 3CXTunnel | TUNL | 7392 | Bridge.cpp:712 | Has no registered RTP session for local destination 192.168.1.92:10096
192.168.1.xx are phone IP. On firewall i have created a policy where traffic from SBC IP to AWS public IP is allowed for any port and on AWS i have opened ports mentioned on documentation.
Can somebody explain why is this happening and what might be the solution?
SBC is installed on Hyper-V dedicated Windows 10 computer. No joined to domain or anything. No other functions in it.