But as a result of the upgrade, some of the settings seem to have reverted to their default vaules. The following fixed ICE error 1007:
- Edit the file /opt/freeswitch/conf/sip_profiles/external.xml on the machine which hosts the BBB server: say,
sudo vim /opt/freeswitch/conf/sip_profiles/external.xml
- Locate the lines
<param name="ext-rtp-ip" value="$${local_ip_v4}"/>
<param name="ext-sip-ip" value="$${local_ip_v4}"/>
- Replace with:
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/>
<param name="ext-sip-ip" value="$${external_sip_ip}"/>
- Restart BigBlueButton:
sudo bbb-conf --restart --setip <external hostname>
Of course, this fix will only work if all the other steps in
http://docs.bigbluebutton.org/2.2/configure-firewall have also been followed. This includes defining
external_rtp_ip and external_sip_ip in /opt/freeswitch/conf/vars.xml . But in my case, the customised /opt/freeswitch/conf/vars.xml was not changed as a result of the upgrade; /opt/freeswitch/conf/sip_profiles/external.xml was.
P.S. I inserted the following into /etc/bigbluebutton/bbb-conf/apply-config.sh to hopefully prevent the above problem from reoccuring after the next upgrade:
echo Patching /opt/freeswitch/conf/sip_profiles/external.xml
patch --forward /opt/freeswitch/conf/sip_profiles/external.xml << '_ENDOFPATCH_'
@@ -69,8 +69,8 @@
-->
<param name="rtp-ip" value="$${local_ip_v4}"/>
<param name="sip-ip" value="$${local_ip_v4}"/>
- <param name="ext-rtp-ip" value="$${local_ip_v4}"/>
- <param name="ext-sip-ip" value="$${local_ip_v4}"/>
+ <param name="ext-rtp-ip" value="$${external_rtp_ip}"/>
+ <param name="ext-sip-ip" value="$${external_sip_ip}"/>
<param name="rtp-timeout-sec" value="300"/>
<param name="rtp-hold-timeout-sec" value="1800"/>
<param name="enable-3pcc" value="proxy"/>
_ENDOFPATCH_