On Mon, 30 Jun 2014 17:33:25 +0200, Eeri Kask wrote:
> [...]
> The sip-provider "mangles" the above m= and c= during the initial INVITE
> request/response and attempts to reroute the stream through its own
> relay (according to inserted IP's, port numbers), so the first thought
> is they are inbetween now as well, but there is no proof.
For the sake of completeness, there is proof that the sip-provider does
its job fine too: from the moment of activating "--use-tls" (and then
"--registrar=sip:provider.org;transport=tls") for pjsua each and every
problem disappeared. (It looks like "common" sip-providers offering
free service all support tls, though mostly not prominently documented,
nevertheless it works right out of the box.)
Inspecting the firewall logs it looks like it has been under occasional
DoS and other attacs on its external interface. Still it remains to be
clarified why media streams by "usual", i.e. provider-relayed (i.e.
non-ICE) transport was apparently not manipulated and ICE-transport was...
Eeri Kask
