Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-12 Thread Olivier
2009/11/11 Tzafrir Cohen tzafrir.co...@xorcom.com

 On Wed, Nov 11, 2009 at 08:24:53PM +0100, Olivier wrote:
  2009/11/10 Tzafrir Cohen tzafrir.co...@xorcom.com
 
   On Tue, Nov 10, 2009 at 06:06:12PM +0100, Olivier wrote:
Hello,
   
1. How can specify in /etc/dahdi/genconf_parameters file that a port
 from
   a
B410P board is to be disabled.
  
   There's currently no way to do that.
  
   It should be trivial to implment. The more difficult part of it would
 be
   how to define exactly what spans / channels to disable.
  
   But why do you need that?
  
 
  I don't really know why I thought I needed that feature but as some
 gateways
  implement this feature (the ability to enable or disable each port), I
 must
  have told myself I may have missed here.
 
  On a general point of view, as most Dahdi cards have a light showing
 nearby
  port status, it should ideally possible, to turn this light off when a
 port
  is disabled.
 
  But I must also add it doesn't seem very important to me to have this
  implemented.

 dahdi_genconf is an optional tool. Ideally it should need no
 configuration at all and generate configuration that Just Works (though
 the fact that it can do that indicates that the current defaults are
 broken).

 It should not be another configuration layer. If the configuration it
 has generated is not good enough, you can also manually edit it.

 
 
Playing with comments (see bellow) doesn't help : file
/etc/asterisk/dahdi-channels.conf is filled with 4 ports data.
   
pri_termtype
SPAN/1  TE
SPAN/2  TE
SPAN/3  TE
#   SPAN/4  TE
  
   Currently pri_termtype is the only directive in dahdi_genconf that uses
   this list syntax. I'm not very happy with it.
  
   I'm not exactly sure if there should be some sort of generic way of
   adding per-span (span? channel? how do you define a span?) definitions.
   Think of ssh_config.
  
 
 
  What about adding per-span section headers like Asterisk .conf files ?
  [span1]
  group_lines 1
  pri_termtype
  SPAN/1  TE
  SPAN/2  TE
 
  [span2]
  group_lines 2
  pri_termtype
  SPAN/2  TE

 This implies you will know span numbers in advance. I would like better
 ways to specify configuration.


Really ?
I used this [span1] header as an example. Using any other string would be
fine for me as what matters, if I'm not mistaken, is the group_lines number
:

[foo]
group_lines 1
pri_termtype
 SPAN/1  TE
 SPAN/2  TE

[bar]
group_lines 2



 
 
  I don't think we need to define any further what a span is, beside that
  rules that applied to the whole genconf_parameters (no more than 1
  group_lines statement) should apply to each section.

 --
Tzafrir Cohen
 icq#16849755  
 jabber:tzafrir.co...@xorcom.comjabber%3atzafrir.co...@xorcom.com
 +972-50-7952406   mailto:tzafrir.co...@xorcom.com
 http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-12 Thread Tzafrir Cohen
On Thu, Nov 12, 2009 at 01:43:48PM +0100, Olivier wrote:
 2009/11/11 Tzafrir Cohen tzafrir.co...@xorcom.com
 
  On Wed, Nov 11, 2009 at 08:24:53PM +0100, Olivier wrote:

   What about adding per-span section headers like Asterisk .conf files ?
   [span1]
   group_lines 1
   pri_termtype
   SPAN/1  TE
   SPAN/2  TE
  
   [span2]
   group_lines 2
   pri_termtype
   SPAN/2  TE
 
  This implies you will know span numbers in advance. I would like better
  ways to specify configuration.
 
 
 Really ?
 I used this [span1] header as an example. Using any other string would be
 fine for me as what matters, if I'm not mistaken, is the group_lines number
 :
 
 [foo]
 group_lines 1
 pri_termtype
  SPAN/1  TE
  SPAN/2  TE
 
 [bar]
 group_lines 2

How can you tell which spans / channels will use each section?

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-12 Thread Olivier
2009/11/12 Tzafrir Cohen tzafrir.co...@xorcom.com

 On Thu, Nov 12, 2009 at 01:43:48PM +0100, Olivier wrote:
  2009/11/11 Tzafrir Cohen tzafrir.co...@xorcom.com
 
   On Wed, Nov 11, 2009 at 08:24:53PM +0100, Olivier wrote:

What about adding per-span section headers like Asterisk .conf files
 ?
[span1]
group_lines 1
pri_termtype
SPAN/1  TE
SPAN/2  TE
   
[span2]
group_lines 2
pri_termtype
SPAN/2  TE
  
   This implies you will know span numbers in advance. I would like better
   ways to specify configuration.
  
 
  Really ?
  I used this [span1] header as an example. Using any other string would be
  fine for me as what matters, if I'm not mistaken, is the group_lines
 number
  :
 
  [foo]
  group_lines 1
  pri_termtype
   SPAN/1  TE
   SPAN/2  TE
 
  [bar]
  group_lines 2

 How can you tell which spans / channels will use each section?


