[Knowledge sharing] SFB Enterprise voice Getting Started RRS feed

  • General discussion

  • Enterprise Voice

    Enterprise Voice is Microsoft’s software-powered VoIP[1] solution, a SIP[2]-based implementation of IP telephony for the enterprise

    Enterprise Voice work flow


    Enterprise Voice is a full-featured VoIP [1] solution that includes connectivity with PSTN [5] gateways and interoperation with PBX (Private Branch Exchange) installations.

    The Enterprise Voice’s work flow like the following screenshot.

    Mediation server

    The function of mediation:

    Mediation Server provides signaling and media translation between SFB and a media gateway

    • Encrypting and decrypting SRTP [4] on the SFB Server side
    • Translating SIP [2] over TCP (for gateways that do not support TLS) to SIP [2] over mutual TLS
    • Translating media streams between SFB Server and the gateway peer of the Mediation Server
    • Connecting clients that are outside the network to internal ICE components, which enable media traversal of NAT and firewalls

    Collocated with the Front-End Server by default

    Enterprise Voice Management in Control Panel

    • Normalization rule
    • Dial plan
    • Voice Policies
    • PSTN [5] Usage
    • Routes
    • Trunks configuration

    1. Normalization rule

    The function of Normalization rule:

    The process of translating number strings that are entered in various formats into a single standard format (E.164)

    • Provide a consistent reference for reverse number look-up. Reverse number look-up is the process of mapping a user’s number to a corresponding SIP [2] URI
    • Identify and apply phone usage authorization (comparable to traditional “class of service” options) for the calling party.
    • Route calls to the appropriate media gateway

    2. Dial plan

    Dial plan: A set of normalization rules 

    Dial plan can be assigned per user, pool, site, or global

    3.Voice Policies

    Voice Policies can be assigned per user, site, or global

    The function of Voice Policies:

    1. Provides admins with flexibility to control user voice entitlements

    • Call Forwarding
    • Delegation
    • Call Transfer
    • Call Park
    • Simultaneous Ringing
    • Team Call
    • PSTN [5] rerouting
    • Malicious Call Tracing

    2. Control Dialing capabilities (Class of Service) by assigning PSTN [5] Usages

    3. Not only for users but also useful to address Common Area Device requirements. Assign a Voice Policy to a common area phone to prevent misuse and high cost

    4. Call Forwarding & Simultaneous ringing

    • An administrator can associate a set of PSTN [5] usages to specify this call authorization in a voice policy
    • Call authorization types:

    -Voice policy PSTN [5] usages
    -Restrict to SFB users only
    - Custom set of PSTN [5] usages

    4. PSTN [5] Usage

    The function of PSTN [5] Usage:

    1) A PSTN [5] usage record specifies a class of call (such as internal, local, or long distance) that can be made by various users or groups of users in an organization.

    2) By themselves, PSTN [5] usage records do not do anything. For them to work, they must be associated with the following:

    • Voice policies, which are assigned to users.
    • Routes, which are assigned to phone numbers


    The function of Routes:

    1) A voice route associate’s destination phone numbers with one or more PSTN gateways or SIP [2] trunks and one or more PSTN [5] usage records.

    2) PSTN [5] Usages control if a user can use the route

    3) Routes are associated to one or more trunks

    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    • Edited by ForumFAQ Thursday, November 29, 2018 5:29 AM
    Monday, October 8, 2018 8:56 AM

All replies

  • 6. Trunks configuration

    Definition of Trunks configuration

    Trunk configuration settings define the relationship and capabilities between a Mediation Server and the PSTN [5] gateway, an IP-PBX.

    Trunks configuration Settings include:

    • Whether media bypass should be enabled on the trunks.
    • Whether or not secure real-time protocol (SRTP [4]) encryption is required on each trunk.

    Allow for centrally managing number formatting prior to routing to PBX/PSTN [5] for both calling and called number

    • Alice calls +44221234567; based on route translation pattern, called number is formatted to 01144221234567 when using gateway in Redmond
    • Alice’s number +44334455667; based on route translation pattern, calling number is formatted to 5667 when using gateway in Redmond

    Work flow of Voice Routing

    1. Start with User Initiates Call - determine whether the type of the phone is Phone or SIP [2] URI. If the type of the phone is Ph is Phone, go to user=phone (number 2 above). If the type of the phone is SIP [2] URI, directly inbound Routing (internal) Routing), from the internal route directly to the corresponding end user (picture number 1 above).
    2. If it is judged that the type of phone is Phone, it is judged whether it is a normal call or an emergency call. If it is an emergency call, skip the Reverse Number Lookup (the process of reverse lookup, serial number 10) directly to the location policy (via the PSTN [5] in the location policy) Usage , where PSTN [5] usage contains associated routes and voice policies. After applying the corresponding policies, the emergency call is routed out to mediation server serial number 8, and then to the PSTN [5] gateway, and finally to the external terminal user serial number 9).
    3. If it is judged that it is not an emergency call, go through the normal phone call process and determine which Normalization Rule is in Global (No. 5). If it follows the internal Normalization rule, the phone is an internal call. Perform reverse number lookup, match the corresponding number (serial number 6), perform inbound routing, and route to the internal client.
    4. If the judgment is not emergency call, the matching is not the internal normalization rule, and the external normalization rule does not match, there will be 404: No matching rule (number 4) in the log; if it matches the external normalization rule, then proceed Reverse Number lookup (inverse query, in fact, query the internal Address Book), if the query does not find No match in Address Book, then the Voice Policy (serial number 7), associated with the corresponding routes, routed to the Mediation server, by Mediation The server communicates with the PSTN [5]  gateways, and then the gateways goes to the external terminal phone (serial number 8-9).

    Relationship of Voice policy, PSTN [5] Usages,Routes

    For example:

    If you configure those users who can make internal calls, which users can make domestic calls, and which users can make calls abroad, you can assign a voice policy to each user through Voice policies, including PSTN [5]  Usages (internal, local, long distance) ,PSTN [5] Usage can include a variety of routes, the actual PSTN [5] usage is achieved through different Routes - restricting different calls to different users.

    [1] Voice over Internet Protocol (VoIP)

    [2] Session Initiation Protocol (SIP) 

    [3] Real-Time Transport Protocol (RTP)

    [4] Secure Real-time Transport Protocol (SRTP)

    [5] Public Switched Telephone Network (PSTN)

    Hope the above information can be helpful. If you need further assistance on this, feel free to post a question with all details to our forum (via clicking “Ask a question” at the top left of this page), we’ll look further into the issue and try our best to help you.

    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    • Edited by ForumFAQ Thursday, November 29, 2018 5:30 AM format
    Monday, October 8, 2018 8:59 AM