[cisco-voip] Adding CUCM6 to an existing RSVP-enable topology

[Jose Mujica]

Hi.

I was wondering if someone from the forum can shed some light. Currently we
have a network that is already RSVP-enable end-to-end that supports 8-10
regional offices using different types of circuits / bandwidth to
interconnect them. Customer deployed VoIP Gateways in all regional offices
connected to an existing Nortel PBXs in each office and all VoIP Gateways
are registered to a Gatekeeper cluster for all dialplan resolution. CAC /
QoS is beeing done using RSVP end-to-end and it is running without any
problem for quite some time.

Now the customer deploy a CUCM6 cluster in one of the regional offices and
registered an H323 trunk to the gatekeeper in order to call other reginal
offices. The problem is that because all other regional VoIP Gateways are
using RSVP to establish voice calls in order to have bandwidth available and
proper qos. Calls from/to CUCM Cluster are failing do to RSVP. Customer
removed rsvp request from the dialpeers on the non-CUCM regional offices and
they were able to send/receive calls to CUCM cluster but without using their
RSVP bandwidth reservation mechanism and proper QoS.

I know that CUCM has location based RSVP but I think that in order to have
that working CUCM needs to manage the other regional offices in order to
have RSVP Agents on those sites as well as the main office. That is not my
customer scenario at the moment.

Is there a way to have the H323 CUCM Trunk RSVP enable in order to have
calls working in the customer existing topology/configuration as they are
now? As of this moment customer took out all the "req-qos guaranteed-delay"
from all the VoIP Gateways in order to be able to call the CUCM site. But
without that command in the DialPeer the VoIP gateways cannot use the RSVP to
request quality of service guarantees from the network.

Any ideas?

Thanks in Advanced,
Jose Mujica
CCIE 18184
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090114/2c29fa5e/attachment.html>