FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a versatile software implementation that runs on any commodity hardware. From a Raspberry PI to a multi-core server, FreeSWITCH can unlock the telecommunications potential of any device.
When freeswitch is running on the public network, sip can be connected, and ext-rtp-ip is configured as the public ip address, but the video and voice cannot be connected #2229
Our freeswitch uses docker to run on a server with fixed IP mapping, and uses web and android to connect freeswitch through the public network. web and android are in the same LAN. We have configured ext-rtp-ip and ext-sip-ip public ip addresses in freeswitch. Now, you can call android from the web side, but there is no video and sound.
The debugging logs of freeswitch show that sdp information uses public ip addresses. We use tcpdump on the server to capture udp packets and find that the data is sent from freeswitch's LAN ip address to the Intranet ip address of the web end. The captured packet logs are as follows :(192.168.2.202 is freeswitch's Intranet ip address, 192.168.201.19 is the Intranet ip address of the web side).
tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
16:15:15.392172 IP (tos 0x0, ttl 64, id 43423, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:16.392174 IP (tos 0x0, ttl 64, id 43607, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:17.412172 IP (tos 0x0, ttl 64, id 43808, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:18.412186 IP (tos 0x0, ttl 64, id 44006, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:19.432172 IP (tos 0x0, ttl 64, id 44198, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:20.432178 IP (tos 0x0, ttl 64, id 44417, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:21.432173 IP (tos 0x0, ttl 64, id 44484, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:22.452172 IP (tos 0x0, ttl 64, id 44606, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:23.452172 IP (tos 0x0, ttl 64, id 44686, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:24.452172 IP (tos 0x0, ttl 64, id 44868, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:25.472174 IP (tos 0x0, ttl 64, id 45025, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:26.492176 IP (tos 0x0, ttl 64, id 45074, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:27.512170 IP (tos 0x0, ttl 64, id 45140, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:28.512171 IP (tos 0x0, ttl 64, id 45243, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
16:15:29.532169 IP (tos 0x0, ttl 64, id 45381, offset 0, flags [DF], proto UDP (17), length 184)
192.168.2.202.30620 > 192.168.201.19.55024: UDP, length 156
Both "ext-rtp-ip" and "ext-sip-ip" are public ip in internal.xml and external.xml. Modify "rtp-start-port" and "rtp-end-port" in switch.conf.xml,open this port range on the firewall.
Our freeswitch uses docker to run on a server with fixed IP mapping, and uses web and android to connect freeswitch through the public network. web and android are in the same LAN. We have configured ext-rtp-ip and ext-sip-ip public ip addresses in freeswitch. Now, you can call android from the web side, but there is no video and sound. The debugging logs of freeswitch show that sdp information uses public ip addresses. We use tcpdump on the server to capture udp packets and find that the data is sent from freeswitch's LAN ip address to the Intranet ip address of the web end. The captured packet logs are as follows :(192.168.2.202 is freeswitch's Intranet ip address, 192.168.201.19 is the Intranet ip address of the web side).
sdp information sent by the web end:
sdp information about freeswitch:
sdp information sent by android:
sdp information about freeswitch:
Other log information: