danbarua
commented
9 years ago Hi @padmanabanravikumar , I am on the fence as to whether we ought to remove the response timeout code altogether (you will see that it is marked with the [Obsolete] attribute in the codebase.)
However, if you are using database logging with NLog, then perhaps you might benefit from wrapping your database logging in an async target: https://github.com/nlog/NLog/wiki/AsyncWrapper-target This will keep the NEventSocket worker threads from blocking and is generally worth doing if your log writes are going to be non-trivial.
Since working with FreeSwitch can involve a lot of trial and error, NEventSocket can be quite chatty with its logs to give you as much information as possible, you might also want to filter out Trace and Debug level logs from going to the DB.
padmanabanravikumar
"No Auth Request received within the specified timeout of 00:00:05" exception thrown when using NLog with database logging. If i remove NLog then everything works fine.
var socket = new InboundSocket(host, port, timeout);
await socket.Messages.Where(x => x.ContentType == ContentTypes.AuthRequest) .Take(1) .Timeout( socket.ResponseTimeOut, Observable.Throw(
new TimeoutException(
"No Auth Request received within the specified timeout of {0}.".Fmt(socket.ResponseTimeOut))))
.Do(_ => Log.Trace(() => "Received Auth Request"), ex => Log.ErrorException("Error waiting for AuthRequest.", ex))
.ToTask();
In these statements, If there is no delay in execution between these two statements it just works fine. and if there is a delay executing the second statement then it always fails.
for example, if we add the "System.Threading.Thread.Sleep(50);" in between the above two statements then second statement always fails and throws "No Auth Request received within the specified timeout of 00:00:05" exception.