cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
968
Views
5
Helpful
5
Replies

FXO Remains Busy after PSTN User HangUP - Only seen with Unity

jmujica
Level 1
Level 1

Here is the situation..

I have all calls arriving on FXO ports go to Unity for Auto Attendant Capabilities. What happens is if I start listening to the Unity Conversation and I hang up the call for some reason the FXO remain open for a long period of time. Also if I get transfer to a subscriber and I reach the subscriber VoiceMail and I hang up the call, the line also remains open for a long period of time. That doesn't happen if I'm oonnected to an IP Phone and then I hang up the call then the FXO port is available in a resonable time.

I got the following command in the FXO port of the router. I don't know if I'm missing something else on the router, CCM or even Unity..

!

timeouts interdigit 2

timeouts call-disconnect 2

connection plar opx (VM-Pilot)

supervisory disconnect dualtone mid-call

!

I'm using H323 for signalling to the gateway.

Gateway - Cisco 2611XM with 12.3(7)T IP-VOICE

NM-HD-2VE with VIC2-4FXO

CCM - v3.3(3)SR4

Unity - v4.0(3)SR1

TSP - Latest TSP Version..

Can someone point me into the right direction as this is getting very critical for my client because the lines are always busy because are not getting disconnected as fast as it should be.

Sorry for the long post

TIA

-Jose

5 Replies 5

cbuckingham
Level 1
Level 1

Try adding:

timeouts call-wait 2

I had the same issue w/ MGCP g/w - and this is the only command differance I see - I had a 5 min delay reduced to less than 10 seconds.

Good Luck!

Chris

I don't have that command available in the router. I tried the timeouts wait-release but without any luck. After the PSTN get to the Auto Attendant and for some reason disconnect the call, the fxo port remain open for more than 1 minute.

That is making the lines busy most of the time..

TIA,

-Jose

Hi,

The command worked for me after I entered some additional configuration shown below. This is from a white paper titled "Cisco | Understanding FXO Disconnect Problem"

Hope you can get it working!

Erik

FXO_Paper#configure terminal

FXO_Paper(config)#voice-port 3/1/1

FXO_Paper(config-voiceport)#supervisory disconnect dualtone mid-call

FXO_Paper(config-voiceport)#cptone us

FXO_Paper(config-voiceport)#timeout wait-release 5

FXO_Paper(config-voiceport)#timeout call

{exit}

danielvilla
Level 1
Level 1

Jose,

Try adding this lines to the voice-port 3/0 configuration:

!

cptone

no battery-reversal

timeouts call-disconnect 5

timeouts wait-release 5

!

Regards

DV

dariush90
Level 1
Level 1

Found the solution:

important part is the supervisory disconnect as it checks the tones coming in mid-call also the cptone is important this is the tone the PSTN creats when the call ends. 

voice-port 1/1/0
 supervisory disconnect dualtone mid-call
 cptone NL
 timeouts call-disconnect 5
 timeouts wait-release 5
 timing hookflash-out 50