Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

execute() does not detect socket disconnection #84

Open
ssinyagin opened this issue Dec 19, 2019 · 4 comments
Open

execute() does not detect socket disconnection #84

ssinyagin opened this issue Dec 19, 2019 · 4 comments
Labels

Comments

@ssinyagin
Copy link

I'm running synchronous outbound ESL socket toward the node-esl server. If the server starts an conn.execute(xxxx) command, and the socket disconnects during the execution, the execute() never returns and hangs forever.

by looking through the sources of Connection.js, I couldn't find any handling for such event.

Here's my code:

                    function run_phrases() {
                        if( phrases.length > 0 && input === null ) {
                            let file = phrases.shift() + ext;
                            console.log(conn.cs.uuid + ' Playing ' + file);
                            try {
                                conn.execute('play_and_get_digits', '1 1 1 10 # ' + file + ' "" dialed_digits',
                                             function(ev) {
                                                 input = ev.getHeader('variable_dialed_digits');
                                                 if( input !== null ) {
                                                     console.log(conn.cs.uuid + ' User pressed ' + input);
                                                 }
                                                 run_phrases();
                                             });
                            }
                            catch (err) {
                                if( err.code != 'ERR_STREAM_DESTROYED' ) {
                                    console.error(err);
                                }
                                else {
                                    console.log(conn.cs.uuid + ' disconnected');
                                }
                                reject();
                            }
                        }
                        else {
                            resolve();
                        }
                    }
                    
                    run_phrases();
@englercj englercj added the Bug label Dec 19, 2019
@ssinyagin
Copy link
Author

net.Socket is not sending "end" event on error. It sends "close" in both error and non-error cases, and that's when you need to emit esl::end

I'll send a PR

ssinyagin added a commit to voxserv/node-esl that referenced this issue Jan 6, 2020
net.Socket emits "end" only on successful closing, but it emits "close" in error conditions as well.
ssinyagin added a commit to voxserv/node-esl that referenced this issue Jan 6, 2020
net.Socket emits "end" only on successful closing, but it emits "close" in error conditions as well.
@ssinyagin
Copy link
Author

also a branch to fix it in 1.2.1: https://github.com/voxserv/node-esl/tree/v1.2.1-bugfix

@englercj
Copy link
Owner

englercj commented Jan 7, 2020

Can you open a PR for that branch to the v1.x branch?

@pablito25sp
Copy link

Until this is merged you can set up the callback on your own code.

    connection.socket.on('close', (hadError: boolean) => {
      if (hadError) logger.warn('esl socket closed with error')
      else logger.debug('esl socket closed')
      endCall()
    })

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants