This article illustrates how to configure 1 to 98 OBi100/OBi110/OBi202 devices plus any number of OBiON Apps for single-stage dialing capability. Any OBi or OBiON App can initiate a call through any trunk of any OBi. OBi's are named #2 through #99, with no OBi named #1 due to Speed Dial #1 being forced to be an OBiON App by the OBiTALK Web Portal.
Three OBi100/OBi110/OBi202 devices will be used to illustrate the configuration steps. The dialing syntax from an OBi or OBiON App to another OBi is:
18005551212 -> Local PrimaryLine
**1 18005551212 -> Local SP1 Service
**2 18005551212 -> Local SP2 Service
**8 18005551212 -> Local LINE Port
**9 200123456 -> Local OBiTALK Service
2*18005551212 -> OBi #2 PrimaryLine
2 **1 18005551212 -> OBi #2 SP1 Service
2 **2 18005551212 -> OBi #2 SP2 Service
2 **8 18005551212 -> OBi #2 LINE Port
2 **9 200123456 -> OBi #2 OBiTALK Service
3*18005551212 -> OBi #3 PrimaryLine
3 **1 18005551212 -> OBi #3 SP1 Service
3 **2 18005551212 -> OBi #3 SP2 Service
3 **8 18005551212 -> OBi #3 LINE Port
3 **9 200123456 -> OBi #3 OBiTALK Service
4*18005551212 -> OBi #4 PrimaryLine
4 **1 18005551212 -> OBi #4 SP1 Service
4 **2 18005551212 -> OBi #4 SP2 Service
4 **8 18005551212 -> OBi #4 LINE Port
4 **9 200123456 -> OBi #4 OBiTALK Service
OBi # : OBiTALK #
==== =======
OBi #2 : 200123002
OBi #3 : 200123003
OBi #4 : 200123004
Voice Services -> OBiTALK Service -> InboundCallRoute (OBi100/OBi110):
{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<*8:>(Mli)),(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},
{(Mcot)>(Mpli):pli},{(Mcot):aa},{ph}
Voice Services -> OBiTALK Service -> InboundCallRoute (OBi202):
{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<*3:>(Msp3)),(Mcot)>(<**3:>(Msp3)):sp3},{(Mcot)>(<*4:>(Msp4)),(Mcot)>(<**4:>(Msp4)):sp4},
{(Mcot)>(<*8:>(Mli)),(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},
{(Mcot)>(Mpli):pli},{(Mcot):aa},{ph1,ph2}
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 : (200123002|200123003|200123004)
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(ob200123002)
Speed Dial #3 : PP(ob200123003)
Speed Dial #4 : PP(ob200123004)
Thanks RonR for summarising our previous threads in a single thread such that it can be more concise and easy to read.
YH
Quote from: RonR on June 27, 2011, 10:45:14 PM
This article illustrates how to configure 1 to 98 OBi100/OBi110 devices plus any number of OBiON Apps for single-stage dialing capability. Any OBi or OBiON App can initiate a call through any trunk of any OBi. OBi's are named #2 through #99, with no OBi named #1 due to Speed Dial #1 being forced to be an OBiON App by the OBiTALK Web Portal.
Three OBi100/OBi110 devices will be used to illustrate the configuration steps. The dialing syntax from an OBi or OBiON App to another OBi is:
18005551212 -> Local PrimaryLine
**1 18005551212 -> Local SP1 Service
**2 18005551212 -> Local SP2 Service
**8 18005551212 -> Local LINE Port
**9 200123456 -> Local OBiTALK Service
2*18005551212 -> OBi #2 PrimaryLine
2 **1 18005551212 -> OBi #2 SP1 Service
2 **2 18005551212 -> OBi #2 SP2 Service
2 **8 18005551212 -> OBi #2 LINE Port
2 **9 200123456 -> OBi #2 OBiTALK Service
3*18005551212 -> OBi #3 PrimaryLine
3 **1 18005551212 -> OBi #3 SP1 Service
3 **2 18005551212 -> OBi #3 SP2 Service
3 **8 18005551212 -> OBi #3 LINE Port
3 **9 200123456 -> OBi #3 OBiTALK Service
4*18005551212 -> OBi #4 PrimaryLine
4 **1 18005551212 -> OBi #4 SP1 Service
4 **2 18005551212 -> OBi #4 SP2 Service
4 **8 18005551212 -> OBi #4 LINE Port
4 **9 200123456 -> OBi #4 OBiTALK Service
OBi # : OBiTALK #
==== =======
OBi #2 : 200123002
OBi #3 : 200123003
OBi #4 : 200123004
Voice Services -> OBiTALK Service -> InboundCallRoute:
{(Mcot)>(Mpli):pli},{(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 : (200123002|200123003|200123004)
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(ob200123002)
Speed Dial #3 : PP(ob200123003)
Speed Dial #4 : PP(ob200123004)
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!
Quote from: facaletz on July 30, 2011, 03:17:31 PM
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!
I don't sell OBi's. I'm just a regular user like yourself.
Quote from: facaletz on July 30, 2011, 03:17:31 PM
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!
Straight to the point. There is a strong message here.
RonR!! You ,,regular'' users should get some slices from the bread!!!I thought you're promoting your own product.
It is ,,trendy'' now to trow the unfinished product on the market and put clever minds to finish it off for you!!
If u buy a computer you don't program it,just use it . Have a nice working week ahead...the weekend is just around the corner!
Ron: Quick question on the digitmap:
You mentioned change Phone/AutoAttendant:
{([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}
if my understanding is right, the above means: No digit or single digit(starts with a digit in the range 1-9) with a * after that and anything after the *.
if my understanding of the above is correct, then Obi speed dial references(gateway) can only be from 2-9 and cannot be 2 thru 99.
Quote from: earthtoobi on August 02, 2011, 11:34:55 AM
You mentioned change Phone/AutoAttendant:
{([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}
([1-9]x?*@@.)
[1-9]x? matches one- or two-digits in the range 1 - 99
* matches an *
@@. matches anything
thanks Ron.
1. [1-9] in itself is a digit that can be from 1-9.
2. x?:zero or one digit between 0-9.
effectively the above give a range of 1-99.
Quote from: earthtoobi on August 02, 2011, 12:30:21 PM
1. [1-9] in itself is a digit that can be from 1-9.
2. x?:zero or one digit between 0-9.
effectively the above give a range of 1-99.
That's it!
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!!!
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.
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.
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.
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.
RonR as per your previous reply, you mentioned that this is possible:
- If you want to use two Google Voice accounts and be able to handle four calls, (each Google Voice account can handle two calls) you would want to use Trunk Group1 as your PrimaryLine. Then when SP1 has two calls, calls number 3 and number four will go to SP2. Before I purchased the devices Obihai also mentioned that this will work.
I have configured and tested the gv accounts, the problem is that when making call3 instead of being handled by sp2 I get a service provider rejected the call, reason 503 message.
I called Obihai support line and the rep told me that trunk works as a "fail over", if sp1 is not working then it goes to sp2...!!!????
I have in the Outbound settings-Phone primary line the Trunk Group 1 and Trunk Group 1 has sp1,sp2 and is enable.
Am I missing something? Do I also have to configure DigitMap and OutboundCallRoute.?
Your help is appreciated!
You don't need to modify the PHONE Port DigitMap or OutboundCallRoute to use Trunk Group1.
Trunk Group1 defaults to sp1,sp2. You simply need to set:
Physical Interfaces -> PHONE Port -> PrimaryLine : Trunk Group 1
SP1 will be used for outgoing calls first, followed by SP2 if all sessions of SP1 are in use.
When you implement the changes described in this thread, replace {(Mcot)>(Mpli):pli} with {(Mcot)>(Mtg1):tg1} to have Trunk Group1 also used for single-stage dialing through the PrimaryLine.
Not working for me. I can dial out through the pap2 connected ObiOn-Pc App, works fine including **9 222 222 222 , just can't switch trunks. ie:**3 still tries to go out on tg1. The call log shows that **3 18005551212 is trying to go out on SP1 (part of tg1) which results in a busy signal as it is also sending **3. All other settings are per the RonR's instruction. Phone connected to Obi100 will switch trunks (**3 and **2) and connect/call fine including **9 222 222 222. Trying **2 gives the same result as **3.
What am I missing? I am using only one Obi100 w/provisioning disabled.
ObiTalk
{(Mcot)>(Mtg1):tg1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg1)):vg1},{(Mcot)>(<*8:>(Mli)):li}, {(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg1)):vg1},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}
AA DigitMap ([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
AA OutboundCallRoute {([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Phone Port
DigitMap ([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|**0|***|#|*1(Msp1)|*2(Msp2)|**3(Mvg1)|**2(Mvg2)|**6(Mvg6)|**7(Mvg7)|**9(Mpp)|(Mpli)|x.*x.)
OutboundCallRoute {([1-9]x?*@@.):pp},{**0:aa},{***:aa2},{(<*1:>(Msp1)):sp1},{(<*2:>(Msp2)):sp2},{(<**3:>(Mvg1)):vg1},{(<**2:>(Mvg2)):vg2}, {(<**6:>(Mvg6)):vg6},{(<**7:>(Mvg7)):vg7},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
lhm.,
What is the Trunk Group1 -> DigitMap?
Digit Map is (Msp1)
The Trunk List is sp1,sp2,vg1,vg2
ISTP Profile A is
(<**3>011xx.|<911:6158628600>|<411:8005000000>|1xxxxxxxxxx|<1615>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|<**20118835100>xxxxxxxx|[*#0-9][*#0-9]x.|[x*][x*].|(Mipd)|[^*]@@.)
**318005551212 matches the {(Mcot)>(Mtg1):tg1} rule in the OBiTALK InboundCallRoute due to the |[x*][x*].| rule in SP1. Consequently, the call goes out TG1.
Should I remove that part to make it work? If so, what do you recommend for my digit map? If anything.
Update: Removed |[x*][x*].| and still the same. Goes out to SP1
Quote from: lhm. on January 06, 2012, 01:22:06 PM
Should I remove that part to make it work? If so, what do you recommend for my digit map?
You have a lot of rules throughout your configuration that aren't readily apparent to me what their purpose is, so I'm not in a good position to advise.
I think you're in much deeper trouble than you might suspect as you've elected to change some of the normal service route access codes from **n to *n. The single-stage dialing configuration I posted relies on OBi-to-OBi dialing losing one of *'s in process, such that dialing **2 arrives as *2 in the receiving OBi's OBiTALK InboundCallRoute. This will be indistinguishable from your dialing *2+number from an OBiON App.
So what do I dial from ObiOn App? **3 or *3 ?
An OBiON App doesn't alter what's dialed.
My setup is now modified from the default settings per the instructions. Do you see any problems?
SP1 Digitmap:(<**2>011xx.|<911:6158628600>|<411:8005000000>|1xxxxxxxxxx|<1615>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|<**20118835100>xxxxxxxx|[*#0-9][*#0-9]x.|(Mipd)|[^*]@@.)
ObiTalk
{(Mcot)>(Mtg1):tg1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg1)):vg1},{(Mcot)>(<*8:>(Mli)):li}, {(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg1)):vg1},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}
AA DigitMap ([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
AA OutboundCallRoute {([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Phone Port
DigitMap ([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
OutboundCallRoute {([1-9]x?*@@.):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Update: Solved. It was this [*#0-9][*#0-9]x.| that was also causing the problem of going to SP1.
Thanks, RonR for leading me to the solution.
I've been trying to mess around with this and get this to work, and have been very unsuccessful. Is there anyone around that could help me to set this up. Even from my main account obiapp it won't let me do single stage calls through my sp1, sp2, or sp4 trunks, only right through with my default sp3 trunk. I'm willing to pay for time as I've just not been able to get this done and have wasted a lot of time trying to trouble shoot. I really wish that Obi would do as mentioned before and they probably would see a lot of improvement in sales and usability. I wouldn't recommend this product to anyone that would want something plug and play, and easy setup that is somewhat a novice.
Quote from: QBZappy on July 30, 2011, 11:01:50 PM
Quote from: facaletz on July 30, 2011, 03:17:31 PM
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!
Straight to the point. There is a strong message here.
Since I don't have this configuration on any of my Obi's, I just set this up on one of my Obi110's to make sure everything works.
I had problems getting it to work and found out what my problem was.
I copied the Obitalk Service InboundCallRoute and made the needed changes. I then copied the new route to the Obi's field. After messing with it for a few minutes I found that the whole call route did not paste in the field.
For some reason only the first line would paste in the field.
although I could copy and paste the full route from the post to my computer, it would only paste the first line of the route every time. I tried to copy and paste from both my computer and from the forum, both gave the same results.
I had to copy and paste one line at a time to get it all in the field.
Now it is working like it is supposed to.
Hi, I just acquired an Obi110 to use its line feature.
Now I have an Obi202 and a Obi110 that I would like should work together.
Such that calls to Obi110 line port are forwarded to Obi202 ph1 and ph2, and sometimes also to Obi110's ph port.
Also, I want to be able to use Obi110's line using single stage dialing.
---
Confirming my understanding before I go and make all the changes:
Based on the first post (thank you!) in this thread, I understand that I have to change inbound call route on both devices, create user defined digitmap on both devices, and change DigitMap and OutBoundCallRoute on ph and AA for both devices.
I should make these changes and on both Obi110 and Obi202 and all the phone ports (three in all) and AA ports of both devices?
Now for Obi202, I already have some routing logic built into the Sp1 and Sp2 digitmaps such that some numbers are routed to different SIP providers. I can let them be, right?
Such that calls to Obi110 line port are forwarded to Obi202 ph1 and ph2, and sometimes also to Obi110's ph port.
Also, I want to be able to use Obi110's line using single stage dialing
Forwarding calls to the 202
add the number of the 202 to the LINE inbound call route of the 110
{ph,pp(ob500xxxxxx)} - this will ring the phone port of the 110 plus fork all calls to the 202. You will configure the inbound call route of Obitalk Service on the 202 to direct those calls to ph1 and/or ph2
and sometimes also to Obi110's ph port.
define sometimes
Once you set up single stage dialing you can use any service of the 110. If the line is not the default for outgoing calls on the 110 you will have to prepend the trunk designation when dialing from the 202.
example:
with the 110 in speed dial slot 3 of the 202, dial 3***8+number to use the line service on the 110.
@jimates - thank you for the reply. i have set up call forward on Obi110 line port. It works!
I realized that being able to do one-stage dialing such that I can call using Obi110's PSTN line would be a good thing.
However, I am nervous about making so many changes with these complicated rules.
I already have things setup such that if there is an inbound call on the Obi110 PSTN line, then Obi202 conencted phones ring. For that I had to change Inbound routes for Obi110 Line and Obi202 Obiservice.
Now, all I want to do is being able to dial using Obi110's Line from any of the two phones connected to Obi202. While keeping the inbound logic of Obi110's PSTN line in place.
Any advice as to what portion of the initial post I need to adopt? I do have a third Obi100 device on my account, but I do not want to bring that into single stage dialing. Not needed.
Thank you!!
Mish,
Jimates has given you a way forward using RonR's "single-stage" method. RonR's post is brilliant and a classic, but may be a lot more than you need. If your OBi110 is using its default setting of PhonePort PrimaryLine = PSTN, then the following should do what you want:
In your Obi202 set a speed dial slot (I will use speed dial slot 2 in this example):
pp(ob200123456)
Where 200123456 is the number of your Obi110.
In your Obi110 use this setting:
Voice Services -> OBiTALK Service -> InboundCallRoute : {500123456>(Mpli):pli},{500123456:aa},{ph}
Where 500123456 is the number of your Obi202.
Dialling from the Obi202:
2*11223344556 will call 11223344556 using the Obi110 PSTN line.
200123456 will connect you to the auto attendant of the Obi110. If you want calls from your Obi202 to your Obi110 to go direct to its phone port, then omit {500123456:aa}.
The above is limited in as much as you can only call out on the PrimaryLine of the Obi110. In this case, if it is PSTN, then it meets your needs.
@ianobi - I did what you suggested.
PSTN line is the default line for the Phone port on Obi110.
Created a speed dial at #5 using the Obitalk website. If I press 5, then the phone connected to Obi110 rings.
Also created InboundCallRoute in Obi110:
{(290123456|300123456|500123456)>(Mpli):pli},{ph}
Did this because I am calling from Obi100 for testing purposes. Obi202 is where I need the capability.
Then I dialled 5*9812312345. However, all that happens is that ph rings. But the call does not go through to the PSTN line.
Obi110 log shows this:
Peer Name Obi100
Peer Number 300123456
Obi100 where I called 5*9812312345 from shows this
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number 5*19812312345 5*19812312345
Notice, the 1 that is prefixed to the number by Obi100. I am thinking that this must be done in SP1 of the Obi100 that I am using to call. I wonder if I can say that if a number begins with 5* then let anything that comes after that pass through without modification.
---
As to trying to resolve the basic functioning of this setup, wondering if
Some outbound call rule also needs to change? If so, in Obi110's Phone Port?
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}
You could make the changes to the outbound rules, but in the OBi100 not the OBi110. It will stop the 1 being prepended to outgoing numbers. So long as the number arriving at the OBi110 is in a format accepted by Mpli then it should be sent to pli.
In case there is any doubt regarding the OBi110 Primary Line use this rule:
{(290123456|300123456|500123456)>(Mli):li},{ph}
I think you are very close! Let me know how you get on. I cannot log in here for next 24 hours, but I will be back!
I just re-read RonR's original post:
QuoteNote: 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.
Looks like using pli does not work in InboundCallRoutes. I did not know that :-[
The suggested change to
{(290123456|300123456|500123456)>(Mli):li},{ph}
Is probably all that is required to fix it.
@ianobi - Success at last! The change you suggested worked. Further, I had to change the digit map of ITSP A because parsing of that digitmap was prefixing a 1 to the number. Now it works!
Thank you! Before I received your reply, I had already tried a lot of options. Had changed pli to li, but not Mpli to Mli!
One more question: If I do not want PSTN line to be the default line, and if I change the default line, this routing should still work right, because the inbound route in Obi110 now seems to explicitly point to li, and has nothing to do with pli.
Right?------
And one more question: :)
What do these lines achieve?
QuoteIn 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}
Mish,
I believe that you are correct about changing the Primary Line, the (Mli):li rule should still work. I cannot test that here, maybe you would :)
Let's look at the outgoing side of what you have done:
Speed dial 5 = the Obi110 number 290123456
You dialled from your Obi100: 5*9812312345
Phone Port DigitMap rule [1-9]x?*(Mpli) decides that is a valid number. It means any one or two digit number followed by a star, then a number that fits Mpli DigitMap.
Phone Port OutboundCallRoute rule {([1-9]x?*(Mpli)):pp} routes that number to the OBiTALK trunk.
The format going out to the OBiTALK trunk must be something like:
300123456 5*9812312345
I'm guessing that the Obi servers know that 5* coming from 300123456 means use the speed dial 5 number to route the call to 290123456 and strips out the 5*. So, 9812312345 is sent to 290123456 along with the "from" info 300123456
Using these default rules, only numbers matching Mpli in the sending Obi can be sent using this method.
RonR suggests changing the rules to:
Phone Port DigitMap rule [1-9]x?*@@. This means any one or two digit number followed by a star followed by anything.
Phone Port OutboundCallRoute rule {([1-9]x?*@@.):pp} routes that number to the OBiTALK trunk.
I like RONR's better as it allows us to send any numbers we wish – or letters!
Now let's look at the incoming side – the "target" OBi110 in this case.
OBiTALK InboundCallRoute:
{(290123456|300123456|500123456)>(Mli):li},{ph}
If the number coming in from any of the callers in the list matches Mli, then that number will be sent out to line.
(290123456 does not need to be in its own list)
I see no reason why this should not work, if all the DigitMaps are different from each other:
{(300123456|500123456)>(Mli):li},{(300123456|500123456)>(Msp1):sp1},{(300123456|500123456)>(Msp2):sp2},....more here...{ph}
In practice the caller numbers are best put in a User Defined Digit Map, which if called "cot" then the rules would be:
{(Mcot)>(Mli):li},...more here...
If anyone would like to take on the testing of some of this, or already knows it works, then please let us know .
I'm sorry this has been long and rambling, but my thinking and my typing are not always in synch. Did I answer the question?? ::)
Quote from: ianobi on September 27, 2012, 06:38:39 AM
Did I answer the question?? ::)
Absolutely. Thanks for the education.
My understanding of the Obi codes is increasing.
I will test out the one open matter once I am back in the same location as the Obi110 - should be in a few days. I think it should work.
Btw, one more education oriented question: What is the M in the Mpli or Mli?
Some day I need to sit down and see if I can learn Regular Expressions. :)
At last an easy question :)
M = Map (short for DigitMap)
Mpli = DigitMap Primary Line
Mli = DigitMap Line
At last, an easy answer for something related to an OBi device :)
Powerful devices, but designed for Sys Admins.