<html><body><div style="font-family: Verdana; font-size: 10pt; color: #000000"><div><br></div><div>Thanks Brian. </div><div><br></div><div>I had to read the bug twice. It's the troubleshooter on CUPS, but it's testing what's configured on CUCM by the sounds of it.</div><div><br></div><div>I think I will play it safe and use IP addresses on the CUCM configuration pointing to the HA CUPS pair. And on the CUPS server, I will go ahead an use an SRV record since I want to be able to point to more than one CUCM server.</div><div><br></div><div>Another question arises though. I remember when playing with intercluster trunks, it had to be fully meshed, so all trunk members on one cluster had to point to all members on the other cluster, or calls would fail.</div><div><br></div><div>Does a SIP trunk have to be fully meshed as well?</div><div><br></div><div>For example, if the device pool of the SIP trunk includes subA, subB and subC, do I have to make sure that the SRV records I'm using on the CUPS server have those three servers included?</div><div><br></div><div>I was also considering checking off "make active on all nodes" - but I'm not sure of the ramifications of that. I'd have to probably write the SRV record properly so that the publisher is (never) used or used only as a last resort.</div><div><br></div><div>Thanks!</div><div><br></div><div><br></div><div><br></div><div><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><div><br></div>519‐824‐4120 Ext 56354<br>lelio@uoguelph.ca<br>www.uoguelph.ca/ccs<br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span name="x"></span><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Brian Meade" <bmeade90@vt.edu><br><b>To: </b>"Lelio Fulgenzi" <lelio@uoguelph.ca><br><b>Cc: </b>"Cisco VoIP Group" <cisco-voip@puck.nether.net><br><b>Sent: </b>Monday, January 18, 2016 4:56:18 PM<br><b>Subject: </b>Re: [cisco-voip] curious - no DNS SRV for SIP trunk to IM&P in HA<br><div><br></div><div dir="ltr">Looks like it may just be the CUPS Troubleshooter Tool doesn't know how to handle it- <a href="https://tools.cisco.com/bugsearch/bug/CSCue72366" target="_blank" data-mce-href="https://tools.cisco.com/bugsearch/bug/CSCue72366">https://tools.cisco.com/bugsearch/bug/CSCue72366</a><div><br></div><div>So it looks like it will work as an SRV but may fail in the troubleshooting tool. It looks like this was because IM&P/CUPS disn't support resolving SRVs until recently- <a href="https://tools.cisco.com/bugsearch/bug/CSCui67346" target="_blank" data-mce-href="https://tools.cisco.com/bugsearch/bug/CSCui67346">https://tools.cisco.com/bugsearch/bug/CSCui67346</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 18, 2016 at 3:47 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank" data-mce-href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><div><div style="font-family:Verdana;font-size:10pt;color:#000000" data-mce-style="font-family: Verdana; font-size: 10pt; color: #000000;"><div><br></div><div>Just reading through some documentation (see link below) and it states that when configuring the SIP trunk from CUCM to the IM&P cluster, I can not use DNS SRV records if I'm using HA. Tells you to use IP address or FQDN. <span style="font-size:10pt" data-mce-style="font-size: 10pt;"><br></span></div><div><span style="font-size:10pt" data-mce-style="font-size: 10pt;"><br></span></div><div><span style="font-size:10pt" data-mce-style="font-size: 10pt;">Just wondering what others have thought about this. I'll go ahead and use IP address, but it struck me as odd.</span></div><div><br></div><div><br></div><div><a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/9_1/CUP0_BK_C68AA046_00_config-admin-guide-imp-91/CUP0_BK_C68AA046_00_config-admin-guide-imp-91_chapter_0101.html#CUP0_TP_SBE6AFC1_00" target="_blank" data-mce-href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/9_1/CUP0_BK_C68AA046_00_config-admin-guide-imp-91/CUP0_BK_C68AA046_00_config-admin-guide-imp-91_chapter_0101.html#CUP0_TP_SBE6AFC1_00">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/9_1/CUP0_BK_C68AA046_00_config-admin-guide-imp-91/CUP0_BK_C68AA046_00_config-admin-guide-imp-91_chapter_0101.html#CUP0_TP_SBE6AFC1_00</a></div><div><br></div><div><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><div><br></div><a href="tel:519%E2%80%90824%E2%80%904120%20Ext%2056354" target="_blank" data-mce-href="tel:519%E2%80%90824%E2%80%904120%20Ext%2056354">519‐824‐4120 Ext 56354</a><br><a href="mailto:lelio@uoguelph.ca" target="_blank" data-mce-href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a><br><a href="http://www.uoguelph.ca/ccs" target="_blank" data-mce-href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span></span><br></div><div><br></div></div></div><br>_______________________________________________<br> cisco-voip mailing list<br> <a href="mailto:cisco-voip@puck.nether.net" target="_blank" data-mce-href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank" data-mce-href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> <br></blockquote></div><br></div></div><div><br></div></div></body></html>