asterisk users - Jul 2007 - Problem after upgrading from 1.2.21.1 to 1.2.22

Yesterday I upgraded from asterisk 1.2.21.1 to 1.2.22. We are running
Zaptel-1.2.17.1. After upgrading all of our calls from the phone company
(DIDs trunks with wink start on a channelized T1) were not coming in.
Looking in the log file  '/var/log/messages'. I saw the following error
message. 

pbx.c: Cannot find extension '' in context '(null)'

This was confusing since I had not changed my configuration files at
all. After going back to 1.2.21, things worked fine again. Again last
night I did a make clean; make install for 1.2.22. Again this error
message appeared. Internal calls (Zap to Zap or Zap to SIP or SIP to
SIP) worked fine. Outgoing calls worked fine. 

Has something changed in the way configuration files are parsed? Where
does a context '(null)' come from.

Don Pobanz

Hi Don -
> Yesterday I upgraded from asterisk 1.2.21.1 to 1.2.22. We are running
> Zaptel-1.2.17.1. After upgrading all of our calls from the phone company
> (DIDs trunks with wink start on a channelized T1) were not coming in.
I believe you'll need to upgrade Zaptel to the latest version if you
want to run asterisk 1.2.22.



- Noah

You should be running the latest Zaptel & LibPRI both of which
recently have been updated. We run a similar configuration and have
not seen this problem with the upgrade. I do get a flood of:

Jul 19 19:36:18 WARNING[7277]: pbx.c:815 pbx_find_extension: Maximum
PBX stack exceeded
Jul 19 19:36:18 WARNING[7277]: pbx.c:815 pbx_find_extension: Maximum
PBX stack exceeded
Jul 19 19:36:18 WARNING[7277]: pbx.c:815 pbx_find_extension: Maximum
PBX stack exceeded
Jul 19 19:36:18 WARNING[7277]: pbx.c:815 pbx_find_extension: Maximum
PBX stack exceeded


But that's probably because we updated the dialplan at the same time
as the upgrade (bad bad bad idea)