How To Test Card Dialogic ?

[Guest huuphuc]

Hi.

I have a card dialogic D/300PCI-E1, please help me how to test D/300PCI-E1 work? I had setup voiceguide v7.

Are you sent my mail adrress: huuphuc1976@yahoo.com.vn? Thanks.

[SupportTeam]

The Dialogic card needs to be tested with Dialogic's ISDIAG test tool to confirm it is working on your E1. Once the card is working you can then install VoiceGuide and start using it.

 

We do offer and installation service. Please contact sales@voiceguide.com for details.

 

[Guest huuphuc]

Dear Sir

I had run ISDIAG, no error but not receive signal from line E1.

Please help me.

My Bpx: Alcaltel Ommi OXO

Protocol: QSIG

Thanks

[SupportTeam]

What does ISDIAG show? Please post some screenshots.

 

We also offer an installation service where we can log into the system and do the Dialogic card testing and installation. Please contact sales@voiceguide.com for pricing.

[Guest huuphuc]

Dear Sir

This is file .jpg. Please help me.

Thanks

[SupportTeam]

Screenshot shows the D channel on the ISDN line is OK. You should now be able to try placing some calls into the system and use ISDIAG to answer the call.

 

You could also start the ISDN level trace.

 

It's best to start a trace then place a call into the system and then answer the cal and then hangup. Then save the ISDN trace and have a look at it (or post it here) to make sure all is OK. Once ISDIAG shows all is OK you can start VoiceGuide and start using VoiceGuide to receive and make calls.

[Guest huuphuc]

Dear Sir

This is file trace.log, please help me.

trace.log

[SupportTeam]

Trace shows the ISDN's D channel is working fine and the incoming call's SETUP messages can be seen in it.

 

Did you try answering the incoming call using ISDIAG?

 

When you just start VoiceGuide v7 now and place a call into the system what happens?

 

Please post VoiceGuide's ktTel trace which captures the incoming call. ktTel trace is created in VoiceGuide's \log\ subdirectory.

 

I attach the trace translated using Dialogic's ISDTRACE.EXE utility.

trace.txt

[Guest huuphuc]

[Did you try answering the incoming call using ISDIAG?]

Yes, i do.

 

[When you just start VoiceGuide v7 now and place a call into the system what happens?]

No happen.

 

 

0311_ktTel.txt

Voiceguide.bmp

[SupportTeam]

Looking at the System Status screenshot we can see that you have not changed VoiceGuide's Config.xml file to match the Dialogic card which you are using.

 

VoiceGuide by default installs the Config.xml file for a 4 line analog card, and you want the 30 line ISDN version of the Config.xml

 

Do this:

 

1. Stop VoiceGuide.

2. Go to VoiceGuide's \Config\ subdirectory.

3. Rename "Sample Config for 30 ports using one E1 ISDN.xml" to "Config.xml" (overwrite previous Config.xml)

4. Start VoiceGuide.

 

Make another call into system after VoiceGuide is started.

 

post ktTel trace capturing incoming call.

[Guest huuphuc]

Dear Sir

This is a file ktTel.log, please me. Thanks

0311_ktTel.txt

[SupportTeam]

Trace shows that the VoiceGuide starts the Dialogic card OK, and all the 30 channels on the card are opened and unblocked.

 

But no calls are reported by the Dialogic card.

 

Are you using the latest SR6.0 Dialogic drivers?

 

What ISDN protocol have you selected for this card?

 

Which Telco or Switch/PBX supplies this E1? What is the protocol name/spec that that is configured on that Switch/PBX?

[Guest huuphuc]

Dear sir

 

[Are you using the latest SR6.0 Dialogic drivers?]

I using System Release 5.1.1 FP1 Service Update 148, because SR6.0 Dialogic drives not support D/300PCI-E1 card.

 

[What ISDN protocol have you selected for this card?]

ISDN protocol: QSIG / QTE

 

[Which Telco or Switch/PBX supplies this E1? What is the protocol name/spec that that is configured on that Switch/PBX?]

