Voice Ports Not working

Answered Question
Feb 4th, 2008
User Badges:

I have a 2801 router with 2 voice ports connecting to 2 PSTN lines. The router is a CCME,running IOS c2801-advipservicesk9-mz.124-4.T1.bin, supporting a few IP phone. Port 0/2/0 is added recently. I copied the config from port 0/2/1. But it does not work. 'debug voip ccapi inout' shows both incoming dial-peer and out-going dial-peer are matched, but success is 0. Why did this happen? When I swapped the PSTN line on the 2 voice ports, the new line started working, the old line stopped working. Can anyone there give me a hand? The configuration is as follows.

===============

voice-port 0/2/0

no battery-reversal

connection plar opx 300

caller-id enable

!

voice-port 0/2/1

no battery-reversal

connection plar opx 300

caller-id enable

!

dial-peer voice 1 pots

description ** FXO pots dial-peer **

destination-pattern 1111

port 0/2/1

forward-digits 3

!

dial-peer voice 2 pots

description ** FXO pots dial-peer **

destination-pattern 1T

port 0/2/1

!

dial-peer voice 3 pots

description ** FXO pots dial-peer **

preference 1

destination-pattern 1111

port 0/2/0

forward-digits 3

!

dial-peer voice 4 pots

description ** FXO pots dial-peer **

preference 1

destination-pattern 1T

port 0/2/0

!

ephone-dn 1 dual-line

number 301

hold-alert 30 originator

!

!

ephone-dn 2 dual-line

number 302

hold-alert 30 originator

!

ephone-dn 10 dual-line

number 300

label Main Line

description Main Line

name Main Line

!

ephone 1

mac-address 0016.47A8.6623

type 7940

button 1:1 2:10

!

ephone 2

mac-address 0016.9DD2.1A2E

type 7940

button 1:2 2:10

!

============================



Correct Answer by Robert Salazar about 9 years 2 months ago

Looks like that port 0/2/0 is locked up.

You may need to either bounce the voice port or reload the gw.

The correct operational state is seen in port 0/2/1 when the status is on-hook.


Bounce the voice port and/or reload the gateway and see if port 0/2/0 comes back.

Then let me know.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
paolo bevilacqua Mon, 02/04/2008 - 13:34
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, which exact IOS are you using? Some are buggy and would benefit from a reload.

Chuan Liu Mon, 02/04/2008 - 13:36
User Badges:

Thanks for the quick response. I am running c2801-advipservicesk9-mz.124-4.T1.bin

pcameron Mon, 02/04/2008 - 13:37
User Badges:
  • Cisco Employee,

You said "When I swapped the PSTN line on the 2 voice ports, the new line started working, the old line stopped working"


Your Configs look OK. If the old line works in the new voice port, this sounds like the actual line is not working properly. If you have a old analogue handset lying around, plug it into the new line directly and confirm if you are getting dial tone and can make calls.

Chuan Liu Mon, 02/04/2008 - 13:43
User Badges:

I swapped the new line into the 'old' port, it is working. But not the other way round.

Robert Salazar Mon, 02/04/2008 - 13:49
User Badges:
  • Cisco Employee,

Try removing the connection plar statement from the newly added voice port that doesn't work.

Then when you dial into that port/line you should get a second dialtone.

When you hear that dialtone, try dialing the extension from the plar config '300'.

See if that rings the desired phone.

You may need to check the show voice port status to see if there's any difference in status from port 0/2/0 and 0/2/1.

Chuan Liu Mon, 02/04/2008 - 13:57
User Badges:

The show output is as follows:

sh voice port su

IN OUT

PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC

========= == ============ ===== ==== ======== ======== ==

0/2/0 -- fxo-ls up up idle on-hook y

0/2/1 -- fxo-ls up dorm idle on-hook y


One is up, which is the non-working one; the other is dorm. What is the difference?



I just tested removing the plar command. I did not get a second dialtone. It keeps ringing.


Correct Answer
Robert Salazar Mon, 02/04/2008 - 14:16
User Badges:
  • Cisco Employee,

Looks like that port 0/2/0 is locked up.

You may need to either bounce the voice port or reload the gw.

The correct operational state is seen in port 0/2/1 when the status is on-hook.


Bounce the voice port and/or reload the gateway and see if port 0/2/0 comes back.

Then let me know.

Chuan Liu Wed, 02/06/2008 - 12:30
User Badges:

Hi,


Problem solved by reloading the router.


Thanks for all the tips.

MooneyN Mon, 02/04/2008 - 19:20
User Badges:

This has been seen before on FXO ports for CCME. The FXO ports mysteriously lock up and need to be manually shut/no-shut, or the router rebooted.


Check for known bugs and consider software upgrades. Or consider migration to ISDN if possible.


Actions

This Discussion