[asterisk-users] Re: DUNDi with SIP
Douglas Garstang
dgarstang at oneeighty.com
Wed Aug 2 16:16:17 MST 2006
Bradley,
I changed the type from friend to peer in sip.conf...
[dundisip1]
type=peer
secret=password
insecure=very
context=global_dundi_local
host=labpbx1.ipt.twoeighty.com
qualify=yes
[dundisip2]
type=peer
secret=password
insecure=very
context=global_dundi_local
host=labpbx2.ipt.twoeighty.com
qualify=yes
but that just yielded the same error...
[Aug 2 17:07:51] NOTICE[10971]: chan_sip.c:9685 handle_response_invite: Failed to authenticate on INVITE to '"Chocolate Chip" <sip:3254101 at xxx.yyy.142.162>;tag=as5e6e3efe'
Btw, here's a sip trace between the asterisk boxes...
Capturing on eth0
1 0.000000 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE sip:9220370 at labpbx1.ipt.twoeighty.com;user=phone, with session description
2 0.000311 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP Status: 407 Proxy Authentication Required
3 0.177497 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: ACK sip:9220370 at labpbx1.ipt.oneeighty.com
4 0.329036 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE sip:9220370 at labpbx1.ipt.twoeighty.com;user=phone, with session description
5 0.329492 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP Status: 100 Trying
6 0.643513 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP/SDP Request: INVITE sip:9220370 at labpbx2.ipt.twoeighty.com, with session description
7 0.644104 xxx.yyy.142.163 -> xxx.yyy.142.162 SIP Status: 407 Proxy Authentication Required
8 0.644356 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP Request: ACK sip:9220370 at labpbx2.ipt.oneeighty.com
9 0.647990 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP/SDP Status: 200 OK, with session description
10 0.806136 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: ACK sip:9220370 at xxx.yyy.142.162
11 2.280664 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: BYE sip:9220370 at xxx.yyy.142.162
12 2.280780 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP Status: 200 OK
You can see that the first system doesn't resend the INVITE with the auth credentials as requested.
So, then I also put the username field, and sip.conf now looks like this:
[dundisip1]
type=peer
username=dundisip1
secret=password
insecure=very
context=global_dundi_local
host=labpbx1.ipt.twoeighty.com
qualify=yes
[dundisip2]
type=peer
username=dundisip2
secret=password
insecure=very
context=global_dundi_local
host=labpbx2.ipt.twoeeighty.com
qualify=yes
and with dundi.conf as:
180netsip => global_dundi_local,0,SIP,dundisip1/${NUMBER}
180netsip => global_dundi_local,0,SIP,dundisip2/${NUMBER}
A CLI lookup still yields:
*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 130 ms
HOWEVER, at attempt to dial results in this now:
[Aug 2 17:14:00] WARNING[11178]: chan_sip.c:9696 handle_response_invite: Forbidden - wrong password on authentication for INVITE to '"Chocolate Chip" <sip:3254101 at xxx.yyy.142.162>;tag=as6090e60f'
And here's the SIP trace for THAT!
1 0.000000 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE sip:9220370 at labpbx1.ipt.twoeighty.com;user=phone, with session description
2 0.000311 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP Status: 407 Proxy Authentication Required
3 0.158008 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: ACK sip:9220370 at labpbx1.ipt.twoeighty.com
4 0.295054 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE sip:9220370 at labpbx1.ipt.twoeighty.com;user=phone, with session description
5 0.300557 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP Status: 100 Trying
6 0.602324 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP/SDP Request: INVITE sip:9220370 at labpbx2.ipt.twoeighty.com, with session description
7 0.603002 xxx.yyy.142.163 -> xxx.yyy.142.162 SIP Status: 407 Proxy Authentication Required
8 0.603303 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP Request: ACK sip:9220370 at labpbx2.ipt.twoeighty.com
9 0.603485 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP/SDP Request: INVITE sip:9220370 at labpbx2.ipt.twoeighty.com, with session description
10 0.604251 xxx.yyy.142.163 -> xxx.yyy.142.162 SIP Status: 403 Forbidden
11 0.604553 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP Request: ACK sip:9220370 at labpbx2.ipt.twoeighty.com
12 0.608324 xxx.yyy.142.162 -> xxx.yyy.128.18 SIP/SDP Status: 200 OK, with session description
13 0.749668 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: ACK sip:9220370 at xxx.yyy.142.162
And on the second Asterisk console we have logged:
Aug 2 17:13:57 NOTICE[29764]: chan_sip.c:10469 handle_request_invite: Failed to authenticate user "Chocolate Chip" <sip:3254101 at xxx.yyy.142.162>;tag=as6090e60f
Ugh... not having much luck with this...
> -----Original Message-----
> From: Watkins, Bradley [mailto:Bradley.Watkins at compuware.com]
> Sent: Wednesday, August 02, 2006 5:01 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> Try putting a username= in the peer (BTW, use peer not friend)
> definitions. You appear to be attempting to authenticate as the
> originating callerid (3254101).
>
> - Brad
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Douglas
> Garstang
> Sent: Wednesday, August 02, 2006 6:45 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
> > -----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
>
>
> _______________________________________________
> --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
>
More information about the asterisk-users
mailing list