ohh.. i take that back,.... so CCIELabRat... what was it??.. u had the mtp
"on" ? or "off"??.. very curious now to see how it worked..

On Mon, Mar 23, 2009 at 10:14 PM, Joel Jose <[email protected]> wrote:

> no way... he must have meant that.. he "off" ed it.. and then it worked...
> the first case..the signaling went through..but the media must have
> terminated at the gateways...
>
>
> On Mon, Mar 23, 2009 at 10:09 PM, Chris Parker <[email protected]> wrote:
>
>> Does the call complete as 729 withthe mtp checked?
>>
>> ------------------------------
>> From: [email protected]
>> Sent: Monday, March 23, 2009 12:28 PM
>> To: Chris Parker <[email protected]>
>> Cc: [email protected] <[email protected]>
>> Subject: Re: [OSL | CCIE_Voice] Gatekeeper blues :|
>>
>> Yep, everything started working once I checked off requires MTP on the
>> trunk. .
>>
>> But why? The call is coming in as g.729 and the device pool the trunk is
>> in is set to g.729
>>
>>
>>
>>
>>
>> On Mon, Mar 23, 2009 at 11:54 AM, Chris Parker <[email protected]>wrote:
>>
>>> If you are getting ring through when you place the call, then your GK
>>> config is probably OK. If its ringing that tells me the GK sent the call to
>>> the UCM.
>>>
>>> The fact that it goes fast busy when you pick up sounds like a
>>> codec/media problem to me. Check the media resources config and your
>>> regions.
>>>
>>> Chris
>>>
>>> [email protected] wrote:
>>>
>>>> I'm working through scenario , trying to get 4 digit dial from BR2 to HQ
>>>> working via the HQ GK.
>>>> The GK config looks like this.
>>>>
>>>> gatekeeper
>>>>  zone local UCM ipexpert.com <http://ipexpert.com> 142.1.1.1
>>>>  zone prefix UCM 1... gw-priority 10 Trunk_2
>>>>  zone prefix UCM 1... gw-priority 9 Trunk_1
>>>>  zone prefix UCM 1... gw-priority 0 cmegw
>>>>  zone prefix UCM 3... gw-priority 10 cmegw
>>>>  zone prefix UCM 3... gw-priority 0 Trunk_2 Trunk_1
>>>>  gw-type-prefix 1#* gw ipaddr 142.2.64.12 1720 gw ipaddr 142.2.64.11
>>>> 1720
>>>>  no shutdown
>>>>
>>>> I have the UCM registering without a tech-prefix defined and I've
>>>> adjusted the "service parameter" to insure the UCM listens on port 1720.
>>>>
>>>> The problem is the call rings through to the HQ DN but comes up fast
>>>> busy when I answer the call.
>>>>
>>>> I've attempted to configure the "Trunk" from UCM as both an H.225 Trunk
>>>> as well as an ICT trunk.
>>>> I've unchecked "Wait for far end h.245 terminal capability" as well.
>>>>
>>>> Any help is greatly appreciated.
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> "it's not the years in your life that count. It's the life in your years."
> Abraham Lincoln
>



-- 
"it's not the years in your life that count. It's the life in your years."
Abraham Lincoln

Reply via email to