VoiceGuide IVR Software Main Page
Jump to content

D/41jct-ls (dx_getdig() And Dx_gtcallid()) Dtmf

Recommended Posts

hello, this from Intel General Dialogic Discussion Forum, the first post is from me and the second is a replay on my post.

 

================================================================================

======

 

Topic: D/41JCT-LS - CallerID in DTMF support? (1 of 2), Read 15 times

Conf: General Dialogic Discussion

Date: Wednesday, March 23, 2005 09:58 AM

 

hello, this is my first post here.

i wonder before i buy the D/41JCT-LS card if it support detecting the CallerID in my country.

im in saudi arabia, and the teleco here use DTMF when sending the CallerID not FSK.

we are using an IVR software (VoiceGuide.com) and wondering if we have to do extra coding work to get the callerID or the card will do it and detect the callerid and pass it to the IVR software when the call come.

 

thanks.

 

 

================================================================================

======

 

 

Topic: D/41JCT-LS - CallerID in DTMF support? (2 of 2), Read 9 times

Conf: General Dialogic Discussion

Date: Thursday, March 24, 2005 05:28 AM

 

Hi,

The board supports DTMF digit collection while the line is on-hook. It uses the dx_getdig() function to retrieve these rather than the dx_gtcallid(), so it will probably require a change in the application.

Regards,

Dan

 

================================================================================

======

 

 

my question is will (VoiceGuide + D/41JCT-LS) detect the callerid?

is it possible tm make the Dcard use dx_getdig() instead of dx_gtcallid().

 

im not a C programmer, will have to do any programing work to do this? can VoiceGuide do it transparency?

Share this post


Link to post

VoiceGuide should be accepting DTMF tones before the call is answered.

 

Please do this test:

1. Restart VG.

2. Make a call into the system.

Important: Make sure this test call is the first call into system after restarting!

3. Post the trace of the initialization and fist arriving call.

 

 

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.

It is the MMDDvgm.txt logs from VG's \log\ subdirectory that will contain the initialization and the first call details.

Share this post


Link to post

hello

 

 

 

1. Restart VG.

OK

 

 

2. Make a call into the system.

Important: Make sure this test call is the first call into system after restarting!

 

Ok , VoiceGuide anserwd the call and the script is runing.

 

 

 

3. Post the trace of the initialization and fist arriving call.

