Inbound calls to FXO ring once then busy. CCM, CUE, MGCP

[Erick Bergquist]

We have issue where we are losing inbound calls due to calls hearing a ring, then a busy.

2811 MGCP Gateway going to CCM 4.02(a) SR1a

FXO ports Attendant DNs configured for CTI Route Point DN

2811 is on 12.4(1) IOS and CUE is on 2.1.1

CTI RP is a AutoAttendant trigger on a AIM-CUE module in 2811.

On calls that fail, we see this in CCM detailed trace.

ERROR Unable to receive call for FXO Trunk-check portType/callAttendent

06/07/2005 15:13:58.105

CCM|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744

826><MN::MGCPEndPoint><MV::aaln/S0/SU0/3@GW2801

><DEV::>

06/07/2005 15:13:58.105 CCM|MGCPTrunkD - ERROR Unable to receive call for FXO

Trunk-check portType/callAttendent

DN.|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744

826><IP::172.19.4.2><DEV::aaln/S0/SU0@GW2801>

06/07/2005 15:13:58.105 CCM|MGCPHandler send msg SUCCESSFULLY to: 172.19.4.2

200 325636426

|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744826

><IP::172.19.4.2><DEV::aaln/S0/SU0@GW2801>

06/07/2005 15:13:58.105 CCM|MGCPTrunkD - MGCPOutputStartTone: 76

endpointId=AALN/S0/SU0/3@GW2801

|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744826

><IP::172.19.4.2><DEV::aaln/S0/SU0@GW2801>

06/07/2005 15:13:58.105 CCM|MGCPHandler send msg SUCCESSFULLY to: 172.19.4.2

RQNT 237010 AALN/S0/SU0/3@GW2801 MGCP 0.1

X: 0

R: L/hu, D/[0-9ABCD*#]

S: T/ro

Q: process,loop

[thisisshanky]

Can you call the attendant from an inside ip phone ? Is the CUE on the same router as the MGCP gateway ?

PS: why does the MGCP trace show the name as GW2801 -- is it named as GW2801 ?

[Erick Bergquist]

Yea, most calls go through fine but we have instances where some calls don't connect to AA.

The calling party hears one ring, then busy signal. On router, show voice call summ shows the port connected and None as codec type. All devices in same region and G711 calls. Again, this works for most calls and we can call back and the same port will work fine but then later on fail, then work again.

When the error happens in CCM Detailed traces, there is no trace of activity from that time in the CTI traces and error message suggests ccm is having issue picking up call from FXO port.

Gw2801 is name of Gateway (I edited it actually for this posting).

[thisisshanky]

Run trace on the CUE to see what happens in CUE, when the call fails, You can try a show trace buffer command with a pipe (|) to specify specific match strings to filter the output of the trace. This will show if the call is being answered by the AA or not.

Check here for more details on traces.

http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_tech_note09186a008041d950.shtml

[Erick Bergquist]

Update on this, we had the issue again on an inbound call from another MGCP gateway with FXO ports and same error in CCM Detailed trace.

This gateway, the voice port Attendant DN was set to go a IP Phone however and that phone never rings and nothing in trace shows call manager attempting to extend call to phone or reach that phone at all. Same behavior as before. The phone is registered and works fine, as it receives calls fine from this port on the gateway at other times and from other lines on the gateway.

So issue appears to be Call Manager, or MGCP related on the Call Manager side.

[frommer]

I am getting the same issue with a VIC2-4FXO MGCP in an 2811. I am working with TAC now and will post if get it fixed....

[Erick Bergquist]

What version of Call Manager?

[frommer]

4.1(2)SR1

[Erick Bergquist]

Ok. Were on 4.02a SR1a. Had issue again and TAC is looking at it also.

You are seeing the same error in the CCM Detailed trace about unable to answer FXO?