When we configure SIPp to use a transport layer, say -t t1 for TCP, is it a
requirement to add the parameter "transport=tcp" in the Contact header of
the INVITE?
Ex:INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/TCP 206.81.53.100:5060;branch=z9hG4bK-22475-1-0
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=22475SIPpTag001
To: sut <sip:[EMAIL PROTECTED]:5060>
Call-ID: [EMAIL PROTECTED]
CSeq: 1 INVITE
Contact: sip:[EMAIL PROTECTED]:5060;transport=TCP
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 135
...If this is a requirement,
(1) could you please point me to the rfc where this requirement is stated?
(2) why SIPp does not automatically add the parameter "transport="?
Thanks,
Ricardo.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
