Watkins, Bradley
2006-Mar-17 13:15 UTC
[Asterisk-Users] Re: DUNDi .... Halfway and CLUSTERING
Do you mean the peristence of connecting a specific phone to a specific server? If so, then it's relatively easy. The ldirectord has a persistence setting that does that. If I'm misunderstanding you, then could you explain further what you mean? Regards, - Brad -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of David Thomas Sent: Friday, March 17, 2006 9:53 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [Asterisk-Users] Re: DUNDi .... Halfway and CLUSTERING Brad, How are you able to overcome the Call-ID stickiness problem when loadbalancing with Ultramonky? As I understand it LVS does not properly support SIP in that it doesn't always use the same source path. regards, David On 3/17/06, Watkins, Bradley <Bradley.Watkins@compuware.com> wrote:> At the moment I'm out of the office, but when I return I'll be certain > to do that. Note that my solution is different from what you are > working on with regexten, though I suspect some of the challenges that > I've faced and overcome are not. I'm actually using UltraMonkey for > load-balancing and failover of the Asterisk boxes, and my dialplan is > set up so that it need not be changed when extensions are added or > removed. I've been meaning for some time to do a write-up of how it > all works, both in the hopes of giving my knowledge back to the > community as well as learning some things that may help me improve the > solution. > > I've had to make a couple of (minor) tweaks to both app_voicemail.c > (to ensure proper password synchronization) and pbx_dundi.c. The > latter is for larger sites(more than one cluster since my clusters are > designed as "buliding blocks" of two Asterisk systems), adding a count > flag to return the number of matching records and the ability to > return a specific record. The former, I suspect, would be unnecessary > if I were using Realtime for voicemail. But I'm not using Realtime > for anything at the moment. > > Anyway, I apologize for not being able to answer you fully right now, > but I've got this set to remind me to follow up on Monday. > > Regards, > - Brad > > -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of JR > Richardson > Sent: Friday, March 17, 2006 12:27 AM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] RE: DUNDi .... Halfway and CLUSTERING > > > 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: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > asterisk-users-request@lists.digium.com > Sent: Thursday, March 16, 2006 9:42 PM > To: asterisk-users@lists.digium.com > Subject: Asterisk-Users Digest, Vol 20, Issue 114 > > Send Asterisk-Users mailing list submissions to > asterisk-users@lists.digium.com > > 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 > > > > The contents of this e-mail are intended for the named addressee only. > It contains information that may be confidential. Unless you are the > named addressee or an authorized designee, you may not copy or use it, > or disclose it to anyone else. If you received it in error please > notify us immediately and then destroy it. > > _______________________________________________ > --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 >_______________________________________________ --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 The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
On 3/17/06, Watkins, Bradley <Bradley.Watkins@compuware.com> wrote:> Do you mean the peristence of connecting a specific phone to a specific > server? If so, then it's relatively easy. The ldirectord has a persistence > setting that does that. If I'm misunderstanding you, then could you explain > further what you mean? >Have a look at this doc from the developers of LVS... http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.services_that_dont_work_yet.html This has been discussed a few times in the SER list. The issue is specific to UDP which includes the majority of SIP endpoints. Currently LVS does not always send reply packets from the addresses that they were received on. This breaks SIP dialog. If you have found a way around this, that would be great. Please let me know. David