Why is it even looking at the q931 setup, i didnt tell it to look at
that. I only said to look at LRQ;ARQ (disregarding aliasauth since that
is only for registration and i am having problems with calls being
refused). them manual said prefixauth doesnt work on setup messages.David Winter Senior Network Engineer Planet-Telecom, Inc. Tampa FL (813)901-5182 Office (813)864-3162 Direct (813)817-4204 Mobile (813)881-9762 Fax ------------------------------------------ AIM: mobofool ICQ: 3563403 MSN: dwinter@xxxxxx Y!: vt_fool Zygmuntowicz Michal wrote: In this setup, you can ommit the default rule - it is required only if all preceeding modules are set as optional. You should look at auth rules both "horizontally" and "vertically" - each event is passed down through all rules. So, in case of RRQ is is first processed by AliasAuth, then (if AliasAuth cannot accept or reject the request) by PrefixAuth (which just does nothing and passes control to the next module), and finally by the default rules, which rejects all requests. So let's see what happens if Q.931 Setup event is processed: AliasAuth does nothing and passes control to the PrefixAuth, the PrefixAuth passes control to the default module, the default module rejects the request (the call). One important thing is that the processing is UNCONDITIONALLY aborted, if any module REJECTS the request - then the final result is always REJECT, no matter how would remaining rules decided. So even if you have default=allow and AliasAuth rejects RRQ or PrefixAuth rejects LRQ or ARQ, then the request is always rejected. ----- Original Message ----- From: "david winter" <dwinter@xxxxxxxxxxxxxxxxxx> Sent: Wednesday, August 04, 2004 9:16 PM |
