linphone-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Linphone-users]proxy authorization with linphone


From: Aymeric Moizard
Subject: RE: [Linphone-users]proxy authorization with linphone
Date: Sat, 1 Feb 2003 00:31:12 +0100 (CET)

The warning is ok. You can discard it silently.

authentication has been done for REGISTER only. It
would not require a lot of work to do it for all requests
type.

Aymeric

On Fri, 31 Jan 2003, [iso-8859-1] Kedar B. Patil wrote:

> OK, KPhone looks good, but it's in cpp, I am "c" person.
>
> Linphone does MD5 for WWW-Authenticate, but not for Proxy-Authenticate.
> In Linphone code, I observed that the handling of 407 in Invite client
> callbacks was commented. So I am inquisitive to know if there was any
> problem with it.
>
> Also, I wanted to know about the WARNING in the log.
>
> thanks,
> = Kedar =
>
>
>  --- Craig Thornton <address@hidden> wrote:
> > Kedar,
> >
> > I was having the same problem.  It seems that Digest (MD5) authentication 
> > is still on the TODO
> > list for linphone.  Basically, in response to the "407 Proxy Authentication 
> > Required" linphone
> > should send another SIP INVITE containing the response to the "nonce" sent 
> > by the Proxy. But, as
> > I mentioned, this feature is not part of the linphone package...yet.
> >
> > If you absolutely need to have digest authentication and don't want to 
> > modify the linphone code
> > then you could try Kphone3.0.  I know for a fact that it supports Digest 
> > authentication.
> >
> > Hope this helps.
> >
> > Cheers,
> >
> > Craig
> >
> > -----Original Message-----
> > From: Kedar B. Patil [mailto:address@hidden
> > Sent: January 30, 2003 6:08 PM
> > To: address@hidden
> > Subject: [Linphone-users]proxy authorization with
> >
> >
> > Hi,
> >
> > I use linphone-9.0.1 with libosip-0.9.0 on Debian linux
> > and Partysip as Registrar & also an outbound proxy.
> >
> > In Linphone parameter config "SIP" tab, I have enabled:
> > - Proxy Server
> > - Outbound Proxy
> >
> > On Partysip I have enabled "Auth".
> >
> > Linphone succeeds in Rgistration. However it initiates
> > a SIP call, it fails due to "407 Proxy Authentication Required"
> >
> > Linphone does not respond with "Proxy-Authorization" to proxy.
> > Also , I see one WARNING in the log.
> >
> > Kindly clarify.
> >
> > thanks,
> > = Kedar =
> >
> > ====================== log ============================
> > | INFO1 | <udp.c: 191> Sending message:
> > REGISTER sip:192.168.51.11 SIP/2.0
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK3684131597
> > From: <sip:address@hidden>;tag=915546564
> > To: <sip:address@hidden>;tag=915546564
> > Call-ID: address@hidden
> > CSeq: 0 REGISTER
> > Contact: <sip:address@hidden>
> > max-forwards: 10
> > expires: 900
> > user-agent: oSIP/Linphone-0.9.1
> > Content-Length: 0
> >
> >
> > | INFO1 | <udp.c: 162> info: RECEIVING UDP MESSAGE:
> > SIP/2.0 401 Unauthorized
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK3684131597
> > From: <sip:address@hidden>;tag=915546564
> > To: <sip:address@hidden>;tag=915546564
> > Call-ID: address@hidden
> > CSeq: 0 REGISTER
> > WWW-Authenticate: Digest realm="192.168.51.11", 
> > nonce="196cae3d068c3ed9dc5102f1249d6ac7",
> > opaque="0b75bbe42bc9e0924e4915e5391cb763"
> > Content-Length: 0
> >
> >
> >
> > | INFO1 | <nict_callbacks.c: 107> OnEvent_New_Incoming4xxResponse!
> >
> > | INFO1 | <nict_callbacks.c: 127> User need to authenticate to REGISTER!
> >
> > | INFO1 | <authentication.c: 269> Response in authorization 
> > |817766c5d2549c7fc25c73c2866237e3|
> >
> > | INFO1 | <udp.c: 191> Sending message:
> > REGISTER sip:192.168.51.11 SIP/2.0
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK3862457899
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>;tag=3474828842
> > Call-ID: address@hidden
> > CSeq: 1 REGISTER
> > Contact: <sip:address@hidden>
> > Authorization: Digest username="kpatil", realm="192.168.51.11",
> > nonce="196cae3d068c3ed9dc5102f1249d6ac7", uri="sip:192.168.51.11",
> > response="817766c5d2549c7fc25c73c2866237e3", algorithm=MD5,
> > opaque="0b75bbe42bc9e0924e4915e5391cb763"
> > max-forwards: 10
> > expires: 900
> > user-agent: oSIP/Linphone-0.9.1
> > Content-Length: 0
> >
> >
> > | INFO1 | <udp.c: 162> info: RECEIVING UDP MESSAGE:
> > SIP/2.0 200 OK
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK3862457899
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>;tag=3474828842
> > Call-ID: address@hidden
> > CSeq: 1 REGISTER
> > Contact: <sip:address@hidden>;expires=900
> > Content-Length: 0
> >
> >
> >
> > | INFO1 | <nict_callbacks.c: 30> Transaction 8 killed.
> >
> > | INFO1 | <nict_callbacks.c: 30> Transaction 9 killed.
> >
> > | INFO1 | <osipdialog.c: 1601> Call leg is removed. It remains 0 call legs 
> > in the ua list.
> >
> > state=0
> >
> > WARNING: call_leg->from already contain a tag???
> >
> > invite state=1
> > | INFO1 | <udp.c: 191> Sending message:
> > INVITE sip:address@hidden SIP/2.0
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK2525740633
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 20 INVITE
> > Contact: <sip:address@hidden>
> > max-forwards: 10
> > user-agent: oSIP/Linphone-0.9.1
> > Content-Type: application/sdp
> > Content-Length: 361
> >
> > v=0
> > o=kpatil 123456 654321 IN IP4 192.168.51.229
> > s=A conversation
> > c=IN IP4 192.168.51.229
> > t=0 0
> > m=audio 7078 RTP/AVP 3 115 8 0 110 111 101
> > a=rtpmap:3 gsm/8000/1
> > a=rtpmap:115 lpc10-1.5/8000/1
> > a=rtpmap:8 PCMA/8000/1
> > a=rtpmap:0 PCMU/8000/1
> > a=rtpmap:110 speex-4/8000/1
> > a=rtpmap:111 speex_lbr-4/8000/1
> > a=rtpmap:101 telephone-event/8000
> > a=fmtp:101 0-11
> >
> > | INFO1 | <udp.c: 162> info: RECEIVING UDP MESSAGE:
> > SIP/2.0 100 Trying
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK2525740633
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 20 INVITE
> > Content-Length: 0
> >
> >
> >
> > | INFO1 | <ict_callbacks.c: 41> OnEvent_New_Incoming1xxResponse!
> >
> > | INFO1 | <udp.c: 162> info: RECEIVING UDP MESSAGE:
> > SIP/2.0 407 Proxy Authentication Required
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK2525740633
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 20 INVITE
> > Proxy-Authenticate: Digest realm="192.168.51.11", 
> > nonce="565ff5a5ef707334c3d803fa8f501711",
> > opaque="91e58a2b33a1e9e9a367bbe8d587da48"
> > Content-Length: 0
> >
> >
> >
> > | INFO1 | <udp.c: 191> Sending message:
> > ACK sip:address@hidden SIP/2.0
> > Via: SIP/2.0/UDP 192.168.51.229:5060;branch=z9hG4bK2525740633
> > From: <sip:address@hidden>;tag=3474828842
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 20 ACK
> > Content-Length: 0
> >
> >
> > | INFO1 | <ict_callbacks.c: 233> OnEvent_New_Incoming4xxResponse!
> >
> > error handler done.
> > | INFO1 | <ict_callbacks.c: 30> Transaction 10 killed.
> >
> > | INFO1 | <osipdialog.c: 1601> Call leg is removed. It remains 0 call legs 
> > in the ua list.
> > ========================================================
> >
> >
> >
> > ________________________________________________________________________
> > Missed your favourite TV serial last night? Try the new, Yahoo! TV.
> >        visit http://in.tv.yahoo.com
> >
> >
> > _______________________________________________
> > Linphone-users mailing list
> >
> === message truncated ===
>
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
>        visit http://in.tv.yahoo.com
>
>
> _______________________________________________
> Linphone-users mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/linphone-users
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]