locked
Policy, Usage records, Routes RRS feed

  • Question

  • As a good PBX we must assess the call by policy and permit/deny route the call.
     
    Our policy includes a set of rules. Rules are prioritized and executed in the “first to last” order. Each rule includes reference to a previously defined route. Each rule includes conditions. First passed rule routes the call to the designated destination. First failed rule deny the call.

    For example, rule_5 includes condition +1хххх and route to the VoIP gateway AudioCodes MP-114.

    If a user calls number +12345, his call meets the rule_5 condition and is routed to AudioCodes MP-114.

    It's just similar to MS ISA 2004/2006 and clear to understand.
     


    But I partially don’t understand OCS routing architecture.

     

    I see the routing architecture is route-centric but I don't understand the real purpose of the Usage Records. 

    Thursday, July 5, 2007 12:34 PM

Answers

  • From the Voice Planning and Deployment guide:

     

    Planning phone usage records consists mainly of listing all the call permissions that are currently in force in your organization, from the CEO down to temporary workers, consultants, and contingent staff. This process also provides an opportunity to re-examine existing permissions and revise them if desired. You can create phone usage records only for those permissions that apply to your anticipated Enterprise Voice users, but a better long-range solution might be to simply create phone usage records for all permissions regardless of whether some may not currently apply to the group of users to be enabled for Enterprise Voice. If permissions change or new users with different permissions are added, you will have already created the required phone usage records.

    Table 6 shows a typical phone usage table:

    Table 6. Phone Usage Records   

    Phone Attribute

    Description

    Local

    Local calls

    Long-Distance

    Long distance calls

    International

    International calls

    Delhi

    Delhi full-time employees

    Redmond

    Redmond full-time employees

    RedmondTemps

    Redmond temporary employees

    Zurich

    Zurich full-time employees

     

    By themselves, phone usage records don’t do anything. For them to work, you must associate them with:

    §  Voice policies, which are assigned to users, and

    §  Routes, which are assigned to phone numbers.

    The following two topics describe voice policies and routes. For information on how to create and configure them, see Configure Outbound Dialing and Routing.

    Friday, July 6, 2007 9:56 PM

All replies

  • From the Voice Planning and Deployment guide:

     

    Planning phone usage records consists mainly of listing all the call permissions that are currently in force in your organization, from the CEO down to temporary workers, consultants, and contingent staff. This process also provides an opportunity to re-examine existing permissions and revise them if desired. You can create phone usage records only for those permissions that apply to your anticipated Enterprise Voice users, but a better long-range solution might be to simply create phone usage records for all permissions regardless of whether some may not currently apply to the group of users to be enabled for Enterprise Voice. If permissions change or new users with different permissions are added, you will have already created the required phone usage records.

    Table 6 shows a typical phone usage table:

    Table 6. Phone Usage Records   

    Phone Attribute

    Description

    Local

    Local calls

    Long-Distance

    Long distance calls

    International

    International calls

    Delhi

    Delhi full-time employees

    Redmond

    Redmond full-time employees

    RedmondTemps

    Redmond temporary employees

    Zurich

    Zurich full-time employees

     

    By themselves, phone usage records don’t do anything. For them to work, you must associate them with:

    §  Voice policies, which are assigned to users, and

    §  Routes, which are assigned to phone numbers.

    The following two topics describe voice policies and routes. For information on how to create and configure them, see Configure Outbound Dialing and Routing.

    Friday, July 6, 2007 9:56 PM
  • It's a really bad architecture decision.

     

    IMHO

    Tuesday, July 10, 2007 10:24 AM
  • I would love to have any feedback you might have to improve the product. I will produce a report and give it to the product group.
    Friday, July 13, 2007 10:55 PM