HOWTO : B410P with 2.8.x.x and DAHDI DRIVER

Dahdi tools see the card and detect the different port.
But you are maybe right.

another advice??

Greate
This is already a good news thats b410p works with DAHDI.
Now just needed a configuration exemple for BRI

Thanks rob

Hi,

It seems that you have a buggy dahdi-channels.conf in order to be Dialing using group=3 .

According with your file posted (dahdi-channels.conf)

channel => 1-2 ; belongs to group 0

and then you setup first the proper group=3 and two lines bellow you overwrite it back to group=0.

After that you define channel => 4-5 that by inheritance will belong to group 0 and not to group 3 , so you won't be able to dial using DAHDI/g3 because you don't have any channels in that group.

remove the group definition you have just after defining group 3 and problem should be solved.

Hope it helps.

Marco Mouta

no it doesn't work
I have reinstall the serveur
For the moment i test the first port in TE (BRI)

i change the /etc/dahdi/genconf_parameters like this

# The dialplan context into which to send trunks in chan_dahdi.conf or
# users.conf. The default value is:
context_lines           from-pstn
#
# The dialplan context into which to send extensions in chan_dahdi.conf or
# users.conf. The default value is:
#context_phones         from-internal
#
# Two extra contexts for the input ports and output ports of an
# Astribank. Default values are:
#context_input          astbank-input
#context_output         astbank-output

# A group to put all analog phones in. By default 0, so you can dial to
# the 'first phone available' using Dahdi/g5 .
#group_phones           5
#
# A group in which to put all the channels belonging to some trunk.
# Thus you can dial through "some trunk" using Dahdi/G0/NUMBER
group_lines             1

# Channels of digital trunk of span N are also added to group 10+N (that
# is: 14 for channels of span 4).

# Do we want to use PtP ('bri') or PtMP ('bri_ptmp') for BRI? PtMP
# allows connecting several CPE devices on the same network device
# (several BRI phones on the same line, kind of like several analog
# phones on the same analog line). However it is generally brings
# unnecessary complexity for a pbx-pbx connection. It is still the
# default as this is normally what you get for a BRI PSTN connection.
bri_sig_style           bri_ptmp
#
# If this option is set (that is: not remmed-out), BRI NT ports will
# also be set as overlap. This is useful if you want to connect ISDN
# phones.
#brint_overlap

# The echo canceler to use. If you have a hardware echo canceler, just
# leave it be, as this one won't be used anyway.
#
# The default is mg2, but it may change in the future. E.g: a packager
# that bundles a better echo canceler may set it as the default, or
# dahdi_genconf will scan for the "best" echo canceler.
#
#echo_can               hpec
#echo_can               oslec
echo_can                none  # to avoid echo canceler altogether

# bri_hardhdlc:
#   'yes'  - forces BRI cards to use 'hardhdlc' signalling.
#   'no'   - forces BRI cards to use 'dchan' (an alias for 'fcshdlc').
#            It is usefull only for dahdi with the bristuff patch.
#
# If it is left out or set to 'auto':
#   * Information supplied by the driver is used to decide:
#     - Currently implemented for Astribanks.
#     - Taken from /sys/bus/xpds/drivers/bri/dchan_hardhdlc.
#   * Without this info, falls back to 'hardhdlc'.
bri_hardhdlc            auto

# For MFC/R2 Support: 'R2' will make E1 spans CAS and with the
# 'r2_idle_bits' bit in system.conf . It will also make dahdi_genconf default
# to generating the channels of this card in unicall.conf rather than in
# chan_dahdi.conf . The meaning of this may be extended somehow to support
# R2 through openr2/chan_dahdi later on.
#pri_connection_type    R2
#r2_idle_bits           1101

