Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: "Outgoing Call Routes"

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Feb 2007
    Posts
    423

    Default "Outgoing Call Routes"

    Tim and Brandon; I'm posting here because I believe you said you wanted questions to migrate to the Beta instead of the Alpha. More this or correct me if I'm wrong.

    Anyway; on the "Overseas" thread in Alpha, I mentioned wanting to be able to dial 3 digit codes like 511 and 411 and have them auto dial the appropriate 1-800 type number. Tim, you mentioned Brandon saying this can already be done in the "Outgoing Call Routes" section. I put in a 3 digit number "511" in the outgoing with a forward number of 1-888-xxx-xxxx (X=real number). I saved it. I've waited a while, but when I dial 511 after about 3 0r 4 seconds, I just get a busy. Dialing the actual 1-888 number works fine. Is there a certain time limit to wait? (It's been a while). Do I need to reboot the adapter? Is it still a feature in the works? Thx... Mike....
    Mike
    "Born Wild - Raised Proud"
    Do you like your life? - Thank a Vet!!!

  2. #2
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,043

    Default Re: "Outgoing Call Routes"

    It should be instant. We need to look at it to see what that's not working
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  3. #3
    Join Date
    Jul 2007
    Location
    Irvine CA
    Posts
    519

    Default Re: "Outgoing Call Routes"

    Hello Mike, I will check on this, but enter a 10 digit number, so without leading 1, so i.e. 8005558355.

    I will make sure that the correct changes are applied no matter the format.

    Let me know if that works for you, thanks!
    ________
    Old Man Boys
    Last edited by VOIPoBrandon; 03-21-2011 at 07:35 PM.

  4. #4
    Join Date
    Feb 2007
    Posts
    423

    Default Re: "Outgoing Call Routes"

    Yes brandon; Thanks. Forwarding WITHOUT the "1" fixed it. Definitely might want to fix that so either format works. If not, there will be a lot of customer support calls. Thanks again. It works fine. Later.... mike.....
    Mike
    "Born Wild - Raised Proud"
    Do you like your life? - Thank a Vet!!!

  5. #5
    Join Date
    Feb 2007
    Posts
    146

    Default Re: "Outgoing Call Routes"

    Would using this method of only entering a 3-digit number cause an issue with other numbers containing the same 3-digit number? 411 vs. xxx-xxx-4110, for example.

  6. #6
    Join Date
    Feb 2007
    Posts
    423

    Default Re: "Outgoing Call Routes"

    I will try that tonight. I have some extensions at work that have 511 in it's number. I doubt it will be a problem because the pbx (sip server) has certain timers. I.e. When I dial manually the 1-888 number that my 511 points to, it immediately pretty much starts to ring on the other end. However, when I dial 511, there is a good 2-3 second pause before it starts ringing. I believe the server is waiting to see if there are more numbers. If there are, then obviously the 511 isn't the shortcut number. I'll experiment with it. Later... Mike....
    Mike
    "Born Wild - Raised Proud"
    Do you like your life? - Thank a Vet!!!

  7. #7
    Join Date
    Jul 2007
    Location
    Irvine CA
    Posts
    519

    Default Re: "Outgoing Call Routes"

    Quote Originally Posted by sbradshaw View Post
    Would using this method of only entering a 3-digit number cause an issue with other numbers containing the same 3-digit number? 411 vs. xxx-xxx-4110, for example.
    Hello, the answer to this question is simply put -- no. The call routing matches either a) Only the partial number, in the above example "411". Now keep in mind there are wild cards, however in which case if you *DID* for whatever reason want to match something like that number you mentioned, you could simply do:

    "******4110"

    Essentially * matches [0-9] for any of you guys who may know regex, simply put once again, this is any numeric integer between 0 and 9, matched 1 or more times.


    So a few examples
    "411" matches -> 411
    "*411" matches *411******
    "*411*5" matches *411*5***

    Now that above is the current method, of how we're matching, however this is not 100% set, so I do need some more input from you guys actually.

    Heres somewhat of my thinking:
    CURRENT METHOD:
    714* -> 714*******
    *714 -> *714******
    *714* -> *714******

    NEW METHOD ?:
    714* -> 714*******
    *714 -> *******714
    *714* -> *714******

    Also, I'm perhaps thinking about integrating some other type of wild card symbol such as %, how this would work, would be such as: %714%, would match any number with 714 in it, so it would match the following:

    714 *** ****
    *** 714 ****
    *** *** 714*
    *** *** *714
    and so on.......

    The other thing to consider also, is how we would want to integrate international numbers into this too, any thoughts / suggestions, etc is all appreciated, let me now what you guys feel would work best for you.
    ________
    LESBIAN ASSLICKING
    Last edited by VOIPoBrandon; 03-21-2011 at 07:35 PM.

  8. #8
    Join Date
    Feb 2007
    Posts
    801

    Default Re: "Outgoing Call Routes"

    You have a lot of options here. If you want to find the solution that will meet most peoples' needs, you should consider real-world scenarios. How are phone numbers related? It's pretty rare that there's any real relationship (that a customer would want to filter against) between multiple DIDs that share the same digits in the 7-10th digits in the 10-digit number. The only thoughts that come to mind are Papa John's pizza places--they seem to ask the incumbent telcos for NPA-NXX-7272 (PAPA) or some other repeating pattern, and there's no guarantee that they get it)--or that businesses often seek numbers like this: (NPA-NXX-x000). However, there's nothing to say that residences are never assigned "x000" numbers; in fact, I know of at least one without thinking very hard.

    The watch-out I'm presenting here is that if you make the filtering 'too powerful' you may well run into the law of unintended consequences. Your system will end up blocking the calls your customers program it to block, rather than the calls your customers intend it to block.

    For domestic pattern matching, you might be best served with a system that only uses numerals and 'X' characters that match digit-for-digit (as opposed one or more times). That way, all patterns the user enters must be ten digits long (nice error check), and it should be pretty explicit. Customer can choose any of the patterns:
    919XXXXXXX (block all 919 area-code calls)
    XXX249XXXX (block all calls from/to 'exchange' 249, no matter the area code)
    XXXXXXX249 (block all calls ending in 249, though I'm not sure why)

    You could have a radio button to select domestic or international call pattern matching, where the domestic calls have the ten-digit requirement and X or numeral limitations. For international calls, though, having a wild card that matches one or more digits would be necessary. There again, most people would be blocking calls to/from a specific country (or part of a country); I would expect most blocking patterns to specify the beginning of the pattern specifically, followed by a variable number of digits (e.g. 01144* to block all calls from country code 44 vs 011*44 for any international call with "44" in it).

  9. #9
    Join Date
    Feb 2007
    Posts
    280

    Default Re: "Outgoing Call Routes"

    How about offering a 'nice' auto-block of 242, 246, 264, 268, 284, 345, 441, 473, 649, 664, 670, 758, 767, 784, 787, 809, 829, 867, 868, 869, 939 area codes unless somehow expressly requested to be authorized. Might save some mighty big billing surprises from NANPA countries other than Canada and the U.S.A.

  10. #10
    Join Date
    Jul 2007
    Location
    Irvine CA
    Posts
    519

    Default Re: "Outgoing Call Routes"

    Quote Originally Posted by gbh2o View Post
    How about offering a 'nice' auto-block of 242, 246, 264, 268, 284, 345, 441, 473, 649, 664, 670, 758, 767, 784, 787, 809, 829, 867, 868, 869, 939 area codes unless somehow expressly requested to be authorized. Might save some mighty big billing surprises from NANPA countries other than Canada and the U.S.A.
    This should already be in effect, let me know if otherwise .
    ________
    500
    Last edited by VOIPoBrandon; 03-21-2011 at 07:35 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •