Re: [asterisk-users] Where an extension really is (DUNDi woes)
Kyle Sexton wrote: On 6/15/07, *Anthony Francis* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Kyle Sexton wrote: I have two servers setup to do DUNDi lookups against each other. The scenario is that on server A, I have a wildcard match for extensions 64XX that rings to a local extension on the server. On server B I have a 6442 real extension that I would like to have ring if called. It seems that DUNDi is matching on the 64XX and not searching out to see if there is a *more* exact match than the pattern match. Is there any way to get around this? I don't think I am incorrect in saying that dundi doesn't look for externally that which it knows about locally. I think thats pretty standard of routing protocols. 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. :( it will, look into the regexten for your sip accounts. Now have dundi lookup a number in that extension... Now, you might need to abstract extension numbers from sip accounts, but that only has advantages anyway... -- Kyle Sexton ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Remco Post I didn't write all this code, and I can't even pretend that all of it makes sense. -- Glen Hattrup ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Where an extension really is (DUNDi woes)
Kyle Sexton wrote: I have two servers setup to do DUNDi lookups against each other. The scenario is that on server A, I have a wildcard match for extensions 64XX that rings to a local extension on the server. On server B I have a 6442 real extension that I would like to have ring if called. It seems that DUNDi is matching on the 64XX and not searching out to see if there is a *more* exact match than the pattern match. Is there any way to get around this? -- Kyle Sexton ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I don't think I am incorrect in saying that dundi doesn't look for externally that which it knows about locally. I think thats pretty standard of routing protocols. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Where an extension really is (DUNDi woes)
On 6/15/07, Anthony Francis [EMAIL PROTECTED] wrote: Kyle Sexton wrote: I have two servers setup to do DUNDi lookups against each other. The scenario is that on server A, I have a wildcard match for extensions 64XX that rings to a local extension on the server. On server B I have a 6442 real extension that I would like to have ring if called. It seems that DUNDi is matching on the 64XX and not searching out to see if there is a *more* exact match than the pattern match. Is there any way to get around this? I don't think I am incorrect in saying that dundi doesn't look for externally that which it knows about locally. I think thats pretty standard of routing protocols. 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. :( -- Kyle Sexton ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
