VoiceGuide IVR Software Main Page
Jump to content

Cli Has Disappeared

Recommended Posts

Hi All,

 

I recently had a problem with our Dialogic card where it stop recognising DTMF tones. I solved this problem, by moving our one line system from the first port to the second port (we have a four port board, but only use one poet) I can only suppose that the first port has broken or something, as the second port works properly, however we are not getting CLI. I have checked that CLI is on the line, by plugging in a regular phone and it shows it fine,

 

I have looked around the settings in VoiceGuide but can't see anything like "CLI on/off". Also the CLI information is not shown in the VoiceGuide call log, were it used to show before.

 

Nothing has changed in our script, the only thing has changed is that we are using the second port on the Dialogic card instead of the first port.

 

Has anyone any ideas?

 

Many thanks - Colin

 

 

Share this post


Link to post

If the CLI/CallerID is not showing up in the VoiceGuide log this means that the Dialogic card is not detecting any CLI being sent.

 

As the first port on that card is faulty then most likely the CallerID detection on that card is broken as well.

 

You could try using other ports, but more likely you will need to get a new card.

 

You can post the VoiceGuide logs here to let us confirm what is going on.

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

ktTel=10

SapiWrapOcx=0

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

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

 

 

 

 

Share this post


Link to post
If the CLI/CallerID is not showing up in the VoiceGuide log this means that the Dialogic card is not detecting any CLI being sent.

 

As the first port on that card is faulty then most likely the CallerID detection on that card is broken as well.

 

You could try using other ports, but more likely you will need to get a new card.

 

You can post the VoiceGuide logs here to let us confirm what is going on.

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

ktTel=10

SapiWrapOcx=0

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

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

 

If the CLI/CallerID is not showing up in the VoiceGuide log this means that the Dialogic card is not detecting any CLI being sent.

 

As the first port on that card is faulty then most likely the CallerID detection on that card is broken as well.

 

You could try using other ports, but more likely you will need to get a new card.

 

You can post the VoiceGuide logs here to let us confirm what is going on.

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

ktTel=10

SapiWrapOcx=0

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

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

 

--------------------

 

Hi there

 

Sorry about the delay in replying, but I was called out of the office for a few days - back now.

 

Tried all other port and still no CLI

 

Enclose log of a call with CLI - would be grateful if you could have a look.

 

Regards - Colin

 

0917tw.zip

Share this post


Link to post

It looks like the system is setup to answer when the first ring arrives

 

The CallerID information is usually sent between the first and the second ring, so the system should be setup to answer after the second ring.

 

Please change the Config.xml file to have the system answer the call after the second ring and then restart VoiceGuide.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×