On 21/07/14 23:56, Praveen Bandari wrote: > Thanks for the reply. Actually the problem is with the SIPp, but I > might be wrong here. Could you validate this. > > -> When I register the user1 on server with -t tn and without > providing the port, the location table shows clientIP:45128 (UAC) > -> I have started the UAS scenario for user1 to listen for messages > using -t tn and without providing the port -> When I register the > user2 on server with -t tn and without providing the port, the > location table shows clientIP:36897 (UAC) -> When I send message to > user1 from user2, I got 477 error (UAC) > > When I talked to my Dev team, they told that the error is due to > the server is unable to send the message to the client using the IP > and port.
That seems completely believable to me - it sounds like you're running a UAC scenario (which will use a random ephemeral TCP port) to register, ending this scenario (so closing the TCP connection), and starting a new UAS scenario to receive calls (which will listen on TCP port 5060). There's nothing on the server to link these two TCP connections, so I wouldn't expect this to work. (One limitation of SIPp's design is that registering and then receiving calls isn't very easy - this is pretty hard to change.) > So, I have modified the script as below and it is working fine. > > -> Register the user1 on server with -t t1 and -p 50001, the > location table shows clientIP:50001 (UAC) -> I have started the UAS > scenario for user1 to listen for messages using -t t1 and -p > 50001, -> Register the user2 on server with -t t1 and -p 50002 , > the location table shows clientIP:50002 (UAC) -> When I send > message to user1 from user2, it was successful. If it's working fine, that's great - though this relies on the server creating a new TCP connection to the client if it doesn't have an active TCP connection to them, so it's not necessarily going to work with all servers. > I am able to achieve this using on UDP with -t u1 option. This has > always registered the user on 5060 and 5061. So, the messages are > working fine. I'd expect this to be fine with UDP - because it's not a connection-oriented protocol, ephemeral ports aren't used in the same way, and you don't need to rely on the server creating new connections. > Please let me know if I am doing correctly. Your approach seems fine. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
