[asterisk-users] E&M Wink and T4xxP losing ability to dial
Steve Totaro
stotaro at totarotechnologies.com
Tue Oct 9 11:56:42 CDT 2007
A critical lesson I learned was not to rely to heavily on the AMI,
especially when there are other ways of doing the same thing that are
just as simple.
I suggest, rather than using AMI originate, mv or ftp .call files.
Thanks,
Steve
Whit Thiele wrote:
>
> Still having no luck with this scenario. Has anyone else experienced
> problems with e&m wink lines?
>
> I'm thinking that there could be problems with the timing settings in
> zapata.conf, but documentation is pretty light.
>
> How could the telco not be receiving enough digits when it works for 500
> calls...?
>
> Anyone have any similar experiences/ possible solutions?
>
> Whit
>
>
>
>
> On 10/2/07, *Whit Thiele* <whitneythiele at gmail.com
> <mailto:whitneythiele at gmail.com>> wrote:
>
> Hey folks,
>
> I'm pulling my hair out on this situation and would welcome some advice:
>
> I'm using the AMI Manager to Originate calls onto 2 E&M wink T1
> circuits via a T4XXP card from Digium.
>
> Everything works fine for about 600(+/- 50) calls then the Manager
> is suddenly unable to launch calls. Using ZapBarge to listen to the
> channels themselves you can hear the dtmf digits being dialed, but
> then either there is dialtone (again), or a fast busy signal.
>
> I've also noticed(via ZapBarge) that before the T1 seizure that the
> call launched will immediately go to an automated message claiming
> that not enough digits have been dialed. The rest of the T1's become
> useless right after it.
>
> Once the T1's get into this state, even trying to launch a call
> directly through the dialplan experiences the same behavior. Its
> like the T1 has locked up.
>
> The telco provider (quest) claims they aren't even seeing the digits
> placed on the circuit. They say they see the channel being grabbed,
> but no digits appearing.
>
> Verbose and debug show nothing out of the ordinary.
>
> Could this be an issue with the Digium card? Both T1's experience
> the same behavior at the same time. I've tried some different
> settings such as callprogress=yes and busydetect=no but nothing has
> helped. Only restarting asterisk seems to allow another 600 calls to
> be processed.
>
> I'm using the latest asterisk release version 1.4.11 and zaptel
> 1.4.5.1 <http://1.4.5.1>
>
> Regards,
>
> Whit
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
More information about the asterisk-users
mailing list