Answer Detection While Still Ringing

[bgharddisk]

I am having problems with the VG playing the message before the call is answered. I have gone through the steps to properly configure ringback in ConfigLine.xml, but it still is not working. Can you have a look and see if you can see what I am missing.

 

Thank you.

 

Attached:

ringing.wav

tx log

vgm log

configline.xml

vg.zip

[SupportTeam]

Try using these values for the TID_RNGBK1 setting:

 

<Tone Name="Call Progress Tone TID_RNGBK1">

<Notes>Ringback 1 Default Setting</Notes>

<ID>TID_RNGBK1</ID>

<Freq1>430</Freq1>

<Freq1Dev>30</Freq1Dev>

<Freq2>480</Freq2>

<Freq2Dev>30</Freq2Dev>

<On>200</On>

<OnDev>20</OnDev>

<Off>400</Off>

<OffDev>40</OffDev>

<Count>1</Count>

</Tone>

[bgharddisk]

Still answers when ringing. I attached the new logs. Standing by. Thank you.

updated.zip

[SupportTeam]

What is the model of the Dialogic card being used?

 

You could try removing the TID_RNGBK2 definition from configLine.xml file altogether, just in case it somehow conflicts with the TID_RNGBK2 definition.

[bgharddisk]

The card is a D/4 PCI UF running Dialogic SR 6.0 PCI

 

I removed TID_RNGBK2 and tested. I got the same result.

 

I made another recording (attached) with more rings to see if the cadence really did break as tw reports, but it looks uniform to me.

ring.wav

[SupportTeam]

Not sure why it is not detecting ringback...

 

Another thing to note is that it traces are showing "No Cadence" - which probably means that the Dialogic card did detect ringback, but then ringback went away (ie. Dialoigc card could not detect it anymore).

 

If Dialogic did not detect ringback at all then it would report "No Ringback" instead... (CR_NORB)

 

Lets try relaxing the ringback definition a bit. Try this:

 

<Tone Name="Call Progress Tone TID_RNGBK1">

<Notes>Ringback 1 Default Setting</Notes>

<ID>TID_RNGBK1</ID>

<Freq1>430</Freq1>

<Freq1Dev>100</Freq1Dev>

<Freq2>0</Freq2>

<Freq2Dev>0</Freq2Dev>

<On>200</On>

<OnDev>50</OnDev>

<Off>400</Off>

<OffDev>100</OffDev>

<Count>1</Count>

</Tone>

[bgharddisk]

Same. Logs Attached.

updated2.zip

[SupportTeam]

What version of Windows are you running?

 

Are you using the original SR6.0 release or a later Service Update version?

[bgharddisk]

Windows Xp Pro

Its build "74 Production"

[bgharddisk]

I can't stay up all night waiting. I have to wake up early and explain why the dialer is not working. Please let me know a few options on what to do next when you respond because I won't be able to get in touch with you until tomorrow night (~12 hour time difference). Thanks.

[SupportTeam]

Its build "74 Production"

Please change the SR6.0 driver installation to either the original release ("Build 61") or the latest version ("Build 125"). We don't know what the "74 Production" version of SR6.0 is, maybe that release has a problem with ringback detection...

 

As an interim solution you could use the announce message option to ask recipients of call to "Press1 to accept this call..."

[bgharddisk]

YOU are the man. SR6 125 seems to have resolved the issue.

[SupportTeam]

Thanks for letting us know that installing the new Dialogic drivers fixed the problem.

 

Let us know if we can assist with anything in the future.