[SR-Users] Struggling with RTPProxy and RTPEngine
abalashov at evaristesys.com
Thu Aug 23 10:43:40 CEST 2018
The expectation that the RTP will come from the same place as the signalling does exist in some sclerotic telco interconnects, since big brand SBCs would ordinarily meet this need and big brand SBCs are the only thing sclerotic telcos understand.
But I agree that it's an exotic and uncommon requirement, certainly not applicable to anything like end-user UAs or ordinary business SIP devices.
Sent from mobile. Apologies for brevity and errors.
From: Daniel Tryba <d.tryba at pocos.nl>
To: "Kamailio (SER) - Users Mailing List" <sr-users at lists.kamailio.org>
Sent: Thu, 23 Aug 2018 4:35 AM
Subject: Re: [SR-Users] Struggling with RTPProxy and RTPEngine
On Wed, Aug 22, 2018 at 05:05:02PM +0000, Wilkins, Steve wrote:
> The SIP traffic is working this way for me but I still see RTP traffic going directly from Asterisk to the UAC, which means they need to whitelist asterisk IP. Am I missing something?
In what sense do they need whitelisting? In a common NATed solution
where is no white/blacklist needed. UA gets RTP endpoints from SDP,
starts sending packets to ip/port and the destination will send back
packets to the source ip/port, the router/firewall will just send this
to the actual UA. I have yet to find an UA that cares about where the
RTP stream is coming from with regards to the SIP traffic.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sr-users