Say I have DN 1234 forwarded to 5678.  If someone internally dials 1234,
their display changes to the number they are forwarded to, 5678.

However if I dial my VM pilot, the pilot number stays on the screen
instead of displaying the DN of the VM port I am connected to.

I'm looking for a comparison of which functions (call forwarding,
translation pattern, hunt list, etc.) maintain the originally-dialed
number on the caller's display, and which ones cause the display to change.


Thanks
Bill

[ Post a follow-up to this message ]

I am not sure of the technical reasons, however, the voicemail is going to a
huntgroup and the internal caller will always see the hunt pilot number as
his called number.

However, for translation patterns (and CTI Route Points that connect via a
CTI port), the called number appears as the final connected port, not the
route point.

I did notice that if I changed the "Connected Line ID Presentations" to
restricted, it changed to 'unknown number' as my outdialed call...


Jonathan


On 1/3/07, Simon, Bill <bills@tns.its.psu.edu> wrote:
>
> Say I have DN 1234 forwarded to 5678.  If someone internally dials 1234,
> their display changes to the number they are forwarded to, 5678.
>
> However if I dial my VM pilot, the pilot number stays on the screen
> instead of displaying the DN of the VM port I am connected to.
>
> I'm looking for a comparison of which functions (call forwarding,
> translation pattern, hunt list, etc.) maintain the originally-dialed
> number on the caller's display, and which ones cause the display to
> change.
>
>
> Thanks
> Bill
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

Any way to change this behavior?

We need to set up route points where the called number doesn't change on
the display of an internal IP phone, and hunt pilot/list/LG won't do the
trick.


> However, for translation patterns (and CTI Route Points that connect via
> a CTI port), the called number appears as the final connected port, not
> the route point.

[ Post a follow-up to this message ]

One more plea for help on this then I give up.  I get the feeling this
can't be done.

Imagine you are forwarding a call that is supposed to "look" internal to
an off-net location and it would be better for the user not to see where
it's going.  That's what I'm after.


Simon, Bill wrote:
> Any way to change this behavior?
>
> We need to set up route points where the called number doesn't change on
> the display of an internal IP phone, and hunt pilot/list/LG won't do the
> trick.
>
> 
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/

[ Post a follow-up to this message ]

Have you looked at the Connected Party Transformations on the hunt
pilot?  You can restrict the name and number there on both CM 4.1(3)
and 4.2.


-Ryan

On Jan 4, 2007, at 10:48 AM, Simon, Bill wrote:

One more plea for help on this then I give up.  I get the feeling this
can't be done.

Imagine you are forwarding a call that is supposed to "look" internal to
an off-net location and it would be better for the user not to see where
it's going.  That's what I'm after.


Simon, Bill wrote:
> Any way to change this behavior?
>
> We need to set up route points where the called number doesn't
> change on
> the display of an internal IP phone, and hunt pilot/list/LG won't
> do the
> trick.
>
> 
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Yes but I am not sure how to use hunt pilot for this type of thing.  I
thought you can only add local phones (DNs) to a linegroup.  We need to
add a pattern that routes off-net.

Ryan Ratliff wrote:[vbcol=seagreen]
> Have you looked at the Connected Party Transformations on the hunt
> pilot?  You can restrict the name and number there on both CM 4.1(3) and
> 4.2.
>
>
> -Ryan
>
> On Jan 4, 2007, at 10:48 AM, Simon, Bill wrote:
>
> One more plea for help on this then I give up.  I get the feeling this
> can't be done.
>
> Imagine you are forwarding a call that is supposed to "look" internal to
> an off-net location and it would be better for the user not to see where
> it's going.  That's what I'm after.
>
>
> Simon, Bill wrote: 

[ Post a follow-up to this message ]

Another options is the CM service parameter "Always Display Original
Dialed Number*".  This is global however so may be overkill.

-Ryan

On Jan 4, 2007, at 11:06 AM, Simon, Bill wrote:

Yes but I am not sure how to use hunt pilot for this type of thing.
I thought you can only add local phones (DNs) to a linegroup.  We
need to add a pattern that routes off-net.

