Renne,
Thanks for your note.
Whilst enumdroid is capable of supporting alternate ENUM trees, the
reason it was written was to promote use of the official e164.arpa
ENUM tree.
Since the e164.org tree "competes" with that and their update API is
bespoke it is unlikely that we would consider adding support for this.
kind regards,
Ray
I agree (except the competion), and even Duane Groth does.
e164.org was never planned for daily usage but to promote ENUM
by showing convenient use cases and gaining the critical mass.
And that's why I ask you to implement the update API until ENUM
achieves the critical mass and an update API will be standardized.
kind regards,
Renne