Configuring a T1 or E1 Signaling 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 4 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.



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



  1. Once the Facility Object has been created, Right-click on the Facility object and select New TDM Spans. Select the drop down menu for the property Interface. Select Signaling.  Commit This. A tabbed field named Signaling Spans will get created on the right hand side of ClientView. ClientView will create 4 offsets that are ready to be get configured. These 4 offsets are associated with the four Signaling/Timing spans on the rear of the IMG.

  2. Each Signaling span must associate itself with a specific profile. Create a profile by right clicking on IMG EMS and selecting  New Profiles. Commit this.

  3. 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).

  4. Once the different profiles have been created, they can now be associated with specific spans. There are two ways to do this










  1. At this point spans 0 though 1 are associated with profile T1_Profile2 and should be in service. User can now go and set spans 2 and 3 to another profile which was previously created and is in the Profiles list.