Freephoneline, voip.ms, and googletalk dialplan request

[Webslinger]

Hi,

I've been having a lot of difficulty getting an OBi202 dialplan working properly, and I'm a complete n00b. If someone would assist me in coming up with a working dialplan, I would really appreciate it.

I am only using 1 physical phone jack.

SP1 is freephoneline.ca

SP2 is voip.ms (outgoing only)

SP3 is google voice

A) I would like all 10 digit outgoing calls (area code + phone number) going through SP1. Also need 911, 311 dialing to 416-392-2489, *98 for voicemail, and *67 for occasional outgoing blocked caller id.

B) I would like 11 digit ((1+area code+phone number) dialing to automatically go through SP3 (google voice)

c) I would like to dial #1 to use voip.ms for everything else

I have tried all of sorts messing around with my own dial plans that I thought would work, but everything I'm trying fails; and I'm becoming pretty frustrated.

If someone could provide me a proper digit code and outbound call route for phone port 1 and the proper digit maps for profiles A, B, and C, I would really appreciate it.

Thank you (and sorry in advance for being so stupid)

[azrobert]

Physical Interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|*67|*67[2-9]xxxxxxxxx|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|#1XX.S3|**0|***|222222222)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp3):sp3},{(Msp2):sp2}

Service Provider -> ITSP Profile A -> DigitMap:
([2-9]xxxxxxxxx|<311:4163922489>|*67|*67[2-9]xxxxxxxxx|*98|911)

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (<#1:>XX.)

Service Provider -> ITSP Profile C -> DigitMap:
DigitMap: (1xxxxxxxxxx)

I didn't know if you just dial *67 or *67 plus a 10 digit number, so I allowed for both.

Dialing #1 plus a number will be routed out SP2.
When you code XX. in a digit map there will be a 10 second delay.
I changed it to a 3 second delay.
If you get more specific with the format of the numbers dialed, you can improve on this.

222222222 is the OBi echo test.

[Webslinger]

Wow, thank you very much!

I'm going to try this out right now!

[azrobert]

I just helped someone else with almost the same configuration.
I copied my suggestion for him and made changes required for you.
That's why my fast response.
You might want the look at that topic.
It could help you understand how to configure the OBi.
http://www.obitalk.com/forum/index.php?topic=9107.0

[azrobert]

I had a coding error.
I changed the following from (#1XX.)

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (<#1:>XX.)

[Webslinger]

I didn't know if you just dial *67 or *67 plus a 10 digit number, so I allowed for both.

Thanks a lot for helping me. I really appreciate it.

The only thing is I don't want *67 to be dialing out (to a service). I just want *67 to disable caller id, for the current phone call only, in the ATA device/Obi202.

For example, if I dial *67 to freephoneline, I get an automated voice message stating "this call is not covered by your tariff plan."

What modification should I make in the dial plan?

Thanks again

[Webslinger]

Do I just remove "*67|*67[2-9]" from the two Digit Maps?

[azrobert]

You must remove those rules from the DigitMaps.
This Star Code is already defined on the OBi.
It is found here:
Star Codes -> Star Code Profile A

[azrobert]

The OBi can't block outbound CallerID.
Your provider must support this function.

[Webslinger]

You must remove those rules from the DigitMaps.

DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|*67|*67[2-9]xxxxxxxxx|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|#1XX.S3|**0|***|222222222)


Service Provider -> ITSP Profile A -> DigitMap:
([2-9]xxxxxxxxx|<311:4163922489>|*67|*67[2-9]xxxxxxxxx|*98|911)

So, I would remove "*67|*67[2-9]xxxxxxxxx", correct?

[Webslinger]

You must remove those rules from the DigitMaps.

DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|*67|*67[2-9]xxxxxxxxx|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|#1XX.S3|**0|***|222222222)


Service Provider -> ITSP Profile A -> DigitMap:
([2-9]xxxxxxxxx|<311:4163922489>|*67|*67[2-9]xxxxxxxxx|*98|911)

So, I would remove "*67|*67[2-9]xxxxxxxxx", correct?

That appears to have worked. And now caller ID is being blocked properly.

[Webslinger]

Just wanted to say thank you again to azrobert. You really made my day. Thank you!

[azrobert]

You are welcome.
We need more people like you on this forum.
Some people don't have enough class to even say if the suggestions worked or not.

Please, never apologize for not knowing how to do something.
Everybody on this forum started "Stupid", including me.

[Webslinger]

Thank you very much!

I have another question concerning the Obi202.

Is there any way to make it so that a call will go through to SP1 normally but also get the auto attendant if I hang up early? Is there a way to call straight through under this situation without getting prompted by the auto attendant?

This is my inbound call route for SP1: {(<**1>(x.1234567890|x.2345678901)):aa($1)},{ph,ph2}

If I hang up early, I get an auto callback, which is what I want. But if I call without ending the call early, with either of the two numbers listed after "x.", I get the Auto Attendant, which I don't want (the other number belongs to someone else, and I guess she would prefer not typing an additional "1" to get through to me--but still wants the benefit of being able to get free long distance when she needs it).

Basically, I would like to get an auto callback if I hang up early--but do not want the AA if I don't hang up early (I would want the call to go straight through as per normal). I suspect what I'm asking isn't possible, but I thought I'd ask anyway. Thanks again

[azrobert]

The only way I know is to block her CallerID when she doesn't want the AA.

You can shorten the AA prompt, so she doesn't have to listen to the long message.
Delete the Welcome Message and the Menu Title.

Voice Services -> Auto Attendant -> Auto Attendand Prompts
Welcome: &pause()
Menu Title: &pause()

Now you will only hear the prompt for the 3 options. You don't have to listen to the whole message. As soon as it starts, dial 1. Actually, you can enter 1 as soon as the message starts without eliminating the 2 prompts.

[Webslinger]

Okay, thank you very much, again. I appreciate your help.

The turning on and off callerID is a decent workaround. Thanks!

[Webslinger]

This is my inbound call route for SP1: {(<**1>(x.1234567890|x.2345678901)):aa($1)},{ph,ph2}

Hi,

Is there any way to remove the "**1" that shows up on the incoming caller id before the phone number and still force the AA callback through SP1?

I tried deleting <**1>, but that didn't work.

This really isn't a big deal, but I'm trying to learn.

Also, is there any way to determine T.38 protocol is, in fact, being used during a fax call from the call status screen in an Obi202?

[azrobert]

I'm trying to learn.

You want to learn, so here is the whole process.

1st this is how the AA processes a normal (non-callback) call.
After you select 2 and enter an outbound number the AA does:
Validates the number using the AA DigitMap
Routes the call using the AA outbound route.

For a callback the AA hacks its own process.
$1 is a variable that contains the inbound callerid.
The AA sends "00" to the AA DigitMap.
Rule <00:$1> in the DigitMap replaces 00 with the callerid
Now the AA outbound route receives the callerid as the dialed number.

When you do this to route the call to the aa:
{(<**1>(x.1234567890|x.2345678901)):aa($1)}
You prepend the callerid with "**1" before it's sent to the AA.

The AA outbound call route will use rule {(<**1:>(Msp1)):sp1} to route the call to SP1.

When you do this to route the call to the aa:
{(x.1234567890|x.2345678901):aa($1)}
The callerid is sent unchanged to the AA.

The AA outbound call route will use rule {(Mpli):pli} to route the call to route the call.
pli points to the AA Primary Line.
If the AA Primary Line is set to SP1 (Default) the callback will use SP1.


I don't know why removing "<**1>" didn't work for you unless the AA Primary Line wasn't set to SP1.
Note: The AA Primary Line and the Phone Port Primary Line can be different.

[Webslinger]

I don't know why removing "<**1>" didn't work for you unless the AA Primary Line wasn't set to SP1.

It's not. It's set to SP3. If I dial in and get a callback, I want to use SP3 to make a new call.

Thank you. I'm going to read over and try to understand what you just posted.

The AA Primary Line and the Phone Port Primary Line can be different.

Phone Port Primary line is set to SP1.

Also, is there any way to determine T.38 protocol is, in fact, being used during a fax call from the call status screen in an Obi202?

Thank you very much

[azrobert]

Try changing rule <00:$1> in the AA DigitMap to: 00

Now 00 will be sent to the AA outbound route.

Then add the following rule to the beginning of the AA outbound route:
{00:sp1($1)},