stetson Report post Posted 12/08/2006 08:59 AM It's for an IVR questionnaire. We absolutely need to know the called number when Voice Guide answers the call. So we are able to answer with the right introduction. I have searched inband signaling by testing dtmf or get number .... What can you know about Avaya IP Office -> a Dialogic card and Voice Guide . When ther is a caller ID, this caller ID is given with called nr. But when there is no caller ID, there is no called number ! Please help ! I need the solution When I call : xxxx xxx 01 I must have a different answer if I call xxx xxx 02 Thanks for your help Share this post Link to post
SupportTeam Report post Posted 12/08/2006 09:05 AM When ther is a caller ID, this caller ID is given with called nr.Are you saying that the Avaya is sending via Inband Signalling both the CallerID and the Dialed Number (DNIS) information when CallerID is available, But when there is no caller ID, there is no called number !but is not sending DNIS when CallerID is not available? You should probably contact your Avaya supplier and ask them why the Inband Siganlling information for other data is not sent when CallerID information is not available. Which model Avaya are you using, and what options/cards if any are installed on it? Can you post examples of what Inband Signalling data is the Avaya sending in the various cases? Share this post Link to post
stetson Report post Posted 12/08/2006 02:13 PM Thanks for your quick reply. Sincerely, I don't know if we have or not "inband signalling" out of the Avaya IP406, sinc I do not hear dtmf tones when doing as you say in the help manual. But ... I had a look on other topics in the forum, particularly a question of Gulano (8th November) wher he shows a logfile like this : 092834.20 6 rv lg add [$RV_STARTTIME]{11/8/2006 9:28:34 AM} 092834.20 6 rv lg add [$RV_DEVICEID]{6} 092834.20 6 rv lg add [$RV_CIDNAME]{} 092834.20 6 rv ns add [PathApp]{C:\Program Files\VoiceGuide\} 092834.20 6 rv lg add [$RV_CIDNUMBER]{} 092834.20 6 rv lg add [$RV_DNIS]{4582} 092834.22 6 rv lg add [DNIS]{4582} And I had a lok on my logfiles and my logfile doesn't have DNIS !!! it looks like this: 141251,23 1 init StartLoadedVgs_InitLineState start 141251,23 1 rv add [$RV_STARTTIME]{08/12/2006 14:12:51} 141251,23 1 rv add [$RV_DEVICEID]{1} 141251,23 1 rv add [$RV_CIDNAME]{0148889696>IVR_5594} 141251,23 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 141251,23 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\IVR_mobistar_bilingue\} 141251,23 1 rv add [$RV_CIDNUMBER]{0148889696} with a detected caller ID and likethis when caller ID is masked or unknown init StartLoadedVgs_InitLineState start 124031,05 1 rv add [$RV_STARTTIME]{08/12/2006 12:40:31} 124031,05 1 rv add [$RV_DEVICEID]{1} 124031,05 1 rv add [$RV_CIDNAME]{} 124031,05 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 124031,05 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\IVR_mobistar_bilingue\} 124031,05 1 rv add [$RV_CIDNUMBER]{} So you can see that the dial number or group (here is IVR_5594) is not present wher caller ID is absent. But the most important question is : How to obtain DNIS from Avaya IP Office 406 ??? Thanks for your help ! Jean-Paul DAYAN Share this post Link to post
SupportTeam Report post Posted 12/08/2006 08:43 PM You should ask your Avaya distributor how to enable the IP406 to still send DNIS in situations when the CallerID is masked or unknown... Share this post Link to post
stetson Report post Posted 12/12/2006 06:56 AM Ok, I understand ther is not "inband signalling". But I just discover that the information I'm looking for is not received in 1212vgm.txt : 074322,20 1 rv add [$RV_STARTTIME]{12/12/2006 07:43:22} 074322,20 1 rv add [$RV_DEVICEID]{1} 074322,20 1 rv add [$RV_CIDNAME]{} 074322,20 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 074322,20 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\IVR_mobistar_bilingue\} 074322,20 1 rv add [$RV_CIDNUMBER]{} but is received at the same time in 1212tw.txt: 074320.531 001 dlgc dx_gtextcallid(1, CLIDINFO_CMPLT, =>€12120743Ext>IVR5591) in CtEventProcess => 0 074320.546 001 dlgc dx_gtextcallid(1, CLIDINFO_GENERAL, =>12/12 07:43 Ext>IVR5591) in CtEventProcess => 0 074320.546 001 dx_gtextcallid(1,CLIDINFO_CALLID) error [128]:[Caller ID info/sub-msg not available] 074320.546 001 dlgc dx_gtextcallid(1, CLIDINFO_FRAMETYPE, => 0xffffff80) in CtEventProcess => 0 074320.546 dlgc caller id frame type: CLASSFRAME_MDM or CLIPFRAME_MDM or ACLIPFRAME_MDM 074320.546 001 dlgc dx_gtextcallid(1, MCLASS_DATETIME, =>12120743) in CtEventProcess => 0 074320.546 001 dlgc dx_gtextcallid(1, MCLASS_DN, =>) in CtEventProcess => -1 074320.546 001 dlgc dx_gtextcallid(1, MCLASS_DDN, =>) in CtEventProcess => -1 074320.546 001 dlgc dx_gtextcallid(1, MCLASS_ABSENCE1, =>) in CtEventProcess => -1 074320.546 001 dlgc dx_gtextcallid(1, MCLASS_REDIRECT, =>) in CtEventProcess => -1 074320.562 001 dlgc dx_gtextcallid(1, MCLASS_QUALIFIER, =>) in CtEventProcess => -1 074320.562 001 dlgc dx_gtextcallid(1, MCLASS_NAME, =>Ext>IVR5591) in CtEventProcess => 0 074320.562 001 dlgc dx_gtextcallid(1, MCLASS_ABSENCE2, =>) in CtEventProcess => -1 074320.562 001 dlgc dx_gtextcallid(1, CLIP_CALLTYPE, =>) in CtEventProcess => -1 074320.562 001 dlgc dx_gtextcallid(1, CLIP_NETMSG, =>) in CtEventProcess => -1 074320.562 001 in CLASSFRAME_MDM: _CMPLT=[€12120743Ext>IVR5591] _GENERAL=[12/12 07:43 Ext>IVR5591] _CALLID=[] datetime=[12120743] dn=[] ddn=[] name=[Ext>IVR5591] absence1=[] absence2=[] qualifier=[] redirect=[] calltype=[] netmsg=[] This is great ... if you help me to transfer and use this information (called group) in the voiceguide script for broadcasting the correct welcome message. Thanks for your help Jean-Paul Share this post Link to post
SupportTeam Report post Posted 12/12/2006 04:25 PM Could you please post the "tw" trace from this system showing both cases - when the call arrives and CallerID is supplied, and when call arrives and caller ID is masked or unknown. Share this post Link to post
stetson Report post Posted 12/12/2006 04:47 PM here are the tw trace for 2 calls : 1st one with caller ID masked or unknown, 2nd one with a supplied caller ID 1212tw.zip Share this post Link to post
SupportTeam Report post Posted 12/12/2006 11:36 PM The attached OCX should now allow you to receive the group information when the CallerID is masked/unknown. Place the OCX in Windows' System32 directory, overwriting existing file then restart VG and try a few calls. Please let us know how you go with it. ktTel_061213.zip Share this post Link to post
stetson Report post Posted 12/13/2006 08:54 AM That's great ! You are a magician ... ! Now I can see DNIS in vgm logfile when Caller ID is absent or masked 094211,66 1 init StartLoadedVgs_InitLineState start 094211,66 1 rv add [$RV_STARTTIME]{13/12/2006 09:42:11} 094211,66 1 rv add [$RV_DEVICEID]{1} 094211,66 1 rv add [$RV_CIDNAME]{Ext>IVR5594} 094211,66 1 rv add [$RV_DNIS]{Ext>IVR5594} 094211,66 1 rv add [DNIS]{Ext>IVR5594} 094211,66 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 094211,66 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\} 094211,66 1 rv add [$RV_CIDNUMBER]{} 094211,66 1 fn RunModule start [Play,[Play 1],1,,] 094211,66 1 tw DialogicEvent 134,TDX_CST,3324,0,0,DE_LCON,, and when the callerID is present, there is no change, I can receive the DNIS in CIDNAME: 094339,61 1 init StartLoadedVgs_InitLineState start 094339,61 1 rv add [$RV_STARTTIME]{13/12/2006 09:43:39} 094339,61 1 rv add [$RV_DEVICEID]{1} 094339,61 1 rv add [$RV_CIDNAME]{0148889696>IVR5591} 094339,61 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 094339,61 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\} 094339,61 1 rv add [$RV_CIDNUMBER]{0148889696} 094339,61 1 fn RunModule start [Play,[Play 1],1,,] 094339,61 1 tw DialogicEvent 134,TDX_CST,8500,0,0,DE_LCON,, except of course if you have a new version of this fabulous ocx which should give DNIS in any case - ! Thank you very much for your help, Now I know we can have multi-surveys IVR, so I'm going to order some more licenses for my IVR. Share this post Link to post
SupportTeam Report post Posted 12/13/2006 10:22 AM OK, thanks for letting us know it's working now. Let us know if there is anything we can help with in the future. Share this post Link to post
stetson Report post Posted 12/15/2006 09:37 AM Hi, Thanks again for your help, Before we close this topic and complete our IVR application using the new ocx version and the information on called number that we can get now, let me ask a last question: Thanks to your help we have now an ocx that gives 2 new fields $RV_DNIS and DNIS when the callerId is unavailable. And when the caller ID is available, we found the CalleDId in the CIDNAME field, since there is not DNIS field The question is: Would it be possible to get an ocx giving the fields "DNIS" and "$RV_DNIS" in any case (callerId available or not) so we can use it always. If not, it is not a problem since we can use the field CIDNAME which now always contains the Dnis info . Have a nice day and a pleasant end of year. Jean-Paul Share this post Link to post
SupportTeam Report post Posted 12/17/2006 11:04 PM Attached version of OCX will copy the contents of the Name field into the DNIS field if the DNIS field supplied from the PBX is empty (as is the case with the Avaya if CallerID is available - see the tw logs). ktTel_061218.zip Share this post Link to post
stetson Report post Posted 12/18/2006 07:49 AM It's great !! It's working fine and we can get now the DNIS info even if it is not given by Avaya IP Office and even if the callerid is masked ! Here are two examples with and without callerid: 082956,67 1 rv add [$RV_STARTTIME]{18/12/2006 08:29:56} 082956,67 1 rv add [$RV_DEVICEID]{1} 082956,67 1 rv add [$RV_CIDNAME]{0175439293>IVR5591} 082956,67 1 rv add [$RV_DNIS]{0175439293>IVR5591} 082956,67 1 rv add [DNIS]{0175439293>IVR5591} 082956,67 1 rv add [$RV_CIDNUMBER]{0175439293} 083334,45 1 rv add [$RV_STARTTIME]{18/12/2006 08:33:34} 083334,45 1 rv add [$RV_DEVICEID]{1} 083334,45 1 rv add [$RV_CIDNAME]{Ext>IVR5594} 083334,45 1 rv add [$RV_DNIS]{Ext>IVR5594} 083334,45 1 rv add [DNIS]{Ext>IVR5594} 083334,45 1 rv add [$RV_CIDNUMBER]{} Thanks very much for your help and congratulations for your very high level of products and assistance Regards Jean-Paul Share this post Link to post
stetson Report post Posted 01/05/2007 06:04 PM I would like to wish you an happy new year and many good things for you and your team and family. I'm still working on my IVR developpement with caller orientation along the called number. The specific kttel.ocx that you sent to me is a great magic wand and works in almost every case. But today I've just discovered a very strange case: We receive many calls from Belgium (caller ID is 0032xxx) and among these calls most of them are from gsm mobiles (00324xxxxxxx). - When the caller ID is received by Avaya IP office , no problem, it follows to Voice Guide with DNIS - When the caller ID is absent or masked, no problem, your magic kttel.ocx gives the DNIS to VoiceGuide. - But last case, one problem today : On many numbers received by Avaya IP Office (traced in avaya call logger) from ground lines in Belgium (for example 003250301800 this morning) nothing is given to Voiceguide : nor Callerid, nor DNIS ! and this was the case for some ten or twelve ground numbers from Belgium. From France, I could not make the problem, even with a gsm or with a ground line, masked or not, in any case I received the dnis. Do you have an idea on what should be the source of this problem ? Maybe a difference between some networks in Belgium using DTMFD or FSKD . (In France we use FSKD ) bu I don't know any more on this subject ! Thanks for your help Jean-Paul DAYAN Share this post Link to post
SupportTeam Report post Posted 01/05/2007 10:35 PM Could you please post the "tw" trace from this system showing both normal working and non-working call cases. We can then see what information is sent from the PBX. Share this post Link to post
stetson Report post Posted 01/05/2007 11:55 PM Yes, thanks for helping me Here are the three cases: The first two cases are good: Both habve the dnis, one without the CID, the other one with CID The third one is bad : Voiceguide does'nt receive nor CID nor DNIS, although the caller is well identified in the IP Office Avaya PABX : It is a ground line calling from Belgium, Bruxelles and the CID is visible : 003225386011 In attachement you will find the 3 extracts from tw trace: I put also the 3 vgm traces And the line in Avaya log which shows the number that is not transmitted to voiceguide : 2007/01/05 18:57:43,00:00:02,4,003225386011,I,5594,5594,,0,7978,0,E207,IVRn207,T9015,Line 1.15,0,0 (date, time, duration, 4, caller number, Inbound, DNIS, DNIS,,0,7978,0,Extension N°, Ext.name, ...) Hope this may help Really strange ! What should be the reason why a gsm number works and a fixed (ground line) number does'nt ... when all cases tested from France works perfectly ! Have a nice week-end Regards Jean-Paul DNIS_WITH_CID.txt DNIS_without_CID.txt NOTHING_RECEIVED.txt vgm_dnis_with_cid.txt vgm_dnis_wo_cid.txt vgm_nothing_received.txt Share this post Link to post
stetson Report post Posted 01/06/2007 12:07 AM ... and if this should be useful, here is the whole tw trace of the day ! Thanks again. jpd 0105tw.zip Share this post Link to post
SupportTeam Report post Posted 01/06/2007 01:20 AM 3rd trace shows that Dialogic has not received any CallerID information form the PBX: 185743.093 001 ev TDX_CST DE_RINGS data=0 ringcount=2 (hli=0x1beb10, hli->chdev=1, hli->linedev=1) 185743.093 001 CLIDINFO_CMPLT error [128]:[Caller ID info/sub-msg not available] 185743.093 001 CLIDINFO_GENERAL error [128]:[Caller ID info/sub-msg not available] 185743.109 001 CLIDINFO_CALLID error [128]:[Caller ID info/sub-msg not available] 185743.109 001 CLIDINFO_FRAMETYPE error [128]:[Caller ID info/sub-msg not available] This question should go back to the PBX Supplier as the PBX is not sending any data to the analog extension at all for his call. In the "No CID" case the information is still sent, it is just re-arranged in different fields, so we were able to just retrieve it from a different field. In this case nothing is sent at all... Traces 1 and 2 show what traces would look like if the PBX did send CallerID information before the second ring: with CID: 185225.218 004 ev TDX_CST DE_RINGS data=1 ringcount=2 (hli=0x1f9e98, hli->chdev=4, hli->linedev=4) 185225.218 004 dlgc CLIDINFO_CMPLT=>[€00105185200324951495180032495149518>IVR5594] 185225.218 004 dlgc CLIDINFO_GENERAL=[01/05 18:52 0032495149518 0032495149518>IVR5594] 185225.218 004 dlgc CLIDINFO_CALLID=[0032495149518] 185225.234 004 dlgc CLIDINFO_FRAMETYPE=[0x80] no CID: 185123.875 003 ev TDX_CST DE_RINGS data=1 ringcount=2 (hli=0x1e62c0, hli->chdev=3, hli->linedev=3) 185123.875 003 dlgc CLIDINFO_CMPLT=>[€01051851Ext>IVR5594] 185123.890 003 dlgc CLIDINFO_GENERAL=[01/05 18:51 Ext>IVR5594] 185123.890 003 CLIDINFO_CALLID error [128]:[Caller ID info/sub-msg not available] 185123.890 003 dlgc CLIDINFO_FRAMETYPE=[0x80] Trace 1 and 2 shows call coming in on Dialogic port 3 and 4, and Trace 1 shows call coming in on Dialogic port 1 - but I assume that all analog lines from the PBX are configured the same (?). Share this post Link to post
stetson Report post Posted 01/07/2007 11:00 PM Yes ... but ... something remains un-understandable ! For which reason, Avaya IP Office does'nt forward the signal when the call comes from a belgian landline, when it forwards a correct signal when the call comes from anywhere in France or from a gsm mobile in Belgium ? Here are two examples of this sunday evening: 1) A landline from Belgium +3227213990 Here is the trace in the PABX IP Office / Avaya 2007/01/07 21:05:46,00:00:02,4,003227213990,I,5594,5594,,0,8509,0,E207,IVRn207,T9002,Line 1.2,0,0 and here is the tw trace: no ID is received ! (we can read error [128] and caller id frame type: UNKNOWN ) 210543.437 001 ev TDX_CST (CST Event Received) 210543.437 001 ev TDX_CST DE_RINGS data=0 ringcount=2 (hli=0x1beb10, hli->chdev=1, hli->linedev=1) 210543.437 001 CLIDINFO_CMPLT error [128]:[Caller ID info/sub-msg not available] 210543.453 001 CLIDINFO_GENERAL error [128]:[Caller ID info/sub-msg not available] 210543.453 001 CLIDINFO_CALLID error [128]:[Caller ID info/sub-msg not available] 210543.453 001 CLIDINFO_FRAMETYPE error [128]:[Caller ID info/sub-msg not available] 210543.453 001 dlgc caller id frame type: UNKNOWN [0x00] 210543.453 001 pbx display not supported on this card 210543.453 001 pbx display not supported on this card 210543.453 001 te LINE_LINEDEVSTATE(1, 0x1, 0x2, 0x0, 0x2) (dwIdx=8849) 210543.453 001 ocxfn LineAnswer(lLineId=1, lParam=0, strParam=) 210543.453 pbx display (1) [1286]:[invalid device] 210543.453 pbx callid (1) [1286]:[invalid device] 210543.453 dx_sethook(1, DX_OFFHOOK, EV_ASYNC) ok 210543.453 001 ocxev DoFireDialogic(dwIdx=8850, 1, 134, [TDX_CST], 0, 0, 0, [DE_RINGS], [ET_RON], []) (dwIdx=8850) 210543.453 001 ocxev DoFireDialogic completed 210544.000 001 ev TDX_SETHOOK (SetHook Completed) 210544.000 setting call progress tones according to [C:\Program Files\VoiceGuide\data\ConfigLine.xml] 210544.000 001 dlgc dx_deltones(1) returned ok (DelTones_SetTones_InitCallProgress) 2) And the same person calling with a gsm +32475726731 3 minutes before in Avaya : 2007/01/07 21:02:41,00:02:49,3,0032475726731,I,5594,5594,,0,8508,0,E207,IVRn207,T9001,Line 1.1,0,0 and in tw 210237.640 001 ev TDX_CST (CST Event Received) 210237.640 001 ev TDX_CST DE_RINGS data=1 ringcount=2 (hli=0x1beb10, hli->chdev=1, hli->linedev=1) 210237.640 001 dlgc CLIDINFO_CMPLT=>[€001072102 00324757267310032475726731>IVR5594] 210237.656 001 dlgc CLIDINFO_GENERAL=[01/07 21:02 0032475726731 0032475726731>IVR5594] 210237.656 001 dlgc CLIDINFO_CALLID=[0032475726731] 210237.656 001 dlgc CLIDINFO_FRAMETYPE=[0x80] 210237.656 dlgc caller id frame type: CLASSFRAME_MDM or CLIPFRAME_MDM or ACLIPFRAME_MDM 210237.656 001 dlgc MCLASS_DATETIME=[01072102] => 0 210237.656 001 dlgc MCLASS_DN=[0032475726731] => 0 210237.656 001 dlgc MCLASS_DDN=[] => -1 210237.656 001 dlgc MCLASS_ABSENCE1=[] => -1 210237.656 001 dlgc MCLASS_REDIRECT=[] => -1 210237.671 001 dlgc MCLASS_QUALIFIER=[] => -1 210237.671 001 dlgc MCLASS_NAME=[0032475726731>IVR5594] => 0 210237.671 001 dlgc MCLASS_ABSENCE2=[] => -1 210237.671 001 dlgc CLIP_CALLTYPE=[] => -1 210237.671 001 dlgc CLIP_NETMSG=[] => -1 210237.671 001 in CLASSFRAME_MDM: _CMPLT=[€001072102 00324757267310032475726731>IVR5594] _GENERAL=[01/07 21:02 0032475726731 0032475726731>IVR5594] _CALLID=[0032475726731] datetime=[01072102] dn=[0032475726731] ddn=[] name=[0032475726731>IVR5594] absence1=[] absence2=[] qualifier=[] redirect=[] calltype=[] netmsg=[] 210237.671 001 strCallerID_DN trigger (CLASSFRAME_MDM) 210237.671 001 pbx display not supported on this card 210237.671 001 pbx display not supported on this card 210237.671 001 ev OnFireCallerIdArrived (hli=0x1beb10) (0032475726731,0032475726731>IVR5594,0032475726731>IVR5594) 210237.687 001 te LINE_LINEDEVSTATE(1, 0x1, 0x2, 0x0, 0x2) (dwIdx=8788) 210237.687 001 ocxfn LineAnswer(lLineId=1, lParam=0, strParam=) I think the problem comes from the format of the ID when calling from a landline in Belgium. The coding system may be different and Avaya can deal with but Dlg does not recognize it. What do you think about this hypothesis ? As I am going to conduct a survey in nine countries (USA, Canada, Venezuela, Germany, Italy, Spain, UK, France, Mexico), I'm very concerned to obtain DNIS whatever system is used. Do you have an idea on this subject. Can I found a parameter in my pabx allowing to change the codin of the ID ? Did you ever hear something on this matter ? Thanks for your help. Share this post Link to post
SupportTeam Report post Posted 01/07/2007 11:29 PM Traces show that Dialogic has not detected any CallerID being sent by the PBX. You should be able to re-confirm this by attaching an external CallerID detection device to the line - they you will be able to confirm whether the external CallerID detection device is/isn't detecting the CallerID in these cases. We expect that any external CallerID device will also show that no CallerID is sent by PBX, as we have never seen a case of Dialogic detecting sent CallerID information on some calls and not detecting sent CallerID information on others. Share this post Link to post
stetson Report post Posted 01/08/2007 01:15 AM OK, I think that obviously you are right, and I will try with another device to confirm there is not caller id sent by the pabx in this case. But my conviction is that the difference comes from the coding of signaling: from France (land and mobile) as from Belgium mobiles, signaling is FSKD from Belgium landlines it is DTMFD (tones) and when I set the parameter of the extension which goes to the DLG to "DTMFD" in place of FSKD (default) I receive, in any case, the caller ID by DTMF ... But I come back to my first problem !!! I receive caller ID, but not DNIS It seems difficult to obtain a good communication between Avaya and Dialogic in all the cases Another solution should be to obtain DNIS when parameter is set to DMFD: Here is an example of vgm trace in this case: 010057,73 1 tw dtmf 0 (1,48,48) 010057,73 1 event 0, iCode=48 state=900 010057,73 1 LsAwaitingCalls 0 010057,88 1 tw dtmf 1 (1,49,49) 010057,88 1 event 1, iCode=49 state=900 010057,88 1 LsAwaitingCalls 1 010058,02 1 tw dtmf 7 (1,55,55) 010058,02 1 event 7, iCode=55 state=900 010058,02 1 LsAwaitingCalls 7 010058,14 1 tw dtmf 5 (1,53,53) 010058,14 1 event 5, iCode=53 state=900 010058,14 1 LsAwaitingCalls 5 010058,28 1 tw dtmf 4 (1,52,52) 010058,28 1 event 4, iCode=52 state=900 010058,28 1 LsAwaitingCalls 4 010058,44 1 tw dtmf 3 (1,51,51) 010058,44 1 event 3, iCode=51 state=900 010058,44 1 LsAwaitingCalls 3 010058,56 1 tw dtmf 9 (1,57,57) 010058,56 1 event 9, iCode=57 state=900 010058,56 1 LsAwaitingCalls 9 010058,70 1 tw dtmf 2 (1,50,50) 010058,70 1 event 2, iCode=50 state=900 010058,70 1 LsAwaitingCalls 2 010058,86 1 tw dtmf 9 (1,57,57) 010058,86 1 event 9, iCode=57 state=900 010058,86 1 LsAwaitingCalls 9 010058,98 1 tw dtmf 3 (1,51,51) 010058,98 1 event 3, iCode=51 state=900 010058,98 1 LsAwaitingCalls 3 010059,13 1 tw dtmf c (1,99,99) 010059,13 1 event c, iCode=99 state=900 010059,13 1 LsAwaitingCalls c 010059,72 1 timer fired EV_TIMEOUT_AFTERIDLE_ALLOWOUT 010059,72 1 event EV_TIMEOUT_AFTERIDLE_ALLOWOUT, iCode=9013 state=900 010059,72 1 setting iDialoutReadyToDialout=1 010059,92 1 event callstate OFFERING 1 2,0,0 010059,92 1 script interpretor: VgMulti v6.0.3179 010059,92 1 fired OFFERING event to listeners 010059,92 1 set LineState().hCall = 1 in LINECALLSTATE_OFFERING 010059,92 1 cid CallerID vars set (in 'offering' event) [0175439293,,] 010059,92 1 call AnswerTheCallIfAllowed from LINECALLSTATE_OFFERING 010059,92 1 rings=0, min rings before answer=2 (iCallerIdHasArrived=1) 010059,92 1 tw ring 1 010059,92 1 ring time since last ring event (sec): 0,00 010059,92 1 rings=1, min rings before answer=2 (iCallerIdHasArrived=1) 010059,92 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_RINGS,ET_RON, 010059,92 1 event TDX_CST, iCode=134 state=900 010059,92 1 LsAwaitingCalls EV_UNKNOWN_134 010104,95 1 tw ring 2 010104,95 1 ring time since last ring event (sec): 5,03 010104,95 1 rings=2, min rings before answer=2 (iCallerIdHasArrived=1) 010104,95 1 should answer as number of rings reached 010104,95 1 rv clear all 010104,95 1 init LineState ResetAtStartOfNewCall. 010104,95 1 answering the call (0175439293,,,1) 010104,95 1 timer clear 010104,97 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_RINGS,ET_RON, 010104,97 1 event TDX_CST, iCode=134 state=6001 010104,97 1 LsModuleTransition : 134, [TDX_CST] 010105,59 1 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_INBOUND, 010105,59 1 event TDX_SETHOOK, iCode=135 state=6001 010105,59 1 LsModuleTransition : 135, [TDX_SETHOOK] 010105,59 1 event callstate CONNECTED 1 256,0,0 010105,59 1 LineEvCallState_Connected hDevice=1 params=256,0,0 010105,59 1 WorkingModes tapi= script= LineState().iState=6001 010105,59 1 Inband detection not enabled 010105,59 1 StartLoadedVgs at 08/01/2007 01:01:05 (VgMulti v6.0.3179) 010105,59 1 set LineState().iVgsIdx=1 010105,59 1 set sScriptToRunOnHangup=[] in StartLoadedVgs 010105,59 1 init StartLoadedVgs_InitLineState start 010105,59 1 rv add [$RV_STARTTIME]{08/01/2007 01:01:05} 010105,59 1 rv add [$RV_DEVICEID]{1} 010105,59 1 rv add [$RV_CIDNAME]{} 010105,59 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\} 010105,59 1 rvns add [scriptsPath]{C:\Program Files\VoiceGuide\Scripts\IVR_mobistar_bilingue\} 010105,59 1 rv add [$RV_CIDNUMBER]{0175439293} At the same time, the tw trace is : 010057.609 001 ev TDX_CST (CST Event Received) 010057.609 001 ev TDX_CST DE_DIGITS data=100 [d], iSetSpeedVolKeyControls_IsUsed=0 010057.609 001 te LINE_MONITORDIGITS(1, 0x1, 100|d, 100|d) (dwIdx=8944) 010057.609 001 ocxfn RingsBeforeAnswer(lLineId=1, lRings=2, lParam1=0, strParam2=) 010057.734 001 ev TDX_CST (CST Event Received) 010057.734 001 ev TDX_CST DE_DIGITS data=48 [0], iSetSpeedVolKeyControls_IsUsed=0 010057.734 001 te LINE_MONITORDIGITS(1, 0x1, 48|0, 48|0) (dwIdx=8945) 010057.875 001 ev TDX_CST (CST Event Received) 010057.875 001 ev TDX_CST DE_DIGITS data=49 [1], iSetSpeedVolKeyControls_IsUsed=0 010057.875 001 te LINE_MONITORDIGITS(1, 0x1, 49|1, 49|1) (dwIdx=8946) 010058.015 001 ev TDX_CST (CST Event Received) 010058.015 001 ev TDX_CST DE_DIGITS data=55 [7], iSetSpeedVolKeyControls_IsUsed=0 010058.015 001 te LINE_MONITORDIGITS(1, 0x1, 55|7, 55|7) (dwIdx=8947) 010058.140 001 ev TDX_CST (CST Event Received) 010058.140 001 ev TDX_CST DE_DIGITS data=53 [5], iSetSpeedVolKeyControls_IsUsed=0 010058.140 001 te LINE_MONITORDIGITS(1, 0x1, 53|5, 53|5) (dwIdx=8948) 010058.281 001 ev TDX_CST (CST Event Received) 010058.281 001 ev TDX_CST DE_DIGITS data=52 [4], iSetSpeedVolKeyControls_IsUsed=0 010058.281 001 te LINE_MONITORDIGITS(1, 0x1, 52|4, 52|4) (dwIdx=8949) 010058.437 001 ev TDX_CST (CST Event Received) 010058.437 001 ev TDX_CST DE_DIGITS data=51 [3], iSetSpeedVolKeyControls_IsUsed=0 010058.437 001 te LINE_MONITORDIGITS(1, 0x1, 51|3, 51|3) (dwIdx=8950) 010058.562 001 ev TDX_CST (CST Event Received) 010058.562 001 ev TDX_CST DE_DIGITS data=57 [9], iSetSpeedVolKeyControls_IsUsed=0 010058.562 001 te LINE_MONITORDIGITS(1, 0x1, 57|9, 57|9) (dwIdx=8951) 010058.703 001 ev TDX_CST (CST Event Received) 010058.703 001 ev TDX_CST DE_DIGITS data=50 [2], iSetSpeedVolKeyControls_IsUsed=0 010058.703 001 te LINE_MONITORDIGITS(1, 0x1, 50|2, 50|2) (dwIdx=8952) 010058.859 001 ev TDX_CST (CST Event Received) 010058.859 001 ev TDX_CST DE_DIGITS data=57 [9], iSetSpeedVolKeyControls_IsUsed=0 010058.859 001 te LINE_MONITORDIGITS(1, 0x1, 57|9, 57|9) (dwIdx=8953) 010058.984 001 ev TDX_CST (CST Event Received) 010058.984 001 ev TDX_CST DE_DIGITS data=51 [3], iSetSpeedVolKeyControls_IsUsed=0 010058.984 001 te LINE_MONITORDIGITS(1, 0x1, 51|3, 51|3) (dwIdx=8954) 010059.125 001 ev TDX_CST (CST Event Received) 010059.125 001 ev TDX_CST DE_DIGITS data=99 [c], iSetSpeedVolKeyControls_IsUsed=0 010059.125 001 te LINE_MONITORDIGITS(1, 0x1, 99|c, 99|c) (dwIdx=8955) 010059.921 001 ev TDX_CST (CST Event Received) 010059.921 001 ev TDX_CST DE_RINGS data=0 ringcount=1 (hli=0x1beb10, hli->chdev=1, hli->linedev=1) 010059.921 001 CLIDINFO_CMPLT error [128]:[Caller ID info/sub-msg not available] 010059.921 001 CLIDINFO_GENERAL error [128]:[Caller ID info/sub-msg not available] 010059.921 001 CLIDINFO_CALLID error [128]:[Caller ID info/sub-msg not available] 010059.921 001 CLIDINFO_FRAMETYPE error [128]:[Caller ID info/sub-msg not available] 010059.921 001 dlgc caller id frame type: UNKNOWN [0x00] 010059.921 001 pbx display not supported on this card 010059.921 001 pbx display not supported on this card 010059.921 001 info ktTel v2.3.8, Dec 18 2006 10:00:28 010059.921 001 te LINE_CALLSTATE(1, 0x1, 0x2, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_OFFERING 010059.921 001 te LINE_LINEDEVSTATE(1, 0x1, 0x2, 0x0, 0x1) (dwIdx=8957) 010059.921 001 ocxev DoFireDialogic(dwIdx=8958, 1, 134, [TDX_CST], 0, 0, 0, [DE_RINGS], [ET_RON], []) (dwIdx=8958) 010059.921 001 ocxev DoFireDialogic completed 010104.953 001 ev TDX_CST (CST Event Received) 010104.953 001 ev TDX_CST DE_RINGS data=0 ringcount=2 (hli=0x1beb10, hli->chdev=1, hli->linedev=1) 010104.953 001 CLIDINFO_CMPLT error [128]:[Caller ID info/sub-msg not available] 010104.953 001 CLIDINFO_GENERAL error [128]:[Caller ID info/sub-msg not available] 010104.953 001 CLIDINFO_CALLID error [128]:[Caller ID info/sub-msg not available] 010104.953 001 CLIDINFO_FRAMETYPE error [128]:[Caller ID info/sub-msg not available] 010104.953 001 dlgc caller id frame type: UNKNOWN [0x00] 010104.953 001 pbx display not supported on this card 010104.953 001 pbx display not supported on this card 010104.953 001 te LINE_LINEDEVSTATE(1, 0x1, 0x2, 0x0, 0x2) (dwIdx=8959) 010104.953 001 ocxfn LineAnswer(lLineId=1, lParam=0, strParam=) 010104.968 pbx display (1) [1286]:[invalid device] 010104.968 pbx callid (1) [1286]:[invalid device] 010104.968 dx_sethook(1, DX_OFFHOOK, EV_ASYNC) ok 010104.968 001 ocxev DoFireDialogic(dwIdx=8960, 1, 134, [TDX_CST], 0, 0, 0, [DE_RINGS], [ET_RON], []) (dwIdx=8960) 010104.968 001 ocxev DoFireDialogic completed 010105.500 001 ev TDX_SETHOOK (SetHook Completed) 010105.500 setting call progress tones according to [C:\Program Files\VoiceGuide\data\ConfigLine.xml] 010105.515 001 dlgc dx_deltones(1) returned ok (DelTones_SetTones_InitCallProgress) 010105.515 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[0] 010105.515 tone an id:FAX:191, f1:1100:110, cad:30:15:0:0, count:0 010105.515 tone description save hli=0x1beb10, iToneUserID[0]=191 sToneUserName[0]=[FAX] 010105.515 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[1] 010105.515 tone an id:DISCONNECT_TAPI1 192 f1:620:200, f2:480:200, cad:30:10:20:10, count:3 010105.531 tone description save hli=0x1beb10, iToneUserID[1]=192 sToneUserName[1]=[DISCONNECT_TAPI1] 010105.531 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[2] 010105.531 tone an id:DISCONNECT_TAPI2:193, f1:550:200, cad:30:10:20:10, count:3 010105.546 tone description save hli=0x1beb10, iToneUserID[2]=193 sToneUserName[2]=[DISCONNECT_TAPI2] 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[3] 010105.546 tone an id:DISCONNECT_Telstra:194, f1:425:50, cad:37:5:37:5, count:2 010105.546 tone description save hli=0x1beb10, iToneUserID[3]=194 sToneUserName[3]=[DISCONNECT_Telstra] 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[59] 010105.546 tone ch id:TID_DIAL_LCL:250, f1:340:40, f2:440:40, cad:100:0,0:0, count:1 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[60] 010105.546 tone ch id:TID_DIAL_INTL:251, f1:340:40, f2:440:40, cad:100:0,0:0, count:1 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[61] 010105.546 tone ch id:TID_DIAL_XTRA:252, f1:340:40, f2:440:40, cad:100:0,0:0, count:1 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[62] 010105.546 tone ch id:TID_BUSY1:253, f1:500:200, f2:0:0, cad:55:40,55:40, count:4 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[63] 010105.546 tone ch id:TID_RNGBK1:254, f1:438:138, f2:0:0, cad:130:105,400:200, count:1 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[64] 010105.546 tone ch id:TID_BUSY2:255, f1:500:200, f2:525:175, cad:55:40,55:40, count:4 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[65] 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[66] 010105.546 tone ch id:TID_DISCONNECT:257, f1:500:200, f2:525:175, cad:55:40,55:40, count:4 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[67] 010105.546 tone ch id:TID_FAX1:258, f1:2150:50, f2:0:0, cad:25:25,0:0, count:1 010105.546 001 zTonesFromConfigLine tone entry found iTonesFromConfigLine_ArrIdx=[68] 010105.546 tone ch id:TID_FAX2:259, f1:1100:50, f2:0:0, cad:25:25,0:0, count:1 010105.593 001 cp_init(1) returned ok (DelTones_SetTones_InitCallProgress) 010105.593 001 ocxev DoFireDialogic(dwIdx=8961, 1, 135, [TDX_SETHOOK], 0, 0, 0, [DX_OFFHOOK], [CALL_INBOUND], []) (dwIdx=8961) 010105.593 001 ocxev DoFireDialogic completed 010105.593 001 te LINE_CALLSTATE(1, 0x1, 0x100, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_CONNECTED 010105.593 001 ev TDX_CST (CST Event Received) 010105.593 001 ev TDX_CST DE_LCON data=7420 010105.609 001 ocxev DoFireDialogic(dwIdx=8963, 1, 134, [TDX_CST], 7420, 0, 0, [DE_LCON], [], []) (dwIdx=8963) 010105.609 001 ocxev DoFireDialogic completed 010105.609 001 ocxfn RecStop(hLine=1, lRecId=0, lParam1=0, lParam2=0, strParam1=, strParam2=) 010105.609 001 dx_stopch call in RecStop 010105.609 001 dx_stopch 1 ok 010105.609 001 ocxfn PlayStop(hLine=1, lPlayId=0(0x0), lParam1=0, lParam2=0, strParam1=, strParam2=) 010105.609 001 dx_stopch call in PlayStop 010105.609 001 dx_stopch 1 ok 010105.609 001 ocxfn LineDrop(sLineId=1, sOpt=0) 010105.609 001 dx_sethook(1) call 010105.609 001 dx_sethook 1 DX_ONHOOK ok Share this post Link to post
SupportTeam Report post Posted 01/08/2007 02:36 AM But my conviction is that the difference comes from the coding of signaling: from France (land and mobile) as from Belgium mobiles, signaling is FSKD from Belgium landlines it is DTMFD (tones) Are you saying that the Avaya is sending the CallerID information differently depending on where the call is coming from? Have you spoken to the PBX supplier about this? What was their response/comment? Share this post Link to post
stetson Report post Posted 01/08/2007 07:38 AM Are you saying that the Avaya is sending the CallerID information differently depending on where the call is coming from? What I think is that Avaya PBX transmits the CID info like it receives it. If it receives it in FSKD mode, it transmits it in FSKD mode, and when in DTMFD ... in DTMFD. And this is a fact that CID mode is not the same in France and in Nederland ... Belgium is somewhere in the middle depending of the network. Effectively, I'm going to search for somebody able to discuss this topic at Avaya's. But the support in France at my PBX supplier is not very efficient ! I'll try to discuss in Avaya forums ... For the moment, I'm testing if it is possible to force pbx to always send FSKD, even if it receives DTMFD Share this post Link to post
SupportTeam Report post Posted 01/08/2007 09:22 PM What I think is that Avaya PBX transmits the CID info like it receives it. If it receives it in FSKD mode, it transmits it in FSKD mode, and when in DTMFD ... in DTMFD.You really need to speak with Avaya or your PBX supplier about this. Are the calls from different locations arriving on the same phone lines into the PBX? It is unlikely that the telephone company which is delivering these calls is using different CallerID encoding from call to call... (you can confirm that with the phone company). Share this post Link to post
stetson Report post Posted 01/09/2007 01:56 AM I know that this might be incredible. But there is something with Dialogic which made possible to discover this very amazing situation. My PBX receives approx. 300 calls from Belgium each day. 20% are from landlines (Belgacom) and 80% from mobile GSM lines (Mobistar, subsidiary of Orange). For two years we have used every day for 10 interviewers the Avaya application called "Phone Manager". And Phone Manager receives caller ID and DNIS with no difference between landlines and GSM. With Dialogic, it's the first time that I understand that the signal is not the same. Because Dialogic does not report the CID to VoiceGuide when the call comes from a Belgian land line ! And this is not because Dialogic does not receive from Avaya, it is because Dialogic receives DTMF and not FSK signalling ! It is clearly written in the IP Office help books that Begium and France have not the same coding standard. France, like USA, Australia and most countries in the world are FSKD. UK is UK20 and Belgium and Nederland are DTMFD. When I put the parameter to "DTMFD calls" in my PBX, Dialogic receives the CID information (from any line, France and Belgium) by DTMF tones, but in this case I can't get the DNIS and I believe that, in this mode DNIS info is not sent. So I will have no solution ... except if you have another magic wand (kttel.ocx) to extract DNIS info from DTMF tones ... At this time I prefer to go to sleep (it is 3 a.m. in Paris). Thanks for your help and very sorry if my problem is difficult to trust. Thanks to you, I have learnt many things I did'nt understand before. Best regards Jean-Paul Share this post Link to post
SupportTeam Report post Posted 01/09/2007 03:07 AM Are the calls from different locations arriving on the same phone lines into the PBX? Have you asked the phone company which supplies the lines and delivers the calls to thei PBX in which format they supply the CallerID/DNIS data? It is clearly written in the IP Office help books that Begium and France have not the same coding standard. France, like USA, Australia and most countries in the world are FSKD. UK is UK20 and Belgium and Nederland are DTMFD.This refers to standardized way in which telephone companies in those countries deliver the CallerID info. To have the Avaya send CallerID info in different way depending on source of call is very strange. As mentioned before, you should speak to Avaya or your PBX Supplier to find out how to setup this PBX so that it delivers CallerID information in consistent manner, regardless of where the call originated from. The DTMF tones sent in the trace example provided were "0175439293". I assume this represents the CallerID number? To receive DNIS information the PBX would need to send this DNIS information to the Dialogic card, and looks like the PBX is not sending this information in the example provided. I think the "Phone Manager" you are referring to is software running on a computer which has a direct link to the Avaya PBX. So it does not get call details from the information which is sent by the Avaya on the phone line, but has a propriety over-the-computer-network type connection to Avaya. Share this post Link to post
stetson Report post Posted 01/09/2007 09:11 AM You are perfectly right ! And I agree with you. Phone Manager is a proprietary application of Avaya which is located "inside" the pbx. So no need to send anything ! And, as you do, I can see that IP Office doesn't send DNIS when sending DTMF. So again lots of thanks for all your help. I have to look for a solution by discussing with Avaya whose support is not at the same level as you ! But I do not know elsewhere such a support ! Bravo et merci ! Share this post Link to post