Hi,
I realized that after tearing a session down in the QoS-NSLP, this session
was effectively torn down in the QoS-NSLP but the routing state for the
session was not deleted at the GIST layer. Therefore, I could see some
refreshing QUERY/RESPONSE messages every 50 seconds.
Looking at the NSIS NTLP draft, I understood there were two ways for the
routing state to be deleted :
- either when there is no activity for this session (in this case a timer
has to be reset each time some data corresponding to this session is
either sent or received)
-or when the signaling application calls the SetStateLifetime() function
of the API with 0 as the state lifetime.
It seems that the first solution is not implemented in the 0.5.1-dev
version of the NSIS stack (I couldn't see any timer being reset in the
GistFsmSender::Rx_Data_Msg() and GistFsmSender::Establ_Api_SendMsg()
functions).
Then I tried to use the second solution : calling the SetStateLifetime()
function of the API when releasing the reservations for a flow in the
QoS-NSLP. But at the GIST layer the SetStateLifetime() function (in
./nsis-0.5.1-dev/gist/nslp_api/nslp_api.cpp) only displays the MRI. I
wanted to add a condition so that if the state_lifetime parameter was
equal to 0, the fsm corresponding to the session should be deleted. The
problem was that I couldn't identify the fsm because the SID is not part
of the parameters of the SetStateLifetime() function (although Appendix
B.5 of the NSIS NTLP drafts say the SID should be one of the parameters).
Can anyone confirm this before I start looking at how to add the SID to
the parameters ?
Regards,
Bertrand
