[cisco-voip] Manipulate Caller ID CUCM 6.1

Damian Turburville d_turburville at yahoo.com
Mon Apr 4 05:16:25 EDT 2011


Wes,
Ok sounds good, when you say parameter, do you mean something on the Hunt Pilot 
page or is it an actual System or Enterprise parameter?
Thanks,
Damian




________________________________
From: Wes Sisk <wsisk at cisco.com>
To: Damian Turburville <d_turburville at yahoo.com>
Cc: Nate VanMaren <VanMarenNP at ldschurch.org>; Jason Aarons (US) 
<jason.aarons at us.didata.com>; "cisco-voip at puck.nether.net" 
<cisco-voip at puck.nether.net>
Sent: Tue, March 29, 2011 4:43:45 PM
Subject: Re: [cisco-voip] Manipulate Caller ID CUCM 6.1

In CM this can be done with hunt pilot / hunt list / line group.      There is a 
parameter to display the ID associated with the pilot     rather than the actual 
caller id.

Regards,
Wes

On 3/29/2011 11:22 AM, Damian Turburville wrote: 
Wow that looks complicated :-) I havent         explored TCL scripting but it 
looks interesting. For the sake of         simplicity however is there no way to 
do this name presentation         within the CUCM itself?
>
>Thanks,
>Damian
>
>
>
>
________________________________
From: Nate VanMaren <VanMarenNP at ldschurch.org>
>To: Jason               Aarons (US) <jason.aarons at us.didata.com>; Damian               
>Turburville <d_turburville at yahoo.com>; "cisco-voip at puck.nether.net" 
><cisco-voip at puck.nether.net>
>Sent: Tue,               March 29, 2011 3:34:27 PM
>Subject: RE: [cisco-voip] Manipulate Caller ID CUCM 6.1
>
> 
> 
>Here you go:
> 
>Implement a TCL script with the                   following.
>Make a file on the route called                   “drup” that is formatted 
>number~name like
>~No Caller ID
>20001~SWITCH ROOM CELL PHONE
>20002~CAR SALES MESSAGE
> 
>Make an app like:
> 
>application
>  service modify_name                   flash:modify_caller_name.tcl
> 
>dial-peer voice 1 pots
>incoming called-number .
>direct-inward-dial
>service modify_name
> 
>This TCL script was given to me by                   a guy at Cisco.  I hacked 
>it to load a file to look                   for caller id.  I don’t remember if 
>it still does but                   it used to match prefixes of numbers to show 
>the name.
> 
># modify_caller_name.tcl
># Script Version 1.0(1)
>#------------------------------------------------------------------ 
># March 2003, Niels Brunsgaard
># 
># Copyright (c) 1998-2002 by cisco                   Systems, Inc. 
># All rights reserved. 
>#------------------------------------------------------------------ 
>######debug voip application script 
># This tcl script changes the                   calling display name to a value 
>that depends on the                   calling number. # 
>
> 
>proc init { } { 
>    global param 
>} 
> 
>proc NameLookup {ani} {
>        puts "Finding name for                   $ani"
>  set dave ""
>  if { [catch {open drup r}                    NameFile] } {
>    puts  "Could not open drup"
>    } elseif  {
>    [regexp -line $ani~.*$ [read                   $NameFile] fred] == 1} {
>    set dave [string trimleft $fred                   $ani~]}
>  puts "Found name $dave for $ani"
>        catch {close $NameFile}
>return $dave
>}
> 
> 
>proc act_Setup { } { 
>    
>    leg setupack leg_incoming 
> 
>    set dnis [infotag get leg_dnis]
>    set ani [infotag get leg_ani]
>    set display_name_orig [infotag                   get leg_display_info]
>    set anipi [infotag get                   leg_ani_pi]
>    set anisi [infotag get                   leg_ani_si]
>    puts "dnis: $dnis ani: $ani                   pi:$anipi si:$anisi name: 
>$display_name_orig"
> 
>    set display_name [NameLookup                   $ani]
>    if {$display_name == "No Caller                   ID"} {puts "No name found, 
>not changing."} else {
>    
>    set callInfo(displayInfo)                   [string trim [concat 
>$display_name                   $display_name_orig]]}
>                puts "Changed Name                   to $display_name 
>$display_name_orig for $ani"
>    leg proceeding leg_incoming
>    leg setup $dnis callInfo                   leg_incoming
>} 
> 
>proc act_CallSetupDone { } { 
>    global beep 
>  
>    set status [infotag get                   evt_status] 
>  
>    puts "Entering                   act_CallSetupDone"
>    if { $status != "ls_000"} { 
>        puts "Call [infotag get                   con_all] got event $status 
>while placing an outgoing                   call" 
>
>        call close           
>    } 
>} 
> 
>proc act_Cleanup { } { 
>    puts "Entering act_Cleanup"
>    call close 
>} 
> 
>proc act_Abort { } { 
>    puts "Unexpected event -                   entering act_Abort"
>    call close 
>} 
> 
>init
>  
>#---------------------------------- 
>#   State Machine 
>#---------------------------------- 
>  set                   TopFSM(any_state,ev_disconnected)                   
>"act_Abort,same_state" 
>
>  set                   TopFSM(CALL_INIT,ev_setup_indication)                   
>"act_Setup,PLACECALL" 
>
>  set                   TopFSM(PLACECALL,ev_setup_done)                    
>"act_CallSetupDone,CALLACTIVE" 
>
>  set                   TopFSM(CALLACTIVE,ev_disconnected)                     
>"act_Cleanup,CALLDISCONNECTED" 
>
>  set                   TopFSM(CALLDISCONNECTED,ev_disconnect_done)                   
>"act_Cleanup,same_state" 
>
> 
>  fsm define TopFSM  CALL_INIT 
> 
> 
> 
> 
>From:cisco-voip-bounces at puck.nether.net 
>[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (US)
>Sent: Tuesday, March 29, 2011 7:46 AM
>To: Damian Turburville; cisco-voip at puck.nether.net
>Subject: Re: [cisco-voip] Manipulate Caller                       ID CUCM 6.1
> 
>I wonder if you can use a IOS                   Translation Profile at the 
>Gateway to modify called                   party name.  What type of 
>gateway/protocol/ios version                   are you running?
> 
>From:cisco-voip-bounces at puck.nether.net 
>[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Damian Turburville
>Sent: Tuesday, March 29, 2011 9:43 AM
>To: cisco-voip at puck.nether.net
>Subject: [cisco-voip] Manipulate Caller ID                       CUCM 6.1
> 
>Hi guys,
>We have a customer who wants to have a text string                     come up 
>on their phone based upon the number dialled                     by the outside 
>party. i.e. if a member of the public                     dialled 01234 567890 
>which would come into our CUCM                     6.1 box they would want it to 
>display "Slough" for                     instance or if they dialled 01234 
>567891 it would                     come up as "Chichester"
>This is basically for a group of users who will be                     taking 
>calls from many geographic locations and want                     to be able to 
>know which line the public is dialling                     in from.
>
>(The actual setup is as follows)
>
>Public dials 0845 number
>0845 number is forwarded by BT onto a DDI number                     (01234 
>567890)
>DDI number comes into our CUCM 6.1 system via MGCP                     gateway
>Call goes to a CTI Route Point which forwards onto                     Unity 
>Connection 7 Call Handler
>Call Handler announces "Welcome to the Slough                     Helpline you 
>will now be placed in a queue"
>Call is transferred (release to switch) to an                     Attendant 
>console Pilot Point (so we can queue                     calls)
>Pilot point addresses four 7942 phones in a circular                     
pattern
>User expects to see "Slough" come up as the Caller                     ID
>
>The same would happen for the other geographic                     regions but 
>the call would come in via a different                     DDI number eg : 01234 
>567891
>
>Is this possible?
>Thanks,
>Damian
> 
>
________________________________
 
>Disclaimer: This e-mail communication and any                   attachments may 
>contain confidential and privileged                   information and is for use 
>by the designated                   addressee(s) named above only. If you are 
>not the                   intended addressee, you are hereby notified that you                   
>have received this communication in error and that any                   use or 
>reproduction of this email or its contents is                   strictly 
>prohibited and may be unlawful. If you have                   received this 
>communication in error, please notify us                   immediately by 
>replying to this message and deleting                   it from your computer. 
>Thank you. 
>
>
>
>NOTICE: This email message is for the sole use of                     the 
>intended recipient(s) and may contain                     confidential and 
>privileged information. Any                     unauthorized review, use, 
>disclosure or distribution                     is prohibited. If you are not the 
>intended                     recipient, please contact the sender by reply email                     
>and destroy all copies of the original message.
>
>
>
>This body part will be downloaded on demand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110404/9974c655/attachment.html>


More information about the cisco-voip mailing list