using OBI100 for a 2nd handset

(1/2) > >>

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

Navigation

[0] Message Index

[#] Next page