[cisco-voip] Question on FXO error in CCM Trace for MGCP Gateway
Erick Bergquist
erickbe at yahoo.com
Mon Jun 20 22:16:14 EDT 2005
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
More information about the cisco-voip
mailing list