Meeetme issue with external call in CM5.1(3)ES4102

Unanswered Question
Nov 17th, 2008
User Badges:

CM server are running 5.1(3) ES4102 version. Hardware conference and transcoder are created. Voice gateway are running 12.(4)16b.

As ip phone user start a meetme conference, another ip phone user make external call to mobile user and transfer the call to existing meetme conference.External mobile user can join to meetme without issue.As the mobile user hang up, all remaining users in meetme will hear the disconnect tone. The meetme conference cannot release even all ip phone users hangup. It seems the voice path from the mobile user still exists.

If the external user comes from PSTN fix network e.g. office,home. As the external user hangup, the remaining phone users cannot hear disconnect tone and the meetme can be released after all members hangup the phone.

If the external mobile ring directly to existing meetme conference, the result is the same as from PSTN home user and will not case this issue.

It seems the mobile network cannot pass the disconnect signal to PSTN fix network.

I find out the command "disc_pi_off " but this command only useful in h.323 gateway, the current voice gateways are running MGCP protocol.

How can I fix this issue?

Does anyone have this experience?

Thanks for any suggestions!


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Anonymous (not verified) Sun, 11/23/2008 - 19:16
User Badges:

Test if the IOS conference or IOS Xcoder working by setting up Ahoc conference. Check whether Xcoder CFB on the gateway is working.

Are you using Software or Hardware Conference Bridges?

What codec is used when the call is setup between the IP phones?

What codec is used when the call is setup between the IP phone and external user via the MGCP gateway?

lwai Sun, 11/23/2008 - 19:57
User Badges:

Hi friend,

The issue is cause from PSTN exchange because the exchange need to backward compability with FXO lines.The call will be disconnected after 60 seconds while mobile user disconnect the call.

In new exchange, it will not casue this issue and the call disconnect immediately.

We have tested it in CM5.X and 6.X. It is not relative to CM.




This Discussion