Call Conferencing Doesnt Not Hang Up

[SangAstra]

Im using VG for dialogic. Call conferencing is put through successfully but after either party hangs up - VG shows line state back to waiting for call - however the line is actually remining busy and not hung up.

 

Please advise urgently - event trace log attached.

event_trace1230_141205.txt

[SupportTeam]

Trace shows that about 10 seconds after the 3-way call was established the Dialogic card indicated that it detected that call is ended as disconnect tone was heard on the line:

 

122955.89 3 tw DialogicEvent 134,TDX_CST,191,0,0,DE_TONEON,DISCONNECT_TAPI1,

 

VoiceGuide then hung up as well and the Dialogic card sent confirmation that the line was hung up:

 

122955.99 3 event callstate IDLE 3 1,0,0

 

So it all looks fine from the Dialogic's side...

 

Only other thing we can do is to look at the MMDDtw.txt log, just to confirm the lower level is functioning as expected (see VG's \log\ subdirectory).

[SangAstra]

to look at the MMDDtw.txt log,

 

There is no such log in vg directory or elsewhere on the PC (i've done a search too)

[SupportTeam]

If logging level has been set to a value other then 0 then log files will be created in \log\ subdirectory. MMDD stands for Month and Day...

[SangAstra]

attached as requested

tw_file.txt

[SangAstra]

hi we sorted out the above by setting Detect loop current drop = 1 but there is a new problem.

 

Call gets disconnected without reason.

 

please see attached logs

1215tw.txt

[SangAstra]

Hello Support?

 

Are we going to go to next day for the reply??

[SupportTeam]

Traces show that after issuing "!,3" to connect the 3rd caller the Dialogic card detects that the loop current drop happens on the line.

 

And as you've set SendDisconnectOnLoopCurrentDrop=1 this instructs the Dialogic card to send a disconnect as well when it detects loop current drop - and then VoiceGuide disconnects when it gets that message...

 

The Dialogic card is not detecting any loop current drop events when a hookflash is sent when the number is dialed, so there is probably changing the 'minimum loop current off time' would not change anything.

 

You can try though... by adding this section to Config.xml file - just after the DXBD_FLASHTM entry:

 

<SetParm>

<Description>Minimum Loop Current Off<Description>

<Key>DXBD_MINLCOFF</Key>

<Value>50</Value>

<Default>50</Default>

</SetParm>

 

It is looking like you should be considering using 'Dial and Conference' instead...

[SangAstra]

hookflash causing loop current drop

 

i've looked at subsequent logs. The disconnect is happening randomly even before call transfer is initiated - what else could be the cause?

 

im using d/4 card which doesnt support dial and conferencing

 

what next please?

[SupportTeam]

The disconnect is happening randomly even before call transfer is initiated - what else could be the cause?

Could you please post a copy of VoiceGuide's Debug Printout which captures the event, this will allow us to see what happened.

 

When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.

You can enable the automatic saving of the logs to files in \log\ directory as well.

When posting traces please .ZIP them up and post them as attachments.