News:

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

Main Menu

using OBI100 for a 2nd handset

Started by bill-cary, September 16, 2019, 10:03:56 AM

Previous topic - Next topic

bill-cary

I have an OBI200 with 4 lines configured.
I would like to use my old OBI100 for a second handset so that I can answer and make calls on it when the OBI200 handset is in use.
Basically, make the 2 of them into an OBI202.

Both are on the same network.
How can I configure that?
thanks

azrobert

The following example uses the OBiTalk network to route calls between the 2 devices. **1 numbers will be routed to SP1. **2 numbers routed to SP2. All other numbers including 911 will be routed to SP3. Inbound calls on SP1-3 will ring both devices. I did it this way because the OBi100 is only configured for **1 and **2 and this example required the least amount of code.  I see by a previous post you have a basic understand of coding, so if you want more functionality you should be able to figure it out.

OBi100

Voice Services -> OBiTalk Service -> InboundCallRoute: ph

Physical Interfaces -> Phone Port -> OutboundCallRoute:
{***:aa2},{(<500111111*>@@.):pp}

Replace 500111111 with the OBi Number of the OBi200
To send data over OBiTalk the format is OBi_number * data
The above will prepend the OBi200 OBi number and an * to the dialed number and then send it to OBiTalk

OBi200

Voice Services -> SP1 Service -> InboundCallRoute: ph,pp(200222222)

Voice Services -> SP2 Service -> InboundCallRoute: ph,pp(200222222)

Voice Services -> SP3 Service -> InboundCallRoute: ph,pp(200222222)

Voice Services -> OBiTalk Service -> InboundCallRoute:
{>(<**1:>xx.):sp1},{>(<**2:>xx.):sp2},{sp3}

Replace 200222222 with the OBi number of the OBi100

bill-cary

#2
Of course, it would be THE MAN who answered me. Thank you azrobert

Yes, I have a BASIC understanding. The problem is I only do it for my system so infrequently that it is hard to remember.

Let me see if I understand this
OBi100

Voice Services -> OBiTalk Service -> InboundCallRoute: ph
...... anything coming into the 100 from pp goes to the phone

Physical Interfaces -> Phone Port -> OutboundCallRoute:
{***:aa2},{(<500111111*>@@.):pp}
........anything going out gets 200 address prepended to it and sent to obitalk network (pp).

what does {***:aa2} do?

Why use @@. instead of xx.?


OBi200

Voice Services -> SP1 Service -> InboundCallRoute: ph,pp(200222222)

Voice Services -> SP2 Service -> InboundCallRoute: ph,pp(200222222)

Voice Services -> SP3 Service -> InboundCallRoute: ph,pp(200222222)

these all send incoming calls to the phone or to the obitalk network(obi100 address)
I guess I should put one in for sp4 also.....right???


Voice Services -> OBiTalk Service -> InboundCallRoute:
{>(<**1:>xx.):sp1},{>(<**2:>xx.):sp2},{sp3}

I assume here that the 200 receives **1 + the dialed number from the 100 so that is sent to sp1
what does the > do?

similarly for sp2

why is {sp3} needed?
should I also put {sp4} on it?


Your config works when I dial **1xxxxxxxxxx from the OBI100 handset
but not for **2xxxxxxxxxx  ==> "we could not complete your call, please try again."

I have not tried when OBI200 handset is in use.

thanks again

drgeoff

azrobert gave you an example.  Yes if you want the OBi100 to be able to use all four of the services you have on the 200 you need to add its SP4 into the mix.

I think azrobert assumed that any OBi100 settings he did not mention were at the default values.  If they are not, that could be a reason why **2 is giving the " We could not complete your call message". (From GV?)

The {***:aa2) bit is just the usual part of a Phone port OutboundCallRoute which lets one access the various config options by entering codes from the handset.

azrobert

#4
@@. will match "**1", xx. won't.

The syntax for the rule is:
{ obi_number > number : dest}
The > is a separator
I didn't include the obi100's obi number, so the rule will match any obi number.
You can add the obi number for more security.

