[asterisk-r2] Problems with Telco

Mc GRATH Ricardo mcgrathr at mail2web.com
Mon Sep 1 11:25:11 CDT 2014


Sorry, but crazy idea to suggest set CRC4, if change in one side CRC4 it will cause a physical frame problem!

Mc GRATH Ricardo
E-Mail mcgrathr at mail2web.com<mailto:mcgrathr at mail2web.com>

________________________________
From: asterisk-r2-bounces at lists.digium.com [asterisk-r2-bounces at lists.digium.com] On Behalf Of Victor Villarreal [mefhigoseth at gmail.com]
Sent: 01 September 2014 12:02
To: asterisk-r2 at lists.digium.com
Subject: Re: [asterisk-r2] Problems with Telco


Hi Thiago,

I never have this issue here, in Argentina. But you can try enable CRC4, maybe your provider need this to work.

Other setting i have been to tweak every time, with diferent telco provider are metering_pulse and mfback timeouts.

Hope this help. Please, submit if you success.

El ago 18, 2014 8:14 p.m., "Thiago Maluf" <malufrj at gmail.com<mailto:malufrj at gmail.com>> escribió:
Dear List,

I have a big problem in a Asterisk connected with Brazilian Telco (EMBRATEL).

Every received call, I have the same error:

[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - Bits changed from 0x08 to 0x00
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Rx << [SEIZE] 0x00
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - Call started at Mon Aug 18 20:06:26 2014 on chan 1 [openr2 version 1.3.2, revision (release)]
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - Initialized R2 MF detector
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Tx >> [SEIZE ACK] 0x0C
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Raw Tx >> 0x0D
New MFC/R2 call detected on chan 1.
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - Bits changed from 0x00 to 0x08
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Rx << [CLEAR FORWARD] 0x08
Chan 1 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 1
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - Call ended
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Tx >> [IDLE] 0x08
[Aug 18 20:06:26] DEBUG[19254]: chan_dahdi.c:4119 dahdi_r2_write_log: Chan 1 - CAS Raw Tx >> 0x09
MFC/R2 call end on channel 1



My config is:

#DAHDI : /etc/dahdi/system.conf
span=1,0,0,cas,hdb3
cas=1-10:1001
echocanceller=mg2,1-10

#DAHDI_SCAN
[1]
active=yes
alarms=OK
description=T2XXP (PCI) Card 0 Span 1
name=TE2/0/1
manufacturer=Digium
devicetype=Wildcard TE220 (5th Gen) (VPMOCT064)
location=Board ID Switch 0
basechan=1
totchans=31
irq=0
type=digital-E1
syncsrc=2
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=AMI,HDB3
framing_opts=CCS,CRC4
coding=HDB3
framing=CAS


#ASTERISK: /etc/asterisk/chan_dahdi.conf
context=from-pstn
signalling=mfcr2
mfcr2_variant=br
mfcr2_immediate_accept=yes
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_mfback_timeout=2500
mfcr2_metering_pulse_timeout=500
mfcr2_allow_collect_calls=no
mfcr2_double_answer=no
mfcr2_charge_calls=yes
mfcr2_forced_release=no
mfcr2_call_files=yes
mfcr2_logdir=SPAN1
mfcr2_logging=all
channel => 1-10


Asterisk Version: 1.8.11-cert7
OpenR2 version: 1.3.2, revision: (release)

mfcr2 show channels
Chan Variant Max ANI Max DNIS ANI First Immediate Accept Tx CAS   Rx CAS
   1 BR      20      4        No        Yes              IDLE     IDLE
   2 BR      20      4        No        Yes              IDLE     IDLE
   3 BR      20      4        No        Yes              IDLE     IDLE
   4 BR      20      4        No        Yes              IDLE     IDLE
   5 BR      20      4        No        Yes              IDLE     IDLE
   6 BR      20      4        No        Yes              IDLE     IDLE
   7 BR      20      4        No        Yes              IDLE     IDLE
   8 BR      20      4        No        Yes              IDLE     IDLE
   9 BR      20      4        No        Yes              IDLE     IDLE
  10 BR      20      4        No        Yes              IDLE     IDLE




Please, if you already had this problem. Send me the possible problem.

I already tried too possibilities in dahdi config or in r2proto.conf. But all tests failed by the same error.

best regards,
Thiago Maluf.



--
----------------------------------------------------------------
Thiago Maluf Resende
Tel: +55 21 9700-9113
e-mail: malufrj at gmail.com<mailto:malufrj at gmail.com>

--
_____________________________________________________________________
-- 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/20140901/6b88984d/attachment-0001.html>


More information about the asterisk-r2 mailing list