Archive for the ‘VoIP’ Category

CME/UC500: IP phones, dual-line, and call waiting

Tuesday, March 3rd, 2009 by tburns

Most of the 7900 series Cisco IP phones can be configured for dual-line capability. The most notable exceptions are the 7936/7 series conference phones and the 7921 series wireless phones that are both considered single-line. In this case, dual-line function allows an incoming call to display on an IP phone when that phone is off-hook or otherwise already in use. This is not to be confused with a telco-enabled call-waiting feature that may be installed on an analog, CO line. For information on how to use that feature, reference this, earlier post.

There may be reasons why you wouldn’t want a phone to display more than one active/alerting call at a time. If, for example, you have a call center or other type of hunt group function, you may not want additional calls to be coming in to a hunt group member when that person/phone is already engaged.
Read more »

Directing calls in and out a specified fxo port

Tuesday, February 10th, 2009 by tburns

I was asked to install a new analog circuit on a UC520 system to add to the several existing analog lines already on the box. The company was adding a new product line, and wanted the new line, with the new number to display a different caller-id than the company had been displaying when placing outbound calls. In other words, there were no new employees in Company ABC, they simply wanted a different visual presence to show their customers when working the phones for the new product line which they were calling, Company XYZ.

To do this, I created a new trunk group via a global config command:

!
trunk group  xyz
 description outgoing xyz calls
!

Read more »

Don't park a page (configuring simple park slots)

Saturday, February 7th, 2009 by tburns

Last week, I was at a customer’s location where I had previously installed a CME build. They have on order a PRI and associated DIDs to cover the current users with plenty more for growth. They had hoped to coordinate the PRI install with the CME install, but couldn’t get the telco to move as quickly as they wanted.

I installed the CME build (v.7.0.0.1 on a 2821) with three FXO 4-port cards to handle the 11 analog lines they have coming into the facility. They handle incoming calls through a rotating receptionist system where there is one primary receptionist who forwards calls to one of two other backup receptionists. They are looking forward to getting the DIDs so they can reduce the number of calls handled by the receptionists.

Read more »

CME – Configuring Overhead Paging

Thursday, February 5th, 2009 by tburns

I was asked to configure two paging groups for a customer. One, for through-the-phone paging; and one for both through-the-phone paging AND overhead paging using a Bogan PA device. The idea was that not all employees needed to hear every page, and the receptionist was able to decide which of the two pages she would use at any one time.

First, I configured paging through-the-phones. I used the 239.0.1.0 multicast address and assigned this address .10 for no good reason but that I expected to run multicast addresses sequentially from that point:

!
ephone-dn  105
 number 400
 label Phone Paging
 name Phone Paging
 paging ip 239.0.1.10 port 2000
!

Read more »

Cisco CME 7.0.0.1 – Background images

Monday, February 2nd, 2009 by tburns

I recently installed a site where the customer ordered the 6-button 7965 phones with CME 7.0.0.1. The background images were not loading when the phones came up. Debugging TFTP packets indicated that the phones were looking for the images list file (List.xml) in a folder called flash:Desktops/320×212x16. Instead of flash:Desktops/320×212x12, which is where all the images were stored. I’d already configured all the tftp-server entries for the images, so I created a new folder in flash called 320×212x16:

Router#mkdir flash:Desktops/320x212x16/
Create directory filename [Desktops/320x212x16/]?
Created dir flash:Desktops/320x212x16
Router#

Read more »