[cisco-voip] AS5300 Call Routing

[Nick Matthews]

Scratch that, this is correct:


voice translation-rule 2
rule 1 /\(.*\)/ /#2\1/




On Wed, Apr 1, 2009 at 2:16 AM, Nick Matthews <matthnick at gmail.com> wrote:
> There would be two primary ways of changing the outbound dial peer
> based on an incoming port:
> 1) Something similar to the solution below, where you prefix digits to
> the dialed string inbound, match a different outgoing dial peer, and
> strip the digits off there
> 2) corlists.  Design it so that the incoming dial peer has a corlist
> defined that only matches one outgoing dial peer with a matching
> corlist.
>
> Given the choice, I'd probably go with 1.  It's easier to
> troubleshoot, and has a few less moving parts.  2 is slightly more
> graceful and gives you more options, but is confusing.  However, it
> would probably scale better.
>
> Since you're just doing this based on port, you're probably fine with
> prefixing digits
>
> It would look a something like this:
>
> voice translation-rule 1
> rule 1 /\(.*\)/ /#1\1/
>
> voice translation-profile add-1
> translate called 1
>
>
> voice translation-rule 2
> rule 1 /\(.*\)/ /#1\1/
>
> voice translation-profile add-2
> translate called 2
>
> voice translation-rule 3
> rule 1 /#.\(.*\)/ /\1/
>
> voice translation-profile strip-prefix
> translate called 3
>
>
> dial-peer voice 1 pots
> port 1/0:23
> translation-profile incoming add-1
>
> dial-peer voice 2 pots
> port 2/0:23
> translation-profile incoming add-2
>
> dial-peer voice 11 voip
> session target ipv4:1.1.1.1
> destination-pattern #1.T
> translation-profile outgoing strip-prefix
>
> dial-peer voice 21 voip
> session target ipv4:2.2.2.2
> destination-pattern #2.T
> translation-profile outgoing strip-prefix
>
>
> All calls that come in on 1/0 have a #1 prefixed, match dial peer 11,
> and prefix is stripped.  All calls from 2/0 have a 2# prefixed, match
> dial peer 21, and prefix is stripped.
>
>
> -nick
>
>
>
> On Tue, Mar 31, 2009 at 4:27 PM, Jeremy Rogers
> <Jeremy.Rogers at ip-soft.net> wrote:
>> Thanks.  I am looking to to this on a Voip dial peer for the outbound leg to a SIP gateway.  They require DNIS info for their internal routing so I don't see a way to say "anything coming from port 1/0:13 go to x IP address".
>>
>> Jeremy Rogers
>> Network Management
>> IPsoft, Inc.
>> Jeremy.Rogers at ip-soft.net
>> Phone: 888.IPSOFT8
>> http://www.ipsoft.com
>>
>>
>>
>> -----Original Message-----
>> From: Alex Balashov [mailto:abalashov at evaristesys.com]
>> Sent: Tuesday, March 31, 2009 4:27 PM
>> To: Jeremy Rogers
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] AS5300 Call Routing
>>
>> It is possible to apply a translation-profile to a voice-port.  From
>> there, you can add a prefix that can be matched by an outgoing dial-peer
>> and stripped off.
>>
>> Jeremy Rogers wrote:
>>
>>> Hi,
>>>
>>> I have a customer who is looking to see if they can change an incoming
>>> Voip dial peer on an AS5350 to route based on the source port instead of
>>> a dial string.  I don't believe there is but was wondering if anyone had
>>> come up with a way to do this.
>>>
>>> They have a lot of numbers coming the ports and as it stands, every time
>>> a new number is provisioned we need to create a new dial peer.  They are
>>> looking to get away from this if possible.  Has anyone done this?
>>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Jeremy Rogers
>>>
>>> Network Management
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> --
>> Alex Balashov
>> Evariste Systems
>> Web    : http://www.evaristesys.com/
>> Tel    : (+1) (678) 954-0670
>> Direct : (+1) (678) 954-0671
>> Mobile : (+1) (678) 237-1775
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>