Hi! Issue I can’t figure out. Or all working ok and that’s just me who not understands.
I have situation softPhone (111.222.3.2) -> Kamailio w. rtpproxy (111.222.3.3) -> PBX (111.222.3.4) All addresses are on same public network. rtpproxy is running with -l 111.222.3.3 -A 111.222.3.3 I want all media goes through rtpproxy. So, in INVITE and ACK I call rtpproxy_manage(). But according to sip packets on PBX (10.0.0.4) I got media address 10.0.0.2 in SDP, but not 10.0.0.3
If I use scheme, where client in some other NATted network (like 192.168.1.100), all is replaced correctly (means rtpproxy_manage() is working)
So, I can’t understand, rtpproxy_manage() changes only rfc1918 addresses or I’m missing something? If any - can provide pcap’s with both cases.
Regards, Igor
Sorry, I got media address 111.222.3.2 in SDP, but not 111.222.3.3
Regards, Igor
On 22 дек. 2016 г., 19:19 +0200, Igor Olhovskiy igorolhovskiy@gmail.com, wrote:
Hi! Issue I can’t figure out. Or all working ok and that’s just me who not understands.
I have situation softPhone (111.222.3.2) -> Kamailio w. rtpproxy (111.222.3.3) -> PBX (111.222.3.4) All addresses are on same public network. rtpproxy is running with -l 111.222.3.3 -A 111.222.3.3 I want all media goes through rtpproxy. So, in INVITE and ACK I call rtpproxy_manage(). But according to sip packets on PBX (10.0.0.4) I got media address 10.0.0.2 in SDP, but not 10.0.0.3
If I use scheme, where client in some other NATted network (like 192.168.1.100), all is replaced correctly (means rtpproxy_manage() is working)
So, I can’t understand, rtpproxy_manage() changes only rfc1918 addresses or I’m missing something? If any - can provide pcap’s with both cases.
Regards, Igor
That just sounds like the rtpproxy is not being engaged, i.e. that the rtpproxy_manage() call is failing. When that happens, the SDP from .2 will be passed through unaltered.
The Kamailio log should give you some idea of why the rtpproxy invocation has failed.
RTPProxy is certainly not limited to RFC 1918 addresses or any particular network characteristics.
-- Alex
Yep, logs helps. Actually, was mix of errors in PBX and Kamailio config. So yea, rtpproxy is working as expected, can’t say same for my config files :)
Regards, Igor
On 22 дек. 2016 г., 19:24 +0200, Alex Balashov abalashov@evaristesys.com, wrote:
That just sounds like the rtpproxy is not being engaged, i.e. that the rtpproxy_manage() call is failing. When that happens, the SDP from .2 will be passed through unaltered.
The Kamailio log should give you some idea of why the rtpproxy invocation has failed.
RTPProxy is certainly not limited to RFC 1918 addresses or any particular network characteristics.
-- Alex _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On Thu, Dec 22, 2016 at 12:23:52PM -0500, Alex Balashov wrote:
That just sounds like the rtpproxy is not being engaged, i.e. that the rtpproxy_manage() call is failing. When that happens, the SDP from .2 will be passed through unaltered.
The Kamailio log should give you some idea of why the rtpproxy invocation has failed.
I'd guess rtpproxy_manage() isn't failing, it just isn't called since dialplan logic is only instructed to do this for natted stuff. Since the source ip and SDP both contain the same ip the assumption is that rtpproxy is not needed.
Oh, I see. Yes, that could be.
-- Alex
On Dec 22, 2016, at 12:49 PM, Daniel Tryba d.tryba@pocos.nl wrote:
On Thu, Dec 22, 2016 at 12:23:52PM -0500, Alex Balashov wrote: That just sounds like the rtpproxy is not being engaged, i.e. that the rtpproxy_manage() call is failing. When that happens, the SDP from .2 will be passed through unaltered.
The Kamailio log should give you some idea of why the rtpproxy invocation has failed.
I'd guess rtpproxy_manage() isn't failing, it just isn't called since dialplan logic is only instructed to do this for natted stuff. Since the source ip and SDP both contain the same ip the assumption is that rtpproxy is not needed.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Daniel Tryba -
Igor Olhovskiy