My understanding of Dahdi is that I mostly need a group number to use with
Dial application :
Dial(DAHDI/g1/0123456789).





To get that dahdi-channels.conf file generated with dahdi_genconf, the only
missing feature (if my understanding is correct) is to be able to group
together a couple of ports so that I could either include in my diaplans,
lines such as Dial(DAHDI/g1/0123456789) or Dial(DAHDI/g2/9876543210).

So with a /etc/dahdi/genconf_parameters like this ...

[foo]
group_lines 1
pri_termtype
  SPAN/1TE


[bar]
group_lines 2
pri_termtype
  SPAN/2TE


... I think we've got everything needed to generate a
/etc/asterisk/dahdi-channels.conf file this :

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

; Span 2: B4/0/2 B4XXP (PCI) Card 0 Span 2 AMI/CCS
group=2,12
context=remote
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel = 4-5
context = default
group = 63


So I don't understand where I would have to tell which spans / channels
will use each section. The only purpose of sections within
genconf_parameters is to set the scope of parameters like group_lines.

Am I correct to think I can't today generate
/etc/asterisk/dahdi-channels.conf files in which 2 groups of BRI ports are
defined ?



 --
   Tzafrir Cohen
 icq#16849755  
 jabber:tzafrir.co...@xorcom.comjabber%3atzafrir.co...@xorcom.com
 +972-50-7952406   mailto:tzafrir.co...@xorcom.com
 http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-11 Thread Olivier
2009/11/10 Tzafrir Cohen tzafrir.co...@xorcom.com

 On Tue, Nov 10, 2009 at 06:06:12PM +0100, Olivier wrote:
  Hello,
 
  1. How can specify in /etc/dahdi/genconf_parameters file that a port from
 a
  B410P board is to be disabled.

 There's currently no way to do that.

 It should be trivial to implment. The more difficult part of it would be
 how to define exactly what spans / channels to disable.

 But why do you need that?


I don't really know why I thought I needed that feature but as some gateways
implement this feature (the ability to enable or disable each port), I must
have told myself I may have missed here.

On a general point of view, as most Dahdi cards have a light showing nearby
port status, it should ideally possible, to turn this light off when a port
is disabled.

But I must also add it doesn't seem very important to me to have this
implemented.


  Playing with comments (see bellow) doesn't help : file
  /etc/asterisk/dahdi-channels.conf is filled with 4 ports data.
 
  pri_termtype
  SPAN/1  TE
  SPAN/2  TE
  SPAN/3  TE
  #   SPAN/4  TE

 Currently pri_termtype is the only directive in dahdi_genconf that uses
 this list syntax. I'm not very happy with it.

 I'm not exactly sure if there should be some sort of generic way of
 adding per-span (span? channel? how do you define a span?) definitions.
 Think of ssh_config.



What about adding per-span section headers like Asterisk .conf files ?
[span1]
group_lines 1
pri_termtype
SPAN/1  TE
SPAN/2  TE

[span2]
group_lines 2
pri_termtype
SPAN/2  TE


I don't think we need to define any further what a span is, beside that
rules that applied to the whole genconf_parameters (no more than 1
group_lines statement) should apply to each section.


 
  2. How can specify groups in /etc/dahdi/genconf_parameters ?
  I would like to group SPAN/1 and SPAN/2 into group 1 and SPAN/3 into
 group
  2.
  I was unsuccessful with :
 
  group_lines 1
  pri_termtype
  SPAN/1  TE
  SPAN/2  TE
  group_lines 2
  pri_termtype
  SPAN/3  TE
 
  3. After a dahdi_genconf commande, generated
  /etc/asterisk/dahdi-channels.conf is like this :
  ; Span 1: B4/0/1 B4XXP (PCI) Card 0 Span 1 (MASTER) AMI/CCS
  group=5,11
  context=remote
  switchtype = euroisdn
  signalling = bri_cpe_ptmp
  channel = 1-2
  context = default
  group = 63
 
  I can see 2 group= and context= lines. What is the difference between
  them ?
  Shall I care to have them both ?

 The second ones are not really needed. Unless you want to assume less of
 the configuration below.

 TODO: implement a [section] syntax there to care even less about such
 inclusion.

 --
   Tzafrir Cohen
 icq#16849755  
 jabber:tzafrir.co...@xorcom.comjabber%3atzafrir.co...@xorcom.com
 +972-50-7952406   mailto:tzafrir.co...@xorcom.com
 http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-11 Thread Tzafrir Cohen
