asterisk users - Aug 2014 - Connecting Asterisk and BT Versatility PBX via NT BRI port

Hi All,

I've a BT Versatility PBX that I want to connect to my asterisk 11.9.0 box
via BRI port in NT
mode but actually I wasn't able to get it working. I've another
standalone PBX, it's a
Panasonic model, which works fine connected to the same port. The BT connected
to a UK
BT BRI line works quite fine after roughly a minute once connected. The PBX can
be
seen at
http://www.telephone-engineer.com/downloads/versatility/versatility-installation.pdf

Putting the pri span in debug mode I can see the following log continuously
scrolling
and the PBX never synchronize with the openvox B400P card:

PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 TEI=0 Sending SABME
PRI 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 SAPI/TEI=0/0 Kick starting link
PRI Span: 1 TEI=0 Sending SABME
PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 1 TEI=0 Sending SABME

Below you can find the /etc/dahdi/system.conf
# Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS RED
span=1,0,0,ccs,ami
# termtype: nt
bchan=1-2
hardhdlc=3
echocanceller=mg2,1-2

# Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED
span=2,0,0,ccs,ami
# termtype: nt
bchan=4-5
hardhdlc=6
echocanceller=mg2,4-5

# Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
span=3,1,0,ccs,ami
# termtype: te
bchan=7-8
hardhdlc=9
echocanceller=mg2,7-8

# Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
span=4,2,0,ccs,ami
# termtype: te
bchan=10-11
hardhdlc=12
echocanceller=mg2,10-11

# Global data

loadzone    = uk
defaultzone    = uk

the /etc/asterisk/dahdi-channels.conf
group=0
context=from-PBX
overlapdial=yes
switchtype = euroisdn
signalling = bri_net
channel => 1-2
context=from-PBX

; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED
group=0
context=from-PBX
overlapdial=yes
switchtype = euroisdn
signalling = bri_net
channel => 4-5
context=from-PBX

; Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
group=1
context=from-NT1
overlapdial=yes
callerid=asreceived
switchtype = euroisdn
signalling = bri_cpe
channel => 7-8
context=from-NT1

; Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
group=1
context=from-NT1
overlapdial=yes
callerid=asreceived
switchtype = euroisdn
signalling = bri_cpe
channel => 10-11
context=from-NT1

the /etc/asterisk/chan_dahdi.conf

has the default settings and include the dahdi-channels.conf at the end.

Does anyone know how can I solve this problem?

Thanks in advance.
Roberto Fichera.

On Fri, Aug 1, 2014 at 12:03 PM, Roberto Fichera <kernel at tekno-soft.it>
wrote:
> Hi All,
>
> I've a BT Versatility PBX that I want to connect to my asterisk 11.9.0
box
> via BRI port in NT
> mode but actually I wasn't able to get it working. I've another
standalone
> PBX, it's a
> Panasonic model, which works fine connected to the same port. The BT
> connected to a UK
> BT BRI line works quite fine after roughly a minute once connected. The
> PBX can be
> seen at
>
http://www.telephone-engineer.com/downloads/versatility/versatility-installation.pdf
>
> Putting the pri span in debug mode I can see the following log
> continuously scrolling
> and the PBX never synchronize with the openvox B400P card:
>
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 TEI=0 Sending SABME
> PRI 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 SAPI/TEI=0/0 Kick starting link
> PRI Span: 1 TEI=0 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting
> establishment)
> PRI Span: 1 TEI=0 Sending SABME
>
> Below you can find the /etc/dahdi/system.conf
> # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS RED
> span=1,0,0,ccs,ami
> # termtype: nt
> bchan=1-2
> hardhdlc=3
> echocanceller=mg2,1-2
>
> # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED
> span=2,0,0,ccs,ami
> # termtype: nt
> bchan=4-5
> hardhdlc=6
> echocanceller=mg2,4-5
>
> # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
> span=3,1,0,ccs,ami
> # termtype: te
> bchan=7-8
> hardhdlc=9
> echocanceller=mg2,7-8
>
> # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
> span=4,2,0,ccs,ami
> # termtype: te
> bchan=10-11
> hardhdlc=12
> echocanceller=mg2,10-11
>
> # Global data
>
> loadzone    = uk
> defaultzone    = uk
>
> the /etc/asterisk/dahdi-channels.conf
> group=0
> context=from-PBX
> overlapdial=yes
> switchtype = euroisdn
> signalling = bri_net
> channel => 1-2
> context=from-PBX
>
> ; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED
> group=0
> context=from-PBX
> overlapdial=yes
> switchtype = euroisdn
> signalling = bri_net
> channel => 4-5
> context=from-PBX
>
> ; Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
> group=1
> context=from-NT1
> overlapdial=yes
> callerid=asreceived
> switchtype = euroisdn
> signalling = bri_cpe
> channel => 7-8
> context=from-NT1
>
> ; Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
> group=1
> context=from-NT1
> overlapdial=yes
> callerid=asreceived
> switchtype = euroisdn
> signalling = bri_cpe
> channel => 10-11
> context=from-NT1
>
> the /etc/asterisk/chan_dahdi.conf
>
> has the default settings and include the dahdi-channels.conf at the end.
>
> Does anyone know how can I solve this problem?
>
You might want to try bri_net_ptmp since bri_net is for point-to-point
operation
and you are not getting any response from the BT.  The BT may be expecting
to operate in point-to-multi-point mode.  Otherwise, you may have a cabling
problem.

Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140801/aa9046cf/attachment.html>