sorry, mgcp...... did a no mgcp and mgcp. no change reset from CM and all registered to cmsub reset but the once on the pub didn't.
CM shows good replication on the DB's. it's the wierdest thing I've seen. Scott On Tue, Jan 17, 2017 at 10:17 AM, Brian Meade <bmead...@vt.edu> wrote: > Try resetting all the ports from CUCM then maybe bounce SCCP on the VG if > that still didn't work. > > On Tue, Jan 17, 2017 at 12:45 PM, Scott Voll <svoll.v...@gmail.com> wrote: > >> All are in the same DP. we just changed from IP to FQDN over the >> weekend. Any other thoughts? >> >> Scott >> >> >> On Tue, Jan 17, 2017 at 9:41 AM, Jeffrey McHugh <jmchugh >> <jmch...@fidelus.com>> wrote: >> >>> Pretty sure you can assign device pools to the specific ports, different >>> DP’s may have diff. call mgr groups >>> >>> >>> >>> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On >>> Behalf Of *Scott Voll >>> *Sent:* Tuesday, January 17, 2017 12:38 PM >>> *To:* cisco-voip@puck.nether.net >>> *Subject:* [cisco-voip] vg224 registered to two different Cm's >>> >>> >>> >>> How can some ports on a VG register to the pub and some to the Sub on >>> the same VG? >>> >>> >>> >>> totally confused on this one. >>> >>> >>> >>> CM 10.5.2 / VG vg224-i6k9s-mz.151-4.M9.bin >>> >>> >>> >>> Scott >>> >>> >>> >>> >> _______________________________________________ >> cisco-voip mailing list >> cisco-voip@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
