Voice over IP Cisco - H.323 LCR setup

This is Interesting: Free IT Magazines  
Home > Archive > Voice over IP Cisco > January 2008 > H.323 LCR setup





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author H.323 LCR setup
Louis Koekemoer \(ZA\)

2008-01-03, 1:11 pm

I need help at a client with their LCR routing. We've got a H.323
gateway setup on the CallManager pointing to the LCR supplier's server
ip address over the WAN. The LCR co can call my client over this trunk,
but when we are calling out, we just get an engaged tone. The way I
tested it was to create a route pattern to a cell number, and pointing
this pattern to the H.323 gateway directly. This way I eliminate any
issues with route lists and route groups. As I'm pointing to their
gateway directly, I have now way to debug from my side. They say they
are not getting anything from me. Their trunks are pointing to the
subscriber and publisher ip's. Can any of you guys send me in some
direction here?



Kind Regards



Louis Koekemoer
Cisco IPT Systems Engineer

Dimension Data South Africa

* +27 11 575 6560

* +27 76 608 7221

*louis.koekemoer@za.didata.com <mailto:louis.koekemoer@za.didata.com>




This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer.htm"

Matthew Saskin

2008-01-03, 1:11 pm

'debug voip ccapi inout' should let you see call flow among dial peers =

to verify that your call is actually leaving your gateway and heading =

towards them.

-matt

Louis Koekemoer (ZA) wrote:
> I need help at a client with their LCR routing. We=92ve got a H.323 =


> gateway setup on the CallManager pointing to the LCR supplier=92s server =


> ip address over the WAN. The LCR co can call my client over this trunk, =


> but when we are calling out, we just get an engaged tone. The way I =


> tested it was to create a route pattern to a cell number, and pointing =


> this pattern to the H.323 gateway directly. This way I eliminate any =


> issues with route lists and route groups. As I=92m pointing to their =


> gateway directly, I have now way to debug from my side. They say they =


> are not getting anything from me. Their trunks are pointing to the =


> subscriber and publisher ip=92s. Can any of you guys send me in some =


> direction here?
> =


> =


> =


> **/Kind Regards/**
> =


> =


> =


> */Louis Koekemoer/*
> /Cisco IPT Systems Engineer/
> =


> /Dimension Data //South Africa/
> =


> (/ +27 11 575 6560/
> =


> ) +/27 76 608 7221/
> =


> */louis.koekemoer@za.didata.com <mailto:louis.koekemoer@za.didata.com>/
> =


> =


> =


> This email and all contents are subject to the following disclaimer:
> =


> "http://www.dimensiondata.com/emaildisclaimer.htm"
> =


> =


> ------------------------------------------------------------------------
> =


> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

Justin Steinberg

2008-01-03, 1:11 pm

a few things I would check:

codec - I would verify what codec the CM will try to use and verify
that is supported by the h323 ISP.
mtp - You could also try to check the 'require MTP' box on the h323
gwy config page and reset the gwy and try again.
faststart/slowstart - see what your ISP supports or requires and
configure the same on CM
digits sent - verify you are sending digits that your ISP expects
firewall - check your WAN firewall

On Jan 3, 2008 8:45 AM, Louis Koekemoer (ZA)
<Louis.Koekemoer@za.didata.com> wrote:
>
>
>
>
> I need help at a client with their LCR routing. We've got a H.323 gateway
> setup on the CallManager pointing to the LCR supplier's server ip address
> over the WAN. The LCR co can call my client over this trunk, but when we are
> calling out, we just get an engaged tone. The way I tested it was to create
> a route pattern to a cell number, and pointing this pattern to the H.323
> gateway directly. This way I eliminate any issues with route lists and route
> groups. As I'm pointing to their gateway directly, I have now way to debug
> from my side. They say they are not getting anything from me. Their trunks
> are pointing to the subscriber and publisher ip's. Can any of you guys send
> me in some direction here?
>
>
>
>
> Kind Regards
>
>
>
>
>
> Louis Koekemoer
> cisco IPT Systems Engineer
>
>
> Dimension Data South Africa
>
>
>
> ( +27 11 575 6560
>
>
> ) +27 76 608 7221
>
>
> *louis.koekemoer@za.didata.com
>
>
>
> This email and all contents are subject to the following disclaimer:
>
> "http://www.dimensiondata.com/emaildisclaimer.htm"
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com