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

ims_qos: create a proper flow description for the SIP signaling #720

Closed

Conversation

vingarzan
Copy link
Contributor

  • before there was just an empty one in the AAR
  • re-using the function typically used for the RTP media
  • fixing then that function to not just hard-code protocol 17 (UDP) for everything
  • now supporting also 6 (TCP) and IP (IP has no protocol number, we use just the
    magic word "ip" (see RFC 3588 IPFilterRule for more details)
  • adding the IP of the P-CSCF as a parameter to the module, as this is required
    in the flow (UE IP <-> P-CSCF IP)
  • also some inline/static fixes to function for avoiding warnings on gcc >=5

- before there was just an empty one in the AAR
- re-using the function typically used for the RTP media
- fixing then that function to not just hard-code protocol 17 (UDP) for everything
- now supporting also 6 (TCP) and IP (IP has no protocol number, we use just the
magic word "ip" (see RFC 3588 IPFilterRule for more details)
- adding the IP of the P-CSCF as a parameter to the module, as this is required
in the flow (UE IP <-> P-CSCF IP)
- also some inline/static fixes to function for avoiding warnings on gcc >=5
@vingarzan
Copy link
Contributor Author

Will complete with or more fix to the ims_registrar_pcscf module and then request again (sorry for the spam)

@vingarzan vingarzan closed this Jul 20, 2016
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

Successfully merging this pull request may close these issues.

None yet

2 participants