I test the template “ TransDemo2” with Dialogic card D/41EPCI and found the following problem :- <br> <br>* after establishing the call between the two port and then hang-up . The program remains looping because it is not recognize the global hang-up event. <br>Can you direct me what to do? <br> <br>Note : when I used the Simulator to test the program it perform OK.

We need you to do a test to determine if this is a hangup supervision or an application issue. <br> <br>Please do the following: <br> <br>Run your test until you reach the point at which the application is stuck in an endless loop. Then, pull the phone cable(s) from the Dialogic card. Does the application recognize the hang up and respond to it properly at that point? If it doesn't, use 'Show Messages' on the TeleFlow Monitor, and copy the entire contents of the window into your reply. <br> <br>We will follow-up with further instructions based on your response.

Hello Chriss <br> <br>If you remember I received mail from you that teleflow team will do some thing regarding this Issue. <br>Let me know what happen?

The issue is that in your location, the Telco doesn't provide a loop current drop to indicate that a caller has hung up the phone, and so your record step continues to record after a hang up, until the maximum record time is reached. In analog environments, this is how TeleFlow determines that a hang up has occurred, and jumps to the Global Hangup label. What needs to happen is that during a record, TeleFlow needs to "listen" for reorder tones (the tones played by the Telco indicating the end of a call), and generate its own hangup event in that way. <br> <br>This is expected to be addressed in the next release of TeleFlow, scheduled for the beginning of July. <br> <br>We will update this post when the July release is available, and to state whether or not the fix for the issue was indeed able to be released.