No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Terminal registered GK already, but RM can`t call it in

Publication Date:  2013-12-30 Views:  168 Downloads:  0
Issue Description
One project which has 1 8650C, 1 SMC, and many terminals. And the terminal is set in different province, and all the terminal will enable NAT to the internet.
Alarm Information
Handling Process
Terminal and MCU are both in private network. And all the facility are enable NAT. all the terminal register NAT of GK IP addr.
When we call the terminal and it will have a option of `no response`
① First we check the logs in the gk files
MCU send the DRQ, and the logs shows that the site is hungup by the GK.
② And in RM, we call this site, but shows no response, it leads to this site was hungup by Gk
③ From MCU site, we ping terminal but still can`t reach.
So we diagnose this issue is caused by the network.
④ But why we can`t reach the remote. Engineer said that if we change another MCU, the same type and the same type, and the MCU can ping terminal.
So we ask customer for the historical operation to check whether they change some relative operations, we get more information, this network use the GE1 firewall-mode, and config the relative route information.
And this GE1 port has a router and it leads to other place, so we delete the router as follows.
After we delete the router, it can be reached。
Root Cause
as follows
After we delete the router, the site can be called into the conference。