Menu
▾
▴
Re: [Sipp-users] Unable to connect a twin sipp socket
|
From: Charles P W. <cpw...@us...> - 2008-02-28 15:11:32
|
You should have separate ports for 3pcc and SIP traffic. Also, I think you should have the same address in both 3pcc arguments; it should be the address of the instance that has recvCmd first. Charles sip...@li... wrote on 02/28/2008 09:31:37 AM: > Hi all, > > I'm having a problem when trying to use the 3PCC function. > > I want to use the same server to implement both SIPp twins. So, the > one who sends the 'sendCmd' and the 'recvCmd' will be in the same > machine. But I'm not sure if this configuration is Ok: > > The first to send the sendCmd: Remote-host is 127.0.0.1:5065 > ./sipp -3pcc 127.0.0.1:5060 127.0.0.1:5065 -sf test-A-side.xml > > The first to receive the recvCmd: Remote-host is 127.0.0.1:5060 > ./sipp -3pcc 127.0.0.1:5065 127.0.0.1:5060 -sf test-B-side.xml > > > First, I start the instance who first will receive the recvCmd. But > after starting the other instance, I receive the following message: > > 1204208031.173001: Unable to connect a twin sipp socket > Use 'sipp -h' for details, errno = 111 (Connection refused). > > If you guys have some clue, I'll appreciate it. > > Kind regards, > > Daniel Aires > > Veja mapas e encontre as melhores rotas para fugir do trânsito com o > Live Search Maps! Experimente já! > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sipp-users mailing list > Sip...@li... > https://lists.sourceforge.net/lists/listinfo/sipp-users |
