Re: [Sipp-users] Not RFC compliant SIPp behaviour

[Olivier J. <oja...@us...>]

Diels Terry wrote:
> Hi *,
> 
> I'm a new SIPp user, and I think it is a very powerfull tool.

I do to :)

> One thing I have to mention is that it is not RFC compliant :
> SIPp responds to requests to the UDP port were the request is sent from.
> The RFC states that a respond msg must be sent to the address stated in 
> the Via header.

Your're right. SIPp is a simple tool, it doesn't implement a SIP stack 
as such. That's why it is not RFC compliant on some points.

> Does anyone have allready patched SIPp to be RFC compliant on this matter?
> Or can someone help me to patch it?

I don't have a patch for this.
To implement this, you might want to look how the -rsa option has been 
implemented. Here is the diff in sipp.cpp:
http://cvs.sourceforge.net/viewcvs.py/sipp/sipp/sipp.cpp?r1=1.8&r2=1.9

There is already a function to get the value of an header 
(call::get_header_content) which you might want to use to parse the Via 
header.
Let us know when you have something that works!

Olivier.