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.

Sign up for GitHub

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

Jump to bottom

ACKs and unhandled responses #120

Open
yallxe opened this issue Aug 13, 2024 · 3 comments
Open

ACKs and unhandled responses #120

yallxe opened this issue Aug 13, 2024 · 3 comments
Labels
breaking change critical Critical issue documentation Improvements or additions to documentation enhancement New feature or request

Comments

@yallxe
Copy link

yallxe commented Aug 13, 2024

Is there a way in sipgo to catch unhandled responses? Let's say I have a case where the server missed the ACK I've send after WaitAnswer() finished. How should I handle such cases?
@emiago
Copy link
Owner

emiago commented Aug 14, 2024

I am confused is it response from server missed, or just ACK from client after getting 200ok

@yallxe
Copy link
Author

yallxe commented Aug 14, 2024

The second one, ACK from client.

@emiago
Copy link
Owner

emiago commented Aug 15, 2024

yes, ok this also fails in this corner case, same as Cancel.
Normally you will get 2xx retransmitted, and you should Re ACK, but currently you may need to handle this as caller, until we introduce some API interface.

@emiago emiago added documentation Improvements or additions to documentation enhancement New feature or request critical Critical issue breaking change labels Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change critical Critical issue documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@emiago @yallxe