[cisco-voip] What is wrong with my destination pattern?

[Nick Matthews]

The T in destination patterns works like this:

if you're dialing digit-by-digit from an FXS port or on speakerphone
from an IP phone, it will check every dial peer each digit.  If it
matches a dial peer, it will send it out.  Meaning, if you have ....
and ..... it will match 4 digits every time.  If you want to be able
to dial digit by digit with overlapping dial plans, your shorter dial
pattern must contain a T.

Most calls are done what's called en-bloc.  This means all the numbers
are sent as once - H323, SIP, "offhook dialing" all meet these
criteria.  In this case you can send a 5 digit number out if you have
the aforementioned 4 and 5 digit destination patterns.  If all of your
numbers are en-bloc, the T will do nothing at all.  9 and 9T are
equivalent in this scenario.

Hope that clarifies.

-nick

2010/2/2 Reynaldo Castaño <racu2000 at hotmail.com>:
> John,
>
> you have to make a little change in your dial-peer configuration, as follow:
>
> dial-peer voice 20 pots
> destination-pattern 9...............
> direct-inward-dial
> port 0/3/0:23
> forward-digits extra
>
> this way, you're telling the gateway, that all trafic beggining with 9, must
> be redirected to port 0/3/0,
>
> depending on the pattern, you can use something like this:
>
> destination-pattern 9011............
>
> hope this can help
>
>
>
>> On Tue, Feb 2, 2010 at 10:43 AM, John Lange <john at johnlange.ca> wrote:
>> > We have a Cisco connected to a PRI acting as a VOIP gateway for an
>> > Asterisk system. In our setup, we have every call arriving at the
>> > gateway that begins with "9" routed to the PRI, and everything else
>> > routed to the Asterisk server.
>> >
>> > In short, this means any number starting with "9" should be an outbound
>> > call (to the PRI), and everything else should be is an inbound call (to
>> > the Asterisk server).
>> >
>> > The problem is, any international call seems to be looping back to the
>> > Asterisk box. For example, if we dial '9011448712002000' it ends up
>> > looping back to the Asterisk server as if the Cisco is ignoring the 9.
>> >
>> > Here are the dialpeers. Pretty straight forward. What could be wrong?
>> >
>> > What commands can I use to trace the progress of a call on the console
>> > to see why the Cisco is doing this?
>> >
>> > ---
>> >
>> > dial-peer voice 20 pots
>> >  destination-pattern 9
>> >  direct-inward-dial
>> >  port 0/3/0:23
>> >  forward-digits extra
>> > !
>> > dial-peer voice 40 voip
>> > preference 1
>> > destination-pattern .
>> > session protocol sipv2
>> > session target ipv4:192.168.134.9
>> > session transport udp
>> > dtmf-relay sip-notify rtp-nte
>> > codec g711ulaw
>> > fax rate 14400
>> > fax protocol t38 ls-redundancy 2 hs-redundancy 1 fallback pass-through
>> > g711ulaw
>> > no vad
>> >
>> > ---
>> >
>> >
>> > --
>> > John Lange
>> > http://www.johnlange.ca
>> >
>> > _______________________________________________
>> > cisco-voip mailing list
>> > cisco-voip at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>> >
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________
> Hotmail: Free, trusted and rich email service. Get it now.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>