Multiple network interfaces

[penguinpbx (C. Maj)]

@Bogazki

Friends, I was able to solve this.

@Bogazki

After adding or changing a transport, you need to reboot. Because pjsip show transports didn’t show any transports before rebooting.

This is hard to do in all scenarios without at least a restart of Asterisk – although not necessarily a reboot of the entire system.

Also, you could try enabling Allow Transports Reload at the top of the PJSIP settings page, with some caveats (see FreePBX forum post here, Asterisk blog post here, Asterisk GitHub issue here, etc.)

@Bogazki

FreeBX may not make changes to trunk configuration files that have already been created, but only when they are created.

Hmm, that sounds like a bug, possibly for the issue tracker. But, it could be related to transports not changing dynamically, without either modifying the reload setting as mentioned above (or restart/reboot) not sure.

@Bogazki

It might be due to extensions. I’ll try deleting it and creating it again.
because they were created before changes in the transport infrastructure and also used UDP 0.0.0.0

What about changes made after the reboot ? Are those all set now ? Or is an Asterisk restart/system reboot not enough to correct things ?

@Bogazki

I can check the configuration files, but freepbx doesn’t like it when change.

Changing transports on a server is usually kind of a big deal – lots of low-level network related things are happening when you do that, and if there’s active calls on those interfaces that are disappearing, well, you and your users are not going to have a very good time.