[Asterisk-Users] Asterisk and Mitel SX 200 Slip and Frame Err ors causing Major Ala rms

[Geoff Manning]

Eric "ManxPower" Wieling wrote:
>> 
>>> span=1,1,0,d4,ami
>>> e&m=1-24
>>> 
> 
> Looks like you have told Asterisk to get it's timing from the Mitel.
> I'll bet the Mitel is trying to get it's timing from Asterisk.
> 
> Try span=1,0,0,d4,ami and run ztcfg -vvv


We turned on the zaptel debugging and noticed the following entries in the
/var/log/messages log. Any clue to what they are indicating?

server:/et/asterisk# tail /var/log/messages -f | grep -A 1 resync

Oct 11 12:21:45 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:45 localhost last message repeated 3 times
--
Oct 11 12:21:45 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:45 localhost last message repeated 7 times
--
Oct 11 12:21:47 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:47 localhost last message repeated 4 times
--
Oct 11 12:21:47 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:47 localhost last message repeated 2 times
--
Oct 11 12:21:51 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:51 localhost last message repeated 5 times
--
Oct 11 12:21:55 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:21:55 localhost last message repeated 6 times
--
Oct 11 12:22:01 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:22:01 localhost last message repeated 3 times
--
Oct 11 12:22:01 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:22:01 localhost last message repeated 2 times
--
Oct 11 12:22:02 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:22:02 localhost last message repeated 3 times
--
Oct 11 12:22:08 localhost kernel: T1: Lost our place, resyncing
Oct 11 12:22:08 localhost last message repeated 3 times


They are too numerous to match the slip errors/framing errors per hour
(about 500 and 1000 respectively). These are generating at a clip of about
7,000 per hour.

Thanks,
Geoff