[AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-04-03 Por tôpico Eduardo Souza
Boa tarde,

alguém pode em ajudar com esse erro, já fiz de tudo.


[Apr  3 13:45:06] ERROR[3266] chan_dahdi.c: Chan 15 - Protocol error.
Reason = Invalid CAS, R2 State = Idle, MF state = MF Engine Off, MF Group =
No Group, CAS = 0x04
DNIS = , ANI = , MF = 0x20
[Apr  3 13:45:06] ERROR[3266] chan_dahdi.c: MFC/R2 protocol error on chan
15: Invalid CAS
[Apr  3 13:45:06] NOTICE[3267] chan_dahdi.c: Far end unblocked on chan 31
[Apr  3 13:45:06] NOTICE[3266] chan_dahdi.c: Far end unblocked on chan 15


Att

Eduardo Souza
___
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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  www.digivoice.com.br
___
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-unsubscr...@listas.asteriskbrasil.org

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-28 Por tôpico Raphael Rodrigues
Não se esqueça de ativar o CAS Persistant Check assim como o mestre
Alexandre sugeriu.

boa sorte.

abraço

2013/3/28 Hudson Cardoso hudsoncard...@hotmail.com

 Parece que ja tem um asterisk rodando em outra console
 Experimentar formatar a maquina e instalar do zero
 faca um teste em uma VM .


 Hudson
 (048) 8413-7000
 Para quem nao cre, nenhuma prova converte,Para aquele que cre, nenhuma prova 
 precisa.



 --
 From: deny.san...@gmail.com
 Date: Thu, 28 Mar 2013 00:27:12 -0300
 To: asteriskbrasil@listas.asteriskbrasil.org
 Subject: Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel



 On Mar 27, 2013, at 1:04 PM, Alexandre Cavalcante Alencar wrote:

 Cadê seu protocol file?

 Você ativou CAS Persistant Check?

 Sds


 Boa noite Alexandre, eu acabei reinstalando o asterisk com o freepbx
 novamente porem estou com o seguinte erro agora , nao consigo subir o
 asterisk de forma alguma, ele me gera o erro abaixo no messages e tambem
 entra em safe mode

 Erro ao startar o asterisk amportal start ou /etc/init.d/asterisk

 /usr/sbin/safe_asterisk: line 145:  7517 Illegal instruction (core
 dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} 
 /dev/${TTY} 21  /dev/${TTY}
 Asterisk ended with exit status 132
 Asterisk exited on signal 4.
 Automatically restarting Asterisk.
 /usr/sbin/safe_asterisk: line 145:  7604 Illegal instruction (core
 dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} 
 /dev/${TTY} 21  /dev/${TTY}
 Asterisk ended with exit status 132
 Asterisk exited on signal 4.
 Automatically restarting Asterisk.


 Erro no messages

 Mar 28 00:23:02 srv01-asterisk kernel: asterisk[5395] trap invalid opcode
 rip:2b77e45f3a46 rsp:7fff79c23990 error:0
 Mar 28 00:23:07 srv01-asterisk kernel: asterisk[5444] trap invalid opcode
 rip:2b22e72a7a46 rsp:7fffca5d7e50 error:0
 Mar 28 00:23:12 srv01-asterisk kernel: asterisk[5494] trap invalid opcode
 rip:2b4cbc5f3a46 rsp:7fff29978d50 error:0
 Mar 28 00:23:17 srv01-asterisk kernel: asterisk[5537] trap invalid opcode
 rip:2b2bd2295a46 rsp:7fffecee8670 error:0
 Mar 28 00:23:21 srv01-asterisk kernel: asterisk[5589] trap invalid opcode
 rip:2ae2266a4a46 rsp:73f99eb0 error:0

 Meu uname -a

 2.6.18-348.3.1.el5 #1 SMP Mon Mar 11 19:39:25 EDT 2013 x86_64 x86_64
 x86_64 GNU/Linux

 Meu processador é este

 # cat /proc/cpuinfo
 processor : 0
 vendor_id : GenuineIntel
 cpu family : 15
 model : 6
 model name :   Intel(R) Pentium(R) D CPU 3.20GHz
 stepping : 5
 cpu MHz : 3192.176
 cache size : 2048 KB
 physical id : 0
 siblings : 2
 core id : 0
 cpu cores : 2
 apicid : 0
 fpu : yes
 fpu_exception : yes
 cpuid level : 6
 wp : yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
 constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
 bogomips : 6384.35
 clflush size : 64
 cache_alignment : 128
 address sizes : 36 bits physical, 48 bits virtual
 power management:

 processor : 1
 vendor_id : GenuineIntel
 cpu family : 15
 model : 6
 model name :   Intel(R) Pentium(R) D CPU 3.20GHz
 stepping : 5
 cpu MHz : 3192.176
 cache size : 2048 KB
 physical id : 0
 siblings : 2
 core id : 1
 cpu cores : 2
 apicid : 1
 fpu : yes
 fpu_exception : yes
 cpuid level : 6
 wp : yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
 constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
 bogomips : 6384.56
 clflush size : 64
 cache_alignment : 128
 address sizes : 36 bits physical, 48 bits virtual
 power management:







 On Tue, Mar 26, 2013 at 9:12 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-28 Por tôpico Alexandre Cavalcante Alencar
Pelo contrário,

Perguntei porque ele está setando o timers.cas_persistence_check no
advanced protocol file...

Sds


Alexandre Alencar
Twitter @alexandreitpro
http://blog.alexandrealencar.net/
http://www.alexandrealencar.net/
http://www.alexandrealencar.com
http://www.servicosdeti.com.br/
COBIT, ITIL, CSM, LPI, MCP-I



2013/3/28 Raphael Rodrigues raphael...@gmail.com

 Não se esqueça de ativar o CAS Persistant Check assim como o mestre
 Alexandre sugeriu.

 boa sorte.

 abraço


 2013/3/28 Hudson Cardoso hudsoncard...@hotmail.com

 Parece que ja tem um asterisk rodando em outra console
 Experimentar formatar a maquina e instalar do zero
 faca um teste em uma VM .


 Hudson
 (048) 8413-7000

 Para quem nao cre, nenhuma prova converte,Para aquele que cre, nenhuma prova 
 precisa.



 --
 From: deny.san...@gmail.com
 Date: Thu, 28 Mar 2013 00:27:12 -0300
 To: asteriskbrasil@listas.asteriskbrasil.org
 Subject: Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel



 On Mar 27, 2013, at 1:04 PM, Alexandre Cavalcante Alencar wrote:

 Cadê seu protocol file?

 Você ativou CAS Persistant Check?

 Sds


 Boa noite Alexandre, eu acabei reinstalando o asterisk com o freepbx
 novamente porem estou com o seguinte erro agora , nao consigo subir o
 asterisk de forma alguma, ele me gera o erro abaixo no messages e tambem
 entra em safe mode

 Erro ao startar o asterisk amportal start ou /etc/init.d/asterisk

 /usr/sbin/safe_asterisk: line 145:  7517 Illegal instruction (core
 dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} 
 /dev/${TTY} 21  /dev/${TTY}
 Asterisk ended with exit status 132
 Asterisk exited on signal 4.
 Automatically restarting Asterisk.
 /usr/sbin/safe_asterisk: line 145:  7604 Illegal instruction (core
 dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} 
 /dev/${TTY} 21  /dev/${TTY}
 Asterisk ended with exit status 132
 Asterisk exited on signal 4.
 Automatically restarting Asterisk.


 Erro no messages

 Mar 28 00:23:02 srv01-asterisk kernel: asterisk[5395] trap invalid opcode
 rip:2b77e45f3a46 rsp:7fff79c23990 error:0
 Mar 28 00:23:07 srv01-asterisk kernel: asterisk[5444] trap invalid opcode
 rip:2b22e72a7a46 rsp:7fffca5d7e50 error:0
 Mar 28 00:23:12 srv01-asterisk kernel: asterisk[5494] trap invalid opcode
 rip:2b4cbc5f3a46 rsp:7fff29978d50 error:0
 Mar 28 00:23:17 srv01-asterisk kernel: asterisk[5537] trap invalid opcode
 rip:2b2bd2295a46 rsp:7fffecee8670 error:0
 Mar 28 00:23:21 srv01-asterisk kernel: asterisk[5589] trap invalid opcode
 rip:2ae2266a4a46 rsp:73f99eb0 error:0

 Meu uname -a

 2.6.18-348.3.1.el5 #1 SMP Mon Mar 11 19:39:25 EDT 2013 x86_64 x86_64
 x86_64 GNU/Linux

 Meu processador é este

 # cat /proc/cpuinfo
 processor : 0
 vendor_id : GenuineIntel
 cpu family : 15
 model : 6
 model name :   Intel(R) Pentium(R) D CPU 3.20GHz
 stepping : 5
 cpu MHz : 3192.176
 cache size : 2048 KB
 physical id : 0
 siblings : 2
 core id : 0
 cpu cores : 2
 apicid : 0
 fpu : yes
 fpu_exception : yes
 cpuid level : 6
 wp : yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
 pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
 constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
 bogomips : 6384.35
 clflush size : 64
 cache_alignment : 128
 address sizes : 36 bits physical, 48 bits virtual
 power management:

 processor : 1
 vendor_id : GenuineIntel
 cpu family : 15
 model : 6
 model name :   Intel(R) Pentium(R) D CPU 3.20GHz
 stepping : 5
 cpu MHz : 3192.176
 cache size : 2048 KB
 physical id : 0
 siblings : 2
 core id : 1
 cpu cores : 2
 apicid : 1
 fpu : yes
 fpu_exception : yes
 cpuid level : 6
 wp : yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
 pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
 constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
 bogomips : 6384.56
 clflush size : 64
 cache_alignment : 128
 address sizes : 36 bits physical, 48 bits virtual
 power management:







 On Tue, Mar 26, 2013 at 9:12 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-27 Por tôpico Alexandre Cavalcante Alencar
Cadê seu protocol file?

Você ativou CAS Persistant Check?

Sds

Alexandre Alencar
Twitter @alexandreitpro
http://blog.alexandrealencar.net/
http://www.alexandrealencar.net/
http://www.alexandrealencar.com
http://www.servicosdeti.com.br/
COBIT, ITIL, CSM, LPI, MCP-I



On Tue, Mar 26, 2013 at 9:12 PM, deny.san...@gmail.com 
deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in
 new stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend)
 in new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'







 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

  Posta o chan_dahdi.conf

 Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62



 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando este
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an
 unknown call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new
 stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 2
  MFC/R2 call end on channel 2
  Chan 1 - Handling persistent pattern 0x08
  Chan 1 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-27 Por tôpico deny.san...@gmail.com

