[captivateglobal]

Hi,

Whilst talking to 3CX about it they mentioned they use the VAD to deliver music on hold. Since there is no option in the base 3CX platform for MoH outside of the five files you specify, we wonder if there is a way we can use the VAD to deliver music on hold?

Would the application made by VAD be responsible for handling the phone call from the moment it hits the trunk, or can it just take effect in an 'on hold' environment?


Cheers,

Dylan

[VAD_Support]

Hi,

No, music on hold is played by 3CX media server. You can not do that with a VAD application. A VAD application can play an audio file, but you can not transfer the call to the VAD callflow when it's on hold...

Regards,

[captivateglobal]

Hi,

No, music on hold is played by 3CX media server. You can not do that with a VAD application. A VAD application can play an audio file, but you can not transfer the call to the VAD callflow when it's on hold...

Regards,

Okay, how about a VAD Application which acts as the main trunkline?

That is to say, any phone calls are intercepted and processed by this VAD application. The VAD application then would make another 'leg' of the call, to wherever it was meant to go in the first place. However, then the VAD application will still have vision of the phone call.

When the VAD is placed on hold, instead of blindly playing 3CX Media Server's audio to the other client, it could instead play back from a stream source, SIP extension, or any other content you could think of.

Would this be possible?

[VAD_Support]

No, unfortunatelly a VAD application can not make a second call. It can only transfer the call in blind mode, so the call is not passing through it any more. Bridge mode transfers are not supported.

[SWSDEV]

What happened to bridge mode transfers?

Why was this functionality taken away?

[VAD_Support]

That never really worked. The 3CX IVR is not capable to do bridge transfers, so we removed it from the VAD to avoid confusions.

[SWSDEV]

OK, that makes sense.

But what about the VAD just waiting to complete a transfer until the line is answered. This is existing functionality in 3CX that I'd think would be simple to include in the VAD.

[VAD_Support]

That's true, but VAD applications run under the 3CX IVR, which has a limited functionality related to transferring calls. 3CX as an entire system has more control about it, because it is done outside the 3CX IVR.

I really hope to get that problem addressed in the future...