On Wed, Nov 11, 2009 at 08:24:53PM +0100, Olivier wrote:
 2009/11/10 Tzafrir Cohen tzafrir.co...@xorcom.com
 
  On Tue, Nov 10, 2009 at 06:06:12PM +0100, Olivier wrote:
   Hello,
  
   1. How can specify in /etc/dahdi/genconf_parameters file that a port from
  a
   B410P board is to be disabled.
 
  There's currently no way to do that.
 
  It should be trivial to implment. The more difficult part of it would be
  how to define exactly what spans / channels to disable.
 
  But why do you need that?
 
 
 I don't really know why I thought I needed that feature but as some gateways
 implement this feature (the ability to enable or disable each port), I must
 have told myself I may have missed here.
 
 On a general point of view, as most Dahdi cards have a light showing nearby
 port status, it should ideally possible, to turn this light off when a port
 is disabled.
 
 But I must also add it doesn't seem very important to me to have this
 implemented.

dahdi_genconf is an optional tool. Ideally it should need no
configuration at all and generate configuration that Just Works (though
the fact that it can do that indicates that the current defaults are
broken).

It should not be another configuration layer. If the configuration it
has generated is not good enough, you can also manually edit it.

 
 
   Playing with comments (see bellow) doesn't help : file
   /etc/asterisk/dahdi-channels.conf is filled with 4 ports data.
  
   pri_termtype
   SPAN/1  TE
   SPAN/2  TE
   SPAN/3  TE
   #   SPAN/4  TE
 
  Currently pri_termtype is the only directive in dahdi_genconf that uses
  this list syntax. I'm not very happy with it.
 
  I'm not exactly sure if there should be some sort of generic way of
  adding per-span (span? channel? how do you define a span?) definitions.
  Think of ssh_config.
 
 
 
 What about adding per-span section headers like Asterisk .conf files ?
 [span1]
 group_lines 1
 pri_termtype
 SPAN/1  TE
 SPAN/2  TE
 
 [span2]
 group_lines 2
 pri_termtype
 SPAN/2  TE

This implies you will know span numbers in advance. I would like better
ways to specify configuration.

 
 
 I don't think we need to define any further what a span is, beside that
 rules that applied to the whole genconf_parameters (no more than 1
 group_lines statement) should apply to each section.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-10 Thread Olivier
Hello,

1. How can specify in /etc/dahdi/genconf_parameters file that a port from a
B410P board is to be disabled.
Playing with comments (see bellow) doesn't help : file
/etc/asterisk/dahdi-channels.conf is filled with 4 ports data.

pri_termtype
SPAN/1  TE
SPAN/2  TE
SPAN/3  TE
#   SPAN/4  TE

2. How can specify groups in /etc/dahdi/genconf_parameters ?
I would like to group SPAN/1 and SPAN/2 into group 1 and SPAN/3 into group
2.
I was unsuccessful with :

group_lines 1
pri_termtype
SPAN/1  TE
SPAN/2  TE
group_lines 2
pri_termtype
SPAN/3  TE

3. After a dahdi_genconf commande, generated
/etc/asterisk/dahdi-channels.conf is like this :
; Span 1: B4/0/1 B4XXP (PCI) Card 0 Span 1 (MASTER) AMI/CCS
group=5,11
context=remote
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel = 1-2
context = default
group = 63

I can see 2 group= and context= lines. What is the difference between
them ?
Shall I care to have them both ?

Regards
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Questions about Dahdi's /etc/dahdi/genconf_parameters

2009-11-10 Thread Tzafrir Cohen
On Tue, Nov 10, 2009 at 06:06:12PM +0100, Olivier wrote:
 Hello,
 
 1. How can specify in /etc/dahdi/genconf_parameters file that a port from a
 B410P board is to be disabled.

There's currently no way to do that.

It should be trivial to implment. The more difficult part of it would be
how to define exactly what spans / channels to disable.

But why do you need that?

 Playing with comments (see bellow) doesn't help : file
 /etc/asterisk/dahdi-channels.conf is filled with 4 ports data.
 
 pri_termtype
 SPAN/1  TE
 SPAN/2  TE
 SPAN/3  TE
 #   SPAN/4  TE

Currently pri_termtype is the only directive in dahdi_genconf that uses
this list syntax. I'm not very happy with it.

I'm not exactly sure if there should be some sort of generic way of
adding per-span (span? channel? how do you define a span?) definitions.
Think of ssh_config.

 
 2. How can specify groups in /etc/dahdi/genconf_parameters ?
 I would like to group SPAN/1 and SPAN/2 into group 1 and SPAN/3 into group
 2.
 I was unsuccessful with :
 
 group_lines 1
 pri_termtype
 SPAN/1  TE
 SPAN/2  TE
 group_lines 2
 pri_termtype
 SPAN/3  TE
 
 3. After a dahdi_genconf commande, generated
 /etc/asterisk/dahdi-channels.conf is like this :
 ; Span 1: B4/0/1 B4XXP (PCI) Card 0 Span 1 (MASTER) AMI/CCS
 group=5,11
 context=remote
 switchtype = euroisdn
 signalling = bri_cpe_ptmp
 channel = 1-2
 context = default
 group = 63
 
 I can see 2 group= and context= lines. What is the difference between
 them ?
 Shall I care to have them both ?

The second ones are not really needed. Unless you want to assume less of
the configuration below.

TODO: implement a [section] syntax there to care even less about such
inclusion.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users