Showing results for 
Search instead for 
Did you mean: 

The addition of trunk ports to the Cisco MeetingPlace audio server causes the existing trunk ports to enter busyout status


Core Issue

In this scenario, newly added Public Switched Telephone Network (PSTN) trunk ports are configured along with existing PBX trunk ports. The blade command is issued to add the ports. Port licenses are added successfully, and the license count is good as well.

However, when the blade command is issued, it overwrites the configuration characteristics of existing ports with those of the newly added ports. This causes the busyout status on the existing ports.

Note: The existing PBX trunk ports use loop-start signaling, but the newly added trunk ports use wink-start signaling.

Note: When loop start is used, the correct sample output for the spanstat -all command is a port status of 11. When wink start is used, the correct sample output for the spanstat -all command is a port status of 00.


To resolve this issue, manually reconfigure the existing ports with the correct port group configuration characteristics (using loop start).

If records of previous port configurations are not available, perform this procedure to resolve the issue:

  1. Review and enable new port groups with different configuration characteristics.

  2. Assign the trunk ports that are not functional to use the new port groups. 

  3. Restart the Cisco MeetingPlace audio server with the restart enable command. 

  4. Login to the Cisco MeetingPlace audio server, and issue the spanstat -all command to review the status of the changed ports. Verify their operational status again.

  5. Make test calls to verify operations.
  6. Test again with different port groups and using different configuration characteristics until the ports are functional.

For information on MeetingPlace Server quality issues, refer to:

MeetingPlace Server Voice Quality Issues