[OpenSIPS-Users] Minimal example of NAT traversing. How could it be done? No need for MediaProxy at first glance.

Wed Aug 5 09:59:14 CEST 2015

Hi Nabeel,

You mentioned getting some "failed to load module" errors - maybe your 
script id pointing to a different path rather than where your opensips 
is installed.

The "unknown commnad" errors are side effects of modules not being loaded.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 05.08.2015 07:25, Nabeel wrote:
> Hi,
>
> I used 'make menuconfig' to create a script with NAT support and a few 
> of the other options like 'use_dbusrloc'.
>
> When I check with 'opensips -c' I get a bunch of errors saying 'failed 
> to load module' (see examples below). I used the script as provided 
> from the script generator, with only IP/db info changes.  Does the 
> script generator work with version 1.11.5 of OpenSIPS?
>
> ERROR:core:yyparse: module 'signaling.so' not found in 
> '/usr/local/lib/opensips/modules/'
>
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 382, column 21-22: unknown 
> command <nat_uac_test>, missing loadmodule?
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 383, column 21-22: unknown 
> command <fix_nated_contact>, missing loadmodule?
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 385, column 21-22: unknown 
> command <rtpproxy_answer>, missing loadmodule?
>
> ERROR:core:set_mod_param_regex: no module matching tm found
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 66, column 19-20: 
> Parameter <fr_timeout> not found in module <tm> - can't set
> ERROR:core:set_mod_param_regex: no module matching tm found
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 67, column 20-21: 
> Parameter <fr_inv_timeout> not found in module <tm> - can't set
> ERROR:core:set_mod_param_regex: no module matching tm found
> CRITICAL:core:yyerror: parse error in config file 
> /usr/local//etc/opensips/opensips.cfg, line 68, column 19-20: 
> Parameter <restart_fr_on_each_reply> not found in module <tm> - can't set
>
>
>
>
>
> On 4 August 2015 at 17:39, Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>> wrote:
>
>     Rodrigo,
>
>     In OpenSIPS you have 2 type of NAT modules:
>     - for NAT detection, mangling SIP signaling and for doing the NAT
>     keepalive: you have here the NAT_traversal and nathelper, 2
>     similar modules as capabilities;
>     - for media relay - modules that interact with an external media
>     relay for RTP; and here you have again 2 modules, the mediaproxy
>     and rtpproxy.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>     On 04.08.2015 16:51, Rodrigo Pimenta Carvalho wrote:
>>
>>     Hi Bogdan,
>>
>>
>>     Thank you. Very well remembered!
>>
>>
>>     Let me ask you conceptual question, please:
>>
>>
>>     When should I use MediaProxy, not being necessary to use
>>     NAT_TRAVERSAL and NATHELPER?
>>
>>
>>     When should I use NAT_TRAVERSAL, no being necessary to use
>>     MediaProxy and NATHELPER?
>>
>>
>>     When should I use NATHELPER, not being necesary to use MediaProxy
>>     and NAT_TRAVERSAL?
>>
>>
>>     When should I use some kind of mix of these 3?
>>
>>
>>     Best regards.
>>
>>
>>
>>
>>
>>     RODRIGO PIMENTA CARVALHO
>>     Inatel Competence Center
>>     Software
>>     Ph: +55 35 3471 9200 <tel:%2B55%2035%203471%209200> RAMAL 979
>>     ------------------------------------------------------------------------
>>     *De:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>>     <mailto:bogdan at opensips.org>
>>     *Enviado:* terça-feira, 4 de agosto de 2015 09:21
>>     *Para:* OpenSIPS users mailling list; Rodrigo Pimenta Carvalho
>>     *Assunto:* Re: [OpenSIPS-Users] Minimal example of NAT
>>     traversing. How could it be done? No need for MediaProxy at first
>>     glance.
>>     Hi Rodrigo,
>>
>>     User "make menuconfig" in order to auto-generate scripts - the
>>     residential script has an options for NAT support.
>>
>>     Regards,
>>     Bogdan-Andrei Iancu
>>     OpenSIPS Founder and Developer
>>     http://www.opensips-solutions.com
>>     On 04.08.2015 00:00, Rodrigo Pimenta Carvalho wrote:
>>>
>>>     Dear OpenSIPS-users,
>>>
>>>
>>>     I'm studying about NAT traversal with OpenSIPS, since last week.
>>>     I also have found the documentation about the software
>>>     MediaProxy (in http://mediaproxy.ag-projects.com/).
>>>
>>>
>>>     As long as I'm still getting 'kind of first steps' knowledge
>>>     base about NAT traversal, I'm not interested, at least for a
>>>     while, in MediaProxy software functionalities.
>>>
>>>     By the way, as a first contact with the NAT traversal mechanism,
>>>     I just would like to let the INVITE from a caller reaches
>>>     the callee, with caller behind a NAT. For this purpose I have 2
>>>     questions:
>>>
>>>
>>>     a) Am I free of using a kind of mediaproxy
>>>     software, whether I want to build a prototype schema that
>>>     will just creates and sends an simple INVITE, from caller behind
>>>     a NAT, to a callee? That is, if I want just to run a simple test
>>>     of NAT traversal, I don't have to worry about mediaproxies, have I?
>>>
>>>
>>>     b) How could be an example of a simplest script code for that,
>>>     considering that there is only one proxy for all peers
>>>     and all of it is registered in such proxy using the same domain?
>>>
>>>
>>>     Any hint will be very helpful!!
>>>
>>>     Thanks a lot.
>>>
>>>
>>>     RODRIGO PIMENTA CARVALHO
>>>     Inatel Competence Center
>>>     Software
>>>     Ph: +55 35 3471 9200 <tel:%2B55%2035%203471%209200> RAMAL 979
>>>
>>>
>>>     _______________________________________________
>>>     Users mailing list
>>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150805/d39a4049/attachment.htm>