Emerging Technology

Expand all | Collapse all

Avaya Workplaces Dialing Rules

  • 1.  Avaya Workplaces Dialing Rules

    Posted 17 days ago

    I can't seem to find a good document on how this is managed and setup, and we are testing this manually at first and the fields are pretty ambiguous. So does Avaya Workplaces Dialing Rules support the following scenarios in our Local Dialing plan:

    Having 3 Area Codes that are both Local and Long Distance from us (So 10 digit dial for local, 11 digit dial for long distance)

    A PBX that Spans multiple areas, so we have extensions in different LATAs throughout the state of Nebraska.

    And a WIDE Range of PBX Extension Numbers (Or what Workplaces call's PBX Main Prefix)

    So I am wondering if anyone else has found themselves banging their head on the wall trying to get the Dialing Rules to just "Work" for Workplaces?

    It would be super helpful if Avaya would put out a document explaining in detail each one of the fields of the Dialing Rules (Found Below):

    Thanks,



    ------------------------------
    James Davis
    Lead Voice and Data Engineer
    University of Nebraska Medical Center
    Omaha NE
    ------------------------------


  • 2.  RE: Avaya Workplaces Dialing Rules

    Posted 16 days ago

    We stopped trying to manage dialing (local vs LD) at the endpoint.  This was mostly because we also have locations across multiple area codes and employees coming from different places that wouldn't necessarily know what's local to them in the office.

     

    We uplift anything dialed (starting with the ARS access code – 9 for us) to 11 digits.   So if a customer dials 10 digits, we uplift that in ARS digit-conversion to 11 digits, prepending a 1 and marking the call as fnpa.    This greatly simplified the ARS analysis table.  We used localcallingguide.com to figure out which prefixes in our area codes were local to each of our trunks and route "local" calls out those trunks.  For carriers that want 10-digit for local calls, we use prefix mark 4 in the route-pattern to strip off the 1.

     

    If you want to have a peak/demo, DM me and we can Zoom... err Spaces.

     

     

    Sam Osheroff

    UC Engineer

    UW-IT Infrastructure - Telecom

    University of Washington

    sosherof@uw.edu

    Internal: x16362 Direct: 206.221.6362