Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <1269533383.2149.451.ca...@localhost> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <43875> Message-ID: <[email protected]>
Thanks for the feedback. I'm not sure that what I want to do works in 4.0.4. To better describe: I want to block all directory assistance calls. I can easily block 411, 800555, 877555, etc, but I want to block it for any area code, as Scott described. To block specific area codes, I just added, for example, 800555 to the list of "area codes" in the "Restricted" Dial Plan that came with 4.0.4. Since I did not give my test users access to the "900 Dialing" permission that is assigned to this dial plan they were given a "403 forbidden" message which is sufficient for my application. If I try to add XXX5551212 to the list of "900" area codes, the area code list gets flagged as an error in the web GUI. I then tried to create a new Dial Plan Dial Rule. This time I again said the permissions was "900 Dialing" (which is not granted to the user), the PSTN prefix is 9, and the Long Distance prefix is "1XXX5551212". I left the area code field blank. I activated the rule and move it up above the working Restricted rule for 900 calls. I tried dialing either 916305551212 or 16305551212 and the call was not blocked, it went through. Am I missing something? My dial plan rules do not have a redirect option, so maybe this kind of pattern matching only works in the 4.1.7 release. By the way, the reason I want to block all DA calls is because my ITSP charges $1 for each such call, including 8005551212. _______________________________________________ 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/
