TechNote (Archived)

Unable to connect to a meeting after upgrading from Breeze 4.x or 5.x to Connect 6

Issue

---

After upgrading from Breeze 4.x or 5.x to Connect 6, you find users are unable to connect to a meeting.

Reason

---

The RTMP sequence format is changed in Connect Professional 6, causing the connection to fail. The RTMP sequence is the URI used to connect users to a Connect Professional meeting.

Solution

---

In order to fix the problem, you need to update your custom.ini file located in the c:\breeze\ folder.

1. Open the c:\breeze\custom.ini file.
2. Find the current RTMP_SEQUENCE sequence in the custom.ini file.
   
   Here is an example of what a default 4.x/5.x RTMP_SEQUENCE looks like:
   RTMP_SEQUENCE=rtmp://edge-host:1935/?rtmp://host:1935/,rtmpt://edge-host:443/?rtmp://host:1935/
3. Edit your current RTMP_SEQUENCE line:
   1. Change all instances of the text "edge-host" to "external-host" in the RTMP_SEQUENCE line.
   2. Change all instances of "host:1935" to "localhost:8506" in the RTMP_SEQUENCE line.
   Here is an example of what a default 6.x RTMP_SEQUENCE looks like after the changes:
   RTMP_SEQUENCE=rtmp://external-host:1935/?rtmp:// localhost:8506/
   
   Your RTMP_SEQUENCE may have more sequences, each sequence is seperated by a comma (,). You must make sure you update every sequence within the RTMP_SEQUENCE, as follows:
   
   RTMP_SEQUENCE=rtmp://external-host:1935/?rtmp:// localhost:8506/,rtmp://external-host:443/?rtmp:// localhost:8506/
4. Save the custom.ini file and restart all Connect services.

Note: If you have users connecting to meetings on other ports, then refer to Configuring Connect Professional to listen on additional ports in Connect 6 and 5.x (TechNote 2405470e).

Search Support

---