Direct IP call: connected but packets not received
Toulousaing:
Quote from: azrobert on May 26, 2013, 08:59:45 am
I successfully called my OBi110 with softphone Phonerlite using DYNDNS.
The OBi110 and Phonerlite were on the same LAN, but this should work with two LANs.
I have a Grandstream HT386 ATA. This thing is so old it's not supported anymore.
I got the HT386 to call my OBi110 with the same setup as Phonerlite.
I hope this info will help. At minimum you should be able to do some testing with Phonerlite to see if the ISP will block your call.
I love my two OBi's but as I said in my previous post:
The OBi SUCKS big time when it comes to direct URI calling.
Ok it'd be really a pity because OBi is great and distance-manageable, I don't want to use an outdated ATA unless I really have to. Something close to what OBi offers would be nice (distance-manageable + very configurable).
Concerning the tests, I already have an available OBi110 with auto attendant on the other end, so shouldn't be a problem even if there is no physical person who can answer.
Now my problem is at phase 1: get a working configuration without that annoying ISP
And then I'll go to phase 2: get a working configuration with that ISP (who is blocking IPs/Ports).
Finally, about dynamic DNS, it's not the biggest issue as I can have a computer running on same LAN with dyndns running on it.
Toulousaing:
Quote from: giqcass on May 26, 2013, 09:28:10 am
Did you port forward 5061? I like afraid.org for dyn dns.
This is why.
Quote
This hack will let your OBi update Dynamic DNS. It isn't perfect but it works very well. It's as simple as calling a url to update the DNS at afraid.org. I believe it would be a simple task to add this feature to the OBi firmware directly. So please add this OBiHai. Pretty please. Until then here you go.
Set up a Dynamic DNS host at http://freedns.afraid.org/
Go to the Dynamic DNS tab.
Copy the "direct" update url link.
Open your Obi admin page.
Click the System management page.
Click Auto Provisioning.
Under "ITSP Provisioning" Change the following.
Method = Periodically
Interval = This setting must be greater then 400 so not to over use resources. I use 3667.
ConfigURL = Paste the update link you got from afraid.org
Press Submit at the bottom of the page. Restart you OBi.
Thanks a lot giqcass, your solution sounds very interesting, I'm eager to test it.
However, I'm now still stuck at phase 1.
And yes I forwarded port 5061, otherwise two devices wouldn't be connected (already experienced ;)).
QBZappy:
Quote from: Toulousaing on May 26, 2013, 11:21:17 am
I already have an available OBi110 with auto attendant on the other end,
I may have missed something, but why don't you just call using the OBiTALK service. You mentioned that you don't want to use any 3rd party services, you may not have realized that the OBiTALK service (3rd party) is already involved. Use it to call the other obi.
azrobert:
Quote from: giqcass on May 26, 2013, 09:28:10 am
I like afraid.org for dyn dns.
giqcass,
afraid.org works perfectly!
I was thinking about getting another dynamic DNS service.
Free DYNDNS accounts are now required to log in once a month to stay active. I'm keeping my DYNDNS account until I get tired of signing in.
Currently my router updates my DYNDNS account and my afraid.org account is updated by my OBi110.
Thanks for the info.
Toulousaing:
Quote from: QBZappy on May 26, 2013, 02:44:20 pm
Quote from: Toulousaing on May 26, 2013, 11:21:17 am
I already have an available OBi110 with auto attendant on the other end,
I may have missed something, but why don't you just call using the OBiTALK service. You mentioned that you don't want to use any 3rd party services, you may not have realized that the OBiTALK service (3rd party) is already involved. Use it to call the other obi.
Is OBiTALK already involved in my direct IP call?
As far as I know, answer is no. Could you please explain how OBiTALK is involved?
Why do I need direct IP call?
This would be my backup line if my ISP blocks the OBiTALK service. And this is easy as OBiTALK seems to use always the same IP (54.241.xxx.x) + port (10500) when establishing connection between the 2 ends.
Navigation
[0] Message Index
[#] Next page
[*] Previous page