jlperezdiaz Report post Posted 11/05/2006 12:19 PM 1) Scenario: Simple ani screening such if Ani not included in database call is dropped. 2) Script properties: Start script not answering the call. Except if required (ie ani authorised). Problem: All calls with ani not authorised get dead air during some seconds instead to be dropped inmediately. Calls are connected, but it gets confussion to the calling parties not hearing anything during 10 seconds or so. Calls should be dropped inmediately after (not dead air) is being check ani is not authorised. Please see traces from voiceguide logs and isdn traces: Note: It appears to be Voiceguide app doesn´t send a disconnect isdn message. is this fair? Tracing from logs (Voiceguide app) 125223.89 2 tw DialogicEvent 2084,GCEV_OFFERED,2084,0,0,,, 125223.89 2 event GCEV_OFFERED, iCode=2084 state=0 125223.89 2 event callstate OFFERING 2 2,0,0 125223.89 2 script interpretor: VgMulti v6.0.3168 125223.89 2 fired OFFERING event to listeners 125223.89 2 cid CallerID vars set (in 'offering' event) [,,] 125223.89 2 call AnswerTheCallIfAllowed from LINECALLSTATE_OFFERING 125223.89 2 rings=0, min rings before answer=0 (iCallerIdHasArrived=0) 125223.89 2 tw lev_CallerID [918292341,,902007599], strWorkingModeScript=[] 125223.89 2 cid LastCidMessage values [918292341,,902007599] 125223.89 2 cid CallerID vars set (in levCallerId) [918292341,,902007599] 125223.89 2 dnis not defined in rv set 125223.89 2 adding dnis to rv set 125223.89 2 rings=0, min rings before answer=0 (iCallerIdHasArrived=1) 125223.89 2 should answer as sLineType=[dlgc digital] and CallerID has arrived 125223.89 2 rv clear all 125223.89 2 init LineState ResetAtStartOfNewCall. 125223.89 2 starting without answering the call (link pickup is not made) 125223.89 2 StartLoadedVgs at 11/5/2006 12:52:23 PM (VgMulti v6.0.3168) 125223.89 2 set LineState().iVgsIdx=1 125223.89 2 set sScriptToRunOnHangup=[] in StartLoadedVgs 125223.89 2 state [MVNO_IVR] Evaluate [$RV[DNIS]] 125223.89 2 eval[902007599] 125223.89 2 Eval Expr result:[902007599] 125223.89 2 next module is [Happy_Customer?] (idx=5) 125223.89 2 state [Happy_Customer?] DB Query 125223.91 2 db ODBC mode used name:[mvno] connect:[ODBC;DSN=mvno;UID=uprog;database=mvno;PWD=a037maintenance;srv=10.50.1.2 5] 125223.92 2 db About to execute a Retrieve type operation [select Riesgo_Limite from pv_msisdn where MSISDN = 918292341 ;] 125223.95 2 db [Happy_Customer?] movelast err : 125223.95 2 next module is [HangupCall] (idx=2) 125223.95 2 state [HangupCall] Hangup Call 125223.95 2 HangupCall start (Hangup Module) 125223.95 2 state Hanging up call... [Hangup Module] 125223.95 2 HangupCall_Common hCall=2 125223.95 2 HangupCall_Common Mode=BeforeAnswerRun 125248.98 2 tw DialogicEvent 2086,GCEV_DISCONNECTED,2086,0,0,GCRV_CCLIBSPECIFIC,event caused by cclib specific failure,Recovery on timer expire 125248.98 2 event GCEV_DISCONNECTED, iCode=2086 state=900 125248.98 2 LsAwaitingCalls EV_UNKNOWN_2086 125248.98 2 tw DialogicEvent 2053,GCEV_DROPCALL,2053,0,0,,, 125248.98 2 event GCEV_DROPCALL, iCode=2053 state=900 125248.98 2 LsAwaitingCalls EV_UNKNOWN_2053 125248.98 2 tw DialogicEvent 2137,GCEV_RELEASECALL,2137,0,0,,, 125248.98 2 event GCEV_RELEASECALL, iCode=2137 state=900 125248.98 2 LsAwaitingCalls EV_UNKNOWN_2137 125248.98 2 event callstate IDLE 2 1,0,0 125248.98 2 WorkingMode@Idle= 125248.98 2 on-hangup script:[] 125250.02 2 event EV_TIMEOUT_TIMETOREINITLINE, iCode=9008 state=900 125250.02 2 init atidle reinit : start 125250.02 2 init atidle reinit iConferenceOtherLegLid=-1 125250.02 2 init atidle reinit : reset all LineState variables 125250.02 2 state Waiting for a call... 125252.20 2 event EV_TIMEOUT_AFTERIDLE_ALLOWOUT, iCode=9013 state=900 ------------------------------------------------------------------------------------------------------------------------- Tracing from ISDN Trace Start Time : 11/5/2006, 13:2:53.656 PRI NET5 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0xad Receive Ready TIME STAMP: 11/5/2006, 13:2:53.656 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xdb Receive Ready TIME STAMP: 11/5/2006, 13:2:53.656 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xda 0xac Information Dest=0 CR=0x016c SETUP(0x05) 1: SENDING COMPLETE(0xa1) 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 ---00011 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 -0000010 Channel Number/Slot Map 1: CALLING PARTY NUM(0x6c) 2: IE Length(0x0b) 3: 0------- Extension Bit -010---- Type Of Number ----0001 Numbering Plan ID 3a: 1------- Extension Bit -00----- Presentation Indicator ---000-- Spare ------11 Screening Indicator 918292341 Number Digit(s) 1: CALLED PARTY NUM(0x70) 2: IE Length(0x0a) 3: 1------- Extension Bit -010---- Type of Number ----0001 Numbering plan ID 902007599 Number Digit(s) TIME STAMP: 11/5/2006, 13:2:54.616 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xdc Receive Ready TIME STAMP: 11/5/2006, 13:2:54.616 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0xac 0xdc Information Orig=1 CR=0x816c 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 -0000010 Channel Number/Slot Map TIME STAMP: 11/5/2006, 13:2:54.616 RECEIVE Response=0 SAPI=0x00 TEI=0x00 0x01 0xae Receive Ready TIME STAMP: 11/5/2006, 13:2:54.680 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0xaf Receive Ready TIME STAMP: 11/5/2006, 13:2:56.616 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xdd Receive Ready TIME STAMP: 11/5/2006, 13:2:56.616 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0xaf Receive Ready TIME STAMP: 11/5/2006, 13:2:58.624 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xdd Receive Ready TIME STAMP: 11/5/2006, 13:2:58.624 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xdc 0xae Information Dest=0 CR=0x016c CALL DISCONNECT(0x45) 1: CAUSE(0x08) 2: IE Length(0x03) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0000 Location 4: 1------- Extension Bit -1100110 Cause Value 5: 0x0a Diagnostic TIME STAMP: 11/5/2006, 13:2:59.624 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xde Receive Ready TIME STAMP: 11/5/2006, 13:2:59.624 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0xae 0xde Information Orig=1 CR=0x816c RELEASE(0x4d) 1: CAUSE(0x08) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---0---- Spare ----0000 Location 4: 1------- Extension Bit -1100110 Cause Value TIME STAMP: 11/5/2006, 13:2:59.624 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0xde 0xb0 Information Dest=0 CR=0x016c RELEASE COMPLETE(0x5a) 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: 11/5/2006, 13:2:59.624 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xe0 Receive Ready TIME STAMP: 11/5/2006, 13:2:59.624 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0xb1 Receive Ready TIME STAMP: 11/5/2006, 13:3:1.632 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0xe1 Receive Ready TIME STAMP: 11/5/2006, 13:3:1.632 Share this post Link to post
SupportTeam Report post Posted 11/05/2006 08:05 PM The script you have is just choosing not to answer the call - so caller should just keep hearing ringing all the time. Are you saying the caller does not hear ringing? If the caller does not hear ringing then you should probably be speaking with both the phone companies which provide the ISDN line and with the phone company which provides the line from which the call is made. What ISDN protocol is used on this system? Which Dialogic card and Dialogic SR drivers are used? Was the ISDN trace from a different call then the one captured by the VG trace? Share this post Link to post
jlperezdiaz Report post Posted 11/05/2006 11:51 PM The script you have is just choosing not to answer the call - so caller should just keep hearing ringing all the time. Are you saying the caller does not hear ringing? NO, BASICALLY THE SCENARIO IS IF THE ANI IS NOT REGISTERED, CALL MUST BE DROPPED INMEDIATELY. NO RING AT ALL. FROM APP WE CHECK ANI, IF NOT IN THE DATABASE, THEN WE REJECT THE CALL INMEDIATELY (SENDING A DISCONNECT I ASSUME). THE POINT IS: A) IT´S TRUE WE DON´T ANSWER THE CALL IT´S TRUE WE SEND THE CALL TO A "HANG CALL" MODULE. THE FACT IS WE GET DEAD AIR. AFTER SOME TIMEOUT, CALL IS BEING RELEASE AND WE GET TIPICALLY REORDER TONES. If the caller does not hear ringing then you should probably be speaking with both the phone companies which provide the ISDN line and with the phone company which provides the line from which the call is made. I DON´T THINK SO. WE GET A SETUP FROM THE COMPANY, AND BASICALLY IF WE DON´T WANT THE CALL, WE MUST SEND A DISCONNECT INMEDIATELY. ISN´T IT? What ISDN protocol is used on this system? EUROISDN. CRT4. Which Dialogic card and Dialogic SR drivers are used? IT´S A D300JCT. sr5.1.1 SERVICE PACK 1 Was the ISDN trace from a different call then the one captured by the VG trace? NO, IT´S THE SAME CALL. WHAT I´M UNDERSTAND IS BASICALLY SINCE THE CALL IS NOT BEING ANSWERED, WHEN THE CALL IS FORWARDEN TO A "HANG CALL" MODULE, WE DON´T SENT TO THE OPERATOR AN ISDN DISCONECT MESSAGE. COULD IT BE? THANKS IN ADVANCE FOR YOUR HELP. Share this post Link to post
SupportTeam Report post Posted 11/06/2006 12:31 AM The attached version of VG should result in a DISCONNECT ISDN message to be sent to Telco if VG chooses not to answer the call, so the caller will get a Disconnected tone being played to them (almost) immediately. In the version which you were using the "not answering of call" should have resulted in the caller just hearing a ringing for as long as the Telco call answer timeouts allow. Obviously this did not work as intended on the lines you're using. Please post a trace using the new version. Was the ISDN trace from a different call then the one captured by the VG trace? NO, IT´S THE SAME CALL. Looks like the time as used by the ISDN connection is very different to the time set on PC. According to PC call arrived at: 12:52:23.89 According to ISDN line trace call arrived at: 13:02:53.656 which is a difference of 10min and 30seconds. This does not cause any problems, just makes two traces harder to compare if a more complex traces were needed to be examined. VgMulti_6.0.3150.zip Share this post Link to post
