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

not close socket connection on server #64

Open
matheuspazesteves opened this issue Dec 12, 2023 · 1 comment
Open

not close socket connection on server #64

matheuspazesteves opened this issue Dec 12, 2023 · 1 comment

Comments

@matheuspazesteves
Copy link

What I'm trying to solve is,
A leg ----> call ---> B leg. then A leg execute att_xfer to C leg and hangup.
Is there any way to keep the socket open while still observing the new channel with C and B?
I had no problem transferring B to C, but when it is the origin(A leg) that execute att_xfer the socket closes the connection.

@shimaore
Copy link
Owner

@matheuspazesteves once the call is transferred it might not be present on the server anymore — the connection between A and C might not go through FreeSWITCH.

If you know for sure that the transferred call stays on the server I'm happy to spend some time investigating how to get ahold of it, feel free to send me a request through e.g. Github Sponsor.

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

No branches or pull requests

2 participants