Summary:	ASTERISK-01515: Authentication with FWD is broken
Reporter:	bdolljr (bdolljr)	Labels:
Date Opened:	2004-05-01 19:08:27	Date Closed:	2004-09-25 02:48:27
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) fwd-auth.txt ( 1) Fwd-Working.txt
Description:	An outbound call to Free World Dialup will not authenticate. ****** ADDITIONAL INFORMATION ****** chan_sip.c (1.342) works.  Anything after that is broken.  Attached is a log (sip debug peer fwd.pulver.com).  The username='10001' is the number that I dialed,  not my account.
Comments:	By: Mark Spencer (markster) 2004-05-01 19:12:52 How about the diff that alledgedly breaks it? By: Brian West (bkw918) 2004-05-01 19:13:29 -- Executing Dial("SIP/10-46e6", "SIP/55555@fwd.pulver.com") in new stack    -- Called 55555@fwd.pulver.com    -- SIP/fwd.pulver.com-9567 is ringing    -- SIP/fwd.pulver.com-9567 is ringing I think you need to clarify that you are behind NAT. By: Brian West (bkw918) 2004-05-01 19:18:40 can you get us a sip debug of before the break and after it breaks and attach it. bkw By: bdolljr (bdolljr) 2004-05-01 19:26:27 i will try and get the diff ASAP.  The changelog notes: 2004-04-26 08:26  markster * channels/chan_sip.c (1.343): Use proper token for authenticating BYE maybe this had an adverse effect.  I will work on the diff for you. By: bdolljr (bdolljr) 2004-05-01 19:28:12 To clarify...  My 7960 IS behind a NAT.  However, the leg from * to FWD is not NAT'D.  My * server has a real IP. By: twisted (twisted) 2004-05-01 19:41:26 Can you verify your configuration with us please?  (ie, post it here?) By: Brian West (bkw918) 2004-05-01 19:47:16 do you have username= in your peer entry in sip.conf if not add it. bkw By: bdolljr (bdolljr) 2004-05-01 19:47:32 /* from extensions.conf */ [Outgoing-FWD] exten => _82.,1,SetCallerID(70563) exten => _82.,2,SetCIDName(Big Sky Tech) exten => _82.,3,Dial(SIP/${EXTEN:2}@fwd.pulver.com,60,r) /* from sip.conf */ register => 70563:****@fwd.pulver.com/5000 [fwd.pulver.com] type=friend secret=**** username=70563 host=fwd.pulver.com context=Incoming-FWD canreinvite=no dtmfmode=inband callerid=asreceived fromuser=70563 fromdomain=fwd.pulver.com By: twisted (twisted) 2004-05-01 19:48:36 Do me a favor and try changing your peer entry to [fwd] and using fwd in your dialstring instead of addressing the hostname directly, see if this fixes your problem. By: Brian West (bkw918) 2004-05-01 19:48:39 [fwd.pulver.com] type=friend username=XXXXXX secret=XXXXXX disallow=all allow=ulaw host=fwd.pulver.com context=sipext qualify=500 dtmfmode=rfc2833 canreinvite=no This is my sip.conf entry. By: twisted (twisted) 2004-05-01 19:50:24 yeah, it shouldn't make a difference... By: bdolljr (bdolljr) 2004-05-01 19:50:33 twisted...  I've tried it both ways [fwd] and [fwd.pulver.com] By: Brian West (bkw918) 2004-05-01 19:50:38 twisted I didn't have to do that for it to work. I suspect fromuser or fromdomain might have issues?!?! By: bdolljr (bdolljr) 2004-05-01 20:01:37 tried changing type=friend to type=peer.  Still doesn't work. By: bdolljr (bdolljr) 2004-05-01 20:09:34 commenting out fromdomain=fwd.pulver.com fixes this.  i should be able to specify fromdomain shouldn't I? By: Brian West (bkw918) 2004-05-01 20:19:34 depends. fromdomain is needed on some and not others .. welcome to the wonderful world of SIP. By: Mark Spencer (markster) 2004-05-01 21:25:15 Reverted the patch that broke it.  The previous bug ASTERISK-1421 needs to use username=foo instead of trying to pull it from the username field.