Configuration of the FTTB and FTTC VoIP Services (Based on the H.248 Protocol)-HUAWEI

*******FTTB and FTTC VoIP Services -Based on the H.248 Protocol*********

Configure the OLT:

  1. Create an SVLAN and add an upstream port to it.Create smart VLAN 200 and add upstream port 0/19/0 to it.
    OLT(config)#vlan 200 smart
    OLT(config)#port vlan 200 0/19 0
  2. Add an ONU on the OLT. The ONU is connected to the GPON port of the OLT through an optical fiber. You can perform the service configuration only after adding an ONU successfully on the OLT. To log in to the ONU through Telnet and configure the ONU from the OLT, you must configure the inband management VLAN and IP address for the OLT and the ONU on the OLT.
    1. Configure the inband management VLAN and IP address of the OLT. Create management VLAN 4000 and add upstream port 0/19/0 to it. Configure the inband management IP address to


      To manage the ONU through SNMP, you must configure the management VLAN, configure the IP address, and create a management service port.
      OLT(config)#vlan 4000 smart
      OLT(config)#port vlan 4000 0/19 0
      OLT(config)#interface vlanif 4000
      OLT(config-if-vlanif4000)#ip address 24
    2. Add a DBA profile.Configure the DBA profile name to VoIP, type to Type3, assured bandwidth to 15Mbit/s and upstream bandwidth to 30Mbit/s.
      OLT(config)#dba-profile add profile-name VoIP type3 assure 15360 max 30720
    3. (Optional) Add an alarm profile.
      • The ID of the default GPON alarm profile is 1. The thresholds of all the alarm parameters in the default alarm profile are 0, which indicates that no alarm is generated.
      • In this example, the default alarm profile is used, and therefore the configuration of the alarm profile is not required.
      • Run the gpon alarm-profile add command to add an alarm profile, which is used for monitoring the performance of an activated ONU line.
    4. Add an ONU line profile.Add GPON ONU line profile 10 and bind T-CONT 2 to DBA profile named VoIP. In this way, the T-CONT can flexibly provide DBA solutions based on different configurations in the DBA profile.


      The ONU line profile must not be the existed on and you can create different ONU line profiles based on different services. This topic considers creating the ONU line profile 10 for example.

      OLT(config)#ont-lineprofile gpon profile-id 10
      OLT(config-gpon-lineprofile-10)#tcont 2 dba-profile-name VoIP

      Add GEM port 0 for carrying management traffic streams and GEM port 1 for carrying traffic streams of the ETH type. Bind GEM port 0 and GEM port 1 to T-CONT 2. Configure the QoS mode to priority-queue (default).


      1. To change the default QoS mode, run the qos-mode command to configure the QoS mode to gem-car or flow-car, and run the gem add command to configure the index of the traffic profile to which the GEM port is bound.
      2. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car, traffic profile 6 is bound by default (no rate limitation); when the QoS mode is gem-car, traffic profile 6 is bound by default (no rate limitation).
      OLT(config-gpon-lineprofile-10)#gem add 0 eth tcont 2
      OLT(config-gpon-lineprofile-10)#gem add 1 eth tcont 2

      Configure the mapping mode from the GEM port to ONU-side service to VLAN (default), map the service port of management VLAN 4000 to GEM port 0, and map the service port of SVLAN 200 (CVLAN 200) to GEM port 1.

      OLT(config-gpon-lineprofile-10)#mapping-mode vlan
      OLT(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 4000
      OLT(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 200

      After the configuration is complete, run the commit command to make the configured parameters take effect.

    5. Add an ONU. Connect the ONU to GPON port 0/2/1. The ONU ID is 0, the SN is 32303131B39FD641, the management mode is SNMP, and the bound line profile ID is 10.


      • You can run the ont add command to add an ONU offline or run the ont confirm command to confirm an automatically discovered ONU.
      • Before running the ont confirm command to confirm the automatically discovered ONU, you must run the port ont-auto-find command in the GPON mode to enable the ONU automatic discovery function.
      • In this example, the method of confirming an automatically discovered ONU is used.
      OLT(config)#display ont autofind all
         Number              : 1
         F/S/P               : 0/2/1
         Ont SN              : 32303131B39FD641
         Password            :
         VenderID            : HWTC
         Ont Version         :
         Ont SoftwareVersion : V8R307 C00
         Ont EquipmentID     : SmartAX MA5616
         Ont autofind time   : 2009-08-21 16:51:45
         The number of GPON autofind ONT is 1
      OLT(config)#interface gpon 0/2
      OLT(config-if-gpon-0/2)#ont confirm 0 ontid 0 sn-auth 32303131B39FD641 snmp
       ont-lineprofile-id 10


      • After an ONU is added, it is recommended that you run the display ont info command or the display ont state command to query the ONU status. In this step, ensure that Config State and Match State of the ONU are normal and match respectively.
      • If the ONU state in the actual query result is different from the preceding description, run the display ont capability command to query the actual ONU capabilities and then add a proper ONU profile and a proper ONU based on the queried ONU capabilities.
    6. (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.
      OLT(config-if-gpon-0/2)#ont alarm-profile 1 0 profile-id 1
    7. Configure the inband management VLAN and IP address of the ONU.Configure the static IP address of the ONU to and the management VLAN ID to 4000 (the same as the management VLAN of the OLT).
      OLT(config-if-gpon-0/2)#ont ipconfig 1 0 static ip-address
       mask vlan 4000
    8. Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 4000, GEM port ID to 0, and CVLAN ID to 4000. The rate of the inband service port on the OLT is not limited. Therefore, use traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip command to add a traffic profile and bind it to the service port.
      OLT(config)#service-port 0 vlan 4000 gpon 0/2 ont 0 gemport 0 multi-service
       user-vlan 4000 rx-cttr 6 tx-cttr 6


    Now, the ONU is successfully added to the OLT, and the management channel between the OLT and the ONU is available. You can log in to the ONU by running the telnet command on the OLT to configure the ONU.

  3. Configure the traffic profile.You can run the display traffic table ip command to query the traffic profiles existing in the system. If the traffic profiles existing in the system do not meet the requirements, you need to run the traffic table ip command to add a traffic profile.Add traffic profile 9, and no rate limitation on user packets. The priority is 6 and the priority policy is scheduled by the priority that the packets bear.
    OLT(config)#traffic table ip index 9 cir off priority 6 priority-policy
  4. Create a service port.

    Configure the service port ID to 200, SVLAN ID to 200, GEM port ID to 1, bind traffic profile 9 and CVLAN ID to 200.


    The CVLAN must be consistent with the upstream VLAN of the ONU.
    OLT(config)#service-port 200 vlan 200 gpon 0/2/1 ont 0 gemport 0 multi-service
     user-vlan 200 rx-cttr 9 tx-cttr 9
  5. Configure the queue scheduling.Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with the weight as 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode. Configure the priority of the VoIP service to 6 and adopt the PQ mode.


    Queue scheduling is configured globally. You need to configure queue scheduling only once on the OLT, and then the configuration takes effect globally. In the subsequent phases, you need not configure queue scheduling repeatedly when configuring other services.
    OLT(config)#queue-scheduler wrr 10 10 20 20 40 0 0 0

    Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map queues 0-7 respectively.

    OLT(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7


    For the service board that supports only four queues, the mapping between 802.1p priorities and queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue 2; priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.
  6. Save the data.


Be the first to comment

Leave a Reply

Your email address will not be published.


For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

I agree to these terms.