Star Code to a specific SP?
giqcass:
Quote from: SteveInWA on January 31, 2015, 06:07:21 pm
That's ridiculous. It is so much simpler to just enter **2, or whatever the SP is, that has been configured with the oubound/generic GV account. Even with all that tweaker configuration, you'd still be pressing three buttons (*67).
It sounds like he already has a service provider on SP2 and it isn't Google.
azrobert:
If you want to use **2*67 followed by a number, you still have to do some tweaking.
The characters after **2 must match a rule in the ITSP B DigitMap and it doesn't.
This is the default ITSP B DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
*67 doesn't match any of these rules.
The Star Code giqcass suggested in the 1st reply should work.
SteveInWA:
Agreed -- the simplest change possible to fix the digit map(s) to properly interpret a SP selection (e.g. **2 or **4) followed by a star code, would make the most sense. In fact, IMO, Obihai ought to correct their default configurations to handle this.
The overall goal of supporting the OBi products should be to assume that less than 0.1% of the product line's users have the programming aptitude or interest in learning how to write, modify or maintain the sort of digit map code ianobi posts, and that the simplest, most technically-elegant solution, is always easier to understand and maintain, for the large majority of users.
Remember how many people had flashing 12:00 on their VCRs? That's the paradigm to keep in mind.
202Owner:
Quote from: 7Priest7 on January 31, 2015, 11:03:18 am
Greetings,
Is there a way to cause a star code to use your non primary SP?
For example, I'd like to use *67 exclusively with SP2 as Google Voice doesn't support caller id blocking. If not, guess I can just use **2.
Thanks!
Maybe... Star Code script processing is very finicky. What works on my OBi202 may not work on your OBi.
Star Code scripts are barely documented on page 175 of the Admin Guide http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf
I assume:
o GV is on SP1 and another service is on SP2.
o (Msp2) is defined to support the SP2 dialing requirements.
o PHONE Port digit map and outbound call route are defined to route **2(Msp2) to the SP2 trunk.
Redefine the *67 Block Caller ID Once Star Code (edit, submit, reboot):
star code, description, action, action
*67(<**2>(Msp2)), B, set($Bci1,1), call($Code)
Leave the description argument B as a single letter... small. I don't think the Star Code processing is intended to do too much. Truncating the description seems to let it process ok here.
Dial *67number. The number **2(Msp2) will be stored in variable $Code. set($Bci1,1) will block CallerID once. call($Code) will send the number **2(Msp2) to the PHONE Port outbound call route.
If you have a DID for SP2 and a CallerID filter defined to send Anonymous (no CallerID) to voice mail, a *67did call *should* go out SP2 to voice mail. It works here.
7Priest7:
Quote from: giqcass on January 31, 2015, 05:54:02 pm
Quote from: ianobi on March 09, 2013, 05:51:11 am
This will make every number that starts with *67 go out via sp2. I’m using sp2 of an OBi110 in this example. Changes shown in bold.
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|*67(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
Physical Interfaces > PHONE Port > OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(*67(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
This should be useful.
Thanks, incredibly useful stuff.
Now if only I could get my digitmap and outboundcallroute to actually apply.
I set obitalk expert config to use device defaults for those, then I unticked default on my devices config page, then I put some new digitmap and outboundcallroute. I tried it both without auto provisioning and with, doesn't seem to want to work today...
Did I mess them up somehow?
DigitMap ([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|*67(Msp2)|**2(Msp2)|**9(Mpp)|(Mpli))
OutboundCallRoute {(<411:18003733411>):sp1},{(*67(Msp2)):sp2},{([1-9]x?*(Mpli)):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
To answer the reason of why, guests.
Explaining what **2 does is a stupid conversation.
Course at this point it would have been easier.
Navigation
[0] Message Index
[#] Next page
[*] Previous page