Outbound Call Routing - Is "Policy Based Routing" Feasible?
Torvette:
Here is my setup:
SP1= FreePhoneLine.ca (Account #1)
SP2= Google Voice
SP3= CallCentric
SP4= FreePhoneLine.ca (Account #2)
Here is what I need to accomplish:
(1) I want to default all outbound calls through SP1, but if I am dialing to a North American number that is long distance to me via my SP1 provider, I want the Obi to automagically detect that I am dialing outbound to North American long distance, and to automatically use SP2 (Google Voice), rather than have me prefix my call with "**2" to make this happen.
Here is what I tried to make this happen. It MOSTLY worked - I think I was close, but the cigar eludes me, because after I made the following configuration, I somehow lost my ability to use
"*98" to access my SP1 voice mail (and I do not see/understand the correlation):
ServiceProviders->ITSP Profile
A->PhonePort->OutboundCallRoute={0:ph},{(1416x.|1647x.|1905x. |1
8x.|1613x.|1514x.|1519x.|1604x.|911):sp1},{(Msp2): sp2}
... which I understand means all regular 416/647/905/1800/613/514 calls (and 911) go out
via SP1. All other calls (i.e. long distance) go to SP2. Again, in my case
SP1 is FreePhoneLine.ca, and SP2 is Google Voice.
(2) In addition to (1), I also need to be able to dial "*98" to access my
SP1 voice mail.
(3) I also would like to use a distinct star code to access my SP2
voicemail (which is Google Voice - so is this even possible??), and so on for my sp3 voicemail and my sp4 voicemail. Therefore, if *98 accesses my SP1 voicemail, can I use *88 to access my SP2 voicemail, *77 to access my SP3 voicemail, and *66 to access my SP4 voicemail (I realize that these star codes I am using in my example conflict with existing star codes - I am just using them as an example. When I have a solution, I will choose star codes that are not already in use).
Many thanks!
zapattack:
Why not use Speed Dial? For example, for Freephone use 'F' (3).
By pressing F# you would access speed dial 3, in which you put
**1 ( to access SP1) followed by what you need to access the VM system.
For FP account 2, you could use 'FF#' which is Speed Dial 33. (**4 etc.)
Similarly for GV you could use G# for Speed Dial 4 and put in **2 (for SP2)followed by your GV 11 digit number. eg:**212025551234
and C# for CallCentic - Speed Dial 2 (**3, etc.)
Torvette:
Interesting idea.
I will give a shot and report back on my results - thanks for the input!
Torvette:
Hmmm....
I did as you suggested (slight modification to the speed dial numbers, though):
Configured speed dial such that:
(1) 1# calls my SP1 voicemail
(2) 2# calls my SP2 voicemail
(3) 3# calls my SP3 voicemail
(4) 4# calls my SP4 voicemail
... and this worked as I expected.
BUT - when I then went to edit the "Outbound Call Route" again, it blew up - and I am now getting the "there is no call route available" error message. So I am back to where I started.
Here is my Outbound Call Route Config again (the issue must lie here somewhere, but I cannot see it):
ServiceProviders->ITSP Profile
A->PhonePort->OutboundCallRoute={0:ph},{(1416x.|1647x.|1905x. |1
8x.|1613x.|1514x.|1519x.|1604x.|911):sp1},{(Msp2): sp2}
.... thoughts?
Torvette:
Well, I have some progress.
There was a hard-to-catch typo in my OutboundCallRoute string - an extra space before the toll-free numbers. So, mostly all is good with the setup.
I was hoping to use *98 star code in addition to the speed dial (1#) config to access the voice mail for SP1 (just because the wife is picky, and insists she wants the use of *98).
*98 now just gives me a continuous tone. The adventure continues....
Navigation
[0] Message Index
[#] Next page