HELP! IPkall + Localphone weird issues
mo832:
I appreciate everyone's input so far. My primary concern at this point is to get localphone to actually WORK on the Obi with 2-way audio. If localphone won't even make a good phone call, there's no point in buying their DID no matter how cheap, and no point in paying anyone anything until I know the dry-run tests are successful. I'm worried that I cannot use localphone as my provider if I can't get it to work. But I have believe there is something I can fix. Too many people have this working.
The secondary issue is the Ipkall caller id (if in fact this is the cause). But again, I'm looking to test before I start paying good money that is going to be burned up for nothing.
jazzy:
I'm also fowarding my GV > IPKALL # and OBi pickups up the calls. But CID is not working. I get
the infamous 206-682-0185 on all incoming calls. But the incoming calls do get picked up by Obi
and there is decent 2 way audio. And it is free incoming calls. So I just have to live with no CID.
As for my outgoing calls, I too have been testing Localphone, for outgoing calls. I've setup Localphone
as a Voice Gateway, since it's just for outgoing calls. It works fine, and quality is good.
You can test out your Localphone for outgoing calls by setting up Obi like this:
Voice Services > Gateways and Trunk Groups >
Voice Gateway2
Enable (checked)
Name Localphone
AccessNumber sp2(localphone.com)
DigitMap (1800xxxxxxx|1888xxxxxxx|1877xxxxxxx|1866xxxxxxx|)
this will only route 1800 calls to Localphone ( 800 calls are free on Localphone )
if you want to route all calls to Localphone, leave DigitMap blank
AuthUserID 8xxxxx
AuthPassword yourpassword
Physical Interfaces > Phone Port
OutboundCallRoute
{(Mvg2):vg2} must place this to the far left of the Outbound call route ( ie..first entry )
that should allow you to test Localphone outgoing calls to 800 numbers.
mo832:
1. So is it pretty certain that it's the IPkall DID that is corrupting the caller id? In other words, if you forward GV to another DID issued by another source, and then to a SIP provider including localphone or anyone else, it still passes the caller id info thru all those steps?
2. HOW CAN I FIX MY OBI AUDIO for localphone? Nothing else can move forward until I clear up this problem. I already can register the Obi with localphone's server, and the OBi can ring with the DID number, but once connected, the calls are not usable. One way audio only. Fixing the audio is the goal.
[Again, my hunch is it has something to do with my Uverse gateway, since I've read that others have had issues. Still, other phone providers work fine with my current setup]
jazzy:
Quote from: mo832 on February 25, 2014, 11:09:57 am
#
1. So is it pretty certain that it's the IPkall DID that is corrupting the caller id? In other words, if you forward GV to another DID issued by another source, and then to a SIP provider including localphone or anyone else, it still passes the caller id info thru all those steps?
When I call my IPKALL # directly, the CID passes correctly. It must be GV that is messing up the CID
by using that generic 206-682-0185 CID. Been reading that it's because the IPKALL # has been used so many times with a GV fwd number, that GV is banning the IPKall #. When I forwarded my GV > Obivoice #, the CID passed correctly. It has something to do with the free DIDs.
Try setting up Localphone as a Voice Gateway and see if you have the same issues with audio. Just be sure that when you fill out the Access Number sp2(localphone.com) under Voice Gateways and Trunk Groups to be certain your SP2 is set up as a SIP, not GV
mo832:
The problem with that is I don't have any calling credit on Localphone in order to place an outgoing call. Even so, it would not be a long term solution if I cannot take incoming.
I still need more details on how to set up STUN. That sounds promising...
Navigation
[0] Message Index
[#] Next page
[*] Previous page