[DracoFelis]

Originally Posted by MarkLL

I have a SNOM 320 phone which supports ENUM. It uses e164.apra as it's default. If I change that to e164.org, should I expect it to work?

It should work. But the e164.arpa and e164.org "ENUM roots" have a different list of phone numbers that they support. So if you just switched from e164.arpa to e164.org (for your lookups), you would add the e164.org numbers (good) but lose support for the e164.arpa numbers (bad).

Ideally (if your equipment supports multiple ENUM root lookups), you would want to lookup numbers in both ENUM roots, to get both sets of numbers "free". Or, if you don't have built-in hardware ENUM lookup support (or your hardware lookup is limited to a single ENUM root), you could use either voxalot.com or sipbroker.com for your ENUM lookups. Both SIP Broker and Voxalot will check 5 different ENUM roots, to see if the number is listed in any of them (and therefore a "free call"): e164.arpa, e164.org, e164.info, e164.televolution.net, and enum.org

Originally Posted by MarkLL

I'm still a bit confused as the doco (at Snom wiki)

I looked at that link, and admit I'm a little confused as well. The article mentions ENUM lookups, but doesn't say anything about which ENUM roots are looked up (or even if a user can set this info). So that article leaves as many questions (about that hardware) as it answers.

Originally Posted by MarkLL

So my question is:
Does the VSP have to support ENUM lookups? or is there Hardware that will do the lookup and fall back to the VSP when it's not found?

A small minority of VoIP hardware/software can do ENUM lookups. For example, I think the open source http://www.asterisk.org has direct support for ENUM. However, I can't tell from that wiki article what support your snom equipment has or doesn't have (as the article leaves out key pieces of info).

And it is true, that the majority of VoIP hardware seems to lack ENUM support. And even when there is ENUM support in the hardware, the equipment makers may have just (falsely) assumed that only one ENUM root was sufficient (when you really want to lookup with multiple ENUM roots, to get the most numbers "for free"). For people with equipment this is more limited like this (and that's the majority of us out there), it is usually easier to have some VoIP service (such as Voxalot) handle the ENUM lookups for you, instead of trying to do your own local ENUM lookups directly.

NOTE: Even if your equipment could (in theory) handle the ENUM lookups for you, you could still choose to use a VoIP provider (such as Voxalot) to handle ENUM, if you desired. For example, if your snom system doesn't let you set the ENUM roots (or limits you to only a single ENUM root for lookup), you would likely be better off just sending the calls via Voxalot, which looks up ENUM on 5 different ENUM roots (and therefor can handle potentially fancier ENUM lookups than your hardware directly supports).