RE: [asterisk-users] Re: DUNDi with SIP
Well, after 24 hours I'm still trying to get SIP trunking to work. I'm going in
circles and it's driving me nuts. Here's my latest sip.conf, that I have on
both systems.
system 1 sends dundisip1_in as the userid to system 2. System 2 asks for proxy
auth. System 1 sends an ACK and doesn't do anything else. It then logs on the
console:
[Aug 4 10:19:59] NOTICE[30136]: chan_sip.c:9685 handle_response_invite: Failed
to authenticate on INVITE to '"Chocolate Chip" ;tag=as7da2967e'
:(
[dundisip1]
type=peer
secret=password
insecure=very
host=labpbx1.ipt.twoeighty.com
qualify=no
fromuser=dundisip1_in
[dundisip2]
type=peer
secret=password
insecure=very
host=labpbx2.ipt.twoeighty.com
qualify=no
fromuser=dundisip2_in
[dundisip1_in]
type=user
username=dundisip1_in
secret=password
insecure=very
context=global_dundi_local
host=labpbx2.ipt.twoeighty.com
qualify=no
[dundisip2_in]
type=user
username=dundisip2_in
secret=password
insecure=very
context=global_dundi_local
host=labpbx1.ipt.twoeighty.com
qualify=no
> -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"
> > ;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-
> >
RE: [asterisk-users] Re: DUNDi with SIP
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"
> > ;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
> >
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"
;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"
;tag=as34445cb0
> To:
> Contact:
> Call-ID: [EMAIL PROTECTED]
> CSeq: 103 INVITE
> User-Agent: Asterisk PBX
> Max-Forwards: 70
> Remote-Party-ID: "Chocolate Chip"
> ;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=I
RE: [asterisk-users] Re: DUNDi with SIP
Title: RE: [asterisk-users] Re: DUNDi with SIP
Didn't
work Brad. I changed fromuser to dundisip1 from dundisip2. The first Asterisk
box sends dundisip1.
[dundisip1]
type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx1.ipt.oneeighty.comqualify=nousername=dundisip1fromuser=dundisip1
[dundisip2]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx2.ipt.oneeighty.comqualify=nousername=dundisip2fromuser=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"
;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 AMTo: Asterisk Users Mailing List - Non-Commercial
DiscussionSubject: 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
GarstangSent: Thursday, August 03, 2006 4:18 PMTo:
Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE:
[asterisk-users] Re: DUNDi with SIP
*scream* I just got it to work with
this...
180netsip =>
global_dundi_local,0,SIP,dundisip1/${NUMBER},nopartial180netsip =>
global_dundi_local,0,SIP,dundisip2/${NUMBER},nopartial
[dundisip1]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx1.ipt.oneeighty.comqualify=nousername=dundisip1fromuser=dundisip1
[dundisip2]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx2.ipt.oneeighty.comqualify=nousername=dundisip2fromuser=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 PMTo: Asterisk Users Mailing List - Non-Commercial
DiscussionSubject: 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 2006To: Asterisk Users
Mailing List - Non-Commercial
DiscussionSubject: RE:
[asterisk-users] Re: DUNDi with SIPBrad...Here's the INVITE
that the second asterisk box receives fromthe first Asterisk box, after
the second asterisk box sends aProxy auth message to the first. The
first sends the dundisipuserid, but for some reason the second asterisk
box ismatching it against the From: 3254101 address. Do I need
morethan just the two sip.conf entries, dundisip, and dundisip2as
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" ;tag=as34445cb0> To:
> Contact:
> Call-ID:
[EMAIL PROTECTED]> CSeq: 103
INVITE> User-Agent: Asterisk PBX> Max-Forwards: 70>
Remote-Party-ID: "Chocolate Chip">
;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
listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe
contents of this e-mail are intended for
RE: [asterisk-users] Re: DUNDi with SIP
Title: 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
GarstangSent: Thursday, August 03, 2006 4:18 PMTo:
Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE:
[asterisk-users] Re: DUNDi with SIP
*scream* I just got it to work with
this...
180netsip =>
global_dundi_local,0,SIP,dundisip1/${NUMBER},nopartial180netsip =>
global_dundi_local,0,SIP,dundisip2/${NUMBER},nopartial
[dundisip1]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx1.ipt.oneeighty.comqualify=nousername=dundisip1fromuser=dundisip1
[dundisip2]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx2.ipt.oneeighty.comqualify=nousername=dundisip2fromuser=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 PMTo: Asterisk Users Mailing List - Non-Commercial
DiscussionSubject: 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 2006To: Asterisk Users Mailing
List - Non-Commercial
DiscussionSubject: RE:
[asterisk-users] Re: DUNDi with SIPBrad...Here's the INVITE
that the second asterisk box receives fromthe first Asterisk box, after
the second asterisk box sends aProxy auth message to the first. The first
sends the dundisipuserid, but for some reason the second asterisk box
ismatching it against the From: 3254101 address. Do I need morethan
just the two sip.conf entries, dundisip, and dundisip2as
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" ;tag=as34445cb0> To:
> Contact:
> Call-ID:
[EMAIL PROTECTED]> CSeq: 103
INVITE> User-Agent: Asterisk PBX> Max-Forwards: 70>
Remote-Party-ID: "Chocolate Chip">
;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
listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe
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
RE: [asterisk-users] Re: DUNDi with SIP
Title: RE: [asterisk-users] Re: DUNDi with SIP
*scream* I just got it to work with
this...
180netsip =>
global_dundi_local,0,SIP,dundisip1/${NUMBER},nopartial180netsip =>
global_dundi_local,0,SIP,dundisip2/${NUMBER},nopartial
[dundisip1]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx1.ipt.oneeighty.comqualify=nousername=dundisip1fromuser=dundisip1
[dundisip2]type=friendsecret=passwordinsecure=verycontext=global_dundi_localhost=labpbx2.ipt.oneeighty.comqualify=nousername=dundisip2fromuser=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 PMTo: Asterisk Users Mailing List - Non-Commercial
DiscussionSubject: 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 2006To: Asterisk Users Mailing
List - Non-Commercial
DiscussionSubject: RE:
[asterisk-users] Re: DUNDi with SIPBrad...Here's the INVITE
that the second asterisk box receives fromthe first Asterisk box, after
the second asterisk box sends aProxy auth message to the first. The first
sends the dundisipuserid, but for some reason the second asterisk box
ismatching it against the From: 3254101 address. Do I need morethan
just the two sip.conf entries, dundisip, and dundisip2as
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" ;tag=as34445cb0> To:
> Contact:
> Call-ID:
[EMAIL PROTECTED]> CSeq: 103
INVITE> User-Agent: Asterisk PBX> Max-Forwards: 70>
Remote-Party-ID: "Chocolate Chip">
;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
listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe
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
RE: [asterisk-users] Re: DUNDi with SIP
Title: RE: [asterisk-users] Re: DUNDi with SIP I don't think that will do it. SInce I started with Asterisk a year ago, I've wrestled the ENTIRE time with the sip conf file. It really makes no sense to me after doing this 8-5 for 10 months now. The first system is sending the correct user id. Do I need two entries in dundi.conf? Do I need two or four (in and out) users in sip.conf? Should they be peers or friends? :( -Original Message-From: Watkins, Bradley [mailto:[EMAIL PROTECTED]Sent: Thursday, August 03, 2006 2:06 PMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: 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 2006To: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [asterisk-users] Re: DUNDi with SIPBrad...Here's the INVITE that the second asterisk box receives fromthe first Asterisk box, after the second asterisk box sends aProxy auth message to the first. The first sends the dundisipuserid, but for some reason the second asterisk box ismatching it against the From: 3254101 address. Do I need morethan just the two sip.conf entries, dundisip, and dundisip2as 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" ;tag=as34445cb0> To: > Contact: > Call-ID: [EMAIL PROTECTED]> CSeq: 103 INVITE> User-Agent: Asterisk PBX> Max-Forwards: 70> Remote-Party-ID: "Chocolate Chip"> ;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 listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe 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
RE: [asterisk-users] Re: DUNDi with SIP
Title: 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" ;tag=as34445cb0 > To: > Contact: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 INVITE > User-Agent: Asterisk PBX > Max-Forwards: 70 > Remote-Party-ID: "Chocolate Chip" > ;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. ___ --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
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" ;tag=as34445cb0 > To: > Contact: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 INVITE > User-Agent: Asterisk PBX > Max-Forwards: 70 > Remote-Party-ID: "Chocolate Chip" > ;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
RE: [asterisk-users] Re: DUNDi with SIP
Brad, Here's the invite that the first Asterisk box sends to the second Asterisk box. I see no reference to dundisip1 or dundisip2 in there... I'm not even sure that SIP can support using different From: and authid's? [Aug 3 12:45:49] Reliably Transmitting (no NAT) to xxx.yyy.142.163:5060: INVITE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.142.162:5060;branch=z9hG4bK280b3a7d;rport From: "Chocolate Chip" ;tag=as45fbdb6f To: Contact: Call-ID: [EMAIL PROTECTED] CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 70 Remote-Party-ID: "Chocolate Chip" ;privacy=off;screen=no Date: Thu, 03 Aug 2006 18:45:49 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length: 269 v=0 o=root 16089 16089 IN IP4 xxx.yyy.142.162 s=session c=IN IP4 xxx.yyy.142.162 t=0 0 m=audio 32738 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 - - - - And once again, here's sip.conf: [dundisip1] type=peer username=dundisip1 secret=password insecure=very context=global_dundi_local host=labpbx1.ipt.oneeighty.com qualify=yes [dundisip2] type=peer username=dundisip2 secret=password insecure=very context=global_dundi_local host=labpbx2.ipt.oneeighty.com qualify=yes > -Original Message- > From: Watkins, Bradley [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 03, 2006 12:29 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > > I'm basically trying to figure out why you aren't > authenticating properly. > > When you posted the [peer] sections of your sip.conf, were > the secret= lines literal, or did you replace the actual > secret with "password"? > > - Brad > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Douglas Garstang > Sent: Thursday, August 03, 2006 11:43 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > Thanks Bradley. > > Here's a full sip console trace on the first pbx box. > > xxx.yyy.128.18(phone 3254101): Originating phone, registered on pbx1. > xxx.yyy.142.162: pbx1 > xxx.yyy.142.163: pbx2 > > Do you know what you are looking for? > > Doug. > > [Aug 3 09:40:28] > <-- SIP read from xxx.yyy.128.18:5060: > INVITE sip:[EMAIL PROTECTED];user=phone SIP/2.0 > Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: > CSeq: 1 INVITE > Call-ID: [EMAIL PROTECTED] > Contact: > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, > SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER > User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 > Supported: 100rel,replace > Allow-Events: talk,hold,conference > Max-Forwards: 70 > Content-Type: application/sdp > Content-Length: 229 > > v=0 > o=- 1154619309 1154619309 IN IP4 xxx.yyy.128.18 s=Polycom IP > Phone c=IN IP4 xxx.yyy.128.18 t=0 0 a=sendrecv m=audio 2260 > RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 > a=rtpmap:18 G729/8000 > a=rtpmap:101 telephone-event/8000 > > [Aug 3 09:40:28] --- (14 headers 10 lines)[Aug 3 09:40:28] > --- [Aug 3 09:40:28] Using INVITE request as basis request - > [EMAIL PROTECTED] > [Aug 3 09:40:28] Sending to xxx.yyy.128.18 : 5060 (non-NAT) > [Aug 3 09:40:28] Reliably Transmitting (no NAT) to > xxx.yyy.128.18:5060: > SIP/2.0 407 Proxy Authentication Required > Via: SIP/2.0/UDP > xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58;received=xxx.yyy.128.18 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: ;tag=as7757655f > Call-ID: [EMAIL PROTECTED] > CSeq: 1 INVITE > User-Agent: Asterisk PBX > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY > Contact: > Proxy-Authenticate: Digest realm="ipt.twoeighty.com", nonce="673c57e6" > Content-Length: 0 > > > --- > [Aug 3 09:40:28] Scheduling destruction of call > '[EMAIL PROTECTED]' in 15000 ms [Aug > 3 09:40:28] Found user '3254101' > [Aug 3 09:40:28] > <-- SIP read from xxx.yyy.128.18:5060: > ACK sip:[EMAIL PROTECTED] SIP/2.0 > Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: ;tag=as7757655f > CSeq: 1 ACK > Call-ID: [EMAIL PROTECTED] > Contact: > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, > SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER > User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 > Max-Forwards: 70 > Content-
RE: [asterisk-users] Re: DUNDi with SIP
Brad, Not sure what you mean... I had literally 'secret=password' password being 'password' for testing purposes... > -Original Message- > From: Watkins, Bradley [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 03, 2006 12:29 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > > I'm basically trying to figure out why you aren't > authenticating properly. > > When you posted the [peer] sections of your sip.conf, were > the secret= lines literal, or did you replace the actual > secret with "password"? > > - Brad > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Douglas Garstang > Sent: Thursday, August 03, 2006 11:43 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > Thanks Bradley. > > Here's a full sip console trace on the first pbx box. > > xxx.yyy.128.18(phone 3254101): Originating phone, registered on pbx1. > xxx.yyy.142.162: pbx1 > xxx.yyy.142.163: pbx2 > > Do you know what you are looking for? > > Doug. > > [Aug 3 09:40:28] > <-- SIP read from xxx.yyy.128.18:5060: > INVITE sip:[EMAIL PROTECTED];user=phone SIP/2.0 > Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: > CSeq: 1 INVITE > Call-ID: [EMAIL PROTECTED] > Contact: > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, > SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER > User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 > Supported: 100rel,replace > Allow-Events: talk,hold,conference > Max-Forwards: 70 > Content-Type: application/sdp > Content-Length: 229 > > v=0 > o=- 1154619309 1154619309 IN IP4 xxx.yyy.128.18 s=Polycom IP > Phone c=IN IP4 xxx.yyy.128.18 t=0 0 a=sendrecv m=audio 2260 > RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 > a=rtpmap:18 G729/8000 > a=rtpmap:101 telephone-event/8000 > > [Aug 3 09:40:28] --- (14 headers 10 lines)[Aug 3 09:40:28] > --- [Aug 3 09:40:28] Using INVITE request as basis request - > [EMAIL PROTECTED] > [Aug 3 09:40:28] Sending to xxx.yyy.128.18 : 5060 (non-NAT) > [Aug 3 09:40:28] Reliably Transmitting (no NAT) to > xxx.yyy.128.18:5060: > SIP/2.0 407 Proxy Authentication Required > Via: SIP/2.0/UDP > xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58;received=xxx.yyy.128.18 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: ;tag=as7757655f > Call-ID: [EMAIL PROTECTED] > CSeq: 1 INVITE > User-Agent: Asterisk PBX > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY > Contact: > Proxy-Authenticate: Digest realm="ipt.twoeighty.com", nonce="673c57e6" > Content-Length: 0 > > > --- > [Aug 3 09:40:28] Scheduling destruction of call > '[EMAIL PROTECTED]' in 15000 ms [Aug > 3 09:40:28] Found user '3254101' > [Aug 3 09:40:28] > <-- SIP read from xxx.yyy.128.18:5060: > ACK sip:[EMAIL PROTECTED] SIP/2.0 > Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: ;tag=as7757655f > CSeq: 1 ACK > Call-ID: [EMAIL PROTECTED] > Contact: > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, > SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER > User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 > Max-Forwards: 70 > Content-Length: 0 > > > [Aug 3 09:40:28] --- (11 headers 0 lines)[Aug 3 09:40:28] --- > [Aug 3 09:40:28] > <-- SIP read from xxx.yyy.128.18:5060: > INVITE sip:[EMAIL PROTECTED];user=phone SIP/2.0 > Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bK23dd36ae56C5E669 > From: "Chocolate Chip" > ;tag=6140575F-F74900CC > To: > CSeq: 2 INVITE > Call-ID: [EMAIL PROTECTED] > Contact: > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, > SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER > User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 > Supported: 100rel,replace > Allow-Events: talk,hold,conference > Proxy-Authorization: Digest username="3254101", > realm="ipt.twoeighty.com", nonce="673c57e6", > uri="sip:[EMAIL PROTECTED];user=phone", > response="9d5875c8a16dfdf29ac5a43a02e44eec", algorithm=MD5 > Max-Forwards: 70 > Content-Type: application/sdp > Content-Length: 229 > > v=0 > o=- 1154619309 1154619309 IN IP4 xxx.yyy.128.18 > s=Polycom IP Phone > c=IN IP4 xxx.yyy.128.18 > t=0 0 > a=sendrecv > m=audio 2260 RTP/AVP 0 18 101 > a=rtpmap:0 PCMU/8000 &g
RE: [asterisk-users] Re: DUNDi with SIP
I'm basically trying to figure out why you aren't authenticating properly. When you posted the [peer] sections of your sip.conf, were the secret= lines literal, or did you replace the actual secret with "password"? - Brad -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Garstang Sent: Thursday, August 03, 2006 11:43 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [asterisk-users] Re: DUNDi with SIP Thanks Bradley. Here's a full sip console trace on the first pbx box. xxx.yyy.128.18(phone 3254101): Originating phone, registered on pbx1. xxx.yyy.142.162: pbx1 xxx.yyy.142.163: pbx2 Do you know what you are looking for? Doug. [Aug 3 09:40:28] <-- SIP read from xxx.yyy.128.18:5060: INVITE sip:[EMAIL PROTECTED];user=phone SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 From: "Chocolate Chip" ;tag=6140575F-F74900CC To: CSeq: 1 INVITE Call-ID: [EMAIL PROTECTED] Contact: Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 Supported: 100rel,replace Allow-Events: talk,hold,conference Max-Forwards: 70 Content-Type: application/sdp Content-Length: 229 v=0 o=- 1154619309 1154619309 IN IP4 xxx.yyy.128.18 s=Polycom IP Phone c=IN IP4 xxx.yyy.128.18 t=0 0 a=sendrecv m=audio 2260 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 [Aug 3 09:40:28] --- (14 headers 10 lines)[Aug 3 09:40:28] --- [Aug 3 09:40:28] Using INVITE request as basis request - [EMAIL PROTECTED] [Aug 3 09:40:28] Sending to xxx.yyy.128.18 : 5060 (non-NAT) [Aug 3 09:40:28] Reliably Transmitting (no NAT) to xxx.yyy.128.18:5060: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58;received=xxx.yyy.128.18 From: "Chocolate Chip" ;tag=6140575F-F74900CC To: ;tag=as7757655f Call-ID: [EMAIL PROTECTED] CSeq: 1 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: Proxy-Authenticate: Digest realm="ipt.twoeighty.com", nonce="673c57e6" Content-Length: 0 --- [Aug 3 09:40:28] Scheduling destruction of call '[EMAIL PROTECTED]' in 15000 ms [Aug 3 09:40:28] Found user '3254101' [Aug 3 09:40:28] <-- SIP read from xxx.yyy.128.18:5060: ACK sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bKeac2a6619BA84D58 From: "Chocolate Chip" ;tag=6140575F-F74900CC To: ;tag=as7757655f CSeq: 1 ACK Call-ID: [EMAIL PROTECTED] Contact: Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 Max-Forwards: 70 Content-Length: 0 [Aug 3 09:40:28] --- (11 headers 0 lines)[Aug 3 09:40:28] --- [Aug 3 09:40:28] <-- SIP read from xxx.yyy.128.18:5060: INVITE sip:[EMAIL PROTECTED];user=phone SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.128.18;branch=z9hG4bK23dd36ae56C5E669 From: "Chocolate Chip" ;tag=6140575F-F74900CC To: CSeq: 2 INVITE Call-ID: [EMAIL PROTECTED] Contact: Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.3.0067 Supported: 100rel,replace Allow-Events: talk,hold,conference Proxy-Authorization: Digest username="3254101", realm="ipt.twoeighty.com", nonce="673c57e6", uri="sip:[EMAIL PROTECTED];user=phone", response="9d5875c8a16dfdf29ac5a43a02e44eec", algorithm=MD5 Max-Forwards: 70 Content-Type: application/sdp Content-Length: 229 v=0 o=- 1154619309 1154619309 IN IP4 xxx.yyy.128.18 s=Polycom IP Phone c=IN IP4 xxx.yyy.128.18 t=0 0 a=sendrecv m=audio 2260 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 [Aug 3 09:40:28] --- (15 headers 10 lines)[Aug 3 09:40:28] --- [Aug 3 09:40:28] Using INVITE request as basis request - [EMAIL PROTECTED] [Aug 3 09:40:28] Sending to xxx.yyy.128.18 : 5060 (non-NAT) [Aug 3 09:40:28] Found user '3254101' [Aug 3 09:40:28] Found RTP audio format 0 [Aug 3 09:40:28] Found RTP audio format 18 [Aug 3 09:40:28] Found RTP audio format 101 [Aug 3 09:40:28] Peer audio RTP is at port xxx.yyy.128.18:2260 [Aug 3 09:40:28] Found description format PCMU [Aug 3 09:40:28] Found description format G729 [Aug 3 09:40:28] Found description format telephone-event [Aug 3 09:40:28] Capabilities: us - 0x104 (ulaw|g729), peer - audio=0x104 (ulaw|g729)/video=0x0 (nothing), combined - 0x104 (ulaw|g729) [Aug 3 09:40:28] Non-codec capabilities: us - 0x1 (telephone-event), peer - 0x1 (telephone-event), combined - 0x1 (telephone-event) [Aug 3 09:40:28] Looking for 9220370 in pbx_betty_start (domain labpbx1.ipt.twoeighty.com) [Aug 3 09:40:28] list_route: hop: [
RE: [asterisk-users] Re: DUNDi with SIP
- Using INVITE request as basis request - [EMAIL PROTECTED] Sending to xxx.yyy.142.162 : 5060 (NAT) Reliably Transmitting (no NAT) to xxx.yyy.142.162:5060: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP xxx.yyy.142.162:5060;branch=z9hG4bK23000840;rport;received=xxx.yyy.142.162 From: "Chocolate Chip" ;tag=as097cbc86 To: ;tag=as004358bd Call-ID: [EMAIL PROTECTED] CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: Proxy-Authenticate: Digest realm="ipt.twoeighty.com", nonce="122095ae" Content-Length: 0 --- Scheduling destruction of call '[EMAIL PROTECTED]' in 15000 ms Found user '3254101' <-- SIP read from xxx.yyy.142.162:5060: ACK sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.142.162:5060;branch=z9hG4bK23000840;rport From: "Chocolate Chip" ;tag=as097cbc86 To: ;tag=as004358bd Contact: Call-ID: [EMAIL PROTECTED] CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Remote-Party-ID: "Chocolate Chip" ;privacy=off;screen=no Content-Length: 0 --- (11 headers 0 lines)--- <-- 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=z9hG4bK188cc77a;rport From: "Chocolate Chip" ;tag=as097cbc86 To: Contact: Call-ID: [EMAIL PROTECTED] CSeq: 103 INVITE User-Agent: Asterisk PBX Max-Forwards: 70 Remote-Party-ID: "Chocolate Chip" ;privacy=off;screen=no Proxy-Authorization: Digest username="dundisip2", realm="ipt.twoeighty.com", algorithm=MD5, uri="sip:[EMAIL PROTECTED]", nonce="122095ae", response="c3812ae6a639df3827b26ff969acad23", opaque="" Date: Thu, 03 Aug 2006 15:40:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length: 269 v=0 o=root 13082 13083 IN IP4 xxx.yyy.142.162 s=session c=IN IP4 xxx.yyy.142.162 t=0 0 m=audio 27164 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 - - - - --- (15 headers 12 lines)--- Using INVITE request as basis request - [EMAIL PROTECTED] Sending to xxx.yyy.142.162 : 5060 (NAT) Found user '3254101' Aug 3 09:40:25 NOTICE[10884]: chan_sip.c:10469 handle_request_invite: Failed to authenticate user "Chocolate Chip" ;tag=as097cbc86 Reliably Transmitting (no NAT) to xxx.yyy.142.162:5060: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP xxx.yyy.142.162:5060;branch=z9hG4bK188cc77a;rport;received=xxx.yyy.142.162 From: "Chocolate Chip" ;tag=as097cbc86 To: ;tag=as004358bd Call-ID: [EMAIL PROTECTED] CSeq: 103 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: Content-Length: 0 --- <-- SIP read from xxx.yyy.142.162:5060: ACK sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP xxx.yyy.142.162:5060;branch=z9hG4bK188cc77a;rport From: "Chocolate Chip" ;tag=as097cbc86 To: ;tag=as004358bd Contact: Call-ID: [EMAIL PROTECTED] CSeq: 103 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Remote-Party-ID: "Chocolate Chip" ;privacy=off;screen=no Content-Length: 0 --- (11 headers 0 lines)--- Destroying call '[EMAIL PROTECTED]' > -Original Message- > From: Watkins, Bradley > [mailto:[EMAIL PROTECTED] Behalf Of Watkins, > Bradley > Sent: Wednesday, August 02, 2006 6:31 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > > Could you perhaps post a sip debug from both of the Asterisk > consoles for the respective peers? > > I think we're very close, and I definitely want to get this > working for you. > > Regards, > - Brad > > _ > > From: [EMAIL PROTECTED] on behalf of > Douglas Garstang > Sent: Wed 8/2/2006 7:16 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] Re: DUNDi with SIP > > > > 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" ;tag=as5e6e3efe' > > Btw, here's a sip trace between the asterisk boxes... > > Capturing on eth0 > 1 0.00 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP > Request: INVITE >
RE: [asterisk-users] Re: DUNDi with SIP
Could you perhaps post a sip debug from both of the Asterisk consoles for the
respective peers?
I think we're very close, and I definitely want to get this working for you.
Regards,
- Brad
From: [EMAIL PROTECTED] on behalf of Douglas Garstang
Sent: Wed 8/2/2006 7:16 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] Re: DUNDi with SIP
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" ;tag=as5e6e3efe'
Btw, here's a sip trace between the asterisk boxes...
Capturing on eth0
1 0.00 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL
PROTECTED]
4 0.329036 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
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:[EMAIL
PROTECTED]
11 2.280664 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: BYE sip:[EMAIL
PROTECTED]
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 [EMAIL PROTECTED]
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"
;tag=as6090e60f'
And here's the SIP trace for THAT!
1 0.00 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL
PROTECTED]
4 0.295054 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
9 0.603485 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
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:[EMAIL
PROTECTED]
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" ;tag=as6090e60f
Ugh... not having much luck with this...
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, Au
RE: [asterisk-users] Re: DUNDi with SIP
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" ;tag=as5e6e3efe'
Btw, here's a sip trace between the asterisk boxes...
Capturing on eth0
1 0.00 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL
PROTECTED]
4 0.329036 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
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:[EMAIL
PROTECTED]
11 2.280664 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP Request: BYE sip:[EMAIL
PROTECTED]
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 [EMAIL PROTECTED]
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"
;tag=as6090e60f'
And here's the SIP trace for THAT!
1 0.00 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL
PROTECTED]
4 0.295054 xxx.yyy.128.18 -> xxx.yyy.142.162 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED];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:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
9 0.603485 xxx.yyy.142.162 -> xxx.yyy.142.163 SIP/SDP Request: INVITE
sip:[EMAIL PROTECTED], 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:[EMAIL
PROTECTED]
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:[EMAIL
PROTECTED]
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" ;tag=as6090e60f
Ugh... not having much luck with this...
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> 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: [EMAIL PROTECTED]
> [mailto
RE: [asterisk-users] Re: DUNDi with SIP
Yeah, they're both in the sip.conf files on each server in the system.
That's how I got the SIP/${server}/${exten} to work.
On Wed, 2006-08-02 at 17:01 -0600, Douglas Garstang wrote:
> Ok, but don't you need to have [scm1] AND [sgw1] in sip.conf?
>
> > -Original Message-
> > From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 02, 2006 4:56 PM
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: RE: [asterisk-users] Re: DUNDi with SIP
> >
> >
> > You don't have to have every host in your dundi.conf files. The way
> > we've got ours set up, each server tells the other servers
> > how to reach
> > it. For example, our primary call server (scm1) publishes
> > what numbers
> > it can handle, so I only list it's contexts in it's own file. Then,
> > sgw1 publishes what IT can handle. There's a matching e164
> > and internal
> > context on each server to tell the others what it can take.
> >
> > On Wed, 2006-08-02 at 16:35 -0600, Douglas Garstang wrote:
> > > > -Original Message-
> > > > From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> > > > 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:[EMAIL PROTECTED]/${NUMBER}
> > > > internal => dundi-extens,0,SIP,scm1/${NUMBER}
> > > > internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${NUMBER}
> > > >
> > > > [scm1]
> > > > type=friend
> > > > secret=p4ssw0rd
> > > > insecure=very
> > > > context=incoming
> > > > host=scm1.shsu.edu
> > > > qualify=yes
> > > > nat=no
> > >
> > > Thanks Aaron, but I don't understand how that can work.
> > Don't you have more than one host in your DUNDi domain?
> > >
> > > 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
> >
> ___
> --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
RE: [asterisk-users] Re: DUNDi with SIP
Ok, but don't you need to have [scm1] AND [sgw1] in sip.conf?
> -Original Message-
> From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:56 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> You don't have to have every host in your dundi.conf files. The way
> we've got ours set up, each server tells the other servers
> how to reach
> it. For example, our primary call server (scm1) publishes
> what numbers
> it can handle, so I only list it's contexts in it's own file. Then,
> sgw1 publishes what IT can handle. There's a matching e164
> and internal
> context on each server to tell the others what it can take.
>
> On Wed, 2006-08-02 at 16:35 -0600, Douglas Garstang wrote:
> > > -Original Message-
> > > From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> > > 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:[EMAIL PROTECTED]/${NUMBER}
> > > internal => dundi-extens,0,SIP,scm1/${NUMBER}
> > > internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${NUMBER}
> > >
> > > [scm1]
> > > type=friend
> > > secret=p4ssw0rd
> > > insecure=very
> > > context=incoming
> > > host=scm1.shsu.edu
> > > qualify=yes
> > > nat=no
> >
> > Thanks Aaron, but I don't understand how that can work.
> Don't you have more than one host in your DUNDi domain?
> >
> > 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
>
___
--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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:45 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> Errr... I should learn to pay attention to what I'm writing...
>
> Actually, try:
>
> 180netsip => global_dundi_local,100,SIP,dundi_pbx1/${NUMBER},nopartial
>
> I was thinking in terms of Dial() arguments when I wrote the
> SIP/peername/number instead of SIP,peername/number syntax.
>
> My bad...
Brad, that's pretty much what Aaron just posted with. Thanks. I've made a
subequent post trying what you/he suggested but I'm still getting some errors.
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
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED]
> 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:[EMAIL PROTECTED]/${NUMBER}
> internal => dundi-extens,0,SIP,scm1/${NUMBER} internal-iax =>
> dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${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 [EMAIL PROTECTED]
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"
;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
RE: [asterisk-users] Re: DUNDi with SIP
You don't have to have every host in your dundi.conf files. The way
we've got ours set up, each server tells the other servers how to reach
it. For example, our primary call server (scm1) publishes what numbers
it can handle, so I only list it's contexts in it's own file. Then,
sgw1 publishes what IT can handle. There's a matching e164 and internal
context on each server to tell the others what it can take.
On Wed, 2006-08-02 at 16:35 -0600, Douglas Garstang wrote:
> > -Original Message-
> > From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> > 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:[EMAIL PROTECTED]/${NUMBER}
> > internal => dundi-extens,0,SIP,scm1/${NUMBER}
> > internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${NUMBER}
> >
> > [scm1]
> > type=friend
> > secret=p4ssw0rd
> > insecure=very
> > context=incoming
> > host=scm1.shsu.edu
> > qualify=yes
> > nat=no
>
> Thanks Aaron, but I don't understand how that can work. Don't you have more
> than one host in your DUNDi domain?
>
> 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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> 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:[EMAIL PROTECTED]/${NUMBER}
> internal => dundi-extens,0,SIP,scm1/${NUMBER}
> internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${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 [EMAIL PROTECTED]
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" ;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
RE: [asterisk-users] Re: DUNDi with SIP
Errr... I should learn to pay attention to what I'm writing...
Actually, try:
180netsip => global_dundi_local,100,SIP,dundi_pbx1/${NUMBER},nopartial
I was thinking in terms of Dial() arguments when I wrote the
SIP/peername/number instead of SIP,peername/number syntax.
My bad...
- Brad
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Douglas
Garstang
Sent: Wednesday, August 02, 2006 6:21 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:07 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> The way to make this work is to define a sip user/peer with the IP
> address in it, then have your dundi.conf entry look like:
>
> 180netsip => global_dundi_local,1,SIP/peername/${NUMBER},nopartial
>
> As far as I can tell from the code, this is the only way to make it
> work properly based on the way the string sent to the channel driver
> is being parsed.
No luck Brad.
dundi.conf has as you suggested:
180netsip => global_dundi_local,100,SIP/dundi_pbx1/${NUMBER},nopartial
180netsip => global_dundi_local,200,SIP/dundi_pbx2/${NUMBER},nopartial
and dundi.conf has:
[dundi_pbx1]
type=peer
context=global_dundi_local
host=labpbx1.ipt.oneeighty.com
[dundi_pbx2]
type=peer
context=global_dundi_local
host=labpbx2.ipt.oneeighty.com
and when I do a query, I get:
dundi lookup [EMAIL PROTECTED]
1. 200 Unknown/nopartial (EXISTS|CANMATCH)
from 00:14:22:1e:2a:d0, expires in 0 s DUNDi lookup completed in
121 ms
Obviously, something is seriously screwed up.
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
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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Aaron Daniel [mailto:[EMAIL PROTECTED]
> 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:[EMAIL PROTECTED]/${NUMBER}
> internal => dundi-extens,0,SIP,scm1/${NUMBER}
> internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${NUMBER}
>
> [scm1]
> type=friend
> secret=p4ssw0rd
> insecure=very
> context=incoming
> host=scm1.shsu.edu
> qualify=yes
> nat=no
Thanks Aaron, but I don't understand how that can work. Don't you have more
than one host in your DUNDi domain?
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
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:[EMAIL PROTECTED]/${NUMBER}
internal => dundi-extens,0,SIP,scm1/${NUMBER}
internal-iax => dundi-extens,0,IAX2,dundi:[EMAIL PROTECTED]/${NUMBER}
[scm1]
type=friend
secret=p4ssw0rd
insecure=very
context=incoming
host=scm1.shsu.edu
qualify=yes
nat=no
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:07 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> The way to make this work is to define a sip user/peer with the IP
> address in it, then have your dundi.conf entry look like:
>
> 180netsip => global_dundi_local,1,SIP/peername/${NUMBER},nopartial
>
> As far as I can tell from the code, this is the only way to
> make it work
> properly based on the way the string sent to the channel
> driver is being
> parsed.
No luck Brad.
dundi.conf has as you suggested:
180netsip => global_dundi_local,100,SIP/dundi_pbx1/${NUMBER},nopartial
180netsip => global_dundi_local,200,SIP/dundi_pbx2/${NUMBER},nopartial
and dundi.conf has:
[dundi_pbx1]
type=peer
context=global_dundi_local
host=labpbx1.ipt.oneeighty.com
[dundi_pbx2]
type=peer
context=global_dundi_local
host=labpbx2.ipt.oneeighty.com
and when I do a query, I get:
dundi lookup [EMAIL PROTECTED]
1. 200 Unknown/nopartial (EXISTS|CANMATCH)
from 00:14:22:1e:2a:d0, expires in 0 s
DUNDi lookup completed in 121 ms
Obviously, something is seriously screwed up.
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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:07 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> The way to make this work is to define a sip user/peer with the IP
> address in it, then have your dundi.conf entry look like:
>
> 180netsip => global_dundi_local,1,SIP/peername/${NUMBER},nopartial
>
> As far as I can tell from the code, this is the only way to
> make it work
> properly based on the way the string sent to the channel
> driver is being
> parsed.
You this, this is:
a) completely different to what's in dundi.conf right now
b) completely different to the docs posted on the wiki.
Have people actually TRIED this, or do they just what they _THINK_ will work as
docs???
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
RE: [asterisk-users] Re: DUNDi with SIP
So... given then that there's multiple systems in the DUNDI domain (obviously),
that means there's going to be multiple hosts, and therefore I'll need to have
one sip user for each host, and one dundi entry for each user as well... Bleck.
> -Original Message-
> From: Watkins, Bradley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 4:07 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
>
> The way to make this work is to define a sip user/peer with the IP
> address in it, then have your dundi.conf entry look like:
>
> 180netsip => global_dundi_local,1,SIP/peername/${NUMBER},nopartial
>
> As far as I can tell from the code, this is the only way to
> make it work
> properly based on the way the string sent to the channel
> driver is being
> parsed.
>
> - Brad
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Douglas
> Garstang
> Sent: Wednesday, August 02, 2006 5:59 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Re: DUNDi with SIP
>
> > -Original Message-
> > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 02, 2006 3:49 PM
> > To: asterisk-users@lists.digium.com
> > Subject: [asterisk-users] Re: DUNDi with SIP
> >
> >
> > In article
> > <[EMAIL PROTECTED]>,
> > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > > -Original Message-----
> > > > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > > > Sent: Wednesday, August 02, 2006 2:01 PM
> > > > To: asterisk-users@lists.digium.com
> > > > Subject: [asterisk-users] Re: DUNDi with SIP
> > > >
> > > >
> > > > In article
> > > > <[EMAIL PROTECTED]>,
> > > > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > > > I've trying to use DUNDi with SIP to see if it works around
> > > > some limitations of IAX2.
> > > > >
> > > > > I do a DUNDi lookup, get my SIP path, and try to dial it.
> > > > Asterisk immediately says 'No such
> > > > > host', eventhough that's the path is just returned!
> > > > >
> > > > > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> > > > u9220371, 3) exited non-zero on
> > > > > 'SIP/3254101-eb7d'
> > > > > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> > > > "*** OnNet originated call
> > > > > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > > > > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> > > > "ipt/originator.py") in new stack
> > > > > [Aug 2 13:07:13] -- Launched AGI Script
> > > > /var/lib/asterisk/agi-bin/ipt/originator.py
> > > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > > (SetAccount) Options: (9220371)
> > > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > > (ChanIsAvail) Options: (SIP/9220371)
> > > > > [Aug 2 13:07:14] -- AGI Script Executing Application:
> > > > (Dial) Options:
> > > > > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > > > > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> > > > create_addr: No such host: xxx.yyy.142.163/9220371
> > > >
> > > > Try specifying the SIP argument as:
> > > >
> > > > SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
> > > >
> > > > See the following line in the sample extensions.conf as
> > an example:
> > > >
> > > > ;exten =>
> > > > _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
> > >
> > > Tony... it's DUNDi
> >
> > OK, I know nothing about DUNDi. I was only highlighting
> what appeared
> > to be invalid or at least ambiguous syntax in the SIP channel
> > requested.
> > SIP appears not to like SIP/user:[EMAIL PROTECTED]/number, but
> instead wants
> > SIP/user:[EMAIL PROTECTED]@host
> >
> > Unless you can set up a sip.conf friend entry [] and then use
> > SIP//number
> >
> > Hope this helps. If not, oh well.
>
> Tony, I was able to fiddle with dundi.conf, and am now getting a SIP
> path in the format SIP/user:[EMAIL PROTECTED]@h
RE: [asterisk-users] Re: DUNDi with SIP
The way to make this work is to define a sip user/peer with the IP
address in it, then have your dundi.conf entry look like:
180netsip => global_dundi_local,1,SIP/peername/${NUMBER},nopartial
As far as I can tell from the code, this is the only way to make it work
properly based on the way the string sent to the channel driver is being
parsed.
- Brad
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Douglas
Garstang
Sent: Wednesday, August 02, 2006 5:59 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 3:49 PM
> To: asterisk-users@lists.digium.com
> Subject: [asterisk-users] Re: DUNDi with SIP
>
>
> In article
> <[EMAIL PROTECTED]>,
> Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > -Original Message-
> > > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, August 02, 2006 2:01 PM
> > > To: asterisk-users@lists.digium.com
> > > Subject: [asterisk-users] Re: DUNDi with SIP
> > >
> > >
> > > In article
> > > <[EMAIL PROTECTED]>,
> > > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > > I've trying to use DUNDi with SIP to see if it works around
> > > some limitations of IAX2.
> > > >
> > > > I do a DUNDi lookup, get my SIP path, and try to dial it.
> > > Asterisk immediately says 'No such
> > > > host', eventhough that's the path is just returned!
> > > >
> > > > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> > > u9220371, 3) exited non-zero on
> > > > 'SIP/3254101-eb7d'
> > > > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> > > "*** OnNet originated call
> > > > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > > > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> > > "ipt/originator.py") in new stack
> > > > [Aug 2 13:07:13] -- Launched AGI Script
> > > /var/lib/asterisk/agi-bin/ipt/originator.py
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (SetAccount) Options: (9220371)
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (ChanIsAvail) Options: (SIP/9220371)
> > > > [Aug 2 13:07:14] -- AGI Script Executing Application:
> > > (Dial) Options:
> > > > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > > > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> > > create_addr: No such host: xxx.yyy.142.163/9220371
> > >
> > > Try specifying the SIP argument as:
> > >
> > > SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
> > >
> > > See the following line in the sample extensions.conf as
> an example:
> > >
> > > ;exten =>
> > > _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
> >
> > Tony... it's DUNDi
>
> OK, I know nothing about DUNDi. I was only highlighting what appeared
> to be invalid or at least ambiguous syntax in the SIP channel
> requested.
> SIP appears not to like SIP/user:[EMAIL PROTECTED]/number, but instead wants
> SIP/user:[EMAIL PROTECTED]@host
>
> Unless you can set up a sip.conf friend entry [] and then use
> SIP//number
>
> Hope this helps. If not, oh well.
Tony, I was able to fiddle with dundi.conf, and am now getting a SIP
path in the format SIP/user:[EMAIL PROTECTED]@host:
*CLI> dundi lookup [EMAIL PROTECTED]
1. 1 SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163 (EXISTS)
from 00:14:22:1e:2a:d0, expires in 0 s DUNDi lookup completed in
171 ms
However, when I try to dial this, I am still getting:
[Aug 2 15:57:35] WARNING[9916]: chan_sip.c:1980 create_addr: No such
host: [EMAIL PROTECTED] [Aug 2 15:57:35] NOTICE[9916]:
app_dial.c:1040 dial_exec_full: Unable to create channel of type 'SIP'
(cause 3 - No route to destination)
Arrgh
___
--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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 3:49 PM
> To: asterisk-users@lists.digium.com
> Subject: [asterisk-users] Re: DUNDi with SIP
>
>
> In article
> <[EMAIL PROTECTED]>,
> Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > -Original Message-
> > > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, August 02, 2006 2:01 PM
> > > To: asterisk-users@lists.digium.com
> > > Subject: [asterisk-users] Re: DUNDi with SIP
> > >
> > >
> > > In article
> > > <[EMAIL PROTECTED]>,
> > > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > > I've trying to use DUNDi with SIP to see if it works around
> > > some limitations of IAX2.
> > > >
> > > > I do a DUNDi lookup, get my SIP path, and try to dial it.
> > > Asterisk immediately says 'No such
> > > > host', eventhough that's the path is just returned!
> > > >
> > > > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> > > u9220371, 3) exited non-zero on
> > > > 'SIP/3254101-eb7d'
> > > > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> > > "*** OnNet originated call
> > > > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > > > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> > > "ipt/originator.py") in new stack
> > > > [Aug 2 13:07:13] -- Launched AGI Script
> > > /var/lib/asterisk/agi-bin/ipt/originator.py
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (SetAccount) Options: (9220371)
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (ChanIsAvail) Options: (SIP/9220371)
> > > > [Aug 2 13:07:14] -- AGI Script Executing Application:
> > > (Dial) Options:
> > > > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > > > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> > > create_addr: No such host: xxx.yyy.142.163/9220371
> > >
> > > Try specifying the SIP argument as:
> > >
> > > SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
> > >
> > > See the following line in the sample extensions.conf as
> an example:
> > >
> > > ;exten =>
> > > _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
> >
> > Tony... it's DUNDi
>
> OK, I know nothing about DUNDi. I was only highlighting what appeared
> to be invalid or at least ambiguous syntax in the SIP channel
> requested.
> SIP appears not to like SIP/user:[EMAIL PROTECTED]/number, but instead wants
> SIP/user:[EMAIL PROTECTED]@host
>
> Unless you can set up a sip.conf friend entry [] and then use
> SIP//number
>
> Hope this helps. If not, oh well.
Tony, I was able to fiddle with dundi.conf, and am now getting a SIP path in
the format SIP/user:[EMAIL PROTECTED]@host:
*CLI> dundi lookup [EMAIL PROTECTED]
1. 1 SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163 (EXISTS)
from 00:14:22:1e:2a:d0, expires in 0 s
DUNDi lookup completed in 171 ms
However, when I try to dial this, I am still getting:
[Aug 2 15:57:35] WARNING[9916]: chan_sip.c:1980 create_addr: No such host:
[EMAIL PROTECTED]
[Aug 2 15:57:35] NOTICE[9916]: app_dial.c:1040 dial_exec_full: Unable to
create channel of type 'SIP' (cause 3 - No route to destination)
Arrgh
___
--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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 3:49 PM
> To: asterisk-users@lists.digium.com
> Subject: [asterisk-users] Re: DUNDi with SIP
>
>
> In article
> <[EMAIL PROTECTED]>,
> Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > -Original Message-
> > > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, August 02, 2006 2:01 PM
> > > To: asterisk-users@lists.digium.com
> > > Subject: [asterisk-users] Re: DUNDi with SIP
> > >
> > >
> > > In article
> > > <[EMAIL PROTECTED]>,
> > > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > > I've trying to use DUNDi with SIP to see if it works around
> > > some limitations of IAX2.
> > > >
> > > > I do a DUNDi lookup, get my SIP path, and try to dial it.
> > > Asterisk immediately says 'No such
> > > > host', eventhough that's the path is just returned!
> > > >
> > > > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> > > u9220371, 3) exited non-zero on
> > > > 'SIP/3254101-eb7d'
> > > > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> > > "*** OnNet originated call
> > > > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > > > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> > > "ipt/originator.py") in new stack
> > > > [Aug 2 13:07:13] -- Launched AGI Script
> > > /var/lib/asterisk/agi-bin/ipt/originator.py
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (SetAccount) Options: (9220371)
> > > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > > (ChanIsAvail) Options: (SIP/9220371)
> > > > [Aug 2 13:07:14] -- AGI Script Executing Application:
> > > (Dial) Options:
> > > > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > > > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> > > create_addr: No such host: xxx.yyy.142.163/9220371
> > >
> > > Try specifying the SIP argument as:
> > >
> > > SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
> > >
> > > See the following line in the sample extensions.conf as
> an example:
> > >
> > > ;exten =>
> > > _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
> >
> > Tony... it's DUNDi
>
> OK, I know nothing about DUNDi. I was only highlighting what appeared
> to be invalid or at least ambiguous syntax in the SIP channel
> requested.
> SIP appears not to like SIP/user:[EMAIL PROTECTED]/number, but instead wants
> SIP/user:[EMAIL PROTECTED]@host
>
> Unless you can set up a sip.conf friend entry [] and then use
> SIP//number
>
> Hope this helps. If not, oh well.
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.
___
--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
[asterisk-users] Re: DUNDi with SIP
In article <[EMAIL PROTECTED]>,
Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 02, 2006 2:01 PM
> > To: asterisk-users@lists.digium.com
> > Subject: [asterisk-users] Re: DUNDi with SIP
> >
> >
> > In article
> > <[EMAIL PROTECTED]>,
> > Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > > I've trying to use DUNDi with SIP to see if it works around
> > some limitations of IAX2.
> > >
> > > I do a DUNDi lookup, get my SIP path, and try to dial it.
> > Asterisk immediately says 'No such
> > > host', eventhough that's the path is just returned!
> > >
> > > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> > u9220371, 3) exited non-zero on
> > > 'SIP/3254101-eb7d'
> > > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> > "*** OnNet originated call
> > > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> > "ipt/originator.py") in new stack
> > > [Aug 2 13:07:13] -- Launched AGI Script
> > /var/lib/asterisk/agi-bin/ipt/originator.py
> > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > (SetAccount) Options: (9220371)
> > > [Aug 2 13:07:13] -- AGI Script Executing Application:
> > (ChanIsAvail) Options: (SIP/9220371)
> > > [Aug 2 13:07:14] -- AGI Script Executing Application:
> > (Dial) Options:
> > > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> > create_addr: No such host: xxx.yyy.142.163/9220371
> >
> > Try specifying the SIP argument as:
> >
> > SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
> >
> > See the following line in the sample extensions.conf as an example:
> >
> > ;exten =>
> > _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
>
> Tony... it's DUNDi
OK, I know nothing about DUNDi. I was only highlighting what appeared
to be invalid or at least ambiguous syntax in the SIP channel requested.
SIP appears not to like SIP/user:[EMAIL PROTECTED]/number, but instead wants
SIP/user:[EMAIL PROTECTED]@host
Unless you can set up a sip.conf friend entry [] and then use
SIP//number
Hope this helps. If not, oh well.
Cheers
Tony
--
Tony Mountifield
Work: [EMAIL PROTECTED] - http://www.softins.co.uk
Play: [EMAIL PROTECTED] - http://tony.mountifield.org
___
--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
RE: [asterisk-users] Re: DUNDi with SIP
> -Original Message-
> From: Tony Mountifield [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 2:01 PM
> To: asterisk-users@lists.digium.com
> Subject: [asterisk-users] Re: DUNDi with SIP
>
>
> In article
> <[EMAIL PROTECTED]>,
> Douglas Garstang <[EMAIL PROTECTED]> wrote:
> > I've trying to use DUNDi with SIP to see if it works around
> some limitations of IAX2.
> >
> > I do a DUNDi lookup, get my SIP path, and try to dial it.
> Asterisk immediately says 'No such
> > host', eventhough that's the path is just returned!
> >
> > [Aug 2 13:07:05] == Spawn extension (global_vmdeposit,
> u9220371, 3) exited non-zero on
> > 'SIP/3254101-eb7d'
> > [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373",
> "*** OnNet originated call
> > "Chocolate Chip" <3254101> -> 9220371") in new stack
> > [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> "ipt/originator.py") in new stack
> > [Aug 2 13:07:13] -- Launched AGI Script
> /var/lib/asterisk/agi-bin/ipt/originator.py
> > [Aug 2 13:07:13] -- AGI Script Executing Application:
> (SetAccount) Options: (9220371)
> > [Aug 2 13:07:13] -- AGI Script Executing Application:
> (ChanIsAvail) Options: (SIP/9220371)
> > [Aug 2 13:07:14] -- AGI Script Executing Application:
> (Dial) Options:
> > (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> > [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980
> create_addr: No such host: xxx.yyy.142.163/9220371
>
> Try specifying the SIP argument as:
>
> SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
>
> See the following line in the sample extensions.conf as an example:
>
> ;exten =>
> _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
Tony... it's DUNDi
___
--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
[asterisk-users] Re: DUNDi with SIP
In article <[EMAIL PROTECTED]>,
Douglas Garstang <[EMAIL PROTECTED]> wrote:
> I've trying to use DUNDi with SIP to see if it works around some limitations
> of IAX2.
>
> I do a DUNDi lookup, get my SIP path, and try to dial it. Asterisk
> immediately says 'No such
> host', eventhough that's the path is just returned!
>
> [Aug 2 13:07:05] == Spawn extension (global_vmdeposit, u9220371, 3) exited
> non-zero on
> 'SIP/3254101-eb7d'
> [Aug 2 13:07:13] -- Executing NoOp("SIP/3254101-6373", "*** OnNet
> originated call
> "Chocolate Chip" <3254101> -> 9220371") in new stack
> [Aug 2 13:07:13] -- Executing AGI("SIP/3254101-6373",
> "ipt/originator.py") in new stack
> [Aug 2 13:07:13] -- Launched AGI Script
> /var/lib/asterisk/agi-bin/ipt/originator.py
> [Aug 2 13:07:13] -- AGI Script Executing Application: (SetAccount)
> Options: (9220371)
> [Aug 2 13:07:13] -- AGI Script Executing Application: (ChanIsAvail)
> Options: (SIP/9220371)
> [Aug 2 13:07:14] -- AGI Script Executing Application: (Dial) Options:
> (SIP/dundisip:[EMAIL PROTECTED]/9220371)
> [Aug 2 13:07:14] WARNING[5429]: chan_sip.c:1980 create_addr: No such host:
> xxx.yyy.142.163/9220371
Try specifying the SIP argument as:
SIP/dundisip:[EMAIL PROTECTED]@xxx.yyy.142.163
See the following line in the sample extensions.conf as an example:
;exten => _42X.,1,Dial(SIP/user:[EMAIL PROTECTED]:[EMAIL PROTECTED],30,rT)
Cheers
Tony
--
Tony Mountifield
Work: [EMAIL PROTECTED] - http://www.softins.co.uk
Play: [EMAIL PROTECTED] - http://tony.mountifield.org
___
--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
