It's been missing a break there for ~4 years and instead using the 8k max_ms values(the ptime_div value is the same).

This condition should NEVER be hit, but in case the started thread is unable to locate itself in the EVENT_DISOATCH_QUEUE_THREADS array, it's best to return null here and kill the unexpected event thread rather than segfault FS by writing outside of the bounds of the EVENT_DISPATCH_QUEUE_RUNNING array.

More explicit and defensive code so if the init fails we know we handling this pointer safely, because  rc_config_init will free the pointer if there was a problem, but it will not set the pointer to NULL.

Appears to have been a copy paste error because this doesn't do what the api claims, and it also leaks the reference to the new node.

FS-5453 --resolve this is a different issue, we just have to hangup the loopback channel so the loopback and the sip don't both execute the extension

FS-5402 --resolve the problem is ent originate has many channels and many causes to parse so we need to check it against all the causes