I use PBX Alcatel OXO, connect with Dialogic card via E1 DLT2 Card (QSIG protocol)

[SupportTeam]

Are there any other ISDN protocol options available on the PBX apart from QSIG?

 

If not then do you have a chance to try the setup with the D/300JCT card (and SR6.0)?

 

You can probably obtain the D/300JCT card form your Dialogic supplier on a trial basis to see if this card along with SR6.0 will connect to Alcatel's QSIG properly.

 

[Guest huuphuc]

Thank for the reply.

ISDN protocol's Alcaltel: QSIG only.

I will retry

Thank you very much.

[Guest huuphuc]

Dear Sir

I had receive incoming call, but i don't hear sound.

Please help me.

0212_ktTel.txt

0215_ktTel.txt

[SupportTeam]

Trace shows VoiceGuide is issuing commands for the Dialogic card to Accept and Answer the call, but immediately after issuing the Answer command the Dialogic drivers respond that the call is DISCONNECTED

There is really not much that we can do about this. The card which you are trying to use is old and the drivers have already been discontinued, so this product is not supported by Dialogic any more.

Recommend you change to a D/300JCT card and use the current release SR6.0 drivers.

 

 

 

0212:

 

133050.279 1368 002 ev GCEV_DETECTED crn=0x0=0 {2:crn_set}

133050.279 1368 002 CtEventProcess (from store) idx=32, iDev=2, lEvtType=2084, pEvtData=0x6d36f38, lEvtDataLen=28, (store: evinque=0, maxever=1)

133050.279 1368 002 ev GCEV_OFFERED crn=0x2008001=33587201 (ktTel_SR60 v7.0.5, Feb 26 2008 16:17:15) {2:crn_set}

133050.279 1368 002 calling CIPStateMachine_NullGcevOffered next

133050.279 1368 002 raising LINECALLSTATE_OFFERING next

133050.279 1368 002 CTelProxy::Event_CallState m_pTelProxyClient=0078146C

133050.279 1368 002 raise CallState LINECALLSTATE_OFFERING

133050.340 1368 002 calling OnOffered_GetCallerID next

133050.340 1368 002 OnOffered_GetCallerID start (with CallerID report)

133050.340 1368 002 OnOffered_GetCallerID gc_GetCRN: crn=0x2008001=33587201 {2:crn_set}

133050.350 1368 002 could not retrieve CALLNAME

133050.350 1368 002 CTelProxy::Event_CallerId begin. name=, nbr=123, dnis=102

133050.360 1368 002 raise CallerId

133050.390 1368 002 fn LineAnswerCall(sXMLOptions=[])

133050.400 1368 002 gc_AcceptCall crn=0x2008001=33587201

133050.400 1368 002 CTelProxy::Event_CallerId end

133050.400 1368 002 CtEventProcess (from store) idx=33, iDev=2, lEvtType=2052, pEvtData=0x6d36f68, lEvtDataLen=28, (store: evinque=0, maxever=1)

133050.400 1368 002 ev GCEV_ACCEPT crn=02008001=33587201

133050.400 1368 002 CTelProxy::Event_CallState m_pTelProxyClient=0078146C

133050.400 1368 002 raise CallState LINECALLSTATE_ACCEPTED

133050.400 1368 002 IssueAnswerCallAfterReceivingAcceptedEvent=true

133050.400 1368 002 gc_AnswerCall crn=02008001=33587201

133050.430 1368 002 CtEventProcess (from store) idx=34, iDev=2, lEvtType=2086, pEvtData=0x6d36f98, lEvtDataLen=28, (store: evinque=0, maxever=1)

133050.430 1368 002 ev GCEV_DISCONNECTED crn=02008001=33587201

133050.440 1368 002 GCEV_DISCONNECTED : gcValue=68(0x44), gcMsg=[invalid parameter], ccLibId=2, ccLibName=[GC_ISDN_LIB], ccValue=0x38a, ccMsg=[bad input parameter], additionalInfo=[]

133050.440 1368 002 raise Dialogic GCEV_DISCONNECTED 2086 (2086 0 0 )

 

 

0215:

 

