[cisco-voip] Mask Inbound Calling NAME on MGCP T1 CAS Trunk?

[Nick Matthews]

For those interested:

Calling Name / Number order of operations:

1.  Caller ID if enabled and available
2.  Station-id from voice-port
3.  If it matches an incoming dial peer with an explicit destination
pattern, that will be used.  This is why so many people have problems
with 911 showing as the caller ID.

-nick

On Tue, Sep 8, 2009 at 5:46 PM, Andrew Dorsett<vtadorsett at gmail.com> wrote:
> I found through some testing that setting the station-name won't take effect
> if you have inbound caller-id.  It will only apply to an interface which has
> the caller-id removed or blocked.  However, in CUCM 6.1+ you can configure
> an outbound caller name on a SIP trunk which will override any caller name
> already present on the call.  So a simple solution is to bounce the call out
> to CUBE and back via a SIP trunk.  You can then configure media flow-around
> which will prevent CUBE from being in the middle of the media stream and
> allow you to use it simply to just modify the name.
> Andrew
>
>
> On Tue, Sep 8, 2009 at 4:50 PM, Wes Sisk <wsisk at cisco.com> wrote:
>>
>> if h.323 then station-name will work.  if mgcp currently no workaround
>> without special scripting -
>>
>> special scripting - send to an IP-IVR, allow it to set the the name via
>> CTI and then redirect to true destination.
>>
>> not currently possible to rewrite name in CM.
>>
>> /Wes
>>
>> On Tuesday, September 08, 2009 4:45:05 PM , Ted Nugent
>> <tednugent73 at gmail.com> wrote:
>>
>> 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??
>> TIA
>> Ted
>>
>> ________________________________
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>