[cisco-voip] Stopping Prank Callers
Ray Burkholder
ray at oneunified.net
Tue Jan 11 14:08:21 EST 2005
Sorry, I missed the bottom of your note about about the calling vs called. And
I think you are correct: source based routing is not there. If you had
personal assistant, it has rules for that sort of thing.
Quoting Vandy Hamidi <vandy.hamidi at markettools.com>:
> I only know how to use a route pattern for routing the "CALLED NUMBER."
> I don't think it's possible to use it for routing "CALLING NUMBER"
>
> Am I missing something?
>
> -=Vandy=-
>
> -----Original Message-----
> From: Ray Burkholder [mailto:ray at oneunified.net]
> Sent: Tuesday, January 11, 2005 1:27 PM
> To: Jared Mauch
> Cc: Vandy Hamidi; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Stopping Prank Callers
>
> Why not just stick in a route pattern in Callmanager with a reject on
> it? That
> way you keep all changes visibly documented in Callmanager and can keep
> with
> the philosophy of MGCP, everything done in Callmanager.
>
> Ray.
>
> Quoting Jared Mauch <jared at puck.nether.net>:
>
> > On Tue, Jan 11, 2005 at 10:17:58AM -0800, Vandy Hamidi wrote:
> > > 2651 w/ 1mft-t1, but I'm running MGCP controlled by the Call
> Manager.
> > > Can I still block it at the IOS level?
> >
> > should be able to.
> >
> > that's our rule (number replaced) for our chicago gateway
> > for someone that was bugging us.
> >
> > we're sip, but the fact is that the call gets
> > rejected (probally at the isdn layer, haven't checked into it too
> > much) prior to being handed off to our softpbx.
> >
> > try it out, testing blocking your cell# or something like
> > that..
> >
> > - jared
> >
> > > -----Original Message-----
> > > From: Jared Mauch [mailto:jared at puck.nether.net]
> > > Sent: Tuesday, January 11, 2005 12:35 PM
> > > To: Vandy Hamidi
> > > Cc: cisco-voip at puck.nether.net
> > > Subject: Re: [cisco-voip] Stopping Prank Callers
> > >
> > > On Tue, Jan 11, 2005 at 09:09:39AM -0800, Vandy Hamidi wrote:
> > > > I have an interesting situation where one of my users is getting
> Prank
> > > > Calls from a particular number in Chicago.
> > > >
> > > >
> > > >
> > > > I'm pretty sure I can call my phone company and block that number,
> but
> > > > I'd rather do it internally.
> > > >
> > > >
> > > >
> > > > Is there a way on the Call Manager to block a call based on the
> > > Incoming
> > > > Caller-ID?
> > > >
> > >
> > > What's the gateway you're using?
> > >
> > > you can block it on the IOS device directly.
> > >
> > > eg:
> > >
> > > voice translation-rule 10
> > > rule 1 reject /3125551212/
> > >
> > > voice translation-profile call_block
> > > translate calling 10
> > >
> > > - Jared
> > >
> > > --
> > > Jared Mauch | pgp key available via finger from
> jared at puck.nether.net
> > > clue++; | http://puck.nether.net/~jared/ My statements are
> only
> > > mine.
> > >
> >
> > --
> > Jared Mauch | pgp key available via finger from jared at puck.nether.net
> > clue++; | http://puck.nether.net/~jared/ My statements are only
> mine.
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> > --
> > Scanned for viruses and dangerous content at
> > http://www.oneunified.net and is believed to be clean.
> >
> >
>
>
> --
> Ray Burkholder
> http://www.oneunified.net
> ray at oneunified.net
> 441 505 7293
>
> -------------------------------------------------
> Sent from http://www.oneunified.net via IMP: http://horde.org/imp/
>
> --
> Scanned for viruses and dangerous content at
> http://www.oneunified.net and is believed to be clean.
>
>
>
> --
> Scanned for viruses and dangerous content at
> http://www.oneunified.net and is believed to be clean.
>
>
--
Ray Burkholder
http://www.oneunified.net
ray at oneunified.net
441 505 7293
-------------------------------------------------
Sent from http://www.oneunified.net via IMP: http://horde.org/imp/
--
Scanned for viruses and dangerous content at
http://www.oneunified.net and is believed to be clean.
More information about the cisco-voip
mailing list