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

Thread: Incoming wild-card routing still possible?

  1. #1
    Join Date
    Feb 2007
    Location
    Michigan
    Posts
    2,220

    Default Incoming wild-card routing still possible?

    Former thread ...

    714* -> 714*******
    *714 -> *714******
    *714* -> *714******
    Just wondering if partial matches is still possible?
    I am thinking to whitelist my 734 exchange.
    I should be able to use 734* and see all local calls get through?


    Using VOIPo services since February 2007
    Beta Tested the VOIPo Reseller Plan.
    A happy VOIPo Residential Customer

    Using VoIP devices since 12-2002
    Companies I've tried
    iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
    VOIPo is a keeper!


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

    Default Re: Incoming wild-card routing still possible?

    Quote Originally Posted by usa2k View Post
    Former thread ...

    Just wondering if partial matches is still possible?
    I am thinking to whitelist my 734 exchange.
    I should be able to use 734* and see all local calls get through?
    Should be yeah.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  3. #3
    Join Date
    Feb 2007
    Location
    Michigan
    Posts
    2,220

    Default Re: Incoming wild-card routing still possible?

    An observation ...
    With call routing I have mainly used

    • All Unknown contacts
    • Groups


    I see

    • Contact (leverages the phone book data)
    • Contact Number (leverages the phone book data)
    • Number (Is any number and need not be in the phone book)

    My tests of 734* or 734******* get displayed as 734******* in the routing list.

    My tests seem to prove this can be entered without error to route to whitelist.

    Still, unknown 734xxxxxxx numbers still go to voicemail.

    VOIPo may need to allow a hierarchy of matching, so the call is tested against 734******* first before being routed by unknown?


    Using VOIPo services since February 2007
    Beta Tested the VOIPo Reseller Plan.
    A happy VOIPo Residential Customer

    Using VoIP devices since 12-2002
    Companies I've tried
    iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
    VOIPo is a keeper!


  4. #4
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: Incoming wild-card routing still possible?

    I'm adding the wildcards as something we need to review some to make sure it's still working and document the possible uses/formatting.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  5. #5
    Join Date
    Feb 2007
    Location
    Michigan
    Posts
    2,220

    Default Re: Incoming wild-card routing still possible?

    Thanks!

    (I MEAN) Putting in 4 digit numbers in dial-out routing has odd results also BTW.

    Definitely think about an order to fall through like a firewall would use.


    I offer this structure as food for thought.

    THIS IS A POSSIBLY GOOD HIERARCHY: (defaults are RING)

    • Route Hidden-Private to: (VM/BUSY/DISCONNECTED/RING/VIRTUAL-VM)
    • Route Unknown Number to: (VM/BUSY/DISCONNECTED/RING/VIRTUAL-VM)
    • Route Wildcard XXX* to: (VM/BUSY/DISCONNECTED/RING/VIRTUAL-VM)
    • Route Blacklist to: (VM/BUSY/DISCONNECTED/RING/VIRTUAL-VM)
    • Route Whitelist to: (RING)
    • Route Forward to : (FORWARD/VIRTUAL-VM)
    • Route Destination to : (VM/BUSY/DISCONNECTED/RING/FORWARD/VIRTUAL-VM/DIAL-OUT)

    * The last MATCH wins.
    * A Destination could be affected by the Primary or Virtual DID number called.)
    * A Virtual Number could be set as dial-out/password , and offer a dial tone.
    * Forward on busy would be a good addition
    * Forward on no answer could be a good CALL-HUNT
    * RING-LIST would be a good simul-ring concept.

    A call directed at a virtual number could send an email with attachment.
    And then have the primary or another virtual number have an email with attachment and SMS.
    Last edited by usa2k; 06-21-2008 at 01:57 PM.


    Using VOIPo services since February 2007
    Beta Tested the VOIPo Reseller Plan.
    A happy VOIPo Residential Customer

    Using VoIP devices since 12-2002
    Companies I've tried
    iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
    VOIPo is a keeper!


  6. #6
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: Incoming wild-card routing still possible?

    Can you verify that wildcards are working in call routes for you now?
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  7. #7
    Join Date
    Feb 2007
    Location
    Michigan
    Posts
    2,220

    Default Re: Incoming wild-card routing still possible?

    I took my cell phone out of my Phone Book a while ago.
    I have had 734******* as a white list call route
    A test a moment ago, my cell phone went straight to Voicemail.

    I will reboot the TA and retry. (But its not related to my end is it?)
    Reboot, no-go.

    I see if I try 1734* it dumps the 1 and adds the seven asterisks
    Last edited by usa2k; 07-02-2008 at 06:35 PM.


    Using VOIPo services since February 2007
    Beta Tested the VOIPo Reseller Plan.
    A happy VOIPo Residential Customer

    Using VoIP devices since 12-2002
    Companies I've tried
    iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
    VOIPo is a keeper!


  8. #8
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: Incoming wild-card routing still possible?

    Quote Originally Posted by usa2k View Post
    I took my cell phone out of my Phone Book a while ago.
    I have had 734******* as a white list call route
    A test a moment ago, my cell phone went straight to Voicemail.

    I will reboot the TA and retry. (But its not related to my end is it?)
    Reboot, no-go.

    I see if I try 1734* it dumps the 1 and adds the seven asterisks
    Ray worked on it today, so I'll ask him to post about the usage cases and have him double check it again tomorrow.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  9. #9
    VOIPoRay Guest

    Default Re: Incoming wild-card routing still possible?

    Quote Originally Posted by usa2k View Post
    I took my cell phone out of my Phone Book a while ago.
    I have had 734******* as a white list call route
    A test a moment ago, my cell phone went straight to Voicemail.

    Should work now.... I was under the impression that you had DND set to go to voicemail and that wasn't working... after reviewing your account, i saw that it was "all unknown contacts" set to go to voicemail.... since the wildcard wasn't working on DND either, i ASSuMEd i'd found the problem and stopped there...

  10. #10
    Join Date
    Feb 2007
    Location
    Michigan
    Posts
    2,220

    Default Re: Incoming wild-card routing still possible?

    I'll check when I get home, but the phone rang 3 times from work before going to VM and that is a good sign


    Using VOIPo services since February 2007
    Beta Tested the VOIPo Reseller Plan.
    A happy VOIPo Residential Customer

    Using VoIP devices since 12-2002
    Companies I've tried
    iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
    VOIPo is a keeper!


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
  •