Unless you like calling name delivery... <br><br><div class="gmail_quote">On Mon, Mar 31, 2008 at 5:53 PM, Tim Reimers <<a href="mailto:treimers@ashevillenc.gov">treimers@ashevillenc.gov</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<br>
<p><font size="2">yeah --- sorry about that.<br>
I didn't realise you were hoping for something for MGCP as well -- thought the other guy was.<br>
<br>
H.323 ROCKS!<br>
;-)<div><div></div><div class="Wj3C7c"><br>
<br>
-----Original Message-----<br>
From: Scott Voll [<a href="mailto:svoll.voip@gmail.com" target="_blank">mailto:svoll.voip@gmail.com</a>]<br>
Sent: Mon 3/31/2008 6:24 PM<br>
To: Tim Reimers<br>
Cc: Lelio Fulgenzi; Rogers, Jeremy; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] Inbound calls<br>
<br>
the script is also H323 depended.<br>
<br>
So from MGCP it's still a no go.<br>
<br>
Scott<br>
<br>
On Mon, Mar 31, 2008 at 12:06 PM, Tim Reimers <<a href="mailto:treimers@ashevillenc.gov" target="_blank">treimers@ashevillenc.gov</a>><br>
wrote:<br>
<br>
> Yup.<br>
><br>
> There's a good (but TAC unsupported) TCL script available that's able to<br>
> read the ANI, and send all matching calls to just ONE internal destination<br>
> DID.<br>
><br>
> ------------------------------<br>
> *From:* <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<br>
> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] *On Behalf Of *Scott Voll<br>
> *Sent:* Monday, March 31, 2008 2:10 PM<br>
> *To:* Lelio Fulgenzi<br>
> *Cc:* Rogers, Jeremy; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
><br>
> *Subject:* Re: [cisco-voip] Inbound calls<br>
><br>
> yep. thus far..... unless something changed resently it can only be<br>
> done via H323 VGWs. and since the 6608 is MGCP only... your up a creek......<br>
><br>
> Might look at a CMM blade as an upgrade.<br>
><br>
> Scott<br>
><br>
> On Mon, Mar 31, 2008 at 10:51 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br>
> wrote:<br>
><br>
> > not with 6608s. i think 6608s can only support MGCP.<br>
> ><br>
> > scott v. can confirm.<br>
> ><br>
> > you need h.323 to do this sort of stuff.<br>
> ><br>
> > ----- Original Message -----<br>
> > From: "Paul" <<a href="mailto:asobihoudai@yahoo.com" target="_blank">asobihoudai@yahoo.com</a>><br>
> > To: "Rogers, Jeremy" <<a href="mailto:Jeremy.Rogers@wmg.com" target="_blank">Jeremy.Rogers@wmg.com</a>>; <<br>
> > <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
> > Sent: Monday, March 31, 2008 1:45 PM<br>
> > Subject: Re: [cisco-voip] Inbound calls<br>
> ><br>
> ><br>
> > > Jeremy<br>
> > ><br>
> > > I could be mistaken, but I think you can do it with<br>
> > > voice translation rules and profiles.<br>
> > ><br>
> > > Paul<br>
> > > --- "Rogers, Jeremy" <<a href="mailto:Jeremy.Rogers@wmg.com" target="_blank">Jeremy.Rogers@wmg.com</a>> wrote:<br>
> > ><br>
> > >> Is there any way to block inbound calls based on the<br>
> > >> ANI of the calling<br>
> > >> party? The terminating gateway is a 6608.<br>
> > >><br>
> > >><br>
> > >><br>
> > >> Jeremy Rogers<br>
> > >><br>
> > >><br>
> > >><br>
> > >> > _______________________________________________<br>
> > >> cisco-voip mailing list<br>
> > >> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> > >> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > >><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ____________________________________________________________________________________<br>
> > > Special deal for Yahoo! users & friends - No Cost. Get a month of<br>
> > > Blockbuster Total Access now<br>
> > > <a href="http://tc.deals.yahoo.com/tc/blockbuster/text3.com" target="_blank">http://tc.deals.yahoo.com/tc/blockbuster/text3.com</a><br>
> > > _______________________________________________<br>
> > > cisco-voip mailing list<br>
> > > <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > ><br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> ><br>
><br>
><br>
<br>
</div></div></font>
</p>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>