OBiTALK Community

Hi,

I have several questions before I order a OBi202 ATA.

I created a OBiTalk account and on the "Approved Service Providers">For Home selection I see, "Free Calling from Your Home Phone with an OBi Device and Google Voice"

I get the impression that the "free calling" might only be to other users of the OBi devices because there is mention of using independent ISPs on the same page.

Or does it mean you can call -anyone- free in the USA using the OBi202 and Google Voice?

Can you directly dial your Google Voice phone number with the OBi202 via OBiTalk to make free Google Voice outbound calls to anyone and use the GV features?  Or does the OBi202 handle that?

Anveo for instance has a $39.99/yr "Free incoming calls" plan with 333 minutes/month (~11 minutes/day) free outbound calls and then charges by the minute. I've waited waaay over 11 minutes for AT&T sales to pick up a phone.  The time limit is not all that practical but if Google Voice is used to make calls then it's no problem.

Thanks for any info to clarify how OBiTalk works with the OBi202.

Oh for the return of the good old daze of Simon.

When it is working properly (which seems not the case for some people currently) you can call most US and Canada numbers at no charge by directly dialling the number on a phone plugged in to the OBi. As far as others are concerned calling you is no different from calling any other number.

OK, thank you for the quick answer.

So in affect I don't need a separate ISP to receive calls to my Google Voice number?

Just set the OBi202 up on OBiTalk using the Google Voice link and it's free In and Out calls?

If so that's as simple as it can get and I was just overthinking the whole process.  That comes from all the weird stuff I was seeing from various external ISPs with offers that weren't so great once you really dug down into the details.

"ISP" = Internet Service Provider; the company that supplies your building's internet service.

"ITSP" = Internet Telephone Service Provider; a company that supplies Voice over IP (VoIP) telephone service.

Google Voice is neither of those things.  It is a cloud-based telephone call forwarding and voicemail and text message management system.  It can make and receive calls using regular 10-digit US telephone numbers over the ordinary telephone network, and it can make and receive calls over VoIP, but that is not its sole function.  Many people think of it as a "free telephone company", but that's not its primary design.

Hi Steve,

Basically I just want to find out will the OBi202 using OBiTalk allow free In/Out calling with no extra ITSP that I have to setup (not counting my normal Internet provider).

I apologize for dragging this out but ....... just so I'm perfectly clear on this. All I have to do is set up the OBi202 thru Google Voice as OBiTalk describes and I can make free inbound and outbound calls through Google Voice?  If so I'm a happy camper and I'm off to get a OBi202.

At first I assumed that with the OBi202 I would have to get an ITSP account with someone else to use Google Voice to -receive- calls.

Ok on the terminology.  I have the same situation when using EE terminology with non engineers.   ;)

It isn't always that easy to convince a non technical person that "calling" and "talking" to someone on the phone or radio is NOT the same thing.   ;D

Since you are making a point of this, *I* am making this point:

Many people ignore explanations like mine, because they are foolishly lured by the come-on of to think that an OBi device + GV = free phone company.  It does not.  It cannot call E911.  It is not meant to be a standalone, bare-bones SIP ITSP.

Do you understand now?  Yes, Google Voice can make free calls to Canadian and other US phone numbers.  Yes, it can receive phone calls for free.  No, it is not a bare-bones ITSP.

Steve wrote:
It cannot call E911.  It is not meant to be a standalone, bare-bones SIP ITSP.

Do you understand now?  Yes, Google Voice can make free calls to Canadian and other US phone numbers.  Yes, it can receive phone calls for free.
------------------------------

I can call 911 on one of several no plan cell phones if necessary.  I carry one with me all the time.

I've been using Google Voice for 9+ years.  My concern was how the OBi202 + OBiTalk interacts with GV.

Yep, that was the clear answer(s) I was looking for.
Thank you.

Well, if you've been using Google Voice for 9+ years, then you already understand how it makes and receives "free calls".  OBiTALK devices are simply SIP clients that connect to your Google Voice account and behave as forwarding destinations, just like using Google Hangouts or a 10-digit PSTN telephone number.

I think you're all set now.

Quote from: olrowdy01 on July 23, 2018, 03:52:15 PMMy concern was how the OBi202 + OBiTalk interacts with GV.

I'm not convinced that you understand what "Obitalk" is and what it does.

Quote from: drgeoff on July 23, 2018, 03:56:20 PM

Quote from: olrowdy01 on July 23, 2018, 03:52:15 PMMy concern was how the OBi202 + OBiTalk interacts with GV.

I'm not convinced that you understand what "Obitalk" is and what it does.

