I'm testing a system which supports SIP over TCP. For calling party tests this is all good - my normal sipp scripts from UDP testing can register and then send an invite and make the call merely by adding '-t t1' at the command line.
For the terminating party, however, I have a problem: - Server-mode scripts MUST start with a receive, so cannot begin with a REGISTER - Client-mode scripts discard messages with non-matching Call_IDs so whilst they can register, they cannot process incoming INVITES I got around this in UDP by having 2 scripts - running one in client mode to register then another one in server mode to receive calls. In TCP this approach does not work: my registration at the SBC is discarded as soon as the TCP session is terminated, i.e. when the client-mode registration script exits in sipp - which means that the server-mode script used to process INVITES will never receive anything. Has anyone come up with an approach to get this working: registering and receiving invites successfully using SIP over TCP? My last resort option is to hack a copy of SIPP to use a single listener and pass all received messages to that listener irrespective of Call_Id. But I'm hoping there's a tidier solution, Matt ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
