Hi,
I was wondering is there a way to make Asterisk blind transfer using REFER supporting the following scenario (Asterisk is the Transferee) like if the transfer agent is busy with response 486 to have it in the notify sipfrag so Transferor can re-invite back the original dialog to recover the call after the failed transfer.
Transferor providing the Transfer Target’s contact information to the Transferee (Asterisk). The Transferee (Asterisk) attempts to establish a session using that contact and reports the results of that attempt to the Transferor. The signaling relationship between the Transferor and Transferee is not terminated, so the call is recoverable if the Transfer Target cannot be reached.
I’d like to have the exact scenario like in https://tools.ietf.org/html/rfc5589#page-15
I turned on debugging and received the REFER message from the Transferor but Asterisk treats this blind transfer as fire and forget and soft-hang the channel.
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: Received request
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: Method is REFER
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_refer.c: Created progress monitor '0x7fea531a4748' for transfer occurring from channel 'PJSIP/team-000000a1' and endpoint 'team'
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_refer.c: Accepting REFER request for progress monitor '0x7fe9a40196f0'
[Nov 22 04:30:17] DEBUG[24120] res_pjsip/pjsip_message_filter.c: Re-wrote Contact URI host/port to 209.135.217.186:5060 (this may be re-written again later)
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: Function session_inv_on_tsx_state_changed called on event TSX_STATE
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The state change pertains to the endpoint 'team(PJSIP/team-000000a1)'
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The inv session does NOT have an invite_tsx
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The UAS REFER transaction involved in this state change is 0x7fe9f4085cb8
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The current transaction state is Completed
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The transaction state change event is TX_MSG
[Nov 22 04:30:17] DEBUG[24120] res_pjsip_session.c: The current inv state is CONFIRMED
[Nov 22 04:30:17] DEBUG[24120] parking/parking_bridge_features.c: Checking if 9725980143@transfer_to_pstn is a parking exten
[Nov 22 04:30:17] DEBUG[2728] devicestate.c: No provider found, checking channel drivers for PJSIP - pstn
[Nov 22 04:30:17] DEBUG[2728] devicestate.c: Changing state for PJSIP/pstn - state 2 (In use)
[Nov 22 04:30:17] DEBUG[24120] bridge_channel.c: Setting 0x7fea4800d2f0(PJSIP/team-000000a1) state from:0 to:2
[Nov 22 04:30:17] DEBUG[2757] app_queue.c: Device 'PJSIP/pstn' changed to state '2' (In use) but we don't care because they're not a member of any queue.
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge_native_rtp.c: Bridge '7a7da3ff-3540-4a6d-8bd0-1085a4b0da15'. Checking compatability for channels 'PJSIP/pstn-000000a2' and 'PJSIP/team-000000a1'
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge_native_rtp.c: Bridge '7a7da3ff-3540-4a6d-8bd0-1085a4b0da15' can not use native RTP bridge as channel 'PJSIP/pstn-000000a2' has features which prevent it
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge.c: Bridge technology native_rtp is not compatible with properties of existing bridge.
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge.c: Bridge technology holding_bridge does not have any capabilities we want.
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge.c: Bridge technology softmix does not have any capabilities we want.
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge.c: Chose bridge technology simple_bridge
[Nov 22 04:30:17] DEBUG[25423][C-00000043] bridge.c: Bridge 7a7da3ff-3540-4a6d-8bd0-1085a4b0da15 is already using the new technology.
[Nov 22 04:30:17] DEBUG[25423][C-00000043] channel.c: **Soft-Hanging (0x02) up channel 'PJSIP/pstn-000000a2**'
Thanks in advace,