this can help u:
SIP.CONF
[1]
host = dynamic
type = friend
language = it
qualify = no
dtmfmode = rfc2833
callgroup = 1
pickupgroup = 1
callerid = "Bruno De Luca 1" 1
secret = 1234
mailbox = 1
context=1
[2]
host = dynamic
type = friend
language = it
qualify = no
dtmfmode = rfc2833
That doesnt really help. As stated in the email you replied to what is
to prevent someone doing say
[1]
exten = 1,1,goto(2,1,1)
or customer A *and* customer B trying to define the same context name,
to use your example lets say they both want to create context '1'.
I want to be able to
, September 23, 2005 11:04 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] context question
They are aware of each other in 2 senses. First you can goto() them. I
wanted to stop the ability of someone to put in a goto() in their
dialplan to a context
On Sat, 2005-09-24 at 09:10 -0400, Alex Vishnev wrote:
I briefly looked thru the code and I don't believe there is a way to
separate the context or really make them independent. I know exactly what
you want to accomplish. I think it could be done with a little trick. For
example, every
Is there any way within asterisk to limit the scope of contexts,
basically to make one context totally unaware of another.
The application I had in mind involved allowing users to create their
own dial plans. To that end I wanted to make it so that a given user
could not call a different users
I may be missing something, but aren't all contexts unaware of each
other be default?
If I do the following
[contexta]
exten = 3200,1,Dial(SIP/3200,5)
[contextb]
exten = 3300,1,Dial(SIP/3300,5)
Each context has a phone and they can't call each other. The are
completely isolated. Unless
They are aware of each other in 2 senses. First you can goto() them. I
wanted to stop the ability of someone to put in a goto() in their
dialplan to a context that is someone elses (think asterisk hosting).
Second naming collissions. I wanted to stop two people from having the
same name and