094901.654 2540 002 ev GCEV_DETECTED crn=0x0=0 {2:crn_set}

094901.654 2540 002 CtEventProcess (from store) idx=32, iDev=2, lEvtType=2084, pEvtData=0x6d36f38, lEvtDataLen=28, (store: evinque=0, maxever=1)

094901.654 2540 002 ev GCEV_OFFERED crn=0x200803f=33587263 (ktTel_SR60 v7.0.5, Feb 26 2008 16:17:15) {2:crn_set}

094901.654 2540 002 calling CIPStateMachine_NullGcevOffered next

094901.654 2540 002 raising LINECALLSTATE_OFFERING next

094901.654 2540 002 CTelProxy::Event_CallState m_pTelProxyClient=0078146C

094901.664 2540 002 raise CallState LINECALLSTATE_OFFERING

094901.724 2540 002 calling OnOffered_GetCallerID next

094901.724 2540 002 OnOffered_GetCallerID start (with CallerID report)

094901.724 2540 002 OnOffered_GetCallerID gc_GetCRN: crn=0x200803f=33587263 {2:crn_set}

094901.724 2540 002 could not retrieve CALLNAME

094901.724 2540 002 CTelProxy::Event_CallerId begin. name=, nbr=123, dnis=300

094901.724 2540 002 raise CallerId

094901.764 2540 002 fn LineAnswerCall(sXMLOptions=[])

094901.774 2540 002 gc_AcceptCall crn=0x200803f=33587263

094901.774 2540 002 CTelProxy::Event_CallerId end

094901.795 2540 002 CtEventProcess (from store) idx=33, iDev=2, lEvtType=2052, pEvtData=0x6d36f68, lEvtDataLen=28, (store: evinque=0, maxever=1)

094901.795 2540 002 ev GCEV_ACCEPT crn=0200803F=33587263

094901.795 2540 002 CTelProxy::Event_CallState m_pTelProxyClient=0078146C

094901.795 2540 002 raise CallState LINECALLSTATE_ACCEPTED

094901.795 2540 002 IssueAnswerCallAfterReceivingAcceptedEvent=true

094901.795 2540 002 gc_AnswerCall crn=0200803F=33587263

094901.815 2540 002 CtEventProcess (from store) idx=34, iDev=2, lEvtType=2086, pEvtData=0x6d36f98, lEvtDataLen=28, (store: evinque=0, maxever=1)

094901.815 2540 002 ev GCEV_DISCONNECTED crn=0200803F=33587263

094901.815 2540 002 GCEV_DISCONNECTED : gcValue=68(0x44), gcMsg=[invalid parameter], ccLibId=2, ccLibName=[GC_ISDN_LIB], ccValue=0x38a, ccMsg=[bad input parameter], additionalInfo=[]

094901.815 2540 002 raise Dialogic GCEV_DISCONNECTED 2086 (2086 0 0 )

094901.815 2540 002 CTelProxy::Event_CallState m_pTelProxyClient=0078146C

094901.815 2540 002 raise CallState LINECALLSTATE_DISCONNECTED

 

 

 

[Guest huuphuc]

Dear sir,

 

Would you please help me to solve this problem, we already bought the D/300 SC and D/300 PCI card, but we do not have the D/300JCT. Please also advice us why the Dialogic drivers response disconnected instead of answering the call.

 

What will i need to check out to fix this problem. We are planning to use you VoiceGuide for this project and can not stop it now.

 

Thank you for your supports.

[SupportTeam]

Try using the D/300 PCI card and setting up the SR 5.1.1 drivers on it, then test teh card using the Dialogic's ISDIAG test application.

 

The ISDIAG will let you accept incoming calls and answer them.

 

Once ISDIAG is working try installing VoiceGuide v6 and see if calls get answered with v6

[Guest huuphuc]

Dear Sir

I had receive incoming call, but i don't hear sound. I use VoiceGuide v6.

Please help me.

0227tw.txt

0227vgm.txt

[SupportTeam]

Trace shows that the Dialogic drivers are reporting a GCEV_DISCONNECTED immediately after the incoming call has been 'Accepted'.

 

