Direct IP calls
drgeoff:
Quote from: Hortoristic on November 18, 2013, 04:58:02 pm
What does directing your outgoing calls to the Asterisk server give you - are you actually calling the asterix server via GV or is the asterix server re-initiating the call using GV there? Does that work around the XMPP problem?
Quote from: drgeoff on November 18, 2013, 07:49:37 am
In a related manner I have a Voice Gateway on my OBi110 with AccessNumber set as SP2(192.168.1.75). That directs outgoing calls on that gateway to my local Asterisk PBX from whence it goes via GoogleVoice (Motif). Doesn't go anywhere near the ITSP that SP2 is registered to.
Only calls for USA numbers (I'm in the UK) from the OBi go to Asterisk. I had already used SP1 and SP2 for two other Service Providers which are more important to me and I wished them to have the lowest failure potential.
Doesn't offer an immediate solution to the XMPP problem. But perhaps Asterisk is more likely than the OBis to get an interface to Hangouts.
N2VWZ:
Quote from: Cobi on November 15, 2013, 07:44:13 am
Just wondering, is it possible to make direct IP calls with the Obi100, without using Obitalk?
I.e. An Obi100 to a Cisco/Linksys ATA, based on IP address (assuming port forwards and all were set up in the router?)
If so, how?
Thanks!
Direct IP Dialing works with the Obi devices, however, the firmware does not do any filtering by the phone number that you assign. Any number dialed to your IPaddress:Port will cause your phone to ring. The phone will ring every time a hacker does a port scan on your IPaddress.
This is a serious flaw that Obihai has chosen not to fix with their firmware.
A much better solution for Direct IP Dialing is to find an old Siprua SPA2000 or SPA3000 ATA on ebay. These devices filter by the phone number that you assign and you will not be bothered by random port scans.
Since there is no registration or logging associated with this type of Direct IP Dialing, it will be a bit more difficult for the Domestic Spy agencies to tap into telephone conversations and steal your meta data.
QBZappy:
@N2VWZ
Beg to differ. There are several ways to avoid the problem you mentioned using the OBi. Have a look here for details.
(Credit to Shale) Summary of various methods mentioned by various posters on this forum
HOWTO: Thwarting SIP Scanners during Set-up
http://www.obitalk.com/forum/index.php?topic=5467.0
The best method IMO is the oleg method because it is simple and easy to set up. I think one of the methods could be used with direct ip calls.
gderf:
My OBi is behind a NAT router. But no manually applied port forwards or firewall rules are required for it to work.
I see UDP scans to the SIP port (5060) on my public IP address frequently in my firewall logs, but these don't cause the phone to ring as that port is not open.
Perhaps your comment applies to OBi devices directly connected to the internet such that they have a public I address.
giqcass:
My example used a domain name but you could replace it with an IP address. I should have mentioned that. I used that example because it's a test number.
SP2(17770000001@in.callcentric.com) is correct if you aren't using a Callcentric account to make the call. I overlooked that because my example was a cut and paste from my device. SP2 happened to be Callcentric on my Obi so it works both ways for me.
I won't call the sip scanner vulnerability a flaw because it can be useful if you want multiple incoming sip uris and it's easily fixed. Like QBZappy I believe the Oleg method is best. It will allow multiple incoming sip uris and defeat the scanners. I think the flaw is that Obi does not document the process or make the consumer aware of it.
If the device you are dialing uses the standard 5060 to listen for sip there is no need to define the port in the dialing string.
Navigation
[0] Message Index
[#] Next page
[*] Previous page