The IWF is a converter, therefore, traffic is received and sent to both the SS7 and Diameter networks. The handling of the messages is based on the type of the message; query or response.

If the IWF is licensed and traffic is activated, on startup, IWF immediately connects to both the SS7 (through the configured SCCP user port) and Diameter (through the configured DSC Diameter UA port). The IWF cannot function without both connections, so critical alarms are raised (except on initial startup) on connection loss and traffic deactivation.

For information about IWF alarms, see the DSC Alarms Guide.

SCCP PC-SSN and AppID registrations (see Configuring SCCP Registrations) are only initiated when Diameter and SCCP connectivity both have been established.

Note

The SCCP and IWF applications have reserved Application IDs. For more information, refer to Reserved Application IDs for SS7 Applications.

Considerations for Traffic Management

Outgoing SS7/MAP Traffic is encoded in an SCCP UDT. The Originating-Host AVP is used to find the Node Mapping necessary for the SCCP Calling Party Address while the Destination-Host (or Destination-Realm AVP+Application ID) is used for the SCCP Called Party Address (see Configuring IWF Node Mappings).

Outgoing Diameter traffic uses two node mapping records to determine the Originating-Host AVP and Destination-Host AVP. The SCCP Calling Party Address digits are used to find the Node Mapping necessary for the Originating-Host AVP while the SCCP Called Party Address digits are used for the Destination-Host AVP.   

Note

Only the SS7 Number attribute in the Node Mapping is used to query the record.  The remaining SCCP PA attributes are used for outgoing SS7 traffic only.

  • No labels