Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Silver

RNA on FXO

I have a remote ISR with a POTS line connected to an FXO port which is not picking up. A tech dispatched, unplugged the POTS from the FXO port and tested it good both ways with a butt set. However, once it's plugged back in I just get RNA and it shows idle when calling the DID #.

The configs are pretty basic:

voice-port 0/2/0

input gain 10

connection plar 4800

caller-id enable type 1

I've also tried to manually set the signalling to groundstart from the default loopstart (which it should be). I wasn't working the issue while the tech was onsite so I wasn't able to get him to move the POTS to another FXO port to rule out a faulty port. ...but how probable is that.

Any ideas?

thanks,

Will

5 REPLIES

Re: RNA on FXO

you can 'debug vpm signal' and see if it's coming in on the port you expected.

Additionally, you can look at your other dial peers and figure out how the router is supposed to reach 4800. Try changing this to another number and see if you get different results.

hth

nick

Silver

Re: RNA on FXO

I didn't get anything on the vpm signal debug. I'm positive that it's not the 4800 dial-peer because a show voice port summary shows that the port is idle and on-hook.

Re: RNA on FXO

If you do 'debug vpm signal', and you've correctly configured debugging - it's not hitting your router.

Try these commands in global config:

no logg mon

no logg con

no logg rate

serv seq

serv time deb date mse lo

logg buff 2000000 7

Then in exec:

clear log

show logg

hth,

nick

Re: RNA on FXO

Is this gateway MGCP controlled or H323? If it is MGCP the plar statement means nothing while the ccm is controlling the port.

Also just try a shut/no shut on the port.

Mc

Silver

Re: RNA on FXO

Good troubleshooting steps. Thanks!

I tried this and didn't see any output, but after bouncing the FXO port, the log shows this:

00305: .Jan 28 14:45:17.364: htsp_process_event: [0/2/0, FXOLS_ONHOOK, E_HTSP_IF_OOS]htspm_mgt_state

000306: .Jan 28 14:45:17.364: htsp_timer_stop

000307: .Jan 28 14:45:17.364: htsp_timer_stop2

000308: .Jan 28 14:45:17.364: htsp_timer_stop3

000309: .Jan 28 14:45:17.364: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/2/0, changed state to Administrative Shutdown

000310: .Jan 28 14:45:17.364: htsp_process_event: [0/2/0, S_OPEN_PEND, E_DSP_INTERFACE_INFO]

000311: .Jan 28 14:45:17.536: htsp_process_event: [0/2/0, S_DOWN, E_DSP_SIG_0110]

000312: .Jan 28 14:45:19.392: htsp_process_event: [0/2/0, S_DOWN, E_HTSP_IF_INSERVICE]

000313: .Jan 28 14:45:19.396: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/2/0, changed state to up

000314: .Jan 28 14:45:19.396: Foreign Exchange Office 0/2/0 rx_signal_map:

F F F F

5 F F F

F F F F

F F F F

000315: .Jan 28 14:45:19.396: [0/2/0] set signal state = 0x4 timestamp = 0

000316: .Jan 28 14:45:19.396: Foreign Exchange Office 0/2/0 tx_signal_map:

0 4 4 4

4 4 6 4

C C C C

C C C C

000317: .Jan 28 14:45:19.396: htsp_process_event: [0/2/0, S_OPEN_PEND, E_HTSP_GO_UP]

000318: .Jan 28 14:45:19.508: htsp_process_event: [0/2/0, FXOLS_NULL, E_HTSP_INIT]fxols_null_init

000319: .Jan 28 14:45:19.508: [0/2/0] set signal state = 0xC timestamp = 0

000320: .Jan 28 14:45:19.508: htsp_process_event: [0/2/0, FXOLS_INIT, E_HTSP_INSERVE]fxols_init_inserve

000321: .Jan 28 14:45:19.508: [0/2/0] set signal state = 0x4 timestamp = 0

000322: .Jan 28 14:45:19.508: htsp_process_event: [0/2/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

000323: .Jan 28 14:45:19.512: htsp_process_event: [0/2/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

The tech who dispatched swears that he put a buttset on the line (both at the demarc as well as the line going into the FXO port), called his cell, and redialed from his cell and the buttset rang.

That only leaves the FXO port right? Doubt this would matter at this point since the FXO port never goes off-hook but it's H.323 back to callmgr. I've never been able to get the csim start to actually dial out through either a POTS or PRI, but I'd like to verify if outbound dialing is working.

Anyways....this is where I'm at now.

thanks,

Will

345
Views
0
Helpful
5
Replies
CreatePlease to create content