No Ring Back

[Guest jackthehack]

A 'No Ring Back' condition is resulting in my scripts starting when they shouldn't. I understand that the associated tone definition should be specified with sufficient tolerance to avoid this. In my case (VOIP), I have determined that it is the low volume of the tone, not the frequencies or cadence, that results in it going undetected, from time to time.

 

Based on my limited understanding, it seems counter-intuitive that a 'No Ring Back' condition should start the script rather than abort the call.

 

Is there any way to abort a call attempt under these circumstances? At this time, my scripts are configured to wait for call recipient confirmation before continuing, but I am looking for a more elegant solution.

 

Thanks

[SupportTeam]

it seems counter-intuitive that a 'No Ring Back' condition should start the script rather than abort the call.

Som phone systems (Digital) can answer the call immediately when the call arrives, and in these situations you would not hear any ringbacks if analog lines are used to place the outgoing call. That is why the Dialogic analog cards are treating "NO_RINGBACK" as a connected call.

 

Is there any way to abort a call attempt under these circumstances?

We could name a VG.INI settable change in VoiceGuide which would allow you to have those "NO_RINGBACK" calls treated as failed calls and hangup the call. You will however then get situations where some people will receive calls which ring 2 of 3 times and then stop, or situations where a person after answering the call has the system hangup on them...

 

These type of issues are the reason why analog lines are a poor choice for making outgoing call and professional solutions use Digital T1/E1 ISDN lines.