![]() The SIPp instance which initiates the call is launched in "master" mode. This feature allows any number of SIPp instances toĮach one of them being connected to a remote host. B drops out of the calls.Īn extension of the 3pcc mode is implemented in SIPp. B "REFER"s A to C and asks to replace A-B call with B-C call.In other words, sendCmd and recvCmd can be seen as synchronization pointsīetween two SIPp instances, with the ability to pass parametersĪnother scenario that has been reported to be do-able with the Will receive a "command" from the twin SIPp instance.Īnd stored in a call variable ($2 in this case), ready to be The Call-ID is mandatory in order to correlate the commands to Will send a "command" to the twin SIPp instance. In 3PCC call flows, like call flow I (SIPp being a controller): A Controller B ![]() One SIPp instance can only talk to one remote. In order to keep SIPp simple (remember, it's a test tool!), ![]() It can also be used for every case where you would need one SIPp to talk While this feature was first developed to allow 3PCC like scenarios, Scenario file: uac.xml ( original XML file) SIPp UAC RemoteģPCC stands for 3rd Party Call Control. Scenarios), a few basic (yet useful) scenarios are available Scenarios (see how to create your own XML Integrated scenarios? Yes, there are scenarios that are embedded configure -with-sctp -with-pcap -with-openssl
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |