failed-Incoming-Outgoing call collision in MGCP gateway

Unanswered Question
Oct 29th, 2007

Hi,

Here we have a CCM v5 connected to a MGCP Gateway, cisco 2811, we have it all configured, we think so...

the gateway is connected to a PBX.

But when debug mgcp packets is on we get this error message.

Oct 29 16:37:06.739: MGCP Packet received from 10.0.0.254:2427--->

CRCX 400 [email protected] MGCP 0.1

C: D0000000012d7963000000F50000000a

L: p:20, a:PCMU, s:off, t:b8

M: recvonly

<---

Oct 29 16:37:06.743: MGCP Packet sent to 10.0.0.254:2427--->

400 400 Voice call setup failed-Incoming-Outgoing call collision

<---

Oct 29 16:37:07.751: MGCP Packet received from 10.0.0.254:2427--->

CRCX 10400 [email protected] MGCP 0.1

C: D0000000012d7963000000F50000000a

L: p:20, a:PCMU, s:off, t:b8

M: recvonly

<---

Oct 29 16:37:07.755: MGCP Packet sent to 10.0.0.254:2427--->

400 10400 Voice call setup failed-Incoming-Outgoing call collision

<---

Oct 29 16:37:07.755: MGCP Packet received from 10.0.0.254:2427--->

DLCX 401 [email protected] MGCP 0.1

X: 1

S:

<---

Oct 29 16:37:07.755: MGCP Packet sent to 10.0.0.254:2427--->

250 401 already deleted connection

<---

Does anyone know what can be done to solve this problem?

Thanks,

Best Regards

Ricardo Rolhas

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Anonymous (not verified) Fri, 11/02/2007 - 12:30

This issue is documented in Cisco bug ID CSCsc43954. One possible workaround for this issue is to reload the gateway in order to recover the timeslots.

In order to prevent this problem, ensure that the DSP resources are not over-subscribed. This is especially true when the DSP resources are used for transcoding and conferencing on the gateway

Aaron Harrison Sat, 11/03/2007 - 04:14

Hi

If you are sure that your DSPs have been provisioned appropriately (i.e. you have sufficient for the number of channels you are running) and that the PBX end of the connection isn't rejecting the call... you may be hitting a bug with the DSPs - I've seen it before where a single channel will lock up and log this collision error when CallManager tried to use it.

If this happens to be the first or last channel it can block all calls as CM will repeatedly try the same channel.

You could try busying it out using the MGCP service parameters, or just rebooting the gateway to see if it resolves it temporarily.

If it doesn't then a config/DSP resource issue is more likely..

Aaron

Please rate helpful posts...

labredes1 Mon, 11/05/2007 - 04:04

Hi,

I think that our problem might be that the PABX is rejecting our calls... Do I need to make specific configurations in the PABX to accept the Bri Backhaul configuration?

André Santos

gogasca Sat, 11/03/2007 - 12:32

MAke sura that your voice ports (S0/SU0/P0/1) in your BRI are not shutdown.

Actions

This Discussion