[asterisk-r2] OpenR2 and A104DE (Sangoma Technologies)

Mon Feb 23 14:26:26 CST 2015

My apologies, I sent before send the complete configurations.

chan_dahdi.conf
;Sangoma A104 port 4 [slot:4 bus:9 span:4] <wanpipe4> MFCR2 S/CRC4 HIPATH
4000 v6.0
signalling=mfcr2
mfcr2_variant=br
mfcr2_immediate_accept=no
mfcr2_get_ani_first=no
mfcr2_max_ani=8
mfcr2_max_dnis=20
mfcr2_category=national_subscriber
mfcr2_logdir=hipath
mfcr2_call_files=yes
mfcr2_logging=all
mfcr2_allow_collect_calls=yes
mfcr2_double_answer=no
mfcr2_metering_pulse_timeout=4000
; Needed because this PABX delay digits forward
mfcr2_mfback_timeout=5000
mfcr2_charge_calls=yes
; This PABX tends to bug without this
mfcr2_forced_release=yes
;mfcr2_metering_pulse_timeout=-1
;mfcr2_advanced_protocol_file=/usr/etc/r2proto.conf
context=default
group=2
channel => 94-108:1101
channel => 110-124:1101

With Best Regards

Josue

2015-02-23 17:25 GMT-03:00 Josué Conti <josueconti at gmail.com>:

