[asterisk-dev] Zaptel LOS threshold
Butler, Larry
lbutler at intercall.com
Mon Jul 2 14:03:08 CDT 2007
Thanks Alex! I believe this is going to be it... Until today I have
never really explored the Zaptel code base and needed a good kick in the
right direction.
Thanks again for the help,
Larry Butler
>Larry
>
>Sounds like the answer you seek may be in ztdynamic.c in the
neighbourhood
>of line 796, function check_for_red_alarm():
>
> while(z) {
> newalarm = z->span.alarms & ~ZT_ALARM_RED;
> /* If nothing received for a second, consider that RED
ALARM */
> if ((jiffies - z->rxjif) > 1 * HZ) {
> newalarm |= ZT_ALARM_RED;
> if (z->span.alarms != newalarm) {
> z->span.alarms = newalarm;
> zt_alarm_notify(&z->span);
> alarmchanged++;
> }
> }
> z = z->next;
> }
>
>
>If I have this wrong, please, someone, correct me. I do not actively
>peruse this code and would hate to misinform someone.
>
>Thank you,
>
>-- Alex
>
>On Mon, 2 Jul 2007, Butler, Larry wrote:
>
>> I am trying to locate a LOS to red alarm threshold value in zaptel.
>> Does this exist? If not, can someone point me in the right
direction
>> of where to start looking to make changes? It appears that any bit
loss
>> will throw the circuit into a red. If I am reading this right, the
>> Telcordia spec states that the circuit should survive LOS for 2.5
>> seconds prior to declaring red alarm.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Larry Butler
>>
>>
>>
>>
>
>--
>Alex Balashov
>Evariste Systems
>Web : http://www.evaristesys.com/
>Tel : +1-678-954-0670
>Direct : +1-678-954-0671
>
>_______________________________________________
>--Bandwidth and Colocation Provided by http://www.api-digital.com--
>
>asterisk-dev mailing list
>To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
More information about the asterisk-dev
mailing list