FXO Port Will Not Dial Out

Unanswered Question
Dec 19th, 2007
User Badges:

I have configured 911 dial peers to route out FXO ports on my 1760 router. When I dial 911 the light on the FXO port briefly lights up for half a second then goes out. It then trys the next FXO port and the same thing happens. I then receive a busy signal.


I have verified that the POTS line is good by plugging in an analog phone and dialing out. I have also tried different IOS versions and swapped out the FXO card with new. Nother seems to help. If you have any advice please post. Thanks in advance.


Below is a copy of the debug vpm signal.


000075: htsp_timer_stop3 htsp_setup_req

000076: htsp_process_event: [3/0, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_se

tup

000077: [3/0] set signal state = 0xC timestamp = 0

000078: htsp_timer - 1300 msec

000079: htsp_process_event: [3/0, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_pow

er_denial_proc

000080: htsp_timer2 - 1000 msec

000081: htsp_timer_stop

000081: htsp_timer_stop

s_timer2_proc

000083: htsp_timer_stop

000084: htsp_timer_stop2

000085: [3/0] set signal state = 0x4 timestamp = 0

000086: htsp_process_event: [3/0, FXOLS_ONHOOK, E_HTSP_RELEASE_REQ]fxols_onhook_

release

000087: htsp_timer_stop3 htsp_setup_req

000088: htsp_process_event: [3/1, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_se

tup

000089: [3/1] set signal state = 0xC timestamp = 0

000090: htsp_timer - 1300 msec

000091: htsp_process_event: [3/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

000092: htsp_process_event: [3/1, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_pow

er_denial_proc

000093: htsp_timer2 - 1000 msec

000094: htsp_timer_stop

000095: htsp_process_event: [3/1, FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER2]fxol

s_timer2_proc

000096: htsp_timer_stop

000097: htsp_timer_stop2

000098: [3/1] set signal state = 0x4 timestamp = 0

000099: htsp_process_event: [3/1, FXOLS_ONHOOK, E_HTSP_RELEASE_REQ]fxols_onhook_

release

000100: htsp_process_event: [3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Brandon Buffin Thu, 12/20/2007 - 08:17
User Badges:
  • Purple, 4500 points or more

Do you have "forward-digits 3" on your dial peers? Can you post your config?


Brandon

zebranutz80 Thu, 12/20/2007 - 08:21
User Badges:

Brandon,


Thanks for replying. This has been becoming a hi-priority issue with the administration. Below is a copy of the 2 dial-peers I use for 911. 8 is our outside access code. I also attached a current copy of the running config on this router.


dial-peer voice 8911 pots

description ***8911 calls over FXO - Priority 1***

destination-pattern 8911

port 3/0

forward-digits 3

!

dial-peer voice 911 pots

trunkgroup AnalogTrunks

description ***911 calls over FXO - Priority 1***

destination-pattern 911

forward-digits all



Attachment: 
Brandon Buffin Thu, 12/20/2007 - 08:33
User Badges:
  • Purple, 4500 points or more

Can you dial any other number with the 8T dial peer? Can you dial 8911 which points directly to the 3/0 port?


Brandon

zebranutz80 Thu, 12/20/2007 - 08:50
User Badges:

NO...


In SRST mode, I receive a dial tone from the router. When I dial 8 the FXO port briefly lights up then the line goes dead. I cannot make ANY calls out this FXO port.

Brandon Buffin Thu, 12/20/2007 - 09:32
User Badges:
  • Purple, 4500 points or more

Under call-manager-fallback, remove the "access-code fxo 8" command.


Brandon

zebranutz80 Thu, 12/20/2007 - 09:35
User Badges:

I removed the access-code and placed a test call. The same thing occurs. I have opened a TAC case they want me to upgrade the IOS. I'm not very confident that will fix the problem.

Actions

This Discussion