[cisco-voip] Question on FXO error in CCM Trace for MGCP Gateway

[Ortiz, Carlos]

How are your analog ports set up?  Is the telco forcing them to hunt
inbound?  We had some initial issues where one of the analog lines was
not working somewhere in the hunt group.  This would lead to a situation
where you would only get this problem when it reaches the specific port
that has a problem.

Carlos

-----Original Message-----
From: Erick Bergquist [mailto:erickbe at yahoo.com] 
Sent: Tuesday, June 21, 2005 10:19 PM
To: Ortiz, Carlos
Subject: RE: [cisco-voip] Question on FXO error in CCM Trace for MGCP
Gateway

A 2811 with 12.4(1) IOS

Multiple locations with this type of gateway but only
one experiencing this issue where the people calling
in can't get through occassionally and then tell them
when they call back they had troubles.

--- "Ortiz, Carlos" <CORTIZ at broward.org> wrote:

> Erick,
> 
> I don't have a solution for you, but a couple of
> questions. 
> 
> 1) What kind of gateway are you using?
> 2) Is this a widespread issue among your gateways or
> just this one?
> 3) Is the detail tracing the only way to monitor
> MGCP calls?
> 
> Reason I am asking these questions is that I
> currently run the same
> version 4.02 (sr1).  I have one location using an
> MGCP gateway with FXO
> ports.  They have been running fine for 4 months,
> but yesterday I got
> some complaints that some outbound calls were not
> completing. I just
> reset all the phones at the location and then they
> said everything was
> fine.  Before I reset the phones I tested their
> claims and did not see
> any issues dialing out, but I just reset the phones
> for good measure.
> This location is using a 2811 IOS 12.3(8)T5.
> 
> Carlos 
> 
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On
> Behalf Of Erick Bergquist
> Sent: Monday, June 20, 2005 10:16 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Question on FXO error in CCM
> Trace for MGCP
> Gateway
> 
> Hi,
> 
> Has anyone seen/had the following error in a CCM
> Detailed trace for issues with inbound calls on FXO
> ports?
> 
> 06/07/2005 15:13:58.105 CCM|MGCPTrunkD - ERROR
> Unable
> to receive call for FXO Trunk-check
> portType/callAttendent
> 
> 
> The FXO port is MGCP, and the issue occurs across
> multiple FXO ports on same gateway occassionally and
> then clears up on it's own. The attendant DN is same
> for all ports and calls work fine and one day we may
> have issue where inbound call rings once, then user
> hears busy signal and this error is in trace. Not
> all
> calls fail, just some and then things will be fine
> again for awhile.
> 
> Upon further searches of trace files, am seeing the
> error also following outbound calls after a call
> disconnects so am puzzled why it is occuring on a
> call
> with a normal disconnect now and then.
> 
> Here is one situation for outbound call where user
> hangs up and this error occurs, from CCM Detailed
> traces.
> 
> IP Phone caller is on a call with external caller
> 
> IP Phone user hangs up
> 
> Call Manager sends MGCP DLCX message to gateway
> 
> Gateway sends notification (NTFY) back to CCM
> 
> We then have this error in the trace about unable to
> receive call at same timestamp as disconnect
> messages.
> 
> This is on CCM 4.0(2a)SR1a
> 
> 
> 
> 		
> ____________________________________________________
> 
> Yahoo! Sports 
> Rekindle the Rivalries. Sign up for Fantasy Football
> 
> http://football.fantasysports.yahoo.com
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 



		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com