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.<br><br>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.
<br><br>I did notice that if I changed the "Connected Line ID Presentations" to restricted, it changed to 'unknown number' as my outdialed call...<br><br><br>Jonathan<br><br><br><div><span class="gmail_quote">
On 1/3/07, <b class="gmail_sendername">Simon, Bill</b> <<a href="mailto:bills@tns.its.psu.edu">bills@tns.its.psu.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Say I have DN 1234 forwarded to 5678. If someone internally dials 1234,<br>their display changes to the number they are forwarded to, 5678.<br><br>However if I dial my VM pilot, the pilot number stays on the screen<br>instead of displaying the DN of the VM port I am connected to.
<br><br>I'm looking for a comparison of which functions (call forwarding,<br>translation pattern, hunt list, etc.) maintain the originally-dialed<br>number on the caller's display, and which ones cause the display to change.
<br><br><br>Thanks<br>Bill<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></div><br>