>Basically, if the number matched a dial rule but you didn't have the correct permission, then SipXecs would drop the call instead of checking >to see if there was another rule that matched the number. I didn't think it had been fixed.
True. It has not been fixed yet. It will be in 4.02. But we are not in that situation. When you perform an internal call you pass both by the diaplan and directly to the destination extension because it belongs to the same sip domain. Its something like a fork. I tried it. A minor issue is that the telephone will ring for less than half a second before the autoattendant answer. Heros Da: Keith Gearty [mailto:[email protected]] Inviato: venerdì 10 luglio 2009 13.04 A: heros Cc: 'Paul Scheepens'; [email protected] Oggetto: Re: [sipx-users] R: R: Multitenanancy heros wrote: More I see another workaround. Create a permission no_customer_1 à assign this permission to customer 2 with extension 500 Create a permission no_customer_2 à assign this permission to customer1 with extension 600 Create a rule in dialplan with permission no_customer_1. This rule forward calls matching 5XX to an autoattendant that say you are not allowed to dial this number Create a rule in dialplan with permission no_customer_2. This rule forward calls matching 6XX call to autoattendant that say you are not allowed to dial this number Have you actually tried that? The last I heard (3.10.2) you couldn't do that sort of thing because of limitations in the SipXecs dial plan implementation. Basically, if the number matched a dial rule but you didn't have the correct permission, then SipXecs would drop the call instead of checking to see if there was another rule that matched the number. I didn't think it had been fixed. Keith.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
