[Asterisk-Users] DUNDi Users

[Aaron Daniel]

If you do a reload pbx_dundi.so, it'll reload the dundi configuration.  If 
you're talking about the strings it returns, if you want to get an 
immediate result and not use the cache, use something like "dundi lookup 
<num> bypass".

Also, if you have separate entry points for each section of the dundi 
numbers, you're going to have to have separate users to identify where the 
call's coming from.  If you only use one iax user, you can only use one 
context.  That's like trying to put a phone in two different contexts... 
where is it supposed to start it's dialing attempts?  If you really want, 
create a context in extensions.conf that includes the other three, because 
that seems to be the functionality you are attempting.

Seems to make sense to me, not sure what's horrible about it :)

On Wed, 14 Jun 2006, Douglas Garstang wrote:

> It has also just become glaringly apparent to me that a 'reload' does not always reload the DUNDi configuation.
> How can I reload DUNDi without stopping/starting Asterisk?
>
>
>> -----Original Message-----
>> From: Douglas Garstang
>> Sent: Wednesday, June 14, 2006 11:00 AM
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: [Asterisk-Users] DUNDi Users
>>
>>
>> I have three Asterisk boxes.
>> Each has the following in dundi.conf:
>>
>> 180net =>
>> dundi_local,0,IAX,dundi:${SECRET}@${IPADDR}/${NUMBER},nopartial
>> 180q =>
>> dundi_q_pbx1,1,IAX,dundi:${SECRET}@${IPADDR}/${NUMBER},nopartial
>> 180q =>
>> dundi_q_pbx2,2,IAX,dundi:${SECRET}@${IPADDR}/${NUMBER},nopartial
>> 180q =>
>> dundi_q_pbx3,3,IAX,dundi:${SECRET}@${IPADDR}/${NUMBER},nopartial
>>
>> My iax.conf on all three Asterisk boxes has this:
>>
>> [dundi]
>> type=user
>> dbsecret=dundi/secret
>> context=dundi_local
>> disallow=all
>> allow=ulaw
>> allow=g729
>>
>> I can do a lookup on pbx2 to find where a number is:
>>
>> hermes*CLI> dundi lookup oe_main at 180q
>>   1.     1
>> IAX2/dundi:IVpqB+nIFnGccXAZhWlbIA at xxx.187.142.232/oe_main (EXISTS)
>>      from 00:0e:0c:a1:92:6f, expires in 0 s
>>   2.     1
>> IAX2/dundi:BhL9b+Xp1AJ6b98kw0KpeQ at xxx.187.142.203/oe_main (EXISTS)
>>      from 00:0e:0c:a1:92:4d, expires in 0 s
>> DUNDi lookup completed in 53 ms
>>
>> However, when I dial the DUNDi path, this is what pbx1 logs
>> on the console:
>>
>> Jun 14 10:51:39 NOTICE[22424]: chan_iax2.c:7215 socket_read:
>> Rejected connect attempt from xxx.187.142.204, request
>> 'oe_main at dundi_local' does not exist
>>
>> I tried adding the contexts to [dundi] in iax.conf:
>>
>> [dundi]
>> type=user
>> dbsecret=dundi/secret
>> context=dundi_local
>> context=dundi_q_pbx1
>> context=dundi_q_pbx2
>> context=dundi_q_pbx3
>> disallow=all
>> allow=ulaw
>> allow=g729
>>
>> However, the call on pbx1 is still routed to the dundi_local
>> context instead of dundi_q_pbx1.
>> Do I have to go and modify dundi.conf, so that every dundi
>> entry uses a different DUNDi user, like this?
>>
>> 180q =>
>> dundi_q_pbx1,1,IAX,dundi1:${SECRET}@${IPADDR}/${NUMBER},nopartial
>> 180q =>
>> dundi_q_pbx2,2,IAX,dundi2:${SECRET}@${IPADDR}/${NUMBER},nopartial
>> 180q =>
>> dundi_q_pbx3,3,IAX,dundi3:${SECRET}@${IPADDR}/${NUMBER},nopartial
>>
>> And then add users dundi1, dundi2 and dundi3 to iax.conf?
>> I sure hope not. What a horrible way to have to do it.
>>
>> Doug.
>>
>>
>>
>>
>> _______________________________________________
>> --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
>

-- 
Aaron Daniel
Computer Systems Technician
Sam Houston State University
amdtech at shsu.edu
(936) 294-4198