Bug 60 - Use configured source port for outgoing TCP connections
Summary: Use configured source port for outgoing TCP connections
Status: NEW
Alias: None
Product: resiprocate
Classification: Unclassified
Component: stack (libresip) (show other bugs)
Version: unspecified
Hardware: All All
: P1 enhancement
Assignee: Owner of all unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-03 03:09 CST by Daniel Pocock
Modified: 2014-01-03 03:09 CST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Pocock 2014-01-03 03:09:53 CST
r10711 fixes bug 24, ensuring that the configured bind address for a TCP-based transport (including TLS) is used as the source IP for outgoing connections.

However, the source port is still selected randomly.  Some users may prefer to use a single source address (e.g. 5060) for their outgoing connections, for example, because of very strict corporate firewall practices.

This can probably be implemented using socket options SO_REUSEPORT and SO_REUSEADDR

If this behavior is changed, then it should be optional.