No audio after UPDATE packages behind NAT #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The variable is used to determine if a device is present on the local network. If the device is on the local network, Kamailio must present itself to the device with its private IP address. If the device is located outside on the internet, Kamailio must use its public IP address. Additional local networks can be added using the `local_networks` field of the JSON object passed to the `configure-module` action. The field is only used in a NAT scenario when a public IP is also set.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Audio get routed to the wrong address when Asterisk send an UPDATE packet while being behind a NAT.
In this scenario, the UPDATE packets were inadvertently modifying dlg_var(direction) variable within Kamailio. This variable is used to track the direction of the media flow (RTP packets) and is integral to the business logic that manages media handling through rtpengine_manage.
When dlg_var(direction) was altered by the UPDATE packets, it caused inconsistencies in how media flow direction was being handled, leading to disruptions in the call handling process. Essentially, the logic that determined the direction of RTP streams was getting confused, which could result in issues like incorrect media routing and dropped calls after 30 seconds.
https://evoseed.atlassian.net/servicedesk/customer/portal/5/EA-29