Frustrated!! Custom Contexts not doing what I want..

[w1ve]

Latest PIAF, Asterisk 1.4.21

I know I've done this before, and that's why it is driving me crazy.

I want to set up a demo, which is essentially multi-tennant.

The only issue remaining is I want a particular extension to go out a particular trunk, so that the caller ID appears correct.

I' m using custom contexts v0.3.4 (even though it says v0.3.2 in the UI!)

I create a custom context. I set everything to Deny except for the outbound route I want enabled.

Of course, the extension's context is set to the custom context created.

Every time I call from the extension the call goes to the fail destination.

If I enable ALL OUTBOUND ROUTES, it of course it picks the 1st route, which is wrong.

Ugh! What has changed or what have I forgotten??

 

[raphou]

Try enable all routes but change the order in custom context and put the route you want to use in the first place.

I don't understand because I've the same setup for me and it works well

 

[w1ve]

Try enable all routes but change the order in custom context and put the route you want to use in the first place.

I don't understand because I've the same setup for me and it works well

Hmmm -- I have enable all routes, prority 50, then in outbound routes, the route I want this context to work with set to 50, Allow, and my other routes set to 51 Deny and 52 Deny. It still dials the 1st route in my Outbound Routes list, no matter what.

 

[w1ve]

Still no go

Try enable all routes but change the order in custom context and put the route you want to use in the first place.

I don't understand because I've the same setup for me and it works well

Hmmm -- I have enable all routes, prority 50, then in outbound routes, the route I want this context to work with set to 50, Allow, and my other routes set to 51 Deny and 52 Deny. It still dials the 1st route in my Outbound Routes list, no matter what.

 

[matka]

Hmmm -- I have enable all routes, prority 50, then in outbound routes, the route I want this context to work with set to 50, Allow, and my other routes set to 51 Deny and 52 Deny. It still dials the 1st route in my Outbound Routes list, no matter what.

Had similar problem, deny "Entire Basic Internal dialplan".

 

[w1ve]

I am denying "Entire Basic Internal Dialplain"

ugh! This is why it's frustrating.

 

[matka]

Sorry to hear that. I installed this module today, however it is different version than yours - 0.3.3 from http://aussievoip.com/wiki/freePBX-CustomContexts. It does work as expected, let me list the steps, maybe there is some detail that you did differently:

- create 2 outbound routes
- create 2 custom contexts, initaly enable ALL, then deny "Entire Basic Internal Dialplan", then "Deny ALL Outbound Routes", then enable 1 of the 2 outbound routes created
- modify extensions to use custom contexts
- save all and reload

My version says 0.3.3 on the menu. Maybe you should try this version ?

George

 

[w1ve]

I'll try it! Thanks!

 

[w1ve]

Still no go...

Hi George,

Thanks for all the help. Still no go. But I'm not quite getting the results you have stated.

I downloaded the script from aussievoip. Even after updating to it, the LINK at the bottom of the custom contexts page (which points to aussivoip) Still says 0.3.2!!

Anyway, in my situation I have the default internal context and one custom context. I do not believe everything has to be custom, does it? It never had to be in the past.

Anyway, I created a new custom context, did as you said.

I made the fail mode "CONGESTION". As soon as I attempt to dial from the extension, I it fails through to congestion.

Gerry

Sorry to hear that. I installed this module today, however it is different version than yours - 0.3.3 from http://aussievoip.com/wiki/freePBX-CustomContexts. It does work as expected, let me list the steps, maybe there is some detail that you did differently:

- create 2 outbound routes
- create 2 custom contexts, initaly enable ALL, then deny "Entire Basic Internal Dialplan", then "Deny ALL Outbound Routes", then enable 1 of the 2 outbound routes created
- modify extensions to use custom contexts
- save all and reload

My version says 0.3.3 on the menu. Maybe you should try this version ?

George

 

[edisoninfo]

I too have used this module several times without any problems. I just setup two new piaf 1.3 boxes and cc does not work on either one. My problems are a little different tho. I can get it to dial out whichever trunk I want, but, non of the *xx commands work anymore. Watching the CLI I can see it trying to dial *98 for example out the trunk instead of doing the voicemail path.

Edit:
Ok. I resolved my issues. Everything works now. It was the Dial Patterns in the outbound routes.

 

[w1ve]

Help, Please!

I cannot seem to get custom contexts to work anymore.

I've made my pbx very simple.

- default context
- One custom context

Two trunks: each with different caller id.

In the custom context, I allow all, then deny entire internal dialplan, deny all outbound, then allow only the outbound I want for that context.

I pulling my hair out on this one... Need to demo Thursday.

Any one else have a suggestion?

 

[w1ve]

Working Fine...

It was a dumb mistake. I kept thinking I was having a custom context issue -- it was really a pattern matching problem on the outgoing trunk.

PIAF/FREEPBX is SOLID.. It's the pilot that has the issues!

Thanks for all the suggestions.

Gerry