[asterisk-users] Re: DUNDi with SIP

[Douglas Garstang]

> -----Original Message-----
> From: Aaron Daniel [mailto:amdtech at shsu.edu]
> Sent: Wednesday, August 02, 2006 4:02 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
> 
> 
> On Wed, 2006-08-02 at 15:52 -0600, Douglas Garstang wrote:
> > Well yes, it looked dubious to me too, although I can't 
> find the syntaxt documented anywhere.
> > However, that's what DUNDis giving me as a path to the phone!
> > 
> > Something is screwed with DUNDi and SIP. Has ANYONE 
> actually implemnted it?
> > I can't find it documented anywhere
> > 
> > Doug.
> 
> DUNDi gives you only what you give it to give you.  You're 
> the one that
> needs to set the dial string correctly in DUNDi to get one back that
> works.  DUNDi is only as automatic as you let it be.
> 
> This is what ours looks like.  We don't use the iax versions (mainly
> cause I want a homogenous SIP system), but we have entries in sip.conf
> include files for each of the servers so we just dial
> ${server}/${number}.  This has been working for us for about 2 months
> now, pretty much flawlessly as long as the phone's registered.
> 
> e164 => dundi-extens,0,SIP,scm1/${NUMBER}
> e164-iax => dundi-extens,0,IAX2,dundi:${SECRET}@scm1/${NUMBER}
> internal => dundi-extens,0,SIP,scm1/${NUMBER}
> internal-iax => dundi-extens,0,IAX2,dundi:${SECRET}@scm1/${NUMBER}
> 
> [scm1]
> type=friend
> secret=p4ssw0rd
> insecure=very
> context=incoming
> host=scm1.shsu.edu
> qualify=yes
> nat=no

Aaron, while not really sure what I was doing, but extending beyond your example, I gave this a shot:

dundi.conf:
180netsip => global_dundi_local,0,SIP,dundisip1/${NUMBER}
180netsip => global_dundi_local,0,SIP,dundisip2/${NUMBER}

sip.conf:
[dundisip1]
type=friend
secret=password
insecure=very
context=global_dundi_local
host=labpbx1.ipt.twoeighty.com
qualify=yes

[dundisip2]
type=friend
secret=password
insecure=very
context=global_dundi_local
host=labpbx2.ipt.twoeighty.com
qualify=yes

A CLI lookup looks better...

*CLI> dundi lookup 9220370 at 180netsip
  1.     0 SIP/dundisip2/9220370 (EXISTS|CANMATCH)
     from 00:14:22:1e:2a:d0, expires in 0 s
DUNDi lookup completed in 107 ms

However, my dial still fails...

[Aug  2 16:42:44]     -- AGI Script Executing Application: (Dial) Options: (SIP/dundisip2/9220370)
[Aug  2 16:42:44]     -- Called dundisip2/9220370
[Aug  2 16:42:44] NOTICE[10474]: chan_sip.c:9685 handle_response_invite: Failed to authenticate on INVITE to '"Chocolate Chip" <sip:3254101 at xxx.yyy.142.162>;tag=as4f13a2f1'
[Aug  2 16:42:44]     -- SIP/dundisip2-7b30 is circuit-busy