Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Create a new article
365
Views
0
Helpful
0
Comments

leg proceeding on h323 leg

cdnadmin
Level 11
Level 11

on ‎01-24-2014 02:26 PM


Subject: RE: leg proceeding on h323 leg
Replied by: Yaw-Ming Chen on 18-07-2011 07:12:45 PM
To be more accurate, we may want to check leg_state before doing leg proceeding, connect ...etc please see the blog for detail.
But this may not the cause of what you saw. Is it possible you can post the section of the script and debug of

debug voip app script
debug voip app tclcommands
debug voip app callsetup
debug voip ccapi inout


leg state check:

Leg State
The state of the call leg and the corresponding status code is reported in lg_xxx format:
Value for xxx Call Leg
000 LEG_INIT
001 LEG_INCOMING_FIRST
001 LEG_INCINIT
002 LEG_INCACKED
003 LEG_INCPROCEED
004 LEG_ALERTING
005 LEG_INCCONNECTED
006 LEG_INCDISCONNECTING
006 LEG_INCOMING_LAST
007 LEG_OUTGOING_FIRST
007 LEG_OUTINIT
008 LEG_OUTPROCEED
009 LEG_OUTRINGING
010 LEG_OUTCONNECTED
011 LEG_OUTDISCONNECTING
011 LEG_OUTGOING_LAST
012 LEG_DISCONNECTED

      if {$legState != "lg_005" && $legState != "lg_008"} {
          if {$legState == "lg_001"} {
              puts "\n>>>>>>>>>legstate = lg_001<<<<<<<<<<<\n"
              leg setupack leg_incoming
              leg proceeding leg_incoming
              leg connect leg_incoming
          } elseif {$legState == "lg_002"} {
               puts "\n>>>>>>>>>legstate = lg_002<<<<<<<<<<<\n"
              leg proceeding leg_incoming
              leg connect leg_incoming
          } else {
               puts "\n>>>>>>>>>legstate = $legState<<<<<<<<<<<\n"
               leg connect leg_incoming
          }
      }
This document was generated from CDN thread

Created by: Patrick Schuettert on 18-07-2011 11:53:43 AM
Second try without MS Word formatting :-)
 
Hello everbody,

i have a little problem with an tcl/ivr script.
I want to send an an ¿proceeding¿ on an incoming h323 call leg.
For this i used the command ¿leg proceeding $legID¿  to send an proceeding to the specified leg.
When I enable debug h225 q931 and initiate a call their is no proceeding send to the Leg.
But when i write the script without ¿leg proceeding $legID¿ and initiate a ¿leg setup $dest callinfo $legID¿. I can see a ¿proceeding¿ in the debugging. It looks like it is auto-generated.

I use the command in the following environment:
 
IPPhone <-------> CUCM <------->CUCME <--------> IPPhone
              (SCCP)               (H323)               (SCCP)

-The call is initiate by a phone on the CUCM
-The script is on an inbound DialPeer on the CUCME
-With and without the Script i can establish connection between IPPhone on CUCM and an IPPhone on the CUCME
     -The only problem is the proceeding message (I need it)
 
 
 
Has anyone an idea that solves the problem?
 
Regards from Germany

Subject: RE: leg proceeding on h323 leg
Replied by: Patrick Schuettert on 29-07-2011 08:42:53 PM
Thanks Yaw-Ming Chen


Excuses my late answer.

I tried much but i can't find a reason for my problem. When I use "leg proceeding $myInLegID" no proceeding is send (see h225 q931 debug), but when the "leg setup $dest callinfo $myInLegID" is executed an proceeding is send.

Notice: This is not the real script, it's only a simple script that shows my problem.

Notice: I Used the timer to get a time slot. So it's easier to see what happen when the "leg proceeding $myInLegID" and the "leg setup $dest callinfo $myInLegID" is executed.

Notice: I will use the script on an incoming Dial-Peer for ISDN and H323 connections. So it is not possible for me to use the "leg setupack" command, because an ISDN Call is connected with this commnad and I don't want the ISDN Call connected at this part of the script.

Here is the script:


