[asterisk-bugs] [Asterisk 0010928]: E&M Wink stops responding after originating about 500 calls
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Feb 14 12:17:16 CST 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=10928
======================================================================
Reported By: SirWhit
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 10928
Category: Channels/chan_zap
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: 1.4.12.1
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 10-09-2007 12:35 CDT
Last Modified: 02-14-2008 12:17 CST
======================================================================
Summary: E&M Wink stops responding after originating about
500 calls
Description:
Able to make about 500 outgoing calls via Manager Originate. Using
ZapBarge, I can hear the calls being launched and DTMF digits dialing on
the trunk. At approximately 500 calls, I'll hear a telco message saying
that not enough digits have been dialed.
Next and all future calls goes into a fast busy and the e&m trunks are
useless until asterisk is restarted.
Setup:
2 x E&M Wink trunks on a TE410p Digium Card
Using Manager API to Originate calls to E&M Wink trunks.
zaptel.conf
-----------
span=1,0,0,d4,ami
span=2,1,0,d4,ami
e&m=1-48
loadzone=us
defaultzone=us
zapata.conf
-----------
group = 2
signalling= em_w
switchtype = national
immediate=no
overlapdial=yes
busydetect=no
callprogress=no
rxgain= 0.0
txgain= 0.0
usecallerid => no
context = outgoing
channel =>1-23
Telco not seeing any issue on their end.
Digium support logged in and saw nothing wrong with the card.
No errors are reported from asterisk either in CLI or
/var/log/asterisk/messages
======================================================================
----------------------------------------------------------------------
file - 02-14-08 12:17
----------------------------------------------------------------------
After examining the code the remembering previous conversations/issues I
believe the fault that caused this has been corrected and the issue should
be fixed.
Issue History
Date Modified Username Field Change
======================================================================
02-14-08 12:17 file Status new => resolved
02-14-08 12:17 file Resolution open => no change
required
02-14-08 12:17 file Assigned To => file
02-14-08 12:17 file Note Added: 0082255
======================================================================
More information about the asterisk-bugs
mailing list