dslreports logo
uniqs
10
Mango
Use DMZ and you get a kick in the dick.
Premium Member
join:2008-12-25
www.toao.net

Mango to bbs2012

Premium Member

to bbs2012

Re: Obi200 - different providers for incoming/outgoing?

Very curious. The guide LOOKS correct. But when I copy/paste, there are extra characters that should not be there. The following should work: (note the extra dashes are removed)

(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6-7]x*xxxxxxxxxxx.)
 
said by bbs2012:

While we are at it, is there a way to block dialling of 911 in the same digit map?

For liability purposes I am not going to answer this. Sorry.
bbs2012
join:2012-04-10
Ontario

bbs2012

Member

I understand. I was able to copy a digit map from elsewhere that made 10 digit dialling work. Thanks for all your help!

One more question - is there a way to prevent SP2 (FPL) from ringing the phone on incoming calls? Or will that happen automatically since the ATA has not registered with the FPL server?
bbs2012

bbs2012 to Mango

Member

to Mango
"For liability purposes I am not going to answer this. Sorry."

Is there a way to design the digit map so that 911 calls go out through SP1 and all other calls through SP2?
bbs2012

bbs2012

Member

And one more question - is there a way to automatically block caller id for outgoing calls using the digit map? (since FPL does not allow caller id spoofing)
Mango
Use DMZ and you get a kick in the dick.
Premium Member
join:2008-12-25
www.toao.net

Mango to bbs2012

Premium Member

to bbs2012
said by bbs2012:

Or will that happen automatically since the ATA has not registered with the FPL server?

That will happen automatically if the ATA is not registered - unless your firewall is insecure and you receive scanning calls; post back and we can give you some advice if that happens.
said by bbs2012:

Is there a way to design the digit map so that 911 calls go out through SP1 and all other calls through SP2?

That we can definitely do. Please try to add the following to the beginning of your PHONE Port OutboundCallRoute:

{([589]11):sp1},
 

The above is from memory. To test to see if I'm right, dial 511 or 811, and if the call is routed via VoIP.ms, 911 should work properly.
said by bbs2012:

And one more question - is there a way to automatically block caller id for outgoing calls using the digit map? (since FPL does not allow caller id spoofing)

As far as I'm aware you can't do this, but you could try to dial *67 before a call to test to see if I'm right.
bbs2012
join:2012-04-10
Ontario

bbs2012

Member


That we can definitely do. Please try to add the following to the beginning of your PHONE Port OutboundCallRoute:

{([589]11):sp1},

The above is from memory. To test to see if I'm right, dial 511 or 811, and if the call is routed via VoIP.ms, 911 should work properly.

That worked. Thanks. Now to to figure out how to block outgoing caller ID so I don't have to dial *67 each time.
Mango
Use DMZ and you get a kick in the dick.
Premium Member
join:2008-12-25
www.toao.net

Mango

Premium Member

*67 worked? Wow. Try *81; that should make it stick.
bbs2012
join:2012-04-10
Ontario

bbs2012

Member

Nope. *67 did not work on FPL. Nor did *81.
In searching around the net and on FPL forums, it looks like FPL does not honour caller ID blocking and passes the information along to other providers. So I don't think this will work for me. I will just have to stick with my voip.ms line and pay the (quite reasonable) charges for outgoing calls.
azrobert
join:2015-02-07
Fountain Hills, AZ

2 edits

azrobert to bbs2012

Member

to bbs2012
said by bbs2012:

And one more question - is there a way to automatically block caller id for outgoing calls using the digit map? (since FPL does not allow caller id spoofing)

You can use a star code to accomplish this function. The following example can be modified if it doesn't meet your requirements.

»www.obitalk.com/forum/in ··· msg88502

Edit:
I didn't see your post saying *67 doesn't work on FPL. Maybe this will help someone else, so I'll leave this post.