Page tree
Skip to end of metadata
Go to start of metadata

Configuring a T1 or E1 Bearer Span (Software 10.5.0 and above)


On the rear of the IMG are ports that are designated to be configured for TDM spans. There are 28 Bearer ports and four Signaling/Timing Spans. The intent of the Signaling Spans was to put Signaling/Timing on these spans and TDM Bearer trunks on the Bearer Spans. Although the intent was to have the four Signaling/Timing Spans used for Signaling, the reality is that all ports Bearer and Signaling can be used for both Signaling and/or Bearer. Signaling can be configured on Bearer Spans and TDM trunks can be configured on Signaling Spans. The procedure below will explain how to configure any offset Signaling/Timing ports and Bearer ports to be used as a Bearer TDM trunk.

When configuring an IMG set up to be used as a T1 system, Bearer Ports 0-27 and Signaling Ports 0-3 can be used.

(28 Bearer + 4 Signaling) * 24 Channels = 768 Channels

When configuring an IMG set up to be used as a E1 system, a combination of bearer ports and signaling ports can be used as long as the sum of the channels equals the number of licensed channels. See examples below.

Example 1

Bearer Ports 0-20 and the Signaling Ports 0-2 can be used. Bearer Ports 21-28 are not used in this configuration.

(21 Bearer Ports + 3 Signaling) * 32 Channels = 768 Channels

Example 2

Bearer Ports 7-27 and the Signaling Ports 0-3 can be used. Bearer Ports 0-6 are not used in this configuration.

(21 Bearer Ports + 3 Signaling) * 32 Channels = 768 Channels 


Prior to creating a TDM Span, an object named Facility must be created in ClientView. The Facility object is created under the Physical IMG object. (Right Click on Physical IMG and select New Facility) From there TDM Spans can be configured through ClientView. For more information on how to configure the Facility Object, see Facility


  • Once the Facility Object has been created, Right-click on the Facility object and select New TDM Spans.  Commit This. A tabbed field named Bearer Spans will get created on the right hand side of ClientView. ClientView will create 28 offsets that are ready to be get configured.
  • Each Bearer span must associate itself with a specific profile. Create a profile by right clicking on IMG EMS and selecting New Profiles. Commit this.
  • Under profiles the user can now select either E1 Profile or T1 Profile. Right Click on the Profiles object and select New T1 Profile or New E1 Profile. The next screen that appears will be the T1 or E1 Profile screen on right portion of ClientView. There will be drop down menus for the user to select from. The user can now select the different properties for the network these spans will be utilized in. Commit these span profiles. (ClientView supports up t0 64 T1 and 64 E1 different profiles).
  • Once the different profiles have been created, they can now be associated with specific spans. There are two ways to do this:
    Method 1: Bearer Spans Pane:
    • Open the Bearer Spans screen in ClientView. The user can select a different profile for each span through use of a drop down list. This has a limitation where only one span can be configured at a time. See screen capture below

    Method 2: Facility Wizard:

    • The Facility Wizard will allow the user to associate multiple spans to a specific profile. To open the Facilty Wizard either Right Click on Bearer Spans and select Facility Wizard or click on the Facility Wizard button in ClientView. A screen like below will appear.

    • Select the profile from the drop down menu.
    • Select the Starting Interface ID from drop down menu.
    • Finally select the span count which is how many spans will use this particular profile. Select the Next button in the wizard.
    • Below is a screen capture after Facility Wizard has completed configuration of Spans 0 - 11 being associated to Profile T1_Profile1

  • At this point spans 0 though 10 are associated with profile T1_Profile1 and should be in service. User can now go and set spans 11- 28 to another profile which was previously created and is in the Profiles list.
  • No labels