On 13.06.13 15:41, Alejandro Imass wrote:
> On Thu, Jun 13, 2013 at 9:17 AM, Ian FREISLICH <[email protected]> wrote:
>> Hi
>>
>> After upgrding from 1.8.20.x to 1.8.22.0, my IAX2 extensions and
>> trunks no longer remain registered.
>>
>> I notice the following message:
>> [2013-06-13 14:56:57] ERROR[91354] chan_iax2.c: Timer failed acknowledge
>> [2013-06-13 14:56:57] ERROR[91354] chan_iax2.c: Timer failed acknowledge
>>
>> shortly after which:
>> [2013-06-13 14:58:01] NOTICE[91354] chan_iax2.c: Peer 'XXXX' is now 
>> UNREACHABLE! Time: 194
>> [2013-06-13 14:58:01] NOTICE[91354] chan_iax2.c: Peer 'XXXX' is now 
>> UNREACHABLE! Time: 194
>> [2013-06-13 14:58:01] NOTICE[91354] chan_iax2.c: Peer 'XXX' is now 
>> UNREACHABLE! Time: 195
>> [2013-06-13 14:58:01] NOTICE[91354] chan_iax2.c: Peer 'XXX' is now 
>> UNREACHABLE! Time: 195
>>
>> After putting the following line in modules.conf IAX2 trunks and
>> extensions remain connected:
>>
>> noload => res_timing_kqueue.so
>>
> 

Thanks for the reports, there is indeed something wrong with
res_timeing_kqueue, I'll update the ports shortly to disable
building/installing the module by default until we can analyze what is
wrong exactly.

Florian


Attachment: signature.asc
Description: OpenPGP digital signature

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Asterisk-BSD mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bsd

Reply via email to