#865 closed enhancement (fixed)
More clever RTP transport remote address switch
Reported by: | bennylp | Owned by: | nanang |
---|---|---|---|
Priority: | major | Milestone: | release-2.8 |
Component: | pjmedia | Version: | trunk |
Keywords: | sipit24 | Cc: | joost, joel |
Backport to 1.x milestone: | Backported: | no |
Description (last modified by ming)
Currently the UDP and ICE media transport has the capability to switch destination RTP/RTCP address to the source address of the RTP/RTCP packets, if they are different than the original address set in SDP received from remote.
It may be better to put this functionality in the stream instead, for the following reason:
- the stream has more information about the packet, such as RTP pt, SSRC, and info from RTCP statistic
- some application that uses media transport wants to inspect and possibly filter the source address
- some firewall such as Microsoft Forefront Threat Management Gateway wants us to send the RTP to the address in SDP, regardless of the source address of the RTP packet
Change History (11)
comment:1 Changed 16 years ago by bennylp
- Description modified (diff)
comment:2 Changed 16 years ago by bennylp
- Priority changed from normal to major
comment:3 Changed 16 years ago by bennylp
- Cc joost joel added
comment:4 Changed 15 years ago by bennylp
- Keywords sipit24 added
- Milestone changed from Sipit24 to release-1.3
- Version changed from Sipit24 to trunk
comment:5 Changed 15 years ago by bennylp
- Milestone changed from release-1.3 to release-1.4
comment:6 Changed 15 years ago by bennylp
- Milestone changed from release-1.4 to release-1.5
comment:7 Changed 15 years ago by bennylp
- Milestone changed from release-1.5 to release-1.6
comment:8 Changed 15 years ago by bennylp
- Milestone changed from release-1.6 to Known-Issues-and-Ideas
comment:9 Changed 13 years ago by bennylp
Enhancement of this behavior in #1366
comment:10 Changed 7 years ago by ming
- Backported unset
- Description modified (diff)
- Milestone changed from Known-Issues-and-Ideas to release-2.8
comment:11 Changed 7 years ago by ming
- Resolution set to fixed
- Status changed from new to closed
In 5752:
Version 0, edited 7 years ago
by ming
(next)
Note: See
TracTickets for help on using
tickets.
There is a temptation to support multiple callback users, so that multiple applications (e.g. stream and PJSUA-LIB) can peek the incoming RTP/RTCP packets. Some sample usage of this includes:
Sure this can be done by creating transport adapter, but utilizing multiple callback users will make it lot easier for application (e.g. application doesn't need to handle transport creation in PJSUA-LIB).
Pending for further review. Moving to 1.4 milestone.