<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5730.11" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=265003820-04122006><FONT face=Arial
color=#0000ff size=2>In the Meridian it is easy to do, just change the
CDP (LD 87) of the DID to the RLI that is associated to the PRI group.
That is the way we do it.</FONT></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>Ryan
O'Connell<BR><B>Sent:</B> Monday, December 04, 2006 10:56 AM<BR><B>To:</B> cisco
voip<BR><B>Subject:</B> Re: [cisco-voip] Meridian Call
Routing<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Another option that may
simplify this is to use the “Vacant Number Routing” feature if supported on the
<st1:City w:st="on"><st1:place w:st="on">Meridian</st1:place></st1:City>. In
summary this feature is similar to the “default gateway” in the routing world.
Essentially any local that is not found on the <st1:City w:st="on"><st1:place
w:st="on">Meridian</st1:place></st1:City> can be simply shipped out the QSIG PRI
to CCM. CCM can then match the digits sent to DN’s in its own database or if no
match is found we can give a busy signal or alternatively send it elsewhere, ie:
Unity Call handler that tells the user that the number dialed is invalid. This
way it’s simple on both sides of the fence from a DialPlan
standpoint.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Regards<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><B><FONT face=Arial color=navy size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Ryan
O’Connell CCIE VOICE #13382<BR></SPAN></FONT></B><FONT face=Arial color=navy
size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">Network Consultant<BR>UNIS
LUMIN - Technology Based Business Solutions<BR>Phone: 888.475.0432
x290</SPAN></FONT><FONT color=navy><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=1><SPAN
style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">Mobile:
403.990.1275<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><A
title=http://www.unislumin.com/
href="http://www.unislumin.com/">roconnell@unislumin.com</A></SPAN></FONT><FONT
color=navy><SPAN style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><A
title=http://www.unislumin.com/
href="http://www.unislumin.com/">http://www.unislumin.com</A></SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=3>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Fred
Nielsen<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, December
04, 2006 10:57 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Vince
Loschiavo'; 'Mike Lay (milay)'; 'Jonathan Charles'; 'cisco voip'<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] Meridian Call
Routing</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">This is correct, we've done this
plenty, with installations up to the 5000 handset range. It eventually
will get real ugly on the Nortel end of things, but since that system is phasing
out, not a huge deal here I would think.</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-- Fred
Nielsen</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=3>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Vince
Loschiavo<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday,
December 04, 2006 9:05 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
Mike Lay (milay); Jonathan Charles; cisco voip<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] Meridian Call
Routing</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I disagree. You
can just route the DIDs you want from the Nortel to CCM over the QSIG. You
don't have to route the whole block. As you migrate one user from the
Nortel to CCM, you route his DID on the Nortel.</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=3>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Mike Lay
(milay)<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, December
04, 2006 11:33 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Jonathan
Charles; cisco voip<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B>
Re: [cisco-voip] Meridian Call Routing</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">It can be done but will
be a very ugly Route plan in CCM! I would recommend that you implement some type
of prefix in the NT & the CM until the migration is complete. After the
migration is complete the prefix will not be needed & you may return to a
more simple dial plan.</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Mike</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=3>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Jonathan
Charles<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, December
04, 2006 10:27 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> cisco
voip<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> [cisco-voip]
Meridian Call Routing</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Customer is migrating (way too slowly) from <st1:City
w:st="on"><st1:place w:st="on">Meridian</st1:place></st1:City> 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<o:p></o:p></SPAN></FONT></P></DIV>
<P><FONT face=Arial size=1>
<HR>
Privileged/Confidential Information may be contained in this message.
Disclosure to any person other than the named recipient is unauthorized.
If you are not the intended recipient, please delete all copies of this
information and kindly notify the sender by reply email. Opinions,
conclusions and other information in this message that do not relate to the
official business of UNIS LUMIN Inc. shall be understood as neither given nor
endorsed by it. UNIS LUMIN Inc. and any of its subsidiaries reserve the
right to monitor all e-mail communications through its networks. Thank
you.</FONT>
<P></P></BODY></HTML>