Opened 12 years ago
Closed 12 years ago
#1575 closed enhancement (duplicate)
Bind TCP and TLS client socket to the configured address too
Reported by: | bennylp | Owned by: | bennylp |
---|---|---|---|
Priority: | normal | Milestone: | release-2.1 |
Component: | pjsip | Version: | trunk |
Keywords: | Cc: | ||
Backport to 1.x milestone: | Backported: | no |
Description
For TCP and TLS, currently only the server (i.e. listening) socket will be bound to the configured bind address. Client (i.e. outgoing/connecting) sockets are let to be bound by the OS when connect() is performed.
This ticket will change the behavior to bind the client sockets to the configured bind address as well, so that the explicit interface will be selected.
Thank you Dan Arrhenius for the suggestion.
Change History (1)
comment:1 Changed 12 years ago by bennylp
- Backport to 1.x milestone release-1.16 deleted
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The fix is integrated in #1585.