On 6 October 2014 15:31, Matthew Jordan mjor...@digium.com wrote:
On Sun, Oct 5, 2014 at 11:33 AM, Dan Ballance tzewang.do...@gmail.com
wrote:
Hi,
Was this question not appropriate for asterisk-users maybe? Should I
post in
dev instead?
No, I think the question is appropriate for this list. The lack of
immediate response probably had more to do with asking it on a Friday
than anything else :-)
Thanks ever so much for the informative response Matt. And apologies about
the bump over a weekend. I was working over the weekend and forget other
people have a better work-life balance than me! Your input is greatly
appreciated :)
On 4 Oct 2014 15:48, Dan Ballance tzewang.do...@gmail.com wrote:
Hi guys,
I'm building a PoC Asterisk 12 cluster based on a number of guides I've
found on the net. The basic concept is using ARA in conjunction with
DUNDi.
I have set up ARA with pjsip according to this excellent guide here:
https://wiki.asterisk.org/wiki/display/AST/Setting+up+PJSIP+Realtime
This is working nicely, so now I am turning my attention to DUNDi, as
per
this guide here:
http://www.ntegratedsolutions.com/wp-content/uploads/2012/07/Using_DUNDi_with_a_Cluster_of_Asterisk_Servers.pdf
Its seems a really neat solution and I'm keen to implement something
similar, however I believe it was written before the pjsip channel
driver
and I've hit a potential issue I think. The guides for configuring DUNDi
seem to suggest using regcontext in sip.conf:
[general]
regcontext=sipregistration
You don't have to use 'regcontext' in order to have the equivalent
functionality. regcontext is an automatic mechanism to create a NoOp
extension matching each peer's name in a particular context. If you
wanted the same functionality for DUNDi, you could create the same
extensions for each endpoint in pjsip.conf.
I see. I suppose the nice thing about regcontext in combination with the
realtime architecture is it means you don't have to hard code this stuff. I
guess my next step then is to look at creating these NoOp extensions via
the database.
However I can't seem to find an equivalent declaration for pjsip.conf.
So
my questions are:
1) Is there a way to achieve the same functionality with pjsip?
Not automatically, no. If you wanted DUNDi to use a context with
extensions named the same as the endpoints for DUNDi lookups, you
would need to create them yourself.
2) Is DUNDi still being maintained and used? If so, then how should it
be
configured with modern versions of Asterisk?
DUNDi hasn't changed much; hence, the configuration of things for
DUNDi is generally the same between recent versions of Asterisk. The
DUNDi specific portions of configuration would also be similar between
chan_sip and chan_pjsip.
As far as 'maintained and used':
* DUNDi (which is provided by the pbx_dundi module) is in extended
support. That means most development activities for it come from the
Asterisk community as a whole. There is not a lot of active
development that occurs in pbx_dundi, although patches for bugs are
occasionally merged for it.
* DUNDi is used by a number of community members, and has some
interesting applications in certain setups. I don't have any hard
numbers on how many people use it, other than it comes up from time to
time in the issue tracker (which is about the extent of my visibility
for usage).
3) If DUNDi is not really used in modern set-ups, then what are my
alternatives?
I really have searched and read and Googled everything I can but I can't
seem to find anything on configuring DUNDi with pjsip. Hoping one of you
people can point me in the right direction!
You may be the first person to try this out!
Thanks again for this info Matt. Glad to hear that DUNDi is still
maintained. We already have OpenSIPS doing SIP signalling on our network
and I'm trying to avoid needing to add more complexity to that set-up. I
really love the idea of clustered peer-to-peer asterisk instances sharing
registration information with one another - this seems a really neat design
to me.
If I manage to get this proof of concept running I'll blog about it
somewhere so others can learn from my experience. If we actually go ahead
and deploy Asterisk using this technique in production then I will make
sure we help with the maintenance where we can,
all the best,
Dan.
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users