<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2995" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>Yes there is a way to do this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>My customer is going very slowly on this as
well.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>The config on the Meridian: No clue as to exact
syntax: but you can point specific DIDs to your QSIG trunk to
CCM.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>CCM config: </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>1) Setup the phones and Directory Numbers as usual.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>2) Create a all inclusive route pattern to the
Nortel/Meridian; ie. 2[3-9]XX (or whatever) to the QSIG.
the CCM will only route DNs it doesn't have configured over that QSIG.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>Make sense?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006><FONT face=Arial
color=#0000ff size=2>-Vince</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=609154116-04122006></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN
class=609154116-04122006> </SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Jonathan
Charles<BR><B>Sent:</B> Monday, December 04, 2006 11:27 AM<BR><B>To:</B> cisco
voip<BR><B>Subject:</B> [cisco-voip] Meridian Call Routing<BR></FONT><BR></DIV>
<DIV></DIV>Customer is migrating (way too slowly) from Meridian to VoIP
(CallManager).<BR><BR>Customer has around 300 phones, they want to move 50
phones over to CallManager (already in place), but the phones are random (I
cannot figure out how they were picked). <BR><BR>These 100 phones are intermixed
(DID-wise, so extensions 2940-2340 are on the PBX, 2341, will be moved, 2342
will stay on the PBX, etc...) all calls come in on six PRIs, which are connected
to the Meridian... Selecting a contiguous range of DIDs is not an option.
<BR><BR>Can I route individual DIDs over a QSIG trunk to the CCM? (IOW, call
comes into PBX for x2341, gets routed over QSIG to 2851 for CCM)? Or only
blocks?<BR><BR><BR><BR>Thanx...<BR><BR><BR><BR>Jonathan<BR></BODY></HTML>