One stage dialling to remote OBi110's voice services in future firmware 1.3
jimates:
RonR,
It did work at the time of that posting. It does not right now. What firmware was in effect on May 4th, I will downgrade to it and see if it works.
edit:
I tried 2283 & 2103, same results as 2286 (doesn't work).
I tried editing the callroute to add additional rules that force the call out sp2 when **2 is prefixed. I don't know enough about the rules.
The best I got was for the call history to show the **2+called number, and the call history does show the call going out on sp2 (default is sp1). But all I got on the app was a busy tone.
This is what I tried
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(**2xx.):SP2},{(290yyyyyy)>(xx.):SP2},{(290xxxxxx|290yyyyyy):aa},{ph}
RonR:
Quote from: jimates on May 28, 2011, 08:19:31 pm
{(290xxxxxx)>(**2xx.):SP2}
You're matching the **2 AND sending it out SP2 with the rest of the number.
You should be using:
{(290xxxxxx)>(<**2:>xx.):SP2}
This matches the **2 and throws it away before sending the rest of the number out SP2.
jimates:
was this discussion started in another sub forum so I can post there instead of here?
Edit:
Ok that all works great for me. But then, I am only dealing with 2 endpoints on my device.
with this callroute
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx)>(<**8:>xx.):LI},{(290yyyyyy)>(xx.):SP2},{(290xxxxxx):ph}
I am allowing access to all services for one endpoint and restricting the other to only sp2
incoming from 290xxxxxx
xxxxxxxxxx - sends the call out the default line (sp1)
**2xxxxxxxxxx - sends the call out sp2
**8xxxxxxxxxx - sends the call out the line
any other entry from this endpoint goes to the phone
incoming from 290yyyyyy
xxxxxxxxxx - call goes out on sp2 as per the single rule for this number
jimates:
This is what I see as a solution.
This is an idea that has been coming back to me in several situations. It is still in crude form.
It requires getting away from the “generic” circle of trust, but for advanced users that should be ok.
Why can’t we have user defined callroutes, the same as we have user defined digit maps. We create a digitmap or a callroute and reference it just like they are referenced now, except we can also reference them from callroutes. (has anyone tired this)
Example: for this situation (I know this can be shortened, I left it like this for some clarity)
Obitalk Service -> OutboundCallRoute =
{(UDCR1)>(xx.):SP1},{(UDCR2)>(<**2:>xx.):SP2},{( UDCR3)>(<**8:>xx.):LI},{(UDCR4):},{(290xxxxxx):ph}
In the “user defined” section, create lists of endpoints (UDCR?) that are to be referenced for the rules.
This defined route only needs to include a list of Obi endpoints that you wish to allow to use the designated services.
290aaaaaa|290bbbbbb|200aaaaaa|200bbbbbb…………………….
The numbers can be in multiple defined routes to allow access to multiple services. The default circle of trust feature could automatically put a number in the first 3, which would equal the access it gives COT numbers now.
In my example,I have one for each service and one to reject. Any number not matching a rule will ring the phone. (I think I got it right)
With multiple callroutes you can restrict certain users to certain services, or just reject their call by using an empty designation.
This first came to me as a way to create a list to block specific numbers, or to list specific numbers for forking or forwarding.
Without any security or circle of trust this exact call route allows access to all services from any incoming endpoint, all with direct dialing.
(no masking in this callroute, entered exactly as it appears)
{(290xxxxxx|200xxxxxx)>(<**1:>xx.):SP1},{(290xxxxxx|200xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|200xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|200xxxxxx):ph}
RonR:
Congratulations, you've reinvented the wheel! :)
What you're doing is a variation of what yhfung came up with back in March:
http://www.obitalk.com/forum/index.php?topic=320.msg2901#msg2901
A much cleaner version of a general purpose dialing scheme is:
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 with your PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't.
User Settings -> User Defined Digit Maps -> User Defined Digit Mapx:
Label : cot
DigitMap : (290aaaaaa|290bbbbbb|290cccccc|290dddddd|290eeeeee)
This should allow any OBiON application listed in the 'cot' User Defined DigitMap to call out the desired trunk using single-stage dialing:
[number] through the OBi defined as the OBiON gateway (using PrimaryLine)
[**n + number] through the OBi defined as the OBiON gateway (using **n)
[<Speed Dial> + **n + number] through the OBi gateway defined in <Speed Dial> (using **n)
There's no security issues as only OBi numbers defined in 'cot' can make calls. Everyone else goes to the PHONE Port.
Navigation
[0] Message Index
[#] Next page
[*] Previous page