Let me mention what I forgot in my first message: There are actually two symptoms, which in most instances happen together: One is that a phone rings indefinitely, the other is that a call is not answerable on a phone on which it should be answerable.
On Tue, 2009-11-10 at 08:06 -0500, Scott Lawrence wrote: > I propose that we divide our response to all this into three separate > work items (issues): one for each of #2, #3, and #4 below. Yes, #1 and #5 together are just advice to phone vendors. The remaining items are separable. Given the complexity of the situation, they are all needed to alleviate the symptoms in various circumstances. > #2 seems like a reasonable idea, and might help. I would make that > extra time more like 5 seconds - we got into this can of worms because > things are not responding in reasonable times: let's not ask for a new > race condition. Ah, yes. > This seems perfectly safe, and should be as easy to change as anything > in SipTransaction ever is (that is to say, not very). Fortunately, we're starting to develop a knowledge base regarding SipTransaction. > This should be a very easy change, and we should do this one first. I > strongly suspect that this alone will solve the problem that Mark first > reported (which doesn't mean that the other changes above are not also > worthwhile improvements). Yes, we understand that code well. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
