D.H. Report post Posted 07/25/2020 04:03 PM Hi Support, seems the caller_id was not captured in the VoiceGuide, as in the call log, the cid is empty. Also, try to use the $RV_CIDNUMBER / $RV_DNIS variable, but both are empty too. could you advise? Share this post Link to post
SupportTeam Report post Posted 07/25/2020 08:24 PM This system is using analog lines. Do you have any details on how CallerID or any other info is sent over the lines that you are using? On telephone company supplied analog telephone lines the CallerID is usually sent between 1st and 2nd Ring (if it is sent at all). So the call should be answered after the 2nd Ring if you want the system to be able to receive the CallerID (and it is sent). DNIS is not usually sent on telephone company supplied analog telephone lines. PBXs can send the CallerID and other information as "inband signaling". VoiceGuide supports inband signalling so you can configure that approach if it is enabled on the telephone lines that you are using. see: https://www.voiceguide.com/vghelp/source/html/inbandsignaling.htm Share this post Link to post
D.H. Report post Posted 07/26/2020 07:08 AM We have already set RingsBeforeAnswer to 3, and the Voiceguide do answer after the third ring, but still no caller ID. That telephone line has caller ID feature, and if we use other IVRS applications to answer call, we can get caller ID (the caller ID comes between the first and second ring). The telephone line is NOT a line from the PABX, but a telephone line connect to telephone plug directly from telco. Can you give us some standard script which you are using at your side, which can capture caller ID for us to try at our side? Share this post Link to post
SupportTeam Report post Posted 07/26/2020 07:39 AM If the CallerID is being sent on the line then you will be able to see it being detected and reported by the Dialogic card in both the ktTel and vgEngine traces, and then accessible using the $RV_CIDNUMBER variable. This is done automatically be default and no special script/setting is required to enable this. Please post VoiceGuide's ktTel and vgEngine traces that capture system startup and the incoming call and we will then be able to see what is happening on the system and advise. Share this post Link to post
D.H. Report post Posted 07/27/2020 12:39 PM HI Support, Please find the trace and ktTel file in attached from the problematic server. server cannot capture callerid.rar Share this post Link to post
SupportTeam Report post Posted 07/28/2020 12:36 AM Dialogic trace shows that the Dialogic card did not detect any CallerID data sent by the telephone company. Are you sure the phone company is sending the CallerID details on this line? We can see that you posted the exact same CallerID related question over 2 months ago here: https://www.voiceguide.com/forums/topic/13171-caller-id-not-captured/?tab=comments#comment-44413 Suggest you confirm whether CallerID data is actually sent on this line by attaching some external CallerID detector to that line. Also suggest asking phone company as to how they are sending the CallerID data. Dialogic D/4PCIUF supports the below CallerID data sending formats. You should confirm what formats the Dialogic card that you are using supports. Quote Analog Caller Identification Applicable standards: Telcordia TR-TSY-000030 Telcordia TR-TSY-000031 TAS T5 PSTN1 ACLIP: 1994 (Singapore) British Telecom SIN 242 (Issue 01)nt British Telecom SIN 227 (Issue 01) Japan NTT CLIP Modem standard Bell 202 or V.23, serial 1200 b/s (simplex FSK signaling) Receive sensitivity –48 dBm to –1 dBm Noise tolerance Minimum 18 dB SNR over 0 dBm to –48 dBm dynamic range for error-free performance Data formats Single Data Message (SDM) and Multiple Data Message (MDM) formats via API calls and commands Impedance 600 Ohm for D/PCIUF Matching complex impedance specified in TBR-21 for D/4PCIUF-EURO. Message formats ASCII or binary SDM, MDM message content From Dialogic trace: Quote 025 194821.816 6228 ncm [D/x1D-PCI][D/4PCI-U #0 in slot 2/0][GM016166] 278 194902.521 5764 1 1 ev TDX_CST (CST Event Received) 279 194902.521 5764 1 1 TDX_CST DE_RINGS data=0 ringcount=1 crn=10000001 (hli->voicedev=1) 280 194902.526 5764 1 1 GetCallerIdInfo_OnAnalogLines begin 281 194902.529 5764 1 1 CLIDINFO_CMPLT returned 282 194902.529 5764 1 1 CLIDINFO_CMPLT err [128]:[Caller ID info/sub-msg not available] 283 194902.531 5764 1 1 CLIDINFO_GENERAL err [128]:[Caller ID info/sub-msg not available] 284 194902.533 5764 1 1 CLIDINFO_CALLID err [128]:[Caller ID info/sub-msg not available] assign strCLIDINFO_CALLID: 285 194902.533 5764 1 1 setting strCLIDINFO_CALLID to NOTAVAILABLE 286 194902.535 5764 1 1 CLIDINFO_FRAMETYPE err [128]:[Caller ID info/sub-msg not available] 293 194902.535 5764 1 1 r Ring 1 299 194906.541 5764 1 1 ev TDX_CST (CST Event Received) 300 194906.541 5764 1 1 TDX_CST DE_RINGS data=0 ringcount=2 crn=10000001 (hli->voicedev=1) 301 194906.541 5764 1 1 GetCallerIdInfo_OnAnalogLines begin 302 194906.543 5764 1 1 CLIDINFO_CMPLT returned 303 194906.543 5764 1 1 CLIDINFO_CMPLT err [128]:[Caller ID info/sub-msg not available] 304 194906.544 5764 1 1 CLIDINFO_GENERAL err [128]:[Caller ID info/sub-msg not available] 305 194906.546 5764 1 1 CLIDINFO_CALLID err [128]:[Caller ID info/sub-msg not available] assign strCLIDINFO_CALLID: 306 194906.546 5764 1 1 setting strCLIDINFO_CALLID to NOTAVAILABLE 307 194906.548 5764 1 1 CLIDINFO_FRAMETYPE err [128]:[Caller ID info/sub-msg not available] 312 194906.548 5764 1 1 r Ring 2 318 194910.492 5764 1 1 ev TDX_CST (CST Event Received) 319 194910.492 5764 1 1 TDX_CST DE_RINGS data=0 ringcount=3 crn=10000001 (hli->voicedev=1) 320 194910.492 5764 1 1 GetCallerIdInfo_OnAnalogLines begin 321 194910.493 5764 1 1 CLIDINFO_CMPLT returned 322 194910.493 5764 1 1 CLIDINFO_CMPLT err [128]:[Caller ID info/sub-msg not available] 323 194910.495 5764 1 1 CLIDINFO_GENERAL err [128]:[Caller ID info/sub-msg not available] 324 194910.498 5764 1 1 CLIDINFO_CALLID err [128]:[Caller ID info/sub-msg not available] assign strCLIDINFO_CALLID: 325 194910.498 5764 1 1 setting strCLIDINFO_CALLID to NOTAVAILABLE 326 194910.500 5764 1 1 CLIDINFO_FRAMETYPE err [128]:[Caller ID info/sub-msg not available] 331 194910.500 5764 1 1 r Ring 3 333 194910.509 6228 1 1 fn AnswerCall 10000001 (sXMLOptions=[]) Share this post Link to post
D.H. Report post Posted 07/29/2020 10:41 AM Hi Support, However, the other server, which used similar model as the server cannot get callerid, can successfully capture the callerid. Attached is the log and trace of the good server, could you help to check if difference make the server cannot get the callerid? server can capture callerid.rar Share this post Link to post
SupportTeam Report post Posted 07/29/2020 07:47 PM If you have used the same telephone line on both systems then this suggests that the the card on the first system is just not able to detect/read the CallerID data. Quote 025 164229.451 6668 ncm [D/x1D-PCI][D/4PCI #0 in slot 2/0][FD067356] 264 164249.191 4340 1 1 ev TDX_CST (CST Event Received) 265 164249.191 4340 1 1 TDX_CST DE_RINGS data=1 ringcount=2 crn=10000001 (hli->voicedev=1) 266 164249.191 4340 1 1 GetCallerIdInfo_OnAnalogLines begin 267 164249.199 4340 1 1 CLIDINFO_CMPLT returned 268 164249.199 4340 1 1 CLIDINFO_CMPLT ok => [0726164251083293] 269 164249.207 4340 1 1 CLIDINFO_GENERAL ok => [07/26 16:42 51083293 O] 270 164249.212 4340 1 1 dlgc CLIDINFO_CALLID=[51083293] 271 164249.220 4340 1 1 CLIDINFO_FRAMETYPE ok => 0x4 272 164249.220 4340 caller id frame type: CLASSFRAME_SDM or ACLIPFRAME_SDM 274 164249.222 4340 1 1 Event_CallerId begin. name=, nbr=51083293, dnis= 275 164249.222 4340 1 1 r CallerId 279 164249.224 4340 1 1 r Ring 2 Share this post Link to post
D.H. Report post Posted 08/01/2020 11:23 AM HI Support, In the same environment, when we use another IVRS program it can get caller ID. And after such program has been started and stopped, Voiceguide can get caller ID too. But once after system reboot, Voiceguide cannot get caller ID, if the other IVRS program has not been started after a reboot. Therefore, reason why Voiceguide cannot get caller ID should be the Dialogic Broad has not been correctly initialized by Voiceguide, at least, for HK situation. Attached are parameters which the other IVRS program used for initialize the Dialogic card, could you check and compare with the parameters Voice guide use to initialize the board? Book1.xlsx Share this post Link to post
SupportTeam Report post Posted 08/01/2020 10:34 PM Quote And after such program has been started and stopped, VoiceGuide can get caller ID too. Can you describe this process in more detail. Is it this: Windows Restart Start other IVRS Make call(s) into other IVRS - multiple calls or just one call? Stop other IVRS Start VoiceGuide Make call(s) into other VoiceGuide. Is CallerID reported on first call only? or on all calls thereafter? Is it on one port only? or is each port able to detect/report CallerID? or is it something else? When does this ability for VoiceGuide to receive CallerID then stop? Or it does not stop until the Dialogic service is restarted? Please also post the vgEngine and ktTel traces from 'step 6' - when VoiceGuide is receiving the CallerID. What is the name of this other IVRS program? You can forward details direct to support@voiceguide.com, along with a link to this support forum thread. You can set any of these DXCH_ 'channel settings' in the ConfigLine.xml file, and VoiceGuide will issue those settings to the Dialogic card, so you can experiment with the different settings if you wish. (the DXCH_PLAYDRATE and DXCH_RECRDRATE should however be left at 8000, as otherwise the playing and recording may not work with your current sound files.) The ConfigLine.xml file is in VoiceGuide's \conf\ subdirectory. See the "<Parameters_DxCh>" section of that file. If you want different ports to use different ConfigLine.xml files, then you can specify a "<ConfigLine>" setting in the "<Channel>" entry of the Config.xml file. Like this: <Channel> <Device_Voice>dxxxB1C1</Device_Voice> <Device_Network>dxxxB1C1</Device_Network> <Protocol>pdk_na_an_io</Protocol> <RingsBeforeAnswer>2</RingsBeforeAnswer> <Script>C:\Program Files (x86)\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script> <ConfigLine>C:\my_directory\my_own_configline_file.xml</ConfigLine> <AllowDialOut>1</AllowDialOut> </Channel> Similarly, the DXBD_ 'board settings' for the Dialogic board can be specified in the Config.xml file. Share this post Link to post
SupportTeam Report post Posted 08/02/2020 12:05 AM Also, have you tried just plugging the lines from the good server (which uses the FD067356 card) into the problem server (GM016166 card) ? Share this post Link to post
D.H. Report post Posted 08/02/2020 02:41 PM HI Support, The flow is like below. And log and trace of step 6 attached. We found that the good server should actually the same, it was fine because it used the other IVRS program before. For the parameters, we try to put them to the "configline.xml" like you mentioned, for "DXBD" we tried to put into "<Parms>", "<Parameters>", "<Parameters_DXBD>" and "<Parameters_DxBd>", but still cannot get the callerid. Could you check and advise? Windows Restart Start other IVRS and initialize all ports Make call(s) into other IVRS - one call or multiple are both fine Stop other IVRS Start VoiceGuide Make call(s) into other VoiceGuide. after call for all port after can report the callerID log.rar Share this post Link to post
SupportTeam Report post Posted 08/02/2020 08:48 PM Pleas add the below entry into the ConfigLine's "<Parameters_DxCh>" section. Looks like this entry is missing from your current ConfigLine.xml Note that the Key to use is: "DXCH_CALLID", not: "DXCH_CALLERID". "DXCH_CALLERID" is not a valid Dialogic DXCH_ parameter name. <Parameter> <Description>Enable CallerID for the channel</Description> <Notes> 0 - Disable Caller ID 1 - Enable Caller ID </Notes> <Key>DXCH_CALLID</Key> <Value>1</Value> <Default>1</Default> </Parameter> Share this post Link to post
SupportTeam Report post Posted 08/02/2020 09:17 PM The above DXCH_CALLID entry is in the default ConfigLine.xml file installed on system when VoiceGuide is installed for Analog systems. Looking at your vgEngine trace we can see that your current ConfigLine.xml file only has an entry for one Disconnct tone, and only for DXCH_RECRDRATE and DXCH_PLAYDRATE parameters: 195 194827.023 6228 tone loaded from ConfigLine idx=0 DISCONNECT_USER_1:1000 620:200 480:200 30:10 20:10 3 196 194827.023 6228 tone loaded from ConfigLine idx=1 DISCONNECT_USER_2:1001 550:200 0:0 30:10 20:10 3 197 194827.023 6228 1 1 dx_setparm (1, DXCH_RECRDRATE, &[8000]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 198 194827.024 6228 1 1 dx_setparm (1, DXCH_RECRDRATE, &[8000]) => 0, ok 199 194827.024 6228 1 1 dx_setparm (1, DXCH_PLAYDRATE, &[8000]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 200 194827.026 6228 1 1 dx_setparm (1, DXCH_PLAYDRATE, &[8000]) => 0, ok The default ConfigLine.xml file for Analog systems is attached at bottom of this post. As you can see it has many other entries in it. Is it possible that you copied the ConfigLine.xml file that you are using right now from a VoIP based system? VoIP based system do not use the DXCH_CALLID setting (but the 'tone' definitions included in it are different to what you have) You can just run the VoiceGuide installer again (without uninstalling current install) and the default Config.xml and ConfigLine.xml will be installed on your system, but with ".defaultinstall" suffix. This will let you compare the ConfigLine.xml that would have been originally installed on an Analog systm with the ConfigLine.xml that you currently have. Note that at install time you need to select whether you are installing for a VoIP based system or for Analog or ISDN based system, See instructions below on how to install new version of VoiceGuide over the top of existing install: 1. Stop VoiceGuide Service. VoiceGuide Service can be stopped by clicking on the VoiceGuide Service Monitor in the Windows's Icon Tray on bottom right of the taskbar and selecting "Stop". 2. Exit all VoiceGuide programs. This includes the Service Monitor applet in the Icon Tray area in bottom right of the screen, as well as the Script Designer, Line Status Monitor, etc. 3. Run the VoiceGuide install and install into same directory as existing installation. (Do NOT uninstall the previous VoiceGuide installation). 4. Start VoiceGuide service. Note: Running a VoiceGuide install over the top of an existing install will NOT overwrite existing configuration or license files (Config.xml, ConfigLine.xml, VG.INI, etc) and will not remove any of users script or sound files, and will not remove any log files etc. ConfigLine.xml Share this post Link to post
SupportTeam Report post Posted 08/02/2020 09:28 PM The ktTel trace on Analog systems with default ConfigLine.xml will show this in trace for Channel settings (DXCH_ settings loaded from ConfigLine.xml): 157 195300.193 9156 1 1 fn ParamSet(1,ConfigLine_Filename,C:\Program Files (x86)\VoiceGuide\conf\ConfigLine.xml,0) 158 195300.194 9156 SetParam ConfigLine_Filename begin 159 195300.194 9156 1 1 tones not set by TSF File as EDX_SYSTEM [dxxxB1C1|dxxxB1C1] 160 195300.194 9156 1 1 config line as per [C:\Program Files (x86)\VoiceGuide\conf\ConfigLine.xml] iReadTonesConfigFromConfigLineXml=1 161 195300.194 9156 1 1 config line XML_ParserCreate 162 195300.194 9156 1 1 config line file load start len=11084 163 195300.197 9156 tone loaded from ConfigLine idx=0 DISCONNECT_USER_1:1000 620:200 480:200 30:10 20:10 3 164 195300.197 9156 tone loaded from ConfigLine idx=1 DISCONNECT_USER_2:1001 550:200 0:0 30:10 20:10 3 165 195300.197 9156 tone loaded from ConfigLine idx=2 FAX:1002 1100:110 0:0 30:15 0:0 0 166 195300.197 9156 tone loaded from ConfigLine idx=3 TID_BUSY1:253 500:200 0:0 55:40 55:40 4 167 195300.197 9156 tone loaded from ConfigLine idx=4 TID_BUSY2:255 500:200 525:175 55:40 55:40 4 168 195300.197 9156 tone loaded from ConfigLine idx=5 TID_DIAL_LCL:250 340:40 440:40 100:0 0:0 1 169 195300.197 9156 tone loaded from ConfigLine idx=6 TID_DIAL_INTL:251 340:40 440:40 100:0 0:0 1 170 195300.197 9156 tone loaded from ConfigLine idx=7 TID_DIAL_XTRA:252 340:40 440:40 100:0 0:0 1 171 195300.197 9156 tone loaded from ConfigLine idx=8 TID_DISCONNECT:257 500:200 525:175 55:40 55:40 4 172 195300.197 9156 tone loaded from ConfigLine idx=9 TID_FAX1:258 2150:50 0:0 25:25 0:0 1 173 195300.197 9156 tone loaded from ConfigLine idx=10 TID_FAX2:259 1100:50 0:0 25:25 0:0 1 174 195300.197 9156 tone loaded from ConfigLine idx=11 TID_RNGBK1:254 450:150 0:0 130:105 580:415 0 175 195300.197 9156 tone loaded from ConfigLine idx=12 TID_RNGBK2:256 450:150 450:150 130:105 580:415 0 176 195300.197 9156 commented out tone defintion encountered (path=[<Samples><Tone>]!=[<Tones><Tone>]) 177 195300.197 9156 commented out tone defintion encountered (path=[<Samples><Tone>]!=[<Tones><Tone>]) 178 195300.197 9156 1 1 dx_setparm (1, DXCH_CALLID, &[1]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 179 195300.199 9156 1 1 dx_setparm (1, DXCH_CALLID, &[1]) => 0, ok 180 195300.199 9156 1 1 dx_setparm (1, DXCH_DTMFDEB, &[0]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 181 195300.201 9156 1 1 dx_setparm (1, DXCH_DTMFDEB, &[0]) => 0, ok 182 195300.201 9156 1 1 dx_setparm (1, DXCH_DTMFTLK, &[5]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 183 195300.203 9156 1 1 dx_setparm (1, DXCH_DTMFTLK, &[5]) => 0, ok 184 195300.203 9156 1 1 dx_setparm (1, DXCH_MINRWINK, &[10]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 185 195300.204 9156 1 1 dx_setparm (1, DXCH_MINRWINK, &[10]) => 0, ok 186 195300.204 9156 1 1 dx_setparm (1, DXCH_PLAYDRATE, &[8000]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 187 195300.206 9156 1 1 dx_setparm (1, DXCH_PLAYDRATE, &[8000]) => 0, ok 188 195300.206 9156 1 1 dx_setparm (1, DXCH_RECRDRATE, &[8000]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 189 195300.209 9156 1 1 dx_setparm (1, DXCH_RECRDRATE, &[8000]) => 0, ok 190 195300.209 9156 1 1 dx_setparm (1, DXCH_RINGCNT, &[1]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 191 195300.209 9156 1 1 dx_setparm (1, DXCH_RINGCNT, &[1]) => 0, ok 192 195300.209 9156 1 1 dx_setparm (1, DXCH_T_IDD, &[5]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 193 195300.211 9156 1 1 dx_setparm (1, DXCH_T_IDD, &[5]) => 0, ok 194 195300.211 9156 1 1 dx_setparm (1, DXCH_TTDATA, &[10]) call , XmlPathBranch_Last2=[<Parameters_DxCh><Parameter>] 195 195300.213 9156 1 1 dx_setparm (1, DXCH_TTDATA, &[10]) => 0, ok 196 195300.213 9156 xml sCurrConfig_Rule_key=[SendDisconnectOnLoopCurrentDrop] 197 195300.213 9156 rule SendDisconnectOnLoopCurrentDrop = 0 198 195300.213 9156 xml sCurrConfig_Rule_key=[DialPrefix] 199 195300.213 9156 rule DialPrefix = 200 195300.213 9156 1 1 config line file load end And this for DXBD_ settings loaded from Config.xml 042 195255.039 9156 configxml board file [C:\Program Files (x86)\VoiceGuide\conf\Config.xml] 043 195255.039 9156 config board file load start (len=6947) 044 195255.039 9156 dx_setparm BOARD (1, DXBD_FLASHTM, &[20]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 045 195255.039 9156 dx_setparm BOARD (1, DXBD_FLASHTM, &[20]) => 0, 046 195255.039 9156 dx_setparm BOARD (1, DXBD_MINLCOFF, &[50]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 047 195255.039 9156 dx_setparm BOARD (1, DXBD_MINLCOFF, &[50]) => 0, 048 195255.039 9156 dx_setparm BOARD (1, DXBD_MINOFFHKTM, &[250]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 049 195255.039 9156 dx_setparm BOARD (1, DXBD_MINOFFHKTM, &[250]) => 0, 050 195255.039 9156 dx_setparm BOARD (1, DXBD_MINSLOFF, &[2]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 051 195255.039 9156 dx_setparm BOARD (1, DXBD_MINSLOFF, &[2]) => 0, 052 195255.039 9156 dx_setparm BOARD (1, DXBD_MINSLON, &[1]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 053 195255.039 9156 dx_setparm BOARD (1, DXBD_MINSLON, &[1]) => 0, 054 195255.039 9156 dx_setparm BOARD (1, DXBD_MINTIOFF, &[5]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 055 195255.039 9156 dx_setparm BOARD (1, DXBD_MINTIOFF, &[5]) => 0, 056 195255.039 9156 dx_setparm BOARD (1, DXBD_MINTION, &[5]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 057 195255.055 9156 dx_setparm BOARD (1, DXBD_MINTION, &[5]) => 0, 058 195255.055 9156 dx_setparm BOARD (1, DXBD_OFFHDLY, &[50]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 059 195255.055 9156 dx_setparm BOARD (1, DXBD_OFFHDLY, &[50]) => 0, 060 195255.055 9156 dx_setparm BOARD (1, DXBD_PAUSETM, &[100]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 061 195255.055 9156 dx_setparm BOARD (1, DXBD_PAUSETM, &[100]) => 0, 062 195255.055 9156 dx_setparm BOARD (1, DXBD_S_BNC, &[4]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 063 195255.055 9156 dx_setparm BOARD (1, DXBD_S_BNC, &[4]) => 0, 064 195255.055 9156 dx_setparm BOARD (1, DXBD_T_IDD, &[15]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 065 195255.055 9156 dx_setparm BOARD (1, DXBD_T_IDD, &[15]) => 0, 066 195255.055 9156 dx_setparm BOARD (1, DXBD_TTDATA, &[10]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 067 195255.055 9156 dx_setparm BOARD (1, DXBD_TTDATA, &[10]) => 0, 068 195255.055 9156 dx_setparm BOARD (1, DXBD_S_BNC, &[4]) call , XmlPathBranch_Last2=[<Parameters_DxBd><Parameter>] 069 195255.055 9156 dx_setparm BOARD (1, DXBD_S_BNC, &[4]) => 0, 070 195255.055 9156 config board file load end The ktTel log from your system is missing many of the above entries, suggesting that the Config.xml and ConfigLine.xml that are currently on your system are different then the default versions that are installed by VoiceGuide on Analog systems. Share this post Link to post
D.H. Report post Posted 08/06/2020 02:37 PM Hi Support, After deployed the default configure file you provided, the system can sometimes capture caller id, but sometimes does not work (even use same port and same caller number). Attached is the trace and log file, please help to check and advise solution. thanks. sometimes cannot capture callerid.rar Share this post Link to post
SupportTeam Report post Posted 08/06/2020 09:15 PM There seems to be some interference on this line. The Dialogic card keeps reporting hearing a "FAX" type tone on the line. This suggests something is causing noise on the line. Such noise may interfere with CallerID signalling, and might be audible during calls. You should check the telephone line quality and quality of connectors, and confirm that there are no other devices attached to this line, and that the line is not passing near any electrical equipment that could cause interference/noise on the line. From vgEngine trace: 004359.162 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004616.669 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004617.797 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004626.917 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004637.380 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004656.724 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004704.585 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004714.688 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, 004715.769 24 1 1 1 ev Dialogic 134,TDX_CST, crn=10000001, 1002,0,0,DE_TONEON,FAX, ... and so on for whole day. Share this post Link to post
D.H. Report post Posted 08/07/2020 01:38 PM Hi Support, The phone line has no other device attached and we did not hear any noise during the call. Actually, as explained previously, using other Dialogic application in same environment, NO such problem of caller ID detection. May be the 'tone definition' file Voiceguide put to the system is not suitable for HK and mistakenly treated some noise as fax, please advise where we can find the 'tone definition' file, then we can try to modify according to the parameters we have been using, which has no problem in detecting caller ID. Share this post Link to post
SupportTeam Report post Posted 08/07/2020 09:45 PM Tone definitions are in the ConfinLine.xml file. You can just remove the <Tone> ... </Tone> entries that you do not want included. Removing tone definitions will not affect CallerID detection. Now that the ConfigLine.xml for analog ports is used on this system the Dialogic card is configured to look for CallerID and report it when it is detected and read in. If this is not done reliably then the problem is usually caused by problems with the telephone line, or maybe the telephone company switch is just sometimes not sending this data. Share this post Link to post
