Hi everyone,
Perviously we were using a zap channel w/ zaptel drivers, since upgrading to the new system i have tried to preserve as much of this settings as possible. this seems to be having a weird issue when rebooting the server (as i found out last night at 11pm)
Any mobile extensions in the extensions configuration part of freepbx 2.8 that has a dial command of DAHDI/g0/04XXXXXXXX seem to taint the kernel when DAHDI boots up at server startup time. if i remove this dial command the server starts fine and i can add them back in later and reload the server config and it works fine.
Unfortunately these extensions need to be there as they are used for our AH priority 1 support (on call staff members)
The trunk is setup as a zap trunk (DAHDI compatibility) but after upgrading to 2.8 i noticed there is now DAHDI trunk available. im not sure if i have configured this correctly as all our outbound calls go out through this trunk.
In /var/log/asterisk/full i get the following
[Sep 10 00:31:51] ERROR[8345] chan_dahdi.c: Syntax error parsing ‘g0’ at ‘g0’
g0 is the name of te trunk but is also referenced by the extensions int eh dial command DAHDI/g0/04XXXXXXXX
I have narrowed it down to the dial command causing this. is there perhaps a better way to do this so when the server restarts it doesnt mean a 1am bedtime?