blanchae
Guru
- Joined
- Mar 12, 2008
- Messages
- 1,909
- Reaction score
- 9
chan_iax2.c: Ignoring bindaddr on reload - NOT SOLVED
It appears that restarting Asterisk and the network services is not enough. Must be some persistance in the network - arp cache, on the switch, etc.. Turned everything back on again today after shutting it all down and now it works and then it doesn't with 1.6.2.6...
Did find a bug with IAX2 and the iax_general_custom.conf file. bindaddr=xxx.xxx.xxx.xxx is ignored on reload. Here's the error message:
chan_iax2.c: Ignoring bindaddr on reload
It defaults back to address 0.0.0.0 which is any interface.
The purpose of the bindaddr="IP address of interface" is to direct IAX2 to only use a specific interface for communication.
This is ABSOLUTELY necessary if you are using VLANs on your PiaF box.
Example: if you have an IAX softphone (PC) on the Data VLAN and attempt to register to PiaF using its Voice VLAN interface (which you should for QoS), PiaF responds with its Data VLAN interface. The softphone chokes on the reply because it received the wrong IP address. It was expecting a Voice VLAN IP address.
I see that it is a recurring bug and the FreePBX crew has been addressed about it over the years but it keeps popping up. I'll follow up on it with FreePBX.
It appears that restarting Asterisk and the network services is not enough. Must be some persistance in the network - arp cache, on the switch, etc.. Turned everything back on again today after shutting it all down and now it works and then it doesn't with 1.6.2.6...
Did find a bug with IAX2 and the iax_general_custom.conf file. bindaddr=xxx.xxx.xxx.xxx is ignored on reload. Here's the error message:
chan_iax2.c: Ignoring bindaddr on reload
It defaults back to address 0.0.0.0 which is any interface.
The purpose of the bindaddr="IP address of interface" is to direct IAX2 to only use a specific interface for communication.
This is ABSOLUTELY necessary if you are using VLANs on your PiaF box.
Example: if you have an IAX softphone (PC) on the Data VLAN and attempt to register to PiaF using its Voice VLAN interface (which you should for QoS), PiaF responds with its Data VLAN interface. The softphone chokes on the reply because it received the wrong IP address. It was expecting a Voice VLAN IP address.
I see that it is a recurring bug and the FreePBX crew has been addressed about it over the years but it keeps popping up. I'll follow up on it with FreePBX.
Phone System 