News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Google Voice CallForwardUnconditional

Started by dialtone, March 16, 2011, 03:54:08 AM

Previous topic - Next topic

dialtone

I am setting up another OBi110.
SP1 is connected to a Google Voice account, number 123-456-7890
SP2 is registered to a Generic SIP account, number 4567

With these SP1 settings in place:
CallForwardUnconditionalEnable (x)
CallForwardUnconditionalNumber SP2(9876)
All inbound calls to the Google Voice number 123-456-7890 make the SIP 9876 number phone ring.
I answer the call, it works. Great.
I undo this SP1 CallForward, Submit and Reboot the OBi110.

With these SP2 settings in place:
CallForwardUnconditionalEnable (x)
CallForwardUnconditionalNumber SP1(8005551234)
I assume that calling the SIP number 4567 would make the call forward to Google Voice and dial 8005551234
Not so.
I just get a busy tone.
I tried some variations:
8005551234
8005551234#
18005551234
18005551234#
None of these work.

What am I doing wrong?



RonR

Quote from: dialtone on March 16, 2011, 03:54:08 AM
With these SP2 settings in place:
CallForwardUnconditionalEnable (x)
CallForwardUnconditionalNumber SP1(8005551234)
I assume that calling the SIP number 4567 would make the call forward to Google Voice and dial 8005551234
Not so.
I just get a busy tone.
1. Without SP2 call forwarding settings in place, does calling SIP number 4567 from a phone other than the one connected to the OBi's PHONE Port ring the phone connected to OBi's PHONE Port and is everything normal in this case?

2. With SP2 call forwarding settings in place and you're getting a busy tone, are you calling SIP number 4567 from a phone other than the one connected to the OBi's PHONE Port?

dialtone



Quote from: dialtone on March 16, 2011, 03:54:08 AM
With these SP2 settings in place:
CallForwardUnconditionalEnable (x)
CallForwardUnconditionalNumber SP1(8005551234)
I assume that calling the SIP number 4567 would make the call forward to Google Voice and dial 8005551234
Not so.
I just get a busy tone.

Quote from: RonR on March 16, 2011, 12:01:52 PM
1. Without SP2 call forwarding settings in place, does calling SIP number 4567 from a phone other than the one connected to the OBi's PHONE Port ring the phone connected to OBi's PHONE Port and is everything normal in this case?
Yes, that is correct.
Before I did ANY of the above call forwarding...
I asked a friend to call the Google Voice 123-456-7890 and it did ring the phone connected to the OBi' PHONE port. I answered and it works.
Then I asked the person at the SIP number 3421 to dial 4567 and it did ring the phone connected to the OBi' PHONE port. I answered and it works.

Quote from: RonR on March 16, 2011, 12:01:52 PM
2. With SP2 call forwarding settings in place and you're getting a busy tone, are you calling SIP number 4567 from a phone other than the one connected to the OBi's PHONE Port?
Yes, that is correct.
I asked the person at the SIP number 3421 to dial 4567 and it gives a busy tone.
In fact we called 4567 several times from 3421, 3422 and 3423 and we still get a busy tone.

dialtone

An update:

OBi SP1 is connected to a Google Voice account, number 123-456-7890
OBi SP2 is registered to a Generic SIP account, number 4567

10 minutes ago, I removed all call forwarding ...
Calling the Google Voice number from any outside landline or mobile phone rings the Phone connected to the OBi's PHONE Port. Answered it. It works.
Calling the SIP number 4567 from any other number on that SIP server rings the Phone connected to the OBi's PHONE Port. Answered it. It works.

5 minutes ago , I added this call forwarding ...
SP1 -> CallForwardUnconditionalNumber SP2(9876)
SP2 -> CallForwardUnconditionalNumber SP2(9878)

So both SP1 and SP2 are forwarding to different endpoints on the same SIP server ...
Calling the Google Voice number from any outside landline or mobile phone rings the SIP number 9876. Answered it. It works.
Calling the SIP number 4567 from any other number on that SIP server rings the SIP number 9878. Answered it. It works.

So calls forwarded using the SIP server work from SP1 and SP2.
But calls forwarded using Google Voice do not work at all.

So I assume that the syntax SP2(9876) and SP2(9878) is correct, as it applies to SIP.

Is this SP1(8005551234) syntax correct, as it applies to Google Voice on SP1 ?
Of course 8005551234 is just an example.
I have tried many other numbers besides 8005551234, it just does not work.



RonR

I think you've found a bona fide bug.

I have GV on SP1/ITSPA and I just put my Sipgate account on SP2/ITSPB.

With no forwarding, calls to my Sipgate number ring the OBi phone, as expected.

Enabling CallForwardUnconditional via SP1 (using either SP1(...) or **1...), the forwarding fails.

I tried the same forwarding from OBiTALK to SP1 and was better able to see the problem.  It appears the outgoing call is actually being placed through SP1, but GV responds "You don't have sufficient credit to place this call."  This would seem to indicate the OBi is not sending the correct number when the new call is placed through GV.

RonR

Quote from: dialtone on March 16, 2011, 02:55:46 PMIs this SP1(8005551234) syntax correct, as it applies to Google Voice on SP1 ?
I think GV would prefer a leading '1', but if I recall correctly, it's also happy without it.  I was testing with a leading '1'.

