asterisk users - Jun 2011 - dahdi_genconf and BRI NT spans in system.conf

Hi,

My genconf_parameter is :

# grep -v "^#" genconf_parameters
lc_country        fr
context_lines        remote
group_lines        1
bri_sig_style        bri
echo_can        oslec
pri_termtype
    SPAN/*        NT

(I also tried various identations and syntax for pri_termtype line such as
bri_termtype but I still get the same output file).
But still, generated system.conf contains only TE spans.

# grep "term,te" system.conf
span=1,1,0,ccs,ami,term,te
span=2,2,0,ccs,ami,term,te
span=3,3,0,ccs,ami,term,te
span=4,4,0,ccs,ami,term,te

Did i miss something ?
If that matters, I'm using Dahdi 2.4.0 and Asterisk 1.6.1.18.

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110614/f2fad102/attachment.htm>

On Tue, Jun 14, 2011 at 11:36:33PM +0200, Olivier wrote:
> Hi,
> 
> My genconf_parameter is :
> 
> # grep -v "^#" genconf_parameters
> lc_country        fr
> context_lines        remote
> group_lines        1
> bri_sig_style        bri
> echo_can        oslec
> pri_termtype
>     SPAN/*        NT
> 
> (I also tried various identations and syntax for pri_termtype line such as
> bri_termtype but I still get the same output file).
> But still, generated system.conf contains only TE spans.
That parameter is intended for spans that dahdi_genconf cannot tell if
they are TE or NT. It seems dahdi_genconf is sure that this specific
port is TE. What device is it?
> 
> # grep "term,te" system.conf
> span=1,1,0,ccs,ami,term,te
> span=2,2,0,ccs,ami,term,te
> span=3,3,0,ccs,ami,term,te
> span=4,4,0,ccs,ami,term,te
Is that actually a generated line?
> 
> Did i miss something ?
> If that matters, I'm using Dahdi 2.4.0 and Asterisk 1.6.1.18.
-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir