[Fixed]Cannot start D-chan between TE110P and Lucent MAX6000

[Zildjian26]

Dear all,
I have a problem about to connect the T1 from TE110P to Lucent MAX6000 switch. I use zttool to check the status of alarm and it say no alarm present. So, I check the status of MAX6000 and found the D-Channel can not be started.

Below is a setting of the zaptel.conf:

span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
loadzone = us
defaultzone=us

Below is a setting of the zapata.conf:

context=default
switchtype=4ess
signalling=pri_cpe
channel => 1-23

Zaptel Configuration:

Zaptel Configuration

SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08 )
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Clear channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18 )
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: D-channel (Default) (Slaves: 24)

24 channels configured.

The MAX6000 show the D-channel can not be started (DF) for the T1.

10-100 1234567890
L1/DF …
12345678901234
…

Below is a configuration for the T1. Notes that the Framing is ESF, Encoding is B8ZS and Switch Type is AT&T (I think it means 4ess. Right? )

x10-1** Factory
x Line 1…
x >Sig Mode=ISDN
x NFAS ID num=N/A
x Rob Ctl=N/A
x Switch Type=AT&T
x Framing Mode=ESF
x Front End=CSU
x Encoding=B8ZS
x FDL=None
x Length=N/A
x Buildout=0 dB
x Clock Source=Yes
x Collect DNIS/ANI=N/A
x Pbx Type=N/A
x Delete Digits=N/A
x Add Number=N/A

Error messages was generated by Asterisk.

Asterisk Ready.
Apr 17 22:30:29 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

Apr 17 22:30:31 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

== Primary D-Channel on span 1 down
Apr 17 22:30:32 WARNING[3016]: chan_zap.c:2290 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway!
Apr 17 22:30:33 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

Apr 17 22:30:35 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

== Primary D-Channel on span 1 down
Apr 17 22:30:36 WARNING[3016]: chan_zap.c:2290 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway!
Apr 17 22:30:37 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

Apr 17 22:30:39 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

== Primary D-Channel on span 1 down
Apr 17 22:30:40 WARNING[3016]: chan_zap.c:2290 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway!
Apr 17 22:30:41 WARNING[3016]: chan_zap.c:8970 pri_dchannel: PRI Error: We think we’re the CPE, but they think they’re the CPE too.

Is my Asterisk not completely configured? If any more configuration is needed, I will happy to show it out. Thanks for your help. Thanks.

Regards
Carpenters

[ianplain]

hi

We think we’re the CPE, but they think they’re the CPE too.

should give you a very big clue as to whats wrong.

you will need to change ond or the other.

Ian

[Zildjian26]

I tried to change the value of signalling to “pri_net” in zapata.conf but still not successful. I will capture the error log to here. Thanks.

[Zildjian26]

Hello all,
The problem fixed. I tried to change the value of signalling to “pri_net” in zapata.conf. Now the D-Channel is up and line is active. I think I have somethong wrong about the setting on the router. Thanks for your help. thanks again.

Carpenters