Hello Craig,
As said, this is just side comment, not a try to cover the problem -
IMHO you are right (in regards to maddr handling in nat_traversal) and
that should be fixed.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 23.05.2014 04:38, Craig Guy wrote:
Thanks Bogdan,
I'd seen in an older mailing list message that nat_traversal went with
mediaproxy and nathelper went with rtpproxy. I'll switch back to
nathelper and troubleshooting my mediaproxy nat issue.
Craig
On 23 May 2014 00:25, Bogdan-Andrei Iancu <[email protected]
<mailto:[email protected]>> wrote:
Hello Craig,
Not trying to deviate from the actual bug, but for both cases
(rtpproxy and mediaproxy) the signaling modules are completely
different from the modules talking to the external media relays.
So, you can use the mediaproxy relay (via the mediaproxy module)
in combination with the nathelper module for the contact fixing.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 22.05.2014 12:44, Craig Guy wrote:
Hi,
I was using nathelper with fix_nated_contact and have changed
over to using nat_traversal and fix_contact as I am having some
other issues with mediaproxy but found that calls are failing
with the apparent difference being that nathelper removes maddr
from the initial INVITE Contact whilst nat_traversal leaves it
intact.
This is causing opensips to route the received PRACK to the maddr
private IP in the contact header and the call to fail.
Is this correct operation for the nat_traversal module and is
there another way to remove the maddr from the contact?
This is with opensips 1.10
Craig
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
