But that would sort of break SIP. A SIP URI is [EMAIL PROTECTED], so it makes
No, A SIP URI is [EMAIL PROTECTED] - there's a big difference. Read on
DNS SRV records on
http://www.voip-info.org/tiki-index.php?page=DNS%20SRV
Quoting myself:
No one really mails [EMAIL PROTECTED] any more. We're
On Sat, Nov 22, 2003 at 11:28:34AM +0100, Olle E. Johansson wrote:
Quoting myself:
No one really mails [EMAIL PROTECTED] any more. We're mailing [EMAIL PROTECTED] and
the DNS MX records helps the mail client to send the mail to the correct
mail server. Why should we call [EMAIL PROTECTED]
This has been giving me a headache for a little while, so
I thought I would throw the question out to the list.
Imagine there is a database lookup function that takes place
that, given a number, returns call routing information. It
might be a postgresql lookup, it might be an enum lookup.
If I
*.3.9.3.0.0 IN NAPTR 100 100 u SIP+E2U !^+*00393(.*)!sip:[EMAIL
PROTECTED] .
*.0.0.7.1 IN NAPTR 100 100 u IAX2+E2U !^+*(.*)!iax2:iaxtel/\1! .
They won't work since the pattern matching and replacement code is unimplemented.
(not to mention the fact that bind barfs on the
