Google Voice Call Arbitrary Provider for Callback
If I dial with 10 digits without the 1, it uses your line that handles 7 digits because it sees the 1st digit as [2-9]
If my {ac} = 212, then if I dial 909-390-0003, the actual number dialed becomes 1-212-909-3900. Maybe it has to do with order of preference but I'm happy with dialing the xtra 1.
Synchron
If my {ac} = 212, then if I dial 909-390-0003, the actual number dialed becomes 1-212-909-3900. Maybe it has to do with order of preference but I'm happy with dialing the xtra 1.
Synchron
I don't think so. Most certainly it's because there's no '$' (end-of-string mark) in the pattern:Maybe it has to do with order of preference ...
when /^([2-9]\d{6})/
You can also check how I do it in Flexible table-controlled dialplan, optimized for US, GV, here is a part of code dealing with 7/10/11-digit numbers:
Code: Select all
case @num
when /^[2-9]\d{6,6}$/ # Local call, 7-digit number
@num = "1#{Area}#{@num}" # prefix it with country and area code
when /^[01]?([2-9]\d{9,9})/ # US number with or without "1" country code
@num = '1' + $1 # add country code and truncate number to 10-digit
when /^\*/ # Voxalot voicemail, echotest & other special numbers
else
sys.Respond(603,'Wrong number, check & dial again')
end
My dialplan was intended for USA dialing. The only way to get to the 7 digit line by dialing 10 or more digits is to begin your 10 digit portion with a 0 or 1, or begin your 7 digit portion with a 0 or 1, which would not match because they are not legit USA numbers. The 7 digit line would have processed your 10/11 digit number only if the 7 digit portion began with a 0 or 1.synchron wrote:If I dial with 10 digits without the 1, it uses your line that handles 7 digits because it sees the 1st digit as [2-9]
In any case, I'm changing my dialplan to accept those erroneous entries in exchange for allowing it to ignore any junk characters appended to the end of a phone number, which my WiFi phone is known to do. That's why I didn't put an end-of-string limiter on any regexp.
Revised dialplan:
Code: Select all
when /^[1]?(\d{10})/ then sys.GoogleVoiceCall(GV_email,GV_pwd,SIPnum,"1#{$1}",GV_nbr) # 10 or 11 digits
...
when /^(\d{7})/ then sys.GoogleVoiceCall(GV_email,GV_pwd,SIPnum,"1#{ac}#{$1}",GV_nbr) # 7 digits
That could only have happened if you entered 2129093900003 into your dialpad. That is not a legit USA phone number but it would have been handled by the 10 digit processing line by chopping off the last 3 digits. The original dialplan worked as it was supposed to.If my {ac} = 212, then if I dial 909-390-0003, the actual number dialed becomes 1-212-909-3900. Maybe it has to do with order of preference but I'm happy with dialing the xtra 1.
Those who don't have my problem with junk appends could easily prevent erroneous misdials by appending the end-of-string limiters to the regexps as follows:
when /^[1]?([2-9]\d{2}[2-9]\d{6})$/
and
when /^([2-9]\d{6})$/
Good news! Google Voice now allows users with locked DIDs to select a "Reclaim this number" option to allow those DIDs to be unlocked. I tried it today and was allowed to confirm.mel2000 wrote:My Sipgate problem is that I cannot forward my GV# to Sipgate because GV shows that my Sipgate number is already in use by another GV customer (who probably never unforwarded their unused Sipgate number from GV). Therefore people dialing my GV# cannot get to my Sipgate phone unless they dial my 415 Sipgate number, which I do not want to use. I've already emailed GV about that issue and am hoping for a reply. I'm not the only Sipgate user with that problem.
Conference call
Is it possible to do a conference call using Sipsorcery & GV? If so how? Did try the regular way (flash, call the second party & again flash) but could not establish the conference.