170812.11  9 linedevstate 2048 0 0
170812.11  9 callstate OFFERING 66136 0 4
170812.11  9 callinfo CALLEDID
170812.11  9 callinfo ORIGIN
170812.11  9 ring 0
170812.66  0 dial  start any summary:|6:idx=0|7:idx=0|8:idx=0|9:hc>0|
170818.11  9 ring 2
170818.11  9 rv    clear
170818.11  9 Answer the call at 24/05/2005 05:08:18 PM
170818.11  9 lineAnswer(66136) => 66426
170818.66  9 callstate CONNECTED 66136 1 0
170818.66  9 callstate CONNECTED 66136,1,0
170818.66  9 WorkingModeTAPI@Connected=
170818.67  9 WorkingModeScript@Connected=
170818.67  9 Inband detection not enabled
170818.67  9 StartLoadedVgs at 24/05/2005 05:08:18 PM, script interpretor VgMulti v5.2.4000 0
170818.67  9 rv    ns add [ScriptsPath]{E:\YmYm\}
170818.69  9 rv    ns add [ScriptPath]{E:\YmYm}
170818.69  9 rv    lg add [$RV_STARTTIME]{24/05/2005 05:08:18 PM}
170818.69  9 rv    lg add [$RV_DEVICEID]{9}
170818.69  9 rv    lg add [$RV_CIDNAME]{}
170818.69  9 rv    ns add [PathApp]{C:\Program Files\VoiceGuide\}
170818.69  9 rv    lg add [$RV_CIDNUMBER]{}
170818.69  9 tapi  Reply (LineEvReply) ok 66426 0
170818.69  9 timer clear
170818.70  9 [Play 11] Playing
170818.70  9 rv    replace start: [Hello Saleh your Phone Number is $RV_CIDNUMBER]
170818.70  9 rv    ns [PathSysVoice]{}[PathApp]{C:\Program Files\VoiceGuide\}[PathDataVm]{C:\Program Files\VoiceGuide\data\}[PathVgSys]{C:\Program Files\VoiceGuide\system\}[ScriptsPath]{E:\YmYm\}[ScriptPath]{E:\YmYm}[$RV_STARTTIME]{24/05/2005 05:08:18 PM}[$RV_DEVICEID]{9}[$RV_CIDNAME]{}[PathApp]{C:\Program Files\VoiceGuide\}[$RV_CIDNUMBER]{}
170818.70  9 rv    replace end: [Hello Saleh your Phone Number is ]
170818.70  9 rv    replace start: [Hello Saleh your Phone Number is $RV_CIDNUMBER]
170818.72  9 rv    ns [PathSysVoice]{}[PathApp]{C:\Program Files\VoiceGuide\}[PathDataVm]{C:\Program Files\VoiceGuide\data\}[PathVgSys]{C:\Program Files\VoiceGuide\system\}[ScriptsPath]{E:\YmYm\}[ScriptPath]{E:\YmYm}[$RV_STARTTIME]{24/05/2005 05:08:18 PM}[$RV_DEVICEID]{9}[$RV_CIDNAME]{}[PathApp]{C:\Program Files\VoiceGuide\}[$RV_CIDNUMBER]{}
170818.72  9 rv    replace end: [Hello Saleh your Phone Number is ]
170818.72  9 tts generate start[Hello Saleh your Phone Number is ]
170818.72  9 tts generate wait
170818.73  9 RunModule PLAY end
170818.73  9 callinfo MONITORMODES
170818.78  9 tts   generate finish. lineCallState=CONNECTED
170818.80  9 amchk test AMdet in TtsToWavFileFinished => False
170818.80  9 [Play 11] Playing (C:\Program Files\VoiceGuide\data\tts_9_1.wav)
170818.80  9 play set playid=814375
170818.81  9 PlaySoundStart ok [C:\Program Files\VoiceGuide\data\tts_9_1.wav]
170818.81  9 timer clear
170818.83  9       wa(2805,81437500)
170818.83  9 callinfo MONITORMODES
170821.69  9 play  end current play (playid=814375)
170821.69  9 ScriptEventCode 8001 iLineState=1100
170821.69  9 LsPlayMsg EV_PLAY_FINISHED
170821.70  9 timer set 10  EV_TIMEOUT_HANGUP
170821.70  9 timer set 0  EV_TIMEOUT_GOTOMODULE
170821.70  9 ScriptEventCode 9002 iLineState=1101
170821.72  9 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE
170821.72  9 rv    lg add [Play 11]{timeout}
170821.72  9 timer clear
170821.73  9 rv    lg add [Hangup Time]{24/05/2005 05:08:21 PM}
170821.73  9 Hanging up call... [Hangup Module]
170821.73  9 RecSoundStop ok
170821.75  9 PlaySoundStop err=0
170821.75  9 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP
170821.77  9 fnHangupCall end
170821.80  9 linedevstate 2048 0 0
170821.81  9 callstate IDLE 66136 0 0
170821.81  9 WorkingMode@Idle=
170821.81  9 timer clear
170821.83  9 timer set 1  EV_TIMEOUT_TIMETOREINITLINE
170821.84  9 tapi  Reply (LineEvReply) ok 66409 0
170822.89  9 timer fired EV_TIMEOUT_TIMETOREINITLINE
170822.89  9 ScriptEventCode 9008 iLineState=900
170822.91  9 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE
170822.92  9       ReinitTelephony due to IDLE
170822.92  9 tapic lineDeallocateCall(MainCall:66136) 0
170822.98  9 lineOpen(9)=>
170823.00  9 Waiting for a call...
170823.00  9 LineHandle=65555
170823.02  9 amchk set AMdet=False in Reinit@idle
170823.03  9 timer set 3  EV_TIMEOUT_ATERIDLE_ALLOWOUT
170823.66  0 dial  start any summary:|6:idx=0|7:idx=0|8:idx=0|9:rdy=0|
170825.84  0 sys   cleanup Start
170825.86  0 sys   cleanup End
170826.31  9 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT
170826.31  9 ScriptEventCode 9013 iLineState=900
170826.69  0 dial  start any summary:|6:idx=0|7:idx=0|8:idx=0|9:idx=0|

 

 

 

by the way i did not find "Saudi Arabia" on the "Intel Dialogic Configuration Manager" on the Country Tap.

 

i selected India and then Belgium, but still cant detect the caller ID.

Share this post


Link to post

if any one know how to configure D/41JCT-LS in the (Intel Dialogic Configuration Manager) for Saudi Arabaia "Configuration Parameter"

 

i am ready to pay for him..

Share this post


Link to post

hi

 

i found this:

 

Caller Line Identification (CLI)
Products which offer CLI, should recognize DTMF signalling in accordance
with the following requirements:
ETSI ES 235-3 V1.2.1
Access and terminals (AT) specification of Dual –Tone Multi Frequency
(DTMF) Transmitters and receivers; Part 3 Receivers.
In section 4.2.1.1 of the above standard, the following figures should be
applied:
a) The tolerance of signalling frequencies should fall within +/- 1.8% +2Hz
b) The receiver should recognize signalling frequencies which fall in the
range –3 to –25dBm
c) The difference between signalling frequencies recognized by terminal
equipment should not exceed 5dB
In section 4.2.2 Digit Recognition Condition Requirements are as described in
table 3 with the following exception:
a) the receiver should not recognize a valid signal of duration less than 24ms
b) the receiver should ignore signal breaks of less than 10ms

http://www.citc.gov.sa/NR/rdonlyres/ABF08C0B-F460-4568-9B16-CBBFC1770FA6/390/AI001AnaloguePSTNdraft2.pdf

 

i dont know where do i put this!

 

can some one help me to configure my dialogic to catch CallerID with VoiceGuide.

 

 

thank you

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
×