ip office lines stuck off hook after forwarding 2

[pccsipoffice]

Ip office 9.1
We have been experiencing phone lines not hanging up after a call has been forwarded outside.
4 pots lines in use all trunk to trunk connect allowed.
We find that a call forwarded to a cell phone will use two lines on the system but
after the call ends the lines remain off hook.
This has been an ongoing issue we need to resolve. A new cisco spa8000 is used for lines.
We would appreciate any thoughts on this.

http://WWW.MC-COMMUNICATIONS.NET

 

[Nortel4Ever]

Obviously the Cisco device is not sending a proper disconnect signal to the IPO so it doesn't know that the calls have dropped. I don't know this Cisco device at all so are there any disconnect tone options that are configurable within it?

If the Cisco device provides busy tone after calls disconnect then you need to enable Busy Tone Detection under System - Telephony - Tones and Music. My Telco's fibre to POTS device they installed at my home provides a busy tone if the far end hangs up first so perhaps the Cisco device does the same?

There is a setting called Unsupervised Analog Trunk Disconnect Handling that can be enabled, but doing that will disable the Allow Trunk to Trunk setting.

Instead of using a Cisco IP to POTS device why not SIP trunks?

That's all I've got, good luck...

 

[pccsipoffice]

Thanks nortel4ever
Everything you said makes sense. We did the busy tone detection a couple weeks ago but it
looks like that did not help.
We are looking at the Cisco admin now to see what it looks like.

http://WWW.MC-COMMUNICATIONS.NET

 

[pccsipoffice]

this thread refers to a possible solution but I don't understand how to implement it.

https://www.tek-tips.com/viewthread.cfm?qid=1758927

http://WWW.MC-COMMUNICATIONS.NET

 

[Nortel4Ever]

Telephone Number Field Characters
t = Allowed Call Duration Set the maximum duration in minutes for a call plus or minus a minute. Follow the character with the number of minutes in brackets, for example t(5).

So I think it might look like this:
9N
Dial
Nt(5)

I think a call dialed out using 9 would then disconnect after 5 minutes

I've never used this before, but it's easiest enough for you to experiment with it. For starters try 1 for 1 minute.

 

[budbyrd]

Cisco doesn't have clear disconnect on by default. They do have a setting for it though. I have no clue what they call it though. I went through that not disconnecting thing for a paging system I was installing last week.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[pccsipoffice]

Thanks Budbyrd the Cisco manual does not have anything spelled out about it but I may take a look at the GUI and
see what is there.
Thanks nortel I will do that on our test system that happens to be our office phones.
I will update this thread with what I find.

http://WWW.MC-COMMUNICATIONS.NET

 

[budbyrd]

What I do know is it had a setting for .5 seconds. Which is the standard for CDS. I don't think the engineer knew what he was doing either.... But it worked. For reference to the IPO and the situation... You have to set the port to IVR. The standard IPO analog port also doesn't have CDS on by default and you will get a reorder over your paging system.


Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[pccsipoffice]

Budbyrd I think you are talking about CPC in the cisco spa8000 manual essentially it is reorder tone or voltage drop to 0 for disconnect.
Avaya wants voltage drop until you set reorder tone instead. Cisco can be set to voltage drop instead. I doubt I will play with it as
I need to resolve this once and for all.

Nortel4ever that works, I would prefer to use that as a last resort, however without
knowing 100% if the CISCO ata changes are going to work perfectly with this periodic problem, I am likely
to just put this on for 90 minutes and call it good for now.

Thanks

http://WWW.MC-COMMUNICATIONS.NET

 

[budbyrd]

Clear disconnect is a 500ms voltage drop. We have the same issue with converted analog lines from our cable company and reorder is a drag to try to get to work consistantly. Solves the issue. If the 500ms isn't working, in the IPO its timing is adjustable.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[Ekster]

The actual setting on the Avaya trunk needs to be less than the time configured on the line:


Default = 500ms.
Range = 0 to 2550ms. This time must be less than the actual disconnect time period used by the line provider by at least 150ms.

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

 

[IPGuru]

If you insist on using Cisco ATA's for the lines then Disconnect clear setting is indeed the correct way to go
however I would re-iterate notel4evers advice
ditch the ATA's & configure the sippppp directly form the IP office. The improvments will be enormous, the most obvious are:-


1) Only 1 single point of failure (the IPO not the IPO or the ATA)
2) The ability to accept multiple calls on the same number

Also you would be able to fully utilise the mobility functions includinng mobile call control & mobile call back.


Do things on the cheap & it will cost you dear

Avaya Remote Support Engineer (A.R.S.E)