AnsweredAssumed Answered

CURRI KeepAliveTimeout

Question asked by nathan.a.reeves on Jan 8, 2017
Latest reply on Jan 24, 2017 by nathan.a.reeves

Taking a look at CURRI with CUCM 11.5.  Been seeing error messages in the logs on CUCM RTMT in regards to the the Timeout value being less than 1000.  From what I can see CURRI expects the timeout to be returned from the server in milliseconds (eg 1000) but the server is returning the value as seconds.  From what I can see in the standards, the value should be specified in seconds.  Only presents an issue where a web server following the standards and reports in seconds.  When we're using a custom app serving web content (eg the sample python app  serving a keepalivetimeout value in ms is possible).


Was this a known issue / Intentional?