Yes, this is "normal" behaviour. The workaround is to issue "mgcp bind" commands only *after* the GW registers to CUCM. Then you can bounce the GW (no mgcp/mgcp) and it registers with proper source address.
best regards kobel On Sun, May 22, 2011 at 10:28, Ki Wi <kiwi.vo...@gmail.com> wrote: > Anyone faced this weird issue? > > Sometimes even with "mgcp bind" command specified, it will bind to ccm > using wrong ip address. What's the solution to resolve it? > > For me, i will just reboot the router but it waste quite a few minutes. > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
