I understand that FOP2 displays all DAHDI extension as active, as it not easy to determine whether a handset is connected to the line.
However, I do not understand why all the IAX2 extensions are also shown as active, even when they are not logged in!
IAx peer status in AMI does not show registration information in many asterisk versions as far as I remember. only sip registration status is available. Besides, registration status <> active. For active I asume busy/inuse.. not registerd/unregistered/lagged.
Best regards,
Nicolas,
I don't know how far in Asterisk you are trying to support, but I have an old PBX which is running Asterisk 1.4 - iax2 show peers displays OK for any active IAX2 extension. FOP2 should be able to monitor that.
I am sure that FOP2 can determine the version of asterisk that it is running, and determine how to handle IAX2 extensions accordingly?
Nicolas,
I don't know how far in Asterisk you are trying to support, but I have an old PBX which is running Asterisk 1.4 - iax2 show peers displays OK for any active IAX2 extension. FOP2 should be able to monitor that.
I am sure that FOP2 can determine the version of asterisk that it is running, and determine how to handle IAX2 extensions accordingly?
Hi, FOP2 does not use the console. It uses AMI. AMI integration with IAX is, as I said, flacky at best. Are you using Asterisk 1.4? Grep "manger_event" on chan_iax2.c and compare to asterisk 1.8. Even in 1.4 I think there is no IaxPeer manager command (I do not recall, it's been a while I am not looking at 1.4 installations).