January 04, 2022, 08:35:50 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi 110: Block incoming numbers  (Read 4269 times)
jillanddavid
Newbie
*
Posts: 5


« on: October 22, 2013, 04:28:13 pm »

I've tried the following:

Physical Interfaces -> LINE Port

And set:
InboundCallRoute = {(1?800xx.|1?888xx.|1?877xx.|1?866xx.|1?855xx.|1?2023168196|1?5197664677|1?2892730228|1?5195269974):},{ph}

And it doesn't appear to be working. I've added my cell number to this list (although not included above Smiley) and tried calling and it got through ok. Can anyone advise what I'm missing?

cheers in advance!
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #1 on: October 22, 2013, 07:52:07 pm »

Try changing each 1? into x. .  I understand that it seems that 1? should be better.

Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4173


« Reply #2 on: October 22, 2013, 08:02:03 pm »

Did you change the Line Port RingDelay parameter?

If the RingDelay is too low the OBi110 will not process the CallerID properly.
Logged
jillanddavid
Newbie
*
Posts: 5


« Reply #3 on: October 23, 2013, 03:40:28 pm »

Thanks for the replies Shale & azrobert. Unfortunately neither did the trick.

I doubled RingDelay from 4000 to 8000 first to no effect. I then updated the InboundCallRoute to the following:
{(5191234567):},{ph}

Where 5191234567 is my cell number - and my cell was still able to call. I also tried:
{(x5194001318):},{ph}

I feel like the syntax above is maybe wrong in some way - any other advise?
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #4 on: October 23, 2013, 03:59:17 pm »

Have you checked your call history on the OBi110 to see what caller ID is being detected?
Logged
jillanddavid
Newbie
*
Posts: 5


« Reply #5 on: October 23, 2013, 04:03:03 pm »

Yes Shale, I copied and pasted the exact caller ID of my phone
Logged
jillanddavid
Newbie
*
Posts: 5


« Reply #6 on: October 23, 2013, 04:16:51 pm »

Side, I found this thread, but the example in there isn't working for me either Sad

http://www.obitalk.com/forum/index.php?topic=4260.0
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|5191234567|un@@.|anon@@.):},{ph}
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4173


« Reply #7 on: October 23, 2013, 04:46:07 pm »

The syntax looks good to me.

Try a test with {(xx.):},{ph} to see if it will block all calls.

Before making the change make sure the inbound route hasn't changed since the last time you made an update. If you make changes via the Web interface and have auto-provisioning enable OBitalk will overwrite your changes.

The default 4000 for RingDelay should work. I have mine set at 3000 and you can probably have it lower. In N. America the CallerID is trasmitted between the 1st and 2nd ring and the OBi110 needs this delay to receive the CallerID before processing the inbound route.
Logged
jillanddavid
Newbie
*
Posts: 5


« Reply #8 on: November 02, 2013, 06:58:22 pm »

Solved (for those with the same problem).

I was trying to set the InboundCallRoute on: Physical Interfaces -> LINE Port when I should've been setting the X_InboundCallRoute on Voice Services -> SP1 Service.  Embarrassed
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement