[AsteriskBrasil] Problema com E1 R2 EBT - Consigo receber mas não consigo realizar (CONGESTION)
Nivaldo Junior
junior em remoto.com.br
Quarta Setembro 19 11:49:09 BRT 2007
Pessoal,
Estou com um problema em um E1 R2D da Embratel.
Estou conseguindo receber ligações numa boa, mas não consigo realizar
chamadas.
Minhas confs:
- Asterisk 1.2.14
- Zaptel 1.2.12
- zaptel.conf
loadzone=br
defaultzone=br
#E1 com 14 canais
span=1,0,0,cas,hdb3
cas=1-14:1101
#E1 com 30 canais
span=2,0,0,cas,hdb3
cas=32-46:1101
cas=48-62:1101
- unicall.conf
[channels]
language=pt_BR
usecallerid=yes
hidecallerid=no
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
immediate=no
; 14 canais
group=0
callgroup=0
pickupgroup=0
protocolclass=mfcr2
protocolvariant=br,20,4,8
protocolend=pce
context=ebt
channel => 1-14
; 30 canais
group=1
callgroup=1
pickupgroup=1
protocolclass=mfcr2
protocolvariant=br,20,4,8
protocolend=pce
context=ebt
channel => 32-46
channel => 48-62
- Tentando realizar uma chamada:
-- Executing Dial("SIP/ramal1-081d9250", "Unicall/g1/40098153") in new
stack
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Call control(1)
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Make call
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Making a new call with CRN 32769
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 0001 -> [1/ 1/Idle /Idle ]
-- Called g1/40098153
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:2644 handle_uc_event: Unicall/32
event Dialing
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 1101 [1/ 40/Seize /Idle ]
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 4 on -> [2/ 40/Group I /Idle ]
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 1 on [2/ 40/Group I /DNIS ]
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 4 off -> [2/ 40/Group I /DNIS ]
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 1 off [2/ 40/Group I /DNIS ]
Sep 19 11:53:58 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 0 on -> [2/ 40/Group I /DNIS ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 5 on [2/ 40/Group I /DNIS ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 0 off -> [2/ 40/Group I /DNIS ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 5 off [2/ 40/Group I /DNIS ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Calling party category 0x0
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 1 on -> [2/ 40/Group I /DNIS ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 5 on [2/ 40/Group I /Category ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 1 off -> [2/ 40/Group I /Category ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 5 off [2/ 40/Group I /Category ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 B on -> [2/ 40/Group I /Category ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 4 on [2/ 40/Group I /End of ANI ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 B off -> [2/ 40/Group I /End of ANI ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 4 off [2/ 40/Group I /End of ANI ]
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Far end disconnected(cause=Switching equipment congestion [42]) -
state 0x40
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:2644 handle_uc_event: Unicall/32
event Far end disconnected
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:2930 handle_uc_event: CRN
32769 - far disconnected cause=Switching equipment congestion [42]
-- Channel 0 got hangup
-- UniCall/32-1 is circuit-busy
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Channel gains
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Channel switching
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Call control(6)
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Drop call(cause=Normal Clearing [16])
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Clearing fwd
Sep 19 11:53:59 WARNING[6902]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 1001 -> [2/ 800/Clear fwd B /End of ANI ]
-- Hungup 'UniCall/32-1'
== Everyone is busy/congested at this time (1:0/1/0)
== Auto fallthrough, channel 'SIP/ramal1-081d9250' status is 'CONGESTION'
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 <- 1001 [1/ 800/Clear fwd D /Idle ]
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Call disconnected(cause=Switching equipment congestion [42]) -
state 0x800
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:2644 handle_uc_event: Unicall/32
event Drop call
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Call control(7)
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Release call
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Destroying call with CRN 32769
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:2644 handle_uc_event: Unicall/32
event Release call
-- Unicall/32 released
Sep 19 11:53:59 WARNING[6897]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/32 Channel echo cancel
O mais intrigante é que tenho atualmente outros servidores funcionando em R2D
sem problemas, mas estou enfrentando este problema e não estou conseguindo
resolver.
Já troquei de máquina, de placa, de balum, de cabo, enfim, fiz todos os testes
e não encontrei o problema.
Estou fazendo os testes usando 3 E1, um de 14 canais, e os outros dois de 30
canais cada um.
--
Nivaldo Montenegro Júnior
Diretor de TI&C
Digivox Soluções de Comunicação Ltda
+ 55 83 4009-8195
+ 55 83 4009-8199 - fax
+ 55 83 8877-0220 - cell
junior em digivox.com.br
http://www.digivox.com.br
Antes de imprimir pense em seu compromisso com o Meio Ambiente
e o comprometimento com os Custos .
____________________________________________________________________________
Esta mensagem e seus anexos podem conter informações confidenciais ou
privilegiadas. Se você não é o destinatário dos mesmos você não está
autorizado a utilizar o material para qualquer fim. Solicitamos que você
apague a mensagem e avise imediatamente ao remetente. O conteúdo desta
mensagem e seus anexos não representam necessariamente a opinião e a
intenção da empresa, não implicando em qualquer obrigação ou
responsabilidade da parte da mesma.
This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose or take any action based on this message or any
information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message. The
contents of this message and its attachments do not necessarily express the
opinion or the intention of the company, and do not implies any legal
obligation or responsabilities from this company.
Mais detalhes sobre a lista de discussão AsteriskBrasil