Probably not.  I assumed OBiTalk was necessary to set the OBi202 up etc and with good luck it would then be the ATA somewhere in the background and allow me to use Google Voice as I have for many years.  I'm used to Google Voice being the portal to my telephone activities when I happen to get a message with my PAP2T just being a dumb ATA.

After reading the OBiTalk Administrator and Provisioning Guides and seeing that OBiTalk was necessary to load the OBi202 with all the settings etc (which I normally do manually) it seemed that OBiTalk could/would also be my main contact with controlling my telephone system rather than Google Voice.

Especially so when I saw the features of OBiExtras.  My first thought was "WHOA .... I don't need all that stuff!"  I just need a phone to call out maybe once/twice a MONTH and get nothing but sales calls which my answering machine gets rid of. (Just load the "disconnect tones" as the opening part of your greeting message.)   ;D

If there is a link to a more detailed description of what OBiTalk can do I'd be happy to read it.

"OBiTALK" has several meanings:

• It is the name of the company's remote device provisioning and management platform, along with the website portal it provides.
• It is now the name of the product line (as opposed to the legacy Polycom devices).
• It is the name of the domain hosting this forum, along with hosting the portal
• It is the name of the proprietary VoIP telephony network provided at no charge for use by OBiTALK device owners, to make calls from one device to another.

Where you might be confused, is that Google Voice requires that you use the OBiTALK portal to configure Google Voice service on a device.  It is not a plain-vanilla SIP ITSP.  It's best to use the portal, vs. the device's local webserver, for configuration, since the portal will overwrite any changes made to the local webpage UI.

"Where you might be confused, is that Google Voice requires that you use the OBiTALK portal to configure Google Voice service on a device."

I read that and I will of course let it do that while praying that Florida Flicker & Flash (Fla Power & Light) doesn't hiccup while updating the firmware.

I saw the illustration of how OBiTalk controls the 202 etc.

My main confusion point was the last one you presented.  It just isn't presented on the site as straight out as you put it.  That's where the webmaster needed a new customer to try to make heads or tails out of what is presented.

In our previous posts and on the website, making "Calls" to me only means I can call someone else.  That someone might have to -also- be using a OBi device for the call to be free.  Making "Calls" to me doesn't say a thing about -receiving- calls.  This is of course no fault of the forum gurus.

The description points you just gave in your post should be prominently shown on the website.  In affect I found hints of the points in my reading all over the site for several days. 

The last point would have saved me a -lot- of time in trying to figure out that I don't need to have an external SIP ITSP for the OBi device because I was used to having to search around to find one that would provide enough minutes of usage etc at a reasonable price because (as a friend used to say) "It's always been thus."

Another confusing thing is that in my Google Voice/legacy settings my PAP2T was listed as a "OBi Device".

