where x = the Loop and shelf assigned to that gateway.
Also you could in LD 117
stat ipmg <--will show the status of all IPMG
prt ipr <--will show all configured gateway IP Addresses
If you see it configured or you add it in LD 97 that is only the ELAN info to allow registration. The TLAN for the MGC, DSP's, Callserver IP etc. all needs setting up. This is carried out in Element manager access
System\IP Network\Media Gateways
select the MG Loop/Shelf by clicking the MGC link on the right that corresponds with the one you are doing. In there you will see all the prompts for IP/MASK/GW of the MGC/DSP cards and you will set the Callserver address, QOS, Codecs etc.
Yep, you don't have it configured in Element Manager in the Node Properties and you don't have it built in the the Superloop Config. Just because you can ping it only means that you have it locally configured in the MGC
the odd thing is the one configured MGC Loop 0 Shelf 0 is down, also is the new one supposed to be in a different subnet, different location etc? The configured one is 10.11.216.2 and the new one is 10.11.116.8
What do you mean 10.11.116.8 is listed on all the phones? If you have no experience with this machine it is a whole different animal than anything you have probably ever seen.
That would be the Node IP then. Kind of a Psuedo IP address for all IP Telephony Hardware. Doesn't really belong to one device but rather a group of devices.
It would explain the difference in subnet as it would be the node address of the sig server for example and on the TLAN so you have 2 subnets ELAN = 10.11.216.xxx and TLAN = 10.11.116.xxx but then that takes you back to the start why is an MGC trying to register with that address.
Might be easier to start from scratch do you know what you have hardware wise some useful commands would be:
LD 22
REQ iss <-- Software Version
REQ tid <-- This is your site ID that all licenses are against from this can check versions, hardware type, applications etc.
LD 117
=> stat ss <-- Status of any signaling servers
=> inv prt cards <-- list of cards in the inventory might help us with what you have
=> stat ucm info <-- this and next command depend on version and if you have a UCM or System Manager earlier releases did not have this
=> stat ucm sys
Access element manager to see details on the Node config and MGC config mentioned earlier.
If you only have one MGC then it could be that its just setup incorrectly, and just needs its ELAN setting to 10.11.216.2, for that you would access the MGC card direct and set the ELAN details and Callserver details leave the rest and reboot.
=> stat ucm info
The Security Domain IP address is : 10.11.116.9
The Security Domain Fingerprint is: AF:56:EA:23:E1:49:6A:93:74:E0:3B:A5:22:55:39:ED
=> stat ucm sys
Requesting UCM registration status from devices.
Waiting for status updates from each of the elements...
No elements registered with the Call Server
1 have 1 MGC card
I also have a backup of my colleagues from the neighboring branch. Hardware settings are the same except for ip. They have 10.11.221. * And 10.11.121. * I have 10.11.116. * And 10.11.216. *
So you have a media Gateway 1010 with a CPPM Callserver running release 7.5, the MGC has a single DSP128 on it. You have a CPDC card which is your sig server.
Register the MGC to the Callserver connect to the MGC Card using Serial cable and follow the link that KCFLHRC mentioned earlier just do the mgcIPClear, diskformat "all", reboot. When the MGC comes back up enter the MGC ELAN IP, MASK, Default GW and Callserver address.
If you are not sure of these in LD 117
=> prt elnk <--will see your Active callserver IP
=> prt mask <--ELAN Mask
=> prt route <--ELAN Default gateway assigned for IP 0.0.0.0
=> prt ipr <--MGC ELAN
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.