ISUP Remote Signaling Destination

The ISUP Remote Signaling Destination objects are children of the ISUP Local Signaling Destination object.

There is an ISUP Remote Signaling Destination object for each adjacent exchange. This object contains configuration parameters and status information for the ISUP signaling stack within the adjacent exchange.

Note that you must configure a Signaling Destination object for the adjacent exchange before you can configure the ISUP Remote Signaling Destination object.

For initial configuration of an ISUP Remote Signaling Destination, you need to do the following:


You cannot delete an ISUP Remote Signaling Destination or change its Destination field if it has one or more Proxied ISUP Circuit Group child objects. You will need to delete these child objects before you can delete or change the parent object.


Parameter

Access

Description
ISUP Remote Signaling Destination index Read only The EMS's identifier for this ISUP Remote Signaling Destination object. This is used to identify the object when using the EMS's configuration export / import function.
Destination Change Inactive The Signaling Destination corresponding to the remote exchange, or to the cluster containing the remote exchange. Select from the displayed list of configured Signaling Destinations. This list does not include internal destinations on the Signaling Gateway referenced by the parent ISUP Local Signaling Destination. If there is no Signaling Destination with a matching point code, or if you attempt to set a default MTP3 destination (point code 0-0-0), this field will display Reference not valid.
Network number Change A numeric identifier for the remote network, which will appear in transit billing records for outgoing calls to this remote exchange. Specify a different number for each remote network, so that all remote exchanges on the same network have the same network number.
Cluster member address Change Inactive This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Active hop counting Change Specifies whether to add a hop count to messages, if one is not already present, and decrement any existing hop counts. Values:
  • False (default)
  • True
Maximum congestion level Change The maximum congestion level recognized by the remote exchange. When an exchange is overloaded it can attach an Automatic Congestion Level parameter to Release Messages at the end of a call. This parameter tells the calling exchange to reduce the calls to the overloaded exchange, and contains a congestion level which indicates how congested the overloaded exchange is. However, not all exchanges support changing their behavior to handle the varying degrees of congestions. For example, an exchange may only have two modes - uncongested and congested. This switch sends Automatic Congestion Level parameters only for levels that the remote exchange will recognize. Values:
  • Level 1
    The remote exchange recognizes only uncongested and Level 1 (the least severe level of congestion).
  • Level 2
    The remote exchange recognizes only uncongested and the lowest two levels of congestion.
  • Level 3 (default)
    The remote exchange recognizes uncongested and all three levels of congestion, including Level 3 (the most severe level of congestion).
  • Uncongested
    The remote exchange does not recognize any congestion levels.
CLLI Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Override local CLLI code Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Local CLLI code override value Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999 and Override local CLLI code is set to True. It does not apply in the UK.
Error handling mode Change Specifies whether the MetaSwitch NE should play the error tones or announcements if the call fails (for example if the called party does not exist). Values:
  • No tones required (default)
    The MetaSwitch NE does not play the tones or announcements. Instead it sends an error code back to the calling switch, and the calling switch plays the tones or announcements.
  • Tones always required
    The MetaSwitch NE always plays the tones or announcements, rather than sending an error code back to the calling switch. This option uses more network capacity than No tones required, because it requires a circuit from the MetaSwitch back to the caller for the duration of the tone or announcement.
  • Tones if interworking
    The MetaSwitch NE plays the tones or announcements if the call spans different types of network between the originating and terminating switches. If the call remains on an ISUP network, MetaSwitch sends the error code so that the calling switch can handle the error.
Request remote echo cancellation devices Change Specifies whether the MetaSwitch NE should request echo cancellation resources from the remote destination rather than supplying its own. Values:
  • True (default)
    Request echo cancellation resources from the remote destination.
  • False
    The NE will supply its own echo cancellation resources. This value is typically used when the NE is acting as a tandem switch and the remote destination is an end office, if echo cancellation resources at the end office are scarce or of lower quality.
Confusion messages Change If the MetaSwitch NE is unable to recognize an ISUP message, it may discard the message. If this happens, this field determines whether the NE sends a Confusion message (ISUP message of type CFN) back to the sending exchange. If the sending exchange receives a Confusion message, it may try to resend a simpler message. The GR-246 specification requires that this behavior is configurable, but you are recommended to leave this field as the default; unrecognized messages should be very rare. Values:
  • True (default)
  • False
