Use CFD to forward a voicemail message to a call (external phone)

[lblokland]

Hi,

I would like to monitor for voicemail messages on an extension, and forward them (or at least a notification) with an automated call to a number.
I s there a way to achieve this, I cannot find relevant info on reading out a voicemail message.

Thanks.

Leon

 

[Evolute IT]

@VoIPTools for sure

 

[lblokland]

@VoIPTools for sure

This is offtopic....I can also buy another PBX system (for a lot less) .
I'm requesting support for the CFD

 

[Evolute IT]

This is offtopic....I can also buy another PBX system (for a lot less) .
I'm requesting support for the CFD

1. You cannot "monitor" extensions with a CFD. It only processes calls.

2. You should build your own "voicemail" with a database or something like that, store the voicemails in there and use a dialer to call the automated number and use a third CFD to play the audio file. Lots of figuring out to do.

 

[lblokland]

Thanks!
'No' is an answer too!
I was not aware that there was no integration with other parts (then dialing) of the 3CX system.

Anyways, case closed!

 

[SweetAction]

Maybe you could use email notifications of a new voicemail to trigger an action outside of 3CX. I.e. the voicemail box gets a new VM, that sends and email, something is watching that email box and does an action as a result.

 

[VoIPTools]

This is certainly possible. You could use our APIs:

1. Subscribe to new voicemail events
2. Lookup the 3CX extension's mobile number
3. Place a phone call (MakeCallPlayFile)
4. Play the wav file when the call is answered

Using two CFDs:

1. Use a filesystemwatcher to detect when a new voicemail .wav file is created
2. Write a transaction to a database (extension, mobile, wav path)
3. Create CFD1 that continuously loops (with a reasonable pause after each iteration).
4. CFD1 queries the database for any unprocessed transactions
5. If a transaction is found, look up the extension's mobile phone in 3CX
6. Update the transaction with the mobile number
7. Place a phone call between the mobile phone and CFD2
8. CFD2 sees the phone number of the caller, queries the database to find a transaction with a matching mobile phone number
9. Plays the associated wav file.
10. Deletes the transaction

Considerations:

• Someone will have to remember to call CFD1 after every 3CX restart to begin the looping process
• The database MUST reside on a separate server (not the 3CX server)
• Ideally create a web API (running on the database server) rather than make direct database queries
• May want to prompt the mobile caller for an authorization PIN prior to playing the wav file