Thanks for your reply Tarek. How is the "-rsa" option different from the "remote_host[:remote_port]" option passed as the first parameter to sipp? I am guessing that the "-rsa" option forces this behavior. However, in that case, if the "rsa" option is not provided, shouldn't the response be sent to the IP and port specified in the "VIA" header instead of sending it back to the originating IP and port? Most of the SIP phones that we test our server with, use the SIP header information to respond back. I am relatively new to SIP and SIPp so please feel free to correct me if I am wrong in my understanding of this scenario.
Another thing I also noticed is that the CALL-ID is the same for the entire scenario. Is this how it should be? Here's my scenario:
REGISTER ---->
200 <-----
INVITE ----->
100 <----
180 <----
200 <----
ACK ---- >
The reason why I started looking at the CALL-ID is because after I used the "-rsa" option, I did get a response back (200 OK), but I got the message from SIPp saying "Discarding message which can't be mapped to a known SIPp call". However, I do find a corresponding SIPp INVITE message with the same CALL-ID ... and then I noticed that every message in the above scenario had the same CALL-ID.
Thanks in advance for any help with this.
Thanks,
Vic
On 9/11/06, F. Tarek Rogers <[EMAIL PROTECTED]> wrote:
To my knowledge, sipp doesn't posses the ability to re-direct socket information based on the contents of the message. When used in UAS mode, SIPp will reply to the same IP and port of the incoming request. If you need to override this behavior, or if your proxy doesn't support connected UDP sockets, you have to use the -rsa host:port option. (However, this obviously forces all calls to the same ip:port - but this is usually what you want for a proxy server anyway)
t
> Hello All,
>
> I have created a custom UAS xml for my SIPp scenario on UDP - client and
> server running on the same machine, hence different ports need to be
> used). Here's what I noticed using ethereal:
>
> 1. The UAS gets the INVITE from the Proxy server (originally from another
> SIPp UAC). Packet info --> Src Port: 32802, Dst Port: 10001, VIA Header -->
> Via: SIP/2.0/UDP 192.168.0.5:5060 ...
> 2. The UAS sends a "100 Trying" to the server. Packet info --> Src Port:
> 10001, Dst Port: 32802, VIA Header --> Via: SIP/2.0/UDP 192.168.0.5:5060 ...
>
> Shouldn't the UAS send the "100 Trying" message to port 5060, as specified
> in the Via header and not port 32802, which it probably parsed from the
> original UDP packet?
>
> Here's a similar discussion on a SIPmessage board -
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2005-September/010489.html
>
> Thanks,
>
> Vic
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
