sh ccm shows they resolve and are registered to the sub and backup to the pub.
That is the wierd thing. as some voice ports show the sub and some the pub.... we are looking at restarting the RIS data collector........ Scott On Tue, Jan 17, 2017 at 11:09 AM, Evgeny Izetov <eize...@gmail.com> wrote: > Can those VGs resolve the FQDNs? My guess they wouldn't even register if > they couldn't but maybe they are keeping some sort of 'last known good' > configuration. > > On Tue, Jan 17, 2017 at 1:59 PM, Jeffrey McHugh <jmch...@fidelus.com> > wrote: > >> Sometimes restarting RIS data collector can clear registration anomalies >> >> >> >> *From:* Scott Voll [mailto:svoll.v...@gmail.com] >> *Sent:* Tuesday, January 17, 2017 1:58 PM >> *To:* Brian Meade <bmead...@vt.edu> >> *Cc:* Jeffrey McHugh <jmch...@fidelus.com>; cisco-voip@puck.nether.net >> *Subject:* Re: [cisco-voip] vg224 registered to two different Cm's >> >> >> >> yup.... but did changed from IP to FQDN on the cluster.. >> >> >> >> On Tue, Jan 17, 2017 at 10:57 AM, Brian Meade <bmead...@vt.edu> wrote: >> >> Same Device Pool on all the ports? >> >> >> >> On Tue, Jan 17, 2017 at 1:55 PM, Scott Voll <svoll.v...@gmail.com> wrote: >> >> 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 >> >> >> >> >> >> >> >> >> *Jeffrey McHugh* | Sr. Collaboration Consulting Engineer | VCP-DCV, CCNP >> Collaboration >> [image: Company_Logo_Image] <http://www.fidelus.com/> >> *Fidelus Technologies, LLC* >> Named Best UC Provider in the USA >> <http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/> >> 240 West 35th Street, 6th Floor, New York, NY 10001 >> *+1-212-616-7801 <(212)%20616-7801>* office | *+1-212-616-7850 >> <(212)%20616-7850> *fax | www.fidelus.com >> [image: LinkedIn] >> <http://www.linkedin.com/company/fidelus-technologies/products>[image: >> Twitter] <http://www.twitter.com/FidelusUCC>[image: Facebook] >> <http://www.facebook.com/FidelusUCC>[image: YouTube] >> <http://www.youtube.com/FidelusTraining> >> >> >> Disclaimer - January 17, 2017 >> >> This email and any files transmitted with it are confidential and >> intended solely for *Scott Voll,Brian Meade,cisco-voip@puck.nether.net >> <cisco-voip@puck.nether.net>*. If you are not the named addressee you >> should not disseminate, distribute, copy or alter this email. Any views or >> opinions presented in this email are solely those of the author and might >> not represent those of Fidelus Technologies, LLC. Warning: Although Fidelus >> Technologies, LLC has taken reasonable precautions to ensure no viruses are >> present in this email, the company cannot accept responsibility for any >> loss or damage arising from the use of this email or attachments. >> >> _______________________________________________ >> 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 >> >> >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