Direct IXC connection Change
  • This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Peer network type Change The type of the network at the remote destination. This field is used only for ISUP tandem calls. If a call is rejected by a remote exchange, the rejection message will include a location value. If the calling remote exchange is not on the same network as the MetaSwitch, the MetaSwitch will change the location value from "local network" to "remote network" before passing the rejection back to the calling exchange. Values:
  • Same network (default)
  • Local network
  • Private network
  • Transit network
  • International network
Maximum simultaneous continuity tests Change This field does not appear if the parent ISUP Local Signaling Destination's ISUP variant is set to UK. It does not apply in the UK.
Exchange performs LNP lookup Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
International exchange Change Specifies whether the link to this remote destination is an international link. Leave this field set to its default value.
USI parameter coding type Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Charge number and outgoing line information Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Jurisdiction information parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Redirecting number parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Redirection information parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Original called number parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Access transport parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Generic address parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. Specifies whether the Generic Address parameter is allowed in an outgoing IAM to this remote exchange. Values:
  • True (default)
  • False
Generic name parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Party information parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
Redirect capability parameter Change This field appears only if the parent ISUP Local Signaling Destination's ISUP variant is set to ANSI 1999. It does not apply in the UK.
CIP parameter Change Specifies whether the Carrier Identification Parameter (CIP) should be included on Initial Address Messages (IAMs) to the remote exchange. The CIP contains the 4 digit code identifying the carrier chosen for the call by the calling party. If the call originated from this switch, a carrier is associated with the call if the FGD carrier requirement attribute is set during Number Validation to indicate that a carrier is required for the call. If the call originated from another switch, the CIP and TNS parameters will be provided by the originating switch. In addition, the CIP parameter can be sent based on the carrier for the call, rather than for all calls to the remote exchange. This configuration option is not currently customer-accessible, so please contact your Support Engineer if you need this feature. The CIP is related to the Carrier Selection Information (CSI) parameter, which indicates how the carrier was chosen (pre-subscribed or casual dialed). By default the CSI parameter is not sent. If you require the CSI parameter to be sent in IAMs, please contact your Support Engineer because this configuration option is currently not customer-accessible. Values:
  • True (default)
    The CIP is included in outgoing IAMs if there is a carrier associated with the call, either by pre-subscription or by casual dialing. If the call is from this switch and there is no associated carrier, or if the originating switch did not provide a CIP, the CIP is never included in the outgoing IAM.
  • False
    The CIP is not included on outgoing IAMs, unless the TNS is present and the Direct IXC connection field (on this object) is set to False. In this case the CIP will still be sent if it exists.
The TNS parameter indicates which carrier's network the switch has chosen to carry the call. This may be different from the carrier chosen by the calling party, so it is a separate parameter.
Incoming ACC processing Change Specifies whether the softswitch should pay any attention to incoming messages containing the Automatic Congestion Level (ACC) parameter. ACC is a process that allows an overloaded exchange to attach an Automatic Congestion Level parameter to Release Messages at the end of a call, which tells the calling exchange to reduce the calls to the overloaded exchange. The current congestion level of the remote exchange is shown by the Congestion status field on this object. Values:
  • True (default)
  • False
TNS parameter Change Specifies whether the softswitch should accept incoming IAMs if they contain the Transit Network Selection (TNS) parameter. This is used to indicate which carrier should be used to carry the call, and is typically removed just before the call is passed to the carrier's network. Note that this is not the same as the CIP parameter, which indicates which carrier the caller choose; the two carriers may not be the same. Note also that, unlike most of the other fields on this object, this field applies to incoming IAMs and not to outgoing IAMs. Values:
  • True
    Incoming calls with the Transit Network Selection parameter are accepted.
  • False (default)
    Incoming calls with the Transit Network Selection parameter are rejected.
Congestion status Read only The current level of congestion in the ISUP stack of the remote exchange. Values:
  • Uncongested
  • Level 1
  • Level 2
  • Level 3
Availability status Read only The status of the ISUP stack in the remote exchange. Values:
  • Available
  • Unavailable
  • Unavailable - busy
  • Unavailable - failed
  • Unavailable - paused
ACC congestion status Read only ACC congestion status. Values:
  • Level 1
  • Level 2
  • Level 3
  • Uncongested
