Custom Context

[riishkid]

does this work with PIAF

 

[jdaustin]

The custom-context module works with freepbx which is part of PIAF. I have it running on a couple of production machines with the most current FPBX.

 

[MACscr]

The custom context module doesnt work with freepbx 2.4. Since the module is distributed with PIAF, does that meant that someone might actually fix it? =)

 

[tshif]

I doubt it. If you check in the forum at freepbx, they have something very different in mind for the future- and don't embrace this module for several reasons. I have used it in the past, but it truly complicates things far to much for the benefits (to us), and we stopped using it.

 

[MACscr]

Yeah, i personally dont like the road freepbx is going down, so i think im going to look for an alternative. Looking at Voiceone at the moment.

I just dont understand why systems such as freepbx dont think that having the ability to set call routing patterns (incoming and outgoing) by extension or a group of extensions isnt a standard feature of a pbx.

 

[tshif]

Well - its usually a matter of communication. We haven't made our case - is basically why its not in there. I think what they have planned is so huge compared to what most people need. I'm afraid they may be having problems separating the really big installs, from the more normal ones that have more typical needs. I certainly think of this need as typical.

Before you give up though - try communicating. I frequent the forum at freepbx, and I would almost call it "dead" compared to here, and the trix guys place.

In a quiet room, any reasonable voice can be heard. Why not give it a try?

 

[jroper]

tshif is quite right. It is the community that influences the way that projects evolve, and although there has to be someone at the top to make a final decision, it is in their interests to supply the needs of the customer - me and you.

I would suggest that rather than jumping onto another setup, and having to go through the pain of learning another interface, make representation to FreePBX in their suggestions section.

At best your suggestion will be taken on board, and at worst, someone will explain to you why it is the way it is.

Joe

 

[wardmundy]

We use custom contexts all the time with 2.4. What exactly is not working for you??

 

[kenn10]

We use custom contexts all the time with 2.4. What exactly is not working for you??

There was an upgrade on Custom-Contexts and it was released under version 0.3.4, if memory serves me. I am using it with Asterisk 1.4.18 and FPBX 2.4 with no issues. I have remote users whom I force over their own local trunks using this module and appropriate dial plan routing.

Based on discussion on the FreePBX forums, the Custom-Contexts module was from a contributor who has since abandoned it. Other FreePBX users corrected some of the issues and reposted it with the improvements. I don't think this module has been part of the FreePBX core per se but user feedback on the forums there got some action.

I looked at VoiceOne as well and I'm not sure I'd want to climb that learning curve. It looks very comprehensive but also very complex to figure out.

 

[jroper]

Hi

I think I know what you are talking about now.

This is the idea of making different extensions use different routes and trunks based on their context and not on the basis of dialed digits.

This would commonly be used in a multi-tennant environment, so that different accounts can be set up with a voice provider, one for each group of extensions.

There were two modules written to achieve this funtionality from memory, but they were third party modules not supported by FreePBX, one of the modules has not been touched in about 2 years.

There was a bounty up for the FreePBX team to write a PBX with multi tennant capabilities, but do it properly. You would have to enquire of the FPBX team as to the status of this.

Joe

 

[Dakota2004]

Did anyone ever find a way to send different extensions out certain trunks? I have this setup in asterisk@home 2.7, with custom contexts and it works great.

Can anyone help me find a way to make this work in PBX in a Flash 1.2?

Randy

 

[sims]

can somebody here suggest as to what the easiest way to use custom context with PIAF is. i would like to have different extensions use different trunks by default without the need to dial a prefix.

as far as i can tell, my best bet is custom context. however, i would like to avoid doing anything which causes my setup to become customized and not friendly to future PIAF upgrades.

thanks!

 

[kenn10]

Custom-Contexts lets you set specific routes based on the context. You could have a different context for "building1" and "building2" for example. In the setup of custom-contexts, you allow or disallow access to specific outbound routes you have created.

This is not customization per se but the module is no longer being supported except by the community. There is discussion about it on the FreePBX site if you search for it.

I use the module for outbound routing and 911 access based on location in my system as I have two homes supported by one system and those homes are in different States.

As to future PIAF upgrades, this is a FreePBX add-on and not related to the PIAF release. However, who knows if it will be compatible with Asterisk 1.6 unless someone can fix the module when its broken again.

Check out this link for additional info: freepbx.org/support/documentation/m...hird-party-unsupported-modules/customcontexts

 

[sims]

thanks kenn10. is there another, more supported way of achieving what you are doing. i am thinking of a home office where one extension should use a different caller id when it is used to call out and another extension should use the home caller id.

if not, then i guess i will stick to the "prefix-9" to call out using this extension approach for the home office phone (and all prefix-9 calls can go via one trunk).

 

[jmullinix]

There is a hack to do this. Put one phone in the context from-internal and it will use the standard outbound trunk. Put the other phone in a context of say [other-phone]. Then add a little code in extensions_custom.conf that looks like this:

[other-phone]
exten => _nxxxxxxxxx,1,goto(outbound-allroutes,789${EXTEN},1)

Then, at the bottom of your outbound routes create a route called say fromOtherPhone and put this match pattern in it:

789|NXXNXXXXXX

That should do it.

 

[sims]

jmullinix, i will try the hack and report. thanks!

i need to figure out a way to decipher and learn asterisk syntax. the kind that you used. even though PIAF is freepbx based, almost all support stuff online is in the asterisk lingo! any tips on what is the easiest, fastest way to learn this stuff?

 

[superuser]

Any update on this... its 2010 and all these messages are from 08.

Using FreePBX 2.5.2.2

 

[wardmundy]

You're using a module that is not supported by the FreePBX project. One reason is because it hasn't been touched in over 2 years. Don't expect any updates but, if it meets your needs, then proceed at your own risk.

 

[kenn10]

You're using a module that is not supported by the FreePBX project. One reason is because it hasn't been touched in over 2 years. Don't expect any updates but, if it meets your needs, then proceed at your own risk.

Actually, Philippe at FreePBX to attempting to find a programmer to adopt and upgrade this module. It is working now with FreePBX 2.7. We know the module absolutely WILL NOT work with FreePBX 2.8 unless we find someone to adopt the module and update it. We will be taking donations to get it updated once a programmer is secured and an estimate of repairs is known.

The current version of Custom-Contexts is 0.3.5 and there should be a 0.3.6 update for it in the near future which keeps it up to speed with FreePBX 2.7 and the routing changes it brought to the table. Beyond that, it will depend on the generosity of the community to determine whether or not this module will die on the vine.

It is unlikely this module will ever be incorporated into the core of FreePBX. Whether it remains as a 3rd party module depends on the community.

 

[superuser]

Thanks Ward.

Do you cover the 'restrict extensions to a specific trunk' issue anywhere in the voluminous tome that is your website?