Is it possible to use the ViewPoint 9000 endpoint to place PSTN calls

To make calls to common phones on a Huawei endpoint, perform the following operations: - After an endpoint is connected to the PSTN, you can make calls to common phones on the endpoint. ViewPoint 9000 series endpoints, TE40, TE50, and TE60 can be connected to the PSTN. - ViewPoint 9000 series endpoints do not provide the PSTN port. To connect ViewPoint 9000 series endpoints to the PSTN, you need to use the PSTN-E1 card, which provides one PSTN port and one E1 port. TE40, TE50, and TE60 provide the PSTN port. - You can also use a common phone to call an endpoint connected to the PSTN directly by dialing the PSTN number of the endpoint. - You can use a common phone to call an endpoint connected to the PSTN only after the endpoint is configured as follows: On the web interface of TE40, TE50, or TE60, choose System Settings > Conference > Normal and set PSTN call to Enable.

For details about how to configure the PSTN port for TE series endpoints, see the PSTN Port for TE Series Videoconferencing Endpoints.

During interconnection between a Huawei endpoint and a device provided by a vendor, both parties must comply with industry communication standards. However, whether the communication is available depends on actual test results. If you have interconnection test requirements, contact the local office of Huawei.

If upgrading the endpoint using its normal system fails, you can use the Bootrom system for the upgrade by performing the following steps: 1. Set the DIP switch on the rear panel of endpoint to Load. The setting method varies with the endpoint model. a. If you are using the ViewPoint 9033, VP9035, ViewPoint 9036, or ViewPoint 9039, set DIP switch 1 to Load; b. If you are using the ViewPoint 9030, VP9035A, VP9036S, ViewPoint 9039S, or VP9039A, set DIP switch 1 or both DIP switches 1 and 2 to Load. 2. Restart the endpoint. a. If you set only DIP switch 1 to Load, the endpoint IP address is restored to 172.16.21.114. b. If you set both DIP switches to Load, the endpoint IP address is restored to the IP address used before setting the DIP switch. 3. Set the IP address of the computer used for web logins to be in the same network segment as the endpoint IP address. For example, if the endpoint IP address is 172.16.21.114, you can set the IP address and subnet mask of the computer to 172.16.21.56 and 255.255.0.0 respectively. 4. Decompress the upgrade software package on the computer, and run the UpgradeTool.exe file in the package. 5. In Remote Terminal IP Address, enter the endpoint IP address, such as 172.16.21.114. Then click Upgrade. 6. In the displayed dialog box, enter the upgrade password and click OK. 7. After the upgrade is complete, set the DIP switches on the endpoint to Norm. 8. Restart the endpoint.

The possible causes and solutions. Cause 1: The local or remote endpoint was not connected to an IP network. Solution: 1) Verify that the endpoint is connected to the IP network, that is, the LAN indicator on the rear panel of the endpoint is steady green. 2) From the remote controlled UI, choose Diagnostics > Network Test. Alternatively, from the web interface, choose Maintenance > Diagnostics > Network Test. Enter the IP address of the remote site and start a Ping test. If the Ping test fails, a network error occurs. 3) From the remote controlled UI, choose Settings > Network > IP. Alternatively, from the web interface, choose System Settings > Network > IP. Verify the IP network settings. Cause 2: The local endpoint was on a private network while the remote endpoint was on a public or different private network, and the NAT settings were incorrect. Solution: 1) Check whether the endpoint can communicate with the remote endpoint using either of the following methods: a. From the remote controlled UI, choose Diagnostics > Network Test. b. From the web interface, choose Maintenance > Diagnostics > Network Test. 2) Enter the remote endpoint IP address and start a Ping test. If the Ping test fails, verify the NAT settings using either of the following methods: a. From the remote controlled UI, choose Settings > Network > IP > Firewall. b. From the web interface, choose System Settings > Network > Security and Service > NAT. Cause 3: The GK with which the local or remote endpoint was registered did not support the function to place calls by IP address. Solution: Use either of the following methods: a. From the remote controlled UI, choose Settings > Network > IP > H.323. b. From the web interface, choose System Settings > Protocol > H.323/SIP Settings. Set Enable GK to Disable.