[AsteriskBrasil] queda ligacao
Luis Antonio Prata Barbosa
luispratalistas em gmail.com
Terça Novembro 5 05:06:07 BRST 2013
Verifique se o busydetect=yes e o busycount=4 ... Isso fará com que o
Asterisk identifique o tom de ocupado e desligue.
Se não estiver dando certo, verifique os ganhos do canal da FXO, sugiro
rxgain=0 e txgain=0, o eco da mensagem da URA pode confundir a detecção do
tom de ocupado também.
Att,
Luis.
Em 4 de novembro de 2013 20:27, cooper <cooper em opentime.com.br> escreveu:
> Luiz.
>
> uma pergunta, acontece que como falei tenho o channel da cianet para os
> ramais e as linhas.
>
> tenho uma ura. e quando alguem liga, e digita o ramal destino, e na hora
> desliga a chamada, o asterisk, ainda continua chamando o ramal ate por
> muitos minutos
>
>
> 2013/11/4 cooper <cooper em opentime.com.br>
>
>> obrigado luiz, era isso mesmo
>>
>>
>> muito obrigado
>>
>>
>> 2013/11/4 Luis Antonio Prata Barbosa <luispratalistas em gmail.com>
>>
>>> Parece que ele não reconheceu o atendimento. Os 5 minutos tem a ver com
>>> o parametro 300 do Dial (5*60)...
>>>
>>> Verifique os parametros call_progress=no e answeronpolarityswitch=no.
>>>
>>> Luis A P Barbosa
>>>
>>>
>>> 2013/11/4 cooper <cooper em opentime.com.br>
>>>
>>>> instalei na emp de minha esposa.
>>>>
>>>> channel bank cianet, 4 linhas analogicas da gvt e 12 ramais,
>>>>
>>>> e todas as chamadas no minuto 5, exato, ela cai,
>>>>
>>>> as ultimas linhas do log sao estas
>>>>
>>>> [Nov 4 11:29:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-dialout-trunk:19] Dial("DAHDI/9-1",
>>>> "DAHDI/g2/40014433,300,tTwW") in new stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-dialout-trunk:20] NoOp("DAHDI/9-1", "Dial failed for some
>>>> reason with DIALSTATUS = NOANSWER and HANGUPCAUSE = 0") in new stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-dialout-trunk:21] Goto("DAHDI/9-1", "s-NOANSWER,1") in new
>>>> stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s-NOANSWER em macro-dialout-trunk:1] NoOp("DAHDI/9-1", "Dial failed due
>>>> to trunk reporting NOANSWER - giving up") in new stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s-NOANSWER em macro-dialout-trunk:2] Progress("DAHDI/9-1", "") in new
>>>> stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s-NOANSWER em macro-dialout-trunk:3] Playback("DAHDI/9-1",
>>>> "number-not-answering,noanswer") in new stack
>>>> [Nov 4 11:34:51] VERBOSE[11822][C-00000004] file.c: -- <DAHDI/9-1>
>>>> Playing 'number-not-answering.gsm' (language 'pt_br')
>>>> [Nov 4 11:34:53] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s-NOANSWER em macro-dialout-trunk:4] Congestion("DAHDI/9-1", "20") in
>>>> new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] app_macro.c: == Spawn
>>>> extension (macro-dialout-trunk, s-NOANSWER, 4) exited non-zero on
>>>> 'DAHDI/9-1' in macro 'dialout-trunk'
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: == Spawn
>>>> extension (from-internal, 040014433, 6) exited non-zero on 'DAHDI/9-1'
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [h em from-internal:1] Macro("DAHDI/9-1", "hangupcall") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:1] GotoIf("DAHDI/9-1", "1?endmixmoncheck") in new
>>>> stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:9] NoOp("DAHDI/9-1", "End of MIXMON check") in new
>>>> stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:10] GotoIf("DAHDI/9-1", "1?nomeetmemon") in new
>>>> stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:28] NoOp("DAHDI/9-1", "End of MEETME check") in
>>>> new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:29] GotoIf("DAHDI/9-1", "1?noautomon") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:34] NoOp("DAHDI/9-1", "TOUCH_MONITOR_OUTPUT=") in
>>>> new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:35] GotoIf("DAHDI/9-1", "1?noautomon2") in new
>>>> stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:41] NoOp("DAHDI/9-1", "MONITOR_FILENAME=") in new
>>>> stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:42] GotoIf("DAHDI/9-1", "1?skiprg") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:45] GotoIf("DAHDI/9-1", "1?skipblkvm") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:48] GotoIf("DAHDI/9-1", "1?theend") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:50] AGI("DAHDI/9-1", "hangup.agi") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] res_agi.c: --
>>>> <DAHDI/9-1>AGI Script hangup.agi completed, returning 0
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: -- Executing
>>>> [s em macro-hangupcall:51] Hangup("DAHDI/9-1", "") in new stack
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] app_macro.c: == Spawn
>>>> extension (macro-hangupcall, s, 51) exited non-zero on 'DAHDI/9-1' in macro
>>>> 'hangupcall'
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] pbx.c: == Spawn
>>>> extension (from-internal, h, 1) exited non-zero on 'DAHDI/9-1'
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] sig_analog.c: --
>>>> Hanging up on 'DAHDI/9-1'
>>>> [Nov 4 11:34:57] VERBOSE[11822][C-00000004] chan_dahdi.c: --
>>>> Hungup 'DAHDI/9-1'
>>>>
>>>>
>>>>
>>>> o que poderia ser o problema,
>>>>
>>>> obrigado
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1;
>>>> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7;
>>>> Intercomunicadores para acesso remoto via rede IP. Conheça em
>>>> www.Khomp.com.
>>>> _______________________________________________
>>>> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7.
>>>> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express.
>>>> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br.
>>>> _______________________________________________
>>>> Para remover seu email desta lista, basta enviar um email em branco
>>>> para asteriskbrasil-unsubscribe em listas.asteriskbrasil.org
>>>>
>>>
>>>
>>> _______________________________________________
>>> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1;
>>> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7;
>>> Intercomunicadores para acesso remoto via rede IP. Conheça em
>>> www.Khomp.com.
>>> _______________________________________________
>>> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7.
>>> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express.
>>> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br.
>>> _______________________________________________
>>> Para remover seu email desta lista, basta enviar um email em branco para
>>> asteriskbrasil-unsubscribe em listas.asteriskbrasil.org
>>>
>>
>>
>
> _______________________________________________
> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1;
> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7;
> Intercomunicadores para acesso remoto via rede IP. Conheça em
> www.Khomp.com.
> _______________________________________________
> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7.
> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express.
> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br.
> _______________________________________________
> 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/20131105/56d3eedb/attachment-0001.htm
Mais detalhes sobre a lista de discussão AsteriskBrasil