Just today after the last few posts I finally figured out that the price of 202 was the one time charge to use it.   :-[

The OBiTalk webmaster etc probably didn't realize that newcomers won't realize that if they come from other ATAs that have to be setup manually with other companies settings etc.  Pay by the minute etc. (Thumbs down.)

So thanks again for the information.

Update:
The OBi202 arrived today. The hardest part of setting it up was moving things around for an hour so the 45" long wall wart cable could reach the place where the 202 was going to sit.

Getting it linked and working was easy compared to the 3" of power cable slack I ended up with.  And I can now make & receive calls again.

I do notice that there is a longer wait for the ringing tone to start when making a call.  I assume that OBiTalk gets involved in making & receiving calls.  With my PAP2T setup everything seemed to go directly through Google Voice even though the legacy settings showed that the Linksys was an "OBi device".

Is there someway to reduce the delay?

When I set up the PAP2T system I used a slightly different dialing plan from the default one & calls were made with no delay.  I looked into the setup of the OBi202 and don't see a setting that specifically says "Dial plan" to change.  (Which might get changed back to the default setting if OBiTalk doesn't like changes made.

With OBiTalk I had to turn the GV "attendant" off in the Google Voice legacy settings because it was talking the same time my normal answering machine gave it's message.  It used to be that I heard GV ring 5 times before it give it's message, so I set my answering machine to answer in two rings.  My test caller person said today that he heard 5 rings before the phone answered.  I heard my phone rang 2 times and it started to gave it's message. About 1/2 second later GV started giving it's message at the same time my answering machine was still talking.  My caller said he only heard the GV message to leave a voice message.

Strangely enough the tail end of the GV message that the "attendant" gave my caller was left on my answering machine. I got his voice message via gmail by going through the ritual of signing into GV, clicking around for awhile and finally hearing his message.

Has anyone else commented on dueling answering machines vs ring times?

The main thing is I have phone service again and we can hear each other etc.  The voice quality is excellent; same as my PAP2T.  Also the OBi202 case temperature is -much- cooler than the PAP2T.

Now I have to agree with DrGeoff, that you really do not understand Google Voice, and it's design, at all.

For the umpteenth time, it is not a bare bones ITSP.  It is not a basic SIP VoIP trunk provider.  It is a complete telephone call management, voicemail, and text messaging service.  It is intended that you use its voicemail, not your answering machine.  If this is more complex than you wish, and you wish it would work like your PAP2T did a decade ago, then get service from a bare-bones SIP ITSP.  Heck, Circlenet Sam would love to have your business at an extremely low cost.

And, comparing an OBi 20x to an ancient PAP2T in terms of sound quality or performance is ridiculous.  It would be like comparing a 1957 Chevy Impala to a 2018 Chevy Volt.  The PAP2T was a very basic device with a low-performance, simple microcontroller.  The OBi products are Linux computers, running on an ARM SOC.  All you were asking the PAP2T to do was the bare-bones registration and SIP VoIP stuff.  And of course the OBi is going to run cooler because again, the guts are about 15 years older in the PAP2T, compared to modern, low-power electronics.

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

Now I have to agree with DrGeoff, that you really do not understand Google Voice, and it's design, at all.

(My response to your comments will be in bold text.)

Thank you for that.
As long as it works the way I want it to I'm satisfied.  If I wanted to understand it's internal electrical design I would have bought two of them and reversed engineered one of them.

For the umpteenth time, it is not a bare bones ITSP.  It is not a basic SIP VoIP trunk provider.  It is a complete telephone call management, voicemail, and text messaging service.  It is intended that you use its voicemail, not your answering machine.
 
Steve, it is very difficult for the manufacture of various products to force people to use their product exactly the way the CEO, Engineering & Sales Departments thinks they should.

i.e. Again, I don't need all that stuff. I just need a phone that will receive and make calls. And I clearly stated that in the beginning of this thread.

Since I don't use a cell phone or tablet etc either; when I want to check if I had any calls I don't have to turn my computer on to see if sales people left me a "click" or a sales pitch. I just look at the number of messages on the answering machine (zero in most cases) and if necessary, push one button and I hear the message.  For the way I use a phone that simplifies things greatly.

If this is more complex than you wish, and you wish it would work like your PAP2T did a decade ago, then get service from a bare-bones SIP ITSP.  Heck, Circlenet Sam would love to have your business at an extremely low cost.

Yes it IS more complex than I wish.  And my phone system using OBiTalk, the OBi202 and my answering machine *IS* working like it did with the PAP2T.

Steve: don't take it so personally. It's not a failure of OBiTalk to allow me to use it the way I want to.

  And, comparing an OBi 20x to an ancient PAP2T in terms of sound quality or performance is ridiculous.
 
Does finding out that the sound quality of both units is the same really cause that much grief on this forum?  And it's not ridiculous if it -is- true in my case.
 
   It would be like comparing a 1957 Chevy Impala to a 2018 Chevy Volt.  The PAP2T was a very basic device with a low-performance, simple microcontroller.
   
My first car was a Model T Ford.  The car and I were both young at the time.  ;-)

As basic as the '57 Cheby, T and the PAP2T seem now, they all served their intended purposes.  And still can.

On the other hand, many people drive cars all their lives and don't have any idea how they work. Not everyone has to fully understand how electronics or mechanical things work to get them to do what they need them to do.
   
   The OBi products are Linux computers, running on an ARM SOC.  All you were asking the PAP2T to do was the bare-bones registration and SIP VoIP stuff.  And of course the OBi is going to run cooler because again, the guts are about 15 years older in the PAP2T, compared to modern, low-power electronics.
   
Please, I started designing electrical circuits most likely before you were born. It was just a casual observation and not meant to cause umbrage concerning the wonderfully modern (cooler running but with a short power cable) OBi202.

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

And I can return the favor if you need to know more about the internal workings of a Model T Ford.  Or my present 13 yr old Honda that can get almost twice the driving range of the Chevy Volt at 64 mph.  Even my 30 year old Honda CRX-HF got more mpg than the Volt.

And now, getting back to the OBi202:
I found a 3 year old forum post how the poster changed the ring delay of incoming calls, I'll try that.

Come on Steve, lighten up.

Is there a cliff note version of this thread?

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.   :-[

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.

QuoteI 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 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.

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.  :)