proc act_setup { } {
global myInLegID
global dest
set myInLegID [infotag get leg_incoming]   
set dest [infotag get leg_dnis $myInLegID]
puts [infotag get leg_state $myInLegID]

leg proceeding $myInLegID
timer start named_timer 3 test

}

proc act_timerHandling { } {
global myInLegID
global dest
puts "---------------------Know in act_timerHandling"
puts [infotag get leg_state $myInLegID]
leg setup $dest callinfo $myInLegID
}


proc act_Cleanup { } {
call close
}



set FSM(CALLINIT,ev_setup_indication) "act_setup,GETDEST"
set FSM(any_state,ev_named_timer) "act_timerHandling,same_state"
set FSM(any_state,ev_disconnected) "act_Cleanup,same_state"

fsm define FSM CALLINIT


Thanks

Subject: RE: leg proceeding on h323 leg
Replied by: Patrick Schuettert on 29-07-2011 08:44:05 PM
debug h225 q931

  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x0075
Message Type           : 0x05: SETUP
Bearer Capability: Length Of IE=3
Data 8090A2
Calling Party Number: Length Of IE=6
Data 008138323031
Called Party Number: Length Of IE=4
Data 80313231
User-User: Length Of IE=192
Data
patrick_CME(config-app-param)#0520B0060008914A0005020180B534401F0038003200300031000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000022C0B50000120F436973636F43616C6C4D616E61676572003100010100454080D53E21A04B31E375007E01C0A8819600D50D800007000A81201406B8110080D53E21A04B31E375007E01C0A88196010001000100010010A00100140140B50000120D82040020040001030003000103
patrick_CME(config-app-param)#


-----------------



time slot of timer


-----------------



  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x8075
Message Type           : 0x02: CALL_PROC
User-User: Length Of IE=51
Data 052180060008914A00042800B500001240013C050100044300110080D53E21A04B31E375007E01C0A881960100010010800100
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x8075
Message Type           : 0x01: ALERTING
Display: Length Of IE=16
Data 44722E204B6C61757320476965726B65
Signal: Length Of IE=1
Data 01
User-User: Length Of IE=51
Data 052380060008914A00042800B500001240013C05010006C300110080D53E21A04B31E375007E01C0A881960100010010800100
patrick_CME(config-app-param)#
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x8075
Message Type           : 0x6E: NOTIFY
Notification Ind: Length Of IE=1
Data F1
Display: Length Of IE=16
Data 44722E204B6C61757320476965726B65
Connected Number: Length Of IE=5
Data 0000313231
User-User: Length Of IE=33
Data 0528501900060008914A00040080D53E21A04B31E375007E01C0A8819610800100
patrick_CME(config-app-param)#
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x0075
Message Type           : 0x5A: RELEASE_COMP
Cause: Length Of IE=2
Data 8090
User-User: Length Of IE=34
Data 052580060008914A00051100110080D53E21A04B31E375007E01C0A8819610800100
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x8075
Message Type           : 0x5A: RELEASE_COMP
Cause: Length Of IE=2
Data 8090
User-User: Length Of IE=34
Data 052580060008914A00041100110080D53E21A04B31E375007E01C0A8819610800100

Subject: RE: leg proceeding on h323 leg
Replied by: Patrick Schuettert on 29-07-2011 08:44:50 PM
debug voip appl ccapi inout

Jul 30 00:16:12.240: //-1/80735A207900/CCAPI/cc_api_display_ie_subfields:
   cc_api_call_setup_ind_common:
   cisco-username=8201
   ----- ccCallInfo IE subfields -----
   cisco-ani=8201
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=1
   dest=121
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=-1
   cisco-rdnplan=-1
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Jul 30 00:16:12.240: //-1/80735A207900/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x872E66F0, Call Info(
   Calling Number=8201,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
   Called Number=121(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
   Incoming Dial-peer=4, Progress Indication=NULL(0), Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=123
Jul 30 00:16:12.240: //-1/80735A207900/CCAPI/ccCheckClipClir:
   In: Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
Jul 30 00:16:12.240: //-1/80735A207900/CCAPI/ccCheckClipClir:
   Out: Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
Jul 30 00:16:12.240: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:12.240: :cc_get_feature_vsa malloc success
Jul 30 00:16:12.240: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:12.240:  cc_get_feature_vsa count is 1
Jul 30 00:16:12.240: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:12.240: :FEATURE_VSA attributes are: feature_name:0,feature_time:2249777040,feature_id:15
Jul 30 00:16:12.240: //123/80735A207900/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
   Called Number=121(TON=Unknown, NPI=Unknown))
