Feature for outbound route

Hi to every one,

A nice feature to have could be to create an outbound route based on the caller extension, or range of extension.

If this parameter stay empty, it works like we have now.
If we specify an extension, this extension will always take this route for outgoing call.
If we specify a range (could be with a wilcard like *) all extension in that rage will always take this route for outgoing call.

Thank you very much.

This is an existing feature request, see http://freepbx.org/trac/ticket/461

dgi wrote:

[quote] Hi to every one,

A nice feature to have could be to create an outbound route based on the caller extension, or range of extension.

If this parameter stay empty, it works like we have now.
If we specify an extension, this extension will always take this route for outgoing call.
If we specify a range (could be with a wilcard like *) all extension in that rage will always take this route for outgoing call.

Thank you very much.


Daniel G.
Sys Eng.
www.biss-web.com


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

[/quote]


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


Amportal-devel mailing list
[email protected]orge.net
https://lists.sourceforge.net/lists/listinfo/amportal-devel

Post generated using Mail2Forum (http://www.mail2forum.com)

I see the existing feature request and it is exactly what I am looking for as well. However looking over it I’m not quite clear on it’s status. Is this something expected in 2.2 or is it still just a twinkle in someone’s eye? I ask because if it’s going to be out soon then I’ll just wait patiently but if not then I need to get busy hacking something together for my own purposes.

I am not too sure how quick it would be to hack things to make it work but I have been trying to do something similar by just changing extensions_additional.conf

If I change
include => outrt-002-interroute-custom
exten => _00.,1,Macro(dialout-trunk,2,${EXTEN},)
exten => _00.,n,Macro(outisbusy,)

to
include => outrt-002-interroute-custom
exten => _00./_20[5-9]X,1,Macro(dialout-trunk,2,${EXTEN},)
exten => _00./_20[5-9]X,n,Macro(outisbusy,)

this seems to only allow callerids from 2050-2099 to access international numbers.

I don’t know how the Dial Pattern section of the web page gets to the conf file but I presume that a little change to the web pages might be all that is required? Also I am not sure about side effects but I hope that someone with more experiance can tell me if this makes sense or not.

Hmm, my extensions_addtional looks like:

[outrt-002-outside]
include => outrt-002-outside-custom
exten => _9.,1,Macro(dialout-trunk,2,${EXTEN:1},)
exten => _9.,n,Macro(dialout-trunk,3,${EXTEN:1},)
exten => _9.,n,Macro(outisbusy,)

I think what I may do is add the following to extension_custom:

[outrt-002-interroute-custom]
exten => _9./_2190,1,Macro(dialout-trunk,3,${EXTEN:1},)
exten => _9./_2190,n,Macro(outisbusy,)

I’m guessing that this would cause extension 2190 to use trunk 3 instead of trunk 2. Thoughts? It would still be kind of a pain to setup on any sort of scale, but at least this way I could manually go in and prevent the fax machines from using the VoIP provider.