CME Intercom Lines

Intercom and Barge-IN: An intercom line is a dedicated two-way audio path between two phones. Cisco Unified CME supports intercom functionality for one-way and press-to-answer voice connections using a dedicated pair of intercom directory numbers on two phones that speed-dial each other. If we have to c0nfigure Intercom between two phones..lets say between a manager phone and his that both these intercom numbers are not reachable from rest of the cluster and are not dial-able. This is how we can configure this: ephone-dn  9 description Manager number D40 no-reg primary intercom E50 ! ephone-dn  10 description Secretary number E50 no-reg primary … Continue reading CME Intercom Lines

CME PerPhone command

You can use an external TFTP server to off load the TFTP server function on the Cisco Unified CME router. This is also important if your router is not a high end router while the CME configuration is complex with many phones and expansion modules. Also Using flash memory or slot memory on the Cisco Unified CME router allows you to use different configuration files for each phone type or for each phone, which allows you to specify different user locales and network locales for different phones To define a location other than system:/its for storing configuration files for per-phone and per-phone type configuration … Continue reading CME PerPhone command

Scenario#19 – CME Phone not Ringing

This was a very interesting scenario I came across for this customer where these two phones were not ringing at all. Any incoming call and they would just flash. No Ringtone. I confirmed that the phones were working fine few days back but then suddenly started just flashing. One other phone in the same group was working fine. I matched the configuration of all three phones and they were all same. I know that the only way you can change the ring settings from CLI is from the button command.If you are using ‘:’ then that means Ring. Taken from … Continue reading Scenario#19 – CME Phone not Ringing

Scenario#12 – Cannot Transfer calls CME

Customer reported an issue that they cannot transfer calls. Any external inbound call cannot be transferred to Internal numbers and any Internal call cannot be transferred to Internal extensions or any number outside. My first check was to make sure what they have got under telephony-service..a snapshot of it as follows: telephony-service no auto-reg-ephone authentication credential cueadmin xxxxxx max-ephones 30 max-dn 150 ip source-address port 2000 timeouts interdigit 4 system message xxxxxxxxxxx url services url authentication load 7936 cmterm_7936.3-3-16-0 load 7970 SCCP70.8-4-2S load 7971 SCCP70.8-4-2S time-zone 21 time-format 24 date-format dd-mm-yy voicemail 4000 max-conferences 4 gain -6 … Continue reading Scenario#12 – Cannot Transfer calls CME

Scenario#11 – Getting ‘unknown number’ when making outbound calls

I came across this issue last week. When making outbound calls, Instead of their DDI, the called party was getting ‘unknown number’. The system was on CME 7.0. I jumped on the gateway and started dissecting the bits and pieces. It was quite a long running config so I just took out what was important. The config below is useful to understand how translation rules, dialpeers and Trunk group work. This rule to prefix incoming calling party number with 9, 90, 900 depending upon the type. voice translation-rule 1 rule 1 /^\(.*\)/ /9\1/ type subscriber subscriber rule 2 /^\(.*\)/ /90\1/ … Continue reading Scenario#11 – Getting ‘unknown number’ when making outbound calls

Ephone Hunt Group

To enter ephone-hunt configuration mode for the purposes of creating and configuring a hunt group for use in a Cisco Unified CME system, use the ephone-hunt command in global configuration mode. To delete a hunt group, use the no form of this command. ephone-hunt hunt-tag {longest-idle | peer | sequential} hunt-tag – Unique sequence number that identifies the ephone hunt group during configuration tasks. Range is from 1 to 100. longest-idle – Hunt group in which calls go to the ephone-dn that has been idle the longest. peer –     Hunt group in which the first extension to ring is the number … Continue reading Ephone Hunt Group

IP Phone Background Image CME

Follow the process to change background Image for phones connected to CME. Lets take 7961 IP phone as an example. First of all load List.xml and Background Image files on a TFTP server. I would recommend you do it on a Call manager if it’s accessible from CME router. Just go in OS Admin and upload all files at root of CUCM TFTP. List.xml will be like this: <CiscoIPPhoneImageList> <ImageItem Image=”TFTP:Desktops/320x196x4/small.png” URL=”TFTP:Desktops/320x196x4/large.png”/> </CiscoIPPhoneImageList> At CME router do the following: Ping the tftp server and check connectivity Check if there is a directory on flash like Desktops/320x196x4/List.xml if not then make … Continue reading IP Phone Background Image CME