> I returned on the old configuration, just disabling r2proto.conf and the
> error occours, for some calls, but not for all calls, libe below:
>
> [2015-02-23 17:23:10] ERROR[11893]: chan_dahdi.c:2004 dahdi_r2_write_log:
> Chan 95 - Protocol error. Reason = Invalid Multi Frequency Tone, R2 State =
> Seize ACK Transmitted, MF state = DNIS Request Transmitted, MF Group =
> Backward Group A, CAS = 0x00
> DNIS = 003001000341, ANI = , MF = 0x46
> [2015-02-23 17:23:10] ERROR[11893]: chan_dahdi.c:1789
> dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 95: Invalid Multi
> Frequency Tone
> [2015-02-23 17:23:10] NOTICE[11893]: chan_dahdi.c:2035
> dahdi_r2_on_line_idle: Far end unblocked on chan 95
>
> So, my current configurations are:
>
> system.conf
> #Sangoma A104 port 4 [slot:4 bus:9 span:4] <wanpipe4> Hipath 4000
> span=4,4,0,cas,hdb3
> echocanceller=mg2,94-108,110-124
> #echocanceller=none
> # termtype: te
> cas=94-108:1101
> cas=110-124:1101
>
>
> 2015-02-23 17:19 GMT-03:00 Josué Conti <josueconti at gmail.com>:
>
> Hi Moy, after change, we can´t complete outbound calls, reporting this
>> error below:
>> [2015-02-23 17:18:27] WARNING[11069]: chan_dahdi.c:2001
>> dahdi_r2_write_log: Chan 96 - MF back cycle timed out!
>> [2015-02-23 17:18:27] ERROR[11069]: chan_dahdi.c:2004 dahdi_r2_write_log:
>> Chan 96 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State
>> = Seize ACK Transmitted, MF state = DNIS Request Transmitted, MF Group =
>> Backward Group A, CAS = 0x00
>> DNIS = 040020022, ANI = , MF = 0x20
>>
>> Why reason this happening?
>>
>>
>> 2015-02-23 15:27 GMT-03:00 Josué Conti <josueconti at gmail.com>:
>>
>> Hi Moy, thanks in advanced my friend.
>>> Even using the configurations below, is mandatory the
>>> mf_g1_tones.no_more_dnis_available=F on the r2proto.conf file? Just the
>>> "mf_g1_tones.no_more_dnis_available=F", right?
>>>
>>> ;Sangoma A104 port 4 [slot:4 bus:9 span:4] <wanpipe4> MFCR2 S/CRC4
>>> HIPATH 4000 v6.0
>>> signalling=mfcr2
>>> mfcr2_variant=br
>>> mfcr2_immediate_accept=no
>>> mfcr2_get_ani_first=no
>>> mfcr2_max_ani=8
>>> mfcr2_max_dnis=20
>>> mfcr2_category=national_subscriber
>>> mfcr2_logdir=hipath
>>> mfcr2_call_files=yes
>>> mfcr2_logging=all
>>> mfcr2_allow_collect_calls=yes
>>> mfcr2_double_answer=no
>>> mfcr2_metering_pulse_timeout=4000
>>> ; Needed because this PABX delay digits forward
>>> mfcr2_mfback_timeout=5000
>>> mfcr2_charge_calls=yes
>>> ; This PABX tends to bug without this
>>> mfcr2_forced_release=yes
>>> ;mfcr2_metering_pulse_timeout=-1
>>> ;mfcr2_advanced_protocol_file=/usr/etc/r2proto.conf - I´ll configure the
>>> r2proto.conf just with: "mf_g1_tones.no_more_dnis_available=F"
>>> context=default
>>> group=2
>>> channel => 94-108:1101
>>> channel => 110-124:1101
>>>
>>>
>>> 2015-02-23 15:17 GMT-03:00 Moises Silva <moises.silva at gmail.com>:
>>>
>>>>
>>>> On Mon, Feb 23, 2015 at 12:12 PM, Josué Conti <josueconti at gmail.com>
>>>> wrote:
>>>>
>>>>> [2015-02-19 11:23:27] ERROR[10903]: chan_dahdi.c:2004
>>>>> dahdi_r2_write_log: Chan 105 - Protocol error. Reason = Invalid Multi
>>>>> Frequency Tone, R2 State = Seize ACK Transmitted, MF state = DNIS Request
>>>>> Transmitted, MF Group = Backward Group A, CAS = 0x00
>>>>> DNIS = 00019054741990, ANI = , MF = 0x46
>>>>> [2015-02-19 11:23:27] ERROR[10903]: chan_dahdi.c:1789
>>>>> dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 105: Invalid
>>>>> Multi Frequency Tone
>>>>>
>>>>
>>>> From these logs, this is an inbound cal (R2 state is Seize ACK
>>>> Transmitted). It seems a lot of DNS has been received already (full number
>>>> 00019054741990). The error occurs when trying to request more DNIS (MF
>>>> State = DNIS Request Transmitted). The error is that the MF tone received
>>>> (0x46) is unexpected (that tone is 'F').
>>>>
>>>> It seems they are trying to send you an 'F' digit, possbily to indicate
>>>> 'No More DNIS Available'. In the Brazilian variant that is not valid. You
>>>> can work-around it by creating a custom r2proto.conf file with this:
>>>>
>>>> mf_g1_tones.no_more_dnis_available=F
>>>>
>>>> That will accept tone 'F' to indicate no more DNIS available.
>>>>
>>>> Cheers,
>>>>
>>>> Moy
>>>>
>>>> Moises Silva
>>>>
>>>> Manager, Software Engineering
>>>>
>>>>
>>>>
>>>> Sangoma Technologies
>>>>
>>>> 100 Renfrew Drive, Suite 100, Markham, Ontario, Canada L3R 9R6
>>>>
>>>> T +1 905 474 1990 x128 | toll-free in North America +1 800 388-2475 |
>>>> F +1 905 474 9223
>>>>
>>>> www.sangoma.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Email Preferences: Click here http://bit.ly/1qCfYNA to opt out of
>>>> future communication from Sangoma.
>>>>
>>>>
>>>> --
>>>> _____________________________________________________________________
>>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>>>
>>>> asterisk-r2 mailing list
>>>> To UNSUBSCRIBE or update options visit:
>>>>    http://lists.digium.com/mailman/listinfo/asterisk-r2
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20150223/7880b3d1/attachment-0001.html>