On Sat, Sep 10, 2011 at 3:42 AM, <manaswini.m...@gmail.com> wrote:
> i tried using softphone instead of sipp, its working perfectly.
> as per ur i captured the traces, its as below
>
>
> INVITE sip:bob@10.50.26.207:49152 SIP/2.0
> Via: SIP/2.0/UDP 10.50.26.207:6067;branch=z9hG4bK-3356-1-3
> From: "alice" <sip:alice@10.50.26.207:6067>;tag=33561
> To: "bob" <sip:bob@10.50.26.207:49152
> Call-ID: 1-3356@10.50.26.207
> CSeq: 2 INVITE
> Proxy-Authorization: Digest username="alice",realm="myvoipapp.com
> ",uri="sip:10.50.26.207:49152
> ",nonce="66bc428c26a770205d047a5b767e450a",response="9f1c08d87105bae5be1a846b92c83e98",algorithm=MD5
>
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.
------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT
space for its ease of implementation, lower cost, and increased
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
