Sorry if I wasn't clear. There is actually no change in this behavior from 2.1.2. There is only a change in your venue configuration.
If you configure your venue to use static addressing, the bridges will start the way you've seen them start before. Tom Jeremy Mann wrote: > Thomas D. Uram said: > >>It looks like you recreated the venues without static addressing, so >>there are no streams in the venue to bridge. If someone enters the >>venue and wants to send audio or video, streams would be allocated and >>the bridge server should start bridges for those streams. This is, >>however, different than you worked previously. If you set up your >>venues for static addressing, the bridges should get started when you >>start the bridge server, as previously. > > > I think I understand. The BridgeServer doesn't do anything until it > detects audio/video streams from a client. Why the change from 2.1.2? > > > >
