Evangelos Ribeiro Tzaras 8b126484cb sip: Use per origin IP instead of a global IP ... Sofia detects a NAT by presence of the "received" parameter in the Via header in the response to a REGISTER. Sofia will then update the Contact header to use the IP as reported by the registrar. The "received" parameter MUST be included in the response according to https://datatracker.ietf.org/doc/html/rfc3261#section-18.2.1 when the registrar detects a difference between the domain part of the top Via header and the packet source address but practice has shown that this will not always be the case. Addditionally this change allows us to have origins bound to different network interfaces which would be useful when a registrar can only be accessed through a VPN. This also fixes an issue with SDP introduced in 36880c3d34 which was only seen on some SIP providers: The session name ("s=") line is not relevant for establishing a connection, the connection data (c=") line is. See https://datatracker.ietf.org/doc/html/rfc4566 section 5.3 and 5.7		2022-01-08 21:25:09 +00:00
..
dummy	origin: Get rid of "numeric-addresses" property	2021-12-26 17:45:12 +01:00
mm	origin: Get rid of "numeric-addresses" property	2021-12-26 17:45:12 +01:00
ofono	origin: Get rid of "numeric-addresses" property	2021-12-26 17:45:12 +01:00
sip	sip: Use per origin IP instead of a global IP	2022-01-08 21:25:09 +00:00
meson.build	sip: Initial provider	2021-04-03 00:08:31 +02:00