Configuring ISUP Learning Exceptions

ISUP learning is used to assist with the routing of public-initiated TCAP transactions to the appropriate private node. In many class feature call flows, an IAM precedes the public TCAP query. Using the IAM's routing label and CIC, a trunk mapping record is found which determines the destined private node. That same IAM contains the Called Party Number (or Original Called Party Number) attributes that are used in the TCAP's SCCP Called Party Address signals for GT routing. Thus if the IAM's digits are learned with the associated private node from the trunk mapping, on receipt of the TCAP, the SCCP Called PA digits find a match. The private node, therefore, is found without requiring a GTT search. Each ISUP learning record has a lifespan (default 24 hours).

ISUP learning exceptions are dialed numbers that are not associated with a fixed private node (for example, 800 numbers). Routing of this service can vary based on time or day and location of caller. The ISUP learning information should not be kept for those digits and can be excluded from ISUP learning. By default, there are no ISUP learning exceptions defined.

To create an ISUP learning exception (Basic and Enhanced PCE)

To view an ISUP Learning Exception