ISUP - SIP: соответствие причин отбоя (CV)
Материал из M-200 WIKI
(Различия между версиями)
Pax (обсуждение | вклад) |
Pax (обсуждение | вклад) |
||
Строка 1: | Строка 1: | ||
− | + | =RFC 3398, ISUP to SIP Mapping, December 2002= | |
+ | == Прямое направление == | ||
− | Normal event | + | If a cause value other than those listed below is received, the |
+ | default response '500 Server internal error' SHOULD be used. | ||
+ | |||
+ | === Normal event=== | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
Строка 23: | Строка 27: | ||
29 facility rejected 501 Not implemented | 29 facility rejected 501 Not implemented | ||
31 normal unspecified 480 Temporarily unavailable | 31 normal unspecified 480 Temporarily unavailable | ||
− | + | ||
(*) ISDN Cause 16 will usually result in a BYE or CANCEL | (*) ISDN Cause 16 will usually result in a BYE or CANCEL | ||
− | + | ||
(+) If the cause location is 'user' than the 6xx code could be given | (+) If the cause location is 'user' than the 6xx code could be given | ||
rather than the 4xx code (i.e., 403 becomes 603) | rather than the 4xx code (i.e., 403 becomes 603) | ||
− | + | ||
(=) ANSI procedure - in ANSI networks, 26 is overloaded to signify | (=) ANSI procedure - in ANSI networks, 26 is overloaded to signify | ||
'misrouted ported number'. Presumably, a number portability dip | 'misrouted ported number'. Presumably, a number portability dip | ||
should have been performed by a prior network. Otherwise cause 26 is | should have been performed by a prior network. Otherwise cause 26 is | ||
usually not used in ISUP procedures. | usually not used in ISUP procedures. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
A REL with ISDN cause 22 (number changed) might contain information | A REL with ISDN cause 22 (number changed) might contain information | ||
about a new number where the callee might be reachable in the | about a new number where the callee might be reachable in the | ||
diagnostic field. If the MGC is able to process this information it | diagnostic field. If the MGC is able to process this information it | ||
SHOULD be added to the SIP response (301) in a Contact header. | SHOULD be added to the SIP response (301) in a Contact header. | ||
− | + | ||
− | + | ===Resource unavailable=== | |
This kind of cause value indicates a temporary failure. A 'Retry- | This kind of cause value indicates a temporary failure. A 'Retry- | ||
After' header MAY be added to the response if appropriate. | After' header MAY be added to the response if appropriate. | ||
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
---------------- ------------ | ---------------- ------------ | ||
Строка 58: | Строка 55: | ||
42 switching equipment congestion 503 Service unavailable | 42 switching equipment congestion 503 Service unavailable | ||
47 resource unavailable 503 Service unavailable | 47 resource unavailable 503 Service unavailable | ||
− | + | ||
− | + | ===Service or option not available=== | |
− | + | ||
This kind of cause value indicates that there is a problem with the | This kind of cause value indicates that there is a problem with the | ||
request, rather than something that will resolve itself over time. | request, rather than something that will resolve itself over time. | ||
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
---------------- ------------ | ---------------- ------------ | ||
Строка 70: | Строка 67: | ||
58 bearer capability not presently 503 Service unavailable | 58 bearer capability not presently 503 Service unavailable | ||
available | available | ||
− | + | ||
− | + | ===Service or option not available=== | |
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
---------------- ------------ | ---------------- ------------ | ||
Строка 78: | Строка 75: | ||
70 only restricted digital avail 488 Not Acceptable Here | 70 only restricted digital avail 488 Not Acceptable Here | ||
79 service or option not implemented 501 Not implemented | 79 service or option not implemented 501 Not implemented | ||
− | + | ||
− | + | ===Invalid message=== | |
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
---------------- ------------ | ---------------- ------------ | ||
87 user not member of CUG 403 Forbidden | 87 user not member of CUG 403 Forbidden | ||
88 incompatible destination 503 Service unavailable | 88 incompatible destination 503 Service unavailable | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | ||
− | + | ===Protocol error=== | |
− | + | ||
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
Строка 103: | Строка 90: | ||
102 recovery of timer expiry 504 Gateway timeout | 102 recovery of timer expiry 504 Gateway timeout | ||
111 protocol error 500 Server internal error | 111 protocol error 500 Server internal error | ||
− | + | ||
− | + | ===Interworking=== | |
− | + | ||
ISUP Cause value SIP response | ISUP Cause value SIP response | ||
---------------- ------------ | ---------------- ------------ | ||
Строка 112: | Строка 99: | ||
+ | == Обратное направление == | ||
− | Just as there are certain ISDN cause codes that are ISUP-specific and | + | |
+ | Just as there are certain ISDN cause codes that are ISUP-specific and | ||
have no corollary SIP action, so there are SIP status codes that | have no corollary SIP action, so there are SIP status codes that | ||
should not simply be translated to ISUP - some SIP-specific action | should not simply be translated to ISUP - some SIP-specific action | ||
should be attempted first. See the note on the (+) tag below. | should be attempted first. See the note on the (+) tag below. | ||
− | + | ||
Response received Cause value in the REL | Response received Cause value in the REL | ||
----------------- ---------------------- | ----------------- ---------------------- | ||
Строка 161: | Строка 150: | ||
604 Does not exist anywhere 1 Unallocated number | 604 Does not exist anywhere 1 Unallocated number | ||
606 Not acceptable --- by Warning header | 606 Not acceptable --- by Warning header | ||
− | + | ||
[[Категория:SIP]] | [[Категория:SIP]] | ||
[[Категория:ОКС7]] | [[Категория:ОКС7]] |
Текущая версия на 16:27, 18 мая 2017
Содержание |
[править] RFC 3398, ISUP to SIP Mapping, December 2002
[править] Прямое направление
If a cause value other than those listed below is received, the default response '500 Server internal error' SHOULD be used.
[править] Normal event
ISUP Cause value SIP response ---------------- ------------ 1 unallocated number 404 Not Found 2 no route to network 404 Not found 3 no route to destination 404 Not found 16 normal call clearing --- (*) 17 user busy 486 Busy here 18 no user responding 408 Request Timeout 19 no answer from the user 480 Temporarily unavailable 20 subscriber absent 480 Temporarily unavailable 21 call rejected 403 Forbidden (+) 22 number changed (w/o diagnostic) 410 Gone 22 number changed (w/ diagnostic) 301 Moved Permanently 23 redirection to new destination 410 Gone 26 non-selected user clearing 404 Not Found (=) 27 destination out of order 502 Bad Gateway 28 address incomplete 484 Address incomplete 29 facility rejected 501 Not implemented 31 normal unspecified 480 Temporarily unavailable (*) ISDN Cause 16 will usually result in a BYE or CANCEL (+) If the cause location is 'user' than the 6xx code could be given rather than the 4xx code (i.e., 403 becomes 603) (=) ANSI procedure - in ANSI networks, 26 is overloaded to signify 'misrouted ported number'. Presumably, a number portability dip should have been performed by a prior network. Otherwise cause 26 is usually not used in ISUP procedures. A REL with ISDN cause 22 (number changed) might contain information about a new number where the callee might be reachable in the diagnostic field. If the MGC is able to process this information it SHOULD be added to the SIP response (301) in a Contact header.
[править]
This kind of cause value indicates a temporary failure. A 'Retry- After' header MAY be added to the response if appropriate. ISUP Cause value SIP response ---------------- ------------ 34 no circuit available 503 Service unavailable 38 network out of order 503 Service unavailable 41 temporary failure 503 Service unavailable 42 switching equipment congestion 503 Service unavailable 47 resource unavailable 503 Service unavailable
[править] Service or option not available
This kind of cause value indicates that there is a problem with the request, rather than something that will resolve itself over time. ISUP Cause value SIP response ---------------- ------------ 55 incoming calls barred within CUG 403 Forbidden 57 bearer capability not authorized 403 Forbidden 58 bearer capability not presently 503 Service unavailable available
[править] Service or option not available
ISUP Cause value SIP response ---------------- ------------ 65 bearer capability not implemented 488 Not Acceptable Here 70 only restricted digital avail 488 Not Acceptable Here 79 service or option not implemented 501 Not implemented
[править] Invalid message
ISUP Cause value SIP response ---------------- ------------ 87 user not member of CUG 403 Forbidden 88 incompatible destination 503 Service unavailable
[править] Protocol error
ISUP Cause value SIP response ---------------- ------------ 102 recovery of timer expiry 504 Gateway timeout 111 protocol error 500 Server internal error
[править] Interworking
ISUP Cause value SIP response ---------------- ------------ 127 interworking unspecified 500 Server internal error
[править] Обратное направление
Just as there are certain ISDN cause codes that are ISUP-specific and have no corollary SIP action, so there are SIP status codes that should not simply be translated to ISUP - some SIP-specific action should be attempted first. See the note on the (+) tag below. Response received Cause value in the REL ----------------- ---------------------- 400 Bad Request 41 Temporary Failure 401 Unauthorized 21 Call rejected (*) 402 Payment required 21 Call rejected 403 Forbidden 21 Call rejected 404 Not found 1 Unallocated number 405 Method not allowed 63 Service or option unavailable 406 Not acceptable 79 Service/option not implemented (+) 407 Proxy authentication required 21 Call rejected (*) 408 Request timeout 102 Recovery on timer expiry 410 Gone 22 Number changed (w/o diagnostic) 413 Request Entity too long 127 Interworking (+) 414 Request-URI too long 127 Interworking (+) 415 Unsupported media type 79 Service/option not implemented (+) 416 Unsupported URI Scheme 127 Interworking (+) 420 Bad extension 127 Interworking (+) 421 Extension Required 127 Interworking (+) 423 Interval Too Brief 127 Interworking (+) 480 Temporarily unavailable 18 No user responding 481 Call/Transaction Does not Exist 41 Temporary Failure 482 Loop Detected 25 Exchange - routing error 483 Too many hops 25 Exchange - routing error 484 Address incomplete 28 Invalid Number Format (+) 485 Ambiguous 1 Unallocated number 486 Busy here 17 User busy 487 Request Terminated --- (no mapping) 488 Not Acceptable here --- by Warning header 500 Server internal error 41 Temporary failure 501 Not implemented 79 Not implemented, unspecified 502 Bad gateway 38 Network out of order 503 Service unavailable 41 Temporary failure 504 Server time-out 102 Recovery on timer expiry 504 Version Not Supported 127 Interworking (+) 513 Message Too Large 127 Interworking (+) 600 Busy everywhere 17 User busy 603 Decline 21 Call rejected 604 Does not exist anywhere 1 Unallocated number 606 Not acceptable --- by Warning header