asterisk users - Sep 2004 - PRI issue

Hi,

 

I recompiled asterisk today from CVS and I've been having a number of
problems, I've read the deadlock page on the wiki and some of it sounds
like that, however, the latest issue we're having it that sometimes
Asterisk doesn't seem to know the PRI channel has dropped, and assumes
it's still busy. However, that same channel can be used to make an
outgoing call?!

 

Has anyone experienced anything similar?

 

Regards,

 

Ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040908/aadfb566/attachment.htm

Ben,

I ran into a similar issue on the 8/31 cvs, except it was backwards.
Outbound calls would report a busy on the channel selected, yet a few
minutes later the channel would be used for an inbound call.  I had to
revert back to my previous checkout from 8/16 to resolve the issue.  The
problems didn't break the channels completely, it happened probably
every 5-10 minutes.

Brian D'Arcy

________________________________________
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Ben
Merrills
Sent: Wednesday, September 08, 2004 7:51 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] PRI issue

Hi,

I recompiled asterisk today from CVS and I've been having a number of
problems, I've read the deadlock page on the wiki and some of it sounds
like that, however, the latest issue we're having it that sometimes
Asterisk doesn't seem to know the PRI channel has dropped, and assumes
it's still busy. However, that same channel can be used to make an
outgoing call?!

Has anyone experienced anything similar?

Regards,

Ben

I think this issues stems from the (in my case) wct4xxp driver. When
updating libpri, I also updated zaptel, however, I'm unsure if I
installed it correctly (i.e. updated to the newly compiled version).

After stopping asterisk, doing rmmod wct4xxp, make install on zaptel and
then restarting asterisk, so far, it seems to be working.

I'm not 100% sure this is the problem, but it would seem this resolved
the issue... time will tell :)

Cheers,

Ben

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Brian
D'Arcy
Sent: 08 September 2004 16:34
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] PRI issue

Ben,

I ran into a similar issue on the 8/31 cvs, except it was backwards.
Outbound calls would report a busy on the channel selected, yet a few
minutes later the channel would be used for an inbound call.  I had to
revert back to my previous checkout from 8/16 to resolve the issue.  The
problems didn't break the channels completely, it happened probably
every 5-10 minutes.

Brian D'Arcy

________________________________________
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Ben
Merrills
Sent: Wednesday, September 08, 2004 7:51 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] PRI issue

Hi,

I recompiled asterisk today from CVS and I've been having a number of
problems, I've read the deadlock page on the wiki and some of it sounds
like that, however, the latest issue we're having it that sometimes
Asterisk doesn't seem to know the PRI channel has dropped, and assumes
it's still busy. However, that same channel can be used to make an
outgoing call?!

Has anyone experienced anything similar?

Regards,

Ben


_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users