<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>The other thing I like about this is that the main number is
on the first line of the phone! If you've been working here for a long time, you
know the number, but if you are visiting, you may not know the main number. I
wish they would allow presentation characters like the ()- though, so you could
format the number nicely.</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an<BR>IP phone on a long haul 10base2
connection"
LFJ</DIV>
<BLOCKQUOTE
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=gea@ufl.edu href="mailto:gea@ufl.edu">Greg Ayoub</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=rratliff@cisco.com
href="mailto:rratliff@cisco.com">Ryan Ratliff</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <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, February 08, 2006 4:23
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] route
patterns/callerid mask/callforward</DIV>
<DIV><BR></DIV>...One solution I have found is to eliminate the "Calling Party
Transform<BR>Mask" from all route patterns. Then, I add an "External Phone
Number<BR>Mask" to each and every line on my phone. This way, when I call out
from<BR>my phone, the caller-id is correct, and calls forwarded through my
phone<BR>retain their caller-id when they go through the route pattern. This
is a<BR>serious maintenance nightmare...<BR><BR>That was our solution as
well. If you find a better one, let us know! <BR><BR>----- Original
Message ----- <BR>From: "Ryan Ratliff" <<A
href="mailto:rratliff@cisco.com">rratliff@cisco.com</A>><BR>To: "IT" <<A
href="mailto:it@cimgroup.com">it@cimgroup.com</A>><BR>Cc: <<A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>><BR>Sent:
Wednesday, February 08, 2006 3:45 PM<BR>Subject: Re: [cisco-voip] route
patterns/callerid mask/callforward<BR><BR><BR>BAT?<BR><BR>It can easily modify
your external calling party number.<BR><BR>-Ryan<BR><BR>On Feb 8, 2006, at
3:40 PM, IT wrote:<BR><BR>Here is my dilemma.<BR>All the phones in my
callmanager 4.0 setup do not have "external phone<BR>number mask" setup.
Instead, I have put the number mask in to the<BR>translation pattern for
outbound calling. For example.<BR>My extension is 4990<BR>I dial a call that
matches the 8.@ route pattern, and the call gets<BR>routed out the PRI
Gateway, and the pattern applies the "Calling Party<BR>Transform Mask" of
323860XXXX<BR>This results in the caller-id showing up as 323-860-4990.
Perfect.<BR>Now here are the problems with this solution. If I enable
callforwarding<BR>on my phone (sending them to my cellphone), the caller-id
gets messed<BR>up. Here is why:<BR>Let's say my friend at 310-833-5625 calls
me on my cisco phone. The call<BR>hits the phone, but there is a CFwdAll
set.<BR>The call forwards to 813239438833 (my cell with the outgoing prefix
of<BR>8).<BR>When the call forwards, it runs through the route pattern
8.@<BR>The call exits the PRI Gateway, and the Calling Party Transform
Mask<BR>applied is 323860XXXX.<BR>The call reaches my cellphone, and the
caller-id says 323-860-5625<BR>So, only the last 4 digits are from the
original callers phone number,<BR>and the rest are from the route pattern's
transform mask.<BR>Needless to say, this is a problem.<BR><BR>One solution I
have found is to eliminate the "Calling Party Transform<BR>Mask" from all
route patterns. Then, I add an "External Phone Number<BR>Mask" to each and
every line on my phone. This way, when I call out from<BR>my phone, the
caller-id is correct, and calls forwarded through my phone<BR>retain their
caller-id when they go through the route pattern. This is a<BR>serious
maintenance nightmare, as I would have number mask's all over<BR>the place.
However, the upside of this route, is that the 2 people in<BR>the office who
want caller-id blocked on their outbound calls can do<BR>so...(anyone know an
easier way?)<BR><BR>I know other people have had to deal with this, but I
cannot find the<BR>answer in my archives of this mailing list.<BR><BR>Have you
ever dealt with this, and do you have a solution that will<BR>allow me to keep
the number masks in the route
pattern?<BR><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">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><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">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><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">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>