[AsteriskBrasil] Ligação Dahdi com Meridian
Danilo Escobar
dengueipaussu em yahoo.com.br
Quinta Janeiro 12 17:09:05 BRST 2012
Oi Pablo, segue alguns comandos,
svp01ibs*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 hotelramais default In Service
2 hotelramais default In Service
3 hotelramais default In Service
4 hotelramais default In Service
5 hotelramais default In Service
6 hotelramais default In Service
7 hotelramais default In Service
8 hotelramais default In Service
9 hotelramais default In Service
10 hotelramais default In Service
11 hotelramais default In Service
12 hotelramais default In Service
13 hotelramais default In Service
14 hotelramais default In Service
15 hotelramais default In Service
17 hotelramais default In Service
18 hotelramais default In Service
19 hotelramais default In Service
20 hotelramais default In Service
21 hotelramais default In Service
22 hotelramais default In Service
23 hotelramais default In Service
24 hotelramais default In Service
25 hotelramais default In Service
26 hotelramais default In Service
27 hotelramais default In Service
28 hotelramais default In Service
29 hotelramais default In Service
30 hotelramais default In Service
31 hotelramais default In Service
*********************************************************************************************
svp01ibs*CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: Network
Remote type: Unknown node type
Overlap Dial: 0
Logical Channel Mapping: 0
Timer and counter settings:
N200: 3
N202: 3
K: 7
T200: 1000
T201: 1000
T202: 10000
T203: 10000
T303: 4000
T305: 30000
T308: 4000
T309: 6000
T312: 6000
T313: 4000
T-HOLD: 4000
T-RETRIEVE: 4000
T-RESPONSE: 4000
T-STATUS: 4000
T-ACTIVATE: 10000
T-DEACTIVATE: 4000
T-INTERROGATE: 4000
T-RETENTION: 30000
T-CCBS1: 4000
T-CCBS2: 2700000
T-CCBS3: 20000
T-CCBS4: 5000
T-CCBS5: 3600000
T-CCBS6: 3600000
T-CCNR2: 10800000
T-CCNR5: 11700000
T-CCNR6: 11700000
Q931 RX: 0
Q931 TX: 0
Q921 RX: 0
Q921 TX: 96
Q921 Outstanding: 0 (TEI=0)
Total active-calls:0 global:0
CC records:
Overlap Recv: No
***************************************************************************88888
OBS: mudei o switchtype para NATIONAL
svp01ibs*CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: Network
Remote type: Unknown node type
Overlap Dial: 0
Logical Channel Mapping: 0
Timer and counter settings:
N200: 3
N202: 3
K: 7
T200: 1000
T201: 1000
T202: 10000
T203: 10000
T303: 4000
T305: 30000
T308: 4000
T309: 6000
T312: 6000
T313: 4000
T-HOLD: 4000
T-RETRIEVE: 4000
T-RESPONSE: 4000
Q931 RX: 0
Q931 TX: 0
Q921 RX: 0
Q921 TX: 3
Q921 Outstanding: 0 (TEI=0)
Total active-calls:0 global:0
CC records:
Overlap Recv: No
******************************************************************************
[Jan 12 16:07:00] WARNING[3324]: app_dial.c:1780 dial_exec_full: Unable to create channel of type 'dahdi' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)
-- Auto fallthrough, channel 'SIP/999-00000001' status is 'CONGESTION'
svp01ibs*CLI>
*********************************************************88
svp01ibs*CLI> pri set debug 2 span 1
Enabled debugging on span 1
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=0, V(S)=0, V(R)=0
K=7, RC=1, l3_initiated=1, reject_except=0, ack_pend=0
T200_id=8192, N200=3, T203_id=0
TEI=0 Sending SABME
> TEI: 0 State 5(Awaiting establishment)
> V(A)=0, V(S)=0, V(R)=0
> K=7, RC=2, l3_initiated=1, reject_except=0, ack_pend=0
> T200_id=0, N200=3, T203_id=0
> [ 02 01 7f ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
-- Starting T200 timer
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=0, V(S)=0, V(R)=0
K=7, RC=2, l3_initiated=1, reject_except=0, ack_pend=0
T200_id=8192, N200=3, T203_id=0
TEI=0 Sending SABME
> TEI: 0 State 5(Awaiting establishment)
> V(A)=0, V(S)=0, V(R)=0
> K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
> T200_id=0, N200=3, T203_id=0
> [ 02 01 7f ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
-- Starting T200 timer
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=0, V(S)=0, V(R)=0
K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
T200_id=8192, N200=3, T203_id=0
SAPI/TEI=0/0 Starting link restart delay timer
TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
Changing from state 5(Awaiting establishment) to 4(TEI assigned)
TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
SAPI/TEI=0/0 Kick starting link
-- T203 requested to stop when not started
-- Restarting T200 timer
TEI=0 Sending SABME
> TEI: 0 State 4(TEI assigned)
> V(A)=0, V(S)=0, V(R)=0
> K=7, RC=0, l3_initiated=1, reject_except=0, ack_pend=0
> T200_id=8192, N200=3, T203_id=0
> [ 02 01 7f ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
________________________________
De: Pablo Foruns <pablo.foruns em gmail.com>
Para: Danilo Escobar <dengueipaussu em yahoo.com.br>; asteriskbrasil em listas.asteriskbrasil.org
Enviadas: Quarta-feira, 11 de Janeiro de 2012 19:17
Assunto: Re: [AsteriskBrasil] Ligação Dahdi com Meridian
Danilo manda o log da CLI no momento da ligação e do dahdi show status também, assim fica muito vago pra galera poder te ajudar.
Att.:
Pablo.
Em 10 de janeiro de 2012 19:38, Danilo Escobar <dengueipaussu em yahoo.com.br> escreveu:
Boa noite!
>
>
>Estou com um probleminha, instalei uma placa te405p no asterisk, os drivers libpri-1.4.12.tar.gz e o Dahdi, hj o rapaz de uma empresa que cuida da Central telefonica Meridian, instalou um canal E1 para o asterisk, onterligando os dois para que possam conversar ramais sip(asterisk) e analógicos E1. Pelo dahdi_toll diz que a porta configurada esta ok, a luz da placa no inicio esta vermelha(red alarm), mas depois com algumas alterações, ficou verde.
>
>
>Problema:
>Ao tentar ligar para o ramal do sip para o Dahdi ou vice-versa, da tom de ocupado e no Cli aparece Congestion.
>O rapaz da central disse que na central esta tudo ok.
>Alguém sabe o que pode ser?
>
>
>segue meu system.conf e o chan_dhadi.conf
>
>
>system.conf
>
>
>span=1,1,0,ccs,hdb3
>loadzone=us
>
>#span=2,1,0,ccs,hdb3
>
>#span=3,0,0,ccs,hdb3,crc4
>bchan = 1-15,17-31
>dchan = 16
>echocanceller = mg2,1-15,17-31
>
>
>
>
> chan_dhadi.conf
>
>
>
>[channels]
>
>overlapdial=yes
>
>callprogress=yes
>
>usercallerid = yes
>callerid = asreceived
>callwaiting = yes
>usecallingpres = yes
>;callwaitingcallerid = yes
>;switchtype = euroisdn
>switchtype = 5ess
>treewaycalling = yes
>transfer = yes
>canpark = yes
>cancallforward = yes
>callreturn = yes
>echocancel = yes
>echocancelwhenbridge = yes
>group = 1
>callgroup = 1
>pickupgroup = 1
>callprogress = yes
>progzone = us
>mohinterpreter = default
>mohsuggest = default
>;signalling = fxo_ks
>signalling = pri_net
>context = hotelramais
>channel => 1-15
>
>
>
>
>No status do Meridian esta dando idle, mas quando tenta ligar pro ramal da ocupado
>
>
>
>
>
>
>
>
>
>
>_______________________________________________
>KHOMP ::: External Series Experience :::
>Um novo conceito para o mercado de aplicações que vai
>fazer você pensar fora da caixa. Aguarde este lançamento
>_______________________________________________
>DIGIVOICE: Lider no mercado de placas para Asterisk
>Único fabricante com Centro de Treinamento especializado.
>LANÇAMENTO: Channel Bank TDMoE, até 64 canais FXS / FXO.
>www.digivoice.com.br ou (11)3016-5200.
>________
>YEALINK: Telefones IP e VídeoPhones IP com o melhor custo/benefício do mercado.
>email: yealink em commlogik.com.br | www.commlogik.com.br | (11) 5503-1011
>______________________________________________
>Para remover seu email desta lista, basta enviar um email em branco para asteriskbrasil-unsubscribe em listas.asteriskbrasil.org
>
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: http://listas.asteriskbrasil.org/pipermail/asteriskbrasil/attachments/20120112/c8185c54/attachment.htm
Mais detalhes sobre a lista de discussão AsteriskBrasil