Or you could use the domain feature, where you set a default context
per domain, that overrides the one in the general section.
/Olle
Olle,
That's the point. The SIP context precedence right now is default, peer,
domain. That precedence doesn't make sense.
The context precedence should
It took me a while to understand what you were saying ... more clarity
to your emails!
I was trying to be clear and complete. So many times if you forget to mention
1 thing or another, or are too long, you get non-helpful comments back. But I
will try harder. Right now Asterisk is as
Yup, one way to guarantee the code in the Asterisk base is to spend a
few months chasing the bug tracker.
I think this feature was simply implemented without taking the users
contexts in mind.
That's my judgment though but I agree with you it's wrong.
Martin
On Sat, Apr 4, 2009 at 11:26 AM,
Or you could use the domain feature, where you set a default context
per domain, that overrides the one in the general section.
/Olle
3 apr 2009 kl. 07.08 skrev Martin:
Hi,
It took me a while to understand what you were saying ... more clarity
to your emails!
I see where the code says
He's already using domain feature but its logic is to override the
user's context even if it was predefined in sip.conf
Martin
On Fri, Apr 3, 2009 at 3:14 AM, Olle E. Johansson o...@edvina.net wrote:
Or you could use the domain feature, where you set a default context
per domain, that
Hi,
It took me a while to understand what you were saying ... more clarity
to your emails!
I see where the code says If we have a context defined, overwrite
the original context and after consideration
I agree with you ... the only problem is that even if you don't define
the context=blah for
