Star Code to a specific SP?

(1/3) > >>

7Priest7:
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!

giqcass:
Yes you can.  I actually do that myself.  I use a second Google Voice account that does not have a number assigned for my *67 calls.

Change Star Code#5 to:
*67(<sp2(*67>xx.<)>), Call block, call($Code)



EDIT: I was looking at the code and realized my suggestion might not work with your set up.It may work with some providers like Callcentric.  In my original reply I was simply sending *67 out as part on the number.  I think the Obi sends it as a sip header.  As such *code 5 may need to remain as it was like the following.
*67, Block Caller ID Once, set($Bci1,1)

Then we may need to redirect the call using
physical intefaces >> Line port >> OutboundCallRoute

Perhaps someone with better skills can enlighten us.

SteveInWA:
I answered this question in another thread, but I'm too lazy to go find it.

GV doesn't support anonymous calling.  *67 doesn't do anything.  Instead, set up a second Google Voice account without its own GV-supplied or ported-in phone number, and add it as another SP on your OBi.  Calls made from that SP will show a generic/shared Google phone number as caller ID.  You'll only use this SP for outbound calls, since it has no inbound number.

So, if the second GV account is provisioned on SP2, then simply prefix calls with **2 and then the phone number.

giqcass:
Quote from: ianobi on March 09, 2013, 05:51:11 am

giqcas,

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}

Now if you dial *6712345678912, this rule {(*67(Msp2)):sp2}, will match it and send *6712345678912 out to sp2.

The problem is that it stops you using *67 on any other service. Here is an alternative way:

Leave this at default:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

Changes shown here in bold:
Physical Interfaces > PHONE Port > OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:*67>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Now if you dial **212345678912, this rule {(<**2:*67>(Msp2)):sp2}, will replace **2 with *67 and send *6712345678912 out to sp2.

All this assumes that you first do this as you suggest:
Delete the following line from your star codes
*67, Block Caller ID Once, set($Bci1,1)

Edit: No need to delete *67, Block Caller ID Once, set($Bci1,1) using the second method as you are using prefix **2 followed by the number, which gets transformed into *67 followed by number when processed through the Phone Port OutboundCallRoute.


This should be useful.

SteveInWA:
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).

Navigation

[0] Message Index

[#] Next page