[asterisk-r2] Problemas con un R2 y Avaya

[Robert Juarez]

Hola buenas me atrevo a mandarte un mail y contarte nuestras desgracias
llevamos ya poco mas de un me con tratar de levantar un par de R2 uno que
sera conectado a un avaya y otro directo a telemex,

Hemos seguido paso a paso todas los tutos posibles uno por uno, al reves al
derecho y nos es posible encontrar una solucion viable para ambos en estos
momentos estamos haciendo pruebas con el r2 y el avaya y parece que estamos
a punto ya de dar con el clavo pero nos ha esta dando una serie de errores
que no sabemos de donde se origina,

Tenemos configurado lo siguiente
Elastix 2.0
asterisk 1.6.2.6
dahdi 2.2.1.1
una tarjeta rhino T1E1 (al parecer configurada)
cuando revisamos (dahdi_tool) configuracion todo esta OK y revisamos los
canales nos da in service dahdi show channels desde la consola, pero si le
damos mfcr2 shown channels nos da ilde

nuestra configuracion system.conf

span=1,1,0,cas,hdb3
cas=1-15:1101
dchan=16
cas=17-31:1101

loadzone = mx
defaultzone = mx

chan_dahdi.conf
[channels]
context=from-pstn
;signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
;Uncomment these lines if you have problems with the disconection of your
analog lines
;busydetect=yes
;busycount=3

context=from-pstn
group=0
echocancel=yes
signalling=mfcr2
mfcr2_variant=mx
mfcr2_get_ani_first=no
mfcr2_max_ani=4
mfcr2_max_dnis=4
mfcr2_category=national_priority_subscriber
;mfcr2_category=national_subscriber
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
channel =>1-15,17-31


hemos intentado de todo y por eso que es que envio este mail de soporte para
ver si pueden ver algo que estemos haciendo mal
esto es lo que nos manda de error

[Jul 12 11:10:52] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 8
[Jul 12 11:10:52] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 9
[Jul 12 11:10:52] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 10
[Jul 12 11:10:52] NOTICE[3497] chan_dahdi.c: Far end unblocked on chan 11
[Jul 12 11:10:52] NOTICE[3497] chan_dahdi.c: Far end unblocked on chan 12
[Jul 12 11:10:52] NOTICE[3497] chan_dahdi.c: Far end unblocked on chan 13
[Jul 12 11:10:52] NOTICE[3497] chan_dahdi.c: Far end unblocked on chan 14
[Jul 12 11:10:52] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 7
[Jul 12 11:10:52] DEBUG[3550] chan_dahdi.c: bits changed in chan 3
[Jul 12 11:10:53] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 4
[Jul 12 11:10:53] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 5
[Jul 12 11:10:53] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 6
[Jul 12 11:10:53] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 1
[Jul 12 11:10:54] NOTICE[3496] chan_dahdi.c: Far end unblocked on chan 2
[Jul 12 11:10:54] DEBUG[3550] chan_dahdi.c: bits changed in chan 3
[Jul 12 11:10:54] ERROR[3550] chan_dahdi.c: Chan 3 - Protocol error. Reason
= Invalid CAS, R2 State = Seize ACK Received, MF state = DNIS Digit
Transmitted, MF Group = Forward Group I, CAS = 0x08
DNIS = 17994, ANI = 7997, MF = 0x20
[Jul 12 11:10:54] ERROR[3550] chan_dahdi.c: MFC/R2 protocol error on chan 3:
Invalid CAS
[Jul 12 11:10:54] VERBOSE[3550] chan_dahdi.c:     -- Hungup 'DAHDI/3-1'
[Jul 12 11:10:54] VERBOSE[3550] app_dial.c:   == Everyone is busy/congested
at this time (1:0/0/1)
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[s at macro-dialout-trunk:20] NoOp("SIP/7997-00000000", "Dial failed for some
reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 111") in new stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[s at macro-dialout-trunk:21] Goto("SIP/7997-00000000", "s-CHANUNAVAIL,1") in
new stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Goto
(macro-dialout-trunk,s-CHANUNAVAIL,1)
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[s-CHANUNAVAIL at macro-dialout-trunk:1] Set("SIP/7997-00000000", "RC=111") in
new stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[s-CHANUNAVAIL at macro-dialout-trunk:2] Goto("SIP/7997-00000000", "111,1") in
new stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Goto
(macro-dialout-trunk,111,1)
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[111 at macro-dialout-trunk:1] Goto("SIP/7997-00000000", "continue,1") in new
stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Goto
(macro-dialout-trunk,continue,1)
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[continue at macro-dialout-trunk:1] GotoIf("SIP/7997-00000000", "1?noreport")
in new stack
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Goto
(macro-dialout-trunk,continue,3)
[Jul 12 11:10:54] VERBOSE[3550] pbx.c:     -- Executing
[continue at macro-dialout-trunk:3] NoOp("SIP/7997-00000000", "TRUNK Dial
failed due to CHANUNAVAIL HANGUPCAUSE: 111 - failing through to other
trunks") in new stack


Un saludo

Roberto Juarez
Hoteles Sandos
Playa del Carmen Q.Roo, Mexico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100712/a318b5bd/attachment.htm