Without a Gatekeeper, why would an H.323 issue a Reject a call (assuming
ports still available)?

I keep getting registerRejectInterceptRequest on the CallManager side.

Any ideas?



Jonathan

[ Post a follow-up to this message ]

The "registerRejectInterceptRequest" you see in the CCM trace is not
apart of the reason why the call is rejected.  This is a function of
the Forwarding Manager within the CCM code.  I believe all it is doing
is setting up the intercept information for when/if the call is
forwarded.  If the GW is rejecting the call then you will want to look
at debugs on the GW to determine the problem.  If the port is a PRI
then you can start with "debug isdn q931".  If not then let us know the
port type.

Kevin
On Oct 14, 2005, at 4:21 PM, Jonathan Charles wrote:

> Without a Gatekeeper, why would an H.323 issue a Reject a call
> (assuming ports still available)?
>
>  I keep getting registerRejectInterceptRequest on the CallManager side.
>
>  Any ideas?
>
>
>
>  Jonathan
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]