EDIT: For me the problem turned out to be that I had set "nat=never" and changing it to "nat=yes" fixed the problem. Keep reading if you want to see what we went through to figure that out!
I have been beating my head against the wall, so to speak, for the last three hours or so and am getting nowhere. I first noticed it when I tried to use the SP2 slot on my OBi100 as an Asterisk trunk (similar to what I'd done with the OBi110, but I was going to try using it as a gateway to Google Voice) and it didn't work, and then I noticed that the OBi110 was having the same issue.
The problem is this: When you reboot the OBi, it will at first register normally with Asterisk. But then, between about 15 and 30 seconds later, it appears that it attempts to re-register on port 65535, which is a big no-no with Asterisk, apparently.
Just to make sure it wasn't something I was doing wrong I disabled SP2 entirely, and used the SIP Account Wizard for ITSP Configuration to set up the extension on SP1 (I have done this before and it worked great). When the device rebooted I watched it do this:
-- Registered SIP '234' at 192.168.0.33 port 5060
(... about 20 seconds later ...)
-- Registered SIP '234' at 192.168.0.33 port 65535
When this happens, I can still make outgoing calls from the connected phone, but any calls from another extension TO the phone don't go through. None of my other extensions do this and while I can't be 100% sure, I believe this problem developed overnight. I didn't make any changes (until this happened, and then I made serveral attempts to fix the problem, all of which proved fruitless). I did install the new firmware last night but tried going back to the previous version and that didn't help, so now I'm back at the new firmware again.
If I try to register the trunk on SP2 the exact same thing happens.
So at this point I can't use either of my OBi's with Asterisk, and I have no idea what caused this problem or even exactly when it started. If anyone has any thoughts on why this is happening I'd sure like to hear them.
Added comment: One other thing I have noticed is that even though I never changed the port setting on SP2 (that is to say, the ProxyServerPort in ITSP Profile B reamis set to port 5060), the initial connection (and until this latest problem, the only connection) to the Asterisk server occurred on port 5061. But if I tried actually changing the ProxyServerPort to 5061, it wouldn't connect to the server at all! So if I have both SP's enabled I see this:
-- Registered SIP '234' at 192.168.0.33 port 5060
-- Registered SIP '1112223333' at 192.168.0.33 port 5061
(... after 15 - 20 seconds, at exactly the same time ...)
-- Registered SIP '234' at 192.168.0.33 port 65535
-- Registered SIP '1112223333' at 192.168.0.33 port 65535
(Obviously the numbers have been changed)
Question: Does rolling back a firmware version undo EVERYTHING that the new firmware might have changed? Because seriously, the only thing that has changed in this entire setup is that I applied the new firmware last night, and then didn't really do any testing (I may have made one quick call to see if the phone rang but probably did that within the 15-second window after the device rebooted). But rolling back to the previous version didn't fix the issue, so now I'm just wondering if the new firmware changes something that going backwards won't undo.