<!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:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3086" 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]-->
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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
{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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{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]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=white>
<DIV><FONT size=2>Calling name is a strange animal. As far as I know, in the US,
calling name is delivered to the called party by the called party's provider
after doing an SS7 directory lookup. Now I'm not sure if this is bypassed if you
actually send a calling name or not.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>In Canada, it is up to the calling party to send the calling
name information.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I'm sure this is one reason why CallManager does not have a
"external calling name" field in the route patterns, etc.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>This is a shame for those of us in Canada who use PRI/Megalink
service and want only one name to be sent out. The telco's here can not program
the calling name on the service. </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>It's not as bad as not being able to forward secondary lines,
but I get strange looks from people saying we can't get outbound calling
name.</FONT></DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo." WJR<BR></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=MLinsemier@apcapital.com
href="mailto:MLinsemier@apcapital.com">Linsemier, Matthew</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> ; <A
title=CarlosOrtiz@bayviewfinancial.com
href="mailto:CarlosOrtiz@bayviewfinancial.com">CarlosOrtiz@bayviewfinancial.com</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A
title=cisco-voip-bounces@puck.nether.net
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
; <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, June 06, 2007 4:15
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] H.323 Gateway
PRI selection</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
forgot to mention CSS but I was thinking along the same lines you were.
The only issue that you may run into if you want to drop PRI’s is calling
name. It’s really easy to send whatever number you want to telco and
have them send it on (haven’t you ever accidently put in the wrong number mask
and your customers think your insurance company is Bob’s Truck Stop), but
calling name is a different story. Good luck in convincing them to add
different entries based on the number you send over one PRI even though I know
feasibly it can be done in their database.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Matt<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Lelio
Fulgenzi<BR><B>Sent:</B> Wednesday, June 06, 2007 4:08 PM<BR><B>To:</B>
CarlosOrtiz@bayviewfinancial.com<BR><B>Cc:</B>
cisco-voip-bounces@puck.nether.net;
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] H.323 Gateway
PRI selection<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">Then I would follow
Gurpinder's idea, but rather then letting the user select, use calling search
spaces so that the appropriate route pattern was automatically
selected.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">Then, each route pattern
could append a prefix that would match the appropriate
dial-peer.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">I would consider removing
call screening on the PRIs and leave it up to the dial-peers to set the
callerID. You might be able to drop the number of PRIs you
need.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt">--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo." WJR</SPAN><o:p></o:p></P></DIV>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">----- Original
Message ----- <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: #e4e4e4"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> <A
title=CarlosOrtiz@bayviewfinancial.com
href="mailto:CarlosOrtiz@bayviewfinancial.com">CarlosOrtiz@bayviewfinancial.com</A>
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">To:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> <A
title=lelio@uoguelph.ca href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A>
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Cc:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> ; <A
title=cisco-voip-bounces@puck.nether.net
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Sent:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> Wednesday, June
06, 2007 4:03 PM<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Subject:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> Re: [cisco-voip]
H.323 Gateway PRI selection<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Basically I need
3 different groups of users always to use their designated PRI's so that the
correct caller ID is presented. Think of it as 3 companies sharing
one gateway, each desginated to a PRI with that companies name and number on
it. </SPAN> <BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">In response to
the Gurpinder's post....I do not need them to select which caller id they
want to use. Each of the 3 groups will always use the same caller ID.
I had an idea similar to yours to prepend digits so that when the call
gets to the gateway I know which PRI it needs to exit from. I just want to
make sure I don't miss an easier method.</SPAN> <BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Carlos</SPAN>
<BR><BR><BR><o:p></o:p></P>
<TABLE class=MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%"
border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 40%; PADDING-TOP: 0.75pt"
vAlign=top width="40%">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">"Lelio
Fulgenzi" <lelio@uoguelph.ca></SPAN></B><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">
</SPAN><BR><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Sent by:
cisco-voip-bounces@puck.nether.net</SPAN> <o:p></o:p></P>
<P><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">06/06/2007
03:50 PM</SPAN> <o:p></o:p></P></TD>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 59%; PADDING-TOP: 0.75pt"
vAlign=top width="59%">
<TABLE class=MsoNormalTable style="WIDTH: 100%" cellPadding=0
width="100%" border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top>
<P class=MsoNormal style="TEXT-ALIGN: right" align=right><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">To</SPAN><o:p></o:p></P></TD>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'"><cisco-voip@puck.nether.net>,
<CarlosOrtiz@bayviewfinancial.com></SPAN>
<o:p></o:p></P></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top>
<P class=MsoNormal style="TEXT-ALIGN: right" align=right><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">cc</SPAN><o:p></o:p></P></TD>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top>
<P class=MsoNormal style="TEXT-ALIGN: right" align=right><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Subject</SPAN><o:p></o:p></P></TD>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Re:
[cisco-voip] H.323 Gateway PRI
selection</SPAN><o:p></o:p></P></TD></TR></TBODY></TABLE>
<P class=MsoNormal><o:p> </o:p></P>
<TABLE class=MsoNormalTable cellPadding=0 border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top></TD>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
vAlign=top></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>
<P class=MsoNormal><BR><BR><BR><SPAN style="FONT-SIZE: 10pt">Wouldn't you do
this with the dial-peers?</SPAN> <BR> <BR><SPAN
style="FONT-SIZE: 10pt">There is a caller ID config statement that you can
configure, then select the appropriate port.</SPAN> <BR> <BR><SPAN
style="FONT-SIZE: 10pt">--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo."
WJR</SPAN> <BR>----- Original Message -----
<BR><B>From:</B> <A
href="mailto:CarlosOrtiz@bayviewfinancial.com">CarlosOrtiz@bayviewfinancial.com</A>
<BR><B>To:</B> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<BR><B>Sent:</B> Wednesday, June 06, 2007 2:24 PM <BR><B>Subject:</B>
[cisco-voip] H.323 Gateway PRI selection <BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><BR>We have a new
H.323 Gateway that will have 4 PRI's. 2 PRI's will be grouped together
and present one caller ID. Each of the remaining 2 PRI's will
have their own caller ID (3 total different Caller ID's). How can you
select a specific PRI to be used so that the correct caller ID is shown
depending on which phone dials outboud? I should be able to prepend a
digit on Call Mgr to the 3 different route patterns (different partitions)
and then route the call based on the leading digit found on the H.323 GW.
I know I can do this via MGCP easily as well. Any other good
ideas or thoughts about this via H.323?</SPAN> <BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><BR>Carlos</SPAN>
<o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<TT><SPAN
style="FONT-SIZE: 10pt">_______________________________________________</SPAN></TT><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><BR><TT>cisco-voip
mailing
list</TT><BR><TT>cisco-voip@puck.nether.net</TT><BR><TT>https://puck.nether.net/mailman/listinfo/cisco-voip</TT></SPAN><o:p></o:p></P></BLOCKQUOTE></DIV>
<P><FONT face=Arial color=#808080 size=1>
<HR>
</FONT>
<P></P>
<P><FONT color=#808080><FONT face=Arial size=1>CONFIDENTIALITY
STATEMENT<BR>This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended solely for the
use of the addressee identified above. If you are not the intended recipient,
any use, disclosure, copying or distribution of this communication is
UNAUTHORIZED. Neither this information block, the typed name of the sender,
nor anything else in this message is intended to constitute an electronic
signature unless a specific statement to the contrary is included in this
message. If you have received this communication in error, please immediately
contact me and delete this communication from your computer. Thank you.</FONT>
</FONT></P>
<P><FONT color=#808080>
<HR>
</FONT>
<P></P></BLOCKQUOTE></BODY></HTML>