< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
Hi!
I've finally found the cause of this problem. It's caused by the TU failing to respond to a CANCEL-request in time. When timer Trying fires mNextTransmission is deleted after 100 Trying is sent. If a retransmission of the CANCEL-request is then received from the wire there will be nothing around to respond with. Steps to reproduce: resiprocate/peer <---INVITE 100---> 180---> <---CANCEL TU does not respond 100--> <---CANCEL Adding a fix similar to that in processServerInvite() (lines 1652-1656, tag 1.8.5) seems to fix the issue, but I'm not sure if this is the correct way. Regards, Krister Från: Krister Jarl
Skickat: den 21 november 2012 09:41 Till: Scott Godin Kopia: resiprocate-users@xxxxxxxxxxxxxxx Ämne: Re: [reSIProcate-users] TransactionState assert, sendCurrentToWire Hi Scott,
I'm afraid not. Regards, Krister Från: slgodin@xxxxxxxxx [slgodin@xxxxxxxxx] för Scott Godin [sgodin@xxxxxxxxxxxxxxx]
Skickat: den 20 november 2012 18:17 Till: Krister Jarl Kopia: resiprocate-users@xxxxxxxxxxxxxxx Ämne: Re: [reSIProcate-users] TransactionState assert, sendCurrentToWire Hi Krister,
Scott
On Tue, Nov 20, 2012 at 4:34 AM, Krister Jarl
<kj@xxxxxxxxxxx> wrote:
|