Not to start it at boot I think is but not the way I suggested you do it temporarily for now...
The Wanpipe scripts are actually setting things up that way...
If I try to do the same thing I told you to do
ie
chkconfig wanrouter off
I get one or two error messages (which relatively seem harmless and which you apparently did not get so it's probably specific to my Sangoma Wanpipe card) but it doesn't stick..
It takes a while before everything gets initialized but once it is done everything works beautifully..
Unfortunately, it only survives one boot...
There is code in /etc/wanpipe/wancfg_zaptel/wancfg_zaptel.pl (see https://issues.freepbx.org/browse/FREEPBX-15491?focusedCommentId=110997&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-110997 for more information) which actually reenables wanrouter to start at boot...
Since you do not have a card which uses Wanpipe this bit of code hopefully does not get run (if it did things would have went back to the way they were before after one reboot) but for someone like me which has a card which does use Wanpipe the fix I suggested you do will not work for them (unless they reapply it over and over again...).
So for now only consider this a workaround and to everyone else, if you have a card which uses Wanpipe, don't bother doing this as it will not survive a reboot...
Have a nice day!
Nick