[asterisk-r2] Incoming calls hangs randomly prior R2 exchange

fauzi_roeli at gratika.co.id fauzi_roeli at gratika.co.id
Thu Mar 15 22:05:20 CDT 2018


maybe you can try to change the value of mfcr2_category with this list option :
national_subscriber
national_priority_subscriber
international_subscriber
international_priority_subscriber
collect_callhope this help----- Original Message -----
From: Ezequiel Quadri <ezequiel_quadri at hotmail.com>
To: asterisk-r2 at lists.digium.com
Sent: Fri, 16 Mar 2018 02:40:21 +0700 (WIB)
Subject: [asterisk-r2] Incoming calls hangs randomly prior R2 exchange


Hello everyone,



I have a issue with the A10Xe sangoma digital cards, using the following versions of WANPIPE 7.0.23, DAHDI 2.11.1, OpenR2 1.3.3 and Asterisk certified 13.13-cert9, on CentOS 7, to receive calls with CAS - MFC/R2 signaling on E1 trunks from Telefónica de
 Argentina.The phenomenon is that the incoming calls in some cases are handled correctly but in others the same call enters into two channels simultaneously, and a few milliseconds later are released from the TELCO without apparently reaching to exchange R2 signals.

In the asterisk console the following is observed:


New MFC/R2 call detected on chan 4.New MFC/R2 call detected on chan 5.Chan 4 - Far end disconnected. Reason: Normal ClearingMFC/R2 call disconnected on channel 4Chan 5 - Far end disconnected. Reason: Normal ClearingMFC/R2 call disconnected on channel 5MFC/R2 call end on channel 4MFC/R2 call end on channel 5
OpenR2 call files:


