Once the VX Unified Communications Wizard is complete, the VX node is ready to place calls. The following configuration screens depict the configurations which are configured by the wizard to allow bidirectional calls between the PBX or Central Office and Microsoft Office Communications Server 2007. If additional customization of the dialing plan for additional functionality is required, necessary changes need to be configured in the following fields.
ISDN / SIP Port Configuration
The wizard configures the T1/E1 ports to basic ISDN settings. These can be further refined using the Chassis link in the VXbuilder Directory tree. In this configuration step, the following settings are configured:
- Port Type
- Assigned Trunk Group
- Number of Channels
- Channel Profile
- Line Type
- Audio Law
Trunk groups configuration allows certain instruction for calls which will be held under one physical or a virtual connection. For instance, while a trunk group is configured and assigned to one particular physical connection to a private ISDN port, another can be configured and applied to another physical connection to public ISDN or to a virtual connection to another IP network.
For a PBX - VX - OCS integration, two trunk groups need to be configured; one for physical ISDN connection and another for virtual IP connection to Mediation Server.
The following two screens show the basic required trunk group configuration.
- ISDN Trunk Group configuration in Telephony > Trunk Groups in the VXbuilder Directory tree.
- SIP Trunk Group configuration in Telephony > Trunk Groups in VXbuilder Directory tree.
Call Routing table(s) are used for matching and manipulating the called number with VX specific translation rules, as well as defining its next destination. More detailed information about Call Routing setup and input / output number formatting can be found in the VX User Guide. For the PBX - VX - OCS integration point of view, two call routes are needed for incoming and outgoing calls:
- Two entries in ISDN-to-SIP Call Routing table in Call Routing in VXbuilder Directory tree.
- Two entries in SIP-to-ISDN Call Routing table in Call Routing in VXbuilder Directory tree.
Calling Number/Name Translation
As specified in the VX User Guide, the Calling Number and Calling Name translation tables are similar to the call routing tables except that they do not actually alter the route taken by a call. Their sole purpose is to alter the CALLING number as the call passes through VX.
The CALLED number (the identifier of the telephone this call is trying to reach) is used for selection in the call routing tables and is potentially altered by the selected call routing entry (via the `output' field). The CALLING number (the identifier of the telephone this call originated from) is used for selection in the Calling Number Translation tables and is altered by a matched entry in those tables. This has no effect on routing. Both CALLING and CALLED number translation follow the same regular expressions rules.
Calling number translation tables are invoked for both the inbound trunk-group and the outbound trunk-group. CALLING name translation uses regular expressions. PBX - VX - OCS integration needs the following two Calling Number/Name Translation tables in Calling Number/Name Translation in the VXbuilder Directory tree.
VX Unified Communications Wizard configures the following codec settings in Media Classes in VXbuilder Directory tree. More detailed information about Media Class configuration is described in the Managing Media Classes and Media Class Table topics.
OCS Mediation Server Status Using SIP Options Messages
VX node needs to know how to reach to its peer(s) in the network. Steps to setup a Peer Table are defined in the VXbuilder Installation and User Guide.
OCS integration requires a Mediation Server to be configured as a SIP-OPTION Peer on the VX node. This is configured by VX Unified Communications Wizard in Networking > Peer Table in the VXbuilder Directory tree.