Damien Sandras <dsandras at seconix.com> writes: > I don't think so. I think sipproxd does not relay the message, no idea > why ;) Turned out to have been my fault. When starting, siproxd does a chroot to a directory where's no /etc/hosts. Hence the internal name didn't resolve. Stupid me. Really sorry. Thanks again, Bruno.