Hello,
Are you using fix_contact from the nat_traversal module ? I have only
tested with fix_nated_contact from the nathelper module, but I just
checked the code and they should both work without any issues.
The scenario should work as long as you call the contact fixing function
before the create_dialog(), but please check with calling fix_contact()
right before of create_dialog(), maybe there is something spooky going
on in-between the two function calls.
Waiting for you testing results. Thanks.
Regards,
--
Vlad Paiu
OpenSIPS Developer
On 08/22/2011 01:32 PM, Saúl Ibarra Corretgé wrote:
Hi Vlad,
On Aug 22, 2011, at 11:52 AM, Vlad Paiu wrote:
Hello Saúl,
The modifications to the script API should not have affected the behaviour.
I have just done a test with the latest OpenSIPS trunk with a very similar scenario
( dialog end parties behind NAT ) and everything went fine ( the caller&
callee contacts are the fixed ones ).
Could you please ngrep on such a call and check if your fixing on the Contact
fields actually get applied ? Maybe it's some kind of scripting error.
Modifications were actually applied, I'll re-check but call was correctly
established, otherwise I would have lost the ACK. It also worked fine on
OpenSIPS 1.6.4.
In order to test the feature I chained 2 proxies, the first one just fixed the
NAT and the second one did the dialog stuff. In this case it worked, since the
Contact was already fixed by the first proxy.
If I call fix_contact and right after create_dialog will the create_contact
dialog 'see' that the contact was modified?
Nevertheless I'll test it again tonight.
Regards,
--
Saúl Ibarra Corretgé
AG Projects
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
