Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help Need for VOIP Cisco Gateway to Gatekeeper configuration

Status
Not open for further replies.

buyerinneed

Vendor
Sep 27, 2006
1
US
Hi,

I hope someone can help me. I am the Buyer for my company. I bring in Carriers. As of late I have been adding what are considered the top International carriers and now have some issues. The issue and my question to you great tech guys is When configuring a Cisco gateway to Gatekeeper should the same configuration be used for inbound traffic that is used for outbound traffic. Specifically as follows and suggested :

Good morning. The problem was located. There was a problem with An inbound customer and the gatekeeper configuration for the Outbound carrier. The customer is an inbound group and on our inbound groups we configure them with a “trunk group” configuration to minimize the amount of configuration needed in a router. Within the “trunk group” configuration, you tell the group the max amount of calls that can be placed on that group. Within a gatekeeper registration there is an required field for capacity. The router was inserting the “trunk group” information into this field and sending it over to the Carrier. Since the Carriere did not know what the Customer was it would reject this information, which would lead to the carrier sending a un-register packet. During the 20 seconds that the gatekeeper is un-registered calls would fail to “no route to destination”. When the gatekeeper was registered however, calls were still failing due to the poor quality of the carrier. The tickets opened with the Carrier with one way audio and recovery on timer expiry were due to the carrier and the quality of service provided to us. The gatekeeper issue just added to the issues to what the Carrier already had. We have fixed the problem by removing the “trunk group” configuration. For the future with gatekeeper configurations, we just need to monitor the router if the gatekeeper configuration will be on the same router as an inbound customer. This issue will not be the same for every gatekeeper/inbound customer case.

Any and all help is appreciated

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top