On Mar 27, 2013, at 1:04 PM, Alexandre Cavalcante Alencar wrote:

 Cadê seu protocol file?
 
 Você ativou CAS Persistant Check?
 
 Sds
 

Boa noite Alexandre, eu acabei reinstalando o asterisk com o freepbx novamente 
porem estou com o seguinte erro agora , nao consigo subir o asterisk de forma 
alguma, ele me gera o erro abaixo no messages e tambem entra em safe mode 

Erro ao startar o asterisk amportal start ou /etc/init.d/asterisk 

/usr/sbin/safe_asterisk: line 145:  7517 Illegal instruction (core dumped) 
nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS}  /dev/${TTY} 
21  /dev/${TTY}
Asterisk ended with exit status 132
Asterisk exited on signal 4.
Automatically restarting Asterisk.
/usr/sbin/safe_asterisk: line 145:  7604 Illegal instruction (core dumped) 
nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS}  /dev/${TTY} 
21  /dev/${TTY}
Asterisk ended with exit status 132
Asterisk exited on signal 4.
Automatically restarting Asterisk.


Erro no messages 

Mar 28 00:23:02 srv01-asterisk kernel: asterisk[5395] trap invalid opcode 
rip:2b77e45f3a46 rsp:7fff79c23990 error:0
Mar 28 00:23:07 srv01-asterisk kernel: asterisk[5444] trap invalid opcode 
rip:2b22e72a7a46 rsp:7fffca5d7e50 error:0
Mar 28 00:23:12 srv01-asterisk kernel: asterisk[5494] trap invalid opcode 
rip:2b4cbc5f3a46 rsp:7fff29978d50 error:0
Mar 28 00:23:17 srv01-asterisk kernel: asterisk[5537] trap invalid opcode 
rip:2b2bd2295a46 rsp:7fffecee8670 error:0
Mar 28 00:23:21 srv01-asterisk kernel: asterisk[5589] trap invalid opcode 
rip:2ae2266a4a46 rsp:73f99eb0 error:0

Meu uname -a 

2.6.18-348.3.1.el5 #1 SMP Mon Mar 11 19:39:25 EDT 2013 x86_64 x86_64 x86_64 
GNU/Linux

