<div>if it were me and H323 Gateways:</div>
<div><br><br>Location1: IP <a href="http://1.1.1.1">1.1.1.1</a><br>Local exchanges: 111xxxx, 222xxxx, 333xxxx<br>dial-peer voice 111 pots</div>
<div>destination pattern [1-3]......</div>
<div>port FXO</div>
<div> </div>
<div>dial-peer voice 444 voip</div>
<div>preference 1</div>
<div>destination pattern [4-5]......</div>
<div>session target <a href="http://1.1.1.2">1.1.1.2</a></div>
<div> </div>
<div>dial-peer voice 445 pots</div>
<div>preference 2</div>
<div>destination pattern [4-5]......</div>
<div>port FXO</div>
<div> </div>
<div>etc</div>
<div><br>Location2: IP <a href="http://1.1.1.2">1.1.1.2</a><br>Local exchanges: 444xxxx, 555xxxx<br><br>Location3: IP <a href="http://1.1.1.3">1.1.1.3</a><br>Local exchanges 666xxxx<br><br>Location 4: IP <a href="http://1.1.1.4">1.1.1.4</a><br>
Local exchanges 777xxxx, 888xxxx</div>
<div> </div>
<div> </div>
<div>so your primary choice is to route those other extensions over the WAN and if NOT then over the FXO ports....</div>
<div>if I have more specific information I would write a tad better config file, but I thing you get the idea. You can do the same thing with MGCP and route patterns but this would be my first choice.</div>
<div> </div>
<div> </div>
<div>Kevin</div>
<div> </div>
<div> </div>
<div><br><br>If I was at location 1 and I wanted to make a call to someone outside<br>of our office close to location 3 I would call 666xxxx but right now<br>it goes out the FXO at location 1 and it's long distance. I would<br>
like for that call to go across the network and out the FXO on the<br>Location 3 router.<br><br>Thanks,<br>Dan.<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> </div><br>