[asterisk-r2] MFCR2 Cantv (Venezuela) Incomming. Sometimes calls works fine. Sometimes one call takes two channels (busy tone) and sometimes we receive "Protocol error. Reason = Multi Frequency Cycle Timeout"
jefedecomunicaciones
jefedecomunicaciones at epa.com.ve
Tue Aug 24 11:53:26 CDT 2010
Hello,
As you can read in the subject, we have unusual behavior trying to set up
an asterisk server using a R2 connection to CANTV in Venezuela.
Following you can find the details:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- Asterisk version 1.6.2.6
- Dadhi version 2.3.0
- Libpri Version 1.4.10.2
- openr2 version 1.3.0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Configuration files:
/etc/dahdi/system.conf
fxoks = 1-8
dynamic=ethmf,eth0/00:50:c2:65:d2:0e/0,31,0
dynamic=ethmf,eth0/00:50:c2:65:d2:0e/1,31,1
cas=9-24:1101
dchan=25
cas=26-40:1101
alaw=9-40
loadzone=us
defaultzone=us
[channels]
group=1
language=es
context=Entrantes
signalling=mfcr2
mfcr2_variant=ve
mfcr2_get_ani_first=yes
mfcr2_immediate_accept=yes
mfcr2_max_ani=10
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_logdir=cantv
mfcr2_logging=all
mfcr2_mfback_timeout=-1
mfcr2_call_files=yes
mfcr2_skip_category=yes ; This parameter was added after
get the Invalid Multi Frequency Tone Error. It did not fix it
channel => 9-24
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
When we receive several unsuccesfull calls we can see all bits remained in
1 state in dadhi-tool. After of a while all bits made a clearing process:
Asterisk Console>
Chan 21 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 21
MFC/R2 call end on channel 21
Chan 11 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 11
MFC/R2 call end on channel 11
Chan 17 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 17
MFC/R2 call end on channel 17
Chan 18 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 18
MFC/R2 call end on channel 18
Chan 19 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 19
MFC/R2 call end on channel 19
Chan 10 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 10
MFC/R2 call end on channel 10
Chan 9 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 9
MFC/R2 call end on channel 9
...A while after a new unsuccesfull call was made
Asterisk Console>
New MFC/R2 call detected on chan 12.
[Jul 21 20:02:40] WARNING[32725]: chan_dahdi.c:1923 dahdi_r2_write_log:
Chan 12 - MF back cycle timed out!
[Jul 21 20:02:40] ERROR[32725]: chan_dahdi.c:1926 dahdi_r2_write_log: Chan
12 - 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 = 3, ANI = , MF = 0x33
[Jul 21 20:02:40] ERROR[32725]: chan_dahdi.c:1711
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 12: Multi
Frequency Cycle Timeout
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The following calls works fine. No change were made in any configuration
file. i.e.:
Asterisk Console>
New MFC/R2 call detected on chan 9.
MFC/R2 call offered on chan 9. ANI = 2412008001, DNIS = 355, Category =
National Subscriber
[Jul 21 20:10:04] WARNING[3404]: chan_dahdi.c:2683 dahdi_enable_ec: Unable
to enable echo cancellation on channel 9 (No such device)
MFC/R2 call has been accepted on backward channel 9
-- Executing [355 at Entrantes:1] Goto("DAHDI/9-1",
"internas-standard,355,1") in new stack
-- Goto (internas-standard,355,1)
-- Executing [355 at internas-standard:1] Macro("DAHDI/9-1",
"extension-con-voicemail,SIP/355") in new stack
-- Executing [s at macro-extension-con-voicemail:1] NoOp("DAHDI/9-1",
"Llamada standard a 355 en SIP/355") in new stack
-- Executing [s at macro-extension-con-voicemail:2] Dial("DAHDI/9-1",
"SIP/355,20") in new stack
== Using SIP RTP CoS mark 5
== Using SIP VRTP CoS mark 6
-- Called 355
-- SIP/355-00000000 is ringing
-- SIP/355-00000000 answered DAHDI/9-1
== Spawn extension (macro-extension-con-voicemail, s, 2) exited non-zero
on 'DAHDI/9-1' in macro 'extension-con-voicemail'
== Spawn extension (internas-standard, 355, 1) exited non-zero on
'DAHDI/9-1'
-- Hungup 'DAHDI/9-1'
New MFC/R2 call detected on chan 10.
MFC/R2 call offered on chan 10. ANI = 2412008001, DNIS = 355, Category =
National Subscriber
[Jul 21 20:11:55] WARNING[3404]: chan_dahdi.c:2683 dahdi_enable_ec: Unable
to enable echo cancellation on channel 10 (No such device)
MFC/R2 call has been accepted on backward channel 10
-- Executing [355 at Entrantes:1] Goto("DAHDI/10-1",
"internas-standard,355,1") in new stack
-- Goto (internas-standard,355,1)
-- Executing [355 at internas-standard:1] Macro("DAHDI/10-1",
"extension-con-voicemail,SIP/355") in new stack
-- Executing [s at macro-extension-con-voicemail:1] NoOp("DAHDI/10-1",
"Llamada standard a 355 en SIP/355") in new stack
-- Executing [s at macro-extension-con-voicemail:2] Dial("DAHDI/10-1",
"SIP/355,20") in new stack
== Using SIP RTP CoS mark 5
== Using SIP VRTP CoS mark 6
-- Called 355
-- SIP/355-00000001 is ringing
-- SIP/355-00000001 answered DAHDI/10-1
MFC/R2 call end on channel 9
== Spawn extension (macro-extension-con-voicemail, s, 2) exited non-zero
on 'DAHDI/10-1' in macro 'extension-con-voicemail'
== Spawn extension (internas-standard, 355, 1) exited non-zero on
'DAHDI/10-1'
-- Hungup 'DAHDI/10-1'
Asterisk Console>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Then with only one incomming call two channels change their bits to one,
we could see it in the dahdi_tool.The call plays a busy tone
Asterisk Console>
New MFC/R2 call detected on chan 10.
New MFC/R2 call detected on chan 11.
Asterisk Console>
dahdi_tool shows two channels seized with the same call
1234567890123456789012345678901
TxA 1111111111111111-11111111111111
TxB 0110000000000000-11111111111111
TxC 0000000000000000-00000000000000
TxD 1111111111111111-11111111111111
After that,and several calls later, the Multi Frecuency error, then clear
automatically all channels again
New MFC/R2 call detected on chan 24.
[Jul 21 20:30:43] ERROR[5134]: chan_dahdi.c:1926 dahdi_r2_write_log: Chan
24 - Protocol error. Reason = Invalid Multi Frequency Tone, R2 State =
Seize ACK Transmitted, MF state = Seize ACK Transmitted, MF Group =
Backward MF init, CAS = 0x00
DNIS = , ANI = , MF = 0x43
[Jul 21 20:30:43] ERROR[5134]: chan_dahdi.c:1711
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 24: Invalid
Multi Frequency Tone
New MFC/R2 call detected on chan 10.
New MFC/R2 call detected on chan 15.
Chan 15 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 15
MFC/R2 call end on channel 15
New MFC/R2 call detected on chan 15.
Chan 20 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 20
MFC/R2 call end on channel 20
Chan 21 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 21
MFC/R2 call end on channel 21
Chan 19 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 19
MFC/R2 call end on channel 19
Chan 18 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 18
MFC/R2 call end on channel 18
Chan 22 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 22
MFC/R2 call end on channel 22
Chan 15 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 15
MFC/R2 call end on channel 15
Chan 23 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 23
MFC/R2 call end on channel 23
[Jul 21 20:32:55] NOTICE[5134]: chan_dahdi.c:1957 dahdi_r2_on_line_idle:
Far end unblocked on chan 24
Chan 10 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 10
MFC/R2 call end on channel 10
New MFC/R2 call detected on chan 20.
New MFC/R2 call detected on chan 21.
Chan 21 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 21
MFC/R2 call end on channel 21
Chan 20 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 20
MFC/R2 call end on channel 20
Do you have any suggestions???
Best Regards
Ramón Jiménez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100824/22d84340/attachment.htm
More information about the asterisk-r2
mailing list