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

[John Lange]

Thanks. For outbound we can't really make it any more specific than 9,
but for inbound we could tune it a lot since we always get calls
presented with 10 digits starting with our area code.

However, I'm confused about the "T" pattern. Unless i'm mistaken, that
is for "timeout" when collecting digits. Since these are 100% SIP calls,
the entire number is always sent in one block so that makes the "T"
irrelevant. Correct?

So what we've established is that the pattern matching is not the
underlying problem (it causes the looping when the PRI rejects the call
but it's not what's causing the call to fail in the first place).

So now we're on to debugging the PRI.

If anyone has any tips for configuring a Cisco to connect to a Bell PRI
please let me know. It's working fine but we just can't dial
international calls.

Regards,

-- 
John Lange
http://www.johnlange.ca


On Tue, 2010-02-02 at 13:24 -0500, Peter Slow wrote:
> Nick was being nice. You need to set your dial peers up so that
> they're more specific so that calls can only go where you want them
> to. if all "9" calls should only go out the PRI, and you know how many
> digits  you want sent to asterisk and what they should start with, you
> should be using a pattern like [0-8]... to send calls to asterisk.
> This wont fix your initial issue, the call failing out the PRI, but it
> will save you a couple hours when you don't have to troubleshoot the
> resulting call routing loops =)
> 
> -Peter
> 
> On Tue, Feb 2, 2010 at 11:30 AM, Nick Matthews <matthnick at gmail.com> wrote:
> > debug voip ccapi inout will give you some call routing details.
> >
> > i would suggest debug isdn q931.  if it's going out isdn, isdn is
> > rejecting it, it will try the next dial peer.
> >
> > you may also want to create more specific dial peers.
> >
> > 9(011).T
> > 91..........
> > 9........
> >
> > Like that, for US numbers at least.
> >
> > -nick
> >
> > 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
> >