This is the same as what the previous traces where showing.

 

Have you tried testing with ISDIAG to see if ISDIAG can answer incoming calls?

 

Does your PBX offer other ISDN protocols other then QSIG? If it does then please try using them to see if the Dialogic card/drivers can work with your /PBX using another ISDN protocol.

 

Apart form the above the only other option is to get a D/300JCT from your local distributor and setup this system with the current SR6.0 drivers.

 

 

090043.343 002 ev GCEV_OFFERED (ktTelControl v2.4.5, Mar 30 2008 13:04:46)

090043.343 002 could not retrieve CALLNAME

090043.343 002 ocxev CallerId(sLineId=2, hCall=0(0x0), crn=33587203(0x2008003) strCallerID=[122], strName=[], strDialed=[300])

090043.343 002 ocxev DoFireDialogic(dwIdx=4, 2, 2084, [GCEV_OFFERED], 2084, 0, 0, [], [], []) (dwIdx=4)

090043.343 002 gc_CallAck(crn=33587203(0x2008003), 0x8e5bfbc GCACK_SRVICE_PROC, EV_ASYNC) call

090043.343 002 eng gc_GetMetaEventEx returned. lEvtHandle=0, iDev=2, lEvtType=2150, pEvtData=0xe6b31c8, lEvtDataLen=28

090043.343 002 ev metaevent: cclibid=0x2, crn=0x2008003, evtdatap=0xe6b31c8, evtdev=0x2, evtlen=0x1c, evttype=0x866, extevtdatap=0x0, flags=0x1, linedev=0x2, magicno=0xbad012fb, rfu1=0x2, usrattr=0x1e2d78 (usrattr=hli)

090043.343 002 ev GCEV_CALLPROC (2150) has no handler

090043.343 002 ocxev DoFireDialogic completed

