[cisco-voip] CCME Speed Dials and COR
Jonathan Charles
jonvoip at gmail.com
Sun Mar 18 10:38:46 EST 2007
The problem here is that I have a ridiculous number of speed dials (33
global and 150+ per site)... and since we have nearly 1000 sites to deploy,
this will create a nightmare configuration per site (the goal is to have one
config for all sites and then use the localized speed-dials as a csv).
Jonathan
On 3/17/07, Paul Choi <asobihoudai at yahoo.com> wrote:
>
> Ah HA!
>
> I have discovered by RTFM'ing that if you stick local
> directory entries underneath telephony-service
> numbered from 31 -> 99, you can list those under
> system-wide speed dials!
>
> Quoth the CCME CLI documentation...
>
> "The Cisco CallManager Express system automatically
> creates a local phone directory consisting of the
> telephone numbers and names that are entered during
> ephone-dn configuration. Additional directory
> entries can be made by administrators using the
> directory entry command. Phone number directory
> listings are displayed in the order in which they are
> entered.
>
> A single entry can be removed using the no directory
> entry directory-tag command.
> Directory entries that have directory-tag numbers from
> 34 to 99 also can be used as systemwide
> speed-dial numbers. That is, if you have the following
> definition for the headquarters office, any phone
> user can speed-dial the number:
>
> Router(config)# telephony-service
> Router(config-telephony)# directory entry 51
> 4085550123 name Headquarters
>
> Analog phone users press the asterisk (*) key and the
> speed-dial identifier (tag number) to dial a
> speed-dial number."
>
> In other words, fill in 32 speed dials using the XML
> configuration file and then fill in the speed dials
> underneath the directory entry configuration
> underneath telephony-service.
>
> I used a freakin' kludge to fill in the rest of the
> speed dials. I used the 'fastdial' command underneath
> each ephone when I should have used directory entry
> instead. Argh!
>
> --- Jonathan Charles <jonvoip at gmail.com> wrote:
>
> > The downside is it is 33 numbers system-wide then
> > another 150 per site (870+
> > sites).
> >
> > I am thinking to change the speed dials to have a
> > ridiculous numerical
> > string in front of them (for example
> > 4891487104718907331..........) and then
> > use a destination-pattern for that string and drop
> > the ridiculous numerical
> > string...
> >
> >
> >
> > Jonathan
> >
> > On 3/17/07, Paul Choi <asobihoudai at yahoo.com> wrote:
> > >
> > > I see one way of blocking LD dialing while
> > allowing
> > > XML speeddials would be to use outbound
> > translation
> > > patterns. This might be very kludgy but you could
> > be
> > > very specific on your dial-peers of which 32
> > numbers
> > > you'd like to permit system-wide.
> > >
> > > After glancing at the CCME documentation, I do not
> > see
> > > any FAC support unfortunately.
> > >
> > > --- Jonathan Charles <jonvoip at gmail.com> wrote:
> > >
> > > > Got a customer, wants to block all LD dialing,
> > > > unless it is a speed-dial in
> > > > an XML for CCME...
> > > >
> > > > How do we do that?
> > > >
> > > > Also, he wants to implement Facility Access
> > Codes so
> > > > that users can be
> > > > prompted to dial a digit string to dial LD...
> > > >
> > > > Any way to do that on CCME?
> > > >
> > > >
> > > >
> > > >
> > > > Jonathan
> > > > >
>
>
>
>
>
> ____________________________________________________________________________________
> No need to miss a message. Get email on-the-go
> with Yahoo! Mail for Mobile. Get started.
> http://mobile.yahoo.com/mail
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070318/f004b460/attachment-0001.html
More information about the cisco-voip
mailing list