Steve, I don't see how it could possibly work. The second system sees a connection from dundisip1 on labpbx2, so it then looks at the dundisip2 entry because it's matching against the host. It then looks at the username, but it's dundisip2... which doesn't match dundisip1, and it fails the call.
> -----Original Message----- > From: Steve Totaro [mailto:[EMAIL PROTECTED] > Sent: Friday, August 04, 2006 8:51 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] Re: DUNDi with SIP > > > Works fine for me. > > Douglas Garstang wrote: > > Didn't work Brad. I changed fromuser to dundisip1 from > dundisip2. The > > first Asterisk box sends dundisip1. > > > > [dundisip1] > > type=friend > > secret=password > > insecure=very > > context=global_dundi_local > > host=labpbx1.ipt.oneeighty.com > > qualify=no > > username=dundisip1 > > fromuser=dundisip1 > > > > [dundisip2] > > type=friend > > secret=password > > insecure=very > > context=global_dundi_local > > host=labpbx2.ipt.oneeighty.com > > qualify=no > > username=dundisip2 > > fromuser=dundisip1 > > > > > > My sip.conf now has: > > > > but at the other end, I get: > > > > Aug 4 08:33:25 NOTICE[20569]: chan_sip.c:10469 > handle_request_invite: > > Failed to authenticate user "Chocolate Chip" > > <sip:[EMAIL PROTECTED]>;tag=as1345d31c > > > > I assume because the call is coming in from [dundisip2]. It > then looks > > for a username of 'dundisip2' but it's receiving dundisip1. > > > > No wonder the sip.conf and iax.conf files drive me nuts! > You spend all > > your time going in circles! > > > > Doug. > > > > > > > > -----Original Message----- > > *From:* Watkins, Bradley [mailto:[EMAIL PROTECTED] > > *Sent:* Friday, August 04, 2006 4:20 AM > > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > > *Subject:* RE: [asterisk-users] Re: DUNDi with SIP > > > > Easy, you change the fromuser=dundisip2 line to > > fromuser=dundisip1. You're just matching the destination peer > > (dunsip2, labpbx2.ipt.oneeighty.com) and sending the configured > > fromuser. > > > > - Brad > > > > > -------------------------------------------------------------- > ---------- > > *From:* [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] *On Behalf Of > > *Douglas Garstang > > *Sent:* Thursday, August 03, 2006 4:18 PM > > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > > *Subject:* RE: [asterisk-users] Re: DUNDi with SIP > > > > *scream* I just got it to work with this... > > > > 180netsip => > global_dundi_local,0,SIP,dundisip1/${NUMBER},nopartial > > 180netsip => > global_dundi_local,0,SIP,dundisip2/${NUMBER},nopartial > > > > [dundisip1] > > type=friend > > secret=password > > insecure=very > > context=global_dundi_local > > host=labpbx1.ipt.oneeighty.com > > qualify=no > > username=dundisip1 > > fromuser=dundisip1 > > > > [dundisip2] > > type=friend > > secret=password > > insecure=very > > context=global_dundi_local > > host=labpbx2.ipt.oneeighty.com > > qualify=no > > username=dundisip2 > > fromuser=dundisip2 > > It works... but the first system sends dundisip2 as the authid, > > not dundisip1. I assume that's because it matches the host > > labpbx2. Well, it should be sending dundisip1.... how > can I get it > > to do that? > > > > Doug. > > > > -----Original Message----- > > *From:* Watkins, Bradley > [mailto:[EMAIL PROTECTED] > > *Sent:* Thursday, August 03, 2006 2:06 PM > > *To:* Asterisk Users Mailing List - Non-Commercial > Discussion > > *Subject:* RE: [asterisk-users] Re: DUNDi with SIP > > > > I forget if this does what you want, but try adding > a fromuser > > setting to yoyr peer entries. > > > > - Brad > > > > -----Original Message----- > > From: Douglas Garstang [mailto:[EMAIL PROTECTED] > > Sent: Thu Aug 03 15:58:50 2006 > > To: Asterisk Users Mailing List - > Non-Commercial Discussion > > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > > > Brad... > > > > Here's the INVITE that the second asterisk box receives from > > the first Asterisk box, after the second asterisk > box sends a > > Proxy auth message to the first. The first sends > the dundisip > > userid, but for some reason the second asterisk box is > > matching it against the From: 3254101 address. Do I > need more > > than just the two sip.conf entries, dundisip, and dundisip2 > > as type=peer? > > > > Anyone? > > > > Doug. > > > > > > > > <-- SIP read from xxx.yyy.142.162:5060: > > > INVITE sip:[EMAIL PROTECTED] SIP/2.0 > > > Via: SIP/2.0/UDP > > xxx.yyy.142.162:5060;branch=z9hG4bK047028fa;rport > > > From: "Chocolate Chip" > > <sip:[EMAIL PROTECTED]>;tag=as34445cb0 > > > To: <sip:[EMAIL PROTECTED]> > > > Contact: <sip:[EMAIL PROTECTED]> > > > Call-ID: [EMAIL PROTECTED] > > > CSeq: 103 INVITE > > > User-Agent: Asterisk PBX > > > Max-Forwards: 70 > > > Remote-Party-ID: "Chocolate Chip" > > > <sip:[EMAIL PROTECTED]>;privacy=off;screen=no > > > Proxy-Authorization: Digest username="dundisip2", > > > realm="ipt.twoeighty.com", algorithm=MD5, > > > uri="sip:[EMAIL PROTECTED]", > > > nonce="012b66e9", > > > response="bd5b3881afd0bdb827915a9eeb97dcd8", opaque="" > > > Date: Thu, 03 Aug 2006 19:52:26 GMT > > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, > SUBSCRIBE, > > NOTIFY > > > Content-Type: application/sdp > > > Content-Length: 269 > > > > > > v=0 > > > o=root 16558 16559 IN IP4 xxx.yyy.142.162 > > > s=session > > > c=IN IP4 xxx.yyy.142.162 > > > t=0 0 > > > m=audio 28454 RTP/AVP 0 18 101 > > > a=rtpmap:0 PCMU/8000 > > > a=rtpmap:18 G729/8000 > > > a=fmtp:18 annexb=no > > > a=rtpmap:101 telephone-event/8000 > > > a=fmtp:101 0-16 > > > a=silenceSupp:off - - - - > > _______________________________________________ > > --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. > > > > 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 > > > > _______________________________________________ > --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
