Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

1700 ios h323 gateway fail to register with CCM

I am trying to have 1750-2V router with 2FXS , to configure as h323 gateway, with CCM 3.3.

Router config is as follows;

interface FastEthernet0

ip address 192.168.10.1 255.255.255.0

speed auto

h323-gateway voip interface

h323-gateway voip id Call-manager multicast

h323-gateway voip h323-id 192.168.10.1

h323-gateway voip bind srcaddr 192.168.10.1

!

dial-peer voice 2 pots

destination-pattern 4444

port 2/1

!

dial-peer voice 100 voip

destination-pattern 600

session target ipv4:192.168.10.3

!

gateway

!

I can ping from the router to CCM server and vice-versa. The gateway as been defined in CCM as h323 gateway.

The router runs IOS version 12.1(5)T9.

The gateway doesn't get registered with CCM.

debug h225 asni gives following output;

value RasMessage ::= gatekeeperRequest :

{

requestSeqNum 8

protocolIdentifier { 0 0 8 2250 0 2 }

rasAddress ipAddress :

{

ip '09BB6346'H

port 54237

}

endpointType

{

gateway

{

protocol

{

voice :

{

supportedPrefixes

{

}

}

}

}

mc FALSE

undefinedNode FALSE

}

gatekeeperIdentifier {"Call-manager"}

endpointAlias

{

e164 : "3333",

e164 : "4444"

}

}

RAW_BUFFER::=

00 A0000706 0008914A 00020009 BB6346D3 DD088001 3C050100 05800043 0061006C 006C002D 006D0061 006E0061 00670065 00720201 80666601 807777

00:05:34: PDU DATA = 80DF5C9C

Any ideas as to what has gone wrong ?

3 REPLIES
Silver

Re: 1700 ios h323 gateway fail to register with CCM

It is normal for an H323 gateway to not get registered with Callmanager. Unlike MGCP (client-server model), H323 is a peer-to-peer protocol and hence the gateways do not register with Callmanager.

For Call adminssion control and bandwidth control, you can have the H323 gateway register with a H323 gatekeeper. Callmanager does not do any gatekeeper functionality. You can use a router with Gatekeeper image for that functionality.

In your configuration, you have configured a gatekeeper with the command

h323-gateway voip id Call-manager multicast

If you do not have a gatekeeper in your network, you can remove this command.

Try placing a call from the analog phone to an IP phone and see how it goes.

Silver

Re: 1700 ios h323 gateway fail to register with CCM

First of all if you are adding this gateway to CCM, then the config doesn't look correct. Change your config to this:

interface FastEthernet0

ip address 192.168.10.1 255.255.255.0

speed auto

h323-gateway voip bind srcaddr 192.168.10.1

!

dial-peer voice 2 pots

destination-pattern 4444

port 2/1

!

dial-peer voice 100 voip

destination-pattern 600

session target ipv4:192.168.10.3

In CCM add the gateway as h323 using Device Name 192.168.10.1. Remember that the Registration will always show unknown on the CCM, but you should get 192.168.10.1 in the IP Address status.

The debug that you were doing and most of the commands is used when you will register this gateway to a gatekeeper.

Thanks,

Partha

New Member

Re: 1700 ios h323 gateway fail to register with CCM

Many thanks for both Partha and Anand !

As you very correctly stated, I can only see the IP address of the gateway in CCM, but the status is "unknown". Therefore I was trying to make it available to CCM.

But I can now place the calls for IPtel domain to Analog domain, vice-versa !

Thanks again !

178
Views
10
Helpful
3
Replies