<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
if h.323 then station-name will work. if mgcp currently no workaround
without special scripting -<br>
<br>
special scripting - send to an IP-IVR, allow it to set the the name via
CTI and then redirect to true destination.<br>
<br>
not currently possible to rewrite name in CM.<br>
<br>
/Wes<br>
<br>
On Tuesday, September 08, 2009 4:45:05 PM , Ted Nugent
<a class="moz-txt-link-rfc2396E" href="mailto:tednugent73@gmail.com"><tednugent73@gmail.com></a> wrote:<br>
<blockquote
cite="mid:22e6380b0909081345u55d9a1ecp5932f4e17b6e80f5@mail.gmail.com"
type="cite">I have a client that just swung over their Corporate
Tieline from their PBX to the CallManager. There's no calling name for
inbound calls on the CAS trunk and apparently the Nortel it came off
used to mask "Corp Tieline" so that users didn't just get unknown
number or whatever on inbound calls. They are running CUCM 6.1 and I
currently have all inbound calls washed through a translation pattern
to at least mask a generic calling number on inbound calls coming
through that trunk but they really would like to have some sort of name
display. Can anyone think of a way to handle this, can you lock it in
on voiceport or something similar? It appears "station-id name" is only
used for outbound??
<div>TIA
<div>Ted<br>
<div><br>
</div>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>