Re: FXO Question

Ryan,
You're correct - one dialpeer will (.T) will cover all others but we don't
actually know his environment. he may have implemented COR.
So in COR scenario, applying it to all POTS is like granual approach.

I just did it the way he had his all POTS :)

Cheers

On Thu, Oct 7, 2010 at 12:28 AM, Ryan West <rwest_at_zyedge.com> wrote:

> Frog,
>
>
>
> Youre usually spot on, but the whole idea of the trunk group in POTS is
> avoid having excess dial-peers and translation patterns. He would really
> only need:
>
>
>
> dial-peer voice 23 pots
> description Outbound Local
> destination-pattern 9T
> trunkgroup 10
>
>
>
> This would cover all the members.
>
>
>
> -ryan
>
>
>
> *From:* Radioactive Frog [mailto:pbhatkoti_at_gmail.com]
> *Sent:* Wednesday, October 06, 2010 6:09 AM
> *To:* Robert Kimble
> *Cc:* Ryan West; ccielab_at_groupstudy.com
> *Subject:* Re: FXO Question
>
>
>
> Hi Robert,
>
> I have prepared a sample config for you. There might be *Some* typo as I
> have typed it out straight off my head.
>
>
> config t
> trunk group 10 ! create trunk-group 10
>
> voice-port 0/2/0
> trunk-group 10 1 ! trunk-group member port1
>
> voice-port 0/2/1
> trunk-group 10 2 ! trunk-group member port2
>
> voice-port 0/2/2
> trunk-group 10 3 ! trunk-group member port3
>
> voice-port 0/2/3
> trunk-group 10 4 ! trunk-group member port4
>
>
> Now apply the above trunk group
> dial-peer voice 20 pots
> description Outbound Local
> preference 4
> destination-pattern 9T
> trunk-group 10
> port 0/2/0
> !
> dial-peer voice 21 pots
> description Outbound Local
> preference 3
> destination-pattern 9T
> trunk-group 10
>
> port 0/2/1
> !
> dial-peer voice 22 pots
> description Outbound Local
> preference 2
> destination-pattern 9T
> trunk-group 10
> port 0/2/2
> !
> dial-peer voice 23 pots
> description Outbound Local
> preference 1
> destination-pattern 9T
> trunk-group 10
> port 0/2/3
> !
>
> On Wed, Oct 6, 2010 at 3:15 AM, Robert Kimble <hoodooman21_at_gmail.com>
> wrote:
>
> Thanks Ryan,
>
> I went with the following:
>
> dial-peer voice 20 pots
> description Outbound Local
> preference 4
> destination-pattern 9T
> port 0/2/0
> !
> dial-peer voice 21 pots
> description Outbound Local
> preference 3
> destination-pattern 9T
> port 0/2/1
> !
> dial-peer voice 22 pots
> description Outbound Local
> preference 2
> destination-pattern 9T
> port 0/2/2
> !
> dial-peer voice 23 pots
> description Outbound Local
> preference 1
> destination-pattern 9T
> port 0/2/3
> !
>
> I appreciate the help!
>
> -Bobby
>
>
>
> On Mon, Oct 4, 2010 at 4:46 PM, Ryan West <rwest_at_zyedge.com> wrote:
>
> > Create a trunk group or set preferences and use the same destination for
> > each dial-peer.
> >
> > Sent from handheld
> >
> > On Oct 4, 2010, at 7:16 PM, "Robert Kimble" <hoodooman21_at_gmail.com>
> wrote:
> >
> > > All,
> > >
> > > I have a CCME with a vic2-4FXO card connected to 4 POTS lines. I'm
> trying
> > to
> > > configure the dial peer in a way that will let users dial 8 and have
> the
> > > call sent out of the first available POTS line. In other words if one
> is
> > > busy then CCME will send the call out of the next line.
> > >
> > > I'm sure this is relatively simple, but I'm having some trouble
> figuring
> > > this one out.
> > >
> > > Any help is much appreciated!
> > >
> > > Thanks,
> > >
> > > Bobby
> > >
> > >
> > > Blogs and organic groups at http://www.ccie.net
> > >
> > > _______________________________________________________________________
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Oct 07 2010 - 00:34:30 ART