H.323

2
H323: ==== H.225 -->handles call setup and teardown and q.931 operations. H.225 RAS(Register admission status)--->Handles the gatekeeper H.245 Feature negotiation(codec negotiation) H.261/H.263 --Video conferencing H.450--Supplementary services (Hold etc) H323 Fast start(default)-->combining the H.225 and H.245 signalling in a single message. T.120-->Data Transfer Why would we use H323? 1)Widely supported and interoperated(h323 is the default protocol for Cisco) 2)It supports Fractional PRI 3)You want caller-id support on FXO or T1 CAS-->H323 Supports whereas MGCP doest not support. Explanation: you are getting an incoming call from PSTN through FXO port on MGCP gateway and MGCP Gateway is connected to call manager. The caller id informatio n you will not get when using the MGCP. 4)PRI Call preservation: suppose the call agent (CUCM goes down) then h323 doest not drop call, in case o f MGCP also call will not drop. For MGCP pri backhaul the calls are dropped. 5)Many call routing and manipulation options 6)supports NFAS(Non facility associated signalling): one siganalling for multipl e PRI lines--Result u will have more channels. 7)H.323 gatekeeper support-->Call admission control H.323 ===== Video codec --H.261 & H.263 H.245 --Control signalling & Capabilities exchange H.225 --Call signalling, Registration & RAS control port--1720 H.323 configuration =================== enable the H.323 service ------------------------

description

H.323

Transcript of H.323

H323:====

H.225 -->handles call setup and teardown and q.931 operations.

H.225 RAS(Register admission status)--->Handles the gatekeeper

H.245 Feature negotiation(codec negotiation)

H.261/H.263 --Video conferencing

H.450--Supplementary services (Hold etc)

H323 Fast start(default)-->combining the H.225 and H.245 signalling in a single message.

T.120-->Data Transfer

Why would we use H323?

1)Widely supported and interoperated(h323 is the default protocol for Cisco)

2)It supports Fractional PRI

3)You want caller-id support on FXO or T1 CAS-->H323 Supports whereas MGCP doest not support.

Explanation: you are getting an incoming call from PSTN through FXO port on MGCP gateway and MGCP Gateway is connected to call manager. The caller id information you will not get when using the MGCP.

4)PRI Call preservation:

suppose the call agent (CUCM goes down) then h323 doest not drop call, in case of MGCP also call will not drop. For MGCP pri backhaul the calls are dropped.

5)Many call routing and manipulation options

6)supports NFAS(Non facility associated signalling): one siganalling for multiple PRI lines--Result u will have more channels.

7)H.323 gatekeeper support-->Call admission control

H.323=====

Video codec --H.261 & H.263

H.245 --Control signalling & Capabilities exchange

H.225 --Call signalling, Registration & RAS control port--1720

H.323 configuration===================

enable the H.323 service------------------------

conf t

voice service voip

h323

no shutdown

verify gateway status----------------------

show gateway

H323 Gateway Addition in call Manager:--------------------------------------

H323 and SIP gatewaty never registers with the gateway.

Call Manager shows the status of them as Unknown.

Cisco CM Administration----->device menu--->Gateway--->Add new-->H323 gateway-->device name==>ip-address.

In the Main menu Call routing--->Route Hunt---> Route pattern-->Add new-->

Route Pattern ==>5001

gateway/Route list ==Ip-address of h323 gateway.

Configuration of H323 Gateway to communicate with cal Manager:--------------------------------------------------------------

conf t

create loopback interface

int loopback 0

ip address 192.168.1.19 255.255.255.255

h323-gateway voip interface

h323-gateway voip