Hi Andrew, Everything is running on an Ubuntu Hardy Xen domu with kernel 2.6.24-23-xen. Erlang is version R12B5 and was compiled from source with options -- enable-hipe, --enable-smp-support en --enable-threads. FS is trunk version 12197. I did copy the configuration file to ~freeswitch/conf/autoload_configs Also, I just checked the 'empd -names', after both FS and an erl shell have been started: root@erlyfs:~# epmd -names epmd: up and running on port 4369 with data: name ldr at port 57114 name freeswitch at port 8031 So that should be fine.. I also tried loading mod_erlang_event from modules.conf, and starting FS as root, but - not surprisingly - that didn't make any difference. I've been looking in wireshark, what exactly is going over the line, and the strange thing is, that erl opens a TCP connection, a SYN packet is sent to FS, after which FS immediately returns an RST/ACK packet and thus closes the connection.. I still don't see anything in the FS CLI. Is there anything I can do to get more verbose output from FS - esp info about why the connection was closed ? thanks, Leon On Feb 23, 2009, at 1:12 AM, Andrew Thompson wrote:
Leon,
I can't replicate your issue, at the very least I'd expect you to see the "Ignorable error in ei_accept - probable bad client version, bad cookie or bad nodename" warning. What OS/Erlang version are you using?
Andrew
_______________________________________________ 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