Jul 30 00:16:12.240: //123/80735A207900/CCAPI/cc_process_call_setup_ind:
   Event=0x87E2D2E0
Jul 30 00:16:12.244: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
   Try with the demoted called number 121
Jul 30 00:16:12.244: //123/80735A207900/CCAPI/ccCallSetContext:
   Context=0x89748A0C
Jul 30 00:16:12.244: //123/80735A207900/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 123 with tag 4 to app "_ManagedAppProcess_simplec"
Jul 30 00:16:12.244: //123/80735A207900/CCAPI/ccCallProceeding:

patrick_CME#Progress Indication=NULL(0)
patrick_CME#
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccCallSetupRequest:
   Destination=, Calling IE Present=TRUE, Mode=0,
   Outgoing Dial-peer=20004, Params=0x89749E04, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccCheckClipClir:
   In: Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccCheckClipClir:
   Out: Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccCallSetupRequest:
   Destination Pattern=121$, Called Number=121, Digit Strip=TRUE
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccCallSetupRequest:
   Calling Number=8201(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
   Called Number=121(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=
   Account Number=8201, Final Destination Flag=TRUE,
   Guid=80735A20-4C4D-31E3-7900-8201C0A88196, Outgoing Dial-peer=20004
Jul 30 00:16:15.244: //123/80735A207900/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=8201
   ----- ccCallInfo IE subfields -----
   cisco-ani=8201
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=1
   dest=121
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=-1
   cisco-rdnplan=-1
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Jul 30 00:16:15.244: //123/80735A207900/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x892A0EBC, Interface Type=6, Destination=, Mode=0x0,
   Call Params(Calling Number=8201,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
   Called Number=121(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=20004, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Jul 30 00:16:15.248: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:15.248: :cc_get_feature_vsa malloc success
Jul 30 00:16:15.248: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:15.248:  cc_get_feature_vsa count is 2
Jul 30 00:16:15.248: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jul 30 00:16:15.248: :FEATURE_VSA attributes are: feature_name:0,feature_time:2249776816,feature_id:16
Jul 30 00:16:15.248: //124/80735A207900/CCAPI/ccIFCallSetupRequestPrivate:
   SPI Call Setup Request Is Success; Interface Type=6, FlowMode=1
Jul 30 00:16:15.248: //124/80735A207900/CCAPI/ccCallSetContext:
   Context=0x89749DB4
Jul 30 00:16:15.248: //123/80735A207900/CCAPI/ccSaveDialpeerTag:
   Outgoing Dial-peer=20004
Jul 30 00:16:15.252: //124/80735A207900/CCAPI/cc_api_update_call_info:
   Interface=0x892A0EBC, Call Id=0x7C
Jul 30 00:16:15.252: //124/80735A207900/CCAPI/cc_api_call_proceeding:
   Interface=0x892A0EBC, Progress Indication=NULL(0)
Jul 30 00:16:15.256: //124/80735A207900/CCAPI/cc_api_call_alert:
   Interface=0x892A0EBC, Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Jul 30 00:16:15.256: //124/80735A207900/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
Jul 30 00:16:15.256: //123/80735A207900/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Jul 30 00:16:15.260: //123/80735A207900/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
patrick_CME#
Jul 30 00:16:15.260: //124/80735A207900/CCAPI/cc_api_get_called_ccm_detected:
   CallInfo(ccm detected=0)
Jul 30 00:16:15.260: //124/80735A207900/CCAPI/ccCallFeature:
   Feature Type=25, Call Id=124
Jul 30 00:16:15.260: //123/80735A207900/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=123
Jul 30 00:16:15.260: //124/80735A207900/CCAPI/cc_api_get_called_ccm_detected:
   CallInfo(ccm detected=0)
Jul 30 00:16:15.260: //123/80735A207900/CCAPI/cc_api_get_delay_xport:
   CallInfo(delay xport=FALSE)
patrick_CME#
Jul 30 00:16:20.400: //123/80735A207900/CCAPI/cc_api_call_disconnected:
   Cause Value=16, Interface=0x872E66F0, Call Id=123
Jul 30 00:16:20.400: //123/80735A207900/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)
Jul 30 00:16:20.400: //124/80735A207900/CCAPI/ccCallDisconnect:
   Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
Jul 30 00:16:20.400: //124/80735A207900/CCAPI/ccCallDisconnect:
   Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)
Jul 30 00:16:20.400: //124/80735A207900/CCAPI/cc_api_get_transfer_info:
   Transfer Number Is Null
Jul 30 00:16:20.404: //123/80735A207900/CCAPI/ccCallDisconnect:
   Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=16)
Jul 30 00:16:20.404: //123/80735A207900/CCAPI/ccCallDisconnect:
   Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)
Jul 30 00:16:20.404: //123/80735A207900/CCAPI/cc_api_get_transfer_info:
   Transfer Number Is Null
Jul 30 00:16:20.408: //124/80735A207900/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x892A0EBC, Tag=0x0, Call Id=124,
   Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)
