Upon further research I kind of answered my own question.. But I will share... If you are seeing multiple H.100 errors in your system log then the hardware echo canceler does not have a good clock source. On our more recent drivers 3.3.12 and up the first port that starts up will be the clocking source. So if your wanpipe1 is not connected then please configure your card to only start the first port that connects. If you have an older driver then the timing source is the first physical port on the card. So if you are not using the first physical port then please follow the steps below to set another port as a timing source.
Please note that only one port can act as timing source for HWEC in a particular AFT102/104/108 card, in other words you can only set HWEC_CLCKSRC = YES for only one port for a card! ________________________________ From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Robert Grignon Sent: Wednesday, October 28, 2009 1:45 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Having a heck of a time Yes I did that... I even recompiled dahdi-linux and tools after wanpipe install... Once I did that it recognized the card and said I could run "dahdi_genconf modules" which in turn would only load the cards that it seeing. I had the PRI running in slot 6. Once I unplugged the PRI I was able to get a response from dahdi_test I then wondered if it was looking for a circuit on channel 1 (this didnt make much sense because the PRI is getting timing from the telco and the port location should not matter) I then moved the PRI to channel 1 and dahdi_test returned the following: [r...@lin-vgw1 asterisk]# dahdi_test -vc 10 Opened pseudo dahdi interface, measuring accuracy... 8192 samples in 8190.808 system clock sample intervals (99.985%) 8192 samples in 8190.288 system clock sample intervals (99.979%) 8192 samples in 8190.776 system clock sample intervals (99.985%) 8192 samples in 8190.872 system clock sample intervals (99.986%) 8192 samples in 8190.720 system clock sample intervals (99.984%) 8192 samples in 8190.833 system clock sample intervals (99.986%) 8192 samples in 8190.960 system clock sample intervals (99.987%) 8192 samples in 8190.864 system clock sample intervals (99.986%) 8192 samples in 8190.744 system clock sample intervals (99.985%) 8192 samples in 8190.800 system clock sample intervals (99.985%) --- Results after 10 passes --- Best: 99.987 -- Worst: 99.979 -- Average: 99.984940, Difference: 99.984940 GO figure... I did notice this in the logs and am not sure what to make of the "CT_C8_A clock behavior does not conform to the H.100 spec" reference: Oct 28 13:26:19 lin-vgw1 kernel: wanpipe6: Lost of Signal is detected! (Unplugged circuit and moved to channel 1) Oct 28 13:26:20 lin-vgw1 kernel: wanpipe2: Lost of Signal is detected! Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: LOF : ON Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: RED : ON Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: T1 disconnected! Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: Enable transmit RAI alarm Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: AFT communications disabled! (Dev Cnt: 6 Cause: Link Down) Oct 28 13:26:22 lin-vgw1 kernel: wanpipe6: TDM Free Run Timing Enabled 1 ms Oct 28 13:26:23 lin-vgw1 kernel: wanpipe6: LOS : ON Oct 28 13:26:24 lin-vgw1 kernel: wanpipe2: LOS : ON Oct 28 13:27:06 lin-vgw1 kernel: wanec1: The H100 slave has lost its framing on the bus! Oct 28 13:27:06 lin-vgw1 kernel: wanec1: The CT_C8_A clock behavior does not conform to the H.100 spec! Oct 28 13:27:06 lin-vgw1 kernel: wanpipe5: Lost of Signal is cleared! Oct 28 13:27:07 lin-vgw1 kernel: wanpipe1: RAI : ON Oct 28 13:27:07 lin-vgw1 kernel: wanpipe1: Open Circuit is cleared! Oct 28 13:27:07 lin-vgw1 kernel: wanpipe1: Lost of Signal is cleared! Oct 28 13:27:17 lin-vgw1 kernel: wanpipe1: RAI : OFF Oct 28 13:27:17 lin-vgw1 kernel: wanpipe5: LOS : OFF Oct 28 13:27:18 lin-vgw1 kernel: wanpipe1: LOS : OFF Oct 28 13:27:18 lin-vgw1 kernel: wanpipe1: LOF : OFF Oct 28 13:27:18 lin-vgw1 kernel: wanpipe1: RED : OFF Oct 28 13:27:21 lin-vgw1 kernel: wanpipe1: T1 connected! Oct 28 13:27:21 lin-vgw1 kernel: wanpipe1: AFT communications enabled! Oct 28 13:27:21 lin-vgw1 kernel: wanpipe1: AFT Global TDM Intr Oct 28 13:27:21 lin-vgw1 kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1 Oct 28 13:27:21 lin-vgw1 kernel: ADDRCONF(NETDEV_CHANGE): w1g1: link becomes ready ________________________________ From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tim King Sent: Wednesday, October 28, 2009 1:27 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Having a heck of a time Did you use ./Setup dahdi when installing the wanpipe drivers? http://wiki.sangoma.com/wanpipe-linux-asterisk-dahdi
_______________________________________________ -- 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
