Cisco 30 VIP Troubleshooting Manual page 68

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
*Mar 12 04:03:57.177:
UserInformation ::=
*Mar 12 04:03:57.181: {
*Mar 12 04:03:57.181: h323-uu-pdu
*Mar 12 04:03:57.181: {
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.181:
*Mar 12 04:03:57.185:
*Mar 12 04:03:57.185:
*Mar 12 04:03:57.185:
*Mar 12 04:03:57.185:
*Mar 12 04:03:57.189:
The following is debug output for Call Control Application Programming interface (CCAPi).
Call control APi is indicating an incoming call. Called and calling party information can also be
seen in the following output. CCAPi matches the dial peer 0, which is the default dial peer. It is
matching dial peer 0 because the CCAPi could not find any other dial peer for the calling
number, so it is using the default dial peer.
*Mar 12 04:03:57.189: cc_api_call_setup_ind (vdbPtr=0x616C9F54, callInfo={called=3333, calling=1001,
fdest=1 peer_tag=0}, callID=0x616C4838)
*Mar 12 04:03:57.193: cc_process_call_setup_ind (event=0x617A2B18) handed call to app "SESSION"
*Mar 12 04:03:57.193: sess_appl: ev(19=CC_EV_CALL_SETUP_IND), cid(17), disp(0)
*Mar 12 04:03:57.193: ccCallSetContext (callID=0x11, context=0x61782BBC)
Mar 12 04:03:57.193: ssaCallSetupInd finalDest cllng(1001), clled(3333)
*Mar 12 04:03:57.193: ssaSetupPeer cid(17) peer list: tag(1)
*Mar 12 04:03:57.193: ssaSetupPeer cid(17), destPat(3333), matched(4), prefix(), peer(6179E63C)
*Mar 12 04:03:57.193: ccCallSetupRequest (peer=0x6179E63C, dest=, params=0x61782BD0 mode=0,
*callID=0x617A87C0)
*Mar 12 04:03:57.193: callingNumber=1001, calledNumber=3333, redirectNumber=
*Mar 12 04:03:57.193: accountNumber=,finalDestFlag=1,
guid=0098.89c8.9233.511d.0300.cddd.ac10.46e6
The CCAPi matches the dial-peer 1 with the destination pattern, which is the called number
3333. Keep in mind that peer_tag means dial peer. Notice the calling and called party number in
the request packet.
*Mar 12 04:03:57.193: peer_tag=1
*Mar 12 04:03:57.197: ccIFCallSetupRequest: (vdbPtr=0x617BE064, dest=, callParams={called=3333,
calling=1001, fdest=1, voice_peer_tag=1}, mode=0x0)
The following debug output shows the H.225 Alerting messages are returning to the
Cisco CallManager.
*Mar 12 04:03:57.197: ccCallSetContext (callID=0x12, context=0x61466B30)
*Mar 12 04:03:57.197: ccCallProceeding (callID=0x11, prog_ind=0x0)
*Mar 12 04:03:57.197: cc_api_call_proceeding(vdbPtr=0x617BE064, callID=0x12, prog_ind=0x0)
*Mar 12 04:03:57.197: cc_api_call_alert(vdbPtr=0x617BE064, callID=0x12, prog_ind=0x8, sig_ind=0x1)
© 2000 Cisco Systems, Inc.
H225Lib::h225RecvData: Q.931 SETUP received from socket [1]value H323-
h323-message-body setup :
{
protocolIdentifier { 0 0 8 2250 0 2 },
sourceAddress
{
h323-ID : "1001"
},
destinationAddress
{
e164 : "3333"
},
H225Lib::h225RecvData: State changed to [Call Present].
68