Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-1862

Processing by ZAP channel prevents DID / CLI based routing (proposed reworking)

    XMLWordPrintable

    Details

      Description

      With a TDM400 card (wctdm) the incoming DID number is not available via signalling. It is however fixed by which DEL is plugged in.

      A Zap inbound route for a FreePBX is processed before CLI / DID routing, leading to not being able to handle these lines with the flexibility one would desire, eg special handling for some recognised CLIs

      I propose a change to
      the Zap channel handling (for TDM400 and any related cards) to only set the DID associated with the line -- ie generate

      [macro-from-zaptel-1]

      _.,1,set(DID=441234654321)

      ; NB one should set ENUM compatible DID to simplify processing elsewhere

      ; end macro-from-zaptel-1

      Rather than the current routing macro

      This will then fall through to the general CLI/DID processing where the full call processing functionality can be applied to route the call.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                andrewknots andrewknots
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.