Jump to content

Search the Community

Showing results for tags 'pattern'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to the 2600Hz Forums!
    • Forum Rules & Announcements
    • Upcoming Events: Come Meet Us!
    • 2600Hz News
    • Introductions
  • Platform Basics
    • Product Discussion
    • Tips and Feedback
    • Starting Out and Training
  • Advanced Topics
  • 2600Hz Mobile
    • 2600Hz Mobile
  • 2600Hz Open Source Developers
    • General OS Kazoo Questions
  • Vendor Discussion
    • Hardware Endpoints
    • PSTN, Software, and Services

Categories

  • 2600Hz Mobile
    • Sales and Marketing
  • Accounts Manager
    • User Resources
    • Sales and Marketing
  • Advanced Provisioner
    • Sales and Marketing
    • User Resources
  • Authentication
    • User Resources
    • Sales and Marketing
  • Billing and Transactions
  • Blocklist Numbers
    • Sales and Marketing
    • User Resources
  • Branding Manager
    • User Resources
    • Sales and Marketing
  • Callflows | Advanced Callflows
    • User Resources
    • Sales and Marketing
  • Call Center
    • Sales and Marketing
  • Call Recording
    • User Resources
    • Sales and Marketing
  • CallThru.us
    • User Resources
    • Sales and Marketing
  • Cluster Manager
    • Sales and Marketing
    • User Resources
  • comm.land Desktop User Portal
    • User Resources
    • Sales and Marketing
  • Conference Manager
    • User Resources
    • Sales and Marketing
  • CSV Onboarding
    • User Resources
    • Sales and Marketing
  • Debug Tool
  • Dial Plan Manager
    • User Resources
    • Sales and Marketing
  • Duo Integration
    • User Resources
    • Sales and Marketing
  • Dynamic Caller ID
    • User Resources
    • Sales and Marketing
    • Sales and Marketing
  • Fax Manager
    • Sales and Marketing
  • Integration | Connector Tools
    • User Resources
    • Sales and Marketing
  • Language Pack Editor
    • User Resources
    • Sales and Marketing
  • Migration Application
    • User Resources
    • Sales and Marketing
  • Number Manager
    • Sales and Marketing
    • User Resources
  • Operator Console
    • User Resources
    • Sales and Marketing
  • Operator Console Pro
    • User Resources
    • Sales and Marketing
  • PBX Connector
    • User Resources
    • Sales and Marketing
  • Pivot
    • User Resources
    • Sales and Marketing
  • Porting Manager
    • User Resources
    • Sales and Marketing
  • Reseller Reporting
    • Sales and Marketing
  • Smart PBX
    • User Resources
    • Video Tutorials
    • Sales and Marketing
  • T-Mobile
    • User Resources
    • Sales and Marketing
  • User Portal
    • User Resources
    • Sales and Marketing
  • Voicemail Manager
    • Sales and Marketing
  • WebHooks
    • Sales and Marketing
  • Websockets
    • Sales and Marketing
  • Zapier
    • User Resources
    • Sales and Marketing
  • General
    • How To Docs
    • General Notes

Calendars

  • Open Source Calendar
  • General Announcements
  • Industry Events

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 1 result

  1. A question was posed about how to set an offnet resource to match more than one regex pattern match in the rules[ ] array. There are 2 methods to achieve this behavior. Both (as far as I know) are acceptable, and vary only in readability. When viewing a carrier document in the offnet database in couch, you'll notice there is an array element for "rules". In the world of regular expressions, capture groups are separated by a pipe "|". So if you're looking for one regular expression to match more than one string, you can use the method listed below. In my example, I want this carrier to match a specific number in Italy, and also any calls to the Netherlands, country code 31. In order to match, the number must be exactly "+390805345208", OR +31 followed by at least 9 digits. "rules": [ "^\\+(390805345208)$|^\\+((31)\\d{9,})$" ] Looking above, this may be hard for some people to read, so it can also be written as 2 individual expressions because the rules element is an array: "rules": [ "^\\+(390805345208)$", "^\\+((31)\\d{9,})$" ]
×
×
  • Create New...