two obis, two gv number, but dialing between boxes

(1/2) > >>

tome:
I have two obi110s. One at my full time residence, one at a cabin.  Both have a GV number as primary, and Callcentric on SP2 for e911 only.   If I dial from one to the other it will go out to GV and back in from GV to the other Obi.  How can I intercept the specific 10 or 11 digit number and send it directly rather then using GV, or can I?
Tom

RonR:
If you're simply wanting to call from one OBi to another OBi, all you need to do is dial : **9 200123456

where 200123456 is the OBiTALK number of the other OBi.

If you're really wanting to intercept a specific outgoing PSTN number and reroute it via OBiTALK to another OBi, add the following rule:

Service Providers -> ITSP Profile X -> General -> DigitMap : ...|<12341234567:**9200123456>|...

where 12341234567 is the number you want to intercept and 200123456 is the OBiTALK number of the OBi you want to divert it to.

tome:
Quote from: RonR on September 28, 2011, 09:48:51 pm

If you're simply wanting to call from one OBi to another OBi, all you need to do is dial : **9 200123456

where 200123456 is the OBiTALK number of the other OBi.

If you're really wanting to intercept a specific outgoing PSTN number and reroute it via OBiTALK to another OBi, add the following rule:

Service Providers -> ITSP Profile X -> General -> DigitMap : ...|<12341234567:**9200123456>|...

where 12341234567 is the number you want to intercept and 200123456 is the OBiTALK number of the OBi you want to divert it to.



Thanks RonR,

I don't want my family (kids mainly) to have to remember to dial **9Obi#, but they know the pstn number.   I also don't want them to have to deal with the AA.  So, on the other end, do I need to intercept the incoming call and route it to the phone port?

Tom

RonR:
tome,

The receiving end is:

Voice Services -> OBiTALK Service -> InboundCallRoute : ph

The default value is simply ph which routes all incoming OBiTALK calls to the PHONE Port.

If you have single-stage dialing or other specialized logic in place that involves trusted callers, you may have a rule that routes trusted callers to the Auto Attendant if the incoming call does not contain a destination number to be called:

Voice Services -> OBiTALK Service -> InboundCallRoute : ...,{(Mcot):aa},{ph}

To bypass the Auto Attendant in this case for a particular calling OBi, you would need to add a rule immediately preceding:

Voice Services -> OBiTALK Service -> InboundCallRoute : ...,{200123456:ph},{(Mcot):aa},{ph}

tome:
Quote from: RonR on September 29, 2011, 10:50:58 am

tome,

The receiving end is:

Voice Services -> OBiTALK Service -> InboundCallRoute : ph

The default value is simply ph which routes all incoming OBiTALK calls to the PHONE Port.

If you have single-stage dialing or other specialized logic in place that involves trusted callers, you may have a rule that routes trusted callers to the Auto Attendant if the incoming call does not contain a destination number to be called:

Voice Services -> OBiTALK Service -> InboundCallRoute : ...,{(Mcot):aa},{ph}

To bypass the Auto Attendant in this case for a particular calling OBi, you would need to add a rule immediately preceding:

Voice Services -> OBiTALK Service -> InboundCallRoute : ...,{200123456:ph},{(Mcot):aa},{ph}



Great, thanks RonR.
Tom

Navigation

[0] Message Index

[#] Next page