Bug#859911: RTP uses wrong source address

Bernhard Schmidt berni at debian.org
Sun Apr 9 07:39:33 UTC 2017


Package: asterisk
Version: 1:13.14.0~dfsg-1
Severity: important

On systems with several IP addresses (i.e. clusters or multihomed servers)
the RTP media stream often uses another source IP address than the transport
used. 

This should be fixable with the following upstream commits in 13.15.0

2017-04-03 15:38 +0000 [2634f48fb5]  Richard Mudgett <rmudgett at digium.com>

	* res_pjsip_sdp_rtp.c: Don't alter global addr variable.

	  * create_rtp(): Fix unexpected alteration of global address_rtp if a
	  transport is bound to an address.

	  * create_rtp(): Fix use of uninitialized memory if the endpoint RTP media
	  address is invalid or the transport has an invalid address.

	  ASTERISK-26851

	  Change-Id: Icde42e65164a88913cb5c2601b285eebcff397b7

2017-03-14 16:22 +0000 [139bc3495f]  Richard Begg <asterisk at meric.id.au>

	* res_pjsip_sdp_rtp: RTP instance does not use same IP as explicit transport

	  Currently a wildcard address is used for the local RTP socket, which
	  will not always result in the same address as used by the SIP socket
	  (e.g. if explicit transport addresses are configured).
	  Use the transport's host address when binding new local RTP sockets if
	  available.

	  ASTERISK-26851

	  Change-Id: I098c29c9d1f79a4f970d72ba894874ac75954f1a



More information about the Pkg-voip-maintainers mailing list