Single-Stage Dialing Through Any OBi Trunk

<< < (3/9) > >>

Everton:
In My case I have only one (1) OBi110 Device and three (3) Android Phones and I want to be able to use Single-Stage Dialing Through Any OBi Trunk from any one of the three phones.  Following your detail procedure, I made the following changes.


      18005551212  ->  Local PrimaryLine
**1 18005551212  ->  Local SP1 Service (Goggle Voice setup on SP1 - Local Primary Line)
**2 18005551212  ->  Local SP2 Service (VOIP.ms setup on SP2)
**8 18005551212  ->  Local LINE Port     (not used at this time)
**9 200123456     ->  Local OBiTALK Service

Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)

    
   My OBi
End Points                                        OBi No.    
=============                         ============
OBi #1 (Home)                             :  200123456
OBi #1 (Everton)                          :  290234561

I have three Android Mobile Devices each with the OBiON App for Android loaded and setup two (2) additional OBiTALK Accounts, which generates two additional OBiTALK Numbers (290XXXXX2 and 290XXXXX3).  So, there are a total of three (3) OBiTALK Numbers as shown below, with  OBi No. 290234561, assigned to my main OBiTalk Account.

OBiTALK #                                                        My OBiTALK No.
=============                                             ===============
OBiON #1 (Everton Mobile Phone)                        :   290234561
OBiON #2 (Friend 1  Mobile Phone)                       :  290XXXXX2
OBiON #3 (Friend 2  Mobile Phone)                       :  290XXXXX3



Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*8:>(Mli)):li},
{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

Note: Replace pli above (2 places) with the OBi's PHONE Port -> PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't do it for you.


User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123456|290234561|290XXXXX2|290XXXXX3)

Note: These are trusted caller OBiTALK numbers.  This DigitMap should also contain the OBiTALK numbers of any OBiON Apps that are used.


In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.

In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}


Speed Dial #2 : PP(ob200123456)

We also have each OBiTALK numbers as part of the speed dial and trusted callers list!

For Mobile Device, Everton, I have added Friend 1 and Friend 2 to "My Circle of Trust", and for Friend 1, I have added Everton and Friend 2 to the "My Circle of Trust" and finally, for Friend 2, I have added Everton and Friend 1 to the "My Circle of Trust".

After making the changes outlined above, I did a test call from OBiON #2 (Friend 1) to a VOIP.ms number and the phone did not ring, yet I got their voice mail.  I also, call a Target Store and was able to speak to someone (that works).

Looking at what I did, could you spot what could cause the VOIP.ms number (Physical analog phone) to NOT ring.  This number is also listed as a speed dial and trusted caller on all three OBiTALK App and the OBi110 speed dial list!!!

RonR:
Quote from: Everton on August 09, 2011, 07:14:02 am

Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)


If you want access to Voice Gateway3 (presumably **3) from OBiON Apps, you will need to add it to the InboundCallRoute.

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},
{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

Quote from: Everton on August 09, 2011, 07:14:02 am

We also have each OBiTALK numbers as part of the speed dial and trusted callers list!

For Mobile Device, Everton, I have added Friend 1 and Friend 2 to "My Circle of Trust", and for Friend 1, I have added Everton and Friend 2 to the "My Circle of Trust" and finally, for Friend 2, I have added Everton and Friend 1 to the "My Circle of Trust".


Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):

User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123456|290234561|290XXXXX2|290XXXXX3)

Quote from: Everton on August 09, 2011, 07:14:02 am

After making the changes outlined above, I did a test call from OBiON #2 (Friend 1) to a VOIP.ms number and the phone did not ring, yet I got their voice mail.  I also, call a Target Store and was able to speak to someone (that works).

Looking at what I did, could you spot what could cause the VOIP.ms number (Physical analog phone) to NOT ring.  This number is also listed as a speed dial and trusted caller on all three OBiTALK App and the OBi110 speed dial list!!!


Again, do not use the OBiTALK Web Portal's Trusted Caller / Circle of Trust mechanisms.

If VOIP.ms voicemail answered, then your call obviously went through to VOIP.ms and the OBi has no control over whether the phone on that end rings or not.

QBZappy:
Quote from: RonR on August 09, 2011, 09:40:38 am

Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):


Implied in this comment is the fact that the OBi should be setup either via the OBi web portal or the OBi unit directly. OBi is designed to be programmed  either way. Users must pick one method. Obviously RonR has designed his code to be setup on the OBi unit directly, making you choose the OBi unit configuration method.

If / when OBi integrates "Single-Stage Dialing Through Any OBi Trunk"  into one of their wizards it looks like RonR is generously offering his time to support this.

RonR:
Quote from: QBZappy on August 09, 2011, 10:33:41 am

Quote from: RonR on August 09, 2011, 09:40:38 am

Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):


Implied in this comment is the fact that the OBi should be setup either via the OBi web portal or the OBi unit directly. OBi is designed to be programmed  either way. Users must pick one method. Obviously RonR has designed his code to be setup on the OBi unit directly, making you choose the OBi unit configuration method.


There is nothing unique about the configuration described in this thread.  Users are free to implement the changes described here directly through the OBi (requiring that Auto Provisoning be disabled) or through the OBiTALK Web Portal (requiring that Auto Provisioning be enabled).

Trusted Caller / Circle of Trust is wholly controlled by rules in the OBi's InboundCallRoute.  Since configuration through the OBiTALK Web Portal generates an InboundCallRoute that limits single-stage dialing to the PrimaryLine only, it's necessary to use a custom set of InboundCallRoute rules to provide single-stage dialing through any OBi trunk.  The OBiTALK Web Portal does not provide Trusted Caller / Circle of Trust support for custom InboundCallRoute rules.  As such, the OBiTALK Web Portal cannot be used for Trusted Caller / Circle of Trust configuration in this case.

Quote from: QBZappy on August 09, 2011, 10:33:41 am

If / when OBi integrates "Single-Stage Dialing Through Any OBi Trunk"  into one of their wizards it looks like RonR is generously offering his time to support this.


If the OBiTALK Web Portal supported "Single-Stage Dialing Through Any OBi Trunk", there wouldn't be a need for a custom set of InboundCallRoute rules as described in this thread.  Regardless of what is integrated in the future, I hope to continue generously offering my time to support users any way I can.

Everton:
Quote from: RonR on August 09, 2011, 09:40:38 am

Quote from: Everton on August 09, 2011, 07:14:02 am

Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)


If you want access to Voice Gateway3 (presumably **3) from ONiON Apps, you will need to add it to the InboundCallRoute.

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},
{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}



Great, you are one step ahead of me, since this was going to be my next question!  Thanks and I did go ahead and add this feature.  Maybe you should add it to you general writeup.

Turns out the reason the phone did not ring is that I had a call filtering associated with the CID associated with SP1, which sent the calls to voice mail without ringing the phone...LOL!!  Once I removed the VOIP.ms filter the calls came through.  I couldn't understand why the calls work to some numbers and not the VOIP.ms DID.

I also, removed all the "My Circle of Trust" and "Trusted Callers" setup from all three OBiONs!

BTW, your writeup, although appearing intimating at first glance, is actually quite simple.  Excellent work/creativity!!  Thanks for your help on this.

Navigation

[0] Message Index

[#] Next page

[*] Previous page