Starsky, Thanks! Your description is very useful.
What does your DNS server do for domain names it can't resolve itself? Does it return an NXDOMAIN response (indicating that the domain doesn't exist) or does it try to forward the request on (if so, presumably this doesn't respond)? As a temporary work-around, you should just be able to set "enum_file=/etc/clearwater/enum.json" in the /etc/clearwater/user_settings file (which you might need to create) and restart sprout (with "sudo monit restart sprout"). This will cause sprout to read ENUM configuration from an (empty) JSON file on disk and so not do true ENUM lookups to your DNS server. Note that this function is only intended to be used for testing - it would be good to get your DNS server configured either to forward requests on or definitively to return NXDOMAIN. Please let me know how you get on. Thanks, Matt From: Starsky Wong [mailto:[email protected]] Sent: 11 August 2013 02:49 To: Matt Williams Cc: clearwater Subject: Re: [Clearwater] Two online client cannot communicate to each other Hi Matt, Thanks a lot for your reply. Since we cannot control any DNS zone, we setup our own DHCP server (i.e.,ns.ims.research.ibm.com<http://ns.ims.research.ibm.com/>) and serving the zone "ims.research.ibm.com<http://ims.research.ibm.com/>". We setup static IP with static DNS server (point to ns.ims.research.ibm.com<http://ns.ims.research.ibm.com/>) for all the nodes. All nodes can reach our DNS server and resolve (e.g., ellis.ims.research.ibm.com<http://ellis.ims.research.ibm.com/> can be resolve by every nodes even the clients) correct. However, our DNS doesn't has the entry for 2.5.7.0.5.5.5.0.5.6.e164.arpa. Is there anything wrong with our setup ? Thanks a lot. Starsky H.Y. Wong Starsky H.Y. Wong
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
