Today at the Interop 2007 Las Vegas Hot Stage event we discovered a strange, but explainable behavior with OpenSER.

If you start OpenSER using fork=no, TCP and TLS support will not get started even though the messages printed out makes it seem like they should be working. Unspin on IRC pointed out the fact that in fork=no the separate process(es) of TCP and TLS would not (could not?) get spawned, leaving only UDP support.

Granted not everyone will want/need to run in fork=no mode, however being that we are in a test situation here at Interop, running without forking was an easy way for us to see ‘under the hood’ with minimal effort.

Tomorrow, we will get into the testing of Wireless VoIP scalability using cool little RF chambers and test equipment provided by Veriwave and determining the interoperability of SRTP between vendors.

Related Posts:
Does Your Linksys SPA-942 Back Light Blink, When Running Asterisk 1.4?
SER/OpenSER Configuration Wizard
OpenSER and Asterisk Training
Astricon 2007 CodeZone Plans
OpenSER Code Hack: Calling Stored Procedures