SOLVED: Suddenly OBi's won't work with Asterisk — port registration issue
MichiganTelephone:
obiliving, I did reboot the Asterisk box earlier today and it didn't help. The only thing between me and it is a switch, and I power cycled that, and it didn't help.
When I set the registration time to a bit longer (like 300) it does delay the onset of the problem, but doesn't eliminate it. When I set it to 7200 it still doesn't eliminate the problem, but as you might expect it takes about a half hour or more for it to start.
One interesting thing I note with the OBi is VERY short qualify (ping) times reported by Asterisk, on the order of 3 ms, whereas all the other connected equipment on the local network is running at anywhere from 9 to 22 ms. I keep wondering if something's in a "race" condition and when you use it with a distant server the added turnaround time eliminates the problem - wish I had a way to test that theory.
I could send you (in email) a sip debug trace from Asterisk showing the problem occurring, but all I really see is that it suddenly changes ports, with no indication as to why that might happen. Then again, I'm not always entirely sure what I'm looking at. But one thing I do notice is that once the problem occurs, the OBi110 seems to get quite "chatty", sending many more packets than I would expect to see in a given period of time. It's as if someone turned on the spigot — you don't see a delay of more than three or four seconds tops between groups of packets coming from the device. Once it's rebooted it gets a lot "quieter" until the problem starts again.
I don't think you quite understood that I really don't have any way to run Wireshark here. As I understand it you have to be able to intercept the packet flow. I saw it used once once or twice (or maybe it was "Ethereal" or something like that) but didn't really understand what I was seeing and don't recall much about it, other than that I think a computer with two network cards was used in the process. It's not that I couldn't run the program itself (I'm pretty sure there's a Mac version) but I don't know how I'd intercept the packet flow, since my Mac Mini only has the one network connection. But if you have any suggestions as to how it might be accomplished, let me know.
OBiSupport:
Hi
Do you have any special setting in your sip.conf?
Pls check your "bindport", are you specifying it to some specific value ?
From your asterisk linux machine, you can also run
"netstat -an | grep <your_asterisk_ip_address>"
This command displays all the port that your PC currently is listening at.
Are you seeing lots of entries for udp, other than 5060 ?
What you said earlier about the registration used to be ok,
are you registering with a different peer userid now ?
If yes, do you have setting for "port" under that [userid] in sip.conf?
What is this unit's OBi number ?
For privacy, you can email this to support@obihai.com
Please register the unit to OBiTALK as your other Device.
PS: Do you have a softphone ? xlite perhaps ?
Does this softphone also behave the same way ? changing registration port ?
-Obihai Support Team
MichiganTelephone:
Just so you know, I run FreePBX so most of the configuration is handled by that.
There is a bindport = 5060 line in sip_general_custom.conf
Are you sure that netstat command is correct? When I run that I see only three UDP entries and none for port 5060, yet I know that port is used by other devices on the network. If I run it without the grep then the only reference I see to 5060 is this:
udp 0 0 0.0.0.0:5060 0.0.0.0:*
There are several other UDP ports listed when I run it without the grep.
With regard to the peer registration for the extension, the port is set in the FreePBX GUI and by default it is always 5060, though it can be changed - but it hasn't been for this extension.
I will send you more information in e-mail.
MichiganTelephone:
I THINK I'VE FOUND THE PROBLEM!!!
Though I do not have any idea why it wasn't a problem until today.
In the post from OBIsupport they suggested that I register the unit to OBiTALK as your other Device. I was reluctant to do that on my OBi110 but got to thinking that maybe I should try setting up another extension on my OBi100. And to make a long story short, it worked and did NOT have the problem.
So then I tried the using the exact same settings on the OBi110, except I did not change the extension, and still had the problem. So now I was getting really suspicious that something was different in my FreePBX configuration. Well, there was. On the extension that didn't work, I had nat set to never, which seems logical for an extension on the same LAN and which is the setting I've always used with Linksys/Sipura devices without any issue (again, only for devices on the same LAN). But when I set up the OBi100 extension I used one that I'd previously used with a softphone and it had nat set to yes, and that seems to be the difference!
So, apparently you have to use nat=yes for the OBi devices, even if they are on the same LAN! I'm still testing this theory but so far it seems to be working, however I'm still extremely puzzled as to why this problem didn't manifest until today, since I had used the nat=never right from the start.
MichiganTelephone:
It's still working, so I revised my article to show nat=yes instead of nat=never, so hopefully nobody else has to deal with this. Still really curious why it didn't seem to make a difference until today, but I'm just happy it works. A big THANK YOU to all who offered suggestions and advice, I really appreciate all the help!
Navigation
[0] Message Index
[#] Next page
[*] Previous page