#204 Connectivity problems
Connectivity Problems:
• Connection attempt is scheduled when DPA is received and the Disconnect-Cause sent in DPR is “REBOOTING”. It means that system is going to reboot and it is in the same time trying to reconnect.
• Connection attempt is not scheduled when DPA is received and the Disconnect-Cause sent in DPR is “BUSY”.
• The general rule is that a connection attempt shall be scheduled (with some exception) when the peer entry is in the DIAMETER_PEER_ST_CLOSED state but there is number of state transitions to the DIAMETER_PEER_ST_CLOSED state without a connection attempt scheduled. These transition include:
o All error scenarios (DiameterPeer_Error)
o All state transition caused by DPR message (DiameterPeerI_SendDPADisconnect and DiameterPeerI_SendDPADisconnect).
o The state transition from the DIAMETER_PEER_ST_CLOSED to the DIAMETER_PEER_ST_CLOSED – a connection attempt is cancelled but not rescheduled.
o CEA with status code different from SUCCESS is received. The transition to the DIAMETER_PEER_ST_CLOSED state is caused by the FSM restart. The problem is not fixed by the patch.
o DWA with status code different from SUCCESS is received. The transition to the DIAMETER_PEER_ST_CLOSED state is caused by the FSM restart. The problem is not fixed by the patch.
• With the respect to the previous item, a reconnect attempt shall be cancelled for all transitions from the DIAMETER_PEER_ST_CLOSED state excluding the state transition caused by the DIAMETER_PEER_EV_START event.
Timer management:
The timer DIAMETER_PEER_EV_TIMEOUT is scheduled when the state is changed from DIAMETER_PEER_ST_CLOSED to DIAMETER_PEER_ST_WAIT_CONN_ACK (a connect attempt) and when the state is changed from DIAMETER_PEER_ST_I_OPEN (or DIAMETER_PEER_ST_R_OPEN) to DIAMETER_PEER_ST_CLOSING. The timer shall be therefore cancelled in transition from the states DIAMETER_PEER_ST_WAIT_CONN_ACK and DIAMETER_PEER_ST_CLOSING. Therefore, there is no need to cancel timer in the following situations:
• DiameterPeerR_AcceptSendCEA
The patch for the listed problems is attached. The similar patch was tested on the version 1.0.7h and this patch was tested on the revisin 374.
Patch for the above problems. It cam be aplied on the latest revision (376)