<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://onnocenter.or.id/wiki/index.php?action=history&amp;feed=atom&amp;title=VoIP_Cookbook%3A_Delegation_Concept_in_ENUM</id>
	<title>VoIP Cookbook: Delegation Concept in ENUM - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://onnocenter.or.id/wiki/index.php?action=history&amp;feed=atom&amp;title=VoIP_Cookbook%3A_Delegation_Concept_in_ENUM"/>
	<link rel="alternate" type="text/html" href="https://onnocenter.or.id/wiki/index.php?title=VoIP_Cookbook:_Delegation_Concept_in_ENUM&amp;action=history"/>
	<updated>2026-04-12T13:27:45Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.4</generator>
	<entry>
		<id>https://onnocenter.or.id/wiki/index.php?title=VoIP_Cookbook:_Delegation_Concept_in_ENUM&amp;diff=17323&amp;oldid=prev</id>
		<title>Onnowpurbo: New page: We hope as we are ready each country will have their very own ENUM Server and receive a delegation from e164.arpa. For Indonesia, it would be 2.6.e164.arpa for handling country code (+62)....</title>
		<link rel="alternate" type="text/html" href="https://onnocenter.or.id/wiki/index.php?title=VoIP_Cookbook:_Delegation_Concept_in_ENUM&amp;diff=17323&amp;oldid=prev"/>
		<updated>2010-03-09T05:05:08Z</updated>

		<summary type="html">&lt;p&gt;New page: We hope as we are ready each country will have their very own ENUM Server and receive a delegation from e164.arpa. For Indonesia, it would be 2.6.e164.arpa for handling country code (+62)....&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;We hope as we are ready each country will have their very own ENUM Server and receive a delegation from e164.arpa. For Indonesia, it would be 2.6.e164.arpa for handling country code (+62).&lt;br /&gt;
&lt;br /&gt;
To understand how ENUM works, one needs to understand how a Domain Name System (DNS) works as ENUM uses DNS Server. Thus, ENUM works fairly similar to DNS but to map and to delegate a phone number. Please note that ENUM is different from a SIP Server.&lt;br /&gt;
&lt;br /&gt;
Imagine at national level there is an allocation of area code for SIP network on +62555. It can be mapped to ENUM under  the domain, for example, 5.5.5.2.6.e164.id. It may have several ENUM Name Server (NS) such as,&lt;br /&gt;
&lt;br /&gt;
 ENUM Server Domain 5.5.5.2.6.e164.id&lt;br /&gt;
 +62555	ENUM NS	202.123.123.124&lt;br /&gt;
 +62555	ENUM NS	235.123.123.234&lt;br /&gt;
&lt;br /&gt;
Please note that at national level, the ENUM Server may not have a complete information on the subscribers.&lt;br /&gt;
&lt;br /&gt;
For example, a community or a corporate or a telecomunication operator, assigned 4444 area code for its network, such that, it may use&lt;br /&gt;
&lt;br /&gt;
 +6255544440000 - +6255544449999&lt;br /&gt;
&lt;br /&gt;
basically, it may allocate phone number for 10.000 subscribers.  Thus, the community may run their own ENUM server under the sub-domain 4.4.4.4.5.5.5.2.6.e164.id, for example&lt;br /&gt;
&lt;br /&gt;
 ENUM Server Domain 4.4.4.4.5.5.5.2.6.e164.id&lt;br /&gt;
 +62555444	ENUM	NS	212.234.234.234&lt;br /&gt;
 +62555444	ENUM	NS	212.234.234.235&lt;br /&gt;
&lt;br /&gt;
In the delegation process, the NS information of ENUM 4.4.4.4.5.5.5.2.6.e164.id must be written in  ENUM 5.5.5.2.6.e164.id that tells&lt;br /&gt;
&lt;br /&gt;
 4.4.4.4.5.5.5.2.6.e164.id	IN NS	212.234.234.234&lt;br /&gt;
 4.4.4.4.5.5.5.2.6.e164.id	IN NS	212.234.234.235&lt;br /&gt;
&lt;br /&gt;
ENUM concept is not confined to operator, any corporate or community with smaller number of extensions, e.g., 100 extentions may use, for example, ENUM allocation for,&lt;br /&gt;
&lt;br /&gt;
 +6255566666600 - +6255566666699&lt;br /&gt;
&lt;br /&gt;
Thus, this particular corporate must has its own ENUM server or collocate to other ENUM server to handle 6.6.6.6.6.6.5.5.5.2.6.e164.id, such as&lt;br /&gt;
&lt;br /&gt;
 NUM Server Domain 6.6.6.6.6.6.5.5.5.2.6.e164.id&lt;br /&gt;
 62555666666	ENUM	NS	212.234.234.4&lt;br /&gt;
 62555666666	ENUM	NS	212.234.234.5&lt;br /&gt;
&lt;br /&gt;
Delegation process for NS of 6.6.6.6.6.6.5.5.5.2.6.e164.id must be entered into the main ENUM Server for 5.5.5.2.6.e164.id tto tell&lt;br /&gt;
&lt;br /&gt;
 6.6.6.6.6.6.5.5.5.2.6.e164.id	IN NS	212.234.234.4&lt;br /&gt;
 6.6.6.6.6.6.5.5.5.2.6.e164.id	IN NS	212.234.234.5&lt;br /&gt;
&lt;br /&gt;
The ENUM delegation concept is clearly shown that is not limited to operator. Any entities may have their very own phone number. Thus, a more comprehensive authentication process may be needed to make sure the phone number is properly delegated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
&lt;br /&gt;
* [[VoIP Cookbook: Building your own Telecommunication Infrastructure]]&lt;br /&gt;
* [[VoIP Cookbook: ENUM]]&lt;/div&gt;</summary>
		<author><name>Onnowpurbo</name></author>
	</entry>
</feed>