Tracked down to a patch that caused a regression in r16997
update to latest and the patch is reverted.


On Thu, Mar 25, 2010 at 8:40 AM, Fabio Pietrosanti (naif) <lists@infosecurity.ch> wrote:
I followed on both installation the same procedure:
mkdir 23.03.2010-FS
cd 23.03.2010-FS
apt-get install subversion autoconf automake libtool gcc g++ make
ncurses-dev libexpat1-dev  zlib1g-dev libssl-dev libgnutls-dev
libcurl3-openssl-dev automake1.9

wget http://latest.freeswitch.org/freeswitch-1.0.5-latest.tar.gz
tar zxvf freeswitch-1.0.5-latest.tar.gz
cd freeswitch-1.0.5-20100321-0400
vim modules.conf
    xml_int/mod_xml_curl
    applications/mod_curl
    applications/mod_cidlookup
    dialplans/mod_dialplan_directory
    applications/mod_directory
    directories/mod_ldap
    endpoints/mod_dingaling
    say/mod_say_it
    applications/mod_spy
    applications/mod_stress

# 23.03.2010
make current #update from SVN
make samples
make install && make cd-sounds-install && make cd-moh-install

Later i just made:
mv /usr/local/freeswitch/conf /usr/local/freeswitch/conf.disabled
cp -pr /usr/local/freeswitch.old/conf /usr/local/freeswitch/conf

So the configurations are fully aligned (is the same), the modules.conf
during the compilation is aligned, the operating system is aligned
(debian/stable up-to-date), verified that mod\* is aligned .

The dynamic xml_curl lookup for REGISTER works.
The dynamic xml_curl lookup for dialplan does not work.

The function that fail is dialplan_xml_locate with error:
2010-03-25 11:59:42.877926 [ERR] mod_dialplan_xml.c:440 Open of dialplan
failed

I verified with tcpdump that it does not even try to make the xml_curl
lookup .

The configuration file of xml_curl.conf.xml is *the same* .

I noticed that mod_dialplan_xml.c changed in several parts between 16272
and 17084 revisions.

Some place where to look at for a deep investigation?
Enable dialplan debugging somehow?

Fabio
On 25/03/10 14.26, Brian West wrote:
> Nothing between these two should have broken... in fact configs from two years ago should work.  We work hard to make sure we don't break anything.
>
> /b
>
> On Mar 25, 2010, at 2:42 AM, Fabio Pietrosanti (naif) wrote:
>
>
>> The same configuration works on 16272M but is broken on 17084M .
>>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>


_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900