SOLVED: Suddenly OBi's won't work with Asterisk — port registration issue
MichiganTelephone:
One more thought...
There is an interesting discussion on the variations on Asterisk's NAT parameter at http://www.voip-info.org/wiki/view/Asterisk+sip+nat — it turns out that nat=never is probably "never" an appropriate setting for many devices, since it was introduced to solve a specific issue with certain types of hardware. Just for fun I tried setting nat=no on the settings for these devices and so far that seems to work as well as nat=yes (and seems more appropriate for a LAN). I'm not sure when I first started using nat=never for internal extensions but it probably dates back to the days of Asterisk@Home and some "recipe" I saw online.
Even reading that page on voip-info.org it's confusing as to whether it's better to just always use nat=yes, or if it really is more appropriate to use nat=no if the device and server are on the same LAN. Just in passing I'll note that setting nat=yes seems to more consistently hold the qualify (ping) times down to around 3 ms, while using nat=no sometimes seems to result in slightly higher times (but generally only 1 or 2 ms higher).
Still, the thing I can't wrap my head around is that the OBi110 worked great with the nat=never setting for nearly a full week.
Speaking of that 3 ms ping time, that's another thing I can't wrap my head around — the next lowest ping time for any device on this LAN is 9 ms and the average is more in the 12-13 ms range. These babies are fast! :D
Navigation
[0] Message Index
[*] Previous page