QuoteI 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.

QuoteCould you post which settings and where to change them please?

The last rule in the Phone DigitMap is (Mpli). This will include the primary line's DigitMap rules. The changes need to be made in the primary lines digit map. Assuming your primary line is SP1:

Service Providers -> ITSP Profile A General -> DigitMap
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.S3)

Or to add 7 digit dialing. Replace AAA with your local area code.
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1AAA>xxxxxxx|011xx.S3)

The catch all "xx." has been removed, so you will need to add additional rules if the above doesn't meet your requirements.

Quote from: olrowdy01 on July 28, 2018, 08:34:16 PM
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. Thank you for the information you've given me (and "us" for later readers) so far.

That setting is only applicable when using a POTS line with the OBi. Unless you have an OBiLINE plugged in to your OBi202 you don't have a LINE port.

The setting is to give the OBi time to get the incoming Caller ID. In the US Caller ID is sent between the first and second ring. In the UK it is sent before the first ring, hence the setting can be much shorter.

With VoIP, Caller ID arrives as part of the SIP signalling so none of the above applies.

Quote from: azrobert on July 28, 2018, 10:56:22 PM

QuoteCould you post which settings and where to change them please?

[/size]

The last rule in the Phone DigitMap is (Mpli). This will include the primary line's DigitMap rules. The changes need to be made in the primary lines digit map. Assuming your primary line is SP1:

Service Providers -> ITSP Profile A General -> DigitMap
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.S3)

I changed the setting as you instructed above.  When I first got to Profile A I noticed the box to enable it wasn't set.  The other Profiles did have the boxes enabled.  I inputted the dialing info and clicked the enable box.  I don't remember the exact wording but the next msg was to reset or reboot the OBi.  I unplugged the power cord, waited ~15 seconds and plugged it back in.

Should I have NOT pulled the plug to cause the 202 take the new dial plan and used some star code instead?

When I looked at Profile A again to make sure it was enabled ... it was NOT.  So I enabled it and again rebooted(?) the 202 and that time the enabled stayed. All the other Profiles had the new dial plan and were enabled too.

On making a call to a Sunday closed business I heard NO ring sound after pressing the 10th digit on the phone keypad. After the usual 5 second delay the store answering machine started so the phone is working & I hung up.

I tried to go back into the OBi202 setup screen and the 202 refused to open with the following browser message:

"The connection has timed out
The server at 192.168.1.76 is taking too long to respond etc etc."

After not being able to get into the 202 I went through the reset procedure of deleting the 202 from my account dashboard and then re-added it etc.

Now when I make a call it takes the usual 5 seconds for the ringing to start so the 202 did go back to the initial settings.
* but *
I still can NOT get into the 202 setup screen using the same ***1 code response address [now] that the 202 used when I first started using it

Now what to do to fix that? 

Try another remove the 202 and set it up again?  Maybe use the bottom button to reset it several times with the LAN cable disconnected after OBiTalk has reset it?

[Edit]I just realized that I DID NOT do step 2 of the instructions to use the bottom reset button!  I used some old instructions I found on the forum said to use a star code. 

That hopefully is why I can't get into the 202 right now.  I'll post the results of after I do another delete 202 etc etc.  Sorry 'bout that.

2nd edit ..... Finished using reset on bottom of 202 to reset it. I still hear no ringing after 5 seconds and I still can't log into the OBi202 device.  :-(
Any advice will be most welcome. [/Edit]

I must say it's not that intuitive to know when some of these resets etc are finished.

Got OBi202 to open the setup page.

Perhaps the following details will help other people with a similar problem if they come across this post later.

After I did the OBi202 factory reset with the OBi202 push button my Internet browser couldn't link with the 202 because the OBi202 factory reset caused the RG  (as AT&T calls the gateway) to issue a new IP to the OBi202.  I had assumed the OBi202 IP address was static and being set by the 202.

