Problem connect GD3 with CS

[sito521]

I am currently trying to connect a GD3 with the CS, but I can not register or download the configuration files
I have managed to configure the IP address of the GD card, and I have a ping with it, but I do not register.
The Media Gateway is created in the OXE, and has the MAC associated in the CS.
If we make a telnet we have been able to connect to the OXE and it shows the error:

Welcome to mg3
IP is 10.31.13.86
* Warning: connect to callserver failed! *
* Please use resolve_connect to get possible cause of failure *
mg3 login: root
Bienvenue to user root
tcp 0 0 10.31.13.86:telnet 10.26.143.1:10106 ESTABLISHED
-bash-3.2 # mgconfig
Sat Apr 21 01:03:08 UTC 2018
[Script /etc/rc.d/init.d/verify_ipmg (PID = 2343) started by "mgconfig"]
The ipmg.cfg is in good shape in RAM
Welcome to the GD configuration tool

Does anyone know why this failure can be?

* Warning: connect to callserver failed! *
* Please use resolve_connect to get possible cause of failure *

How can I register?


Thank you very much!!!!!

[mdhussainvlr]

Is GD3 rebooting after that ??

[sito521]

Hello!! yes, the gd3 restarts continuously

[fery_s]

did you run lanpbxbuild command in cs?

[sito521]

yes,

(1)OXE_a> lanpbxbuild

Sun Apr 22 15:35:17 CEST 2018


Reading data from file.

1. View
2. Add
3. Delete
4. Modify
5. Move
6. Apply changes
7. Copy lanpbx to lanpbx-mipt
0. Quit

[fery_s]

yes,

(1)OXE_a> lanpbxbuild

Sun Apr 22 15:35:17 CEST 2018


Reading data from file.

1. View
2. Add
3. Delete
4. Modify
5. Move
6. Apply changes
7. Copy lanpbx to lanpbx-mipt
0. Quit

use "lanpbxbuild -auto" then with lanpbxbuild menu 1 check the ip download.
did you set the tftp ip address in gd card and then reboot it?

[vad]

On GD-3 - declared cpu_main address (not physical address)?
Exist incidents on CS about downloading or not?
CS and GD - in different subnet - do you have some restriction (tftp allowed or not)?

[sito521]

Hello!

I have managed to correct the problem with the indications.
With the lanpbxbuild command, I have managed to find the problem. The IP MAIN that appeared was not the correct one, it was another old one. We have corrected it and it is already working correctly.

Thank you very much for your help!