The default config allows ONLY "**1", "**2" and no prefix.
I'm routing no prefix to sp3.
There is a rule **1(Msp1) in the phone digit map
Change it to **[1-4](Msp1)
This will add **3 and **4
Again, the last rule in the inbound route is the default for no prefix.

Simultaneous calls on the same trunk will work, but a 3rd inbound call will fail.
To fix this increase the MaxSessions on all spx services to 3 or 4.
Do the same on both box's obitalk service.

bill-cary

@azrobert
thanks = I figured that is what @@. represented, just wanted to verify

I reset the OBI100, by deleting the device and re-adding it.
I reconfigured it and ALMOST everything works

If I use a **1, **2, **3, or **4 the 100 dials out on the associated sp of the 200
If I dial without an **x it goes out on sp1 of the 200.

I have this for the 200 Voice Services -> OBiTalk Service -> InboundCallRoute:

{300111111>(<**1:>xx.):sp1},{300111111>(<**2:>xx.):sp2},{300111111>(<**3:>xx.):sp3},{sp4}

If I use this it is the same
{>(<**1:>xx.):sp1},{>(<**2:>xx.):sp2},{>(<**3:>xx.):sp3},{sp4}
or if I swap the 2 and 4, still the same.

the phone digimap for the 200 is
*0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

and for the 100 is
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))

so I did not change anything there.

what am i missing?

azrobert

I don't understand either. I also don't understand how **3 and **4 work. I'm assuming you want no prefix routed to sp4. Try the following:

Voice Services -> OBiTalk Service -> InboundCallRoute:
{300111111>(xx.):sp4},{300111111>(<**1:>xx.):sp1},{300111111>(<**2:>xx.):sp2},{300111111>(<**3:>xx.):sp3},{300111111>(<**4:>xx.):sp4}

Phone digit map for the 100:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)| **3(Msp1)|**4(Msp1)|**9(Mpp)|(Mpli))

There isn't an SP3 or SP4, so I pointed **3 and **4 at (Msp1)

If it still doesn't work, post call histories from both devices for a failed call.

bill-cary

#7
It is all in the programming!!! not sure how I got what I did b4 - I guess I just confused OBI.
That got it - I just pointed all to sp1 on the 100 and added **4 to cover all cases of dialing out.


In case anyone else is watching, this is what I ended up with.......

The goal was to have my OBI100 function as an extra handset ala an OBI202.
I can dial from the OBI100 handset via any number on the OBI200 whether it is busy or not.
I select the line using **1, **2, **3, **4, or no **x defaults to sp4.
I can answer a call on the OBI100 (the OBI100 handset also rings) whether that line is busy or not on the OBI200


The 200 is programmed with all 4 lines.
I reset the 100 by deleting and re-adding in OBITALK dashboard
I changed the following items only


OBi100

Voice Services -> OBiTalk Service -> InboundCallRoute: ph

Physical Interfaces -> Phone Port -> Digimap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp1)|**3(Msp1)|**4(Msp1)|**9(Mpp)|(Mpli))

Physical Interfaces -> Phone Port -> OutboundCallRoute:
{***:aa2},{(<500111111*>@@.):pp}

Replace 500111111 with the OBi Number of the OBi200



OBi200

Voice Services -> SP1 Service -> InboundCallRoute: ph,pp(300111111)
Voice Services -> SP2 Service -> InboundCallRoute: ph,pp(300111111)
Voice Services -> SP3 Service -> InboundCallRoute: ph,pp(300111111)
Voice Services -> SP4 Service -> InboundCallRoute: ph,pp(300111111)

Voice Services -> OBiTalk Service -> InboundCallRoute:
{300111111>(<**1:>xx.):sp1},{300111111>(<**2:>xx.):sp2},{300111111>(<**3:>xx.):sp3},{300111111>(<**4:>xx.):sp4},{sp4}

Replace 300111111 with the OBi number of the OBi100

thanks to azrobert and drgeoff


azrobert

If you want to add the OBi number for no prefix, this is the syntax:
{300111111:sp4}