Workaround Call will flow through. Symptom User can not press the button configured as trunk-dn monitor to pick up the parked call. Or user cannot press the button configured as M button to speed-dial. Conditions Pressing the monitor button, no OP. Symptom Not able to configure call-forward system redirecting-expanded. Conditions Not able to configure call-forward system redirecting-expanded on a router. Symptom After a license upgrade from 48 to 64 user license on a UC, the Cisco series phone registration fails with the following errors in debug ephone register output:.
The problem only occurs when the ephone tag value for this phone registration is 56 or higher. Workaround Use an ephone tag that is of lower numerical value. Ephone 55 or lower will work. Symptom When shared line has 2 calls, and these 2 calls disconnect at the same time, the port might hang. Symptom Build failure is happening for platform images.
Conditions FXO ports are members of a huntgroup where the first member port is disconnected or down. Unconfigure max-retry. Under each port, configure "timeouts power-denial 0" so that disconnected ports are moved to offhook state and will not be hunted. Symptom CPU profiling under interrupts is not reliable.
Symptom A Cisco router reloads when trying to connect to irc. Conditions The symptom is observed only in the first 36 hours following a reload. Workaround Do not connect to irc. Conditions This happens when the CLI's parser chain was moved, hence missing them on the platforms.
Need to ensure the parser chain is implemented as platform independent. Symptom Consult transfer with third party sip endpoints results in one way audio when the third party endpoint has delayed response to resume request which includes change in rtp stream parameters i. Conditions sip supplementary services refer is disabled. Symptom IP connectivity fails for the interface following extended pings from FastEthernet interface. The show interface command will indicate that the output queue is wedged:.
No indication at this time that this is specific to these images. This problem has not yet been seen on an interface in full duplex mode. Symptom Router reloads with a bus error and no tracebacks. The installed IOS version is any Workaround There is no known workaround available.
Subsequent calls through that same channel continue to fail with "resource unavailable" cause value equal to 47 even after DSP resources have been made available to handle the call. The call must first fail with a legitimate DSP allocation error. Any call made through the same channel as the failed call will also fail. DSP allocation failures on gateway can be checked through the use of the exec command show voice dsp group all.
The last line of the show command output includes a counter for "DSP resource allocation failure". This issue can also be seen in some cases upon bootup. When a gateway is reloaded, system resources will come up with a slightly different timing.
If, for example, a PRI interface comes up before the DSP resources have fully initialized, there may be a similar failure. Workaround The workarounds are as follows:.
When the gateway comes back up, take the voice-port out of shutdown. An increase of almost 10 percent in CPU utilization is observed with every voice call. Workaround Remove the AIM compression card from the motherboard. Outbound calls to the SIP provider have one-way audio. The internal IP phone can hear the remote party, but the remote party cannot hear the internal IP phone. Conditions TNP phones with firmware 8. Workaround Wait for about a minute, and the port will automatically recover back to registered.
Symptom A call from a night hunt forwarded to BACD dial by an extension to an ephone call forwarding no answer to voicemail goes to the night hunt number and not the last redirected number.
The packets will appear as output drops on the ATM interface statistics. Under the PVC level, there are no drops. The ATM interface s need to be bridge-group configured. The bridge-group is in forwarding mode. Symptom The call-waiting tone will not be generated and the caller ID will not be displayed for the second call to a phone connected to a FXS port.
Configuring either caller-id enable or caller-id enable type 2 on the FXS voice port will trigger this issue. Workaround Configuring caller-id enable type 1 under the voice port will provide call-waiting tone. However, caller-id will not be provided for the second call.
This timer dictates how long a T1 CAS, wink-start endpoint must remain offhook before completing a wink. Failure to expire the timer will cause the c to incorrectly classify a valid wink as invalid, failing outbound calls. Conditions This can happen when there is a brief period of increased CPU usage while a call is in the process of connecting.
In other words, a small spike in CPU usage can cause the time to fail to expire, thereby causing a wink failure. This may or may not help depending on the cause of the CPU spikes. A two way conversation is then established between Phone A xxx and Phone C zzz. Then the call is disconnected. With 8. Conditions If the calls come in a PRI or FXO interface, and a user on an active call on the octoline puts the call on hold while there is an incoming call, it will automatically answer the incoming call.
Approximately 13 seconds later the second call is dropped. If the user requires to put a call on hold while a new call is coming in, they must wait until the incoming call stops ringing.
Symptom Memory fragmentation, no call accepted, no output for show run. Symptom A gateway may take an exception when receiving an inbound H call when the call is placed via ISDN overlap sending.
Symptom Symptom A video call for a 3G H. Also, in the media sent to the endpoint, the video port is set to 0 as the debug state. Symptom The dsp allocation signaling dspid command under voice-card on platform is not available. Conditions This issue is on platform alone. Symptom After upgrading to The amount of IO MEM allocated upon boot up of the router has not changed with respect to previous versions. This change in memory consumption is expected due to the integration of new features.
Conditions This defect is seen on Symptom Call is terminated after aborting the transfer attempt. Conditions This problem is observed if transfer-digit-collect is not configured or configured as new , the default. Workaround Configure transfer-digit-collect orig.
Conditions c platform with HW crypto engine. Symptom Router continuously reboots. Conditions This symptom is observed when an NME is installed on the router.
Workaround Replace or remove the NME Workaround Configure clock source line independent on all 4 DS1s. If that's not an option, downgrade to any IOS before Symptom The vlan. It has been observed that when the vlan. Customer needs to reconfigure them again after reboot. Further Problem Description : When a customer is running an image that does not store the VTP and VLAN information in the start-up configuration or the normal output of show running-config, the vlan.
The operating VTP information appears in the output of show running-config all which shows non-default and default values , indicating that the router considers the VTP information to be at default values even when there is a VTP domain name configured. Conditions Running show mrcp client session active detail or show mrcp client session active and using MRCP v2. Workaround Do not run these commands.
Conditions The problem is observed when the media server is no longer reachable from the VXML gateway. The socket connection attempt is not successful but the VXML gateway does not release the socket. With each connection attempt the socket is incremented until the max of is reached. Once the max is reached, the VXML gateway will no longer attempt to open a socket to the media server until a reload occurs. Symptom There is a delay in the propagation of interface link down state.
Link failure is detected with a huge delay once the other end of the link gets disconnected. Workaround The default keepalive period is 10 seconds and the periodic function which updates the link state change runs on the order of keepalive time, hence it takes long time to detect the link down state. If keepalive is set to 1 or 2 seconds, the time taken to detect link down is normal.
If the UC is being managed using the command line, this problem is cosmetic in nature, but if it is being managed by CCA, then the VIC module will not be detected. However, it is possible the problem may be present on other VIC modules as well.
All versions of UC software are affected. Workaround The problem may be able to be worked around in some cases by replacing the VIC module with a more recently manufactured unit.
The seized DN depends on how the auto-line is configured on the phone. Attempts at sustaining a conference or transcoding call fail, users get confused and open up TAC Service Requests. Workaround Not applicable.
Symptom Unable to configure ds1 option on snmp-server host command, ambiguous command error. Conditions router running Symptom A call is placed on hold from an IP phone. For more details, contact Cisco Corporate Compliance. This section contains information on compliance with guidelines related to RF exposure. The Cisco products are designed to comply with the following national and international standards on Human Exposure to Radio Frequencies:.
To ensure compliance with various national and international Electromagnetic Field EMF standards, the system should only be operated with Cisco approved antennas and accessories.
The series device includes a radio transmitter and receiver. It is designed not to exceed the limits for exposure to radio waves radio frequency electromagnetic fields recommended by international guidelines.
The guidelines were developed by an independent scientific organization ICNIRP and include a substantial safety margin designed to ensure the safety of all persons, regardless of age and health. As such the systems are designed to be operated as to avoid contact with the antennas by the end user. It is recommended to set the system in a location where the antennas can remain at least a minimum distance as specified from the user in accordance to the regulatory guidelines which are designed to reduce the overall exposure of the user or operator.
The World Health Organization has stated that present scientific information does not indicate the need for any special precautions for the use of wireless devices. They recommend that if you are interested in further reducing your exposure then you can easily do so by reorienting antennas away from the user or placing he antennas at a greater separation distance then recommended.
It is designed not to exceed the limits for exposure to radio waves radio frequency electromagnetic fields as referenced in FCC Part 1. The device has been tested and found compliant with the applicable regulations as part of the radio certification process. The US Food and Drug Administration has stated that present scientific information does not indicate the need for any special precautions for the use of wireless devices. The FCC recommends that if you are interested in further reducing your exposure then you can easily do so by reorienting antennas away from the user or placing the antennas at a greater separation distance then recommended or lowering the transmitter power output.
It is designed not to exceed the limits for exposure to radio waves radio frequency electromagnetic fields as referenced in Health Canada Safety Code 6. The guidelines include a substantial safety margin designed into the limit to ensure the safety of all persons, regardless of age and health.
Health Canada states that present scientific information does not indicate the need for any special precautions for the use of wireless devices. They recommend that if you are interested in further reducing your exposure you can easily do so by reorienting antennas away from the user, placing the antennas at a greater separation distance than recommended, or lowering the transmitter power output.
You can find additional information on the subject at the following links:. You can obtain additional information from the following organizations:. This section provides administrative rules for operating Cisco Aironet access points in Taiwan. The rules for all access points are provided in both Chinese and English. For those low-power radio-frequency devices that have already received a type-approval, companies, business units or users should not change its frequencies, increase its power or change its original features and functions.
The operation of the low-power radio-frequency devices is subject to the conditions that no harmful interference is caused to aviation safety and authorized radio station; and if interference is caused, the user must stop operating the device immediately and can't re-operate it until the harmful interference is clear.
The authorized radio station means a radio-communication service operating in accordance with the Communication Act. The operation of the low-power radio-frequency devices is subject to the interference caused by the operation of an authorized radio station, by another intentional or unintentional radiator, by industrial, scientific and medical ISM equipment, or by an incidental radiator.
Low-power Radio-frequency Devices Technical Specifications. Within the 5. The U-NII devices shall accept any interference from legal communications and shall not interfere the legal communications. If interference is caused, the user must stop operating the device immediately and can't re-operate it until the harmful interference is clear. Manufacturers of U-NII devices are responsible for ensuring frequency stability such that an emission is maintained within the band of operation under all conditions of normal operation as specified in the user manual.
This section contains special information for operation of Cisco Aironet access points in Brazil. This equipment is not entitled to the protection from harmful interference and may not cause interference with duly authorized systems. Cisco Bug Search Tool BST is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software.
BST provides you with detailed defect information about your products and software. All rights reserved. To view a list of Cisco trademarks, go to this URL: www. Third-party trademarks mentioned are the property of their respective owners.
The use of the word partner does not imply a partnership relationship between Cisco and any other company. Skip to content Skip to search Skip to footer. Available Languages. Download Options. Updated: September 24, Antennas and Radios The series access point contains a dedicated 5 GHz radio and a flexible radio that can be configured as a 2. Internal Antennas The I has 12 cross polarized internal antennas.
External Antennas The E model is configured with up to four external dual-band dipole antennas, and two 2. Safety Instructions Translated versions of the following safety warnings are provided in the translated safety warnings document that is shipped with your access point. Unpacking To unpack the access point, follow these steps: Unpack and remove the access point and the accessory kit from the shipping box. Return any packing material to the shipping container and save it for future use.
Verify that you have received the items listed below. If any item is missing or damaged, contact your Cisco representative or reseller for instructions. Face of the E Model. Ports and Connectors on the Head of the E Model. Ports and Connectors on the Head of the I Model.
Preparing the AP for Installation Before you mount and deploy your access point, we recommend that you perform a site survey or use the site planning tool to determine the best location to install your access point.
Performing a Pre-Installation Configuration The following procedures ensure that your access point installation and initial operation go as expected.
Pre-Installation Configuration Setup. Configure the switch to which your access point is to attach. Set the Cisco wireless LAN controller as the master so that new access points always join with it.
Make sure DHCP is enabled on the network. Mounting and Grounding the Access Point Cisco Aironet series access points can be mounted in several configurations — on a suspended ceiling, on a hard ceiling or wall, on an electrical or network box, and above a suspended ceiling.
Mount the AP using no less than four screw holes on a bracket. Locking the AP to the Bracket. Deploying the Access Point on the Wireless Network After you have mounted the access point, follow these steps to deploy it on the wireless network: Connect and power up the access point.
When you power up the access point, it begins a power-up sequence that you can verify by observing the access point LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks sequentially green, red, and off. When the access point has joined a controller, the LED is chirping green if no clients are associated or green if one or more clients are associated. If the LED is not on, the access point is most likely not receiving power.
If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary, secondary, and tertiary Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN controller, and be sure the access point and the Cisco wireless LAN controller are either on the same subnet or that the access point has a route back to its primary, secondary, and tertiary Cisco wireless LAN controller.
Also, if the access point is not on the same subnet as the Cisco wireless LAN controller, be sure that there is a properly configured DHCP server on the same subnet as the access point. Create the DHCP pool, including the necessary parameters such as default router and name server.
What is a Smart Antenna connector? Smart Antenna Connector on E Model. How Does Auto-Link Aggregation work with the ? What is a ClientLink 4. How is it different from Tx-Beamforming? Can the USB port be used? Declarations of Conformity and Regulatory Information This section provides declarations of conformity and regulatory information for the Cisco Aironet Series Access Points.
You can find additional information at this URL: www. Japanese Translation. Chinese Translation. Cisco Bug Search Tool Cisco Bug Search Tool BST is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software.
Was this Document Helpful? Yes No Feedback. Conditions This is seen with the B models of the wireless routers running This issue does not affect functionality.
Conditions CME running On the with IOS This can occur if there is an ISDN Facility message received after the call connects that does not contain display name information; for example an inbound facility message for Advice of Charge AOC may trigger this problem.
These messages can be seen on the gateway through the use of debug isdn q Make sure as a minimum to disable console logging on the IOS device before enabling any debug. This issue does not have an impact to the operation or performance of the gateway nor phone. Workaround Contact the ISDN service provider to determine if the facility messages causing this problem can be disabled.
Symptom Modem connection is still active on exit. Conditions After "exit" from modem session. Symptom dtmf stop working if using connection plar opx immediate on fxo port. Conditions Cu is running XW on uc Workaround Don't use "immediate" option for the "connection plar opx". Symptom System crashes when there are clients trying to associate with AP. Conditions When AAA authentication fails with mis-configuration in the system or the wireless client's password is given wrong to try to associate.
Workaround Make sure the AAA configuration is setup correctly and the client password is configured correctly. Conditions Phone call has to be from remote phone.
Symptom Call is disconnected when another ephone is reset or unregisters. Conditions The call on the ephone-dn shared by other phone as non monitor button is disconnected if it is reset or unregisters from the CCME. Symptom After a reboot of the router, or sometimes during normal operation, an IPsec tunnel fails to initiate. Conditions The router is running Workaround A short term workaround consists of removing the access-list used in the crypto map, and then adding it again.
This will bring up the tunnel as soon as there is an interesting traffic, but the problem may occur again later. Remove the crypto map name local-address interface statement, if possible.
Downgrade to a release earlier then Instead it sends a BYE and the call gets disconnected. Workaround To work around this problem, reload the device manually after restoring the configuration file.
This vulnerability affects several Cisco products that have support for wired or wireless EAP implementations. Disable MOH from flash that implies tone on hold or beep on hold.
Debug ephone detail will show the following error:. Workaround Reboot the phone. Symptom DTMF levels are 0. Conditions This causes under normal conditions.
Workaround Setting the cptone on the voice port to Singapore cures the problem. When this problem occurs, the tone remote control functionality does not work and voice becomes distorted due to the codec mismatch.
Conditions A SIP call consistently uses the incorrect codec type from the "voice class codec" configuration. It should use the value that is configured for "codec preference 1," instead it uses the value that is configured for the "codec preference 2" setting. This issue occurs when the following configuration is used:.
Conditions The problem can be seen for every call. Symptom SCCP messages are delayed by a few seconds for secure calls, this could effect secure dspfarm secure analog endpoints. Conditions Using secure dspfarm or analog endpoints. Workaround Resetting VC resolve issue. Symptom Router might crash when Extended ACL is applied with mixed of tcp permit statements with host and networks and this acl is applied in the class-map.
Workaround Configure permitted host statements successively and do the same for permitted networks. Symptom A Cisco router may crash due to a bus error. The crash can occur if an access-list linked to a service-policy is removed, or if a service-policy is removed on an interface.
Symptom Directory numbers that are configured in local directory of CME are not being shown in received calls directory. The number and name shows while call in ringing state but is not showing during connected state. Conditions This is seen in Inbound call. Symptom Cisco IP Phone placed on hold hears fast busy instead of tone-on-hold. Workaround This behavior was introduced in If the call is not answered, the caller is placed in the queue and hears an announcement with "all agents busy please hold " and so on.
When the script hunts again after a timeout and this time, the call is answered, it drops the call completely. All phones in the hunt group will see a display of 1 call in queue for a few seconds before clearing.
Conditions Call drops only after the 1st round of hunting. If the call is answered in the initial hunting, the call connects. Once the caller is in the queue and hears MOH, if the agent hunt member answers the call after that the call will drop. Symptom The Cisco Embedded Event Manager may hang and tie up virtual terminal vty lines if the devices host name is longer than 20 characters.
Conditions The device has a hostname configured that is longer than 20 characters. Workaround Use a hostname less than 20 characters. These vulnerabilities pertain to the following protocols or features:. Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself. Conditions This happens under any normal conditions.
If the phones are configured as SCCP endpoints, the phones will not register. Workaround This issue has been resolved. The solution is available in the release of CME 4. Conditions This symptom is observed on a Cisco router that is "fresh out of the box" and affects the following routers:. Workaround For extensive information and a workaround, see the following Field Notice:.
Overall performance of the device can deteriorate to some extent. Solution The only way to rectify this situation is to reboot the device. Cisco recommends upgrading to a fixed software release. Symptom IP phone trying to create an ad-hoc conference is dropped when pressing "Conf" softkey the second time. Conditions Must be using hardware conferencing in CME 4. The IP phone must receive a call first on on overlaid button. This initial call must come in on any DN besides the first DN configured in the "button" command in ephone configuration.
A caller call a person "A". Person "A" answer the call. Person "A" is monitored by the person "B". The person "B" see on his phone that the person "A" has received a call. Also person "B" calls person "A" using the monitor button. Person "A" answers the call, putting the first caller on hold. Person "A" uses the conference softkey "Confirm". The message "Select Line" appears without any effect. Devices running Cisco IOS versions This issue is triggered by a logic error when processing extended communities on the PE device.
Workarounds that mitigate this vulnerability are available. Conditions If another call is dropped during trunk dialing, the DN for this terminated call would move to seized state. To work around the one-way audio issue, the call needs to be transferred out and then transferred back. This workaround is not acceptable. Symptom Malformed SSL packets may cause a router to leak multiple memory blocks. Conditions This symptom is observed on a Cisco router that has the ip http secure server command enabled.
Workaround Disable the ip http secure server command. Symptom When a user configures the no telephony-service command, router crashes at running configuration generation. Conditions This symptom is highly unreproducible, but there is a potential race condition between the running configuration generation and the no telephony-service command. Symptom Non phones will not register securely to CME.
A null value in this field will allow the phones to register securely. Workaround Remove the processNodeName parameter in the capf server of the phone's cnf file. Symptom No audio heard on Caller IP phone. Workaround Yes Fallback image available. Symptom In case the platform supported number of BSSIDs is 8 then configuring any ssid which comes in the 9th to 16th order in "sh run" as "guest-mode" results in a software crash.
Conditions Voice calls should invoke a transcoder in order to see this crash. Workaround Disable "authenticate register" under "voice register global". If "authenticate register" is configured under "voice register global".
GW Stack is not processing this Request and is dropping it. Conditions CME could crash if 1 call monitoring is turned AND 2 an incoming call gets routed to any application scripts other than the Default Session. Workaround The work around is to manually disable callmon before running any non-default applications. Symptom Change CME product version from 4. Conditions This problem happens when this call requires transcoding on the IPIPGW and media transcoder high-density is configured for use.
Workaround The workaround is not to use media transcoder high-density on the dial-peers which would handle such described interconnected calls. Conditions The crash would only occur in very rare condition. Indeed the problem is difficult to reproduce. This could happen when an sccp endpoint attempts a consult transfer. Use this release note with the documents and websites in this release note and the documents listed in the following sections:.
The following documents are specific to Release Hardware installation guides, configuration and command reference guides, and additional documents specific to the Cisco series routers are at. Each module in the Cisco IOS documentation set consists of one or more configuration guides and one or more corresponding command references.
Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information.
Use each configuration guide with its corresponding command reference. Select your release and click the command references, configuration guides, or any other Cisco IOS documentation you need. First Released: May 4, Last Revised: August 12,
0コメント