Jul 30 00:16:20.408: //124/80735A207900/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
Jul 30 00:16:20.408: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Jul 30 00:16:20.408: :cc_free_feature_vsa freeing 8618DEA8
Jul 30 00:16:20.408: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Jul 30 00:16:20.408:  vsacount in free is 1
Jul 30 00:16:20.412: //123/80735A207900/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x872E66F0, Tag=0x0, Call Id=123,
   Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)
Jul 30 00:16:20.412: //123/80735A207900/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
Jul 30 00:16:20.412: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

patrick_CME#
Jul 30 00:16:20.412: :cc_free_feature_vsa freeing 8618DF88
Jul 30 00:16:20.412: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Jul 30 00:16:20.412:  vsacount in free is 0

Subject: RE: leg proceeding on h323 leg
Replied by: Patrick Schuettert on 29-07-2011 08:45:35 PM
debug voip appl tclcommands
debug voip appl script

Jul 30 00:19:47.217: //147//TCL :/tcl_InfotagObjCmd:  infotag get leg_incoming
Jul 30 00:19:47.221: //147//TCL :/tcl_InfotagGetObjCmd: infotag get leg_incoming
Jul 30 00:19:47.221: //147//AFW_:/vtr_lg_incoming: argc 2
Jul 30 00:19:47.221: //147//TCL :/tcl_InfotagObjCmd:  infotag get leg_dnis 147
Jul 30 00:19:47.221: //147//TCL :/tcl_InfotagGetObjCmd: infotag get leg_dnis 147
Jul 30 00:19:47.221: //147//AFW_:/vtr_lg_dnis: argc 3 argindex 2
Jul 30 00:19:47.221: //147//TCL :/tcl_InfotagObjCmd:  infotag get leg_state 147
Jul 30 00:19:47.221: //147//TCL :/tcl_InfotagGetObjCmd: infotag get leg_state 147
Jul 30 00:19:47.221: //147//Tcl :/tcl_parseCallID_vartagObj:
patrick_CME#VARTAG Translation Leg Count=1
Jul 30 00:19:47.221: //147//TCL :/tcl_PutsObjCmd: lg_001
Jul 30 00:19:47.221:
Jul 30 00:19:47.221: //147//TCL :/tcl_LegObjCmd:  leg proceeding 147
Jul 30 00:19:47.221: //147//TCL :/tcl_LegProceedObjCmd: proceeding 147
Jul 30 00:19:47.221: //147//Tcl :/tcl_parseCallID_vartagObj: VARTAG Translation Leg Count=1
Jul 30 00:19:47.221: //147//TCL :/tcl_TimerObjCmd:  timer start named_timer 3 test
Jul 30 00:19:47.221: //147//TCL :/tcl_TimerStartObjCmd: timer start named_timer 3 test
patrick_CME#
Jul 30 00:19:50.221: //147//TCL :/tcl_PutsObjCmd: ---------------------Know in act_timerHandling
Jul 30 00:19:50.221:
Jul 30 00:19:50.221: //147//TCL :/tcl_InfotagObjCmd:  infotag get leg_state 147
Jul 30 00:19:50.221: //147//TCL :/tcl_InfotagGetObjCmd: infotag get leg_state 147
Jul 30 00:19:50.221: //147//Tcl :/tcl_parseCallID_vartagObj: VARTAG Translation Leg Count=1
Jul 30 00:19:50.221: //147//TCL :/tcl_PutsObjCmd: lg_003
Jul 30 00:19:50.221:
Jul 30 00:19:50.221: //147//TCL :/tcl_LegObjCmd:  leg setup 121 callinfo 147
Jul 30 00:19:50.221: //147//Tcl :/tcl_parseCallID_vartagObj: VARTAG Translation Leg Count=1
patrick_CME#
Jul 30 00:19:56.405: //147//TCL :/tcl_CallObjCmd:  call close
Jul 30 00:19:56.405: //147//TCL :/tcl_CallCloseObjCmd:  close

