No disconnect action is being taken

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start unimrcp server (use sip over tcp in config)
2. start umc.exe and give run recog
3. kill umc process at some random point

What version of the product are you using? On what operating system?
unimrcp 1.1.0. the problem probably continues in trunk.
windows7 64 bit.

Please provide any additional information below.
I see that neither channel close nor channel destroyed when the client app 
exits (crashes vs.). In fact we discovered that in our stress tests. We exit 
the umc client at random points  and observe if unimrcpserver.exe is  in a 
stable state. Further analysis showed that the following function has not been 
implemented:

apt_bool_t mrcp_server_on_disconnect(mrcp_channel_t *channel)
{
    /* to be processed */
    return TRUE;
}

I think this is probably related to our problem.
mrcp_server_on_engine_channel_close seems to start a series of calls which may 
lead to calling mrcp_server_session_terminate_process in the end. Could simply 
calling mrcp_server_on_engine_channel_close from this function possible let us 
solve the leaking connection problem and let the corresponding channel 
close/destroy function be called. 

Could you please direct us on how to process server disconnect function. 

Original issue reported on code.google.com by [email protected] on 24 Feb 2014 at 9:58

[GoogleCodeExporter]

Seems like google-groups are more frequently used and this issues page are 
inactive for some time.

With more research in the google groups I've seen the following topics all of 
which are mentioning the same problem I have.
https://groups.google.com/forum/?fromgroups#!searchin/unimrcp/peer$20disconnect/
unimrcp/RaCymP0D8SQ/sMPEhl5rujYJ

https://groups.google.com/forum/#!topic/unimrcp/dHMiMG3zeD0

https://groups.google.com/forum/#!topic/unimrcp/yKa3_U_-jsg

You may close this issue.

Regars

Original comment by [email protected] on 27 Feb 2014 at 12:39

[GoogleCodeExporter]

Thanks for putting all the relevant information together. This issue needs to 
be addressed sooner or later.

Original comment by [email protected] on 8 Apr 2014 at 2:37

• Added labels: Type-Defect, Priority-Medium, OpSys-All, Component-Server, Usability