On Tue, 2009-05-12 at 15:40 -0400, Dale Worley wrote: > Looking at the call with call-id > [email protected]: The 408 is generated as a > response to the transaction with branch value > z9hG4bK-sipXecs-005af41636c06aaada4aa2ee0579e725094e~bd5b5f42556399401f93a2ee6228c94b. > It is not clear how this comes about, because the initial INVITE is at > 16:54:41.372606, and the sending transaction receives a 100 response at > 16:54:41.373493. Once the transaction receives the 100, it should wait a > long time before timing-out. > > This INVITE is also sent on to 65.247.227.196:2878;transport=TCP, with > ultimate destination > sip:[email protected]:50932;rinstance=f08973a393213329;transport=TCP. > That INVITE gets no response, and it's an important question to find out > why. > I don't agree.
Without compiling for transaction debug, it's not completely clear, but I think the timeout actually occurs on the branch z9hG4bK-sipXecs-005d18d17fae0a8fc21a92020a7ec9900e27 When this branch times out, it should roll to the UDP value returned by SipSrvLookup::servers. The 408 seen at sipXproxy.log::8878 is the final response on the branch Dale mentions but it is _not_ the branch that actually timed out. -Kathy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
