Access OBiBT service from another OBi on the network

(1/3) > >>

Xyspade:
Here's the scenario:
I have a network closet with an OBi202 that is connected to my router and home phone wiring.I have an OBi200 in the bedroom near where my cell phone typically resides when I'm home, with the OBiBT adapter paired to the phone.
I want to be able to make and receive cell phone calls, via the cell phone paired to the OBi200, from any phone in the house attached to the OBi202.  It would work just as if the OBiBT USB adapter was attached to the OBi202.  Since the bedroom is a good distance from the network closet, I'm expecting this solution to help improve range issues.  Possible, and how?

I know the setup isn't the greatest, perhaps this could just be a proof of concept.

Thanks for any insight.  (edit: Apologies for the spam, I got an error instead of a post confirmed message, didn't realize it posted anyway)

azrobert:
Quote from: Xyspade on April 07, 2020, 04:10:26 pm

I have an OBi200 in the bedroom near where my cell phone typically resides when I'm home, with the OBiBT adapter paired to the phone.

Since the bedroom is a good distance from the network closet, I'm expecting this solution to help improve range issues.  


Is the OBi200 connected to your network?

What range issue? Do you mean plugging the OBiBT into the OBi202 you have problems pairing to your phone?

You can route outbound from the OBi202 over the OBiTalk network to the OBi200/BT and the reverse for inbound.

Xyspade:
Yes.

OBiBT's range, in my experience, isn't very good.  It usually seems to pair okay, but I find the phone needs to be, at the very least, in the same room as the OBiBT adapter to avoid breakup, and even then it isn't perfect.  And I have a Galaxy Note9, it isn't some obscure thing.

What would the formatting syntax look like?  Feel free to point me somewhere else if an example is already posted.

azrobert:
OBi devices by default are setup to route outbound numbers to another device via OBiTalk network, however the receiving device isn't setup to route the call to a provider. I added a rule to the OBi200 to route the call to BT. The format of the number is "1*1xxxxxxxxxx". The leading "1" is normally the speed dial number where the destination OBi number is defined. I changed this and hard coded the OBi number in outbound call route rule. I also added code to route inbound to both OBi212 phone ports.

OBi202
Physical Interfaces -> Phone1-2 Port -> DigitMap
The 1st rule is: ([1-9]x?*(Mpli)
Change it to: (1*xx.S3)

Physical Interfaces -> Phone1-2 Port -> OutboundCallRoute:
The 1st rule is: {([1-9]x?*(Mpli)):pp}
Change it to: {(<1:510222222>*(xx.)):pp}

Voice Services -> OBiTalk Service -> InboundCallRoute:
ph,ph2

OBi200
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111>(xx.):bt},{ph}

Voice Services -> OBiBlueTooth 1 -> InboundCallRoute:
ph,pp(510111111)


Replace 510111111 with OBi number of the OBi202
Replace 510222222 with OBi number of the OBi200

Dial 1*18005551212 from the OBi212 and 18005551212 will be routed to BT

Xyspade:
"The number you have dialed was rejected by the service provider, reason: 404"
^ When dialing 1*1xxx-xxx-xxxx from OBi202 after following those instructions

You provided instructions for OBi212—I have OBi202, assuming that was a typo?

Admittedly most of that went over my head, I just blindly entered that code into the boxes (I know, probably your favorite average user stereotype to have to deal with for free).  Someday I'll have time to read and understand the documentation.  You don't have to help further unless you want to, the solution seems to be a bit more complex than I was hoping for anyway.  I appreciate your time.

Navigation

[0] Message Index

[#] Next page