I wanted to clarify the information flow for the SIP case. Here is how
I understand it:
* Alice calls Eve
* Eve does consultation hold, putting Alice on hold and connecting to Bob
* Eve does attended transfer to connect Alice and Bob
So at this point, Eve's endpoint will send a SIP REFER to Alice's endpoint, through
Freeswitch (which basically just passes it along), with the Refer-To header set
to *347*. Eve's endpoint will then send an INVITE to extension *347*. The
dialplan will have an entry for *347* which calls the fdial application passing it the ATTENDED_TRANSFER command. From there the fdial application handles the
rest.
At this point I will need to get handles to the following things within fdial code, and
I'm a little unclear how to do it and would like some advice:
- Handle to the session on hold (Alice) since that is whee the SIP REFER w/ Replaces
will need to be sent. This seems like it might be easy, since this will be the
session passed into the dialplan application.
- Handle to the consultation session to Bob, since the Replaces header will need
to be constructed using this session. (as it is the one being replaced)
Maybe the answer is this .. in the fdial application I am passed the controller,
and using the controller I can get the parked alien (Alice) and the active alien (Bob).
Something like that?
Also I'm having trouble figuring out how to test this with my Sipura endpoints.
I have yet to download Twinkle, do you think it is easy to make Twinkle send a SIP REFER
to Alice with *347* as the Refer-To destination? The other approach I was considering
was using sipp, but I got stuck on sending the dtmfs .. could not really get either
the SIP INFO or pcap-replay approaches working correctly with a dtmf sequence.
(though both work sending a single dtmf).