https://onnocenter.or.id/wiki/index.php?action=history&feed=atom&title=VoIP_Cookbook%3A_ENUM 2026-04-12T10:35:20Z Revision history for this page on the wiki MediaWiki 1.35.4 https://onnocenter.or.id/wiki/index.php?title=VoIP_Cookbook:_ENUM&diff=17321&oldid=prev 2010-03-09T05:02:29Z

<p>New page: ENUM is basically a mapping mechanism to map Telco number, such as, +628113334567 or +62555334567, to a number recognize in VoIP network such as, 20333@voiprakyat.or.id or 5007987@fwd.pul...</p> <p><b>New page</b></p><div>ENUM is basically a mapping mechanism to map Telco number, such as, +628113334567 or +62555334567, to a number recognize in VoIP network such as, 20333@voiprakyat.or.id or 5007987@fwd.pulver.com. Thus, in principle, ENUM is merely a table.<br /> <br /> ENUM is not limited to mapping only. ENUM recognize prioritizing. For example, a phone number +6255534567 may have several client with priority, such as,<br /> <br /> +6255534567 priority 1 245678@voiprakyat.or.id<br /> +6255534567 priority 2 6543686@fwd.pulver.com<br /> +6255534567 priority 3 +62215678976 (nomor kantor)<br /> +6255534567 priority 4 +62856789654 (nomor handphone)<br /> +6255534567 priority 5 mail:oknum@salemba.co.id<br /> <br /> The actual writing of ENUM on the Internet, for example using the top level domain e164.id, is as follows,<br /> <br /> +6255512345678 8.7.6.5.4.3.2.1.5.5.5.2.6.e164.id<br /> +6281812345678 8.7.6.5.4.3.2.1.8.1.8.2.6.e164.id<br /> <br /> Please note that the ENUM number is reversed as oppose to the known normal phone number. <br /> <br /> ==More Detailed==<br /> <br /> ** [[VoIP Cookbook: Example of ENUM Service]]<br /> ** [[VoIP Cookbook: Delegation Concept in ENUM]]<br /> ** [[VoIP Cookbook: ENUM Implementation]]<br /> ** [[VoIP Cookbook: Setup BIND for ENUM Server]]<br /> ** [[VoIP Cookbook: Test DNS for ENUM Query]]<br /> <br /> ==See Also==<br /> <br /> * [[VoIP Cookbook: Building your own Telecommunication Infrastructure]]</div>

Onnowpurbo