I think the general rule in the OBi is that numbers in TK format [SP1(18005551212)] are sent to the port directly with no alteration, whereas in PHONE Port format [**118005551212] they're run through the normal DigitMap's and OutboundCallRoute's.  At least that's the way it's stated for Speed Dials.

dialtone

Ron, Thanks for these details.
From all our findings mentioned above, I knew the following would not work but I was curious so ...
I tried SP1(1234567890) and SP1(11234567890) because 123-456-7890 is the associated Google Voice number.
That would normally take you to your Google Voice menu ... To check for new messages, To place a call, etc.
No luck. Busy tone.

Quote from: RonR on March 16, 2011, 03:10:23 PM
I tried the same forwarding from OBiTALK to SP1 and was better able to see the problem.  It appears the outgoing call is actually being placed through SP1, but GV responds "You don't have sufficient credit to place this call."  This would seem to indicate the OBi is not sending the correct number when the new call is placed through GV.

Since it is not clear which or how many of these digits are being sent to GV ...
Is there any way to introduce a Delay in this syntax?
To slow down the number dialing, instead of just shooting it out.

Just like the "w" in D(wwww ...) in the Asterisk Dial() command.
That way a delay could be introduced before and/or during the number like so:
SP1(www1234567890)
or
SP1(www1w2w3w4w5w6w7w8w9w0)
etc.

RonR

Quote from: dialtone on March 16, 2011, 04:39:07 PMSince it is not clear which or how many of these digits are being sent to GV ...
Is there any way to introduce a Delay in this syntax?
To slow down the number dialing, instead of just shooting it out.
The digit's aren't 'pulsed' out to GV as you dial them.  Once the OBi collects and processes what's supposed to go to GV, a packet of information is sent across the Internet containing all the necessary pieces at the same time.  It's not 'dribbled' out in real time.  Consequently, you'd need to 'packet sniff' what's being sent and analyze what is seen.  This is a much better project for Obihai as I'm sure they already have this capability in place and they'll know what should be there instead of what is actually there.

RonR

dialtone,

A correction to my earlier post.  There is not a problem with OBiTALK -> GV forwarding.  I had to have someone help me test that path and I just discovered he was forgetting to dial **9 in front of my OBiTALK number.  It was his GV that was reporting "You don't have sufficient credit to place this call", not mine.  I just ran the tests again to be sure and here's how forwarding stands:

Working:

OBiTALK -> GV
LINE -> GV
GV -> GV


Failing:

SIP -> GV


obi-support2

Below suggestion is posted on another thread....

---------
Please try this setting:
Assume your SP1 is using ITSP Profile A, and SP2 is using ITSP Profile B,
set X_Use302ToCallForward to no (unchecked) under that ITSP Profile for SP2.
The default value is yes (checked).

Please let us know if this resolves your problem. Thanks.

--------
If this works, it implies a bug in the current f/w that should automatically turn
off this option when call forward between two different trunk types.
We will look into a fix for it.
OBIHAI Support Staff

RonR

I'll reconfigure SP2/ITSPB for VoIP again in a little while, test X_Use302ToCallForward, and let you know.

RonR

obi-support2,

I think this may have already been reported in another thread, but I was also able to confirm that having X_Use302ToCallForward checked prevents call forwarding from VoIP to Google Voice.  Unchecking this option allows it to work properly.

dialtone

obi-support2,

Thank you.
Yes, I can confirm this too.
X_Use302ToCallForward unchecked does make it work.

We are almost there ...

dialtone

There is still one related issue.

Given these settings:
SP1 is connected to a Google Voice account, number 123-456-7890
SP2 is registered to a Generic SIP account, number 4567
SP2 => CallForwardUnconditionalNumber SP1(8005551234)

From the SIP number 3421, I dialed 4567.
It does indeed ring 800-555-1234 via Google voice.
It was answered, had a conversation ... great!

So I changed the forwarded number to my own Google Voice number 123-456-7890.
SP2 => CallForwardUnconditionalNumber SP1(1234567890)

Yes, it rings. The Google Voice attendant answers.
"To check for new messages press 1, To place a call press 2, etc."
I hit every key on my phone and it did not recognize any key.

I assume that DTMF is not passing through because ...
*  From that SIP number 3421 (same phone), I dialed 7654.
*  Where 7654 is a Grandstream ATA with its FXO port connected to basic AT&T landline.
*  I get to the AT&T landline dial tone.
*  I dial my Google Voice line.
*  I check my new messages.
*  I place a call.



RonR

dialtone,

I haven't experienced any problems with DTMF through Google Voice myself, but according to OBi-Guru, you may need to enable the following on your Google Voice Port:

Service Providers -> ITSPx -> General -> X_UseFixedDurationRFC2833DTMF

dialtone

Good tip Ron,

That helped.
I was not the X_UseFixedDurationRFC2833DTMF setting.
But I noticed that just above that was DTMFMethod = Auto
Good enough.

The SIP number 4567 (being forwarded) had its dtmfmode=inband

The SIP number 3421 (originating the call) has dtmfmode=rfc2833

In other words, rfc2833 TO inband TO Auto
Yuk!

So I changed dtmfmode=auto for SIP number 4567
That would make it rfc2833 TO auto TO Auto

Now it works all the way.

Thanks RonR, obi-support2 and murzik.