On Sat, Sep 10, 2011 at 3:46 AM, <[email protected]> wrote:
> i tried using softphone instead of sipp, its working perfectly.
> as per ur suggestion, i captured the traces, its as below
>
> trace_msg logs
> ----------------------------------------------- 2011-09-09 14
> :53:44:740.163
> UDP message sent (516 bytes):
>
> INVITE sip:[email protected]:49152 SIP/2.0
> Via: SIP/2.0/UDP 10.50.26.207:6067;branch=z9hG4bK-3356-1-0
> From: "alice" <sip:[email protected]:6067>;tag=33561
> To: "bob" <sip:[email protected]:49152>
> Call-ID: [email protected]
> CSeq: 1 INVITE
> Contact: sip:[email protected]:6067
>
> Max-Forwards: 70
> Subject: Performance Test
> Content-Type: application/sdp
> Content-Length: 133
>
> v=0
> o=user1 53655765 2353687637 IN IP4 10.50.26.207
> s=-
> c=IN IP4 10.50.26.207
> t=0 0
> m=audio 6000 RTP/AVP 0
>
> a=rtpmap:0 PCMU/8000
> ----------------------------------------------- 2011-09-09 14
> :53:44:744.163
> UDP message received [537] bytes :
>
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 10.50.26.207:6067;branch=z9hG4bK-3356-1-0
> From: "alice" <sip:[email protected]:6067>;tag=33561
> To: "bob" <sip:[email protected]:49152>;tag=4dc96444
> CSeq: 1 INVITE
> Call-ID: [email protected]
> Allow: INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
> User-Agent: miniSipServer V3.1.7 (20 clients) build Sep 1 2011
> Proxy-Authenticate: Digest realm="myvoipapp.com
> ",algorithm=MD5,nonce="66bc428c26a770205d047a5b767e450a",stale=FALSE
> Content-Length: 0
>
>
> ----------------------------------------------- 2011-09-09 14
> :53:44:744.163
> UDP message sent (355 bytes):
>
> ACK sip:[email protected]:49152 SIP/2.0
> Via: SIP/2.0/UDP 10.50.26.207:6067;branch=z9hG4bK-3356-1-0
> From: "alice" <sip:[email protected]:6067>;tag=33561
> To: "bob" <sip:[email protected]:49152>;tag=4dc96444
> Call-ID: [email protected]
> CSeq: 1 ACK
> Contact: sip:[email protected]:6067
>
> Max-Forwards: 70
> Subject: Performance Test
> Content-Length: 0
>
>
> ----------------------------------------------- 2011-09-09 14
> :53:44:753.163
> UDP message sent (712 bytes):
>
> INVITE sip:[email protected]:49152 SIP/2.0
> Via: SIP/2.0/UDP 10.50.26.207:6067;branch=z9hG4bK-3356-1-3
> From: "alice" <sip:[email protected]:6067>;tag=33561
> To: "bob" <sip:[email protected]:49152
> Call-ID: [email protected]
> CSeq: 2 INVITE
> Proxy-Authorization: Digest username="alice",realm="myvoipapp.com
> ",uri="sip:10.50.26.207:49152
> ",nonce="66bc428c26a770205d047a5b767e450a",response="9f1c08d87105bae5be1a846b92c83e98",algorithm=MD5
>
>
I don't know if this solves the problem, but just to update this thread (as
I answered on another thread created by mistake for the same issue):
There is a strange space in front of header Proxy-Authorization.
I believe it is being caused by you error in aligning the message properly:
INVITE sip:bob@...] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: "alice" <sip:alice@...]
To: "bob" <sip:bob@...]
Call-ID: [call_id]
CSeq: 2 INVITE
[authentication username=alice password=alice]
Contact: sip:alice@...]
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: [len]
Try aligning
[authentication username=alice password=alice]
properly with the headers.
------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the
Bottom Line. Protect your business and customers by understanding the
threat from malware and how it can impact your online business.
http://www.accelacomm.com/jaw/sfnl/114/51427462/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
