IAX module do not accept config if minregexpire time if less than maxregexpire time but works if is greater.
Hi!
I can’t test it right now as I don’t currently have access to a FreePBX system but it looks like the comparison was inverted…
I am not fully sure though because the message says
Minregexpire is greter then Maxregexpire
and I am not sure what greter then means, I only know what greater than means… 
If after clearing your browser cache you still have that problem I would suggest creating a ticket on http://issues.freepbx.org if one does not already exist…
Good luck and have a nice day!
Nick
After clearing cache I have the same popup error message. But it works if I set 120 and 3600. So I just leaved like this
Hi!
This actually has been fixed in Edge with iaxsettings v14.0.1.2.
re: https://issues.freepbx.org/browse/FREEPBX-15722
I am no Javascript guru but it looks like the problem is that minregexpire and maxregexpire were compared as text and not as numbers.
“60” is indeed greater than “3600” since “6” is after “3” in ASCII and its derivatives…
The test has been changed (for now only in Edge I believe) so that minregexpire and maxregexpire are compared as integers…
The “greter then” typo has been fixed but is now in what appears to be title case (“greater” is written with a capital “G”) for some unknown reason… Since this is not a title I am not sure why this was done…
As soon as it get outs of Edge (or if you decide to switch to Edge) you won’t have the problem you had anymore…
Good luck and have a nice day!
Nick
A simple workaround is to type Minregexpire value “60” as “060” so that the comparison works out correctly.
And it’s actually javascript that is performing that validation.
1 Like