Thanks for reply Amir, my concern is which party is working as a dialer. Either TCL script runnong on VXML VG will dial or is there any option in VXML Studio containing "make call" or "dial" element which will forward the request to VXML VG.
A tcl script runs on the egress gateway and periodically polls the VXML gateway to see if there is an outbound call to make. It does this by making a SIP call to a service running on the VXML gateway.
The VXML gateway service makes an HTTP request to VXML server requesting it to run the outbound application.
The outbound application sends a SQL request to the database which runs a query looking for rows with a status of OUTDIAL_PENDING.
Database returns a single row indicating either a valid DNIS to call or ‘xxxx’ indicating that it has no outdials to make at the moment.
If there are no outdials to be made:
the appropriate status will be sent back to the VXML gateway which will simply disconnect the polling SIP leg that originated from the egress gateway. The tcl script on the egress gateway will sleep for X seconds (configurable) before beginning a new polling cycle.
If there is an outdial to be made:
the DNIS to call, the CLI to use for the outdial, and optionally the ring-no-answer timeout (rna) and user-to-user info (uui) will be sent back to the VXML gateway.
I had tried this solution but ended up with a problem. In my case, call initiated by application and it starts ringing on destination phone but then it automatically disconnects after some time (around three seconds). In VXML logs, I can see every call is being disconnected after 15 seconds.
Is anyone else also experience this issue or I am the first one? I have also posted a question on the support forum. Any help to resolve this issue will be appreciated.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
