Hi, We have two of these 4 port FXO cards. However, we are having some problems with incoming/outgoing calls. The latest version of Asterisk/zaptel from CVS is being used. Voicemail, internal SIP <-> SIP calls between Pingtel xpressa hard phones work terrific, echotest is fine, and so on. The zaptel and wcfxs modules load fine, and show all 8 FXO interfaces in dmesg: --------------------------------------------------------- Zapata Telephony Interface Registered on major 196 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXO Module 1: Installed -- AUTO FXO Module 2: Installed -- AUTO FXO Module 3: Installed -- AUTO FXO Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXO Module 1: Installed -- AUTO FXO Module 2: Installed -- AUTO FXO Module 3: Installed -- AUTO FXO Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) Registered tone zone 0 (United States / North America) --------------------------------------------------------- Following problems have been observed, and are preventing us from dumping our existing Nortel Merdian PBX: 1. echo at beginning of call for several seconds, even with various combinations of echocancel and echotraining in zapata.conf 2. even though multiple incoming lines are connected, only the first ZAP channel is picking up. So if one line is in use, nobody else can call in even though there are other lines free. When in debug mode (-gcvvv) nothing is showing up that there's another call coming in. 3. channels don't always hang up properly - HookState shows as offhook for quite some time. 4. Asterisk Zap channels don't see an incoming call until 2 rings after the existing Nortel PBX sees it. Both people calling in and people answering don't like that. I've gone through whatever documentation and mailing list archives, but haven't been able to find working solutions. Have tried various combinations in zaptel.conf and zapta.conf but no luck yet :-( Ideas anyone? Thanks, Wim
Wim, If ya don't need callerid then add the patch at http://www.nodomain.org/asterisk to zaptel and asterisk directories. I did this for UK callerid and the phone now rings on the first ring of the CO. Bit of a bodge but it works. Dave -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Wim Kerkhoff Sent: 02 June 2004 06:34 To: Asterisk-users Subject: [Asterisk-Users] problems with TDM400P Hi, We have two of these 4 port FXO cards. However, we are having some problems with incoming/outgoing calls. The latest version of Asterisk/zaptel from CVS is being used. Voicemail, internal SIP <-> SIP calls between Pingtel xpressa hard phones work terrific, echotest is fine, and so on. The zaptel and wcfxs modules load fine, and show all 8 FXO interfaces in dmesg: --------------------------------------------------------- Zapata Telephony Interface Registered on major 196 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXO Module 1: Installed -- AUTO FXO Module 2: Installed -- AUTO FXO Module 3: Installed -- AUTO FXO Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXO Module 1: Installed -- AUTO FXO Module 2: Installed -- AUTO FXO Module 3: Installed -- AUTO FXO Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) Registered tone zone 0 (United States / North America) --------------------------------------------------------- Following problems have been observed, and are preventing us from dumping our existing Nortel Merdian PBX: 1. echo at beginning of call for several seconds, even with various combinations of echocancel and echotraining in zapata.conf 2. even though multiple incoming lines are connected, only the first ZAP channel is picking up. So if one line is in use, nobody else can call in even though there are other lines free. When in debug mode (-gcvvv) nothing is showing up that there's another call coming in. 3. channels don't always hang up properly - HookState shows as offhook for quite some time. 4. Asterisk Zap channels don't see an incoming call until 2 rings after the existing Nortel PBX sees it. Both people calling in and people answering don't like that. I've gone through whatever documentation and mailing list archives, but haven't been able to find working solutions. Have tried various combinations in zaptel.conf and zapta.conf but no luck yet :-( Ideas anyone? Thanks, Wim _______________________________________________ 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
On Wed, 2004-06-02 at 00:33, Wim Kerkhoff wrote:> Following problems have been observed, and are preventing us from > dumping our existing Nortel Merdian PBX: > > 1. echo at beginning of call for several seconds, even with various > combinations of echocancel and echotraining in zapata.confEcho is miserable to try to fix. Newer zaptel CVS checkouts have a tool called "zttest" What are the results of running zttest? Unbalanced lines can cause echo, both IRQ sharing, IDE DMA, framebuffer, and graphics (as well as crappy motherboards) can introduce latency on the PCI bus and cause echo.> 2. even though multiple incoming lines are connected, only the first ZAP > channel is picking up. So if > one line is in use, nobody else can call in even though there are other > lines free. When in debug mode (-gcvvv) nothing is showing up that > there's another call coming in.This is not a general problem. It sounds like you are not using groupin your zapata.conf to put the TDM ports into a hunt group.> 3. channels don't always hang up properly - HookState shows as offhook > for quite some time.Sounds like something isn't providing far end disconnect supervision.> 4. Asterisk Zap channels don't see an incoming call until 2 rings after > the existing Nortel PBX sees it. Both people calling in and people > answering don't like that.You don't have Caller*ID on your lines, but Asterisk is configured to use (and waiting for) Caller*ID. See the usecallerid= and calleridoptions. -- Eric Wieling * BTEL Consulting * 504-899-1387 x2111 "In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss."