Version 7.2 523 Mediant 1000B Gateway & E-SBC
User's Manual 24. Manipulation
SIP Response
Description
ISDN Release
Reason
Description
409 Conflict 41 Temporary failure
410 Gone 22 Number changed w/o diagnostic
411 Length required 127 Interworking
413 Request entity too long 127 Interworking
414 Request URI too long 127 Interworking
415 Unsupported media type 79 Service/option not implemented
420 Bad extension 127 Interworking
480 Temporarily unavailable 18 No user responding
481*
Call leg/transaction doesn’t
exist
127 Interworking
482* Loop detected 127 Interworking
483 Too many hops 127 Interworking
484 Address incomplete 28 Invalid number format
485 Ambiguous 1 Unallocated number
486 Busy here 17 User busy
488 Not acceptable here 31 Normal, unspecified
500 Server internal error 41 Temporary failure
501 Not implemented 38 Network out of order
502 Bad gateway 38 Network out of order
503 Service unavailable 41 Temporary failure
504 Server timeout 102 Recovery on timer expiry
505* Version not supported 127 Interworking
600 Busy everywhere 17 User busy
603 Decline 21 Call rejected
604 Does not exist anywhere 1 Unallocated number
606* Not acceptable 38 Network out of order
* Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does
not specify their cause code mapping.
24.8.2 ISDN-to-SIP Release Cause Mapping
24.8.2.1 Configuring ISDN-to-SIP Release Cause Mapping
The Release Cause Mapping from ISDN to SIP table lets you configure up to 12 ISDN ITU-
T Q.850 release cause code (call failure) to SIP response code mapping rules. The table
lets you override the default ISDN-to-SIP release cause mappings, listed in ''Fixed Mapping
of ISDN Release Reason to SIP Response'' on page 525. When the device receives an
To Next Page
Loading...
Need help?
General
