Hi<br><br>I'm not sure whether this is a proper forum, but I have an issue with wanpipe/dahdi driver and the sangoma a102de card.<br>My problem is probably the timing source change in case when the E1 cable is disconnected from the card span or spans.<br>
My application plays a PRI_CPE side and uses a testpattern/keepalive sending on one dedicated e1 channel to detect E1 breakdown.<br>When there is no cable connected to particular span, keepalive algorithm send patterns and reads 'dummy' data so it finds out that E1 is broken.<br>
Actually I've read the info from wanpipe.spec about the free run mode in firmware version V36, I use V37, here is my configuration<br><br>sles 11 SP1, wanpipe-3.5.23 (tested also 3.5.18), dahdi-2.5.0.1 (tested also 2.3.0.1), sangoma a102de, HWEC and DTMF detection off.<br>
<br>I have an experience with digium E1 cards and DAHDI driver that removing a cable from E1 span <br>makes the span to receive a clock from another span connected to telko.<br>Or, given there is no other span connected to telko, to use internal clock on all spans.<br>
So on the digium with dahdi the clock source is moving from span to span as specified <br>in "timing source" parameter of /etc/dahdi/system.conf (and indicated as MASTER in the 1st line of /proc/dahdi/X)<br><br>
I tested sangoma card together with wanpipe and dahdi drivers. Here the behaviour was rather different.<br>When cable was removed, following messages were logged (amongst others)<br><br>Oct 21 09:34:06 v184 kernel: [ 3185.691989] wanpipe2: Lost of Signal is detected!<br>
Oct 21 09:34:10 v184 kernel: [ 3189.604230] wanpipe2: LOF : ON<br>Oct 21 09:34:10 v184 kernel: [ 3189.604234] wanpipe2: E1 disconnected!<br>Oct 21 09:34:10 v184 kernel: [ 3189.604263] wanpipe2: AFT communications disabled! (Dev Cnt: 2 Cause: Link Down)<br>
<br>Between time 09:34:06 and 09:34:10 my application still writes/reads to the channel on span which was removed.<br>After 09:34:10 it is not possible to read/write anymore until the cable is connected back<br> (I use ACE framework event handler registered in reactor with READ | WRITE | EXCEPT mask)<br>
<br>When last cable is removed (tested also with quad card) then the first span 'recovers' and read/write is possible on it.<br>Connecting one span 'enables' reading/writing on re-connected span.<br><br>I think this might be a timing source issue.<br>
My question is, how to configure wanpipe/dahdi in order to share the clock on all spans of sangoma,<br>also when there are spans which are configured and used by an application but not connected.<br><br>Thank you in advance<br>
<br>Juraj Fabo<br><br>