Custom context module?

[killmasta93]

Hi I was wondering if theres a mirror somewhere for the version 2.11.0 Whats odd is that i have it installed the version 0.3.3 and shows me this array on the outbound and internal dial plans while on another elastix machine has it on version 2.11.0 and works fine to block extensions to use the trunk.

Thank you

 

[soborno]

I put it in my G-Drive some time ago, hope can be useful for you:
https://drive.google.com/file/d/0B06BVr ... VfbDg/view

Regards,
Claudio

 

[killmasta93]

THANK YOU SO MUCHHH LIFE SAVER

 

[killmasta93]

hey just a quick question any idea why it shows ? after I upload then went to local modules and clicked on install then shows me the confirmation screen and as soon i click install it shows that popup when usually it shows that it installed correctly.

No direct script access allowed


Thank you

 

[soborno]

Hi,

No clue, never saw it.
But have in mind custom context is not being updated so the time in which it will stop working will come...

Regards,
Claudio

 

[killmasta93]

Hi,
Thank you again i think its because the person before put an elastix version old. Because on another elastix works flawless but thank you again

 

[killmasta93]

Hi,
One for question, so is there another way possible to make the ext (302) to only be able to call another ext but block that ext (302) the use to make outbound calls using the trunk?

With custom context I was able to do that but just curious is there another way also?


Thank you again

 

[soborno]

Well,

You have for instance, Extensions Routing module (a paid one if I recall it correctly) or you can dive more into asterisk and see how contexts and dial patterns with outbound routes really works.

Regards,
Claudio

 

[killmasta93]

Hi,
Thank you so much for the reply I will try it out and see how it works

Thank you

 

[Bob1]

killmasta93,

As you asked, is there a way to block 302 from making outbound calls but still dial extensions.
If your need is simple like this (e.g. you only have a few extensions with restrictions)....

What you can do is in outbound routes, setup a route called NoOutboundCalls, place it at the top of the routes.

Under dial plans that will use this route

prepend prefix matchpattern CallerID
{Blank}....{Blank}.....{.}...............{302} (note that is a full stop under match pattern and brackets not required)

Finally point it to a dummy trunk
either make a SIP Trunk with no information in it (e.g. dont set host ip or password etc) or as some do, especially if they are not using the Dahdi trunk (e.g. they do not have physical lines) point it to Dahdi/G0

What will happen is that when 302 tries to dial an external number, it will end up in dead space, however dialling internal extensions is not affected (as it does not use the outbound routes for this function

In use at a lot of locations particularly for a Public Area phone where they don't want anyone to dial external numbers.

Hope this helps

Regards

Bob