Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAE.IF-RFC3824 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2006-12-27 ÃÑÆäÀÌÁö 32
ÇѱÛÇ¥Áظí SIP¿¡¼­ E.164 ¹øÈ£ »ç¿ë¹ý
¿µ¹®Ç¥Áظí Using E.164 numbers with the Session Initiation Protocol (SIP)
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØÀº SIP¿¡¼­ ÀüÈ­ ¹øÈ£¸¦ »ç¿ëÇϴ ȯ°æ¿¡¼­ SIP ½Ã½ºÅÛ°ú ENUM ½Ã½ºÅÛ°ú ¿¬°èµÇ´Â ÀýÂ÷¿¡ ´ëÇØ Á¤ÀÇÇÏ¿´À¸¸ç, ENUM ¼­ºñ½º°¡ »ç¿ëµÇ´Â ¿¹¸¦ ±â¼úÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à There are a number of contexts in which telephone numbers are employed by Session Initiation Protocol (SIP) applications, many of which can be addressed by ENUM. Although SIP was one of the primary applications for which ENUM was created, there is nevertheless a need to define procedures for integrating ENUM with SIP implementations. This document illustrates how the two protocols might work in concert, and clarifies the authoring and processing of ENUM records for SIP applications. It also provides guidelines for instances in which ENUM, for whatever reason, cannot be used to resolve a telephone number.
±¹Á¦Ç¥ÁØ IETF RFC 3824
°ü·ÃÆÄÀÏ TTAE_IF-RFC3824.zip TTAE_IF-RFC3824.zip            

ÀÌÀü
À̵¿ ¹éȦ¸ÁÀÇ ÀÌ´õ³Ý ¼­ºñ½º ¿ä±¸»çÇ×
´ÙÀ½
ij¸®¾î ÀÌ´õ³Ý °ü¸® Á¤º¸ ¸ðµ¨