Span Clock Problems

One more thing I found (in the kern.log):

May 16 11:00:30 pbx2 kernel: wct4xxp: Setting yellow alarm on span 1
May 16 11:00:30 pbx2 kernel: timing source auto card 1!
May 16 11:01:11 pbx2 kernel: wct4xxp: Setting yellow alarm on span 3
May 16 11:01:11 pbx2 kernel: timing source auto card 1!
May 16 11:01:11 pbx2 kernel: timing source auto card 1!
May 16 11:01:12 pbx2 kernel: wct4xxp: Setting yellow alarm on span 2
May 16 11:01:12 pbx2 kernel: timing source auto card 1!
May 16 11:01:12 pbx2 kernel: timing source auto card 1!
May 16 11:01:16 pbx2 kernel: wct4xxp: Clearing yellow alarm on span 3
May 16 11:01:17 pbx2 kernel: wct4xxp: Clearing yellow alarm on span 2
May 16 11:01:30 pbx2 kernel: timing source auto card 1!
May 16 11:01:33 pbx2 last message repeated 816 times
May 16 11:01:33 pbx2 kernel: NMF workaround on!
May 16 11:01:33 pbx2 kernel: timing source auto card 1!
May 16 11:02:04 pbx2 last message repeated 5500 times
May 16 11:02:49 pbx2 last message repeated 8995 times
...
May 16 11:02:56 pbx2 kernel: timing source auto card 1!
May 16 11:02:56 pbx2 last message repeated 4 times
May 16 11:02:56 pbx2 kernel: NMF workaround off!
May 16 11:03:01 pbx2 kernel: wct4xxp: Clearing yellow alarm on span 1
May 16 11:09:51 pbx2 kernel: wct4xxp: Setting yellow alarm on span 1
May 16 11:09:51 pbx2 kernel: timing source auto card 1!
May 16 11:09:54 pbx2 last message repeated 95 times
May 16 11:09:54 pbx2 kernel: NMF workaround on!
May 16 11:09:54 pbx2 kernel: timing source auto card 1!
May 16 11:10:25 pbx2 last message repeated 6046 times
May 16 11:10:32 pbx2 last message repeated 966 times

[Jan 9 17:37] VERBOSE[19668] logger.c: -- Timeout occured, restarting PRI
[Jan 9 17:37] VERBOSE[19668] logger.c: -- Timeout occured, restarting PRI
[Jan 9 17:37] VERBOSE[19668] logger.c: -- Timeout occured, restarting PRI
[Jan 9 17:37] VERBOSE[19668] logger.c: -- Timeout occured, restarting PRI


[Jan 9 15:05] WARNING[6618]: chan_zap.c:2402 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway!
== Primary D-Channel on span 1 up
== Restart on requested on entire span 1


We run 10 asterisk servers, so far there are two of our servers which have this issue.

After restart request asterisk does not come back up, so i have setup a cron job to check for asterisk pid every minute. If pid does not exist then shell script starts it up again\\

Does anyone else have this issue??

I suggest you change a zaptel version to try, it seems very strange.

It is strange as it just started happening recently. The problem is not consistent, happens once in about a week. I have been trying to find a fix for it but no luck so far

hello,
have you checked with tel provider? ask them to check the line.
regards!
James.zhu

A bit of background.

Of the two asterisk servers we have an issue with, one is located in Melbourne and the other one in Fiji.

The Melbourne server is connected to the PSTN on two spans and two spans connected to an auto-dialer.

while the Fiji server has one span going through muxers to a muxer in Sydney and then to the PSTN (span 1) and the other span connected to a secondary asterisk server (span 2)

Span 3 and 4 are connected to our auto dialer.

So this is happening on two seperate lines in two different countries.

Will get telco to check the lines and advise if it gets fixed.