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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Delayed Unity Port release

Switch was changed from Avaya to Nortel on a Unity 3.1.5 platform. Now when a call is made into Unity, it takes about 60 secs after the call is completed for Unity to release the port. What could be causing this?

Cisco Employee

Re: Delayed Unity Port release

The Avaya was probably sending positive disconnect signaling such as a loop current drop. The Nortel should at least be sending dial tone or reorder tone as disconnect. When you made the move on the PBX side did you also change the switch configuration file used by Unity? With the Avaya switch file, Unity won't look for dial tone as a disconnect. If you are already using the Nortel0001.ini switch file then we may need to fine tune the tone definitions.



New Member

Re: Delayed Unity Port release

Yes it is pointing to the right file (Nortel0001) and you are right there were some tone definitions that need to be set in the switch file which fixed the disconnet issue.

We are now getting a different issue where voice messages are getting cut off. We have checked the System => Configuration settings and all seems fine there. We have set the parameterfile on the Dialogic card to "quiet50.prm" to make the dialogic card more attentive. All these have not worked. Any ideas??

Cisco Employee

Re: Delayed Unity Port release

I'd guess now that LearnTones was the method used to adjust the tone definitions in that switch file. With Unity 3.1(5) you're probably hitting CSCdz72630. If that's the case you can use Notepad to change Cycles=0 to Cycles=4 for each tone in the Nortel0001 file. Hopefully that'll do the trick for you.