Welcome
Guest
FAQ Forum Developers Sign In

Obtaining the Circuit Telephony Connector

Last updated:

As soon as the customer places an order for the Circuit Universal or Advanced Telephony Connectors to be deployed on premise, the Sales Representative from Unify or the Channel Partner who received the order, will meet with the customer to proceed with the implementation.

Prerequisites:
  • The customer is already a Circuit customer with several active Circuit users without a Circuit Universal or Advanced Telephony Connector.

  • The customer who requests the Advanced Telephony Connector already has an Unify OpenScape Voice (V8R1 or later) or Unify OpenScape 4000 (V7R2 or later).

  1. A consultant meets with the customer to clarify:
    1. Expected usage of Circuit (i.e., to determine bandwidth requirements). This will include topics like end-user behavior and usage of features that might impact bandwidth and quality of service and security-related expectations (e.g., for encryption).

    2. Determine the available bandwidth and compare it to the expected QoS requirements.

    3. Determine performance requirements.

    4. If the customer already has an OpenScape SBC, then determine whether it can be used as Telephony Connector (pUTC or ATC).

    5. Discuss with the customer their security policies and explain any required changes.

    6. Determine the current software versions of OpenScape SBC (if present), OpenScape Voice or OpenScape 4000 (for customers interested in ATC) and if software upgrade is needed.

    7. For customers interested in pUTC, discuss with customers' representatives and his potential 3rd party PBX service partner their integration needs.

    8. Identify the required human resources needed from the customer side and available time windows.

  2. A consultant decides if there is a need:
    1. to add a new OpenScape SBC

    2. for additional bandwidth (i.e., trunks or internal bandwidth)

    3. to upgrade the OpenScape SBC or OpenScape Solution for compatibility reasons

    4. to change security configurations.

  3. After the meeting, a project plan is proposed, including milestones, Unify and Customer resources as well as a time plan.
  4. The Sales Representative from Unify or the Channel Partner, who has received the order, prepares the offer to the customer with a project plan and an SOW that includes the following:
    1. a new OpenScape SBC (if required)

    2. additional capacity that might be required (e.g., for SIP trunks)

    3. update or upgrades to the OpenScape SBC or OpenScape Solution (if required)

    4. service work for the OpenScape SBC installation and configuration

    5. service work for the PBX (if it is a Unify PBX)

    6. offer for a mass rollout (optional)

    7. offer for end-user enabling or training (optional).

  5. Once the customer receives the SOW:
    1. The customer orders the OpenScape SBC (if needed).
    2. Maintenance window(s) are scheduled for installs or upgrades. This requires synchronization between Circuit, SBC and PBX teams.
    3. The OpenScape SBC is installed (if needed) or upgraded to the required version.
      • SIP trunks are installed.

      • Arrangements are made for the customer to perform firewall and security configuration as needed.

    4. The ATC or pUTC Client in the OpenScape SBC is configured and:
      • The license from CLS is fetched.

      • The SIP trunks are set up, as necessary.

      • Project specific information is documented.

    5. Any necessary configuration work in the Circuit Cloud and PBX is performed.
    6. PBX is configured for seamless interworking with the Telephony Connector (Call number routing, dial information for outgoing calls, CLIP, etc).
    7. Acceptance testing is conducted and:
      • The Customer Domain Administrator must administrate first test users (in Circuit and on PBX).

      • Tests are performed to verify the pUTC or ATC functionality.

  6. Acceptance criteria are met and the customer signs off.

2 people found this useful.
Me too / Not at all