Ryan Ratliff wrote:[vbcol=seagreen]
> Have you looked at the Connected Party Transformations on the hunt
> pilot?  You can restrict the name and number there on both CM 4.1
> (3) and 4.2.
> -Ryan
> On Jan 4, 2007, at 10:48 AM, Simon, Bill wrote:
> One more plea for help on this then I give up.  I get the feeling this
> can't be done.
> Imagine you are forwarding a call that is supposed to "look"
> internal to
> an off-net location and it would be better for the user not to see
> where
> it's going.  That's what I'm after.
> Simon, Bill wrote: 

[ Post a follow-up to this message ]

Also, if you are using IPCC to do the redirect to the pstn number you
can try routing via hunt pilot to your CTI RP.

You can't unfortunately use a dummy phone with CFA configured because
the hunt pilot will ignore CFA.  If it's a real device however this
may work.

-Ryan

On Jan 4, 2007, at 11:06 AM, Simon, Bill wrote:

Yes but I am not sure how to use hunt pilot for this type of thing.
I thought you can only add local phones (DNs) to a linegroup.  We
need to add a pattern that routes off-net.

Ryan Ratliff wrote:[vbcol=seagreen]
> Have you looked at the Connected Party Transformations on the hunt
> pilot?  You can restrict the name and number there on both CM 4.1
> (3) and 4.2.
> -Ryan
> On Jan 4, 2007, at 10:48 AM, Simon, Bill wrote:
> One more plea for help on this then I give up.  I get the feeling this
> can't be done.
> Imagine you are forwarding a call that is supposed to "look"
> internal to
> an off-net location and it would be better for the user not to see
> where
> it's going.  That's what I'm after.
> Simon, Bill wrote: 

[ Post a follow-up to this message ]

It might not be the best option but you could use a gateway

so lets say you call 4000 and you want that to ring to 888-123-45678

so in CM you setup a RP to point 4000 to a H323 gateway.  Then on the
gateway do a num-exp or a translation pattern or just change the called
number on the dial-peer.

Once the call is released to the gateway CCM will not change the number
dialed.

Craig





"Simon, Bill" <bills@tns.its.psu.edu>
Sent by: cisco-voip-bounces@puck.nether.net
01/04/2007 09:48 AM

To
Cisco Voip <cisco-voip@puck.nether.net>
cc

Subject
Re: [cisco-voip] In what cases does the dialed number change on the
calling terminal?






One more plea for help on this then I give up.  I get the feeling this
can't be done.

Imagine you are forwarding a call that is supposed to "look" internal to
an off-net location and it would be better for the user not to see where
it's going.  That's what I'm after.


Simon, Bill wrote:
> Any way to change this behavior?
>
> We need to set up route points where the called number doesn't change on

> the display of an internal IP phone, and hunt pilot/list/LG won't do the

> trick.
>
> 
via[vbcol=seagreen] 
[vbcol=seagreen] 
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Some interesting options here, mostly ugly.  I wish there were a switch
to toggle for certain entities (especially route points) that would
change this behavior.  I've got some stuff to work with now though.
Thanks folks.

Craig M Staffin wrote:
>
> It might not be the best option but you could use a gateway
>
> so lets say you call 4000 and you want that to ring to 888-123-45678
>
> so in CM you setup a RP to point 4000 to a H323 gateway.  Then on the
> gateway do a num-exp or a translation pattern or just change the called
> number on the dial-peer.
>
> Once the call is released to the gateway CCM will not change the number
> dialed.
>
> Craig
>
>
>
>
> *"Simon, Bill" <bills@tns.its.psu.edu>*
> Sent by: cisco-voip-bounces@puck.nether.net
>
> 01/04/2007 09:48 AM
>
>
> To
> 	Cisco Voip <cisco-voip@puck.nether.net>
> cc
>
> Subject
> 	Re: [cisco-voip] In what cases does the dialed number change on the
> calling terminal?
>
>
>
>
>
>
>
>
> One more plea for help on this then I give up.  I get the feeling this
> can't be done.
>
> Imagine you are forwarding a call that is supposed to "look" internal to
> an off-net location and it would be better for the user not to see where
> it's going.  That's what I'm after.
>
>
> Simon, Bill wrote: 
> via 
>
> --
> Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
> http://tns.its.psu.edu/
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/

[ Post a follow-up to this message ]