Does FreePBX 11.xx support Beta asterisk 11.x?

Question

linux

I have been using this link for a long time, I have not experienced any problems. But the other day I installed asterisk 11.3 and ran into some problems when connecting some extensions that used to work (on early versions of asterisk) without problems.

In a detailed study of the output of the asterisk console, I found, for example, the following warnings:

pbx_config.c:1640 pbx_load_config: The use of '_.' for an extension is strongly discouraged and can have unexpected behavior.  Please use '_X.'
...
pbx.c:11998 ast_context_verify_includes: Context 'macro-outisbusy' tries to include nonexistent context 'macro-outisbusy-custom'
...
sip/config_parser.c:812 sip_parse_nat_option: nat=yes is deprecated, use nat=force_rport,comedia instead
...

the most interesting, perhaps, concerns nat.

Information on the Internet about support is incredibly contradictory. On the freepbx forums they claim that version 2.11 supports the 11th asterisk, on Habré and other resources they claim the opposite.

Tell me who in practice uses this bunch, how are things in fact?

Answer 1

You probably meant fpbx version 2.11 (The major version of fpbx will match the version of asterisk starting from 12).

pbx_config.c:1640 pbx_load_config: The use of '_.' for an extension is strongly discouraged and can have unexpected behavior. Please use '_X.'
...

This warning says the following:
The dialing plan uses a dialing pattern that absolutely all dialing options fall under. It's the same if you don't use a template at all.
fbpx does not create such templates on its own. Users can create them.

pbx.c:11998 ast_context_verify_includes: Context 'macro-outisbusy' tries to include nonexistent context 'macro-outisbusy-custom'
...

Everything is simple here. Asterisk says that one of the dial plan contexts does not exist. But it doesn't exist, because fbpx creates such contexts as needed: when the required module is installed, when the user has added a dial plan to the _custom.conf files. However, fbpx directly announced their existence in the config.
For example, take the sip.conf file and open it. Part of the inserts by the #include directive are essentially empty.

sip/config_parser.c:812 sip_parse_nat_option: nat=yes is deprecated, use nat=force_rport,comedia instead
...

Most likely, the nat=yes parameter is defined in the peer section. The peer section is created not by fpbx, but by users. The asterix parser found a bug.