chan_dahdi: call group warnings

[mkmer]

I've noticed these for some time at startup:

[2025-10-22 10:08:33.542] WARNING[620487] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2025-10-22 10:08:33.542] WARNING[620487] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group

Doesn't appear to cause problems, but we probably shouldn't put chan_dahdi.c in a call group?

My nodes have this in the chan_dahdi.conf file:

; Note that an explicit empty value for 'group' is invalid, and will not
; override a previous non-empty one. The same applies to callgroup and
; pickupgroup as well.
;
group=1
;
; Ring groups (a.k.a. call groups) and pickup groups.  If a phone is ringing
; and it is a member of a group which is one of your pickup groups, then
; you can answer it by picking up and dialing *8#.  For simple offices, just
; make these both the same.  Groups range from 0 to 63.
;
; Call groups and pickup groups may only be specified for FXO signalled channels.
; If you need to pick up an FXS signalled channel directly, you can have it
; dial a Local channel and pick up the ;1 side of the Local channel instead.
;
callgroup=1
pickupgroup=1
;

Setting callgroup=0, and pickupgroup=0 clears up the warning, but it's not clear (to me) why it's setup this way.

[InterLinked1]

You can't put FXO channels (which are FXS signaled) into a call group or pickup group, only FXS channels (which are FXO signaled).

Your configuration is invalid by trying to put FXS-signaled channels into a call group/pickup group, hence the warning.

Here is an example of a chan_dahdi.conf config that separates them out so you can apply the call group / pickup group settings only to FXS channels: https://github.com/InterLinked1/phreaknet-boilerplate/blob/master/chan_dahdi.conf

[mkmer]

I get that it's invalid, but it's the default config coming with an apt install asl3.

[InterLinked1]

I get that it's invalid, but it's the default config coming with an apt install asl3.

Okay, then the default config provided with the package is invalid. The Asterisk sample config is not invalid.

Upon second look, I think I was wrong about this - I'm seeing about a modification to the sample file.

[InterLinked1]

I get that it's invalid, but it's the default config coming with an apt install asl3.

Okay, I think I figured out where that's coming from - looks like users.conf, not chan_dahdi.conf. I deprecated and removed users.conf in Asterisk, so this shouldn't happen anymore with Asterisk 23 or newer. In older versions, just delete users.conf and the warnings should go away.

[mkmer]

No users.conf on my systems.

[InterLinked1]

No users.conf on my systems.

In a stock system, that is what would cause the warning. When deleted, there are no warnings with the sample configs.

If you post your full chan_dahdi.conf I can take a look.

Okay, never mind, I got confused because I delete that one before the users.conf. Both need to be modified.

I'll submit a patch for the other variant, which should fix it completely.

[mkmer]

Thought I was going crazy for a minute ;)
Let's link that PR to this issue (when you gitter' done)...

[InterLinked1]

Already done, see asterisk/asterisk#1552