Quote:
|
Originally Posted by Ron
I have ENUM lookups implemented in my Asterisk server. If the ENUM record is using an IP address, a SIP ENUM record is returned and used properly and the call succeeds. If the ENUM record record is using dyndns.org, it appears two DNC (Do Not Call?) records are returned instead of a SIP and DNC record and my call fails.
Any idea what's going on here?
|
I'm wondering if it's related to the DNS "A" vs DNS "SRV" record issue that VoIP sometimes faces.
Some SIP services insist on "SRV" records, and won't handle the more common "A" records, whereas other proxies (such as VoXaLot's) can use either. And almost all of the dynamic DNS services, do DNS "A" records (not the more obscure "SRV" records).
NOTE: That's one of the reasons I don't use my dynamic DNS entry in ENUM. Even if the lookup went correctly, there would be a good chance that some users wouldn't be able to complete the call, due to the SRV vs A record issue.
Instead, the "work around" is to sign up with some service that can handle the "A" records (SIP Broker aliases, VoXaLot accounts, etc), and then point your ENUM entry to that service's proxy. For example, if you point your ENUM entry to
sip:your_VoXaLot_number@voxalot.com (where
your_VoXaLot_number is of course your specific 6 digit VoXaLot phone number), and then setup VoXaLot forwarding to send all calls to your dynamic DNS entry, everything should work. ENUM callers will be happy, as the voxalot proxy has the needed SRV DNS entry. And you will receive your calls, as the voxalot proxy knows how to forward to a SIP URI that uses DNS "A" records. About the only "down side" of this approach, is that the extra "redirection" means that incomming will be down whenever the voxalot web proxy is down...
BTW: While this Wiki note (link below) doesn't relate to your specific model of equipment, it does relate to using Dynamic DNS with VoIP. As such, you might find some useful tidbits of info in it:
http://faq.sipbroker.com/tiki-index....%20or%20Sipura