Once you have configured the publishing point to listen for these connections you can set it up so that it is either initiated by the client (when they push "start encoding") or on the server side (ready... 1,2,3.. go...).  Many of these decisions are driven by security; ie: can they just start it any time they want?  Or do we initiate the connection at exactly 11:59; for example....

OH NO!!!  I see the error: Server Busy !!!!

If everything seems to be fine and you are getting "server busy" error remember to check and make sure that you have pushed "start encoding" from the client side.  No signal, no stream, and this has happened more than once.  You can view it locally but not over the Internet.