PRI / Zaptel B0rked on 1.2.9.1?

Asterisk Asterisk Support
1

Hi Everyone,

This morning I upgraded Asterisk from 1.2.7.1 to 1.2.9.1 along with libpri to version 1.2.3 and Zaptel to 1.2.6. Then stopped and restarted all the Asterisk and Zaptel components. Service resumed as usual but after about 30minutes the console was filled with errors and the PRI ZAP channel (Digium TDM 2 Span) stopped answering calls. The errors where as follows:

pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner

Forcing restart of channel 0/9 on span 2 since channel reported in use

Channel 0/9, span 2 received AOC-E charging 0 units

channel.c:787 channel_find_locked: Avoided initial deadlock for ‘0x74c570’, 10 retries!

At first I thought it might be a problem with my telco provider (BT) but I decided to downgrade to 1.2.7.1 and everything works fine like it did before the upgrade. Im just wondering if something to do with PRI / Zaptel has been broken in the update?. Any Ideas? I really need this update as it appears to fix a bug that I have with IAX2 which stops listening to frames and timeouts all calls even when the latency is averaging 5ms.

Thanks

Chris Teesdale
I.T. Development / I.P Telephony Development
Philips®
Tel : 01325 384394 ex 221
Email : cjt at philips.org.uk

2

Rebuild_zaptel

and all that goes with it

are you runing centos 4.3 ?
kernal 2.6?

got spinlock issue?

3

Nah I can’t remember anything about a spinlock. It was seriously broke and was saying :

pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner

Constantly, I’m using Mandrake 2006 2.6 Kernel. After hours tonight I’ll try rebuilding everything from scratch after a make clean, lib pri, zaptel, asterisk.