Subject: RE: leg proceeding on h323 leg
Replied by: Patrick Schuettert on 29-07-2011 08:46:27 PM
debug voip appl callsetup

Jul 30 00:20:40.867: //149//CSPK:/tcl_LegSetupObjCmd: leg setup 121 callinfo 149
Jul 30 00:20:40.867: //149//CSPK:/C_CallSetup_Start: ControlInfo = 0x8957381C, callInfo = 0x897342E4, destination[0]=121
Jul 30 00:20:40.867: //149//CSPK:/C_CallSetup_Start: configured mode=rotary (1)
Jul 30 00:20:40.867: //149//CSPK:/C_CallSetup_Start: configured reroutemode=rotary (1)
Jul 30 00:20:40.867: //-1//Call:/AFW_CallSetup_New:
Jul 30 00:20:40.867: //149//Call:/AFW_CallSetup_AddDest:  121 index 0
Jul 30 00:20:40.867: //149//Call:/AFW_CallSetup_SetIntWrkLeg:
Jul 30 00:20:40.867: //149//Call:/AFW_M_CallSetup_Initiate:
Jul 30 00:20:40.867: //149//Call:/CS_UpdateMLPPInfo: ServiceDomain:[none (0)]  DomainIdentifier:[000000]  PrecedenceLevel:[-1 (PRECEDENCE_LEVEL_NONE)]  NormalizedPrecedence:[0 (INTERNAL_PRECEDENCE_0)]  Preempt Hunt Not Set
Jul 30 00:20:40.867: //149//Call:/CallSetupInitiate:
Jul 30 00:20:40.867: //149//Call:/CS_Placecall:
Jul 30 00:20:40.867: //149//Call:/CS_UpdateMLPPInfo: ServiceDomain:[none (0)]  DomainIdentifier:[000000]  PrecedenceLevel:[-1 (PRECEDENCE_LEVEL_NONE)]  NormalizedPrecedence:[0 (INTERNAL_PRECEDENCE_0)]  Preempt Hunt Not Set
Jul 30 00:20:40.867: //-1//Dest:/AFW_Destination_New:
Jul 30 00:20:40.867: //149//Dest:/AFW_Destination_AddDest:
Jul 30 00:20:40.867: //-1//Dest:/AFW_Destination_AddDest: adding destination "121"
Jul 30 00:20:40.871: //149//Dest:/AFW_Destination_SetIntWrkLeg: LEG[149    ][LEG_INCPROCEED(3)][Cause(0)]
Jul 30 00:20:40.871: //149//Dest:/TermInterworking: current state IW_STATE_INIT, Keep IntWrkLeg
Jul 30 00:20:40.871: //149//Dest:/DestSetIntWrkLeg:
Jul 30 00:20:40.871: //149//Dest:/AFW_M_Destination_Initiate:
Jul 30 00:20:40.871: //149//Dest:/AFW_M_Destination_Initiate: Outgoing guid : 003E4EBE.554E31E3.7D008601.C0A88196
Jul 30 00:20:40.871:  Incoming_guid : 00000000.00000000.00000000.00000000
Jul 30 00:20:40.871: //149//Dest:/AFW_M_Destination_Initiate: Outgoing gcid : 00000000.00000000.00000000.00000000
Jul 30 00:20:40.871:  Incoming_gcid : 00000000.00000000.00000000.00000000
Jul 30 00:20:40.871: //149//Dest:/DestSetupInitiate:
Jul 30 00:20:40.871: //149//Dest:/DestAddRerouteSetupInfo:
Jul 30 00:20:40.871: //149//Dest:/DestAddTransferSetupInfo:
Jul 30 00:20:40.871: //149//Dest:/DestMatchDialPeer:
Jul 30 00:20:40.871: //149//Dest:/DestMatchDialPeer: src carrier id:, tgt carrier id:
Jul 30 00:20:40.871: //149//Dest:/DestQueuePeers: Matched peers:
Jul 30 00:20:40.871: //149//Dest:/DestPeerItemUpdatePreemptInfo:
Jul 30 00:20:40.871: //-1//Dest:/DestQueuePeers:  20004
Jul 30 00:20:40.871: //-1//Dest:/DestQueuePeers: , Total(1)
Jul 30 00:20:40.871: //149//Dest:/DestDialPeerRotary:
Jul 30 00:20:40.871: //149//Dest:/DestOutboundCallUsingPeer: dest(121), numexpDest(121), numDestDigits(4)
Jul 30 00:20:40.871: //149//Dest:/DestOutboundCallUsingPeer:    prefix(), peer tag(20004)
Jul 30 00:20:40.871: //149//Dest:/DestUpdatePreemptSetupInfo:
Jul 30 00:20:40.871: //149//Dest:/DestDialPeerFilter:
Jul 30 00:20:40.871: //149//Dest:/DestDialPeerFilter: Checking peer [20004]
Jul 30 00:20:40.871: //149//Dest:/DestPeerFilterRouteCode: Route Code not available in callInfo
Jul 30 00:20:40.871: //149//Dest:/DestCheckTeleUnassBusy:
Jul 30 00:20:40.871: //149//Dest:/DestSetup:
Jul 30 00:20:40.875: //149//Dest:/DestSetup: Destination setup success
Jul 30 00:20:40.875: //149//Dest:/AFW_M_Destination_Initiate: attempting call to destination 121
Jul 30 00:20:40.875: //149//Call:/CS_Placecall: Call placed to 121 index 0
Jul 30 00:20:40.879: //149//Dest:/AFW_M_Destination_Action:
Jul 30 00:20:40.879: //149//Dest:/AFW_Destination_Action:
Jul 30 00:20:40.879: //149//Dest:/OB_FSM_Drive:
Jul 30 00:20:40.879: //149//Dest:/OB_Ignore: IGNORING EVENT
Jul 30 00:20:40.879: //149//Dest:/IW_FSM_Drive:
Jul 30 00:20:40.879: //149//Dest:/IW_Ignore:  IGNORING EVENT
Jul 30 00:20:40.879: //149//Dest:/DestIsEventNotified:
Jul 30 00:20:40.879: //149//Dest:/DestComplete: peer #:20004 IW State IW_STATE_INIT, OB State OB_STATE_SETTING
Jul 30 00:20:40.883: //149//Dest:/AFW_M_Destination_Action:
Jul 30 00:20:40.883: //149//Dest:/AFW_Destination_Action:
Jul 30 00:20:40.883: //149//Dest:/OB_FSM_Drive:
Jul 30 00:20:40.883: //149//Dest:/OB_Setting_Proceeding:
Jul 30 00:20:40.883: //149//Dest:/IW_FSM_Drive:
Jul 30 00:20:40.883: //149//Dest:/IW_InitProc_Proceeding:
Jul 30 00:20:40.883: //149//Dest:/DestIsEventNotified:
Jul 30 00:20:40.883: //149//Dest:/DestComplete: peer #:20004 IW State IW_STATE_INIT, OB State OB_STATE_SETTING
Jul 30 00:20:40.883: //149//Dest:/AFW_M_Destination_Action:
Jul 30 00:20:40.887: //149//Dest:/AFW_Destination_Action:
Jul 30 00:20:40.887: //149//Dest:/OB_FSM_Drive:
Jul 30 00:20:40.887: //149//Dest:/OB_Setting_Alert:
Jul 30 00:20:40.887: //-1//Dest:/OB_Setting_Alert: aData bitmask 0x1

