[cisco-voip] BRI interfaces - Grouping?

[Mike Hawley (AU)]

Use "trunkgroup" command, and prioritize the physical interfaces within the group.  Then all you need to do is reference the group within the "Dial-Peers"

Mike

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Johnny Crothers
Sent: Monday, 17 March 2008 9:18 AM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] BRI interfaces - Grouping?

Hi all,

I'm wandering if anyone has any idea's on this one?

If I was to have 3x2 port BRI interfaces, would there be anyway I can group these? So that when I configure my dial peer I only specify the "Group" rather than having to create individual dial peers with different preferences for each of the BRI cards?

For example:

BRI Configuration - points to 1 specific BRI interface

dial-peer voice 1 pots

 destination-pattern 905.

 port 0/3/0

 forward-digits all

What I'm trying to achieve is the same as what is done with a PRI

dial-peer voice 2 pots

 destination-pattern 905.

 port 0/3/0:15

 forward-digits all


Anyone got any idea's? or has anyone done this before?

Cheers,
Johnny

This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

******************************************************************************
 - NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged information.  If you have received this email in error, please notify the sender and delete it immediately.

Internet communications are not secure. You should scan this message and any attachments for viruses.  Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.
******************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080317/f95c1c9a/attachment.html