Analog phone via built-in FXS port?

Unanswered Question
May 30th, 2006
User Badges:

Hello,


We currently have a Cisco CallManager Express implementataion with a 2811 router, 4 built-in FXS and 4 FXO ports, and (5) 7960 IP phones. We would like to use a standard cordless phone for manager only usage early in the morning.


We connected the phone to the first FXS port and are able to dial out and make calls properly as per the dial-peers that are already configured. We would like to configure this FXS port so this analog phone could function similar to an IP phone (answering incoming calls, possibly transfer and on-hold functions).


I've read the CCME admin guide and the guide on voice ports, but I'm having trouble with the solution. I understand that it needs to be configured as an ephone, but how do I configure the ephone to point to the FXS port? Or am I way off base?


Thanks in advance!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
gpulos Tue, 05/30/2006 - 13:30
User Badges:
  • Blue, 1500 points or more

try this....(change some settings as they pertain to your environment)



router(config)# ephone-dn 1 dual-line

router(config-ephonedn)# number 2500

router(config-ephonedn)# label user1

router(config-ephonedn)# call-forward busy 2599 (2599 can be voice mail, etc)

router(config-ephonedn)# call-forward noan 2599 (2599 can be voice mail, etc)


router(config)# ephone 1

router(config-ephone)# username user1

router(config-ephone)# mac-address xxxx.xxxx.xxxx (mac of your phone)

router(config-ephone)# type 79xx (type of ip phone in use)

router(config-ephone)# button 1:1 (assign ephone-dn 1 to button 1)


router(config)# voice-port 1/1/0

router(config-voiceport)# no shut

router(config-voiceport)# connection PLAR 2500

router(config-voiceport)# port 1/1/0


also, see this link for more info:

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00804ad863.html


maharris Tue, 05/30/2006 - 14:58
User Badges:
  • Silver, 250 points or more

Analog phones are a little different, especially connected to fxs ports:

Analog Phone Support Restrictions


•Cisco Unified CME features such as call forward and call park are not available for analog phones connected to FXS ports in H.323 mode. In order to support these features, SCCP supplementary features must be enabled on the FXS ports. For information about SCCP supplementary features, see the "Analog Phones" section on page 138 and the Cisco Unified CME data sheet.


FXS ports on platforms that cannot enable SCCP supplementary features can use H.323 mode to support call waiting, caller ID, hookflash transfer, modem pass-through, fax (T.38, Cisco fax relay, and pass-through), and PLAR. These features are provisioned as Cisco IOS voice features and not as Cisco Unified CME features. Note that when using Cisco Unified CME, you can configure FXS ports in H.323 mode for call waiting or hookflash transfer, but not both at the same time.


The following links provide information on analog phone features for FXS ports in H.323 mode:


– "Configuring Analog Voice Ports" section in the Voice Port Configuration Guide


–" Caller ID" section of the Cisco IOS Voice Configuration Library


– Cisco IOS Fax and Modem Services over IP Application Guide

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00805c69d8.html#wp998550


The easy answer it to put the phone on an ATA instead of an fxs port.


Mary Beth

aceprecision-jasonl Wed, 05/31/2006 - 05:10
User Badges:

Well, what if I didn't care about the special features...what if I just wanted to allow someone to dial out and answer incoming calls with the analog phone connected to the FXS port?


The phone can already dial out using the dial-peers in place...but I would like the analog phone connected to the FXS port to be able to answer incoming calls? Basically, how do I make it ring when a call comes in?



aceprecision-jasonl Wed, 05/31/2006 - 05:12
User Badges:

Ok, so I already have this on my FXO ports:


voice-port 0/0/0

supervisory disconnect anytone

connection plar opx 150

description FXO-xxx-xxx-xxxx

station-id name Outside Line

!

voice-port 0/0/1

supervisory disconnect anytone

connection plar opx 151

description FXO-xxx-xxx-xxxx

station-id name Outside Line

!

voice-port 0/0/2

supervisory disconnect anytone

connection plar opx 152

description FXO-xxx-xxx-xxxx

station-id name Outside Line


And this as a dial-peer for my FXS port:


dial-peer voice 400 pots

description Cordless Phone

destination-pattern 160

port 0/1/0


I would remove that and make a dial-peer such as this:


dial-peer voice 400 pots

description Cordless Phone

destination-pattern 150

port 0/1/0


And any calls coming in on my first FXO port would also ring my analog phone on the first FXS port? (allowing someone to answer using the analog cordless phone if they are not near an IP phone)


Is that correct? Or, does the destination-pattern just signify the extension number of the phone on the FXS port?


Thanks for all the help by the way!

aceprecision-jasonl Wed, 05/31/2006 - 07:10
User Badges:

Here is a sanitized config from the router:



voice-port 0/0/0

supervisory disconnect anytone

connection plar opx 150

description FXO-xxx-xxx-xxxx

station-id name Outside Line

!

voice-port 0/0/1

supervisory disconnect anytone

connection plar opx 151

