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

Ice error message for invalid transaction ID prints junk #59

Closed
orai-arturo opened this issue May 31, 2019 · 2 comments · Fixed by #61
Closed

Ice error message for invalid transaction ID prints junk #59

orai-arturo opened this issue May 31, 2019 · 2 comments · Fixed by #61
Assignees

Comments

@orai-arturo
Copy link

Running against master

ice ERROR: 2019/05/31 12:44:31 discard message from (relay ... related ...), invalid TransactionID ؛������+�

@Sean-Der
Copy link
Member

Sean-Der commented Jun 1, 2019

Thanks for reporting! I think this is from the STUN migration.

@ernado mind checking this out when you are free?

@Sean-Der Sean-Der transferred this issue from pion/webrtc Jun 1, 2019
@Sean-Der
Copy link
Member

Sean-Der commented Jun 4, 2019

@ernado mind checking this out when you get a chance? thanks!

ernado added a commit that referenced this issue Jun 4, 2019
Receiving the messages with transaction ID that is currently not in
progress is expected.

* Change output format to hexademical to improve readability
* Change log severity to warning
* Update wording (invalid -> unknown)

Relates to #59
ernado added a commit that referenced this issue Jun 4, 2019
Receiving the messages with transaction ID that is currently not in
progress is expected.

* Change output format to hexademical to improve readability
* Change log severity to warning
* Update wording (invalid -> unknown)

Relates to #59
Sean-Der pushed a commit that referenced this issue Jun 4, 2019
Receiving the messages with transaction ID that is currently not in
progress is expected.

* Change output format to hexademical to improve readability
* Change log severity to warning
* Update wording (invalid -> unknown)

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

Successfully merging a pull request may close this issue.

3 participants