Page History

...

• For ISUP A->SIP-I->ISUP A, the source and destination ISUP versions are the same and the

  Spacevars
  0 product

  components in the middle are simply transiting the MIME attachment.
• For ISUP A->SIP-I->ISUP B (depicted by the orange arrows), the source and destination ISUP versions are different and the

  Spacevars
  0 product

  must understand the ISUP MIME and convert from one variant to another.
• For ISUP A->SIP (depicted by the blue arrows), the call is destined to a point where the ISUP MIME can no longer be understood (such as terminating to a SIP IAD) and the

  Spacevars
  0 product

  must interwork the SIP-I/ISUP-MIME into plain SIP. In these cases, the operators may insist on mapping of ISUP information into non-standard SIP headers in order to preserve the functionality of some feature (e.g. BT, CPWH with RBWF).