Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
ISDN User Part
open-in-new
<h2 id="isup-variants">ISUP variants</h2> <p>Different ISUP variants exist. ITU-T specifies the variant used in the international network. In Europe <a href="/facts/ETSI/8rJbbhPg">ETSI</a> releases its own ISUP specification which is close that of the ITU-T.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> ITU-T ISUP is used for international connections and is the base for some national ISUP variants. Most countries have their own variation of ISUP to cover national requirements. <a href="/facts/ANSI/p3d1TQCb">ANSI</a> specifies variations of ISUP utilized under the <a href="/facts/North_American_Numbering_Plan/0QQ8v3ph">North American Numbering Plan</a>; however, some countries under the NANP differ in their support of some procedures (for example, <a href="/facts/Local_access_and_transport_area/0lNjxHb7">LATA</a> is meaningless within Canada. Also, <a href="/facts/Regional_Bell_Operating_Company/9azPk76z">RBOCs</a> support <a href="/facts/Telcordia_Technologies/MBQAkk4J">Telcordia</a> procedures not fully specified by ANSI.) Some countries outside the NANP support ANSI-based variants (e.g. Mexico). </p><p>While these variations of ISUP differ in subtle ways, the vast majority of ISUP message type, parameter type, and parameter field code-points, and related fundamental call processing procedures, agree across all variants. </p> <h3>ITU-T specification versions</h3> <ul><li>1980 – ISUP Yellow Book</li> <li>1984 – ISUP Red Book</li> <li>1988 – ISUP Blue Book</li> <li>1991 – ISUP Q.767<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li> <li>1992 – ISUP'92 White Book (segmentation, compatibility, new supplementary services)</li> <li>1997 – ISUP'97 (new procedures, IN CS1, new supplementary services)</li></ul> <p>According to ITU-T Q.761 section 2.4.1 <i>ISUP interworking</i> ISUP'92 is backwards compatible with ISUP Blue Book and Q.767<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> for basic call procedures and supplementary services except for some procedures (e.g. number portability).<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> Additionally the compatibility features introduced in this version ensure forward compatibility with newer versions. </p> <h2 id="message-types">Message types</h2> <p>An ISUP message contains a fixed header containing the <a href="/facts/Circuit_identification_code/YMVUjvG2">circuit identification code</a> and the ISUP message type, followed by a mandatory fixed-length parameter part, a mandatory variable-length parameter part, and an optional parameter part that are dependent on the type of message being sent. ISUP messages can be sent using the services of the <a href="/facts/Message_Transfer_Part/tzNuwGfm">Message Transfer Part</a>, or, less often, the <a href="/facts/Signalling_Connection_Control_Part/I2srA0lK">Signalling Connection Control Part</a>. These messages are transmitted in various stages of <a href="/facts/Call_setup/CDULq334">call setup</a> and release. The most common messages are:<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <ul><li>Initial address message (IAM) — First message sent to inform the partner switch that a call has to be established on the CIC contained in the message. Contains the called number, type of service (speech or data) and optional parameters.</li> <li>Subsequent address message (SAM) — For networks that support <i>overlap</i> dialing procedures, and then in the case that the IAM did not contain the full called number, one or more SAMs follow containing additional digits. This message is not supported by networks that only support <i>en bloc</i> dialing procedures.</li> <li>Address complete message (ACM) — Message returned from the terminating switch when the subscriber is reached and the phone starts ringing, or when the call traverses an interworking point and the intermediate trunk is seized.</li> <li>Call progress (CPG) — Contains additional information about the progress of a call. Normally sent after the ACM when the status of the call changes from that reported in the ACM.</li> <li>Answer message (ANM) — Sent when the subscriber picks up the phone, a resource is connected or answer supervision is returned by an interworking point. Normally charging starts at this moment. It is required that the call be cut through in both directions by this point.</li> <li>Connect (CON) — Sent when the call is answered by an automatic terminal. This message replaces the ACM, CPG and ANM for calls that are answered by automatic terminals.</li> <li>Release (REL) — Sent to clear the call when a subscriber goes on hook. This is also sent (in direct response to an IAM) if the terminating switch determines that the call cannot be completed. In either case, the terminating switch provides a cause value in the message to explain the reason for the release, <i>e.g.</i>, "User busy".</li> <li>Release complete (RLC) — Acknowledgment of the release – the circuit is idle afterward and can be used again.</li></ul> <h2 id="sample-call-flow">Sample call flow</h2> <p>This is a very basic call flow involving only two telecom switches which exchange the ISUP messages. The subscriber interfaces are not covered here and are only listed for a better understanding. </p> A subscriber telco switch A telco switch B B subscriber Off hook Dial digits ---> -- IAM --> -Ringing -> <-- ACM -- Off hook <-- ANM -- ----------------------- Conversation ----------------------- On hook -- REL --> On hook <-- RLC -- <p>Detailed call flows are provided in ITU-T Recommendation Q.784.1.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p><p>Below is a detailed exchange of ISUP messages involving two ISDN telecom switches. The report was from an Alcatel S12 digital switch. </p> BENIN 2005-07-15 16:49:16 FR 00121 00000000 G159CA01 L6X8AA47 SWA-ORJ-OBSERVATION SYSTEM REPORT ------------------------------------------------------------------------- OBSERVATION/CALL SAMPLING SUCCESSFUL ----------------------------------------------------------------------- TYPE OF OBSERVATION: ORIGINATING DATE = 2005-07-15 TIME = 16:48:23:09 CALLING DN = 52250000 CALLING CAT = PRIORITY SUBSC INC EQ NBR = H'31 & 1 RCVD DIGITS = 012625729 CALLED DN = 012625729 OTG TRNKGRP = LAGOS_SC OTG EQ NBR = H'1111 & 16 BEARER = AUDIO31 XFER MODE = CIRCUIT SWITCHED CAUSE = NORMALUN TERM SEIZED = 0: 0: 2: 3 THROUGH SWITCH = 0: 0: 4: 3 ANSWER = 0: 0:14: 6 RELEASE = 0: 0:46: 3 TAXATION INFO ------------- CHARGED DN = 52250000 CALL DURATION = 0: 0:31: 6 COUNTS = 2 TARIFF GRP = 4 TARIFF ID = 7 RATE = 20 RANDOM CNT = 0 SURCH UNITS = 0 CAT UNITS = 0 TARIFF REG = 1 RECEIVER SZD = 0: 0: 0: 0 RECEIVER RLSD = 0: 0: 4: 2 REC EQ NBR = H'13 & 6 REC RLS INFO = FORCED RLSE REC SIGNAL DIRECTION TIME ------------- --------- ---- REG-I-10 RECEIVED 0: 0: 1: 3 REG-I-1 RECEIVED 0: 0: 1: 6 REG-I-2 RECEIVED 0: 0: 1: 8 REG-I-6 RECEIVED 0: 0: 2: 1 REG-I-2 RECEIVED 0: 0: 2: 3 REG-I-5 RECEIVED 0: 0: 2: 5 REG-I-7 RECEIVED 0: 0: 3: 0 REG-I-2 RECEIVED 0: 0: 3: 3 REG-I-9 RECEIVED 0: 0: 3: 7 INC SIG TYPE = ANALOG-SUBSCR SIGNAL DIRECTION TIME ------------- --------- ---- SEIZURE RECEIVED 0: 0: 0: 0 DIAL-TONE SENT 0: 0: 0: 0 CLEAR-FW-FW RECEIVED 0: 0:46: 1 OTG SIG TYPE = ISUP-NAT MESSAGE DIRECTION TIME LENGTH ------------- --------- ---- ------ IAM SENT 0: 0: 2: 3 29 85014040007000010020000B03020604019010620A0603132552000000 SAM SENT 0: 0: 2: 4 13 85014040007000020200028002 SAM SENT 0: 0: 2: 6 13 85014040007000020200028005 SAM SENT 0: 0: 3: 1 13 85014040007000020200028007 SAM SENT 0: 0: 3: 4 13 85014040007000020200028002 SAM SENT 0: 0: 3: 8 13 85014040007000020200028009 ACM RECEIVED 0: 0: 4: 1 15 850141000070000616040129010100 ANM RECEIVED 0: 0:14: 6 18 8501410000700009012D02000039022DC000 SUS RECEIVED 0: 0:45: 4 10 850141000070000D0100 REL SENT 0: 0:46: 1 13 850140400070000C020002849F RLC RECEIVED 0: 0:46: 3 9 850141000070001000 UNSOLICITED REPORT NO = 00121 <h2 id="cause-codes">Cause codes</h2> <p>Release cause codes are used to identify and debug any events occurring in ISDN User Part signaling. Every event in ISUP signaling generates a cause code number. Even for a normal ISUP call, a cause code is generated. There are lot of applications developed based on the cause code from ISUP signaling. Similarly Telecom operators trace for Causecodes to debug any call failures. </p><p>Following are the list of cause codes used. Cause codes only defined by number are effectively undefined, and may be used for proprietary solutions. </p> <ol><li>Unallocated (unassigned) number</li> <li>No route to specific transit network</li> <li>No route to destination</li> <li>Send special info tone</li> <li>Misdialed <a href="/facts/Trunk_prefix/lTNrM4vU">trunk prefix</a></li> <li>Channel unacceptable</li> <li>Call awarded and being delivered in established channel</li> <li>Preemption</li> <li>Preemption – circuit reserved for reuse</li> <li>10</li> <li>11</li> <li>12</li> <li>Suspend</li> <li>Resume</li> <li>15</li> <li>Normal call clearing</li> <li>User busy</li> <li>No user responding</li> <li>No answer from user (user alerted)</li> <li>Subscriber absent</li> <li>Call rejected</li> <li>Number changed</li> <li>Redirect to new destination (unallocated destination number ANSI)</li> <li>Unknown business group (ANSI)</li> <li>Exchange routing error (ANSI)</li> <li>Non-selected user clearing</li> <li>Destination out of order</li> <li>Invalid number format</li> <li>Facility rejected</li> <li>Response to STATUS ENQUIRY</li> <li>Normal, unspecified</li> <li>32</li> <li>33</li> <li>No circuit/channel available</li> <li>35</li> <li>36</li> <li>37</li> <li>Network out of order</li> <li>Permanent frame mode connection out of service</li> <li>Permanent frame mode connection operational</li> <li>Temporary failure</li> <li>Switching equipment congestion</li> <li>Access information discarded</li> <li>Requested channel/circuit not available</li> <li>Preemption (ANSI)</li> <li>Precedence call blocked</li> <li>Resources unavailable, unspecified</li> <li>48</li> <li><a href="/facts/Quality_of_service/joz9VkUm">Quality of service</a> unavailable</li> <li>Requested facility not subscribed</li> <li>Call type incompatible with service request (ANSI)</li> <li>52</li> <li>Outgoing calls barred within CUG</li> <li>Call blocked due to group restrictions (ANSI)</li> <li>Incoming calls barred within CUG</li> <li>56</li> <li><a href="/facts/Bearer_Capability/jacrNgk3">Bearer capability</a> not authorized</li> <li>Bearer capability not presently available</li> <li>59</li> <li>60</li> <li>61</li> <li>Inconsistency in designed outgoing access information and subscriber class</li> <li>Service or option not available, unspecified</li> <li>64</li> <li>Bearer capability not implemented</li> <li>Channel type not implemented</li> <li>67</li> <li>68</li> <li>Requested facility not implemented</li> <li>Only restricted digital bearer capability is available</li> <li>71</li> <li>72</li> <li>73</li> <li>74</li> <li>75</li> <li>76</li> <li>77</li> <li>78</li> <li>Service or option not implemented, unspecified</li> <li>80</li> <li>Invalid call reference value</li> <li>Identified channel does not exist</li> <li>A suspended call exists, but this call identity does not</li> <li>Call identity in use</li> <li>No call suspended</li> <li>Call having the requested call identity has been cleared</li> <li>User not member of CUG</li> <li>Incompatible destination</li> <li>89</li> <li>Non-existing CUG</li> <li>Invalid transit network selection</li> <li>92</li> <li>93</li> <li>94</li> <li>Invalid message, unspecified</li> <li>Mandatory information element is missing</li> <li>Message type non-existing or not implemented</li> <li>Message incompatible with call state or message type non-existent or not implemented</li> <li>Information element non-existent or not implemented</li> <li>Invalid information element contents</li> <li>Message not compatible with call state</li> <li>Recovery on timer expiry</li> <li>Parameter non-existent or not implemented - passed on</li> <li>104</li> <li>105</li> <li>106</li> <li>107</li> <li>108</li> <li>109</li> <li>Message with unrecognized parameter discarded</li> <li>Protocol error, unspecified</li> <li>112</li> <li>113</li> <li>114</li> <li>115</li> <li>116</li> <li>117</li> <li>118</li> <li>119</li> <li>120</li> <li>121</li> <li>122</li> <li>123</li> <li>124</li> <li>125</li> <li>126</li> <li>Interworking, unspecified.</li></ol> <h2 id="message-format">Message format</h2> <table><tbody><tr><th>8</th><th>7</th><th>6</th><th>5</th><th>4</th><th>3</th><th>2</th><th>1</th></tr><tr><td colspan="8">Routing Label<p>...</p></td></tr><tr><td colspan="8">CIC Least Significant 8 Bits</td></tr><tr><td colspan="4">Padding</td><td colspan="4">CIC Most Sig. 4 Bits</td></tr><tr><td colspan="8">Message type</td></tr><tr><td colspan="8">Mandatory fixed part<p>...</p></td></tr><tr><td colspan="8">Mandatory variable part<p>...</p></td></tr><tr><td colspan="8">Optional part<p>...</p></td></tr></tbody></table> <p>The <i>Signalling Information Field (SIF)</i> for all ISUP Message Signal Units (MSU) contain the following components:<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> </p> <ul><li>Routing Label</li> <li>Circuit Identification Code</li> <li>Message Type</li> <li>Mandatory Fixed Part</li> <li>Mandatory Variable Part</li> <li>Optional Part</li></ul> <p>The <i>Routing Label</i> indicates the <a href="/facts/Point_Code/LePBTk2Q">Point Codes</a> of the originating and destination nodes in the network; it also includes the <a href="/facts/Message_Transfer_Part/tzNuwGfm">Signalling Link Selection</a> field that is used to select between the multiple routes an MSU could take between two nodes. </p><p>The <i>Circuit Identification Code</i> is used to specify which trunk between two <a href="/facts/Telephone_exchange/PaRpGm8I">switches</a> is used to carry a particular call. Note that some versions of <a href="/facts/ANSI/p3d1TQCb">ANSI</a> ISUP permit a CIC with 14 significant bits instead of the 12 that are shown.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <ol><li>The <i>Message Type</i> indicates the ISUP message type. The presence and form of the remaining 3 components are determined by this message type.</li> <li>The <i>Mandatory fixed part</i>, when present, contains the mandatory, fixed-length parameters associated with the message type.</li> <li>The <i>Mandatory variable part</i>, when present, contains the mandatory, variable-length parameters associated with the message type.</li> <li>The <i>Optional part</i>, when present, contains the optional parameters permitted to be included in the message type.</li></ol> <p>When sent using the services of the <a href="/facts/Signalling_Connection_Control_Part/I2srA0lK">Signalling Connection Control Part</a>, ISUP messages passed to SCCP in the User Data parameter (NSDU) consist of only the last 4 components (<i>Message Type, Mandatory fixed part, Mandatory variable part, Optional part</i>). The <a href="/facts/Message_Transfer_Part/tzNuwGfm">routing label</a> and <a href="/facts/Circuit_identification_code/YMVUjvG2">circuit identification code</a> are not included in the user data passed to SCCP.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Integrated_Services_Digital_Network/zcV99rUb">Integrated Services Digital Network</a> (ISDN)</li> <li><a href="/facts/Q.931/CrX6l6gV">Q.931</a> Cause Codes</li></ul> <h2 id="notes">Notes</h2> <h3>Bibliography</h3> <ul><li>Russell, Travis (2002), <i>Signaling System #7</i> (4th ed.), New York: McGraw-Hill, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-0-07-138772-9.</li> <li>ITU-T (December 1999a), "Section 1, General coding principles", <a href="http://www.itu.int/rec/T-REC-Q.763-199912-I/en/"><i>Recommendation Q.763</i></a>.</li> <li>ITU-T (December 1999b) [1996], <a href="http://www.itu.int/rec/T-REC-Q.784.1/en/"><i>Recommendation Q.784.1 (07/96), ISUP basic call test specification: Validation and compatibility for ISUP'92 and Q.767 protocols</i></a>.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Q-Series Recommendations, ITU-T. <a href="http://www.itu.int/rec/T-REC-Q/en/" target="_blank">http://www.itu.int/rec/T-REC-Q/en/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>EN 300 356-1, ISUP Version 4 for the International Interface, ETSI. <a href="http://webapp.etsi.org/workprogram/Report_Workitem.asp?WKI_ID=8105" target="_blank">http://webapp.etsi.org/workprogram/Report_Workitem.asp?WKI_ID=8105</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Recommendation Q.767, ITU-T. <a href="http://www.itu.int/rec/T-REC-Q.767/en" target="_blank">http://www.itu.int/rec/T-REC-Q.767/en</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Recommendation Q.767, ITU-T. <a href="http://www.itu.int/rec/T-REC-Q.767/en" target="_blank">http://www.itu.int/rec/T-REC-Q.767/en</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Recommendation Q.761, ITU-T. <a href="http://www.itu.int/rec/T-REC-Q.761/en" target="_blank">http://www.itu.int/rec/T-REC-Q.761/en</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Russell 2002, pp. 362–419. - Russell, Travis (2002), Signaling System #7 (4th ed.), New York: McGraw-Hill, ISBN 978-0-07-138772-9 <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>ITU-T 1999b. - ITU-T (December 1999b) [1996], Recommendation Q.784.1 (07/96), ISUP basic call test specification: Validation and compatibility for ISUP'92 and Q.767 protocols <a href="http://www.itu.int/rec/T-REC-Q.784.1/en/" target="_blank">http://www.itu.int/rec/T-REC-Q.784.1/en/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>ITU-T 1999a, pp. 3–4. - ITU-T (December 1999a), "Section 1, General coding principles", Recommendation Q.763 <a href="http://www.itu.int/rec/T-REC-Q.763-199912-I/en/" target="_blank">http://www.itu.int/rec/T-REC-Q.763-199912-I/en/</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>Russell 2002, p. 321. - Russell, Travis (2002), Signaling System #7 (4th ed.), New York: McGraw-Hill, ISBN 978-0-07-138772-9 <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>ITU-T 1999a, p. 3. - ITU-T (December 1999a), "Section 1, General coding principles", Recommendation Q.763 <a href="http://www.itu.int/rec/T-REC-Q.763-199912-I/en/" target="_blank">http://www.itu.int/rec/T-REC-Q.763-199912-I/en/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> </ol>