dahdi restart warning

Home » Asterisk Users » dahdi restart warning
Asterisk Users 2 Comments

What is this error ? is this harmful ?

*CLI>*CLI> dahdi restart
[Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘userbase’ (on reload) at line 23.
[Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘vmsecret’ (on reload) at line 31.
[Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hassip’ (on reload) at line 35.
[Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hasiax’ (on reload) at line 39.
[Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hasmanager’ (on reload) at line 47.

[Mar 23 14:01:10] WARNING[4315]: sig_pri.c:985 pri_find_dchan: Span 1: No D-channels available! Using Primary channel as D-channel anyway!

2 thoughts on - dahdi restart warning

  • dump!!

    Can anybody please reply me on below email? I did lots of gooooogling but no clear answer anywhere related below errors.

    I will appreciate your help.

    -S

    What is this error ? is this harmful ?

    *CLI>*CLI> dahdi restart
    [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘userbase’ (on reload) at line 23.
    [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘vmsecret’ (on reload) at line 31.
    [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hassip’ (on reload) at line 35.
    [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hasiax’ (on reload) at line 39.
    [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to ‘hasmanager’ (on reload) at line 47.

    [Mar 23 14:01:10] WARNING[4315]: sig_pri.c:985 pri_find_dchan: Span 1: No D-channels available! Using Primary channel as D-channel anyway!

  • I’ve seen the last error (No D-channels available) on multiport devices
    where some of the ports are not populated. So if you have a 4-port PRI
    device with just one PRI plugged in you would get that error regularly
    on the remaining 3 PRI ports.

    Regards,