Tips? I've created a Permission called 'Restricted'. I created a custom Dialing Plan, requiring the use of '555' for PSTN prefix and 7 digits (just trying local for now), and applying the suffix number only for routing to the gateway.
I define the user 767 with the permission of 'Restricted', assign a polycom phone with no dial plan on the phone (to eliminate any spurious issues). Send profiles, restart required services. Dial the number, prefixed by the new pstn prefix, and get a rapid busy. sipXproxy log shows the following for this call: SipXProxy:"EnforceAuthRules[400_authrules]::authorizeAndModify call ' [email protected]' requires 'LocalDialing' Local Dialing plan is required for the Local dialing plan on sipx, and requires pstn prefix '9' for a match, unlike the Restricted dialing plan which requires 555. Why isn't Restricted being matched? Philippe On Mon, Sep 12, 2011 at 2:00 PM, Philippe Laurent <[email protected]> wrote: > This was my first approach, but despite using a different pstn prefix (and > custom permissions), it still wanted to match up the standard dial plans > (evidenced by tailing the sipXproxy log). I'll nuke the changes and start > from scratch again using this strategy. > > > On Mon, Sep 12, 2011 at 1:50 PM, Tony Graziano < > [email protected]> wrote: > >> i would remove all permissions except internal from the user account, >> create a new dial plan with a customer permission and apply it. authcodes is >> too hard because you would have to create too many and thats a lot of >> maintenance. you have to link the custom perission with the custom dialplan >> and the user has to know the secret sauce ingredient to make it work. >> >> >> On Mon, Sep 12, 2011 at 1:42 PM, Josh Patten <[email protected]> wrote: >> >>> Why wouldn't authorization codes work for you? >>> >>> On Mon, Sep 12, 2011 at 12:40 PM, Philippe Laurent <[email protected]>wrote: >>> >>>> A 'private' phone we have in our MFG environment is potentially >>>> accessible by anyone, especially after-hours, and we would like to limit >>>> outbound dialing to only a few folks. >>>> >>>> What's the best way to tackle this? I've tried using different outbound >>>> dialing rules with permissions and a different pstn prefix, but that failed >>>> miserably. It doesn't look like Authorization Codes in sipX is the right >>>> application either. Any input on how ya'll may have tackled this issue? >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> >>> >>> -- >>> Josh Patten >>> eZuce >>> Solutions Architect >>> O.978-296-1005 X2050 >>> M.979-574-5699 >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> <http://support.myitdepartment.net>Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
