E1 configuration has error of Multi-frame established

Hello team,
I am having the E1 error in my cli. The E1 is going up and down and hase the following observable ******************************************************************************************************************
errors as it changes from stage 5 to 4 to 7


RI Span: 1 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 1 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 1 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 1 TEI=0 Got SABME from network peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1 Changing from state 4(TEI assigned) to 7(Multi-frame established)
PRI Span: 1 TEI=0 DL event: Q931_DL_EVENT_DL_ESTABLISH_IND(1)
Span 1: Processing event PRI_EVENT_DCHAN_UP(1)
== Primary D-Channel on span 1 up
PRI Span: 1 TEI=0 Got SABME from network peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 TEI=0 Got SABME from network peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 TEI=0 Got SABME from network peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 TEI=0 Got SABME from network peer.
*
*
*
PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Unknown (98) len=58
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 25186/0x6262) (Sent from originator)
PRI Span: 1 < Message Type: FACILITY (98)
PRI Span: 1 Not enough room for codeset:0 ie:98(62)
PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Unknown (99) len=58
PRI Span: 1 < TEI=0 Call Ref: len= 3 (reference -32769/0xFFFF7FFF) (Dummy)
PRI Span: 1 < Message Type: Unknown Message Type (99)
PRI Span: 1 Not enough room for codeset:0 ie:99(63)
PRI Span: 1 TEI=0 MDL-ERROR (I): T200 expired N200 times sending RR/RNR in state 8(Timer recovery)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 8(Timer recovery) to 5(Awaiting establishment)
Span 1: Processing event PRI_EVENT_DCHAN_DOWN(2)
== Primary D-Channel on span 1 down


my configurtion are as follows


system.conf

Span 1: XBUS-00/XPD-00 “Xorcom XPD [usb].1: E1” ClockSource

span=1,1,0,ccs,hdb3,crc4

termtype: te

bchan=1-15,17-31
#hardhdlc=16
dchan=16
echocanceller=oslec,1-15,17-31

Span 2: XBUS-00/XPD-10 “Xorcom XPD [usb].2: FXO” (MASTER)

fxsks=32
echocanceller=oslec,32
fxsks=33
echocanceller=oslec,33
fxsks=34
echocanceller=oslec,34
fxsks=35
echocanceller=oslec,35
fxsks=36
echocanceller=oslec,36
fxsks=37
echocanceller=oslec,37
fxsks=38
echocanceller=oslec,38
fxsks=39
echocanceller=oslec,39

Global data

loadzone = us
defaultzone = us


dahdi-channels.conf


; Span 1: XBUS-00/XPD-00 “Xorcom XPD [usb].1: E1” ClockSource
group=11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31
context = default

; Span 2: XBUS-00/XPD-10 “Xorcom XPD [usb].2: FXO” (MASTER)
;;; line="32 XPP_FXO/00/10/0 (no pcm)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 32
callerid=
group=
context=default

;;; line="33 XPP_FXO/00/10/1 (no pcm)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 33
callerid=
group=
context=default

;;; line="34 XPP_FXO/00/10/2 (no pcm)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 34
callerid=
group=
context=default
**
**
**
Kindly assist

Howdy,

Your best path for assistance might be Xorcom themselves. I’m not sure of the familiarity of other posters on this board with Xorcom’s products and configuration.

Cheers

In any case, it is clearly not an error, especially as it causes a transition to UP!