[Draft] Diversion Indication in SIP draft-levy-sip-diversion-10

=================================== Keyword ======================================

Header : Diversion

=================================== Overview ======================================
Diversion Header는 Call Forward시 사용하는데,  이 Header에는 Forward가 발생한 정보들을 담을 수 있다.

=================================== Table of Contents ==============================
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.1.  When is the Diversion header used? . . . . . . . . . . . .  7
   5.  Extension syntax . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Detailed semantics . . . . . . . . . . . . . . . . . . . . . .  8
     6.1.  UAS Behavior . . . . . . . . . . . . . . . . . . . . . . .  8
     6.2.  UAC Behavior . . . . . . . . . . . . . . . . . . . . . . .  8
     6.3.  Redirect Server Behavior . . . . . . . . . . . . . . . . .  8
     6.4.  Proxy Server Behavior  . . . . . . . . . . . . . . . . . .  8
       6.4.1.  Proxy Logic for Diversion header . . . . . . . . . . .  9
   7.  Examples using Diversion header  . . . . . . . . . . . . . . . 10
     7.1.  Call Forward Unconditional . . . . . . . . . . . . . . . . 10
       7.1.1.  Network Call Forward Unconditional, P2 recursing . . . 10
       7.1.2.  Network Call Forward Unconditional, P1
               non-recursing P2 non-recursing . . . . . . . . . . . . 11
       7.1.3.  Network Call Forward Unconditional, P1 recursing
               P2 non-recursing . . . . . . . . . . . . . . . . . . . 12 7.1.4. Endpoint Call Forward Unconditional, P1 recursing P2 non-recursing . . . . . . . . . . . . . . . . . . . 13
     7.2.  Call Forward on Busy . . . . . . . . . . . . . . . . . . . 14
       7.2.1.  Network Call Forward on Busy, P2 recursing . . . . . . 14
       7.2.2.  Network Call Forward on Busy, P1 non-recursing P2
               non-recursing  . . . . . . . . . . . . . . . . . . . . 15
       7.2.3.  Network Call Forward on Busy, P1 recursing P2
               non-recursing  . . . . . . . . . . . . . . . . . . . . 16
       7.2.4.  Endpoint Call Forward on Busy, P1 recursing P2
               non-recursing  . . . . . . . . . . . . . . . . . . . . 17
     7.3.  Call Forward on No-Answer  . . . . . . . . . . . . . . . . 18
       7.3.1.  Network Call Forward on No-Answer, P2 recursing  . . . 18
       7.3.2.  Network Call Forward on No-Answer, P1
               non-recursing P2 non-recursing . . . . . . . . . . . . 19
       7.3.3.  Network Call Forward on No Answer, P1 recursing P2
               non-recursing  . . . . . . . . . . . . . . . . . . . . 20
       7.3.4.  Endpoint Call Forward on No-Answer, P1 recursing,
               P2 non-recursing B non-recursing . . . . . . . . . . . 21
     7.4.  Call Forward on Unavailable  . . . . . . . . . . . . . . . 22
       7.4.1.  Network Call Forward on Unavailable, P2 recursing  . . 22
       7.4.2.  Network Call Forward on Unavailable, P1
               non-recursing P2 non-recursing . . . . . . . . . . . . 23
       7.4.3.  Network Call Forward on Unavailable, P1 recursing
               P2 non-recursing . . . . . . . . . . . . . . . . . . . 24
     7.5.  Multiple Diversions  . . . . . . . . . . . . . . . . . . . 24
       7.5.1.  Call Forward Unconditional and Call Forward Busy . . . 25
       7.5.2.  Call Forward Unconditional and Call Forward No
               Answer . . . . . . . . . . . . . . . . . . . . . . . . 26
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 27
   9.  Further Examples . . . . . . . . . . . . . . . . . . . . . . . 28
     9.1.  Night Service/Automatic Call Distribution (ACD) using
           Diversion header . . . . . . . . . . . . . . . . . . . . . 28
     9.2.  Voicemail Service using Diversion header . . . . . . . . . 36
     9.3.  Q&A on alternative approaches  . . . . . . . . . . . . . . 40
   10. Mapping ISUP/ISDN Redirection information to SIP Diversion
       header . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
     10.1. Mapping ISUP/ISDN Diversion Reason codes . . . . . . . . . 41
     10.2. Mapping ISUP Redirection information to SIP Diversion
           header . . . . . . . . . . . . . . . . . . . . . . . . . . 42
       10.2.1. ISUP Definitions . . . . . . . . . . . . . . . . . . . 42
       10.2.2. ISUP parameters  . . . . . . . . . . . . . . . . . . . 43
       10.2.3. ISUP to SIP translation  . . . . . . . . . . . . . . . 43
       10.2.4. SIP to ISUP translation  . . . . . . . . . . . . . . . 44
       10.2.5. Example of ISUP to SIP translation . . . . . . . . . . 44
       10.2.6. Example of SIP to ISUP translation . . . . . . . . . . 45
     10.3. Mapping ISDN Redirection information to SIP Diversion
           header . . . . . . . . . . . . . . . . . . . . . . . . . . 45
       10.3.1. ISDN Definitions . . . . . . . . . . . . . . . . . . . 46
       10.3.2. ISDN parameters  . . . . . . . . . . . . . . . . . . . 46
       10.3.3. ISDN to SIP translation  . . . . . . . . . . . . . . . 48
       10.3.4. SIP to ISDN translation  . . . . . . . . . . . . . . . 49
       10.3.5. Example of ISDN to SIP translation . . . . . . . . . . 50
       10.3.6. Example of SIP to ISDN translation . . . . . . . . . . 50
     10.4. Information loss in SIP to ISUP/ISDN translation . . . . . 51
       10.4.1. Loss of diversion URI information  . . . . . . . . . . 51
       10.4.2. Loss of diversion reason information . . . . . . . . . 51
       10.4.3. Loss of diversion counter information  . . . . . . . . 51
   11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 52
   12. Acknowlegements  . . . . . . . . . . . . . . . . . . . . . . . 52
   13. Normative References . . . . . . . . . . . . . . . . . . . . . 52
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 52

