Guest jjfama Report post Posted 11/23/2005 12:35 AM We are having problems when testing the IVRS with a T1 connection. We are connecting to a switch and when the application is running nothing is coming up on the remote switch and no change in status on the voiceguide status window. Then after awhile the link goes down as seen from the remote switch. Still no change in status can be seen from the VoiceGuide screens. This happens for both 5ESS and NI2 ISDN protocols. And when I close Voiceguide to restart the system. I get an application error with Error signature szAppName:VgMulti.exe szAppVer:6.0.02322 szModName: Unknown szModver:0.0.0.0 offset: 040a0ae5. We are using a Dialogic D/240JCT-T1 with System release 5.1.1 and SU85 on a Windows 2003 Server Standard Edition. Share this post Link to post
SupportTeam Report post Posted 11/23/2005 02:05 AM nothing is coming up on the remote switch Which LED's on the back of the card are light up? Can you receive calls on this system when using ISDIAG? If you cannot receive calls using ISDIAG then contact your Local Intel Dialogic supplier for assistance in configuring the card which you purchased from them. This happens for both 5ESS and NI2 ISDN protocols. And what is the protocol set on this T1 by the Telco? You should select the matching protocol in Dialogic's configuration. System release 5.1.1 and SU85 Have you installed Service Pack 1? Best to probably install Feature Pack 1 or just go for SR6.0 - pretty much all of the T1/E1 ISDN test systems we have here use either FP1 or 6.0. Share this post Link to post
Guest jjfama Report post Posted 11/23/2005 06:27 PM We got the green LED ON on the dialogic card. Yes we can receive calls using ISDIAG.exe this works fine. The dialogic card seems ok. We matchd ISDN protocols for both sides of the T1 link. 5ESS intially on both sides then we tried NI2 on both ends with the same results. Right now we're using ISDN NI2 on the T1. I tried SR 6.0 (NFS Not for Sale) version to see if that would solve my problem with the Dialogic Service not running on Windows 2003 Server and it did solve my problem. But our dialogic card vendor on the other hand said that we don't need SR6.0 and instead recommended we install System Release 5.1.1 with the update SU85 Dialogic Service up on a Windows 2003 Server. I already have the link stable by not using channel 24 for voice since it is used for the D-channel. But VoiceGuide still does not answer an incoming call as opposed to ISDIAG which has already been able to answer my test calls. I am using VoiceGuide 6.0.2322 Share this post Link to post
SupportTeam Report post Posted 11/23/2005 09:01 PM Sometimes on systems which use the 24th slot as and additional D channel you need to have all 23 lines opened in order for the other switch to start sending calls - which I assume that you've done already? (or are you using a 4 line evaluation version of VG?) Please place the attached file in c:\, then restart VG, then make a test call and then close VG. There will be an isdn trace file created. Please .zip up that file and post it here - this will let us see what messages are sent on the ISDN line between the Telco switch and the Dialogic card and why the calls aren't answered. I tried SR 6.0 (NFS Not for Sale) version to see if that would solve my problem with the Dialogic Service not running on Windows 2003 Server and it did solve my problem. ...using the latest drivers does often help. But our dialogic card vendor on the other hand said that we don't need SR6.0 and instead recommended we install System Release 5.1.1 with the update SU85 Dialogic Service up on a Windows 2003 Server. Did you install Service Pack 1? ktTelControl_TraceSelect.txt Share this post Link to post
Guest jjfama Report post Posted 11/23/2005 09:59 PM Yes we have the 23 channels up and we are using a 24 license version of VG. We did not install Service Pack 1 and I have confirmed with our dialogic vendor that installing SU85 is newer and does the required changes as service pack 1 or the feature pack 1. Installing SR 6.0 will set us back $700 dollars so he said that SR5.1.1 should get the job done without us having to shell out more cash. I've attached the log file as you requested. Thanks. isdn_trace_dtiB1_1123_135144.log Share this post Link to post
SupportTeam Report post Posted 11/24/2005 12:37 AM Trace shows that the Dialogic drivers are rejecting the incoming call without even alerting VoiceGuide of the fact that a call has arrived. The first thing to try would be to install SR5.1.1 and Service Pack 1 (without any Updates) and try calling in with those drivers installed. PROTOCOL TYPE : PRI NI2 TRACE START TIME (MM/DD/YYYY) : 11/24/2005, 8:51:44.984 Time Stamp : 11/24/2005, 8:52:14.264 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x20 0x0c Information Dest=0 CR=0x001a SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. 4: 1------- Extension Bit -00----- Transfer Mode ---10000 Info. Transfer Rate 5: 1------- Extension Bit -01----- Layer 1 Indent ---00010 User Info. Layer 1 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. 3.2: 1------- Extension Bit -00----- Coding Standard ---0---- Number Map ----0011 Channel/Map Element 4: 1------- Extension Bit -0000110 Channel Number/Slot Map 1: PROGRESS INDICATOR(0x1e) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0100 Location 4: 1------- Extension Bit -0000011 Progress Description 1: CALLING PARTY NUM(0x6c) 2: IE Length(0x02) 3: 0------- Extension Bit -000---- Type Of Number ----0000 Numbering Plan ID 3a: 1------- Extension Bit -10----- Presentation Indicator ---000-- Spare ------11 Screening Indicator Number Digit(s) 1: CALLED PARTY NUM(0x70) 2: IE Length(0x0b) 3: 1------- Extension Bit -010---- Type of Number ----0001 Numbering plan ID 8006910783 Number Digit(s) Time Stamp : 11/24/2005, 8:52:14.304 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x22 Receive Ready Time Stamp : 11/24/2005, 8:52:14.304 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x0c 0x22 Information Orig=1 CR=0x801a RELEASE COMPLETE(0x5a) 1: CAUSE(0x08) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0000 Location 4: 1------- Extension Bit -0101100 Cause Value 5: 0x18 Diagnostic Time Stamp : 11/24/2005, 8:52:14.304 RECEIVE Response=0 SAPI=0x00 TEI=0x00 0x01 0x0e Receive Ready Time Stamp : 11/24/2005, 8:52:14.344 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x22 0x0e Information Dest=0 CR=0x001b SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. 4: 1------- Extension Bit -00----- Transfer Mode ---10000 Info. Transfer Rate 5: 1------- Extension Bit -01----- Layer 1 Indent ---00010 User Info. Layer 1 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. 3.2: 1------- Extension Bit -00----- Coding Standard ---0---- Number Map ----0011 Channel/Map Element 4: 1------- Extension Bit -0000111 Channel Number/Slot Map 1: PROGRESS INDICATOR(0x1e) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0100 Location 4: 1------- Extension Bit -0000011 Progress Description 1: CALLING PARTY NUM(0x6c) 2: IE Length(0x02) 3: 0------- Extension Bit -000---- Type Of Number ----0000 Numbering Plan ID 3a: 1------- Extension Bit -10----- Presentation Indicator ---000-- Spare ------11 Screening Indicator Number Digit(s) 1: CALLED PARTY NUM(0x70) 2: IE Length(0x0b) 3: 1------- Extension Bit -010---- Type of Number ----0001 Numbering plan ID 8006910783 Number Digit(s) Time Stamp : 11/24/2005, 8:52:14.344 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x24 Receive Ready Time Stamp : 11/24/2005, 8:52:14.344 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x0e 0x24 Information Orig=1 CR=0x801b RELEASE COMPLETE(0x5a) 1: CAUSE(0x08) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0000 Location 4: 1------- Extension Bit -0101100 Cause Value 5: 0x18 Diagnostic Time Stamp : 11/24/2005, 8:52:14.344 RECEIVE Response=0 SAPI=0x00 TEI=0x00 0x01 0x10 Receive Ready Share this post Link to post
Guest jjfama Report post Posted 11/29/2005 02:09 AM I uninstalled the SR5.1.1 FP1 Service Release 85. Then uninstalled SR5.1.1. Then used the Intel® Dialogic® Clean-up Utility to make sure everything is uninstalled. I first installed SR5.1.1. Then I tried to start the service at this point but got an "Error Starting Dialogic Service". I then installed SR5.1.1 SP1. I tried to start the service but got the same error "Error Starting Dialogic Service". This was what prompted us to get in touch with our Dialogic card vendor erlier on. We were thinking that Windows 2003 server had an effect on the dialogic drivers. Our vendor responded by giving us instructions to use SR5.1.1 but update this using SR5.1.1 FP1 Service Release 85 (SU85). This solved the problem of not being able to start the dialogic service on a Windows 2003 server. Here is a summary of his instructions Please follow these directions to cleanup the old intel driver install and install the latest version fresh. Intel® Dialogic® Clean-up Utility http://resource.intel.com/telecom/support/.../su85/index.htm The cleanup utility is located under \cleanup\dlgc_rel_clean.bat Install SR 5.1.1 http://resource.intel.com/telecom/support/...innt/index.html Reboot Install SU78 http://resource.intel.com/telecom/support/.../su85/index.htm Reboot Run DCM What would you like me to try next? Share this post Link to post
SupportTeam Report post Posted 11/29/2005 07:34 AM If SR6.0 works for you then the quickest way of resolving this will be for you to just start using SR6.0 drivers. Share this post Link to post
Guest jjfama Report post Posted 11/29/2005 06:26 PM I want to make something clear. The problem with the dialogic service not starting on Windows 2003 server was solved by either using SR5.1.1 with SR5.1.1 FP1 Service Release 85 or using SR6.0 NFS. Your recommendation for me to install SR5.1.1 and SP1 put me back in square 1. Your new recommendation for me to install SR6.0 would definitely solve the dialogic service not starting problem but not necessarily solve my problem with regards to not being able to receive calls. The second problem of not being able to receive calls remains to be the problem at hand. Share this post Link to post
SupportTeam Report post Posted 11/30/2005 10:02 AM Was the trace provided beforehand (isdn_trace_dtiB1_1123_135144.log) made while SR6.0 was installed, or while SR5.1.1 + SR5.1.1 FP1 Service Release 85 (SU85) was installed? Can you please provide the trace capturing isdiag accepting an incoming call. (isdiag allows you to make this trace as one of it's options) Share this post Link to post
Guest jjfama Report post Posted 12/01/2005 01:49 AM The trace provided beforehand (isdn_trace_dtiB1_1123_135144.log) was made while SR5.1.1 + SR5.1.1 FP1 Service Release 85 (SU85) was installed. Good news. I installed SR6.0 Not For Sale version just to get the driver issues out of the way. I also did capture a number of logs for both ISDIAG and VoiceGuide. Here are files included in the zip and some remarks that may be useful for the test being conducted. You will see that ISDIAG was able to pick up the call while VoiceGuide was not. Thanks for all your help and patience. isd11waitcall_ch7.log - ISDIAG trace. Call made to ISDIAG with option 11 selected and waiting for a call on channel 7 the call was then answered by ISDIAG isdn_trace_dtiB1_1130_150844_isdvg_allcktbzmsg100.log - voiceguide trace with ISDIAG run in trace mode then VoiceGuide was run after. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" isdn_trace_dtiB1_1130_152422_vgisd_allcktbzmsg100.log - voiceguide trace with Voiceguide running then ISDIAG run in trace mode after voiceguide was run. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" isdn_trace_dtiB1_1130_153248_vg_allcktbzmsg100.log - voiceguide trace with only Voiceguide running. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" isdsimple.log - ISDIAG trace. Call made to ISDIAG with no options selected. The call was then answered by ISDIAG isdtsr_noapp_allcktbz100.log - ISDIAG trace. Call made to ISDIAG in trace mode with no IVR application started. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" isdvg_allcktbzmsg100.log - ISDIAG trace. Call made to ISDIAG in trace mode with VoiceGuide running. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" isd_anscallerdropok.log - ISDIAG trace. Call made to ISDIAG When called ISDIAG picks up then caller drops the call. isd_ansdropok.log - ISDIAG trace. Call made to ISDIAG When called ISDIAG picks up then ISDIAG drops the call. vgisd_allcktbzmsg100.log - ISDIAG trace. Call made to ISDIAG in trace mode with VoiceGuide running before ISDIAG. When called I get a recording saying "I'm sorry all circuits are busy please try again. Message 100" ISDN_Traces.zip Share this post Link to post
SupportTeam Report post Posted 12/02/2005 07:55 AM Can we get access to this machine via PCAnywhere? If yes then please provide connection details to support@voiceguide.com Share this post Link to post
Guest jjfama Report post Posted 12/02/2005 10:51 PM I'm sorry but we cannot give you access to the machine. It has already been set up in a production environment in a remote location with security settings in place. However if there is any information you need from us such as config files, logs as well as how the hardware and software are setup just let me know and I will provide them to you to expedite the solution this issue. Thanks. Share this post Link to post
SupportTeam Report post Posted 12/05/2005 03:36 AM We'll see if we can find some other test apps for you to try, Manwhile for reference, here is the trace of the successful call when ISDIAG is used (isd11waitcall_ch7.log) To get these traces from the .log file just use PRITRACE.EXE or ISDTRACE.EXE utilities from Dialogic. PROTOCOL TYPE : PRI NI2 TRACE START TIME (MM/DD/YYYY) : 12/1/2005, 8:55:6.93 Time Stamp : 12/1/2005, 8:55:16.653 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xae 0x8a Information Dest=0 CR=0x0056 SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. 4: 1------- Extension Bit -00----- Transfer Mode ---10000 Info. Transfer Rate 5: 1------- Extension Bit -01----- Layer 1 Indent ---00010 User Info. Layer 1 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. 3.2: 1------- Extension Bit -00----- Coding Standard ---0---- Number Map ----0011 Channel/Map Element 4: 1------- Extension Bit -0000111 Channel Number/Slot Map 1: PROGRESS INDICATOR(0x1e) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0100 Location 4: 1------- Extension Bit -0000011 Progress Description 1: CALLING PARTY NUM(0x6c) 2: IE Length(0x02) 3: 0------- Extension Bit -000---- Type Of Number ----0000 Numbering Plan ID 3a: 1------- Extension Bit -10----- Presentation Indicator ---000-- Spare ------11 Screening Indicator Number Digit(s) 1: CALLED PARTY NUM(0x70) 2: IE Length(0x0b) 3: 1------- Extension Bit -010---- Type of Number ----0001 Numbering plan ID 8006910783 Number Digit(s) Time Stamp : 12/1/2005, 8:55:16.653 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xb0 Receive Ready Time Stamp : 12/1/2005, 8:55:16.653 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x8a 0xb0 Information Orig=1 CR=0x8056 CALL PROCEEDING(0x02) 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. 3.2: 1------- Extension Bit -00----- Coding Standard ---0---- Number Map ----0011 Channel/Map Element 4: 1------- Extension Bit -0000111 Channel Number/Slot Map Time Stamp : 12/1/2005, 8:55:16.653 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x8c 0xb0 Information Orig=1 CR=0x8056 CALL CONNECT(0x07) Time Stamp : 12/1/2005, 8:55:16.653 RECEIVE Response=0 SAPI=0x00 TEI=0x00 0x01 0x8c Receive Ready Time Stamp : 12/1/2005, 8:55:16.653 RECEIVE Response=0 SAPI=0x00 TEI=0x00 0x01 0x8e Receive Ready Time Stamp : 12/1/2005, 8:55:16.653 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xb0 0x8e Information Dest=0 CR=0x0056 CALL CONNECT ACKNOWLEDGE(0x0f) Time Stamp : 12/1/2005, 8:55:16.693 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xb2 Receive Ready Time Stamp : 12/1/2005, 8:55:27.373 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xb2 0x8e Information Dest=0 CR=0x0056 CALL DISCONNECT(0x45) 1: CAUSE(0x08) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0000 Location 4: 1------- Extension Bit -0010000 Cause Value Time Stamp : 12/1/2005, 8:55:27.373 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xb4 Receive Ready Time Stamp : 12/1/2005, 8:55:27.373 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x8e 0xb4 Information Orig=1 CR=0x8056 RELEASE(0x4d) Share this post Link to post
SupportTeam Report post Posted 12/06/2005 08:06 AM Information about a 'Global Call' based test app which can be used to test incoming calls on ISDN line has been posted in this thread: http://voiceguide.com/forums/index.php?showtopic=3476 Share this post Link to post
