From: John Underhill (stepnwlf@magma.ca)
Date: Wed Nov 26 2003 - 13:08:27 GMT-3
A multilink interface is used to bundle circuits together for their
aggregated bandwidth under a virtual interface, for example combining
several T1s in a multilink group. As it applies to Voice and QOS, a
multilink interface supports packet fragmentation and interleaving, and a
qos structure can be employed to avoid serialization delays and assign real
time traffic to the appropriate priority queues.
----- Original Message -----
From: "iwan" <iwan@i-lusion.nl>
To: <ccielab@groupstudy.com>
Sent: Wednesday, November 26, 2003 6:38 AM
Subject: Warm-up e-book Section 1 question 15//Configuring Low Latency
Queing//But why use a Multilink interface???
> Hi group,
>
> I small question here...
>
> Can someone tell me what the benefit is for the multilink interface
> here...?
>
> I never configured any multilink interface...and I really don't know
> where it can be used for...
>
> And is there a possibility that this question also can be configured
> without a multilink interface?
> And why is this good or bad?
>
> Thanks,
>
> Iwan Hoogendoorn
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> William Chen
> Sent: woensdag 26 november 2003 8:15
> To: Jason Viera
> Cc: ccielab@groupstudy.com
> Subject: Re: Dial Peer Hunt Group
>
> Hi,
>
> No matter there is the huntstop command or not, the call always reach
> 192.168.1.7. It is supposed that I set the call to 192.168.1.10 the
> lowest preference value, the call will be routed to 192.168.1.10, but
> the fact is it always routed to the first dial-peer in the configuration
> file.
>
> Moreover, the huntstop command I put on the dial-peer 30 is that I
> suppose the call will select peer 30 and if so, I disable the hunt of
> that dial peer and the call should not continue to try dial-peer 20 and
> then failed.
>
> Actually, I tried the hunt group with POTS dial peer and it works
> find. However, the hunt group seems don't work with VOIP dial peer as
> expected. I just wonder how well the "csim start" command can simulate a
> real call. Maybe if I have a real telephone plug into the router, it
> will work as I expected.
>
> --- William
>
> >
> > 1H%s*L: "Jason Viera" <jasonviera@avenuecable.com>
> > $i4A: 2003/11/26 ,P4A$T $U$H 03:03:37 GMT+08:00
> > &,%s*L: "William Chen" <kwchen@netvigator.com>
> > 0F%;: <ccielab@groupstudy.com>
> > %D&.: Re: Dial Peer Hunt Group
> >
> > Under Dial-peer 30 you have used the "huntstop" command. I would
> assume
> > based upon what you're seeing that because the call isn't actually
> answered
> > with the csim-start command that the "huntstop" command is doing what
> it's
> > supposed to "stopping" the "hunting" feature. I could be way off, but
> wonder
> > what will happen if you remove the huntstop command, or if phones were
> > actually used and the calls answered?? Let us know.
> > Thanks
> > Jason
> >
> >
> > ----- Original Message -----
> > From: "William Chen" <kwchen@netvigator.com>
> > To: "Jason Viera" <jasonviera@avenuecable.com>
> > Cc: <ccielab@groupstudy.com>
> > Sent: Tuesday, November 25, 2003 10:47 PM
> > Subject: Dial Peer Hunt Group
> >
> >
> > Dear Group,
> >
> > Here is the setting, and testing output, I found that the dial-peer
> voice
> > 20 is always called, even it is configured with the highest preference
> > value:
> >
> > R4#sh run
> > Building configuration...
> >
> > Current configuration : 1249 bytes
> > !
> > version 12.2
> > service timestamps debug datetime msec
> > service timestamps log datetime msec
> > no service password-encryption
> > !
> > hostname R4
> > !
> > logging queue-limit 100
> > !
> > ip subnet-zero
> > !
> > !
> > !
> > ip audit notify log
> > ip audit po max-events 100
> > mpls ldp logging neighbor-changes
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > no voice hpi capture buffer
> > no voice hpi capture destination
> > !
> > !
> > mta receive maximum-recipients 0
> > !
> > !
> > !
> > !
> > interface FastEthernet0/0
> > ip address 192.168.1.4 255.255.255.0
> > duplex auto
> > speed auto
> > !
> > interface Serial0/0
> > no ip address
> > shutdown
> > no fair-queue
> > !
> > interface FastEthernet0/1
> > no ip address
> > shutdown
> > duplex auto
> > speed auto
> > !
> > interface Serial0/1
> > no ip address
> > shutdown
> > !
> > ip http server
> > no ip http secure-server
> > ip classless
> > !
> > !
> > !
> > !
> > !
> > call rsvp-sync
> > !
> > voice-port 1/0/0
> > !
> > voice-port 1/0/1
> > !
> > !
> > mgcp profile default
> > !
> > !
> > !
> > dial-peer cor custom
> > !
> > !
> > !
> > dial-peer voice 10 pots
> > destination-pattern 4444
> > port 1/0/0
> > !
> > dial-peer voice 20 voip
> > preference 5
> > destination-pattern 7777
> > session target ipv4:192.168.1.7
> > !
> > dial-peer voice 30 voip
> > huntstop
> > preference 4
> > destination-pattern 7777
> > session target ipv4:192.168.1.10
> > !
> > dial-peer voice 40 pots
> > preference 8
> > destination-pattern 7777
> > port 1/0/1
> > !
> > !
> > !
> > line con 0
> > line aux 0
> > line vty 0 4
> > !
> > !
> > end
> >
> > R4#debug dialpeer
> > dialpeer detailed info debugging is on
> > R4#csim start 7777
> > csim: called number = 7777, loop count = 1 ping count = 0
> >
> > *Mar 1 00:16:33.123: Inside dpMatchCore:
> > *Mar 1 00:16:33.123: destination pattn: 7777 expanded string: 7777
> > *Mar 1 00:16:33.123: MatchNextPeer: Peer 20 matched
> > *Mar 1 00:16:33.123: MatchNextPeer: Peer 30 matched
> > *Mar 1 00:16:33.123: MatchNextPeer: Peer 40 matched
> >
> > R7#sh voice port | in Oper
> > Operation State is UP
> > Operation State is DORMANT
> >
> > -- William
> >
> > >
> > > 1H%s*L: "Jason Viera" <jasonviera@avenuecable.com>
> > > $i4A: 2003/11/26 ,P4A$T $U$H 02:10:47 GMT+08:00
> > > &,%s*L: "William Chen" <kwchen@netvigator.com>
> > > %D&.: Re:
> > >
> > > How did you set the preference??? Please share your configuration.
> > Whichever
> > > peer has a preference of zero, which is the default, will be the
> first
> > peer
> > > preferred.
> > > Thanks Jason
> > >
> > > ----- Original Message -----
> > > From: "William Chen" <kwchen@netvigator.com>
> > > To: <ccielab@groupstudy.com>
> > > Sent: Tuesday, November 25, 2003 8:11 PM
> > >
> > >
> > > > Dear Group,
> > > >
> > > > I can't make the dial-peer hunt group works with the testing
> with
> > "csim
> > > start" command. I've configure several dial-peer with same
> > > destination-pattern" When I simulate the dialing by "csim start"
> command,
> > > the order of selecting dial-peer is according the order of the
> > configuration
> > > file but not the preference I explicity set. Any idea?
> > > >
> > > > Best Regards,
> > > > William Chen
> > > >
> > > >
> _______________________________________________________________________
> > > > Please help support GroupStudy by purchasing your study materials
> from:
> > > > http://shop.groupstudy.com
> > > >
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials
> from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:17 GMT-3