
OPERATIONAL DEFECT DATABASE
...

...
Problem: Hunting for second line/port is not done by trunkgroup if the first port is down Symptoms: Outgoing calls through the BRI fail due to the highest preference port (as per hunt-scheme) is down. Due to this problem, if the highest preference port is down, the GW will not hunt for next port.
1. BRI ports configured on GW. 2. BRI + trungroup configuration. Scenario ======== # Trunk group configured as follows trunkgroup test hunt-scheme sequential both up ! # trunkgroup is now applied on BRI serial interface 0/0/0 and 0/0/1: interface BRI0/0/0 trunk-group test ! interface BRI0/0/1 trunk-group test ! # At this point, if the interface 0/0/1 is shut, then the BRI interface 0/0/0 is not chosen for call routing itself.
Tested workarounds ============= 1. Use the following trunkgroup configuration: trunk group LOCAL-PSTN hunt-scheme round-robin both ! This way the GW will always look for a random port for the call to egress. There will be some call-failures but the call will definitely work on redial. 2. Configure separate dial-peers (without using trunk-group): dial-peer voice 1 pots port 0/0/0:0 preference 0 no huntstop ! dial-peer voice 2 pots port 0/0/0:1 preference 1 no huntstop !
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.