DISA, Call Relay, Remote Access
azrobert:
You can have a problem like this when you have a mismatched codec on the inbound and outbound call. The inbound call is assigned a codec and then the outbound call is assigned a different codec. If you are using Vitelity for both the inbound and outbound calls, I don't think you will have this problem. If you want to check the codecs anyway, do the following:
Log into OBi Expert
Click Status
Call into the AA
Click Call Status
This should show the 2 codecs (TX and RX) for the inbound call
Now start the outbound call
Repeat clicking Call Status until the codecs for the outbound call are displayed
All the codecs should be the same
If the call ends before the outbound codec is displayed, just make an outbound call from the phone port using the 2nd Vitelity line and click Call Status. This should assign the same codec as an outbound call from the AA.
This does work when you use a different outbound provider. Correct?
eightminobi:
Wow, I realize how little I really understand about the OBi box...
I followed your steps and saw the call status. It reported on Terminal 1:
Audio Codec tx=G711U; rx=G711U
I then tried to make the outbound call by using option 2. As soon as the target phone picked up, the call disconnected. I was unable to obtain the codec from the new call. So I placed a call from the second Vitelity line and saw this on Terminal 2:
Audio Codec tx=G711U; rx=G711U
What's interesting is that I mistakenly pressed option 3 (call back) at one point, then I decided to do the following: I called my AA from my cell phone, used Option 3, specified my cell phone number, and hung up. When the OBi called back, I used option 2 to place a new call and then used **3 to specify that the new call should be made using SP3's caller ID. I then specified the destination number, and everything worked!
When things do not work, what I am doing is this: I called my AA from my cell phone, used Option 2, used **3 to specify that the new call should be made using SP3's caller ID. I then specify the same destination number I used in the working example from the previous paragraph, and the call disconnects as soon as the destination number answers. There is no lag or anything--the callee answers and the line instantly drops.
azrobert:
The codecs look good. The only other suggestion I have is to make sure you're at the current firmware level.
You can make the callback function easier by having the OBi call you back without entering your number.
Change the inbound route to:
{(1?8005551212):aa($1)}
$1 is a variable containing the inbound callerid.
You can also hard code the number:
{(1?8005551212):aa(18005551212)}
Now call the OBi.
Let it ring once and hang up.
The OBi will call you back.
If you let it ring until the AA answers, it will work as previously.
azrobert:
Is GV your AA primary line?
What happens if you setup GV to route the call to the AA and then call the GV number with your mobile?
eightminobi:
Yes, Google Voice (GV) is my SP1 device. I didn't mention it because I am calling a DID that is serviced by Vitelity on SP2 and I'm making an outbound call using the AA on SP3 (also serviced by a second account with Vitelity). I must admit that I don't understand why GV on SP1 would affect the "make a new call" feature but clearly you are onto something....
I think what you are asking me to do is to have GV forward to my AA when it sees the caller iD of my cell phone. I will try that and will get back to you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page