Doug, I feel your pain. I have, since 3 days ago, all but giving up on dundi in a enterprise/carrier core scalable environment, mostly due to no ability to summarize dial plan routes across several servers that may or may not have contiguous extensions registered across the cluster.
Example server 1 has exten 1234, 1235, 1001, 1002 registered and server 2 has 1236, 1237, 1003, 1004. But also in a failure or load balancing event, server 1 could have 1236, 1001, 1235, 1004 and server 2 could have 1237, 1234, 1002 and 1003 registered. The dynamic nature on maintaining extension state across many registration servers in real time, is not something dundi, realtime or regcontext/regexten can handle right now. At least I haven't figured it out yet. Brad, Please be so kind to publish your dundi.conf configs and also dundi snips from extension.conf for server 1, server 2, server3...... Thanks Guys. JR -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 16, 2006 9:42 PM To: [email protected] Subject: Asterisk-Users Digest, Vol 20, Issue 114 Send Asterisk-Users mailing list submissions to [email protected] Could you perhaps post your dundi.conf for both boxes? I'm afraid this message doesn't mean anything to me, but I have about a dozen boxes doing DUNDi peering so I know what the config should look like. But it's basically always worked for me. Regards, - Brad _______________________________________________ --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
