[Asterisk-Users] DUNDi Users
Douglas Garstang
dgarstang at oneeighty.com
Wed Jun 14 12:18:00 MST 2006
> -----Original Message-----
> From: Aaron Daniel [mailto:amdtech at shsu.edu]
> Sent: Wednesday, June 14, 2006 12:54 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] DUNDi Users
>
>
> 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 :)
Ooookay. Why is this possible then?
[vmuser] ; Used by voicemail server to authenticate incoming connections
username=vmuser
type=user
auth=rsa
inkeys=pbxsys
context=vmretrieve
context=vmdeposit
context=vm_test
deny=0.0.0.0/0.0.0.0
permit=xxx.187.142.203
permit=xxx.187.142.204
permit=xxx.187.142.232
permit=xxx.187.142.201
disallow = all
allow = gsm
I can open up an IAX connection from the client side to any one of those three contexts on the vm system.
Why is dundi different?
More information about the asterisk-users
mailing list