<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">generally your gateway CSS should not contain any partition that contains a RP pointing back to the same gateway, or an alternate gateway to the same same cloud since that can cause a call routing loop.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>/Wes</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><DIV><DIV>On Feb 15, 2006, at 10:16 AM, Ciscozest wrote:</DIV><BR class="Apple-interchange-newline"><O:SMARTTAGTYPE name="PlaceName" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></O:SMARTTAGTYPE><O:SMARTTAGTYPE name="PlaceType" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></O:SMARTTAGTYPE><O:SMARTTAGTYPE name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></O:SMARTTAGTYPE> <DIV><FONT face="Arial" size="2">Would it do any harm if we set Gateway CSS (inbound) to contain all configured partitions? I worry if this could cause toll-fraud.</FONT></DIV> <DIV><FONT face="Arial" size="2">On second thought, I realized telco will always send fixed DID numbers to the gateway, thus setting the gateway CSS to contain internal partition is enough and secure. What is the best practice we should follow? Any idea? Thanks</FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A></DIV> </DIV><BR></DIV></BODY></HTML>