Setting Busy Signal in "VG for Dialogic"

[jacksors]

I have applied the VG for Dialogic patch and modified my Transfer call module to do a Hookflash monitored transfer. I have added several paths to results path, including: success, fail, timeout, noanswer, nodialtone, busy, operator, fax and noringback.

 

When the number being dialed is busy, VG just hangs up and leaves the caller on the line and does not proceed with the rest of the script. Log files are attached.

Logs.zip

[SupportTeam]

Have you specified the busy tone on your system in the ConfigLine.xml file? (in VG's \data\ subdirectory).

 

Please post a recording of the busy tone which is played by your Switch/PBX.

[jacksors]

I have the default settings in the Configline.xml file that come with the VG for Dialogic patch, I did not know I needed to modify it.

 

What settings specifically should I change?

 

I have attached a recording of the busy signal on our PBX.

 

The caller hears the call being placed on hold (there are 2 click on the line) then a long pause. When the phone is busy VG just hangs up leaving the caller on the line.

busy.zip

[SupportTeam]

Using Audacity (audacity.sourceforge.net) we can see that the busy tone has cadence of 500ms ON, 500ms OFF, with the tone being composed of two frequencies of 475Hz and 625Hz.

 

In ConfigLine.xml change this section:

<Tone Name="DISCONNECT set by Telstra">

<Notes>Telstra's disconnect tone</Notes>

<ID>DISCONNECT_Telstra</ID>

<Freq1>425</Freq1>

<Freq1Dev>50</Freq1Dev>

<Freq2>0</Freq2>

<Freq2Dev>0</Freq2Dev>

<On>37</On>

<OnDev>5</OnDev>

<Off>37</Off>

<OffDev>5</OffDev>

<Count>2</Count>

</Tone>

 

To reflect your settings. ie. make it like this:

 

<Tone Name="DISCONNECT set by Phone Company">

<Notes>disconnect tone</Notes>

<ID>DISCONNECT_Telco</ID>

<Freq1>475</Freq1>

<Freq1Dev>50</Freq1Dev>

<Freq2>625</Freq2>

<Freq2Dev>50</Freq2Dev>

<On>50</On>

<OnDev>5</OnDev>

<Off>50</Off>

<OffDev>5</OffDev>

<Count>2</Count>

</Tone>

[jacksors]

I made the changes to the file. VG still hung up when the number being dialed was busy. Logs are attached with configline.xml file. Based on the description "disconnect by telco" it seems like we are modifying the wrong entry. Shouldnt we be modifying the Busy entries in the configline.xml file?

 

Something about the monitored transfer that is bothering me. When the person recieving the transfer picks up, VG does not immediately connect the call. The person has to say something, then there is a brief delay, then the caller is connected. Is there a way to change this behavior so the caller is instantly connected on pickup?

Logs.zip

[jacksors]

Not sure if this has anything to do with the problem, but i'll just put it out here.

 

The phone system that the VG server is connected to is an analog computer based telephone system. The numbers that VG are dialing are on a seperate digital system or a cell number. Could this cause any problems?

[jacksors]

Uploading config.xml as well

Config.zip

[jacksors]

Here is a copy of my transfer module using monitored hookflash. I am also attaching vg.ini file

 

on {fail} goto [AvailableTechs]

on {timeout 60} goto [AvailableTechs]

on {busy} goto [AvailableTechs]

on {noanswer} goto [AvailableTechs]

vg.zip

[jacksors]

I have a D/4PCIU card, if that helps anything. What is a good card to get that will integrate with a digital phone system?

[jacksors]

Just trying to provide as much info as possible. The OS is XP Pro SP2. Running Intel Dialogic SR 5.11 with the D/4PCIU add-on support software. The Feature Pack 1 software for Dialogic is not installed.

[SupportTeam]

Your Config.xml is missing lots of stuff... have a look at the original config.xml and you'll see that you've deleted the entire <Parms> section...

 

Please post a trace of the attempted transfer.

[jacksors]

Will making the changes to the config.xml file help with the detecting of the busy signal?

 

 

I have seen in several posts that people use the play module with a ! and a phone number to transfer a call. When is it advisable to use this approach? I have attached my script for review.

 

When the call is made, the user his 2 clicks, then a long silence. Is there anyway to have the caller here the number being dialed during the transfer? My PBX supports on call music, we may eventually implement that feature to help with the silence, but I would like to know if there is anything that can be done about the silence or even reduce the amount of silence by speeding up the call transfer?

SimplifiedVariables.zip

[SupportTeam]

Will making the changes to the config.xml file help with the detecting of the busy signal?

Busy signal is set in ConfigLine.xml file, but Config.xml should contain other configs that are vital for call transfers... have a look at the original Config.xml and you'll see what I mean... Don't just delete whole sections out of the Config.xml unless you are advised to do that - you will run into trouble if you do...

 

I have seen in several posts that people use the play module with a ! and a phone number to transfer a call. When is it advisable to use this approach? I have attached my script for review.

It's just another way of sending signals to the PBX. Using Play modules lets you quickly send exactly what you want to send without changing around any of the PBX string configs.

 

Is there anyway to have the caller here the number being dialed during the transfer?

Not on most PBX systems... when you do a transfer manually on this system does the original caller hear the destination extension being dialed?

[jacksors]

The settings in config.xml were removed because they stopped my system from transferring calls. I have attached the log files.

 

After I added these settings back to the file, when the call was being transferred, the caller only heard one click, followed by a beep, then the number being dialed. A long pause and then the script followed the fail path and the dialed number never rang.

 

I have also uploaded screen shots of my dialogic TSP settings, they are all the defualt settings. I have next to no experience/knowledge about how this stuff works. I have been struggling to get this working for a long time. I like the software, its easy to use and does what I need, but if I can't get it to work with my system soon, we will not be purchasing it.

 

I am contacting the vendor for our phone system today to see if they can provide info on what I need to put in the TSP settings to work with this system. With out those lines in config.xml, the defualt settings seem to work just fine except for disconnecting on busy.

 

Could VG just be falsly detecting or sending a drop disconnect on busy instead of just a busy signal?

Logs.zip

[jacksors]

Dialogic TSP settings

Dialogic_TSP_settings.zip

[jacksors]

The script we have written is going to be used for tech support. The way I have the script written is to check to see if the first tech is available before transferring to the second tech. In reading one of your PDF's it shows VG can queue calls. Maybe there is a better way for me to accomplish this than what I am doing.

 

Do you have any sample VBS scripts on how to handle calls and queue them?

[ktruk]

Sounds like you havn't got your hook-flash timing right. The click is probably the hook-flash and when that doesn't work, you get dial tone, followed by the dialing DTMF tones. Since the hook-flash is failing - the ext never rings and you hear the dialling on your line... just a suggestion...

[jacksors]

I a configuration book for our phone system and modified several settings in the config.xml file. This solved the problem I was facing earlier where I would hear the number being dialed and the call not being transferred, it is working now.

 

However it is still dropping the call when the line being dialed is busy, the logs are attached as well as an updated config.xml file.

 

 

Point 2:

Delay when using mointored transfer. The person answering has to say something in order for VG to recognize that the call was answered. Can't VG just detect that the phone is no longer ringing? There is about a 4 second delay from the time the answering party says something till the caller is patched through.

 

Thanks.

Logs.zip

[jacksors]

I made the following modifications to my Configline.xml file:

 

Based on information provided earlier in this post regarding the frequency of the busy signal, I modified the TID_BUSY1 settings to look like this(also visible in the file):

 

<Tone Name="Call Progress Tone TID_BUSY1">

<Notes>Default Setting</Notes>

<ID>TID_BUSY1</ID>

<Freq1>475</Freq1>

<Freq1Dev>50</Freq1Dev>

<Freq2>625</Freq2>

<Freq2Dev>50</Freq2Dev>

<On>50</On>

<OnDev>5</OnDev>

<Off>50</Off>

<OffDev>5</OffDev>

<Count>2</Count>

</Tone>

 

I changed the "Disconnect_Telco" settings in the same file to the values shown on the "Board Parameters" page of the Dialogic TSP settings(visible in screen shot of earlier post today), that now look like this.

 

<Tone Name="DISCONNECT set by Phone Company">

<Notes>disconnect tone</Notes>

<ID>DISCONNECT_Telco</ID>

<Freq1>620</Freq1>

<Freq1Dev>200</Freq1Dev>

<Freq2>480</Freq2>

<Freq2Dev>200</Freq2Dev>

<On>30</On>

<OnDev>10</OnDev>

<Off>20</Off>

<OffDev>10</OffDev>

<Count>3</Count>

</Tone>

 

Now, the TID_BUSY1 matches the frequency that the BUSY signal makes on the phone, and I entered those values into the BUSY category not the DISCONNECT category to see if the script would see the call as BUSY instead of just disconnecting it.

 

As you can see be reviewing the attached log files, VG did see the line as BUSY. The log files attached in the previous post (when the above mentioned settings where reversed) where showing a DISCONNECT. However, despite the fact that VG sees it as BUSY, it still drops the call.

 

Please review attached log files and Configline.xml file. Thanks

new.zip

[SupportTeam]

Trace shows two calls with a transfer at end of each call.

 

On first call the Dialogic card detected that a human answered the transfer and completed the call by hanging up.

 

On second call the busy tone was detected.

 

152108.78  1      Dial(9,7983679, cp on) call

152108.78  1      Dial(9,7983679) ok

152108.78  1 timer set 60  EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

152120.58  1 tw    DialogicEvent 134,TDX_CST,191,0,0,DE_TONEON,TID_BUSY1,

152120.59  1 event BUSY, code=134, state=1903

152120.59  1      LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,BUSY,191,0,0,DE_TONEON,TID_BUSY1,

152120.61  1 rv    add [Hangup Time]{5/11/2005 3:21:20 PM}

152120.61  1 state Hanging up call...

152108.781    ocxfn Dial(1,0,[9,7983679],DX_PAMDOPTEN,0,0,,)

152108.781          dx_dial(1,[9,7983679],on)

152108.781          dx_dial(1,9,7983679) ok

152120.578 001 ev    TDX_CST (CST Event Received)

152120.578 001 ev    TDX_CST DE_TONEON data=191

152120.578    ocxev DoFireDialogic(dwIdx=60, 1, 134, [TDX_CST], 191, 0, 0, [DE_TONEON], [TID_BUSY1], [])

 

We're looking at this problem now...

[jacksors]

The log should show two completeions. I called the system, picked up the phone and left that call connected(so it would show busy). Called the system again and this time VG should have seen that the call was busy and continued with the script, however it just hung up.

 

Was I right in modifying the TID_BUSY1 settings in the configline.xml file? This made the log file show that it saw the line as "BUSY" instead of "Disconnect_telco" like it did before. All I did was move the settings from "Disconnect_telco" to "TID_BUSY1". Should doing this make VG react differently?

 

Or is there some other setting somewhere else that I should modify?

 

Thanks.

[SupportTeam]

Please place attached file in VG's directory overwriting exiting file, and try transfer to busy extension test again.

If problems persist please post extracts from vgm trace.

Was I right in modifying the TID_BUSY1 settings in the configline.xml file?

Yes.

VgMulti_6.0.2001.zip

[jacksors]

Here are the log files. It is still disconnecting the call.

Logs.zip

[jacksors]

The new logs should show 3 calls.

 

The first call was answered and left on the line to show busy.

 

The next call was from a land line and VG hung up.

 

The last call was from a cell and VG hung up.

 

The version I am currently running is 5.2.3a trial version.

[jacksors]

I reverted to the previous version of the Vgmulti file and modified my script to do an Announced transfer instead of a monitored hookflash transfer. I looked at the log files and it shows that it correctly identified the line as TID_BUSY1 and that it was going down the {false} path. It should be going down the {busy} path, but since they both go to the same place, it doesnt matter.

 

The logs show that it went to the module after the transfer, but then it hung up the call. It should have just continued on and tried to make another transfer but it did not. This also be something to look into.

Anounced.zip

[jacksors]

What are your support hours? Is there a contact number?

[jacksors]

Uploading a file, logs.zip contains 3 zip files.

Config.zip - current config files (configline.xml, config.xml, vg.ini)

newVGfile.zip - log files from using the new VGmulti.exe file sent in previous post

dialogicpatch.zip - log files using VGMulti.exe from the VG for Dialogic patch.

 

Log files show the following when using the VGmulti sent in previous post:

 

The caller makes the call, VG starts the transfer. The dialed number phone rings 4 times, VG transfers the call and the caller hear's the phone ringing. This should not be happening.

 

When using VG for Dialogic VGmulti.exe:

 

Phone rings 3 times then VG follows the fail path. Hits the next transfer module, phone rings 2 times, VG follows the fail path. VG never seems to follow the timeout path or even wait till it hits the timeout period, why?

 

It appears that the new VGMulti.exe you sent me did not resolve my detecting of the busy signal, as you can view by reviewing the logs in this post "Posted on May 12 2005, 11:45 PM", and it has also generated another problem, it ends up just transferring the call.

 

I have reverted back to my previous version of VGMulti.exe file from the VG for Dialogic Patch. However, this is still dropping calls when it detects the busy signal. It seems VG is ignoring all paths except the fail path.

Logs.zip

[SupportTeam]

From trace posted on May 12 2005, 11:45 PM:

 

We see that when a call was being transferred to a busy extension the system correctly detected that the destination extension was busy, and VG then played a hookflash to retrieve the transferred call.

 

However after the hookflash was played the PBX dropped loop current on the line - which is used to indicate that the PBX has ended the call - so VG hung up as well.

 

How do you usually retrieve call transfers on this PBX? ie. if you were doing a call transfer manually and you found the destination extension busy what do you press on the phone handsets to retrieve the call?

 

084035.48  1 tw    DialogicEvent 133,TDX_CALLP,7,0,0,CR_BUSY,,

084035.48  1 event TDX_CALLP, code=133, state=1903

084035.50  1      LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,7,0,0,CR_BUSY,,

084035.50  1 xfer  dial !

084036.16  1 tw    PlayEnd 1 0

084036.16  1 play  end id=0, (current ID)

084036.17  1 event EV_PLAY_FINISHED, code=8001, state=1906

084036.17  1      LsXfer_5B : 8001(EV_PLAY_FINISHED),EV_PLAY_FINISHED,0,0,0,,,

084036.19  1 tw    DialogicEvent 132,TDX_DIAL,0,0,0,,,

084036.19  1 event TDX_DIAL, code=132, state=1906

084036.19  1      LsXfer_5B : 132(EV_UNKNOWN_132),TDX_DIAL,0,0,0,,,

084036.20  1      sXferDialResult_SuccOrFail=

084036.20  1      path {CR_BUSY} not found

084036.22  1 event callstate DISCONNECTED 1 0 0

084036.22  1 event EV_REMOTEPARTY_DISCONNECT, code=9250, state=6001

084036.22  1 rv    add [Hangup Time]{5/12/2005 8:40:36 AM}

 

 

084035.484    ocxev DoFireDialogic(dwIdx=60, 1, 133, [TDX_CALLP], 7, 0, 0, [CR_BUSY], [], [])

084035.500    ocxfn Dial(1,0,[!],,0,0,,)

084035.500          dx_dial(1,[&],off) as ca_intflg=2

084035.500          dx_dial(1,&) ok

084036.156 001 ev    TDX_DIAL (Dial Completed)

084036.156 001 ocxev PlayEnd(dwLineId=1, dwPlayId=0)

084036.187    ocxev DoFireDialogic(dwIdx=61, 1, 132, [TDX_DIAL], 0, 0, 0, [], [], [])

084036.187 001 ev    TDX_CST (CST Event Received)

084036.187 001 ev    TDX_CST DE_LCOF data=3007

084036.218 001 te    LINE_CALLSTATE(1, 0x1, 0x4000, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_DISCONNECTED-DE_LCOF

084036.250 001 ocxfn RecStop(hLine=1, lRecId=0, lParam1=0, lParam2=0, strParam1=, strParam2=)

084036.250 001 ocxfn PlayStop(hLine=1, lPlayId=0(0x0), lParam1=0, lParam2=0, strParam1=, strParam2=)

084036.265 001 ocxfn LineDrop(sLineId=1, sOpt=0)

[jacksors]

We press the flash key. If you want to transfer someone, you press flash, dial the extension ( or 9 then the number) and you get connected.

 

One of the things I see in the excerpts you posted is "xfer dial !". Is this VG playing the hookflash to retrieve the call from hold after it determines it is busy?

 

If so, I have found in some documentation on our phone system that the hookflash sysmbol is & sign not a !. If I modify the the VG.ini file and give it the & symbol instead of !, would this help to correct the problem?

 

If this were to correct the problem, how is VG successfully able to issue a hookflash to put the call on hold but not able to reissue the same signal to retrieve the call?

 

Could VG be incorrectly detecting this "PBX dropped loop current" and inadvertanly dropping the call?

 

When you say "PBX dropped loop current on the line" is this a signal/frequency/PBX string that can be set in a configuration file or in the Dialogic TSP window?

 

Does the Configline.xml, config.xml and VG.ini files overwrite or take prescedence over all settings in the Dialogic TSP screen that can be accessed from the "phone and modem" selections in the Control Panel?

 

Does VG use or access any of the settings that are posted on the Dialogic TSP screens?

 

The ConfigLine.xml file has two entries that seem to be optional: <Tone Name="DISCONNECT set by Phone Company"> and <Tone Name="DISCONNECT sent by PBX">. These two strings to be redundant since there is a "TID_DISCONNECT" setting defined earlier. Can I remove these entries, are thery really necessary?

 

I have also noticed that VG, when making the transfer through the Transfer Call module only keeps the call open for about 30 seconds before taking a fail path or dropping the call. I have a {timeout 60} set that VG never seems to use. Why?

 

It would be great if you could answer each question individually, or if multiple questions have one answer thats fine. I'm attempting to learn as much about this as I can so I can provide you with the best possible information. Please be as thorough as you can. Thanks.

[jacksors]

When VG is making this transfer, it is playing a hookflash (to put the call on hold), then dialing a 9(to access an outside line - the number being dialed is not on this PBX system), then a pause (,) then an external number. Would dialing the 9 to access an outside line cause VG to not properly be able to retrieve the call from hold when it detects a busy signal?

 

If so, what can we do to work around this problem?

 

 

One last thought. What we are trying to accomplish is to dial a number, if their is an answer transfer the call, if no answer, try the alternate, if an answer transfer, if not send to VM. Is there another/better way of accomplishing this other than what I am doing? If so please let me know. Thanks.

[SupportTeam]

One of the things I see in the excerpts you posted is "xfer dial !". Is this VG playing the hookflash to retrieve the call from hold after it determines it is busy?

Yes.

I have found in some documentation on our phone system that the hookflash sysmbol is & sign not a !. If I modify the the VG.ini file and give it the & symbol instead of !, would this help to correct the problem?

Will not make any difference. & and ! both result in the same hookflash being played.

When you say "PBX dropped loop current on the line" is this a signal/frequency/PBX string that can be set in a configuration file or in the Dialogic TSP window?

No. Loop Current is something different. We'll need to give you a version of the

VoiceGuide software which ignores loop current drops.

Does VG use or access any of the settings that are posted on the Dialogic TSP screens?

Not "VG for Dialogic". "VG for Dialogic" does not use the TAPI drivers...

 

The ConfigLine.xml file has two entries that seem to be optional: <Tone Name="DISCONNECT set by Phone Company"> and <Tone Name="DISCONNECT sent by PBX">. These two strings to be redundant since there is a "TID_DISCONNECT" setting defined earlier. Can I remove these entries, are thery really necessary?

Yes, you can remove them. They are there to demonstrate how multiple disconnect tones can be specified.

I have also noticed that VG, when making the transfer through the Transfer Call module only keeps the call open for about 30 seconds before taking a fail path or dropping the call. I have a {timeout 60} set that VG never seems to use. Why?

I assume this relates to for how long a transfer will be attempted before the transfer is abandoned if the call is not accepted? Will check on this on or test system here.

[jacksors]

Quote:

No. Loop Current is something different. We'll need to give you a version of the

VoiceGuide software which ignores loop current drops.

 

When can I exect this version of VG?

 

I am going to do some manual testing of this today and work with our vendor.

 

 

Does dialing 9 to access the outside line have any effect on retrieving the call from hold and getting the drop loop current signal?

[jacksors]

Excerpt from log:

 

090400.00 1 tw DialogicEvent 133,TDX_CALLP,7,0,0,CR_BUSY,,

090400.00 1 event TDX_CALLP, code=133, state=1903

090400.00 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,7,0,0,CR_BUSY,,

090400.02 1 xfer dial !

090400.67 1 tw PlayEnd 1 0

090400.67 1 play end id=0, (current ID)

090400.69 1 event EV_PLAY_FINISHED, code=8001, state=1906

090400.69 1 LsXfer_5B : 8001(EV_PLAY_FINISHED),EV_PLAY_FINISHED,0,0,0,,,

090400.70 1 tw DialogicEvent 132,TDX_DIAL,0,0,0,,,

090400.70 1 event TDX_DIAL, code=132, state=1906

090400.70 1 LsXfer_5B : 132(EV_UNKNOWN_132),TDX_DIAL,0,0,0,,,

090400.72 1 sXferDialResult_SuccOrFail=

090400.72 1 path {CR_BUSY} not found

 

Why does the log say {CR_BUSY} instead of busy? do I need to define a {CR_BUSY} path?

 

 

I have also found a [CallControl] section in VG.ini that says it can IGNORE a LoopCurrentDrop, however it does not seem to work.

[jacksors]

This application is beginning to frustrate me terribly. I have changed nothing yet VG is now transferring the call to the number being dialed regardless of whether anyone answered or not. Logs are attached.

 

I have been in this forum now for 2 weeks and have accomplished nothing. Is there anyway to get better support?

Logs.zip

[jacksors]

Since VG is on one PBX system, and the calls are going to another PBX system (or a cell phone) should the settings in the Configline.xml file match those on the PBX system that VG is attached to or dialing?

[jacksors]

VG is reacting differently everytime I make a call as indicated by the excerpts below. I have found that if I modify(or remove) the following section in my Configline.xml file in any way, that VG dials the first number and then just makes the transfer, the log file shows that it monitors a hookflash even though nothing happened:

 

<Tone Name="DISCONNECT set by Phone Company">

<Notes>disconnect tone</Notes>

<ID>DISCONNECT_Telco</ID>

<Freq1>620</Freq1>

<Freq1Dev>200</Freq1Dev>

<Freq2>480</Freq2>

<Freq2Dev>200</Freq2Dev>

<On>30</On>

<OnDev>10</OnDev>

<Off>20</Off>

<OffDev>10</OffDev>

<Count>3</Count>

</Tone>

 

A call is placed to VG, VG answers and attempts to make a transer:

 

113321.80 1 Dial(9,7983679, cp on) call

113321.80 1 Dial(9,7983679) ok

113321.81 1 timer set 60 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

113339.08 0 sys cleanup Start

113339.13 0 sys cleanup End

113342.30 1 tw DialogicEvent 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113342.31 1 event RINGBACK, code=134, state=1903

113342.31 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,200,0,0,DE_TONEON,TID_RNGBK2,

113342.31 1 event TID_RNGBK2, code=134, state=1903

113342.31 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK2,200,0,0,DE_TONEON,TID_RNGBK2,

113342.31 1 event TDX_CST, code=134, state=1903

113342.33 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113342.97 1 tw DialogicEvent 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113342.97 1 event RINGBACK, code=134, state=1903

113342.97 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,199,0,0,DE_TONEON,TID_RNGBK1,

113342.97 1 event TID_RNGBK1, code=134, state=1903

113342.97 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK1,199,0,0,DE_TONEON,TID_RNGBK1,

113342.98 1 event TDX_CST, code=134, state=1903

113342.98 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113344.97 1 tw DialogicEvent 133,TDX_CALLP,9,0,0,CR_NORB,,

113344.97 1 event TDX_CALLP, code=133, state=1903

113344.97 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,9,0,0,CR_NORB,,

113344.98 1 xfer dial !

113345.64 1 tw PlayEnd 1 0

113345.64 1 play end id=0, (current ID)

113345.64 1 event EV_PLAY_FINISHED, code=8001, state=1906

113345.64 1 LsXfer_5B : 8001(EV_PLAY_FINISHED),EV_PLAY_FINISHED,0,0,0,,,

113345.64 1 tw DialogicEvent 132,TDX_DIAL,0,0,0,,,

113345.66 1 event TDX_DIAL, code=132, state=1906

113345.66 1 LsXfer_5B : 132(EV_UNKNOWN_132),TDX_DIAL,0,0,0,,,

113345.66 1 sXferDialResult_SuccOrFail=

113345.66 1 path {CR_NORB} not found

113345.66 1 path {noringback} not found

113345.66 1 going down False path (iXferType=12) state:LsXferCallRejected

113345.67 1 timer clear

113345.67 1 state [AvailableTechs] Evaluate [$RV[GatherStoreInformation_1_1]]

 

Determines that no one has answered and takes the fail path in the script (not VG does not wait the 60 seconds and follow the timeout path).

 

VG then makes it to the next Transfer Call module and attempts to make the transfer:

 

Dial(9,3611511, cp on) call

113357.61 1 Dial(9,3611511) ok

113357.61 1 timer set 60 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

113412.86 1 tw DialogicEvent 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113412.86 1 event RINGBACK, code=134, state=1903

113412.86 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,199,0,0,DE_TONEON,TID_RNGBK1,

113412.86 1 event TID_RNGBK1, code=134, state=1903

113412.86 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK1,199,0,0,DE_TONEON,TID_RNGBK1,

113412.88 1 event TDX_CST, code=134, state=1903

113412.88 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113419.48 1 tw DialogicEvent 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113419.50 1 event RINGBACK, code=134, state=1903

113419.50 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,200,0,0,DE_TONEON,TID_RNGBK2,

113419.50 1 event TID_RNGBK2, code=134, state=1903

113419.50 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK2,200,0,0,DE_TONEON,TID_RNGBK2,

113419.50 1 event TDX_CST, code=134, state=1903

113419.52 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113420.78 1 tw DialogicEvent 133,TDX_CALLP,9,0,0,CR_NORB,,

113420.78 1 event TDX_CALLP, code=133, state=1903

113420.78 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,9,0,0,CR_NORB,,

113420.78 1 xfer dial !

113421.44 1 tw PlayEnd 1 0

113421.44 1 play end id=0, (current ID)

113421.44 1 event EV_PLAY_FINISHED, code=8001, state=1906

113421.45 1 LsXfer_5B : 8001(EV_PLAY_FINISHED),EV_PLAY_FINISHED,0,0,0,,,

113421.45 1 tw DialogicEvent 132,TDX_DIAL,0,0,0,,,

113421.45 1 event TDX_DIAL, code=132, state=1906

113421.45 1 LsXfer_5B : 132(EV_UNKNOWN_132),TDX_DIAL,0,0,0,,,

113421.45 1 sXferDialResult_SuccOrFail=

113421.47 1 path {CR_NORB} not found

113421.47 1 path {noringback} not found

113421.47 1 False path not defined - hangup call (iXferType=12)

113421.47 1 timer set 2 EV_TIMEOUT_HANGUP

 

VG dials the number, no one answeres so it checks to see what it should do. No fail path is defined. Note that it does not wait 60 seconds and take the fail path, so it just hangs up the call.

 

Another call is made, VG answers and attempts to make a transfer:

 

113508.56 1 LsXfer_2_OnEndHook1PlayDestNbr 9030,EV_TIMEOUT_Transfer_Prefix_PauseAfter,0,0,0,,,

113508.56 1 Dial(9,7983679, cp on) call

113508.56 1 Dial(9,7983679) ok

113508.56 1 timer set 60 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

113524.25 1 tw DialogicEvent 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113524.27 1 event RINGBACK, code=134, state=1903

113524.27 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,200,0,0,DE_TONEON,TID_RNGBK2,

113524.27 1 event TID_RNGBK2, code=134, state=1903

113524.27 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK2,200,0,0,DE_TONEON,TID_RNGBK2,

113524.27 1 event TDX_CST, code=134, state=1903

113524.27 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,200,0,0,DE_TONEON,TID_RNGBK2,

113530.81 1 tw DialogicEvent 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113530.83 1 event RINGBACK, code=134, state=1903

113530.83 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,RINGBACK,199,0,0,DE_TONEON,TID_RNGBK1,

113530.83 1 event TID_RNGBK1, code=134, state=1903

113530.83 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TID_RNGBK1,199,0,0,DE_TONEON,TID_RNGBK1,

113530.83 1 event TDX_CST, code=134, state=1903

113530.83 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 134,TDX_CST,199,0,0,DE_TONEON,TID_RNGBK1,

113544.80 1 tw DialogicEvent 133,TDX_CALLP,10,1,0,TDX_CALLP,CR_CNCT,CON_CAD

113544.80 1 event CON_CAD, code=133, state=1903

113544.80 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,CON_CAD,10,1,0,CR_CNCT,CON_CAD,CON_CAD

113544.80 1 event TDX_CALLP, code=133, state=1903

113544.80 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,10,1,0,CR_CNCT,CON_CAD,CON_CAD

113544.81 1 LsXfer_3 CR_CNCT on an XT_HOOK_MONITORED

113544.81 1 xfer dial

113544.81 1 tw PlayEnd 1 0

113544.81 1 play end id=0, (current ID)

113544.83 1 event EV_PLAY_FINISHED, code=8001, state=1905

113544.83 1 LsXfer_5A : 8001(EV_PLAY_FINISHED),EV_PLAY_FINISHED,0,0,0,,,

113544.83 1 tw DialogicEvent 132,TDX_DIAL,0,0,0,,,

113544.83 1 event TDX_DIAL, code=132, state=1905

113544.83 1 LsXfer_5A : 132(EV_UNKNOWN_132),TDX_DIAL,0,0,0,,,

113544.83 1 sXferDialResult_SuccOrFail=

113544.84 1 rv add [Hangup Time]{5/13/2005 11:35:44 AM}

113544.84 1 state Hanging up call... [LsXfer_5A]

113544.84 1 HangupCall_Common hCall=1

 

Same as before, no one picks up the reciever, however VG thinks the call was accepted and transfers it. Why? No configuration files were changed. These calls were placed withing seconds of each other.

 

 

Also note, that in the first example when no one answered, VG issues a hookflash to successfully retrieve the waiting call and then went on to make the next call.

 

Why is VG able to successfully issue a hookflash and retrieve the on hold call and make the next transfer when no one answers and fail to perform the same action when the number being dialed is detected as busy?

2results.zip

[jacksors]

Does the Non-VG for Dialogic version of Vg allow one to identify the frequency and cadance of the busy signal?

[SupportTeam]

Does dialing 9 to access the outside line have any effect on retrieving the call from hold and getting the drop loop current signal?

Loop current drop is done by PBX. You need to ask PBX maker when do they drop loop current and how you can control that setting.

Why does the log say {CR_BUSY} instead of busy? do I need to define a {CR_BUSY} path?

VG will test for both CR_BUSY and BUSY paths. BUSY path is sufficient. Path checking was stopped there as the loop current drop signal arrived.

I have also found a [CallControl] section in VG.ini that says it can IGNORE a LoopCurrentDrop, however it does not seem to work.

This only works now for the TAPI version of VG. We will post here soon a version of "VG for Dialogic" which will use this setting as well.

should the settings in the Configline.xml file match those on the PBX system that VG is attached to or dialing?

Just record what tones are being played in different situations and set the XML config files appropriately.

 

These two traces:

113344.97 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,9,0,0,CR_NORB,,

 

113420.78 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,9,0,0,CR_NORB,,

show that Dialogic call progress indicated that call was not connected as Ringback cadence was not heard - we can see the ringback tone beginning as DE_TONEON events are arriving for the ringback, but guess that ringback just started playing a bit too long after dialing completed... will look more into this.

 

 

This trace:

113544.80 1 tw DialogicEvent 133,TDX_CALLP,10,1,0,TDX_CALLP,CR_CNCT,CON_CAD

shows that Dialogic call progress indicated that call was connected as the Ringback was heard and then it went away - so call is considered connected as there is no moe ringback online - although it does not appear that anyone has said anything after answering the phone.

 

have you set the ringback settings properly on your system match what the Dialogic card would be hearing when it makes an outgoing call?

 

Does the Non-VG for Dialogic version of Vg allow one to identify the frequency and cadance of the busy signal?

Use a sound file editor like CoolEdit or Audacity for this.

[jacksors]

I opened a new tread entitled "Timeout Path Not Taken". I decided to reload VG, and this time it is producing some different results. I guess it is taking VG longer to detect the drop loop current signal after detecting a busy signal than before. Cause now VG is executing several modules before hanging up. Please review this post. Thanks.

 

What is confusing me, is why is VG able to issue the hookflash and retrieve the call from hold and continue with the script when there is no answer (ie the call just rings back) but it is not able to do this (ie it detects a drop loop current) when the call is busy?

[SupportTeam]

What is confusing me, is why is VG able to issue the hookflash and retrieve the call from hold and continue with the script when there is no answer (ie the call just rings back) but it is not able to do this (ie it detects a drop loop current) when the call is busy?

VG goes through exactly the same process when the call is busy - it issues the hookflash and retrieves the call from hold and tries to continue with the script - but then the PBX drops loop current, which results in call hangup.

If you can get the PBX to not drop loop current then the problem would be solved.

[jacksors]

That would be awesome. Any thoughts on how I can go about doing that?

 

I can call our phone system vendor and ask them about this. What questions should I ask them, or what should I be looking for in the PBX setup?

 

When the call just rings back and no one answers it, does the PBX drop the loop current? I am assuming no since the script continues successfully?

 

Would the PBX system we use be setup to handle ring backs and busy signals differently? Meaning, (it sounds like) our system is dropping a call when it detects a busy signal, but not when it is detecting a ring back?

[jacksors]

QUOTE

should the settings in the Configline.xml file match those on the PBX system that VG is attached to or dialing?

 

 

Just record what tones are being played in different situations and set the XML config files appropriately.

 

 

 

This didnt really answer the question. See, I have the IVR box plugged into a computer telephony system and it makes calls to other locations that have different PBX systems. We make calls to land lines and cell phones.

 

Does VG compare the tones it hears on the remote system to the configline.xml file? If so, wouldnt I need to define what a busy, disconnect, ring back etc.. sound like on every system that we are dialing?

 

How would this be accomplished, especially if a tone for a ring back on one system sounds similar to a busy on another and VG interprets the call the wrong way?

[SupportTeam]

Does VG compare the tones it hears on the remote system to the configline.xml file?

Voiceguide compares the tones that it hears with the tones listed in ConfigLine.xml file.

Whether these tones are played by the remote system or by the local switch/PBX depends on how the Switch/PBX and the systems at the other end are set up.

Such questions should be directed to your phone company.

 

If so, wouldnt I need to define what a busy, disconnect, ring back etc.. sound like on every system that we are dialing?

 

How would this be accomplished, especially if a tone for a ring back on one system sounds similar to a busy on another and VG interprets the call the wrong way?

If you are seeing a great variety of busy etc tones in your environment and you are finding that you are unable to set the tone definition parameters in a way that interprets these tones to your satisfaction then the best thing for you to do is to get a Digital T1/E1 ISDN line. With T1/E1 ISDN you do not need to set any tone definitions. All call connection signaling is done using ISDN signal messages.

[jacksors]

I am reposting this reply I posted earlier because these questions were not addressed. Thanks

 

That would be awesome. Any thoughts on how I can go about doing that?

 

I can call our phone system vendor and ask them about this. What questions should I ask them, or what should I be looking for in the PBX setup?

 

When the call just rings back and no one answers it, does the PBX drop the loop current? I am assuming no since the script continues successfully?

 

Would the PBX system we use be setup to handle ring backs and busy signals differently? Meaning, (it sounds like) our system is dropping a call when it detects a busy signal, but not when it is detecting a ring back?

[jacksors]

Ok, after working with the vendor, I think we may have a solution, just need a little more configuration help.

 

We modified our PBX to use a menu assisted transfer option. When making calls, my transfer call module now needs to be setup like this (#,9,PhoneNumber). This works, VG is successfully able to make calls. And, in the few tests I have done has detected the busy signal and gone down the busy path.

 

My problem is retrieving the call from hold. When a hookflash is issued to retrieve the call from hold, there is a 3-4 second pause followed by a menu asking the caller what they want to do with the onhold call.

 

What I need to do is be able to issue this command (,,,,4 (where 4 is the number that reconnects IVR to the caller)). When working with just the phone system this works great!! How do I accomplish this through the VG script????

 

I have read that a play module can be setup to issue a set of commands and then continue on with the script. Please provide instruction on how to setup a play module (or whatever is needed) to allow me to retrieve this call from hold. Thank you.

[SupportTeam]

That question was just answered in your other thread.

In Script Designer go to "Edit"->"PBX Command Strings" and change the Retrieve Call setting to be !,,,,4

Please place any new questions in one thread only (the new one).