Configuration steps for GEPON based VOIP Services

STEPS TO CONFIGURE VOIP (SIP) SERVICES

Step-1:Connectivity route between VOIP server and Tier-1/2 Switch should be ok. From Tier-1/2 switch it should ping the VOIP server gateway/VOIP server IP via VOIP gateway at Bangalore. Step-2:Check the protocol of VOIP server, if VOIP server is based on H.248 protocol then no need to change the ONT IAD software. But if it is based on SIP based protocol then you have to upgrade ONT IAD software to SIP. Step to upgrade the ONT to SIP based are as follows, First start FTP server, Login it and provide path where the upgraded patch is stored and minimize the server (do not close it). Start EMS server, select HSWA card>Control command>Batch upgrade ONU

Configuration steps for GEPON based VOIP Services

Select ONU CPU/IAD software, provide FTP server IP (IP address of EMS server which is used to communicate with OLT system), User name and Password (same as of FTP server), Select File name (which will come automatically if FTP server is running), Select Slot No. (to which ONTs are connected and at one time you can upgrade up to 128 ONTs at same time but there is one condition all ONTs should be at on state), Select ONT to be upgrading and select Upgraded Software. Step-3:- VOIP Configuration Start EMS server to start VOIP configuration, 1. Select HSWA card>Config>Local VLAN, provide following information : Service Name: Any name Starting VLAN ID: xxxx (service VLAN of VOIP) VLAN ID END: xxxx (service VLAN of VOIP) Interface No.: x:x (Select the interface port to which Uplink fiber is connected) TAG/UNTAGGED: x Service Type: ngn

Configuration steps for GEPON based VOIP Services

2. NGN configuration: a) Select HSWA card>Config>NGN config>NGN interface, provide following information: Signaling service name: Select the name provided in Local VLAN Protocol Type: SIP/H.248/MGCP SIP Register Server Address: IP address of VOIP server SIP Proxy Server Address: IP address of VOIP server

Configuration steps for GEPON based VOIP Services

b) Select HSWA card>Config>NGN config>NGN interface provide following information: Signaling service name: Select the name provided in Local VLAN Telephone No. Local Telephone No. (without codes) ONU Public IP: x.x.x.x (Provide by planning section) ONU Public IP Gateway: x.x.x.x End Point User Name/SIP telephone No.: Local telephone No.(with Country code and STD code) Username: Local telephone No.(with Country code and STD code) Password: Local telephone No.(with Country code and STD code)

Configuration steps for GEPON based VOIP Services

3. Port Service configuration of ONT: Select ONT for configuring FXS ports, EC4B card>ONT>config > port service configuration> Voice config> FXS1or FXS2 port, Provide following information: Telephone No: (as configured in NGN configure) Signal VLAN ID: (as provided in Local VLAN)

Configuration steps for GEPON based VOIP Services

After completing this configuration please check the VOIP LED on ONT, it should glow Green, if it is not glowing then you should check the connectivity between the ONT to VOIP server. How to check this? Answer is Step-4. Step-4:Connectivity route between VOIP server and ONT system should be ok. How to check the connectivity? Ans:- Use Telnet/Hyperlink to check connectivity,(you can access Telnet using EMS server and Hyperlink using console port of HSWA card) which are as follows: Login into Telnet/Hyperlink: Username: GEPON Password: GEPON User: ENABLE Password: GEPON Admin# cd service

(Level-1 login) (Level-2 login)

Configuration steps for GEPON based VOIP Services

Admin/service# Telnet 10.25.100.18 Username: GEPON Password: GEPON User: ENABLE Password: GEPON config# cd service config /service# Telnet 10.25.A1.A2 {where, A1= (100+Slot No.) A2= ((PON No.-1 *64+Auth. ID)} Username: gepon Password: gepon User: enable Password: gepon # system system> ping x.x.x.x

(Fixed private IP of PUBA card) (Level-1 login) (Level-2 login) (Private IP of ONT)

(Level-1 login) (Level-2 login) (IP address of VOIP server)

If ONT is able to ping the VOIP server, it means connectivity is ok. In the similar way VOIP server can also ping your ONT from VOIP server using simple ping command.