Question about OBiTalk and Google Voice
GPz1100:
Is there a cliff note version of this thread?
olrowdy01:
Steve wrote:
I'll let someone else give you a tutorial on digit maps, which are roughly comparable in purpose, but not in syntax, to PAP dial plans
------------------------
That would be most helpful.
Right now I'm making screen shots of all the default settings. When I'm done I'll probably find where I could have downloaded them all with one click. :-[
azrobert:
The DigitMap's control the delay of outbound calls. The default configuration will produce a 2 second delay for 10 and 11 digit N. American numbers and a 10 second delay for other numbers. There are DigitMap rules ending with "x." and "@." that will match any number of digits that cause the 10 second delay. If you eliminate these rules, you can get the delay down to zero.
There is nothing I know in the configuration that will cause a delay on inbound calls. I just made a test call to my GV number and my phone started ringing about 1 second after hearing the ringback on my handset. If you continue getting this delay, you can try deleting the OBi202 from OBiTalk and then repeat the setup process.
Your OBi202/GV will work perfectly with your answering machine when you fix this inbound delay problem.
Quote
I found a 3 year old forum post how the poster changed the ring delay of incoming calls, I'll try that.
If the poster fixed the delay problem, I'm curious what he did.
azrobert:
This is how an OBi works:
With the exception of the Phone Port (PP), the DigitMaps do NOTHING on their own.
After a number is dialed the (PP) DigitMap gets control.
The PP DigitMap validates the dialed number.
You have the option of modifying the dialed number, like add/removing a prefix.
If you modify the dialed number, it is actually changed at this point.
The last rule (Mpli) points to the Primary Lines's (PL) DigitMap.
So if the PL is SP1, the ITSP A DigitMap's rules are included with the PP DigitMap.
If the number is validated by the PP DigitMap, it is passed the PP OutboundCallRoute.
If the number doesn't match a rule, you will get a Busy tone.
OutboundCallRoute Processing:
Rule {(Mpli):pli} routes un-prefixed (without **n) numbers to a trunk.
(Mpli) points to the PL DigitMap and pli points to the PL.
If the PL is SP1 and the dialed number matches a rule in the ITSP A DigitMap the call is routed to SP1.
The PP DigitMap also determines the delay before a call is routed to the outbound trunk.
The DigitMap analyses the number as it's being dialed.
If dialed number matches a DigitMap rule and it can't match any other rule there is no delay.
If dialed number matches a DigitMap rule, but it can potentially match another rule there is a 2 second delay.
If there are rules xxxxxxxxxx and xxxxxxx
If you dial 7 digits it matches xxxxxxx and can potentially match xxxxxxxxxx
The OBi doesn't know if you will dial any more digits, so it waits 2 seconds.
If dialed number only matches a DigitMap rule like "xx.", there is a 10 second delay.
x matches a single digit and x. matches zero or more digits.
xx. will match 1 or more digits.
Since this rule is open ended, the OBi waits 10 seconds.
You can override the delay by coding the rule like this: xx.S3 to produce a 3 second delay.
The following delays exclude any numbers defined in the Phone DigitMap.
Default ITSP DigitMap
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Will produce 2 second delay for 10-11 digit numbers and 10 seconds for all other numbers.
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.S3)
Zero delay for 10-11 and 3 second delay for international. All other numbers will fail.
Add 7 digit dialing. Replace AAA with your local area code.
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1AAA>xxxxxxx|011xx.S3)
Zero delay for 10-11, 2 second delay for 7 digits and 3 second delay for international. All other numbers will fail.
olrowdy01:
Quote from: azrobert on July 28, 2018, 01:42:51 pm
The DigitMap's control the delay of outbound calls. The default configuration will produce a 2 second delay for 10 and 11 digit N. American numbers and a 10 second delay for other numbers.
Right now I haven't changed anything in my 202 settings but I'm not hearing a 2 or a 10 second delay for the ringing to start. For some reason my default delay is 5 seconds to start dialing for a normal 10 digit phone number after I press the last digit. It seemed longer in earlier posts but this time I timed it with a stop watch.
The delay is annoying while I wonder if I hit all 10 of the digits. Two seconds would be great.
There are DigitMap rules ending with "x." and "@." that will match any number of digits that cause the 10 second delay. If you eliminate these rules, you can get the delay down to zero.
Could you post which settings and where to change them please?
Here is what the "Phone Port" values are set to now: (Perhaps these aren't the settings you are referring to?)
([1-9]x?*(Mpli)|
[1-9]S9|1-9]0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
OutboundCallRoute has this:
{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<#:>):ph2},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
and CallReturnDigitMaps has this:
{pli:(xx.)},{sp1:(<**1>xx.)},{sp2:(<**2>xx.)},{sp3:(<**3>xx.)},{sp4:(<**4>xx.)},{bt:(<**8>xx.)},{bt2:(<**82>xx.)},{pp:(<**9>xx.)}
There is nothing I know in the configuration that will cause a delay on inbound calls. I just made a test call to my GV number and my phone started ringing about 1 second after hearing the ringback on my handset.
I believe that was when my out of town tester and I did our first tests when the Google Voice attendant and my answering machine were talking over each other. I did another test tonight after I disabled the Google Voice answering message and my answering machine did answer on the 2nd ring that I heard. My tester said he only heard 1 ring and my machine recorded his message ok. At this point as long as it works this way I'll leave it alone.
If you continue getting this delay, you can try deleting the OBi202 from OBiTalk and then repeat the setup process.
Your OBi202/GV will work perfectly with your answering machine when you fix this inbound delay problem.
Yes, now it is. :)
Quote
I found a 3 year old forum post how the poster changed the ring delay of incoming calls, I'll try that.
If the poster fixed the delay problem, I'm curious what he did.
This is from a 7/10/2015 post by a UK user about the delay he was having when setting up his OBi202 for his carrier.
"Try this: To prevent delays in inbound ringing Set Physical Interfaces ~ Line Port ~ Ring Delay to 400."
I looked in my OBi202 settings and the terminology must have been changed since I don't see a "Ring Delay" box to change. His explanation was so long I didn't look to see what else was in the thread since my dog insisted he really-really needed to go outside. :)
Thank you for the information you've given me (and "us" for later readers) so far.
Navigation
[0] Message Index
[#] Next page
[*] Previous page