Deactivation mode Change Specifies how child objects should be deactivated when deactivating this object. Values:
  • Normal (default)
    Shut down child objects normally before deactivating the object.
  • Quiesce
    Deactivating the ISUP Remote Signaling Destination object in quiesce mode will wait for all existing child objects using the object to be completed before deactivation. No new child objects using this object will be accepted during this deactivation period.
  • Abort
    Deactivate the object and all its child objects immediately. (This may result in errors at remote systems.)
If a Normal or Quiesce deactivation is already in progress, you can force a faster deactivation by changing the value from Normal to Quiesce or from Quiesce to Abort.
Alarm state Read only Specifies whether any alarms are currently raised for this object. Values:
  • Clear
    No alarms are currently raised.
  • Attention Required
    Attention Required - the object is not operating normally, and needs operator intervention.
Alarm log correlator - Attention Required Read only Identifier of the log message for the event that caused the last Attention Required alarm state for this object. This field is reset when the Attention Required alarm events field is reset to zero.
Attention Required alarm events Read only / Reset Number of times (since this field was reset) that this object's alarm state has gone to Attention Required.
Alarm log correlator - Attend To Dependent Read only Identifier of the log message for the event that caused the last Attend To Dependent alarm state for this object. This field is reset when the Attend To Dependent alarm events field is reset to zero.
Attend To Dependent alarm events Read only / Reset Number of times (since this field was reset) that this object's alarm state has gone to Attend To Dependent.
Alarm state changed timestamp Read only Time at which the Alarm state last changed.
Alarm events reset timestamp Read only Time at which the Attention Required alarm events field was last reset to zero.
Media Channel and Circuit Group Attention Required alarms Read only The total number of Media Channels and Circuit Groups (and their child objects) associated with this ISUP Remote Signaling Destination that are in Attention Required state.
Media Channel and Circuit Group Attention Required alarm events Read only / Reset The total number of times that the alarm state for a Media Channel or Circuit Group child object has gone to Attention Required.
Media Channel and Circuit Group Attend To Dependent alarms Read only The total number of Media Channels and Circuit Groups (and their child objects) associated with this ISUP Remote Signaling Destination that are in Attend To Dependent state.
Media Channel and Circuit Group Attend To Dependent alarm events Read only / Reset The total number of times that the alarm state for a Media Channel or Circuit Group child object has gone to Attend To Dependent.
Summary child alarm state Read only Summarizes the alarm status for all children of this object. Values:
  • Clear
    No alarms are currently raised.
  • Attention Required
    Attention Required - one or more child objects are not operating normally, and need operator intervention.
  • Attend To Dependent
    Attention Required elsewhere - another object on which one or more child objects depend is not operating normally.
Diagnostics - logging - log level Change Specifies the level of logs recorded for this object. Logs with a priority equal to or greater than the priority specified are recorded. Set to Default level to use the system-wide default level. Values:
  • Level 10 (diagnostics)
  • Level 20 (verbose statistics)
  • Level 30 (verbose operational)
  • Level 40 (statistics)
  • Level 50 (audit)
  • Level 60 (operational)
  • Level 70 (unexpected)
  • Level 80 (error)
  • Level 90 (fatal)
  • Default level (default)
Diagnostics - API trace - enabled Change Specifies whether API tracing is enabled for this object. Values:
  • True
  • False (default)
Diagnostics - API trace - trace tag Change An optional text string inserted into API tracing and PD logging for this object. (This string can include accented / international characters as defined in ISO 8859-1.) If you want to filter on this tag in the craft interface, do not include spaces or any of the characters ^ \ $ * + ? | ( ) , . ' ' " [ ] { }.
Requested status Read only Specifies whether an administrator has attempted to activate the ISUP Remote Signaling Destination. Values:
  • Active
    The object has been activated.
  • Inactive
    The object has not been activated or has been deactivated.
  • Disabled
    The object has been disabled.
Actual status Read only Specifies the current status of the ISUP Remote Signaling Destination. Values:
  • Active
    The object is active.
  • Activating
    Activation is in progress.
  • Deactivating
    Deactivation is in progress.
  • Inactive
    The object is inactive.
  • Disabled
    The object has been disabled.
  • Activation Failed
    The object is inactive because an activation attempt has failed.
  • Failed
    The object was active but has failed.
  • Quiescing
    The object is preparing for normal deactivation. It is operating normally but will not accept any new users.
  • Waiting For Parent
    The object cannot be used because its parent object is not yet active.
  • Parent Failed
    The object cannot be used because its parent object has failed.