HELP! IPkall + Localphone weird issues
OneForTheTeam:
Not sure if Obi110 supports it. But you can try putting the Obi in the router mode directly behind the modem but before any firewall to rule out any port forwarding issues and STUN issues.
mo832:
Regarding port 5060, I mentioned that because I read somewhere that the Uverse gateway device doesn't like 5060 (but again no issues with CC as the sp), but I don't know if this is the issue with Localphone
http://forums.att.com/t5/Features-and-How-To/Using-Third-party-VOIP-service-with-ATT-Uverse-internet-Call/td-p/3426287#.Uw1Pa670LdM
So in the Obi SP setup for Localphone, should I put in proxy.localphone.com or just localphone.com? I still haven't heard from LP support on this, but the proxy one is the only one I could get to register, though it doesn't fully work. What is everyone else using for the localphone settings? The wizard automatically puts in port 5060.
The Uverse gateway has a built-in modem/router combo, so I don't know any way to bypass the firewall.
jazzy:
Quote from: mo832 on February 25, 2014, 04:14:18 pm
If I want to test the voice gateway, what do I need to do, and do I again need to remove GV from the SP slot? Can you have Localphone on a gateway even if you have the sp set to another provider? What is the likelihood 2way voice will work on a gateway even though it fails on sp?
I just made a test call with Localphone to United Airlines 1-800-241-6522 and the voice system and keypad responses
registered fine. BTW I don't have any credit on my Localphone account, and when I check history online, it shows the call to UAL as $0.00 cost 2 minutes.
See if you can setup Localphone as a Voice Gateway. Use the same SP that you have Callcentric on.
If it is on SP2, then set up VG like this
Voice Services >Voice Gateways and Trunk Groups
Enable (checked)
Name Localphone
Access Number sp2(localphone.com)
DigitMap (1800xxxxxxx|1888xxxxxxx|1877xxxxxxx|1866xxxxxxx|)
AuthUserID your localphone ID
AuthPassword your password
and under Physical Interfaces > Phone port
put this in the OutboundCallRoute
{(Mvg2):vg2} be sure it is the first rule (all the way to the left)
Now when you dial any 800,888,877 or 866 number it will route through VG2 using Localphone.
giqcass:
Quote from: OneForTheTeam on February 25, 2014, 06:09:45 pm
Not sure if Obi110 supports it. But you can try putting the Obi in the router mode directly behind the modem but before any firewall to rule out any port forwarding issues and STUN issues.
He has a 100 NOT a 110 and no his Obi does not support it. That feature is exclusive to the 202 and I believe the brand new 508.
Putting Localphone as a gateway will not help the situation for incoming calls.
No need for proxy,sip, or www just register the Obi directly to the following.
localphone.com
If you think the port is the problem then try 5063.
On the Obi
Voice services
>>>>>>>>>>>>>SP1 Service
>>>>>>>>>>>>>>>>>>>>>> X_UserAgentPort = 5063
This number is completely free to call from localphone. It is an echo test so you can make sure you have good 2 way audio on outbound calls.
883 5100 0000 0091
mo832:
Quote from: giqcass on February 26, 2014, 12:03:12 am
No need for proxy,sip, or www just register the Obi directly to the following.
localphone.com
If you think the port is the problem then try 5063.
On the Obi
Voice services
>>>>>>>>>>>>>SP1 Service
>>>>>>>>>>>>>>>>>>>>>> X_UserAgentPort = 5063
Just to reiterate, in the past when I put in localphone.com, it failed to register. Using proxy.localphone.com and 5060 appears to "register", but is not fully functional. I have not yet tried the proposed suggestions (stun and port forward), so the preceding is simply what I've noticed so far.
Thoughts?
p.s. Let me also repeat that localphone works just fine on a softphone with no special changes, although the softphone does do STUN. Also the softphone uses 5070, but that wouldn't work when I tried it with Obi.
Navigation
[0] Message Index
[#] Next page
[*] Previous page