description FXO-xxx-xxx-xxxx

station-id name Outside Line

!

voice-port 0/0/2

supervisory disconnect anytone

connection plar opx 152

description FXO-xxx-xxx-xxxx

station-id name Outside Line

!

voice-port 0/0/3

description FXO-Unused

!

voice-port 0/1/0

description Cordless Phone

station-id name Cordless Phone

caller-id enable

!

voice-port 0/1/1

!

voice-port 0/1/2

!

voice-port 0/1/3

!

!

!

!

!

dial-peer voice 201 pots

preference 3

destination-pattern 91..........

port 0/0/1

forward-digits 11

!

dial-peer voice 202 pots

preference 2

destination-pattern 91..........

port 0/0/2

forward-digits 11

!

dial-peer voice 200 pots

preference 4

destination-pattern 91..........

port 0/0/0

forward-digits 11

!

dial-peer voice 100 pots

preference 4

destination-pattern 9[2-9]......

port 0/0/0

forward-digits 7

!

dial-peer voice 101 pots

preference 3

destination-pattern 9[2-9]......

port 0/0/1

forward-digits 7

!

dial-peer voice 102 pots

preference 2

destination-pattern 9[2-9]......

port 0/0/2

forward-digits 7

!

dial-peer voice 300 pots

preference 4

destination-pattern 9T

port 0/0/0

!

dial-peer voice 301 pots

preference 3

destination-pattern 9T

port 0/0/1

!

dial-peer voice 302 pots

preference 2

destination-pattern 9T

port 0/0/2

!

dial-peer voice 400 pots

description Local FAX on router

destination-pattern 160

port 0/1/0

!

!

!

!

telephony-service

load 7910 P00403020214

load 7960-7940 P00305000600

max-ephones 36

max-dn 144

ip source-address 192.168.10.254 port 2000

create cnf-files version-stamp Jan 01 2002 00:00:00

max-conferences 8 gain -6

moh music-on-hold-1.wav

multicast moh 239.1.1.1 port 2000 route 192.168.10.254

transfer-system full-consult

secondary-dialtone 9

!

!

ephone-dn 1

number 150

label Line-1

description Outside Line 1

hold-alert 30 shared

!

!

ephone-dn 2

number 151

label Line-2

hold-alert 30 shared

!

!

ephone-dn 3

number 152

label Line-3

hold-alert 30 shared

!

!

ephone-dn 100

number 100

label location0 100

description xxx-xxx-xxxx

name Office

!

!

ephone-dn 101

number 101

label location1 101

description xxx-xxx-xxxx

name location1

!

!

ephone-dn 102

number 102

label location2 102

description xxx-xxx-xxxx

name location2

!

!

ephone-dn 103

number 103

label location3 103

description xxx-xxx-xxxx

name location3

!

!

ephone-dn 104

number 104

label location4 104

description xxx-xxx-xxxx

name location4

!

!

ephone-dn 105

number 105

label location5 105

description xxx-xxx-xxxx

name location5

!

!

!

!

ephone 1

mac-address xxxx.xxxx.xxxx

type 7960

button 1:100 2:1 3:2 4:3

!

!

!

ephone 2

mac-address xxxx.xxxx.xxxx

type 7960

button 1:101 2:1 3:2 4:3

!

!

!

ephone 3

mac-address xxxx.xxxx.xxxx

type 7960

button 1:102 2:1 3:2 4:3

!

!

!

ephone 4

mac-address xxxx.xxxx.xxxx

type 7960

button 1:103 2:1 3:2 4:3

!

!

!

ephone 5

mac-address xxxx.xxxx.xxxx

type 7960

button 1:104 2:1 3:2 4:3

!

!

!

ephone 6

mac-address xxxx.xxxx.xxxx

type 7960

button 1:105 2:1 3:2 4:3


maharris Wed, 05/31/2006 - 08:13
User Badges:
  • Silver, 250 points or more

Yes, an incoming call that hits that fxo port will plar to ext 150 - which would be that fxs port, unless you happen to have an IP phone that also has that number on it, in which case it totally ignores the destination pattern on the fxs port. It you have new enough software, I think cme 3.4, it actually will give busy if you try to share the line, but with older stuff, it at least rings the ip phone. I just went through this, worked with TAC because we could not believe it was true, but we had not actually tried it before. Can duplicate in our lab, too. If you need to share the line with an ip phone, you have to get SCCP controlled analog line, like ATA.


Mary Beth

maharris Wed, 05/31/2006 - 08:54
User Badges:
  • Silver, 250 points or more

Looking more carefully at what you posted, yes the dial-peer with the destination pattern of 150 would be the way to ring that fxs port, but it looks like you also have ephone dn with that number, so IP phone is using it, and as I mentioned before, that will not work. You could remove the ephone dn and put in the dial peer and test that you port rings, but it looks like you already have a fax taking calls, so you know that works, it is the sharing that will not work, and would require something like an ATA.

Mary Beth

Actions

This Discussion