[OpenSIPS-Users] tm detached timer error

[Ovidiu Sas]

In this case the CRITICAL should be turned into a NOTICE or WARNING.
And maybe a little more verbosity (type of reply ignored for
transaction with Call-ID) so it can be correlate with captured SIP
traffic.


Regards,
Ovidiu Sas

On Fri, Apr 3, 2009 at 12:33 PM, Bogdan-Andrei Iancu
<bogdan at voice-system.ro> wrote:
> Hi Jeff,
>
> Even if it is a CRITICAL message, you can simply ignore it.
>
> This happens when there are huge delays in the processing. Typically it
> means the transaction was completed (in a way or the other) and some
> late reply/requests are received  and tried to do something more on the
> transaction:
> Ex:
> 1) INVITE is received and sent out; transaction is created and in timer
> 2) no reply, so the transaction is removed from timer (as timeout occurs)
> 3) replies comes, find the transaction in WAIT (wait for deletion) state
> and try to arm again the FR_INV_TIMER_LIST (id 1). -> err message
>
> Again, just ignore them.
>
> Regards,
> Bogdan
>
> Jeff Pyle wrote:
>> Hello,
>>
>> My log is full of messages like this today:
>>
>> CRITICAL:tm:set_timer: set_timer for 1 list called on a "detached" timer --
>> ignoring: 0xa82f5930
>>
>> Is there a common cause for this?  I discovered today I might be facing a
>> Cisco switch that's dropping packets like they're hot.  Any chance packet
>> loss might cause this?
>>
>> Thanks,
>> Jeff
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>