[cisco-voip] route patterns/callerid mask/callforward

[Ryan Ratliff]

The calling party selection configured on the gateway will play a  
role here, but I can see where a calling party modification on the  
route pattern would change it.

-Ryan

On Feb 8, 2006, at 3:50 PM, Lelio Fulgenzi wrote:

So you're saying that if I forward my phone offcampus to a phone that  
has call display, what I see on the other side depends on whether I  
use the phones external calling mask or the route pattern mask? I  
don't use wildcards, I simply populate the field with our main  
number. If I have the external mask set per phone, I will see the  
original caller's number, but if I use the mask on the RP I will see  
my main number?

------------------------------------------------------------------------ 
--------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more  
jitter than an
IP phone on a long haul 10base2  
connection"                                           LFJ
----- Original Message -----
From: IT
To: cisco-voip at puck.nether.net
Sent: Wednesday, February 08, 2006 3:40 PM
Subject: [cisco-voip] route patterns/callerid mask/callforward

Here is my dilemma.
All the phones in my callmanager 4.0 setup do not have "external phone
number mask" setup.  Instead, I have put the number mask in to the
translation pattern for outbound calling. For example.
My extension is 4990
I dial a call that matches the 8.@ route pattern, and the call gets
routed out the PRI Gateway, and the pattern applies the "Calling Party
Transform Mask" of 323860XXXX
This results in the caller-id showing up as 323-860-4990. Perfect.
Now here are the problems with this solution. If I enable callforwarding
on my phone (sending them to my cellphone), the caller-id gets messed
up. Here is why:
Let's say my friend at 310-833-5625 calls me on my cisco phone. The call
hits the phone, but there is a CFwdAll set.
The call forwards to 813239438833 (my cell with the outgoing prefix of
8).
When the call forwards, it runs through the route pattern 8.@
The call exits the PRI Gateway, and the Calling Party Transform Mask
applied is 323860XXXX.
The call reaches my cellphone, and the caller-id says 323-860-5625
So, only the last 4 digits are from the original callers phone number,
and the rest are from the route pattern's transform mask.
Needless to say, this is a problem.

One solution I have found is to eliminate the "Calling Party Transform
Mask" from all route patterns. Then, I add an "External Phone Number
Mask" to each and every line on my phone. This way, when I call out from
my phone, the caller-id is correct, and calls forwarded through my phone
retain their caller-id when they go through the route pattern. This is a
serious maintenance nightmare, as I would have number mask's all over
the place. However, the upside of this route, is that the 2 people in
the office who want caller-id blocked on their outbound calls can do
so...(anyone know an easier way?)

I know other people have had to deal with this, but I cannot find the
answer in my archives of this mailing list.

Have you ever dealt with this, and do you have a solution that will
allow me to keep the number masks in the route pattern?

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip