On 6/15/07, <b class="gmail_sendername">Anthony Francis</b> <<a href="mailto:anthonyf@rockynet.com">anthonyf@rockynet.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Kyle Sexton wrote:<br>> I have two servers setup to do DUNDi lookups against each other. The<br>> scenario is that on server A, I have a wildcard match for extensions<br>> 64XX that rings to a local extension on the server. On server B I
<br>> have a 6442 real extension that I would like to have ring if called.<br>> It seems that DUNDi is matching on the 64XX and not searching out to<br>> see if there is a *more* exact match than the pattern match. Is there
<br>> any way to get around this?<br><br>I don't think I am incorrect in saying that dundi doesn't look for<br>externally that which it knows about locally. I think thats pretty<br>standard of routing protocols.
<br><br></blockquote></div><br>I was afraid of that. It just means I have to explicitly list every number in the DID range (so hundreds of extensions). I was hoping DUNDi would make the dialplan simpler. :(<br><br>-- <br>
Kyle Sexton