News:

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

Main Menu

Installing a 110+100+202

Started by HAS-MS, January 09, 2017, 04:51:45 PM

Previous topic - Next topic

HAS-MS

Already running  100 and 110.
Steve or Azrobert........
Saw a thread somewhere here as to having
all work and making and receiving calls.
each has a different GV on SP1,SP2.
But will the 110 and 110 have the issue of last to
register to ring when the 202 is online?
All will be on the same lan, if that makes any difference.

Thanks. 

SteveInWA

Are you saying that you have six different Google Voice numbers, two on each OBi, or what, exactly?

The OBi 110/100 models will only ring if they are the last device to register.  If the 202 is using the same GV accounts, then that'll create a mess on the other two OBis.

The 202 can host up to four GV accounts in SP1--SP4.  Can you just get rid of the 1x0 OBis and use the 202 instead?

azrobert

If the 100 and 110 have the same GV acct defined the last to register will receive the call. You can solve this problem by forking the call both directions using the OBiTalk network. The 100 will send the call to the phone port and the 110 and the 110 will do the same in the other direction. Now doesn't matter which OBi receives the call, both will ring. The 202 will always receive the call, so you only have to fork the call in one direction.

Define the SPx X_InboundCallRoute:
ph,pp(123456789)

Replace 123456789 with the OBi number of the OBi you want to send the call.
Make sure there isn't any code in the receiving OBi's OBiTalk InboundCallRoute that will block the call or send the call to the Auto Attendant.

HAS-MS

#3
Lord, I write poorly for an engineer don't I!
The 100 and 110 have 4 different GV numbers.
2 GV numbers per device.
So the 202 will have the 4 different GV accounts
in the 4SP's.
Hoping that all will work simultaneously with the 202.
Thanks again.

SteveInWA

Heh heh, that is why companies hire tech writers to explain what the engineers built.

So, you can either ditch the 1x0 boxes, and just use the 202, or you can do what Robert suggested.

HAS-MS

#5
Yeah, I know. I design and often build but writing it up
ain't my strong suit!
So they won't play nicely together?
If the 202 will always get the call, will the
100 or 110 ring also with the call?

The 110 can access 911 via an "abandoned" POTS line.
When you discontinue pots service here, they must maintain
dial tone and 911 access.

SteveInWA

What is your end goal?

Can you live with four GV accounts and two physical telephone lines?  If so, use the 202 and retire the other OBis.  If you can't, then use the 202 and one or both of the others.

Why do you need four different GV numbers?

RE:  911, if you get rid of the 110, then either keep a phone plugged into the POTS line, or use your cell phone.  Personally, I wouldn't rely on a decommissioned POTS line.  You won't know if it somehow got accidentally  disconnected until you pick up the phone and it's dead.  If you DO use it, it won't provide your location, because it won't have a telephone number, unless your telco has worked out some sort of substitute procedure.

azrobert

#7
Assuming you have all four GV accounts defined on the OBi202, fork inbound calls to OBi110 and OBi100.

OBi202
Voice Services -> SP1/SP2/SP3/SP4 Service -> X_InboundCallRoute:
ph,ph2,pp(200110110),pp(200100100)

OBi110/OBi100
Voice Services -> OBiTalk Service -> InboundCallRoute: ph

You can route 911 from the OBi202 to the OBi110 and out the Line port.

OBi202
Physical Interfaces -> Phone1/2 Port -> OutboundCallRoute
The first rule is: {([1-9]x?*(Mpli)):pp}
Change it to {(<200110110*>911):pp}

OBi110
Voice Services -> OBiTalk Service -> InboundCallRoute: {>911:li},{ph}

Replace 200110110 with the OBi110's OBi number
Replace 200100100 with the OBi100's OBi number

Use OBi Expert to make the above changes.

To test 911 without actually making an emergency call, disconnect the OBi110 line port from Telco and plug it into the OBi110 phone port. Now dial 911 on the OBi202. The call should be routed from the OBi202 over the OBiTalk network to the OBi110. Then the OBi110 will route the call out Line to the OBi100 where the call will fail. You can verify this happened by checking the Call History on the OBi202 and the OBi110.

To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column then click Call History.

HAS-MS

Quote from: SteveInWA on January 09, 2017, 08:32:00 PM
What is your end goal?
Was hoping to have 2 standalone systems running.
Can you live with four GV accounts and two physical telephone lines?  If so, use the 202 and retire the other OBis.  If you can't, then use the 202 and one or both of the others.
I sort of do that now with the 100 and 110...
Why do you need four different GV numbers?
Can you say grandchildren?
RE:  911, if you get rid of the 110, then either keep a phone plugged into the POTS line, or use your cell phone.{ I do an old 2500 rotary} Personally, I wouldn't rely on a decommissioned POTS line.  You won't know if it somehow got accidentally  disconnected until you pick up the phone and it's dead.  If you DO use it, it won't provide your location, because it won't have a telephone number, unless your telco has worked out some sort of substitute procedure.
I have DSL, live rurally, and the old home number stays with the account as the ID.
So if i have carrier I have dial tone, unless the Dslam goes down, then still have tone for dialup  backup and 911. And the 911 info stays with the line assignment.

HAS-MS

#9
Quote from: azrobert on January 09, 2017, 09:21:32 PM
Assuming you have all four GV accounts defined on the OBi202, fork inbound calls to OBi110 and OBi100.

OBi202
Voice Services -> SP1/SP2/SP3/SP4 Service -> X_InboundCallRoute:
ph,ph2,pp(200110110),pp(200100100)

OBi110/OBi100
Voice Services -> OBiTalk Service -> InboundCallRoute: ph

You can route 911 from the OBi202 to the OBi110 and out the Line port.

OBi202
Physical Interfaces -> Phone1/2 Port -> OutboundCallRoute
The first rule is: {([1-9]x?*(Mpli)):pp}
Change it to {(<200110110*>911):pp}

OBi110
Voice Services -> OBiTalk Service -> InboundCallRoute: {>911:li},{ph}

Replace 200110110 with the OBi110's OBi number
Replace 200100100 with the OBi100's OBi number

Use OBi Expert to make the above changes.

To test 911 without actually making an emergency call, disconnect the OBi110 line port from Telco and plug it into the OBi110 phone port. Now dial 911 on the OBi202. The call should be routed from the OBi202 over the OBiTalk network to the OBi110. Then the OBi110 will route the call out Line to the OBi100 where the call will fail. You can verify this happened by checking the Call History on the OBi202 and the OBi110.

To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column then click Call History.

Very simple and elegant, I've had these online for 5 years now and
just got the 202 when it was on sale as a backup plan due to the EOL
for the 100 series.
Have done my own configurations by following you and Steve's wonderful
help to many others. I lurk on a bunch of boards. I learned 60 years ago
to shut up and listen. Learn a lot more that way.
Thanks for the tips, I shall start playing with the systems later today.   

DarioFincher

Quote from: SteveInWA on January 09, 2017, 07:51:56 PM
Heh heh, that is why companies hire tech writers to explain what the engineers built.

So, you can either ditch the 1x0 boxes, and just use the 202, or you can do what Robert suggested.
Technical writer is a very popular profession nowadays. Many companies need tech writers to write about their products and how to use them.

Technical writer at assignment writing help, Dario A. Fincher