AiPBX

Inbound routes (DIDs)

An inbound route sends calls for a DID (the called number the trunk delivers) to a destination such as an extension, ring group, queue, IVR, IVR data step, time condition, announcement, conference or fax. Optional per route: call recording and the channel language.

Matching

• The DID is compared with the number the trunk sends, after the trunk’s DID trimming. Define routes in exactly that format — if a NEC system sends 9391, the route is 9391, not 19391.
• Pattern Matching (Wildcards): Inbound routes support standard Asterisk dialplan patterns starting with an underscore _:
  • X: Matches any single digit from 0 to 9 (e.g., _0850XXXXXXX).
  • Z: Matches any single digit from 1 to 9.
  • N: Matches any single digit from 2 to 9.
  • .: Matches one or more remaining characters (e.g., _905XXXXXXXXX).
  • !: Matches zero or more remaining characters.
• Dynamic DID Routing (__did__): When configuring an inbound route for a block of numbers, destination Extension → Dialed Number (__did__) dynamically matches the dialed DID suffix to existing local extensions.
• A call from a trunk tries exact inbound routes first, then pattern routes; with transit routing enabled it then tries the trunk’s outbound route group and local extensions; unmatched calls fall through to from-trunk-notfound (which also checks extension number length fallbacks) or end with congestion.
• To see what a trunk sends, capture SIP (see Troubleshooting) and read the number in the INVITE line.

Fax DIDs

A route with destination Fax answers with fax detection and stores the document for the department mapped to that DID (Fax Settings). The department mapping uses the same number as the route; when you renumber fax DIDs, update both, otherwise faxes are received but not delivered to the right inbox.

This site is open source. Improve this page.