31.07.2015 Views

Cisco - Gateway to Gatekeeper (H.235) and ... - VOIP Information

Cisco - Gateway to Gatekeeper (H.235) and ... - VOIP Information

Cisco - Gateway to Gatekeeper (H.235) and ... - VOIP Information

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Cisco</strong> - <strong>Gateway</strong> <strong>to</strong> <strong>Gatekeeper</strong> (<strong>H.235</strong>) <strong>and</strong> <strong>Gatekeeper</strong> <strong>to</strong> <strong>Gatekeeper</strong> (IZCT) Security Troubleshooting Guide!no scheduler max-task-timeno scheduler allocatentp master!endOGK2 Configuration!hostname ogk2!interface Ethernet0/0ip address 172.16.13.14255.255.255.224full-duplex!gatekeeperzone local ogk2 domainA.comzone remote ogk1 domainA.com172.16.13.35 1719zone remote tgk2 domainB.com172.16.13.16 1719 foreign-domainzone prefix tgk2 36*zone prefix ogk1 53*security izct password 111222lrq forward-queriesno shutdown!ntp clock-period 17208242ntp server 172.16.13.35!endCall Flow with DebugsThe following examples use the debugs <strong>to</strong> explain the call flow.no shutdown!ntp clock-period 17179797ntp server 172.16.13.35!endTGK2 Configuration!hostname tgk2!interface Ethernet0/0ip address 172.16.13.16255.255.255.224half-duplex!gatekeeperzone local tgk2 domainB.comzone remote tgk1 domainB.com172.16.13.41 1719zone remote ogk2 domainA.com172.16.13.14 1719 foreign-domainzone prefix tgk1 36*zone prefix ogk2 53*security izct password 111222lrq forward-queriesno shutdown!ntp clock-period 17179209ntp server 172.16.13.35!end1.A user on carrier E calls a user on carrier D.Mar 4 15:31:19.989: cc_api_call_setup_ind (vdbPtr=0x6264ADF0, callInfo={called=3653,called_oct3=0x80,calling=4085272923,calling_oct3=0x21,calling_oct3a=0x80calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,peer_tag=5336,prog_ind=0},callID=0x6219F9F0)Mar 4 15:31:19.993: cc_api_call_setup_ind type 13 , prot 0Mar 4 15:31:19.993: cc_process_call_setup_ind (event=0x6231A6B4)Mar 4 15:31:19.993: >>>>CCAPI h<strong>and</strong>ed cid 7 with tag 5336 <strong>to</strong> app "DEFAULT"Mar 4 15:31:19.993: sess_appl: ev(24=CC_EV_CALL_SETUP_IND), cid(7), disp(0)Mar 4 15:31:19.993: sess_appl: ev(SSA_EV_CALL_SETUP_IND), cid(7), disp(0)Mar 4 15:31:19.993: ssaCallSetupIndMar 4 15:31:19.993: ccCallSetContext (callID=0x7, context=0x621533F0)Mar 4 15:31:19.997: ssaCallSetupInd cid(7), st(SSA_CS_MAPPING),oldst(0),ev(24) ev->e.evCallSetupInd.nCallInfo.finalDestFlag = 1Mar 4 15:31:19.997: ssaCallSetupInd finalDest cllng(4085272923), clled(3653)Mar 4 15:31:19.997: ssaCallSetupInd cid(7), st(SSA_CS_CALL_SETTING),oldst(0),ev(24)dpMatchPeersMoreArg result= 0Mar 4 15:31:19.997: ssaSetupPeer cid(7) peer list: tag(3653) called number (3653)Mar 4 15:31:19.997: ssaSetupPeer cid(7), destPat(3653), matched(4), prefix(),peer(626640B0), peer->encapType (2)Mar 4 15:31:19.997: ccCallProceeding (callID=0x7, prog_ind=0x0)Mar 4 15:31:19.997: ccCallSetupRequest (Inbound call = 0x7, outbound peer=3653,dest=,http://kbase:8000/paws/servlet/ViewFile/18729/gw_security.xml?convertPaths=1 (31 of 49) [12/2/2003 5:34:20 PM]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!