Open Source Training Seminar FreePBX Paid Support

Ticket #1864 (closed Feature Requests: fixed)

Opened 1 year ago

Last modified 1 month ago

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

Reported by: andrewknots Assigned to:
Priority: major Milestone: 2.5
Component: Core - Trunks/Routing Version: 2.4-branch
Keywords: Zap Inbound Routes Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

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.

Change History

07/12/08 23:09:07 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation set to Confirmed.
  • resolution set to fixed.
  • version changed from 2.2.1 to 2.4-branch.
  • milestone changed from 4.0 to 2.5.

this was addressed in 2.4

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads