Hi Kyle, "dundi lookup" is only going to find routes that are advertised on other nodes in your DUNDi cloud. Your local node won't query itself, as it knows you can terminate those calls. The proper practice is to try local routes first, then try a DUNDi lookup, and then fail the call. That way you're always calling the local routes properly, and only sending traffic to the cloud when you need to
Cheers, AR ________________________________________________________ Alex Robar, Technical Support, GearyTech Inc. 3075 Fourteenth Avenue, Unit 3, Markham, Ontario L3R 0G9 Markham: 905-513-8000 x 223 Fax: 905-513-8040 [EMAIL PROTECTED] www.gearytech.com -----Original Message----- From: [EMAIL PROTECTED] on behalf of Kyle Sexton Sent: Tue 9/4/2007 5:19 PM To: [email protected] Subject: [Dundi] 'dundi look up' question I'm having trouble understanding how 'dundi lookup' is finding it's results. Scenario: I have two servers configured, both pulling extensions from sipregistration context for where an extension lives. When I do a 'dundi lookup [EMAIL PROTECTED]' from server B, when 1000 is registered to server *A* I get a result. If I do a 'dundi lookup [EMAIL PROTECTED]' on server *A* when the extension is registered there I get no result. But I can call 1000 from either server w/o any issue. Is there something I'm missing w/ the 'dundi lookup' command? -- Kyle Sexton _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- Dundi mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/dundi
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- Dundi mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/dundi
