OBi2xx or OBi10xx with a Backing-Off OBi1xx
PaulInDenver:
So no SP is necessary???
I'm sorry for my ignorance, but unless I configure an SP, OBItalk doesn't want to route calls using **9+OBI#(9digits). The 110 seems unreachable w/o an SP defined.
==>If there is a way to use OBItalk without assigning any SPs on the 110, can someone please tell me how to do that?
Target Configuration:
My goal config is to preserve the functionality on my 2 line phones where each line dials OUT on different GV instances, but both lines ring on incoming calls to either GV instance. I want to dedicate ph2 of the 202 to FAX, so my 2nd voice line needs to come from the 110. Finally, I have another PSTN to attach to the 110, for rare incoming calls, and it can ring on only one appearance.
OBI202: SP1 is GV1 --> rings ph1 + Obi110/ph
SP2 is GV2 --> rings ph1 + Obit110/ph
Fax (TBI) --> Fax rings ph2 dedicated fax line (can GV route fax calls?
Can I detect Incoming Fax on a GV line and direct it to ph2 (iff GV can route fax)?
Or do I need a different ITSP for fax?
ph1 uses SP1/GV1 for outgoing calls
ph2 (ded fax) uses a GV SP if possible for outgoing calls, else alternate ITSP
OBI110: Rings on incoming calls to either GV1 or GV2 (non-fax) --> Obi110/ph is my 2nd line on my 2 line phones
Outgoing calls (from line 2 of phones) via GV2
PSTN In --> OBI110/ph (Line2 of phones) (Outgoing calls to PSTN are rare, ringing only 1 line OK)
I hope the above makes sense.
Quote
You are not saying exactly what you want. I assume you want to route calls to PSTN from either OBi202 phone port. I also assume you want GV as your Primary route. You need to use a prefix to route calls to PSTN. I hate using the ** prefix and I use a single 9 prefix. You can route calls without a prefix if you can identify the PSTN numbers (7 digits to PSTN, 10 digits to GV and 11 to PSTN). You can also use area codes to identify PSTN numbers.
OBi110
Physical Interfaces -> Line Port -> InboundCallRoute: ph,pp(510111111)
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111:li}
Replace 510111111 with OBi number of the OBi200
<cut>
Azrobert, thanks for your CallRoute and DIgitMap work. I'd much appreciate your showing me the rules for my layout above.
Thank you to everyone for your help. and patience.
Paul
drgeoff:
Quote from: PaulInDenver on November 11, 2017, 03:47:49 pm
I'm sorry for my ignorance, but unless I configure an SP, OBItalk doesn't want to route calls using **9+OBI#(9digits). The 110 seems unreachable w/o an SP defined.
What exactly do you mean by "route" in that sentence?
With default settings any OBi can call any other OBi by dialling **9 followed by the 9 digit Obi number, provided both OBis have an internet connection that can reach Obihai's server(s). No SP configuration is necessary.
PaulInDenver:
When I attempt to dial **9 {9-digit OBI #} from a phone on the 202, it replies with a "Not found - 404" voice message for either of the OBI numbers on the 110.
Sounds like I should HW reset the 110?
PaulInDenver:
I did a reset and NOW OBItalk is working as expected on the 110.
I made a string of false inferences from the failure of OBItalk w/o an SP. I am sorry. Cross-eyed.
Now to tackle the DigitMaps, and InBound/OutBound Call Routing rules.
THanks, Paul
azrobert:
The OBi202 can't detect a fax call. You will have to define another GV account on SP3. PSTN inbound will default to OBi110 phone port.
OBi202
Physical Interfaces -> Phone1 Port -> PrimaryLine: SP1
Physical Interfaces -> Phone2 Port -> PrimaryLine: SP3
Voice Services -> SP1 Service -> X_InboundCallRoute: ph,pp(OBi110_OBi_Number)
Voice Services -> SP2 Service -> X_InboundCallRoute: ph,pp(OBi110_OBi_Number)
Voice Services -> SP3 Service -> X_InboundCallRoute: ph2
Voice Services -> OBiTalk Service -> InboundCallRoute:
{OBi110_OBi_Number:sp2},{ph}
OBi110
Physical Interfaces -> Phone Port -> OutboundCallRoute:
The 1st rule is: {([1-9]x?*(Mpli)):pp}
Change it to: {(<OBi202_OBi_Number*>(Msp1)):pp}
Don't skip the *
Navigation
[0] Message Index
[#] Next page
[*] Previous page