Hi Janine,

Actually let me explain what you are seeing. In CVP 4.0, we introduced the concept of application loggers, which are special plugins that can do logging for you. These loggers do their things in different threads. Now, when a call ends, previously we deleted the session once all tasks done at the end of the call (such as the end of call class and final logging) was done. Now, though, the logging is done in separate threads and could cause errors if we deleted the session too quickly. So what we have done is delay the deleting of the session for a period of time (default is 30 seconds - you can change this in the global_config.xml file). Now an ending call frees up a license port for use, but is still in memory in the session until this 30 seconds are up. In order to allow the administrator to see when a call is in that stage, we introduced the new column in the status output for "sessions ending".

So if you went to the subdialog return page and called the status, you would see 0 active calls and 1 call ending. If you then wait 30 seconds, you will see both columns at 0. So its not the audium_action=hangup that did it, though it looked like it was because the whole process took 30 seconds! You do not need to do any pages after you see a VoiceXML page with a <return> tag in it.

Hope this clarifies things!