How to Address DSR Info Application ID Mismatch Causing INFO Event 22003

Asset ID:	1-71-2297022.1
Update Date:	2017-08-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2297022.1 : How to Address DSR Info Application ID Mismatch Causing INFO Event 22003

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 6.0 and later
Information in this document applies to any platform.

Goal

Why is the following INFO event seen:

TIMESTAMP: 2017-08-14 14:07:12.001 EDT
NETWORK_ELEMENT:
SERVER: (server>
SEQ_NUM: 39820572
EVENT_NUMBER: 22003
SEVERITY: INFO
PROCESS: dsr
TYPE: DIAM
INSTANCE: MP
NAME: Application ID Mismatch with Peer
DESCRIPTION: While attempting to route a request message to a peer, a peer's diameter connection was bypassed because the peer did not support the Application ID for that diameter connection.
ERR_INFO:
GN_INFO/INF Peer Name=,Diameter Connection Name=,Application ID=,New Application ID List= ,Origin-Host AVP=,Peer Routing Table Rule=No PRT Rule,Route List Name=No route used.
^^ [17518:DrlRequest.C:6559]

Solution

The system's peer routing table may be using a Route List containing a peer which does not support the Application ID or the list of Application IDs supported by the peer on each connection may not be the same. The list of Application IDs that the peer supports on each connection can be viewed as follows:
1. Navigate to the GUI page: Diameter > Maintenance > Connections
2. Locate the relevant Peer Node and check the supported Application IDs.
If Application IDs are not the same for each connection (but should be) the Application ID for any connection can be refreshed by:
1. Navigate to the GUI page: Diameter > Maintenance > Connections
2. Locate the relevant Connection
3. Disable the Connection
Enable the Connection
The Diameter Node which originated the message (identified by the Origin-Host AVP) could be configured incorrectly and the application is trying to address a node which doesn't support the Application ID. This cannot be fixed using this application.

Attachments

This solution has no attachment