<html><body bgcolor="#FFFFFF"><div>What version of 4.x? </div><div>SIP trunk direct between UCM servers or GW to GW? </div><div>Assumption is that the sip reinvite to 'renew the call' has changed and is using a different command. A sniffer capture or ccm trace can provide more info. <br><br>Sent from my phone, apologies for any typos.</div><div><br>On Jul 1, 2009, at 6:23 AM, GregW <<a href="mailto:gwenzit@yahoo.com">gwenzit@yahoo.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font: inherit;"><div>
<div>
<div> </div>
<div> </div>
<div>The failure is when the call is made *101.XXXX route pattern w/predot carries over to the far end cluster the calls lasts 10 min exactly then drops. The calls are made over a frame/mpls WAN connection and there is no qos. This did work prior to the upgrade to 6.01</div>
<div> </div>
<div> </div>
<div>My client had intracluster sip trunks working between two clusters and now it stopped. One of the clusters recently was upgraded from 4.x to 6.1 and this is when the sip calls started to fail. I suspect some config changes occured but just wanted to know if any of you had come across this could point me in the right direction. I will know more when I troubleshoot this later this morning.</div>
<div> </div>
<div> </div>
<div>Im just reaching out to all of you if there is anybody that had come across this.</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div></div></div></td></tr></tbody></table></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></body></html>