# pri_termtype contains a list of settings:
# Currently the only setting is for TE or NT (the default is TE). This
# sets two different but normally related configuration items:
#
# A TE span will have *_cpe signalling in Asterisk and will also get
# timing from the remote party.
#
# A NT span will have *_new signalling in Asterisk and will provide
# timing to the remote party.
#
# pri_termtype is a list if span specs and configuration (TE/NT) for
# them. The first spec that matches is used. The matching is of perl
# regular expressions, but with '*' and '?' have their meaning from
# basic regular expressions.
#pri_termtype
#       SPAN/2          NT
#       SPAN/4          NT
#
#pri_termtype
#       SPAN/*          NT
#

dahdi_genconf

system.conf

# Autogenerated by /usr/sbin/dahdi_genconf on Wed Sep  2 16:53:13 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS
span=1,1,0,ccs,ami
# termtype: te
bchan=1-2
hardhdlc=3

# Global data

loadzone        = fr
defaultzone     = fr

vi /etc/asterisk/dahdi-channels.conf

; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS
group=1,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
context = default
group = 63

I can receive call but i can't call.

See the error

== fixlocalprefix: Dialpattern XXXXXXXXXX matched. 06XXXXXXXX -> 06XXXXXXXX
    -- <SIP/10-08e47870>AGI Script fixlocalprefix completed, returning 0
  == Primary D-Channel on span 1 up
    -- Executing [s@macro-dialout-trunk:13] Set("SIP/10-08e47870", "OUTNUM=06XXXXXXXX") in new stack
    -- Executing [s@macro-dialout-trunk:14] Set("SIP/10-08e47870", "custom=DAHDI/g1") in new stack
    -- Executing [s@macro-dialout-trunk:15] ExecIf("SIP/10-08e47870", "0?Set(DIAL_TRUNK_OPTIONS=M(setmusic^))") in new stack
    -- Executing [s@macro-dialout-trunk:16] Macro("SIP/10-08e47870", "dialout-trunk-predial-hook,") in new stack
    -- Executing [s@macro-dialout-trunk-predial-hook:1] MacroExit("SIP/10-08e47870", "") in new stack
    -- Executing [s@macro-dialout-trunk:17] GotoIf("SIP/10-08e47870", "0?bypass,1") in new stack
    -- Executing [s@macro-dialout-trunk:18] GotoIf("SIP/10-08e47870", "0?customtrunk") in new stack
    -- Executing [s@macro-dialout-trunk:19] Dial("SIP/10-08e47870", "DAHDI/g1/06XXXXXXXX,300,") in new stack
    -- Requested transfer capability: 0x00 - SPEECH
    -- Called g1/06XXXXXXXX
    -- Channel 0/1, span 1 got hangup, cause 24
    -- Hungup 'DAHDI/1-1'
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [s@macro-dialout-trunk:20] Goto("SIP/10-08e47870", "s-CHANUNAVAIL,1") in new stack
    -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
    -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] GotoIf("SIP/10-08e47870", "1?noreport") in new stack
    -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,3)
    -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:3] NoOp("SIP/10-08e47870", "TRUNK Dial failed due to CHANUNAVAIL (hangupcause: 24) - failing through to other trunks") in new stack

Check chan_dahdi.conf to see if you have this:

pridialplan=unknown
prilocaldialplan=unknown
internationalprefix = 00
nationalprefix = 0


Even though it's BRI not PRI, I couldn't make an outbound call until I had this in there. It's Telco specific. The Telco I tested with before deployment didn't need it, but the customer site did.
Due to a vast range of other issues with the ISDN signalling generated by the dahdi drivers, we ended up dumping the B410P and going for an Epygi box over SIP. Weeks of troubleshooting with one of the best Telco techs I've ever dealt with fixed and not a single weird issue since.

Inbound calls working great - but outbound always gives an ' all circuits are busy'
So card id definitely working, but trunk / group just won't fire up the port

Did anyone solve this one ?

I had a similar problem with other equipment, Dahdi could receive calls, but outbound failed.

I found the solution here:

http://www.freepbx.org/forum/freepbx/users/dahdi-dialing-out-prob...

echo "OUT_1 = DAHDI/g0" >> /etc/asterisk/globals_custom.conf

asterisk –rx “reload”