What I would suggest is try this process out on a simple project first. Create a module project "BModule" and export to the modules directory. Then create "AMain" that uses "BModule". Now rename "Bmodule" to "XModule", and then export it to the reusable modules directory. Now delete the Bmodule from the reusable modules directory. Open (in your favorite text editor) the main.flow file in "AMain" and replace references of "Bmodule" with "XModule". Same for the web.xml file.

<FlowNode class="com.avaya.sce.callflow.internal.appflow.Module" id="3" version="3.1">
<Property name="FlowNodeEditPart.WidgetX" value="215"/>
<Property name="FlowNodeEditPart.WidgetY" value="28"/>
<Property name="ModuleTypeID" value="ZMod"/>
<Property name="ModuleCallType" value="Subdialog"/>
<Property name="Name" value="ZMod1"/>
<FlowItem class="com.avaya.sce.callflow.internal.flowitem.Module" id="4" version="1.2">
<ItemProperties/>
<ChildItems>
<FlowItem class="com.avaya.sce.callflow.internal.flowitem.Submit" id="5" version="1.2">
<ItemProperties>
<Property name="LinkedNodeID" value="6"/>
</ItemProperties>
<ChildItems/>
</FlowItem>
</ChildItems>
</FlowItem>
</FlowNode>

No I cannot explain why. It seem to have been that way forever.

Wilson's answer stands.

I would not recomment that, it will just cause you grief.

If you must. After you rename your modules, A) reexport (deeploy into the reusable modules directory), B you will need to hand edit the main flow file and update the names there and in the web.xml file, C) refresh your project, D) regenerate the project, and E) remove the old modules from <eclipse_home>/DialogDesigner/Modules.

In Od 7.2 on export there is an option to save the ant build script file.

It has to do with how the browsers works and the VXML specification. All prompts are queued and only played when the browser waits for input. In your case the application is already at the end when the prompt queue is flushed out (the exit node).

So you say maybe I will place a "flush prompts" on the announce. The issue is that the prompt queue is flushed while the fetch of the next document is already started and the next VXML page returned is the exit node. When the announce prompt queue is flushed, the "fetch" of the next page will trigger the untitledApplicationTracking1 servlet which executes and forwards the http request to the untitled return.

However if you do this ( Start -> Announce1 -> Announce2 -> untitledtrackign1 -> untitledReturn ) with flush prompts on both announce nodes you will see things are as you expect them. If you leave out the flush prompt, then you will see the original behavior.

Since this is only a simple announce and nothing else the next page is already being fetch before the hangup is detected even using flush prompts. If you have the same applicaiton with a prompt and collect you would see things work as expected.

The session slot shows an issue when fetching /ConsentIVR/GetConsentFromCustomer-LogConsentPresented/

@2018-02-26 12:36:21,009|PAVB_00224|ERROR|VB|2923|Session=adc-cpod-aaep-mpp1-2018057173157-28|Socket Error in function SWIsocket::is_writeready:select, WSA_ERROR_NAME: errno, errorCode: 32|adc-cpod-aaep-mpp1.cable.comcast.com####


Interestingly I see a "DTMF No Input STATUS CODE IS REC_STATUS_TIMEOUT (NO_INPUT)" on http://ncoweb-as-p01:8080/ConsentIVR/GetConsentFromCustomer-PlayConsentSummaryCollect, just before that fetch.

Out of curiosity, what if you altered the prompt timeout from 8000 (8 seconds) to somethign high? I would not think that would have any effect as the recognition unless bargin was allowed possibly.

The prompt play before the recognition is only 4 seconds.

Not sure what is happening here. Maybe the above information will help. I think this is now a platform issue.

That is ODD. I did see this

@2018-02-23 14:32:43,029||FINEST|VB|2749||Session logger for SessionID walynptelwaepmpp02-2018054222813-4 not found! Using global logger instead|walynptelwaepmpp02####

which I have never seen before.

Later I see

@2018-02-23 14:28:13,689||FINEST|VB|2810||VXML_DIALOG_PREPARE
{
mppSessionID: "67123703"
loggingSlot: "SessionSlot-004"
sessionIdentifier: "walynptelwaepmpp02-2018054222813-4"

So SessionSlot-004.log should have the data.

Without the session slop log I could not make any firther determination.

VB / VXI toamto / tomaaaato :)

The other is you go to under System Management /MPP servers / MPP Settings / Categories and Trace Levels Set Voice Browser to Finest. Then use Real-Time Monitoring / <click on your mpp server name>, and on the next page select Service Menu. That will take you to a new page in a new window. From there you can access the mpp logs. I typically clear all the logs then make a test call/run and then examine the resulting log. Look under VXI

that is the session manager not the VXI log. Sorry I shoudl have been more clear. Please attach the VXI session slot that matches the OD trace.log.

What about the sessionslot log from the MPP?

It is possible that could be affeting things. This file is not from OD.