[12:22:03:236] [Thread: 140405976749824] [Chan 4] - Call started at Tue Mar 13 12:22:03 2018 on chan 4 [openr2 version 1.3.3, revision (release)][12:22:03:236] [Thread: 140405976749824] [Chan 4] - Initialized R2 MF detector[12:22:03:236] [Thread: 140405976749824] [Chan 4] - CAS Tx >> [SEIZE ACK] 0x0C[12:22:03:236] [Thread: 140405976749824] [Chan 4] - CAS Raw Tx >> 0x0D[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Bits changed from 0x00 to 0x08[12:22:03:277] [Thread: 140405976749824] [Chan 4] - CAS Rx << [CLEAR FORWARD] 0x08[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Far end disconnected. Reason: Normal Clearing[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Call ended[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Attempting to cancel timer timer 0[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Cannot cancel timer 0


[12:22:03:236] [Thread: 140405976241920] [Chan 5] - Call started at Tue Mar 13 12:22:03 2018 on chan 5 [openr2 version 1.3.3, revision (release)][12:22:03:236] [Thread: 140405976241920] [Chan 5] - Initialized R2 MF detector[12:22:03:236] [Thread: 140405976241920] [Chan 5] - CAS Tx >> [SEIZE ACK] 0x0C[12:22:03:236] [Thread: 140405976241920] [Chan 5] - CAS Raw Tx >> 0x0D[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Bits changed from 0x00 to 0x08[12:22:03:277] [Thread: 140405976241920] [Chan 5] - CAS Rx << [CLEAR FORWARD] 0x08[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Far end disconnected. Reason: Normal Clearing[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Call ended[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Attempting to cancel timer timer 0[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Cannot cancel timer 0
Some additional information:

wanpipe2.conf:
[devices]wanpipe2 = WAN_AFT_TE1, Comment
[interfaces]w2g1 = wanpipe2, , TDM_VOICE, Comment
[wanpipe2]CARD_TYPE       = AFTS514CPU         = ACommPort        = PRIAUTO_PCISLOT    = NOPCISLOT         = 4PCIBUS          = 3FE_MEDIA        = E1FE_LCODE        = HDB3FE_FRAME        = NCRC4FE_LINE         = 2TE_CLOCK        = NORMALTE_REF_CLOCK    = 0TE_SIG_MODE     = CASTE_HIGHIMPEDANCE        = NOTE_RX_SLEVEL    = 430HW_RJ45_PORT_MAP = DEFAULTLBO             = 120OHFE_TXTRISTATE   = NOMTU             = 1500UDPPORT         = 9000TTL             = 255IGNORE_FRONT_END        = NOTDMV_SPAN               = 2TDMV_DCHAN              = 0TE_AIS_MAINTENANCE = NO         #NO: defualt  YES: Start port in AIS Blue Alarm and keep line down                                #wanpipemon -i w1g1 -c Ttx_ais_off to disable AIS maintenance mode                                                                #wanpipemon -i w1g1 -c Ttx_ais_on to enable AIS maintenance modeTDMV_HW_DTMF            = NO            # YES: receive dtmf events from hardwareTDMV_HW_FAX_DETECT              = NO            # YES: receive fax 1100hz events from hardwareHWEC_OPERATION_MODE     = OCT_NORMAL    # OCT_NORMAL: echo cancelation enabled with nlp (default)                                                                                # OCT_SPEECH: improves software tone detection by disabling NLP (echo possible)                                                                                # OCT_NO_ECHO:disables echo cancelation but allows VQE/tone functions.HWEC_DTMF_REMOVAL       = NO    # NO: default  YES: remove dtmf out of incoming media (must have hwdtmf enabled)HWEC_NOISE_REDUCTION    = NO    # NO: default  YES: reduces noise on the line - could break faxHWEC_ACUSTIC_ECHO       = NO    # NO: default  YES: enables acustic echo cancelationHWEC_NLP_DISABLE        = NO    # NO: default  YES: guarantees software tone detection (possible echo)HWEC_TX_AUTO_GAIN       = 0     # 0: disable   -40-0: default tx audio level to be maintained (-20 default)HWEC_RX_AUTO_GAIN       = 0     # 0: disable   -40-0: default tx audio level to be maintained (-20 default)HWEC_TX_GAIN            = 0             # 0: disable   -24-24: db values to be applied to tx signalHWEC_RX_GAIN            = 0             # 0: disable   -24-24: db values to be applied to tx signal
[w2g1]ACTIVE_CH       = ALLTDMV_HWEC       = NOMTU             = 8

dahdi/system.conf:
loadzone=ardefaultzone=ar
#Sangoma A102 port 1 [slot:4 bus:3 span:1] <wanpipe1>span=1,1,0,ccs,hdb3bchan=1-15,17-31hardhdlc=16
#Sangoma A102 port 2 [slot:4 bus:3 span:2] <wanpipe2>span=2,2,0,cas,hdb3cas=32-46:1101#dchan=47cas=48-62:1101
chan_dahdi.conf:
[trunkgroups]
[channels]context=defaultusecallerid=yeshidecallerid=nocallwaiting=yesusecallingpres=yescallwaitingcallerid=yesthreewaycalling=yestransfer=yescanpark=yescancallforward=yescallreturn=yesechocancel=noechocancelwhenbridged=norelaxdtmf=yesrxgain=0.0txgain=0.0group=1callgroup=1pickupgroup=1immediate=no
;Sangoma A102 port 1 [slot:4 bus:3 span:1] <wanpipe1>switchtype=euroisdncontext=trunk_1group=1echocancel=nosignalling=pri_cpechannel =>1-15,17-31
;Sangoma A102 port 2 [slot:4 bus:3 span:2] <wanpipe2>context=trunk_2group=1echocancel=nosignalling=mfcr2mfcr2_variant=armfcr2_get_ani_first=nomfcr2_max_ani=0mfcr2_max_dnis=4mfcr2_category=national_subscribermfcr2_mfback_timeout=-1mfcr2_immediate_accept=yesmfcr2_skip_category=yes;mfcr2_metering_pulse_timeout=500mfcr2_forced_release=yesmfcr2_call_files=yesmfcr2_logdir=logloglevel=allmfcr2_logging=all;mfcr2_advanced_protocol_file=/etc/asterisk/r2proto.conf
hidecallerid=yeschannel => 32-46,48-62

I have already checked that there are no clock issues, frame errors, fifo overruns errors, toggle acpi on/off, set timers.cas_persistence_check, mfcr2_metering_pulse_timeout,
 and other tests.
I hope you can help me to identify the problem, thanks in advance.
Regards, Ezequiel Quadri


-- 
Product Development DepartmentPT. Graha Informatika Nusantara
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20180316/4e45cc3b/attachment-0001.html>


More information about the asterisk-r2 mailing list