Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DSP/MGC problem on CS1000E release 6.0

Status
Not open for further replies.

hellbee

Technical User
Sep 23, 2009
5
CA
Hi all,

I am currently installing a new CS1000E system with MGC and a DB32 & DB96 card. DB32 is in slot #2 and configured on IPMG 4 0 0 0, while my DB96 is configured on 4 0 11 0.

I assigned 2 IP on the TLAN for the DSPs and also another for my MGC. I am able to ping the MGC from my CS and SS and they register together. Now the issue im having is that im not able to ping the DSPS and they remain disabled in LD32. Even if I force them to come up in service, it doesn't work. From the MGC I receive the following error message, which I think is the cause of the problem maybe ?

14:35:16 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from Primary Call Server


I have removed the file from the MGC CF and reinstalled everything in element manager : same problem. I guess that the SS is unable to transfert MGC and DSP property to the CS.


Any Ideas ?



Thanks





Justin
 
heloo Justin
this can help u
____________________________________________________________

Media Gateway Controller (MGC) cannot get the "mgcdb.xml" file from the Call Server (CS)

--------------------------------------------------------------------------------

Problem Description
After the CS initialized, the MGC cannot get the "mgcdb.xml" file. The following error appears in the MGC log files:
"DSP DBs are present, waiting for mgcdb.xml from Primary Call Server"

Voice Gateway (VGW) channels stay in a busy state even when the MGC is registered to the CS.
Problem Resolution
"mgcdb.xml" exists in the MGC and the CS. Normally, the MGC does not use the file located on itself but requests it from the CS. If using patch MPLR27610 which is a part of loadware MGCCAM06, the MGC will use the "mgcdb.xml" file which already existing in the MGC under /u/db directory. Note, if you upgrade the loadware, the MGC may not reboot automatically. The MGC needs to be rebooted manually.


CS patch MPLR25424 also fixes the problem. It resolves the issue on systems that have around 30 MGCs connected to the same CS. Due to socket limitations the system experiences this problem when around 30 MGCs are connected. This patch increases the socket size but it has some special instructions that have to be followed strictly. Since it changes the data structures, special instructions for the installation of this patch should be followed strictly.


MGCCAM06 is available from the Enterprise Solutions PEP Library (ESPL) at Please contact Nortel Technical Support and request patch MPLR25424.
Affected Products
Enterprise VoIP Core CS 1000E 05.50J
____________________________________________________________

install release 6.00 patch from ESPL



Samo
 
From what I have experienced, the MGC and DSPs won't register until you get the MGC registered to the UCM security domain. When you log into UCM, do you see the MGC showing as an element? If not, you can do a register ucmsecurity system from LD 117 and see if the MGC will register with the call server, or go to the OAM prompt on the MGC and type "joinSecDomain" and follow the prompts to register the MGC.

Once the MGC registers to the security domain, it will download the proper loadware from the call server.

The UCM piece of release 6.0 is nothing but a pain in the rear end if you ask me.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top