<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
30 should be fine, just account for the extra call load on that
subscriber. 1 call to that line generates 30 BHCA, a nice multiplier.<br>
<br>
for:<br>
phone1 registered to cluster1cm1<br>
phone2-32 registered to cluster1cm2 all with shared line<br>
<br>
phone1 sends call to cluster1cm1. cluster1cm1 sends a single
CcSetupReq over CM SDL link to cluster1cm2. cluster1cm2 handles all of
the signaling for phone2-32 and the shared line.<br>
<br>
You have to be careful when phones with shared lines register to
different nodes within a cluster. Make sure all of the phones for this
site with this shared line register to this specific cm.<br>
<br>
<br>
for thoroughness:<br>
if 2 phones share x7000<br>
p1 registers to cm1<br>
p2 registers to cm2<br>
<br>
whichever phone registers first chronologically will create the
LineControl process for x7000. All calls for that line going forward
will be processed on that node.<br>
<br>
example:<br>
p1 registers to cm1<br>
-> LC created on cm1<br>
p2 registers to cm2<br>
-> LC still on cm1<br>
p1 fails over to cm2<br>
-> LC still on cm1<br>
network goes down for 3 minutes and both phones unregister<br>
-> LC shutdown<br>
p2 registers to cm2<br>
-> LC created on cm2<br>
<br>
This is why TAC asks for CM SDI/SDL traces from ALL NODES.<br>
<br>
Regards,<br>
Wes<br>
<br>
On Tuesday, March 10, 2009 9:53:17 AM, Joe Pollere (US)
<a class="moz-txt-link-rfc2396E" href="mailto:Joe.Pollere@us.didata.com"><Joe.Pollere@us.didata.com></a> wrote:<br>
<blockquote
cite="mid:C65033A817B5734392E55CB9DF44610417618842@USNAEXCH.na.didata.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;
color:black;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thanks
Wes. This is a remote MAN
attached site with its own subscriber using SCCP. Question - if a call
is
initiated from a phone registered to a subscriber at the central site
to a
shared line on a phone registered to the subscriber at the remote site
does the
call setup get initiated at the remote subscriber for the shared lines
or from
the central site subscriber? (hope that makes sense)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> I think
the max count of phones
with a Shared DN is about 30. I have already suggested Broadcast Hunt
groups as
an alternative but was interested in knowing the recommended MAX if
that was
not acceptable to the client.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Joe<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>] <br>
<b>Sent:</b> Tuesday, March 10, 2009 9:21 AM<br>
<b>To:</b> Joe Pollere (US)<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Max Shared Line Appearances<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CM will ring *many* instances of a shared line.
I
believe common testing caps around 100 instances of a shared line.
However, that certainly adds extra load to the system. Is that many
shared lines really the best design? Review carefully to see if
similar
can be delivered through other features such as linegroups and call
park.<br>
<br>
They way you say "site" makes me think these may be a remote
site. Concurrent signalling to large groups of phones may cause
contention in your priority queues for call signaling. This is
overcome
by a combination of (protocol, message bundling, and link speed).<br>
<br>
Protocol - SCCP is essentially a binary protocol so signaling requires
minimal
number of bits on the wire. SIP is text based and requires more bits
by
several orders of magnitude. Use SCCP if possible.<br>
message bundling - CM service parameter to buffer SCCP messages for a
few msec
so that multiple SCCP messages can be placed in the same TCP segment
which
increases efficiency as fewer TCP headers are passed<br>
link speed - in the end its about how fast you can push bits through
the
single-file-line of the interface<br>
<br>
There is good information in the SRND about this:<br>
<a moz-do-not-send="true"
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/netstruc.html#wpmkr1045581">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/netstruc.html#wpmkr1045581</a><br>
<br>
/Wes<br>
<br>
On Tuesday, March 10, 2009 7:13:58 AM, Joe Pollere (US) <a
moz-do-not-send="true" href="mailto:Joe.Pollere@us.didata.com"><Joe.Pollere@us.didata.com></a>
wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoPlainText">We are in the process of converting a Nortel
PBX over to
UCM 6.1.3 and they have a few dns that are shared amongst many phones.
I
remember reading somewhere that there was a recommended maximum number
of
shared lines you could have configured with the same dn. Does anyone
know what
that recommendation is. These would all be within the same site using
7961's.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText">Thanks,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText">Joe<o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<div class="MsoNormal" style="text-align: center;" align="center"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">
<hr align="center" size="1" width="100%"></span></div>
<p><strong>Disclaimer: This e-mail communication and any attachments
may
contain confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee,
you are hereby notified that you have received this communication in
error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication
in
error, please notify us immediately by replying to this message and
deleting it
from your computer. Thank you. </strong><o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre style="text-align: center;">
<hr align="center" size="4" width="90%">
</pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>cisco-voip mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><o:p> </o:p></span></p>
</div>
<hr size="1">
<p><strong>Disclaimer:
This e-mail communication and any attachments may contain confidential
and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to
this message and deleting it from your computer. Thank you.
</strong></p>
</blockquote>
<br>
</body>
</html>