similar to: Zaptel connectivity issues

Displaying 20 results from an estimated 10000 matches similar to: "Zaptel connectivity issues"

2009 May 20
1
DAHDI fun and games
Hi Listers, I'm running 1.4.25-rc1 on opensuse 11.0 with dahdi-linux-2.1.0.3, dahdi-tools-2.1.0.2, libpri-1.4.7 and snapdsp.0.0.2. Incoming calls work fine. Outgoing calls made directly (exten => s,1,Dial(DAHDI/G1) then number work fine. The problem I have is trying to let Asterisk make the call (exten => s,1,Dial(DAHDI/G1/5551212,,r). If I use "m" (moh) the
2009 Mar 12
1
Outgoing call drops
Greetings Listers, I'm running 1.4.21.2 on SUSE 11.0 with and zaptel 1.4.12.1 on a TDM400P. Most of my calls work great, but occasionally we try to connect to a customer or vendor external conference call and the call will drop after 60-65 seconds unless I have an Answer before the Dial in the dialplan. Isn't this solution a hack and what would be a better one?
2009 Apr 03
1
conference calling
Greetings listers. I'm running asterisk 1.4.21.2 on SUSE 11.0 using Polycom 501 phones. My outgoing connections are Zapata using a TDM401P. For the most part I can make and receive calls fine except for these 3 issues: 1. When I call an external conference, the call never bridges and hangs up after 60-90 seconds. 2. When I call another number there is a
2009 Aug 27
2
POTS supervision with DAHDI in 1.4 releases
Greetings, This may be a dumb question, but here goes. When I was on 1.4.21.2 using Zaptel, I had (at least as far as I could tell) access to line supervision on my POTS lines using a TDM400P/TDM410P. Since upgrading to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I've only been able to duplicate the success of the 1.4.21 functionality once. To test what I'm talking
2009 Apr 16
1
Connection to non-human numbers
Greetings listers, I've got 1.4.21.2 using Polycom 501 phones and Zap lines. Most of my calls come in and go out fine with the exception of Mechanized answering devices. When I call my 401K plan (1-800-777-401K) the call will last exactly one minute. The call never bridges, so even though the connection is made, Asterisk hangs up at the end of the Dial command.
2009 Mar 10
1
Odd occurrence
Greetings listers, I am running Asterisk 1.4.21.2 on Suse 11.0 on a Dual Processor Dell Poweredge 1650. I recently attempted to update the BIOS and now have this happen: When the machine starts up, Asterisk runs fine. When I do a large wget or scp, the local SIP to SIP quality goes to heck in a handbasket. The only resolution I've found so far is to completely
2010 Apr 16
1
incoming ghost call
Hello asterisk users... We are having a little problem in our installation, we are using Asterisk 1.4.21.2 and zaptel 1.4.11 with a Digium TDM410P (3FXO + 1FXS), the problem is that when we disconnect the line from any of the fxo ports, we receive an incoming ghost call (using zap/x channel) it rings on the phone but we cant hear nothing...it's always doing the same everytime we disconnect
2009 May 15
1
help a bald guy
Greetings listers, I have been running 1.4.21 for about 7 months now, but have been told I have to move up the 1.4 food chain or into the 1.6 chain because 1.4.21 is too flaky for our POTS line handling (does funny things with echo, doesn't connect to external conference calls, etc.). Which release will give me the most joy/least headache/closest performance to
2009 Jan 22
1
Zap connection problem
Greetings all, I'm trying to connect to an AT&T teleconference, but the call is never marked as ANSWERED by asterisk and therefore won't bridge and continue. The only work-around I've come up with so far is to dial like this: Exten => 744,1,Dial(Zap/g1,,p) The "private" mode keeps the line open without trying to do a bridge, but requires the
2010 Oct 19
1
dahdi vmware query
Greeting list, I hope this isn't a "lazy" question. I have been running TDM400P and TDM410P cards in Dell PowerEdge Servers for a few years now. We are moving from physical servers to VMWARE servers. What opportunities should I expect moving these cards into the new machines? Or should I leave the existing machines intact and use IAX to get to the DAHDI lines
2010 Dec 02
4
DAHDI on VMWARE
Hi gang, We are moving our computers from a cluster of physical machines to a VMWARE server with virtual machines. We investigated and are looking to replace our TDM400P/TDM410P with AEX410P cards. Can we run asterisk with the DAHDI drivers from one of the Virtual machines or is DAHDI going to have to be a native process on the "REAL" machine? Thanks Danny Nicholas
2010 Apr 09
3
Problems with Fax over TDM410P
Hello my friends... We are having some problems with the fax in our asterisk server... We have: Asterisk 1.4.21.2 Zaptel Version: 1.4.11 libpri version: 1.4.5 Digium Card TDM 410P This digium card has 3 FXO ports and 1 FXS port where we have a fax machine connected! The problem is that we can receive fax very good, but we can't make any outbound fax call, in fact, our asterisk get freezed
2010 Apr 16
2
How to set up Fax on Asterisk - Using analog Fax machines and HT502 (or FXS of a Digium TDM410P)
Hello Asterisk users, We are having MANY but MANY problems configuring an analog fax machine to work properly on Asterisk, the first thing we do was to plug in the Fax analog machine to the FXS port of the Digium TDM410P, we set echocancel=no on zapata.conf and also faxdetect=yes on general section, but our Asterisk CRASH every time we try to send/receive fax! We are using Asterisk 1.4.21 and
2009 Jul 20
0
No subject
expected context is valid (may not work on 1.2, I started this ride at 1.4 and therefore have no backward knowledge). _____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of David Nickel Sent: Wednesday, May 05, 2010 4:41 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Hash Dial
2009 Jan 16
0
No subject
--- span_1 = DAHDI/g1 1,1,dial(${span_1}/${EXTEN:0}) --- I can only presume some form of precedence overrides the group configuration in the recent asterisk installs and not for the servers set up earlier. On 26/5/09 4:01 PM, "Kal Feher" <kalman.feher at melbourneit.com.au> wrote: > Ok I've solved the problem. I do not think it was as switchtype issue after > all as
2009 Jan 16
0
No subject
adding gsm or just comment out the disallow and the 2 allows. (your recipient is using a codec that isn't ulaw or alaw). _____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of michel freiha Sent: Wednesday, January 28, 2009 2:21 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re:
2009 Jan 28
1
asterisk-users Digest, Vol 54, Issue 94
> Date: Wed, 28 Jan 2009 13:11:19 -0600 > From: "Danny Nicholas" <danny at debsinc.com> > Subject: Re: [asterisk-users] SIP Registrations broken on 1.4.22.1? > To: "'Asterisk Users Mailing List - Non-Commercial Discussion'" > <asterisk-users at lists.digium.com> > Message-ID: <D32AD473FC574B41AE6A842E46549174 at db0005> >
2009 Jan 16
0
No subject
adding gsm or just comment out the disallow and the 2 allows. (your = recipient is using a codec that isn't ulaw or alaw). =20 _____ =20 From: asterisk-users-bounces at lists.digium.com = [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of michel = freiha Sent: Wednesday, January 28, 2009 2:21 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re:
2009 Jan 16
0
No subject
adding gsm or just comment out the disallow and the 2 allows. (your recipient is using a codec that isn't ulaw or alaw). _____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of michel freiha Sent: Wednesday, January 28, 2009 2:21 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re:
2009 Jan 16
0
No subject
adding gsm or just comment out the disallow and the 2 allows. (your recipient is using a codec that isn't ulaw or alaw). _____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of michel freiha Sent: Wednesday, January 28, 2009 2:21 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: