Hi all I keeping on testing Call Transfer scenario (using 3PCC), not working yet. I'm thinking that the problem could be the following.
When the 3pcc instances are started such as: 1) sipp -sf CT_Controller_Side_C.xml 172.24.7.231:5081 -p 5084 -3pcc 172.24.3.16:3000 Controller_side_C.xml .... ..... <sendCmd> <![CDATA[ Call-ID: [call_id] ]]> </sendCmd> ..... ..... Is mandatory to send the Call-ID to the other twin sipp instance. Then when B_User start the new call with C_user will use the same Call-ID. I mean both dialogs (A-B and B-C) are equal. This will a problem later, since I need to send a REFER message from B_User to A_user REFER sip:[EMAIL PROTECTED] SIP/2.0 [last_Via:] From: "+420911211000" <sip:[EMAIL PROTECTED]>;tag=[call_number] To: [$1] Call-ID: [$2] CSeq: [cseq] REFER Contact: "sipp" <sip:[EMAIL PROTECTED]:[local_port];transport=udp> Max-Forwards: 70 Referred-By: "+420911211000" <sip:[EMAIL PROTECTED]> Refer-To: <sip:[EMAIL PROTECTED]:5094;transport=udp?Replaces=[$3]> User-Agent: Sipura/SPA841-3.1.4(a) Content-Length: 0 Note: [$2] is the Call-ID A-B dialog [$3] should be the Call-ID B-C dialog So whether both dialog are equal this will be a problem and the REFER message will not sent. 2) sipp -sf CT_BController_Aside.xml 172.24.7.231:5081 -p 5074 -3pcc 172.24.3.16:3000 So, I am wondering whether really is possible to make the Call Transfer scenario with ·3pcc. Any help/suggestion will be welcome. Thanks and regards Rosa -----Original Message----- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: miércoles, 09 de enero de 2008 16:43 To: Maria Rosa Vieira Alvarez Cc: Boulkroune, Olivier (Non-HP:Atos Origin); [email protected] Subject: RE: [Sipp-users] RE: Call Transfer Scenario-3pcc (Urgent¡¡) If you have a start_rtd XML attribute you must have a corresponding RTD attribute. Charles Maria Rosa Vieira Alvarez <[EMAIL PROTECTED]> 01/09/2008 10:25 AM To "Boulkroune, Olivier (Non-HP:Atos Origin)" <[EMAIL PROTECTED]>, Charles P Wright/Watson/[EMAIL PROTECTED] cc [email protected] Subject RE: [Sipp-users] RE: Call Transfer Scenario-3pcc (Urgent¡¡) Hi Oliver/all Thanks for your answer/help. I've tried what you said, I mean without 3pcc extended mode, so I don`t use "-slave_cfg" parameter, but not working yet. Now I got the following ERROR message. "You have started Response Time Duration 1, but have never stopped it!" I am starting the test like this: >sipp -sf B_Controller-C_Side.xml 172.24.7.231:5081 -p 5084 -3pcc 172.24.3.15:5074 Where (172.24.3.15:5074 ) is the IP:Port regarding to "B_controller-A_Side.xml" Thanks again, Regards Rosa -----Original Message----- From: Boulkroune, Olivier (Non-HP:Atos Origin) [mailto:[EMAIL PROTECTED] Sent: miércoles, 09 de enero de 2008 10:08 To: Maria Rosa Vieira Alvarez; Charles P Wright Cc: [email protected] Subject: RE: [Sipp-users] RE: Call Transfer Scenario-3pcc (Urgent¡¡) Hi Maria, Regarding your test case (A calls B, and B user transfers call to C user), you don't need the 3pcc extended mode, which is to be used when more than two sipp 3pcc instances must be synchronized. Just use the 3pcc mode like that: - B is played by two sipp 3pcc instances - A and C are played either by normal sipp instances or by the devices you intent to test (if any) The call flow will then be the same than the one described in the doc: http://sipp.sourceforge.net/doc/reference.html#3PCC , except that the controller A will receive the INVITE from the remote, instead of sending it. So, both 3pcc instances have to be launched with the -3pcc option, the argument being the address of the other instance. You don't need the -slave_cfg option (which is incompatible with the -3pcc option, you should have had an error when launching something like -3pcc X.X.X.X:Y -slave_cfg my_cfg_file). Regards, Olivier Boulkroune -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Maria Rosa Vieira Alvarez Envoyé : mardi 8 janvier 2008 10:50 À : Charles P Wright Cc : [EMAIL PROTECTED]; [email protected] Objet : [Sipp-users] RE: Call Transfer Scenario-3pcc (Urgent¡¡) Hi The Error message that I'am getting is "get_peer_addr: Peer m not found " Thanks, Regards Rosa -----Original Message----- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: miércoles, 02 de enero de 2008 14:51 To: Maria Rosa Vieira Alvarez Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: [Sipp-users] Call Transfer Scenario-3pcc (Urgent¡¡) Without the exact error message you are getting, it is almost impossible to teel what is wrong. Charles [EMAIL PROTECTED] wrote on 12/28/2007 04:41:30 AM: > Hi > I need help regarding to call transfer scenario (A calls B, and B > user transfers call to C user). I?ve understood is needed to execute > 3PCC mode (http://sipp.sourceforge.net/doc/reference.html#3PCC). > I?ve already created the SIPp xml files (4 xml) such as is explained > in main sipp page, but I don?t know how to launch them. I am using > 3PCC extended mode, so, I have a ?master? instance and a ?slave? > instance. Then how would be the right way to launch both > instances??.. I am trying the following without successful. > > Ø sipp ?sf B_Controller_C_side.xml 172.24.7.231:5081 ?p 5078 > -3pcc ?slave_cfg instances > > 172.24.7.231:5081 (P-CSCF regarding to IMS) > > instances file > s1;172.24.3.15:5078 > m;172.24.3.15:5074 > > Thanks in advance, and regards > Rosa------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------ ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
