for a vanilla call process, the called party will hangup immediately after the caller cancels the call before it's answered, this is true when im using 

<action application="bridge" data="user/${destination_number}" />

in the dialplan xml.

however, if the call is handled by a lua script with a pattern like

sessionB = freeswitch.Session('user/xxxx');

if sessionB:ready() then

freeswitch.bridge(session, sessionB);

else

cause = sessionB:hangupCause();

if (cause == "NO_USER_RESPONSE" or cause=="NO_ANSWER") then

session:streamFile("user_no_answer.wav");

end

session:hangup();

end

the called party is still ringing after the caller cancels the call before it's answeredŁ¬this lua call process pattern is from wiki so im pretty sure it's being widely used, but why im having this problem? could someone figure this out?