=================================== 내용 정리 ===================================
Diversion Header는 Call Forwar가 발생할 때의 정보들을 담는 Header이다. 이 Header의 값을 이용하여,
추가적인 서비스 수행과 예외처리등에 사용할 수 있다.

이 Header가 나온 간단한 예를 들면, A가 B에게 전화를 걸려고 시도를 했다. 하지만 B는 C에게 Call Forward 해놓았고, C 또한 B에게 Call Forward를 해놓았다.. 과현 호는??
이외에도 실제 망에서 사용되고 있는 각종 서비스에서도 이 헤더를 이용하여 예외처리가 가능하다.

기본적인 사용법과 예들은 권고안을 보면 굉장히 자세히 설명되어 있다. 

하지만 Deversion의 counter, limit parameter의 예는 없기에 이를 설명한다.
counter parameter는 Forward된 횟수를 말하며, limit는 최대 Forward되는 횟수를 말한다. 
예를 들어 최초 Forward를 시작한 Proxy에서 counter=1;limit=3; 이라는 값을 주면 
Forward가 1번 되었으며, 최대 3번까지 더 Forward가 가능하다는 것을 말하는 것이다.
limit가 없다면, Forward를 하려는 Proxy의 자체 설정으로 처리해도 무방하다. 
만약 Forward가 계속되어 counter값과 limit값이 같아진다면, Proxy는 호를 폐기할 수도 있다.

-------------------- Diversion Header ABNF ----------------------------
Diversion = "Diversion" ":" 1# (name-addr *( ";" diversion_params ))
diversion-params = diversion-reason | diversion-counter |
                            diversion-limit | diversion-privacy |
                            diversion-screen | diversion-extension
diversion-reason = "reason" "="
                           ( "unknown" | "user-busy" | "no-answer" |
                             "unavailable" | "unconditional" |
                             "time-of-day" | "do-not-disturb" |
                             "deflection" | "follow-me" |
                             "out-of-service" | "away" |
                             token | quoted-string )
diversion-counter = "counter" "=" 1*2DIGIT
diversion-limit = "limit" "=" 1*2DIGIT
diversion-privacy = "privacy" "=" ( "full" | "name" |
                               "uri" | "off" | token | quoted-string )
diversion-screen = "screen" "=" ( "yes" | "no" | token | quoted-string )
diversion-extension = token ["=" (token | quoted-string)]
ex = "Diversion: xxx@proxy.com;counter=1;limit=3;
------------------------------------------------------------------


 

by 소걸음 | 2009/09/10 14:05 | [SIP] | 트랙백(2) | 덧글(0)

트랙백 주소 : http://lukiji.egloos.com/tb/3204036
☞ 내 이글루에 이 글과 관련된 글 쓰기 (트랙백 보내기) [도움말]
Tracked from コーチ アウトレット at 2014/07/28 17:52

제목 : coach 財布
の Topdatumコストhelpディレクトリのことが100% コーチ アウトレット 保証です。それはあなたの個人的に自分自身のシフトだ:それは責任 が原因のダウンロード:ケビンEik バッグ Coach enberryの 私は長い間すべてのビジネスベンチャーの時に最良だとき、私は 私の周りを移動するとすべてが所定の位置に設定され、 う 人々の ウォッチたくさん基本的にノー任意のドライブを必要とするラウンド嘆く コーチ 正規品 。 私が見るとき 、定義したいました: "彼......more

Tracked from コーチ 正規品 拍脸按摩.. at 2014/07/29 15:53

제목 : ソフトバンク Iphone
p>唇の週りに...more

:         :

:

비공개 덧글

◀ 이전 페이지                    다음 페이지 ▶