Jul 30 00:20:40.887: //-1//Dest:/OB_Setting_Alert: aData.display_info=Dr. Klaus Gierke

Jul 30 00:20:40.887: //149//Dest:/IW_FSM_Drive:
Jul 30 00:20:40.887: //149//Dest:/IW_AlertRing:
Jul 30 00:20:40.887: //149//Dest:/DestRingBackFromApp: Leg state [LEG_INCALERTING], alert_sent [1], tone_playing [0]
Jul 30 00:20:40.887: //149//Dest:/DestRingBack: Skip Ringback Tone
Jul 30 00:20:40.887: //149//Dest:/DestUpdateDisplayInfo:
patrick_CME#
Jul 30 00:20:40.887: //149//Dest:/DestIsEventNotified:
Jul 30 00:20:40.887: //149//Dest:/DestComplete: peer #:20004 IW State IW_STATE_ALERT_OOB, OB State OB_STATE_SETTING
patrick_CME#
Jul 30 00:20:52.191: //149//Dest:/AFW_M_Destination_Action:
Jul 30 00:20:52.191: //149//Dest:/AFW_Destination_Action:
Jul 30 00:20:52.191: //149//Dest:/IW_FSM_Drive:
Jul 30 00:20:52.191: //149//Dest:/IW_AlertOut_Disconnect:
Jul 30 00:20:52.191: //149//Dest:/DestTerminate:
Jul 30 00:20:52.191: //149//Dest:/TermInterworking: current state IW_STATE_ALERT_OOB, Keep IntWrkLeg
Jul 30 00:20:52.191: //149//Dest:/TermOutboundCall: current state OB_STATE_SETTING
Jul 30 00:20:52.191: //149//Dest:/DestReturn: Destination Returning(ds_008 Status DEST_INTWRKLEG_DISCONNECT)
Jul 30 00:20:52.191: //149//Dest:/OB_FSM_Drive:
Jul 30 00:20:52.191: //149//Dest:/OB_Ignore: IGNORING EVENT
Jul 30 00:20:52.191: //149//Dest:/DestComplete: peer #:20004 IW State IW_STATE_DONE, OB State OB_STATE_DONE
Jul 30 00:20:52.191: //149//Dest:/DestComplete: Module already completed
Jul 30 00:20:52.195: //149//Call:/AFW_M_CallSetup_Terminate:
Jul 30 00:20:52.195: //-1//Call:/CS_Terminate:
Jul 30 00:20:52.195: //149//Dest:/AFW_M_Destination_Terminate:
Jul 30 00:20:52.195: //149//Call:/CS_Complete: Can't complete
Jul 30 00:20:52.195: //149//Dest:/AFW_M_Destination_EventPreProcess:
Jul 30 00:20:52.195: //149//Call:/AFW_M_CallSetup_Action:
Jul 30 00:20:52.195: //149//Call:/CS_Closing_ModuleDone:
Jul 30 00:20:52.195: //149//Call:/CS_Closing_ModuleDone:
patrick_CME#All sub-modules completed, move to DONE state
Jul 30 00:20:52.195: //149//Call:/CS_Complete: CallSetup Returning(ls_015 Status CS_TERMINATED_BY_USER)
Jul 30 00:20:52.195: //-1//Dest:HN00136F50:/AFW_M_Destination_Free:
Jul 30 00:20:52.195: //-1//Dest:HN00136F50:/DestEmptyPreemptHoldQ:
Jul 30 00:20:52.195: //149//Call:/AFW_M_CallSetup_EventPreProcess:
Jul 30 00:20:52.195: //-1//Call:HN00136F50:/AFW_M_CallSetup_Free:

Subject: RE: leg proceeding on h323 leg
Replied by: Anusha Kannappan on 01-08-2011 07:02:43 AM
Hi Patrick,

Are you referring to the ev_proceeding event that is received when leg setup is being done? If yes means here is a small infor about the event.

ev_proceeding is an intermediate event generated by the leg setup or leg setup_continue commands to set up a call. If the callinfo paramater, notifyEvents, is specified, the script receives an ev_proceeding message when the system receives a proceeding event from the remote end.

Thanks,
Anusha
Labels:
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links
Discussions
Customers Also Viewed These Support Documents