3rd Party Call Control

Setting a remote target makes it possible to talk to two or more different endpoints within the same scenario. In the example the program makes the first call, puts the remote side on hold, creates another dialog to a different endpoint and then transfers. If SIP Inspector talks to two or more endpoints it is not mandatory to use different Call-IDs; the INVITEs and their dialogs are told apart by where they are sent.

---- Remote=192.168.1.110:55634
---> INVITE          // first call
<--- 100*
<--- 180
<--- 200
---> ACK
---- Pause[ms]=2000
---> INVITE          // put it on hold
<--- 200
---> ACK
---- Pause[ms]=2000
---- Remote=192.168.1.105:5112
---> INVITE          // second call
<--- 100*
<--- 180
<--- 200
---> ACK
---- Pause[ms]=2000
---- Remote=192.168.1.110:55634
---> REFER
<--- 202
<--- NOTIFY
---> 200
---- Remote=192.168.1.105:5112
---> BYE
<--- 200
<--- BYE
---> 200

At the moment SDP is not passed between the calls automatically, so make sure that a codec that both endpoints can use is enforced. Sending SIP requests to different addresses can be combined with a values file: SIP requests are sent to a list of addresses, which lets you probe addresses and ports within a range (see Port_scan_client.txt). Complete transfer examples: Call_transfer_client.txt, Call_transfer_server.txt and Call_brokering_b2bua_server.txt.