[Asterisk-Users] Re: Alarm on Unicall

[acriollo]

This is my unicall.conf

[channels]
language=es
context=incoming                                                ; Contexto
pod default
usecallerid=yes
hidecallerid=no
;restrictcid=no
callwaitingcallerid=no
threewaycalling=no
transfer=yes
cancallforward=yes
callreturn=no
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
echotraining=800
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
;
immediate=no
;
;callerid=2564286000
;
amaflags=default
;
accountcode=lss0101
;
musiconhold=default
;
;loglevel=255
protocolclass=mfcr2
protocolvariant=mx,10,4
protocolend=co
group = 1
context=incoming
channel => 1-10
;channel => 17-31

And this is my zaptel.

========zaptel.conf
span=1,0,0,cas,hdb3

# E1 1
cas=1-10:1101
loadzone = us
defaultzone=us
#fxoks=32-34
fxsks=32-33

Also I was tested with this another setup with the same results.

========zaptel.conf
span=1,1,0,cas,hdb3

# E1 1
cas=1-10:1101
loadzone = us
defaultzone=us
#fxoks=32-34
fxsks=32-33

Thanks in advanced.

Regards


2006/3/27, acriollo <crmeae at gmail.com>:
>
> Hi all,
> any body can tell me why i am receiving this message in my sever ?
>
> I have running * with 10 Digital Lines, but i am receiving a lot of times
> this message .
> Is a software issue or is a hardware issue ?
>
> Regards.
>
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/5 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/5 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/5 Alarm No Alarm raised, Yellow Alarm cleared
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/6 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/6 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/6 Alarm No Alarm raised, Yellow Alarm cleared
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/7 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/7 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/7 Alarm No Alarm raised, Yellow Alarm cleared
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/8 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/8 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/8 Alarm No Alarm raised, Yellow Alarm cleared
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/9 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/9 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/9 Alarm No Alarm raised, Yellow Alarm cleared
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event:
> Unicall/10 event Alarm
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event:
> Unicall/10 Alarm masks 0x0000 0x0004
> Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event:
> Unicall/10 Alarm No Alarm raised, Yellow Alarm cleared
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060327/4762a4cd/attachment.htm