ISUP definition

ISUP means a part of the SS7 protocol that defines call setup messages and call takedown messages.
ISUP means ISDN User Part;
ISUP and Transaction Capabilities Application Part ("TCAP"), and platforms such as adjuncts, Public Safety Systems (911), Operator Services, Directory Assistance Services and Advanced Intelligent Network ("AIN"). Remote Switching Module functionality is included in the Local Switching function. Local Switching shall also be capable of routing local, intraLATA, interLATA, and international calls to the subscriber's preferred carrier, call features (e.g., call forwarding)

Examples of ISUP in a sentence

  • The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks.

  • The parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the interconnection of their networks.

  • The Parties will cooperate on the exchange of all appropriate SS7 messages for local and intraLATA call set-up signaling, including ISDN User Part (ISUP) and Transaction Capabilities Application Part (TCAP) messages to facilitate full interoperability of all CLASS Features and functions between their respective networks.

  • Either the Union or the Employer may initiate a grievance at Step 2 if the grievance is submitted in writing within ten (10) business days from the date the Employer/employees became aware or reasonably should have known that the grievance existed.

  • The Parties will cooperate on the exchange of all appropriate SS7 messages for local and intraLATA call set-up signaling, including ISUP and Transaction Capabilities Application Part ("TCAP") messages to facilitate full interoperability of all CLASS Features and functions between their respective networks.

  • It also provides access to transport, signaling (ISDN User Part (ISUP) and Transaction Capabilities Application Part (TCAP), and platforms such as adjuncts, Public Safety Systems (911), operator services, Directory Assistance Services and Advanced Intelligent Network (AIN).

  • For all Toll Traffic originated by or terminated to CLEC’s QLSP End User Customer, Qwest may ▇▇▇▇ applicable tariff charges, including SS7 message charges [ISDN User Part (ISUP) and Transaction Capabilities Application Part (TCAP)], to the Interexchange Carrier (IXC) or other wholesale SS7 provider.

  • The Parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Bellcore Standards including ISDN user part ("ISUP") for trunk signaling and Transaction Capabilities Application Part ("TCAP") for CCS-based features in the interconnection of their networks.

  • The parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks.

  • It also provides access to transport, signaling (ISDN User Part (ISUP)) and Transaction Capabilities Application Part (TCAP), and platforms such as adjuncts, Public Safety Systems (911), operator services, Directory Assistance Services and Advanced Intelligent Network (AIN).


More Definitions of ISUP

ISUP. ISUP Version : set to “uk”, “us”, “jp” or “itu” In addition, the Content-Disposition header shall be supported in order to explicitly tag whether the handling of the ISUP is optional or required. An example encapsulated ISUP message would look something like :- --unique-boundary-1 Content-Type: application/ISUP; version=uk; Content-Disposition: signal; handling=mandatory 01 00 49 00 00 03 02 00 07 04 10 00 33 63 21 43 00 00 03 06 0d 03 80 90 a2 07 03 10 03 63 53 00 10 0a 07 03 10 27 80 88 03 00 00 89 8b 0e 95 1e 1e 1e 06 26 05 0d f5 01 06 10 04 00 --unique-boundary-1-- The sending MGC may send either national or ITU variants of ISUP. It is recommended that ITU ISUP be tagged as optional and national versions are tagged as mandatory. The recipient MGC will respond in the following ways :- • If the encapsulated ISUP is marked as “optional” then it will be processed (if understood) and ignored if not. • If the encapsulated ISUP is marked as required and the egress MGC does not understand either the variant of ISUP or it does not understand ISUP at all then it shall respond with 415, "Unsupported Media Type". On receipt of a 415 response, a MGC may then either reject the call or re-send the invite. If the MGC chooses to re-send the invite and in the case where it first encapsulated national version of ISUP, then it may choose to encapsulate international ISUP. In this case, the handling is marked as “optional”. This approach aids inter-operability since (in the general case) a recipient MGC may not understand ITU ISUP but would still permit thew call to proceed. In terms of the GMI2004 event, it is expected that all MGCs will be provisioned with data to enable them to encapsulate the correct version of ISUP on a given interface. Within the packet network SIP servers do not understand encapsulated ISUP, and do not modify or look at the encapsulated message. A conforming recipient MGC shall ensure that the SIP headers take precedence over the ISUP. This is based on the possibility that the contents of SIP headers may be updated by an intermediate SIP server within the IP network. For this profile, en-bloc working shall be applicable (i.e. end of dialling determination applied by the originating CA).