Direct IP call: connected but packets not received
Shale:
Just a few ideas ...
1. Change the (Voice Services)SPn Service->X_UserAgentPort ports for each SPn to not be the same port as used on the other end. This one may be that may be naive or ignorant, but it won't hurt.
2. Connect each OBi to its modem with no router in place. Try again. If success, look to router settings. If you are unable to do that, put each OBi into the DMZ for testing.
hwittenb:
Azrobert is right when he says the OBi has problems when using direct URI calling.
You are trying to call between two external ip addresses, correct?
I biggest problem I have seen is the OBi's inconsistency in determining whether to send an external or an internal ip address in the sip signalling.
I just tried a direct ip incoming test call to my OBi110 from IPKall which, of course, has an external ip address. It had no audio. The problem was the OBi's response (the sip 200 OK) to the incoming sip INVITE said the contact address was a local network ip address (i.e. 192.168.1.120). This was in spite of my setup using a STUN server and in spite of my setup with X_DiscoverExternalIPAddress checked. Direct ip calling has a problem when this happens.
An additional test with STUN disabled did not make any difference.
The problem was I had SP2 setup to not register. When I changed SP2 to register the OBi responded with its external ip address and the audio started up correctly. Of course if you say SP2 needs to Register, you need to register with some server. I had SP2 setup to register to a voip provider.
When I tried setting up the proxy as 127.0.0.1, with Register, and the Register fails, it doesn't work either, and it doesn't work with Register No. However when I tried setting my external ip address under X_PublicIPAddress in the ITSP profile, as Azrobert suggested, with the proxy as 127.0.0.1 and set not to Register, the incoming direct ip call works because the sip signalling used the external ip address.
Another problem you can encounter is that some routers, as part of their NAT scheme, will change port numbers when communicating with an external ip address. This will also cause problems if your router is doing this. Using a STUN server will usually detect and correct this problem. I would try using a STUN server as suggested. The OBi doesn't have all the flexible settings that RFord listed for his SPA, but they do the ones they think are necessary.
Toulousaing:
Thanks all! But I'll not be at home today, so I can't try anything before tomorrow.
But my main requirement was to avoid any 3rd party, whether STUN or SIP service. Indeed, in a second phase, device B will be located in environment B where the ISP blocks SIP ports and may be tempted to block IP/Ports of STUN servers as well. (Now I'm testing in an environment A where ISP is not blocking anything.)
If this is not possible, do you know another ATA which offers solid direct URI service and works well with dynamic DNS proxy (in the second phase, the device B will have dynamic IP)?
Now the "weak" point of environment B is that I'll be using dyn DNS services, they might try to block their IPs but there are plenty of them. Also I think dyn DNS uses TCP port 80 to send my public IP, so hopefully they won't block TCP port 80 ;)
azrobert:
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.
giqcass:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page