Meu processador é este 

# cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 6
model name  :   Intel(R) Pentium(R) D CPU 3.20GHz
stepping: 5
cpu MHz : 3192.176
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 6
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm 
constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
bogomips: 6384.35
clflush size: 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 15
model   : 6
model name  :   Intel(R) Pentium(R) D CPU 3.20GHz
stepping: 5
cpu MHz : 3192.176
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 6
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm 
constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
bogomips: 6384.56
clflush size: 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:



 
 
 
 
 On Tue, Mar 26, 2013 at 9:12 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:
 
 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:
 
 Olá
 
 Qual seu intuito e o conteúdo do protocol file?
 
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 
 Não use o protocol file se não souber exatamente o que está fazendo. No 
 diretório doc/asterisk/br tem um README com vários exemplos para as 
 operadoras brasileiras, incluindo a Embratel.
 
 
 
 Ola Alexandre, eu estava utilizando justamente com a configuração para a 
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem 
 abaixo porem ele gera o Hangup no final e nem chega a chamar.
 
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
 with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == 

[AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com
Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 da 
embratel porem o mesmo quando recebi chamadas esta gerando este erro no dahdi e 
derrubando a ligação , alguma ideia ? 

Obrigado 

New MFC/R2 call detected on chan 1.
Chan 2 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 2.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
   -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
   -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
with DID set to 1) in new stack
   -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
   -- Goto (from-trunk,s,2)
   -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
   -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 2 - Handling persistent pattern 0x08
Chan 2 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 2
MFC/R2 call end on channel 2
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
 == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
   -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new stack
   -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
stack
   -- Goto (macro-hangupcall,s,3)
   -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
0?Set(CDR(recordingfile)=)) in new stack
   -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
 == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' in 
macro 'hangupcall'
 == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
MFC/R2 call end on channel 1
   -- Hungup 'DAHDI/1-1'




MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
[2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
1 - MF back cycle timed out!
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 1 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
Cycle Timeout
Chan 1 - Handling persistent pattern 0x08
[2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 1
[2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
2 - MF back cycle timed out!
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 2 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi Frequency 
Cycle Timeout
Chan 2 - Handling persistent pattern 0x08
[2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 2
___
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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  www.digivoice.com.br
___
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-unsubscr...@listas.asteriskbrasil.org


Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Patrick EL Youssef

Posta o chan_dahdi.conf

Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:

Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 da 
embratel porem o mesmo quando recebi chamadas esta gerando este erro no dahdi e 
derrubando a ligação , alguma ideia ?

Obrigado

New MFC/R2 call detected on chan 1.
Chan 2 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 2.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call with 
DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 2 - Handling persistent pattern 0x08
Chan 2 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 2
MFC/R2 call end on channel 2
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' in 
macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'




MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
[2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
1 - MF back cycle timed out!
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 1 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
Cycle Timeout
Chan 1 - Handling persistent pattern 0x08
[2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 1
[2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
2 - MF back cycle timed out!
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 2 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi Frequency 
Cycle Timeout
Chan 2 - Handling persistent pattern 0x08
[2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 2
___
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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  www.digivoice.com.br
___
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-unsubscr...@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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  www.digivoice.com.br
___
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.

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

 Posta o chan_dahdi.conf

Este é chan_dahdi.conf

trunkgroups]

[channels]

language=br

#include chan_dahdi_additional.conf
#include dahdi-channels.conf

usecallerid=yes
;hidecallerid=yes
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
immediate=no
echocancel=yes
echocancelwhenbridged=yes
faxdetect=both

dahd_channels

signalling=mfcr2
mfcr2_variant=BR
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
mfcr2_logdir=span1
mfcr2_logging=all
faxdetect=both

context=from-trunk
group=0
signalling=mfcr2
callgroup=1
pickupgroup=1
channel = 1-15
channel = 17-31
context=from-trunk
group=1
signalling=mfcr2
callgroup=2
pickupgroup=2
channel = 32-46
channel = 48-62



 
 Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
 Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 
 da embratel porem o mesmo quando recebi chamadas esta gerando este erro no 
 dahdi e derrubando a ligação , alguma ideia ?
 
 Obrigado
 
 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
 with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
 stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
 new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' 
 in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'
 
 
 
 
 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 1 - MF back cycle timed out!
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = 
 Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group = 
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
 Cycle Timeout
 Chan 1 - Handling persistent pattern 0x08
 [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
 Far end unblocked on chan 1
 [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 2 - MF back cycle timed out!
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 2 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = 
 Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group = 
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi Frequency 
 Cycle Timeout
 Chan 2 - Handling persistent pattern 0x08
 [2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
 Far end unblocked on chan 2
 ___
 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.
 ___
 DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
 20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
 Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  
 www.digivoice.com.br
 ___
 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 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Patrick EL Youssef
Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas duas 
opções a mais que o seu


mfcr2_immediate_accept=no
mfcr2_forced_release=no

O pessoal com mais experiencia com placas que usam dahdi podem saber o q é

Patrick

Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:

On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:


Posta o chan_dahdi.conf

Este é chan_dahdi.conf

trunkgroups]

[channels]

language=br

#include chan_dahdi_additional.conf
#include dahdi-channels.conf

usecallerid=yes
;hidecallerid=yes
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
immediate=no
echocancel=yes
echocancelwhenbridged=yes
faxdetect=both

dahd_channels

signalling=mfcr2
mfcr2_variant=BR
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
mfcr2_logdir=span1
mfcr2_logging=all
faxdetect=both

context=from-trunk
group=0
signalling=mfcr2
callgroup=1
pickupgroup=1
channel = 1-15
channel = 17-31
context=from-trunk
group=1
signalling=mfcr2
callgroup=2
pickupgroup=2
channel = 32-46
channel = 48-62




Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:

Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 da 
embratel porem o mesmo quando recebi chamadas esta gerando este erro no dahdi e 
derrubando a ligação , alguma ideia ?

Obrigado

New MFC/R2 call detected on chan 1.
Chan 2 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 2.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call with 
DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 2 - Handling persistent pattern 0x08
Chan 2 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 2
MFC/R2 call end on channel 2
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' in 
macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'




MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
[2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
1 - MF back cycle timed out!
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 1 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
Cycle Timeout
Chan 1 - Handling persistent pattern 0x08
[2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 1
[2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
2 - MF back cycle timed out!
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 2 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi Frequency 
Cycle Timeout
Chan 2 - Handling persistent pattern 0x08
[2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 2
___
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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:

 Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas duas 
 opções a mais que o seu
 
 mfcr2_immediate_accept=no
 mfcr2_forced_release=no
 
 O pessoal com mais experiencia com placas que usam dahdi podem saber o q é
 
 Patrick

Valew Patrick, estou achando que é problema de hardware (balon , cabo BNC, cabo 
e1) mais vou tentar com estas opções que voce me passou 

Valew

 
 Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:
 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:
 
 Posta o chan_dahdi.conf
 Este é chan_dahdi.conf
 
 trunkgroups]
 
 [channels]
 
 language=br
 
 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf
 
 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both
 
 dahd_channels
 
 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both
 
 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62
 
 
 
 Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
 Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link 
 R2 da embratel porem o mesmo quando recebi chamadas esta gerando este erro 
 no dahdi e derrubando a ligação , alguma ideia ?
 
 Obrigado
 
 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown 
 call with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
 stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
 new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 
 'DAHDI/1-1' in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'
 
 
 
 
 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 1 - MF back cycle timed out!
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State 
 = Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group = 
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi 
 Frequency Cycle Timeout
 Chan 1 - Handling persistent pattern 0x08
 [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 
 dahdi_r2_on_line_idle: Far end unblocked on chan 1
 [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 2 - MF back cycle timed out!
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 2 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State 
 = Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group = 
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi 
 Frequency Cycle Timeout
 Chan 2 - Handling persistent pattern 0x08
 [2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 
 dahdi_r2_on_line_idle: Far end unblocked on chan 2
 ___
 KHOMP: completa linha de placas externas FXO, FXS, GSM e E1;
 Media 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Nildo Furtado
segue meu chandahdi.conf verifica se ajuda em algo, funcionando
perfeitamente aqui ...


[channels]
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echotrainning=yes
echocancelwhenbridged=yes

signalling=mfcr2
mfcr2_variant=br
mfcr2_get_ani_first=yes
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_logdir=span1
mfcr2_logging=all




group=1
callgroup=1
pickupgroup=1
callerid=asreceived
context=oi

channel = 1-15,17-31



2013/3/26 deny.san...@gmail.com deny.san...@gmail.com


 On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:

  Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas duas
 opções a mais que o seu

 mfcr2_immediate_accept=no
 mfcr2_forced_release=no

 O pessoal com mais experiencia com placas que usam dahdi podem saber o q é

 Patrick


 Valew Patrick, estou achando que é problema de hardware (balon , cabo BNC,
 cabo e1) mais vou tentar com estas opções que voce me passou

 Valew


 Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:

 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:


  Posta o chan_dahdi.conf

  Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62




  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:

  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 
 da embratel porem o mesmo quando recebi chamadas esta gerando este erro no 
 dahdi e derrubando a ligação , alguma ideia ?

 Obrigado

 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
 with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
 stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
 stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' 
 in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'




 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 1 - MF back cycle timed out!
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 
 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize 
 ACK Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward 
 Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
 Cycle Timeout
 Chan 1 - Handling persistent pattern 0x08
 [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
 Far end unblocked on chan 1
 [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: 
 Chan 2 - MF back cycle timed out!
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 
 2 - Protocol 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Patrick EL Youssef
Se esta sincronizado  e a chamada chegando creio que nao seja hardware, 
a não ser que isso aconteça aleatoriamente.


patrick

Em 26-03-2013 16:11, deny.san...@gmail.com escreveu:


On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:

Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas 
duas opções a mais que o seu


mfcr2_immediate_accept=no
mfcr2_forced_release=no

O pessoal com mais experiencia com placas que usam dahdi podem saber 
o q é


Patrick


Valew Patrick, estou achando que é problema de hardware (balon , cabo 
BNC, cabo e1) mais vou tentar com estas opções que voce me passou


Valew



Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:

On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:


Posta o chan_dahdi.conf

Este é chan_dahdi.conf

trunkgroups]

[channels]

language=br

#include chan_dahdi_additional.conf
#include dahdi-channels.conf

usecallerid=yes
;hidecallerid=yes
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
immediate=no
echocancel=yes
echocancelwhenbridged=yes
faxdetect=both

dahd_channels

signalling=mfcr2
mfcr2_variant=BR
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
mfcr2_logdir=span1
mfcr2_logging=all
faxdetect=both

context=from-trunk
group=0
signalling=mfcr2
callgroup=1
pickupgroup=1
channel = 1-15
channel = 17-31
context=from-trunk
group=1
signalling=mfcr2
callgroup=2
pickupgroup=2
channel = 32-46
channel = 48-62




Em 26-03-2013 14:55,deny.san...@gmail.com  escreveu:

Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link R2 da 
embratel porem o mesmo quando recebi chamadas esta gerando este erro no dahdi e 
derrubando a ligação , alguma ideia ?

Obrigado

New MFC/R2 call detected on chan 1.
Chan 2 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 2.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call with 
DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 2 - Handling persistent pattern 0x08
Chan 2 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 2
MFC/R2 call end on channel 2
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' in 
macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'




MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
[2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
1 - MF back cycle timed out!
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 1 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
Cycle Timeout
Chan 1 - Handling persistent pattern 0x08
[2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 1
[2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
2 - MF back cycle timed out!
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 2 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Accepted Call Transmitted, MF Group = Backward Group B, 
CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi Frequency 
Cycle Timeout
Chan 2 - Handling persistent pattern 0x08
[2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161 dahdi_r2_on_line_idle: 
Far end unblocked on chan 2
___
KHOMP: 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 4:39 PM, Patrick EL Youssef wrote:

 Se esta sincronizado  e a chamada chegando creio que nao seja hardware, a não 
 ser que isso aconteça aleatoriamente.
 
 patrick

Eu coloquei uma central antiga com asterisk 1.2 e zaptel ainda e funcionou com 
a mesma placa , cabos etc , entao nao é hardware mesmo é alguma configuração do 
dahdi que nao esta batendo . Vou tentar a configuracao que o amigo passou 
tambem .

 
 Em 26-03-2013 16:11, deny.san...@gmail.com escreveu:
 
 On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:
 
 Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas duas 
 opções a mais que o seu
 
 mfcr2_immediate_accept=no
 mfcr2_forced_release=no
 
 O pessoal com mais experiencia com placas que usam dahdi podem saber o q é
 
 Patrick
 
 Valew Patrick, estou achando que é problema de hardware (balon , cabo BNC, 
 cabo e1) mais vou tentar com estas opções que voce me passou 
 
 Valew
 
 
 Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:
 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:
 
 Posta o chan_dahdi.conf
 Este é chan_dahdi.conf
 
 trunkgroups]
 
 [channels]
 
 language=br
 
 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf
 
 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both
 
 dahd_channels
 
 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both
 
 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62
 
 
 
 Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
 Bom dia amigos gostaria de uma ajuda de todos, estou configurando um 
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando 
 este erro no dahdi e derrubando a ligação , alguma ideia ?
 
 Obrigado
 
 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown 
 call with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in 
 new stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) 
 in new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new 
 stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 
 'DAHDI/1-1' in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'
 
 
 
 
 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 
 dahdi_r2_write_log: Chan 1 - MF back cycle timed out!
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 
 State = Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF 
 Group = Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915 
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi 
 Frequency Cycle Timeout
 Chan 1 - Handling persistent pattern 0x08
 [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161 
 dahdi_r2_on_line_idle: Far end unblocked on chan 1
 [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 
 dahdi_r2_write_log: Chan 2 - MF back cycle timed out!
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log: 
 Chan 2 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 
 State = Seize ACK Transmitted, MF state = Accepted Call 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 4:38 PM, Nildo Furtado wrote:

 segue meu chandahdi.conf verifica se ajuda em algo, funcionando perfeitamente 
 aqui ...
 
 
 [channels]
 usecallerid=yes
 callwaiting=yes
 usecallingpres=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 canpark=yes
 cancallforward=yes
 callreturn=yes
 echocancel=yes
 echotrainning=yes
 echocancelwhenbridged=yes
 
 signalling=mfcr2
 mfcr2_variant=br
 mfcr2_get_ani_first=yes
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_logdir=span1
 mfcr2_logging=all
 
 
 
 
 group=1
 callgroup=1
 pickupgroup=1
 callerid=asreceived
 context=oi
 
 channel = 1-15,17-31

Adicionei algumas opções no meu que tinha nas suas configuracoes porem mesmo 
erro , este teste foi agora ele cai a chamada no primeiro toque 

[2013-03-26 18:13:57] WARNING[6618]: chan_dahdi.c:4127 dahdi_r2_write_log: Chan 
1 - MF back cycle timed out!
[2013-03-26 18:13:57] ERROR[6618]: chan_dahdi.c:4130 dahdi_r2_write_log: Chan 1 
- Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK 
Transmitted, MF state = Category Request Transmitted, MF Group = Backward Group 
A, CAS = 0x00
DNIS = 1, ANI = , MF = 0x31
[2013-03-26 18:13:57] ERROR[6618]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi Frequency 
Cycle Timeout
Chan 1 - Handling persistent pattern 0x08




 
 
 
 2013/3/26 deny.san...@gmail.com deny.san...@gmail.com
 
 On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:
 
 Cara eu não sei o que pode ser porem nos meus arquivos eu uso estas duas 
 opções a mais que o seu
 
 mfcr2_immediate_accept=no
 mfcr2_forced_release=no
 
 O pessoal com mais experiencia com placas que usam dahdi podem saber o q é
 
 Patrick
 
 Valew Patrick, estou achando que é problema de hardware (balon , cabo BNC, 
 cabo e1) mais vou tentar com estas opções que voce me passou 
 
 Valew
 
 
 Em 26-03-2013 15:18, deny.san...@gmail.com escreveu:
 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:
 
 Posta o chan_dahdi.conf
 Este é chan_dahdi.conf
 
 trunkgroups]
 
 [channels]
 
 language=br
 
 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf
 
 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both
 
 dahd_channels
 
 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both
 
 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62
 
 
 
 Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
 Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link 
 R2 da embratel porem o mesmo quando recebi chamadas esta gerando este 
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
 Obrigado
 
 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown 
 call with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
 stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
 new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new 
 stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 
 'DAHDI/1-1' in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'
 
 
 
 
 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 
 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Roger Pitigliani
Derruba sempre?

Checa os baloons e cabos/conectores, por mais que não pareça, pode ser.

Posta o resultado do comando:
CLI dahdi show status


Att,

2013/3/26 deny.san...@gmail.com deny.san...@gmail.com

 Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link
 R2 da embratel porem o mesmo quando recebi chamadas esta gerando este erro
 no dahdi e derrubando a ligação , alguma ideia ?

 Obrigado

 New MFC/R2 call detected on chan 1.
 Chan 2 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 2.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new
 stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 2 - Handling persistent pattern 0x08
 Chan 2 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 2
 MFC/R2 call end on channel 2
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new
 stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in
 new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'




 MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
 [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log:
 Chan 1 - MF back cycle timed out!
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log:
 Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State =
 Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group =
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi
 Frequency Cycle Timeout
 Chan 1 - Handling persistent pattern 0x08
 [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161
 dahdi_r2_on_line_idle: Far end unblocked on chan 1
 [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127 dahdi_r2_write_log:
 Chan 2 - MF back cycle timed out!
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130 dahdi_r2_write_log:
 Chan 2 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State =
 Seize ACK Transmitted, MF state = Accepted Call Transmitted, MF Group =
 Backward Group B, CAS = 0x00
 DNIS = 1, ANI = , MF = 0x31
 [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi
 Frequency Cycle Timeout
 Chan 2 - Handling persistent pattern 0x08
 [2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161
 dahdi_r2_on_line_idle: Far end unblocked on chan 2
 ___
 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.
 ___
 DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
 20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
 Centro Treinamento - Curso de PABX IP -  Asterisk  - Site
 www.digivoice.com.br
 ___
 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-unsubscr...@listas.asteriskbrasil.org




-- 
--
Roger Pitigliani
rogerwin...@gmail.com
Skype: roger.pitigliani
___
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.
___
DIGIVOICE  Fabricante de Placas de Voz e Channel Bank
20 anos de experiência com E1(R2/ISDN), FXS, FXO e GSM
Centro Treinamento - Curso de PABX IP -  Asterisk  - Site  www.digivoice.com.br

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Patrick EL Youssef

Cara

Pelo warning você tem que mexer nesse parametro

mfcr2_mfback_timeout=-1

Aumenta ele e testa

Patrick


Em 26-03-2013 18:15, deny.san...@gmail.com escreveu:


On Mar 26, 2013, at 4:38 PM, Nildo Furtado wrote:

segue meu chandahdi.conf verifica se ajuda em algo, funcionando 
perfeitamente aqui ...



[channels]
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echotrainning=yes
echocancelwhenbridged=yes

signalling=mfcr2
mfcr2_variant=br
mfcr2_get_ani_first=yes
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_logdir=span1
mfcr2_logging=all




group=1
callgroup=1
pickupgroup=1
callerid=asreceived
context=oi

channel = 1-15,17-31


Adicionei algumas opções no meu que tinha nas suas configuracoes porem 
mesmo erro , este teste foi agora ele cai a chamada no primeiro toque


[2013-03-26 18:13:57] WARNING[6618]: chan_dahdi.c:4127 
dahdi_r2_write_log: Chan 1 - MF back cycle timed out!
[2013-03-26 18:13:57] ERROR[6618]: chan_dahdi.c:4130 
dahdi_r2_write_log: Chan 1 - Protocol error. Reason = Multi Frequency 
Cycle Timeout, R2 State = Seize ACK Transmitted, MF state = Category 
Request Transmitted, MF Group = Backward Group A, CAS = 0x00

DNIS = 1, ANI = , MF = 0x31
[2013-03-26 18:13:57] ERROR[6618]: chan_dahdi.c:3915 
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi 
Frequency Cycle Timeout

Chan 1 - Handling persistent pattern 0x08








2013/3/26 deny.san...@gmail.com mailto:deny.san...@gmail.com 
deny.san...@gmail.com mailto:deny.san...@gmail.com



On Mar 26, 2013, at 4:04 PM, Patrick EL Youssef wrote:


Cara eu não sei o que pode ser porem nos meus arquivos eu uso
estas duas opções a mais que o seu

mfcr2_immediate_accept=no
mfcr2_forced_release=no

O pessoal com mais experiencia com placas que usam dahdi podem
saber o q é

Patrick


Valew Patrick, estou achando que é problema de hardware (balon ,
cabo BNC, cabo e1) mais vou tentar com estas opções que voce me
passou

Valew



Em 26-03-2013 15 tel:26-03-2013%2015:18, deny.san...@gmail.com
mailto:deny.san...@gmail.com escreveu:

On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:


Posta o chan_dahdi.conf

Este é chan_dahdi.conf

trunkgroups]

[channels]

language=br

#include chan_dahdi_additional.conf
#include dahdi-channels.conf

usecallerid=yes
;hidecallerid=yes
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
immediate=no
echocancel=yes
echocancelwhenbridged=yes
faxdetect=both

dahd_channels

signalling=mfcr2
mfcr2_variant=BR
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
mfcr2_logdir=span1
mfcr2_logging=all
faxdetect=both

context=from-trunk
group=0
signalling=mfcr2
callgroup=1
pickupgroup=1
channel = 1-15
channel = 17-31
context=from-trunk
group=1
signalling=mfcr2
callgroup=2
pickupgroup=2
channel = 32-46
channel = 48-62




Em26-03-2013 14  tel:26-03-2013%2014:55,deny.san...@gmail.com  
mailto:deny.san...@gmail.com  escreveu:

Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link 
R2 da embratel porem o mesmo quando recebi chamadas esta gerando este erro no 
dahdi e derrubando a ligação , alguma ideia ?

Obrigado

New MFC/R2 call detected on chan 1.
Chan 2 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 2.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 2 - Handling persistent pattern 0x08
Chan 2 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 2
MFC/R2 call end on channel 2
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
new stack
-- Goto (macro-hangupcall,s,3)
   

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 6:27 PM, Roger Pitigliani wrote:

 Derruba sempre?
 
 Checa os baloons e cabos/conectores, por mais que não pareça, pode ser.
 
 Posta o resultado do comando:
 CLI dahdi show status
 

Segue , só utilizo o SPAN 01 

dahdi show channels
   Chan Extension  Context Language   MOH InterpretBlocked
State 
 pseudodefaultdefault 
In Service
  1from-trunk  br default 
In Service
  2from-trunk  br default 
In Service
  3from-trunk  br default 
In Service
  4from-trunk  br default 
In Service
  5from-trunk  br default 
In Service
  6from-trunk  br default 
In Service
  7from-trunk  br default 
In Service
  8from-trunk  br default 
In Service
  9from-trunk  br default 
In Service
 10from-trunk  br default 
In Service
 11from-trunk  br default 
In Service
 12from-trunk  br default 
In Service
 13from-trunk  br default 
In Service
 14from-trunk  br default 
In Service
 15from-trunk  br default 
In Service
 17from-trunk  br default 
In Service
 18from-trunk  br default 
In Service
 19from-trunk  br default 
In Service
 20from-trunk  br default 
In Service
 21from-trunk  br default 
In Service
 22from-trunk  br default 
In Service
 23from-trunk  br default 
In Service
 24from-trunk  br default 
In Service
 25from-trunk  br default 
In Service
 26from-trunk  br default 
In Service
 27from-trunk  br default 
In Service
 28from-trunk  br default 
In Service
 29from-trunk  br default 
In Service
 30from-trunk  br default 
In Service
 31from-trunk  br default 
In Service
 32from-trunk  br default   R 
In Service
 33from-trunk  br default   R 
In Service
 34from-trunk  br default   R 
In Service
 35from-trunk  br default   R 
In Service
 36from-trunk  br default   R 
In Service
 37from-trunk  br default   R 
In Service
 38from-trunk  br default   R 
In Service
 39from-trunk  br default   R 
In Service
 40from-trunk  br default   R 
In Service
 41from-trunk  br default   R 
In Service
 42from-trunk  br default   R 
In Service
 43from-trunk  br default   R 
In Service
 44from-trunk  br default   R 
In Service
 45from-trunk  br default   R 
In Service
 46from-trunk  br default   R 
In Service
 48from-trunk  br default   R 
In Service
 49from-trunk  br default   R 
In Service
 50from-trunk  br default   R 
In Service
 51from-trunk  br default   R 
In Service
 52from-trunk  br default   R 
In Service
 53from-trunk  br default 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Alexandre Cavalcante Alencar
Olá

Qual seu intuito e o conteúdo do protocol file?

mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

Não use o protocol file se não souber exatamente o que está fazendo. No
diretório doc/asterisk/br tem um README com vários exemplos para as
operadoras brasileiras, incluindo a Embratel.



Alexandre Alencar
Twitter @alexandreitpro
http://blog.alexandrealencar.net/
http://www.alexandrealencar.net/
http://www.alexandrealencar.com
http://www.servicosdeti.com.br/
COBIT, ITIL, CSM, LPI, MCP-I



On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

  Posta o chan_dahdi.conf

 Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62



 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando este
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an
 unknown call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 2
  MFC/R2 call end on channel 2
  Chan 1 - Handling persistent pattern 0x08
  Chan 1 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in
 new stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend)
 in new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
  MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'
 
 
 
 
  MFC/R2 call offered on chan 2. ANI = , DNIS = 1, Category = *Unknown*
  [2013-03-26 10:43:50] WARNING[5264]: chan_dahdi.c:4127
 dahdi_r2_write_log: Chan 1 - MF back cycle timed out!
  [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:4130
 dahdi_r2_write_log: Chan 1 - Protocol error. Reason = Multi Frequency Cycle
 Timeout, R2 State = Seize ACK Transmitted, MF state = Accepted Call
 Transmitted, MF Group = Backward Group B, CAS = 0x00
  DNIS = 1, ANI = , MF = 0x31
  [2013-03-26 10:43:50] ERROR[5264]: chan_dahdi.c:3915
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Multi
 Frequency Cycle Timeout
  Chan 1 - Handling persistent pattern 0x08
  [2013-03-26 10:43:51] NOTICE[5264]: chan_dahdi.c:4161
 dahdi_r2_on_line_idle: Far end unblocked on chan 1
  [2013-03-26 10:43:52] WARNING[5264]: chan_dahdi.c:4127
 dahdi_r2_write_log: Chan 2 - MF back cycle timed out!
  [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:4130
 dahdi_r2_write_log: Chan 2 - Protocol error. Reason = Multi Frequency Cycle
 Timeout, R2 State = Seize ACK Transmitted, MF state = Accepted Call
 Transmitted, MF Group = Backward Group B, CAS = 0x00
  DNIS = 1, ANI = , MF = 0x31
  [2013-03-26 10:43:52] ERROR[5264]: chan_dahdi.c:3915
 dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 2: Multi
 Frequency Cycle Timeout
  Chan 2 - Handling persistent pattern 0x08
  [2013-03-26 10:43:52] NOTICE[5264]: chan_dahdi.c:4161
 dahdi_r2_on_line_idle: Far end unblocked on chan 2
  

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá
 
 Qual seu intuito e o conteúdo do protocol file?
 
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 
 Não use o protocol file se não souber exatamente o que está fazendo. No 
 diretório doc/asterisk/br tem um README com vários exemplos para as 
 operadoras brasileiras, incluindo a Embratel.
 
 

Ola Alexandre, eu estava utilizando justamente com a configuração para a 
Embratel , fiz algumas alterações e agora estou recebendo esta mensagem abaixo 
porem ele gera o Hangup no final e nem chega a chamar.

Chan 1 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 1.
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
MFC/R2 call end on channel 1
Chan 1 - Handling persistent pattern 0x00
New MFC/R2 call detected on chan 1.
MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
MFC/R2 call has been accepted on backward channel 1
-- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new stack
-- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
with DID set to 1) in new stack
-- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
-- Goto (from-trunk,s,2)
-- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
-- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
Chan 1 - Handling persistent pattern 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
  == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
-- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new stack
-- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in new 
stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
0?Set(CDR(recordingfile)=)) in new stack
-- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
  == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' in 
macro 'hangupcall'
  == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
MFC/R2 call end on channel 1
-- Hungup 'DAHDI/1-1'



 
 
 
 
 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:
 
 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:
 
  Posta o chan_dahdi.conf
 
 Este é chan_dahdi.conf
 
 trunkgroups]
 
 [channels]
 
 language=br
 
 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf
 
 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both
 
 dahd_channels
 
 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both
 
 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62
 
 
 
 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link 
  R2 da embratel porem o mesmo quando recebi chamadas esta gerando este erro 
  no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
  stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown 
  call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 2
  MFC/R2 call end on channel 2
  Chan 1 - Handling persistent pattern 0x08
  Chan 1 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
  stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
  new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
  0?Set(CDR(recordingfile)=)) in new stack
 -- Executing 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Nildo Furtado
Cara, qual a operadora que esta fornecendo o seu link E1? Se for a OI, pede
uma ATIVITEC com LOG de ligação com o testador de R2 que equipe da oi usa,
blz ser outra operadora coloca ai qual é, para tentar ajuda-lo... pois
parece que o seu link nao esta recebendo o numero ANI de ninguem   o eu
aqui aparece assim ...

[2013-03-26 21:54:28] New MFC/R2 call detected on chan 10.
[2013-03-26 21:54:32] MFC/R2 call offered on chan 10. ANI = 2178592532,
DNIS = 7650, Category = National Subscriber
[2013-03-26 21:54:32] MFC/R2 call has been accepted on backward channel 10





2013/3/26 deny.san...@gmail.com deny.san...@gmail.com


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in
 new stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend)
 in new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'







 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

  Posta o chan_dahdi.conf

 Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62



 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando este
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an
 unknown call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new
 stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Raphael Rodrigues
Você esta usando alguma distribuição tipo elastix, asterisknow?

Caso sim, tente realizar a troca do contexto nos arquivos customizados das
distribuições, geralmente fica em /etc/asterisk/extencions_custom.conf,
crie um contexto de entrada e faça um teste.


abçs



2013/3/26 deny.san...@gmail.com deny.san...@gmail.com


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in
 new stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend)
 in new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'







 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

  Posta o chan_dahdi.conf

 Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62



 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando este
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an
 unknown call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new
 stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 2
  MFC/R2 call end on channel 2
  Chan 1 - Handling persistent pattern 0x08
  Chan 1 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico deny.san...@gmail.com

On Mar 26, 2013, at 10:06 PM, Raphael Rodrigues wrote:

 Você esta usando alguma distribuição tipo elastix, asterisknow?
 
 Caso sim, tente realizar a troca do contexto nos arquivos customizados das 
 distribuições, geralmente fica em /etc/asterisk/extencions_custom.conf, crie 
 um contexto de entrada e faça um teste.
 
 
 abçs
 

Ola amigo estou utilizando o freepbx 


 
 
 2013/3/26 deny.san...@gmail.com deny.san...@gmail.com
 
 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:
 
 Olá
 
 Qual seu intuito e o conteúdo do protocol file?
 
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 
 Não use o protocol file se não souber exatamente o que está fazendo. No 
 diretório doc/asterisk/br tem um README com vários exemplos para as 
 operadoras brasileiras, incluindo a Embratel.
 
 
 
 Ola Alexandre, eu estava utilizando justamente com a configuração para a 
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem 
 abaixo porem ele gera o Hangup no final e nem chega a chamar.
 
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
 stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown call 
 with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in new 
 stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend) in 
 new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1, 
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'DAHDI/1-1' 
 in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'
 
 
 
 
 
 
 
 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:
 
 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:
 
  Posta o chan_dahdi.conf
 
 Este é chan_dahdi.conf
 
 trunkgroups]
 
 [channels]
 
 language=br
 
 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf
 
 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both
 
 dahd_channels
 
 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both
 
 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62
 
 
 
 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um link 
  R2 da embratel porem o mesmo quando recebi chamadas esta gerando este 
  erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in new 
  stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown 
  call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
  Chan 2 - Handling persistent pattern 0x08
  Chan 2 - Far end disconnected. Reason: Normal Clearing
  MFC/R2 call disconnected on channel 2
  MFC/R2 call end on channel 2
  Chan 1 - Handling persistent pattern 0x08
  Chan 1 - 

Re: [AsteriskBrasil] DAHDI MFCR2 - Embratel

2013-03-26 Por tôpico Raphael Rodrigues
Bom nesse caso, localize o arquivo extencions_custom.conf e cria um
contexto lá ex:

[from-E1]

exten = X.,1,Dial(SIP/1000,30,tr)  ; só não esquecer de mudar o ramal.

faça um teste, geralmente é usado o from-pstn, o contexto from-trunk tem
algumas limitações.

abraço



Em 26 de março de 2013 22:15, deny.san...@gmail.com
deny.san...@gmail.comescreveu:


 On Mar 26, 2013, at 10:06 PM, Raphael Rodrigues wrote:

 Você esta usando alguma distribuição tipo elastix, asterisknow?

 Caso sim, tente realizar a troca do contexto nos arquivos customizados das
 distribuições, geralmente fica em /etc/asterisk/extencions_custom.conf,
 crie um contexto de entrada e faça um teste.


 abçs


 Ola amigo estou utilizando o freepbx




 2013/3/26 deny.san...@gmail.com deny.san...@gmail.com


 On Mar 26, 2013, at 6:56 PM, Alexandre Cavalcante Alencar wrote:

 Olá

 Qual seu intuito e o conteúdo do protocol file?

 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf

 Não use o protocol file se não souber exatamente o que está fazendo. No
 diretório doc/asterisk/br tem um README com vários exemplos para as
 operadoras brasileiras, incluindo a Embratel.



 Ola Alexandre, eu estava utilizando justamente com a configuração para a
 Embratel , fiz algumas alterações e agora estou recebendo esta mensagem
 abaixo porem ele gera o Hangup no final e nem chega a chamar.

 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
 MFC/R2 call end on channel 1
 Chan 1 - Handling persistent pattern 0x00
 New MFC/R2 call detected on chan 1.
 MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
 MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an unknown
 call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in new stack
 -- Executing [s@from-trunk:3] Wait(DAHDI/1-1, 2) in new stack
 Chan 1 - Handling persistent pattern 0x08
 Chan 1 - Far end disconnected. Reason: Normal Clearing
 MFC/R2 call disconnected on channel 1
   == Spawn extension (from-trunk, s, 3) exited non-zero on 'DAHDI/1-1'
 -- Executing [h@from-trunk:1] Macro(DAHDI/1-1, hangupcall,) in
 new stack
 -- Executing [s@macro-hangupcall:1] GotoIf(DAHDI/1-1, 1?theend)
 in new stack
 -- Goto (macro-hangupcall,s,3)
 -- Executing [s@macro-hangupcall:3] ExecIf(DAHDI/1-1,
 0?Set(CDR(recordingfile)=)) in new stack
 -- Executing [s@macro-hangupcall:4] Hangup(DAHDI/1-1, ) in new
 stack
   == Spawn extension (macro-hangupcall, s, 4) exited non-zero on
 'DAHDI/1-1' in macro 'hangupcall'
   == Spawn extension (from-trunk, h, 1) exited non-zero on 'DAHDI/1-1'
 MFC/R2 call end on channel 1
 -- Hungup 'DAHDI/1-1'







 On Tue, Mar 26, 2013 at 3:18 PM, deny.san...@gmail.com 
 deny.san...@gmail.com wrote:


 On Mar 26, 2013, at 3:00 PM, Patrick EL Youssef wrote:

  Posta o chan_dahdi.conf

 Este é chan_dahdi.conf

 trunkgroups]

 [channels]

 language=br

 #include chan_dahdi_additional.conf
 #include dahdi-channels.conf

 usecallerid=yes
 ;hidecallerid=yes
 callwaiting=yes
 callwaitingcallerid=yes
 threewaycalling=yes
 transfer=yes
 cancallforward=yes
 callreturn=yes
 immediate=no
 echocancel=yes
 echocancelwhenbridged=yes
 faxdetect=both

 dahd_channels

 signalling=mfcr2
 mfcr2_variant=BR
 mfcr2_get_ani_first=no
 mfcr2_max_ani=20
 mfcr2_max_dnis=4
 mfcr2_category=national_subscriber
 mfcr2_mfback_timeout=-1
 mfcr2_metering_pulse_timeout=-1
 mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
 mfcr2_logdir=span1
 mfcr2_logging=all
 faxdetect=both

 context=from-trunk
 group=0
 signalling=mfcr2
 callgroup=1
 pickupgroup=1
 channel = 1-15
 channel = 17-31
 context=from-trunk
 group=1
 signalling=mfcr2
 callgroup=2
 pickupgroup=2
 channel = 32-46
 channel = 48-62



 
  Em 26-03-2013 14:55, deny.san...@gmail.com escreveu:
  Bom dia amigos gostaria de uma ajuda de todos, estou configurando um
 link R2 da embratel porem o mesmo quando recebi chamadas esta gerando este
 erro no dahdi e derrubando a ligação , alguma ideia ?
 
  Obrigado
 
  New MFC/R2 call detected on chan 1.
  Chan 2 - Handling persistent pattern 0x00
  New MFC/R2 call detected on chan 2.
  MFC/R2 call offered on chan 1. ANI = , DNIS = 1, Category = *Unknown*
  MFC/R2 call has been accepted on backward channel 1
 -- Executing [1@from-trunk:1] Set(DAHDI/1-1, __FROM_DID=1) in
 new stack
 -- Executing [1@from-trunk:2] NoOp(DAHDI/1-1, Received an
 unknown call with DID set to 1) in new stack
 -- Executing [1@from-trunk:3] Goto(DAHDI/1-1, s,a2) in new
 stack
 -- Goto (from-trunk,s,2)
 -- Executing [s@from-trunk:2] Answer(DAHDI/1-1, ) in