Resolve Fast-Busy When Calling SA-Announce Paging Groups
There are several things that can cause a fast busy when calling a paging group:
- SA-Announce Broadcast Service has stopped.
- Connection to CUCM is blocked.
- G.711 audio isn't set in the device pool of the paging group.
SA-Announce Broadcast Service Stopped
- From the SA-Announce server, navigate to Start > Run > Services.msc.
- Start or restart the SA-Announce Broadcaster Service.
- Test the group.
Connection to CUCM Blocked
- From the SA-Announce server, navigate to Start > Control Panel > Windows Firewall.
- Verify the firewalls are disabled or the appropriate firewall ports are opened:
- SA-Announce Server to CUCM:
- Skinny Client Control Protocol (SCCP) TCP: 2000
- TTP/SOAP/AXL TCP: 80, 443, 8443
- Real-Time Protocol (RTP) UDP: 20480-32767
- TAPI TCP: 2748
- SA-Announce Server to IP Phones:
- HTTP TCP: 80
- Real-Time Protocol (RTP) UDP: 20480-32767
- Multicast Real-Time Protocol (RTP) UDP: 20480-32767
- IP Phones to SA-Announce Server:
- HTTP TCP: 80
- Real-Time Protocol (RTP) UDP: 20480-32767
- Multicast Real-Time Protocol (RTP) UDP: 20480-32767
- From Internet Explorer, navigate to Tools > Internet Options > Connections > LAN Settings.
- Verify that a proxy server is not enabled.
- Test the group.
Verify G.711 Audio
- From CUCM, navigate to Device> Phone.
- Search for the directory number of the paging group.
- Click on the device name and note the Device Pool name.
- Navigate to System > Device Pool.
- Find the Device Pool from step 4 and note the Region.
- Navigate to System > Region.
- Click on the Region name from step 5.
- Verify that the paging group's region uses a G.711 codec to any other region that may be calling the group.
- Test the group.