Open Source Training Seminar FreePBX Paid Support

Ticket #1025 (closed Feature Requests: duplicate)

Opened 2 years ago

Last modified 1 month ago

channel routing

Reported by: user469 Assigned to:
Priority: minor Milestone: 4.0
Component: Core Version:
Keywords: routing Cc: pat98usb@gmail.com
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

There is a way of doing channel routing with the Web Interface maybe modyfing the core , could be usefull for all channel , Zap , Sip , Iax , to do such things with the GUI .

If possible the GUI should config every channel as group with different context.

# etc/asterisk/zapata.conf

context=from-trunk-1

group=1

context=from-trunk-2

group=2

If possible the GUI should config this with number remapping also. ( +X |X )

# etc/asterisk/extensions.conf

from-trunk-1

; from-trunk-1-to-trunk-2

exten => _X.,1,Dial(ZAP/g2/${EXTEN:1},60)

exten => _X.,2,Hangup

from-trunk-2

; from-trunk-2-to-trunk-1

exten => _X.,1,Dial(ZAP/g1/${EXTEN},60)

exten => _X.,2,Hangup

Thanks

Change History

07/15/06 09:27:56 changed by gregmac

  • status changed from new to closed.
  • resolution set to wontfix.

Please explain in more detail what you're looking for here. Zap groups have no ties to trunks. I also don't see the use of from-trunk-1-to-trunk-2... is this like a DISA or calling-card type application, where calls coming in on trunk 1 go back out on trunk 2?

I'm going to close this pending further input, please provide more details and some rationale to put this into core freepbx.

This ticket would also conflict with changes in #1021.

07/17/06 03:24:38 changed by user469

  • status changed from closed to reopened.
  • resolution deleted.

I'll try to explain it better , with this zapata.conf setup

context=pstn-incoming

group=1

signalling = bri_cpe

channel => 1-2

channel => 4-5

context=pbx-incoming

group=2

signalling = bri_net

channel => 7-8

channel => 10-11

you will have two zap trunks group normally named ZAP/g1 and ZAP/g2 consisting of ZAP channel 1-2-4-5 and 7-8-10-11 , if i want to split it again i can end with four ZAP trunks group named ZAP/g1 to ZAP/g4 consisting of ZAP channel 1-2 , 4-5 , 7-8 and 10-11 , i can have split them further to ZAP/1 to ZAP/11 .

Instead of manual putting the "context=$" id like the GUI to create as many context as the group defined or as many channel defined like for example http://www.freepbx.org/trac/ticket/1021 ! Each trunk should have its own [from-trunk-X] context so we can do trunk-specific modifications.

I'd like also feature as http://www.freepbx.org/trac/ticket/1022 ! type: inbound, outbound, inbound & outbound

Then to have a complete control of the "trunk routing" or "call routing" i'd like to do some number manipulation (inbound) when going form [from-trunk-1] to [from-trunk-2] and another kind of number manipulation (outbound )when coming from [from-trunk-2] going to [from-trunk-1] , if i want the same number manipulation the whole thing can be (bidirectional) [from-trunk-1] < to > [from-trunk-2] .

Thanks

07/24/08 14:00:08 changed by p_lindheimer

  • status changed from reopened to closed.
  • confirmation set to Unreviewed.
  • engine_version changed.
  • svn_rev changed.
  • milestone set to 4.0.
  • resolution set to duplicate.

I think part of this is a duplicate from another ticket to do routing based on trunk, and part of it doesn't seem valid. Marking as a duplicate, if there is still a missing requirement that is not captured elsewhere, then open a new ticket and articulate it. Thanks.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads