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