090043.343 002 te LINE_CALLSTATE(2, 0x2, 0x2, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_OFFERING

090043.343 002 eng gc_GetMetaEventEx returned. lEvtHandle=0, iDev=2, lEvtType=2049, pEvtData=0xe6b7168, lEvtDataLen=28

090043.343 002 ev metaevent: cclibid=0x2, crn=0x2008003, evtdatap=0xe6b7168, evtdev=0x2, evtlen=0x1c, evttype=0x801, extevtdatap=0x0, flags=0x1, linedev=0x2, magicno=0xbad012fb, rfu1=0x2, usrattr=0x1e2d78 (usrattr=hli)

090043.343 002 ev GCEV_TASKFAIL

090043.343 002 gc_GetCallState(crn=33587203)

090043.343 002 ev OnFireCallerIdArrived (hli=0x1e2d78) (122,,300)

090043.343 002 callstate=[GCST_CALLROUTING]

090043.343 002 gc GCEV_TASKFAIL status gc:68:[invalid parameter], cc_err=906 cclibid=2

090043.343 002 ResultInfo gcValue=137(0x89) gcMsg=[CCLIB specific] ccLibId=2 ccLibName=[GC_ISDN_LIB] ccValue=[0x11f|EGC_CCLIBSPECIFIC|cclib specific - a catchall] ccMsg=[bad message in service/feature provided] additionalinfo=

090043.343 not calling ResetLineDev

090043.343 002 ocxfn LineAnswer(lLineId=2, lParam=0, strParam=)

090043.343 gc_AcceptCall(33587203(0x2008003), 0, EV_ASYNC) ok

090043.359 002 eng gc_GetMetaEventEx returned. lEvtHandle=0, iDev=2, lEvtType=2052, pEvtData=0xe6b7168, lEvtDataLen=28

090043.359 002 ev metaevent: cclibid=0x2, crn=0x2008003, evtdatap=0xe6b7168, evtdev=0x2, evtlen=0x1c, evttype=0x804, extevtdatap=0x0, flags=0x1, linedev=0x2, magicno=0xbad012fb, rfu1=0x2, usrattr=0x1e2d78 (usrattr=hli)

090043.359 002 ev GCEV_ACCEPT

090043.390 002 eng gc_GetMetaEventEx returned. lEvtHandle=0, iDev=2, lEvtType=2086, pEvtData=0xe6b31c8, lEvtDataLen=28

090043.390 002 ev metaevent: cclibid=0x2, crn=0x2008003, evtdatap=0xe6b31c8, evtdev=0x2, evtlen=0x1c, evttype=0x826, extevtdatap=0x0, flags=0x1, linedev=0x2, magicno=0xbad012fb, rfu1=0x2, usrattr=0x1e2d78 (usrattr=hli)

090043.390 002 ev GCEV_DISCONNECTED

090043.390 002 gc GCST_DISCONNECTED status gc:68:[invalid parameter], cc_err=906 cclibid=2

090043.390 002 ResultInfo gcValue=1280(0x500) gcMsg=[Normal completion] ccLibId=2 ccLibName=[GC_ISDN_LIB] ccValue=[0x210|GCRV_NORMAL|normal completion ] ccMsg=[Normal clearing] additionalinfo=

090043.390 003 dx_stopch call in GCEV_DISCONNECTED

090043.390 003 dx_stopch 3 ok

090043.390 002 gc gc_DropCall(crn=33587203, GC_NORMAL_CLEARING) (on Disconnected event)

090043.390 002 gc gc_DropCall ok

[Guest huuphuc]

Dear sir

How to test with ISDIAG to see if ISDIAG can answer incoming calls?

ISDN protocol's Alcaltel: QSIG only.

Please help me.

[SupportTeam]

Please see: http://www.voiceguide.com/vghelp/source/ht...igisdnsetup.htm

 

The command given there will open the first port.

 

You can then place a call into the system that port.

 

Best to start the ISDN tracing before placing the call.

 

Try running: ISDIAG -? to get more help on it.

 

 

 

[Guest huuphuc]

Dear Sir.

How to configuration parameter for D/300PCI E1 Dialogic card? (Files: TSFFileName?, ISDNProtocol: Value ?, Misc:FirmwareFile ?, ParameterFile ?, TSFFileSupport ?, DisconnectTone ?,...)

Please help me. Thank you for your supports.

 

[SupportTeam]

The only parameter you need top set is the ISDNProtocol. Leave all other settings blank.

 

Have you set the ISDNProtocol parameter before?

 

In your case it needs to be set to "QTE" if the Dialogic card is to function in "User Side" mode, and set it to "QNT" if the Dialogic card is to function in "Network Side" mode.

 

The PBX is most likely functioning in "Network Side" mode, so the Dialogic card should be set in "User Side" mode.

 

Set "Country" to US.

[Guest huuphuc]

Dear Sir.

I used VoiceGuide v6, it's support files sound system .vox files (http://www.voiceguide.com/vghelp/source/html/soundfiles.htm) but I can not choice .vox file. Why?

please help me.

[SupportTeam]

Just type *.vox into the "Filename" text box, press Enter and the .vox files will be displayed.

 

Or just specify the fill path to the .vox file directly in the Module's property pages without using the "Select File" dialog.

 

Did you successfully configure the Dialogic card to receive calls? What settings did you use?

[Guest huuphuc]

Dear Sir

I do not successfully configure the Dialogic card to receive calls. It's worth a try.

[SupportTeam]

So have you decided to move to different card? D/300JCT?

[Guest huuphuc]

Dear Sir.

I don't have D/300JCT card.

D/300PCI E1 support ISDN protocol QSIC-BC (Basic call)?

Please help me.

[SupportTeam]

Yes. D/300PCI supports QSIG.

[Guest huuphuc]

Dear Sir.

Where is QSIC protocol choice? Please help me.

Thanks

[SupportTeam]

The documentation for the SR5.1.1 drivers that you are using should list the various protocols supported.

 

From memory I think it was QTU for QSIG protocol working in User Side mode, and QTN (or QNT?) for QSIG protocol working in Network Side mode.

 

We offer an remote installation service where we will configure the Dialogic card for you and install the and configure the VoiceGuide software. For more details about the installation service please contact sales@voiceguide.com directly.