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

FXO problem

Situation :-

we are facing a problem with FXO ports,We are using vic2-4FX0 with 2801 router (CCME).When we execute cisco IVR script (its-CISCO.2.0.1.0.tcl) for incoming call legs (for my company PSTN number) , its work fine. but when external user from PSTN disconnect its phone my internal phones or operator phone continuously rings. there is no automatic disconnection possible. only one way operator can disconnect his phone or stop ringing by manually pressing button on his phone set. Without execution of IVR script all things work fine no disconnection problem occur .

We have checked with both versions

i) Version 12.4(13r)T, RELEASE SOFTWARE (fc1)

ii) (C2801-IPVOICE-M), Version 12.3(14)T7

3 REPLIES
Hall of Fame Super Gold

Re: FXO problem

Hi,

you are experiencing the classic supervision disconnect problem. After the caller hang-up, the system has no way to know that he/she has abandoned the call. Please see:

http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml

Note, unless you are in north america, ground-start signaling is not available.

Battery reversal and power denial may or may be not available depedning on your location.

Most likely you will need to configure disconnect supervision based on tones. This can be a little difficult, but is explained in the document above.

Hope this helps, please rate post if it does!

Community Member

Re: FXO problem

Dear Sir i have checked all the commands which are mentioned in the cisco document (

http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml )

But still i cannt resolve this problem. I dont know what i am doing wrong .

These are my debugs which i found .

This is the debug when External PSTN user has disconnect its phone . but operator status is still off-hook.

debug vpm port 0/0/0

debug vpm signal

duplex auto

speed auto

May 26 04:45:41.475: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100].110 255.255.255.0

duplex auto

ling time=05/26 04:45 orig called=

May 26 04:45:41.479: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SE

TUP_ACK]

May 26 04:45:41.479: fxols_wait_setup_ack:

May 26 04:45:41.479: [0/0/0] set signal state = 0xC timestamp = 0fxols_check_aut

o_call

May 26 04:45:41.487: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_SETUP_

ACK]

May 26 04:45:41.487: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEE

DING]fxols_offhook_proc

May 26 04:45:41.487: htsp_timer - 120000 msec

May 26 04:45:41.487: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_CONNEC

T]fxols_offhook_connect

May 26 04:45:41.487: htsp_timer_stop

May 26 04:45:41.491: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT

_THROUGH]fxols_connect_proc_voice

May 26 04:45:41.751: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_DSP_SIG_0110]f

xols_rvs_battery

May 26 04:46:01.483: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT

_THROUGH]fxols_connect_proc_voice

May 26 04:46:22.035: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT

_THROUGH]fxols_connect_proc_voice

May 26 04:46:42.587: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT

_THROUGH]fxols_connect_proc_voice

show voice trace 0/0/0

THROUGH]fxols_connect_proc_voice

Router#sh voice trace 0/0/0

0/0/0 State Transitions: timestamp (state, event) -> (state, event) ...

13006.688 (S_SETUP_IND_PEND, E_VTSP_DSM_OPEN_SUCCESS) ->

13006.696 (S_SETUP_INDICATED, E_CC_SETUP_ACK) ->

13006.696 (S_DIGIT_COLLECT, E_CC_PROCEEDING) ->

13006.696 (S_PROCEEDING, E_CC_CONNECT) ->

State Transitions: timestamp (state, event) -> (state, event) ...

13006.684 (FXOLS_RINGING, E_DSP_SIG_0100) ->

13006.688 (FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK) ->

13006.696 (FXOLS_PROCEEDING, E_HTSP_SETUP_ACK) ->

13006.696 (FXOLS_PROCEEDING, E_HTSP_PROCEEDING) ->

13006.696 (FXOLS_PROCEEDING, E_HTSP_CONNECT) ->

13006.700 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

13006.960 (FXOLS_CONNECT, E_DSP_SIG_0110) ->

13026.692 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

13047.244 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

13067.796 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

13088.348 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

13108.900 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

This is the Result when operator manually disconnect its ip phone.

May 26 04:47:58.563: htsp_call_bridged invoked

May 26 04:47:58.575: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT

_THROUGH]fxols_connect_proc_voice

May 26 04:47:59.979: htsp_timer_stop3

May 26 04:47:59.987: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_RELEASE_R

EQ]fxols_offhook_release

May 26 04:47:59.987: htsp_timer_stop

May 26 04:47:59.987: htsp_timer_stop2

May 26 04:47:59.987: htsp_timer_stop3

May 26 04:47:59.987: [0/0/0] set signal state = 0x4 timestamp = 0

May 26 04:47:59.987: htsp_timer - 2000 msec

May 26 04:48:00.259: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_DSP_SIG_0110

May 26 04:48:01.987: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_T

IMER]fxols_guard_out_timeout

May 26 04:48:01.987: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

Can you please define the exect commands ?

I will be looking for your kind reponse.

Hall of Fame Super Gold

Re: FXO problem

Hi,

you need to configure supervisory disconnect based on tones. I cannot help you with exact commands, I would need to know where are you located and the tones that the CO switch sends when the caller disconnects.

Start with the examples, try to figure out the disconnect tone, and if problems post your config here.

This is the only solution with FXO ports. Else, you would need to use ISDN BRI, on which the problem never happens.

Thanks for the nice rating and good luck!

435
Views
5
Helpful
3
Replies
CreatePlease to create content