Openvox D115P/D115E - DAHDI

I have an Asterisk v16.6.2 with DAHDI 2.11.1, so, I am trying to install/configure an OpenVox card (D115P/D115E), however, I am getting some errors in the Asterisk CLI:

chan_dahdi.c:12535 mkintf: Attempt to configure channel 1 with signaling Unknown signalling -1 ignored because it is already configured to be ISDN PRI.
— Reconfigured channel 1, ISDN PRI signalling

[2020-03-25 18:28:55] NOTICE[12175]: chan_dahdi.c:2780 my_handle_dchan_exception: Got DAHDI event: HDLC Abort (6) on D-channel of span 1
[2020-03-25 18:28:55] NOTICE[12175]: chan_dahdi.c:2780 my_handle_dchan_exception: Got DAHDI event: HDLC Bad FCS (8) on D-channel of span 1
[2020-03-25 18:28:55] NOTICE[12175]: chan_dahdi.c:2780 my_handle_dchan_exception: Got DAHDI event: HDLC Abort (6) on D-channel of span 1
[2020-03-25 18:28:55] NOTICE[12175]: chan_dahdi.c:2780 my_handle_dchan_exception: Got DAHDI event: HDLC Bad FCS (8) on D-channel of span 1

The current configurations are:

/etc/dahdi/system.conf

span=1,1,0,ccs,hdb3,crc4
dchan=16
bchan=1-15,17-31
echocanceller=oslec,1-15,17-31
loadzone = it
defaultzone = it

/etc/asterisk/dahdi-channels.conf

context = dahdi-incoming
signalling = pri_cpe
rxgain = 0.000
txgain = 0.000
usecallerid = yes
hidecallerid = no
relaxdtmf = no
faxdetect = no
echocancel = 128
echocancelwhenbridged = yes
switchtype = euroisdn
inbanddisconnect = yes
facilityenable = enabled
overlapdial = yes
resetinterval = never
pridialplan = unknown
prilocaldialplan = unknown
usecallingpres = yes
group = 0
dahdichan = 1-15,17-31

First of all. Any TE (Terminal Equipment) connected to Telco network should always get clock to synchronize.

PBX as TE should make loop by synchronicity clock from Telco frame, therefore in your case FIRST should change dahdi clock setting otherwise should and could happens many frame errors.

dahdi references:

#
# Span Configuration
# ++++++++++++++++++
# First come the span definitions, in the format
#
# span=,,<line build out (LBO)>,,[,yellow]
#
# All T1/E1/BRI spans generate a clock signal on their transmit side. The
# parameter determines whether the clock signal from the far
# end of the T1/E1/BRI is used as the master source of clock timing. If it is, our
# own clock will synchronise to it. T1/E1/BRI connected directly or indirectly to
# a PSTN provider (telco) should generally be the first choice to sync to. The
# PSTN will never be a slave to you. You must be a slave to it.
#
# Choose 1 to make the equipment at the far end of the E1/T1/BRI link the preferred
# source of the master clock. Choose 2 to make it the second choice for the master
# clock, if the first choice port fails (the far end dies, a cable breaks, or
# whatever). Choose 3 to make a port the third choice, and so on. If you have, say,
# 2 ports connected to the PSTN, mark those as 1 and 2. The number used for each
# port should be different.
#
# If you choose 0, the port will never be used as a source of timing. This is
# appropriate when you know the far end should always be a slave to you. If
# the port is connected to a channel bank, for example, you should always be
# its master. Likewise, BRI TE ports should always be configured as a slave.
# Any number of ports can be marked as 0.
#
# Incorrect timing sync may cause clicks/noise in the audio, poor quality or failed
# faxes, unreliable modem operation, and is a general all round bad thing.
#
# NOTE: The B410P card cannot reliably connect one of its four ports
# configured in TE mode to another one configured in NT mode. It will not
# reliably sync clock from itself. Please use another physical card and
# configure one to provide clock and one to recover clock in any B410P test
# environments.
#
# The line build-out (or LBO) is an integer, from the following table:
#
# 0: 0 db (CSU) / 0-133 feet (DSX-1)
# 1: 133-266 feet (DSX-1)
# 2: 266-399 feet (DSX-1)
# 3: 399-533 feet (DSX-1)
# 4: 533-655 feet (DSX-1)
# 5: -7.5db (CSU)
# 6: -15db (CSU)
# 7: -22.5db (CSU)
#
# If the span is a BRI port the line build-out is not used and should be set
# to 0.
#
# framing::
# one of ‘d4’ or ‘esf’ for T1 or ‘cas’ or ‘ccs’ for E1. Use ‘ccs’ for BRI.
# ‘d4’ could be referred to as ‘sf’ or 'superframe’
#
# coding::
# one of ‘ami’ or ‘b8zs’ for T1 or ‘ami’ or ‘hdb3’ for E1. Use ‘ami’ for
# BRI.
#
# * For E1 there is the optional keyword ‘crc4’ to enable CRC4 checking.
# * If the keyword ‘yellow’ follows, yellow alarm is transmitted when no
# channels are open.
#span=x,0,0,ccs,hdb3,crc4

After change don´t forget to restart dahdi service.

Thanks for your help, I will try