I found out what happened by using ***1 and then going into the RG (that's what AT&T calls the gateway) to look at the addresses of the attached network devices.  I found two entries for the OBi202 with different IPs.

I got them to coexist by rebooting both the RG & 202 by un-pluging the power plugs to the RG and the 202.  Then I plugged the RG in first and let it boot.  I then plugged in the 202 and after it booted the two devices are now talking to each other again so I can get into the setup of the 202. 

I still don't have any ring sounds for 5 seconds after pressing the last digit when I place a call.  So back to fixing that.

You appear to be making configuration changes using the 202's onboard web server.  Unless you have disabled Obitalk Provisioning the changes will sooner or later (in the case of rebooting, immediately) by the settings on the portal.  I recommend you use Expert mode on the portal to make all changes.  Note that you need to clear both tick boxes at the right hand side of a line before it will become editable.

Quote from: drgeoff on July 30, 2018, 02:29:05 AM
You appear to be making configuration changes using the 202's onboard web server.  Unless you have disabled Obitalk Provisioning the changes will sooner or later (in the case of rebooting, immediately) by the settings on the portal. 

When I first got the OBi202 I made screen shots of every page of the device setups.  At that time I noticed that the Provisioning was set to either 'Disabled' or 'Periodically' with no enable tick mark.  And it is now set to Periodically & disabled after the factory reset. 

Seems to me that it ought to be enabled but then making any changes is futile in the long run.  I would guess that a re-provisioning is similar to a firmware update and wouldn't happen too often.  If it was only once a year I could just put the new dial plan back in afterwards.  i.e. Once I/we find one that works.

I haven't changed anything other than trying azrobot's dial plan for 10 digits to the A Profile hoping it would speed up the start of dialing.  Before I made his change I was hearing dialing rings.

The OBiTalk test call 222 etc answers immediately when dialed and works OK.

I recommend you use Expert mode on the portal to make all changes.  Note that you need to clear both tick boxes at the right hand side of a line before it will become editable.

OK, I'll certainly do that.

I also notice that the ITSP Profile A > General > DigitMap  does not have the enable box tick mark after the reset.  All the other Profiles do have the tick mark.  azrobot said to modify the A profile which I did and ticked the enable box to make it active.  After I did that all the Profiles had the new dial setting and were enabled.

Should I just set the A Profile to not enabled and when I put the new dial plan in Profile A?  I realize that it gets propagated to all the others from the A Profile.

Is it proper to disconnect only the 12v power for 15-20 seconds to cause the 202 to reboot?

I haven't looked up the star code for that yet.  I had the impression you could reset and clear only some things.  Not knowing what those things do I decided to just pull the power plug.

Thanks again for everyone's help, it is certainly appreciated.

I haven't had the time to search a lot on the forum to see if there is a sticky with some of my questions already answered.  I'll do that later today.  I'm still getting used to how this forum works for posting etc.  It's quite different from several of the others I'm on (giving advice, not taking up people's time with questions that have probably been answered over and over again).

When you:

change settings using the onboard web server you click submit at the bottom of the page.  There will then be a "Reboot" button in the top right corner.  Haven't you noticed that?

change settings using the portal you click submit and your OBi will reboot automatically shortly thereafter.

Quote from: drgeoff on July 30, 2018, 08:18:03 AM
When you:

change settings using the onboard web server you click submit at the bottom of the page.  There will then be a "Reboot" button in the top right corner.  Haven't you noticed that?

change settings using the portal you click submit and your OBi will reboot automatically shortly thereafter.

Yes I did that.  Otherwise nothing was going to happen.

But not knowing the sequence of the 202 LED flashing while rebooting I didn't know what or when it actually finished re-booting.  So after about 7 minutes I unplugged it to make sure.  And the change was made.

Next time I'll go do something else for awhile while it does the magic.    ;D

The reboot itself completes in well under a minute.  It starts immediately (unless a call is in progress) when you click the reboot button on the onboard GUI.  Takes a variable bit longer to start the reboot when using the portal.

No need to power cycle in either case.

Quote from: azrobert on July 28, 2018, 10:56:22 PM

The last rule in the Phone DigitMap is (Mpli). This will include the primary line's DigitMap rules. The changes need to be made in the primary lines digit map. Assuming your primary line is SP1:

Service Providers -> ITSP Profile A General -> DigitMap
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.S3)

I only inputted the above plan in the ITSP Profile A area.  Do I also have to make the dial plan change in the "Physical Interfaces/PHONE1 Port"?  Or does it get changed to match the Profile A change?  I didn't check that when I made the first attempt to shorten the dial ringing.

I think my OBi202 is possessed.
I'm sure that last night I didn't hear any dial rings after the reset when I called a local inactive phone number.  When I just tried it again I did hear ringing!  The AT&T voice message "person" answered the phone after a few rings.

Then I placed a call to a live phone, the person I called obviously heard ringing (which I didn't hear) and picked up the phone sooner than the inactive phone number.

Perhaps the 202 is starting the call but ringing doesn't start in my phone for awhile after the dialing has started.  I don't call with extensions added to the phone number or 4 or 7 digit numbers etc etc.

I just need a shorter 10 digit 'S' time somewhere in the 202 to start the ringing and stop checking everywhere else.